International SEO starts with choosing markets and languages: where there is demand, where you can actually deliver a product or provide a service, and which laws and payment methods apply there. Next, you choose the URL structure (a folder, a subdomain or a separate domain), add language versions with hreflang tags and adapt the content to each market. The first step is a business decision, and translation comes after it.
In brief
- Start with a business decision: which markets and languages have demand and which ones you are able to serve.
- For most small and medium-sized companies, one or two language versions are enough at the start.
- The URL structure (a folder, a subdomain or a separate domain) is chosen once and kept consistent.
- Hreflang tags link the language versions; errors in them are the most common.
- Localization covers terminology, currency, delivery, legal pages and examples along with the translation.
- Results in each market are measured separately in Search Console and analytics.
Do you need international SEO
You need international SEO when you want to attract customers from other countries through search: you export goods, provide services remotely, work with foreign clients or welcome tourists. If your customers are only Ukrainians abroad, Ukrainian-language pages with the right contacts and delivery terms are often enough.
Before launching, answer four questions.
- Is there demand: what Search Console, analytics and inquiries from abroad show.
- Can you serve customers: delivery, payment, support in the market's language.
- Which rules apply: taxes, consumer protection, personal data protection.
- What the competition is like: who holds the search results and what they offer.
Legal and tax questions depend on the country and the type of business, and they change. Check the current requirements with a lawyer or an accountant.
Step 1. Choosing markets and languages
A market is a country, a language is a means of communication. They do not always match: German is needed for Germany, Austria and part of Switzerland, English for many countries at once. Make a short table of candidates and rate them by demand, your ability to serve them, competition and maintenance cost.
Start with one or two markets. Every new language version needs translation, updates, checks and support, so expanding quickly into ten languages at once usually drains resources.
Regional variants of one language (for example, English for the UK and the US) are created only when the currency, spelling, delivery terms or legal requirements differ.
Step 2. URL structure
There are three main schemes for language and country versions. Google describes all of them in its documentation, so none of them is the only correct one.
| Scheme | Example | Advantages | Limitations |
|---|
| Separate country domain | example.de | A clear country signal, convenient separation of markets | More expensive and harder to maintain, each site is promoted separately |
| Subdomain | de.example.com | Hosting and teams can be separated, separate settings | Harder to recognize the country from the URL, promotion is partly separate |
| Folder on the main domain | example.com/de/ | Easier to launch and maintain, one site and one admin panel | One server location, technical settings are harder to separate |
For most small and medium-sized companies, folders or subdomains are simpler because they do not require separate sites. Separate domains are justified when the market is large and full local presence is needed: your own warehouse, team and legal entity.
Whatever the scheme, stay consistent: do not change the structure without need, and set up redirects and a sitemap for each version.
Step 3. Hreflang tags and language versions
The hreflang attribute tells Google which language or country version of a page is intended for which user. The rules are simple, but mistakes are common.
- Each version links to all the other versions and to itself; without reciprocal links the tags are ignored.
- The code consists of a language (uk, en, de) and, if needed, a country (en-GB, de-AT). For Ukrainian the correct code is uk; the country code UA is used only after the language, for example uk-UA.
- The x-default fallback version is shown to users for whom there is no exact match.
- The tags are placed in the head section of the page, in HTTP headers or in the sitemap.
- The URLs in the tags lead to indexable pages: no redirects, no 404 errors and no noindex.
Do not switch the language automatically based on the visitor's IP address. Such a redirect gets in the way of users and search engine crawlers, so it is better to offer a choice through a language switcher or an unobtrusive banner.
Step 4. Content localization
Localization covers everything that affects a customer's decision in a particular market.
- Keywords are selected in the market's language based on real queries from local users, since a literal translation often produces phrases nobody searches for.
- Terminology, units of measurement, date and address formats.
- Currency, prices, taxes and delivery terms for the country.
- Payment methods familiar to local customers.
- Legal pages: privacy policy, terms, returns, company details.
- Contacts: a local phone number or e-mail, business hours that take the time zone into account.
- Examples, case studies and reviews that the local audience can relate to.
Machine translation without editing often sounds unnatural and lowers trust. For pages that lead to an order, involve a native speaker or an editor. Keyword research for a new market is done from scratch in that market's language.
Step 5. Technical foundation and trust in a new market
Technical foundation
- Loading speed for visitors from the chosen countries; use a CDN if needed.
- A separate sitemap or clear sections for each language version.
- Titles, descriptions and structured data are translated and adapted.
- Correct canonical URLs: each language version points to itself.
Trust
A new market needs signals that you really work for it: local contacts, reviews from customers in that country, mentions in industry media and directories, partners, clear return terms. If you have a physical presence, set up a Google Business Profile for that address. Mass purchased links do not replace real mentions.
Step 6. Launch and measuring results
Launch plan for a new language version
- Research: demand, competitors, rules, readiness to serve customers.
- Decision: market, language, URL structure, people responsible for translation and support.
- Preparation: translation and localization of key pages – the home page, categories, service or product pages, contacts, terms.
- Technical setup: hreflang, sitemaps, redirects, language switcher, analytics.
- Testing: links, forms, payments and e-mails on the pages of the new version.
- Launch and monitoring: indexing, impressions and clicks by country, inquiries.
- Expansion: new pages and guides in the market's language, reviews and mentions.
Translating the entire site at once is optional. To begin with, the key pages that lead to an order are enough, and the rest is added based on the results of the first months.
Assign an owner to each language version: someone who knows the market, updates the texts, checks queries and answers inquiries. Without an owner, a version quickly becomes outdated and errors pile up. Agree on an update calendar: prices, promotions and legal pages change at different times for different countries.
Measurement
In Google Search Console, look at performance by country and page; in analytics, look at inquiries and orders by region. Compare the markets with each other: where impressions are growing, where clicks turn into inquiries, where support costs do not pay off. At first it is useful to test demand with ads: they quickly show whether there is interest before you invest in long-term work on the pages.
Common mistakes
- Machine translation of the whole site without editing.
- Launching many languages at once without resources for support.
- Hreflang errors: missing reciprocal links, the code ua instead of uk, links to pages with redirects.
- Forcing a language switch based on the IP address.
- The same currency, delivery and terms for all countries.
- Keywords translated literally without checking real queries.
- Missing local contacts and legal pages.
- One general analytics report without a breakdown by country.
Questions and answers
Do you need a separate domain for each country?
No, folders or subdomains on one site are often enough. Separate domains make sense for large markets with their own team and logistics, because they have to be promoted separately.
Can you simply translate the site automatically?
For an initial draft, yes, but commercial pages need editing by a native speaker. A poor translation lowers trust and can hurt search results.
Do you need to register a company in another country?
It depends on the legislation, the type of business and the sales volume. Tax and registration questions are settled together with a lawyer or an accountant, because the rules change.
How many languages should you choose at first?
One or two, where there is demand and you are ready to serve customers. Once the process is running smoothly, add others.
Will ads help in a new market?
Yes, as a quick demand test: they show which queries and pages bring inquiries. The results can be used when planning SEO for that market.
Conclusion
International SEO starts with a realistic choice of markets and languages and continues with a careful URL structure, correct hreflang tags and genuine content localization. Keep a pace you can sustain: two well-crafted versions are better than ten filled with machine translation. Measure each market separately and add new languages when demand is confirmed. This way you avoid unnecessary spending on pages nobody visits. Check the tags and redirects regularly after every site update. If you need help with a multilingual website or a check of the technical settings, LightSEO can help: see turnkey corporate website and website SEO audit.
Read also