A brand is ready for international SEO when it already has customers in a second market and is losing some of them to a competitor who speaks their language. The work is less about translation than about structure: one URL per language and market, every version pointing at every other version, and the small details (prices, units, phone formats, directories) matching what a buyer in that country expects.
This post covers the decisions in the order you will meet them, from whether to start at all to how to measure each market on its own. Where we quote a rule, it comes from Google's own documentation, because that is where most of the costly mistakes are already written down.
When a business is ready to go multi-language
You are ready when a second language or country already accounts for real demand that you can see in your own data, and you have someone who can answer a customer in that language. Before those two things are true, a translated site is a cost without a return.
Look at three sources. Your analytics will show sessions by country and by browser language; if 15 percent of your visitors have a German-language browser and your site is only in English, you already have a German audience you are serving badly. Your inbox and your order history will show where inquiries come from. Your Search Console data will show queries you rank for in countries you never targeted.
Then check the operational side. Can you ship, deliver, or serve there? Can you invoice in the local currency and handle local tax? Can you answer a support email in the language? If the answer to any of these is no, fix that first. A page that wins a Spanish-speaking customer and then hands them an English-only checkout has spent money to create a bad review.
One more test: is the demand in a language or in a country? Spanish for Spain and Spanish for Mexico are different markets with different prices and vocabulary; English for the UK and for Australia is one language in two markets. Decide which you are targeting, because the structure depends on it.
ccTLD, subfolder or subdomain
For most growing brands the right answer is a subfolder on one domain (example.com/de/, example.com/fr-ca/), because it is the cheapest to run, keeps all authority on one site, and is the easiest to measure. Country-code domains and subdomains have real uses, but they are the exception.
Google's guide to multi-regional sites sets out the trade-offs plainly (Google Search Central).
Country-code top-level domain (example.de). Google describes this as the clearest geotargeting signal: the domain itself says which country the site is for. The costs are that each domain is a separate site to build, host, secure, and earn links for; that some ccTLDs have residency requirements; and that a ccTLD targets exactly one country, so example.de cannot also serve Austria or Switzerland.
Subdomain (de.example.com). Easy to set up and can sit on a different server, but Google notes that a user cannot tell from the URL whether "de" means the German language or the country of Germany, and in practice search engines treat subdomains as partly separate sites, so authority is split.
Subfolder (example.com/de/). Easy to set up, one host, one set of links, one Search Console property that can be filtered. The drawbacks Google lists are that the geotargeting is less obvious to a user and that separating the sites later is harder. For a brand going from one country to three, those drawbacks are small.
URL parameters (example.com?lang=de). Google explicitly does not recommend this, and nor do we.
Whatever you choose, keep one language per URL. Google's documentation says it determines language from the visible content, not from the lang attribute or the URL, and advises against side-by-side translations on one page.
hreflang: the rules that actually matter
hreflang is an annotation that tells a search engine "this page has equivalents in these other languages and regions, and here they are." It does not rank your pages; it stops Google showing your German page to a French searcher, and it stops your three English versions competing with each other. Get it right and the correct version appears in each market. Get it wrong and Google ignores it silently.
The full specification is on Google Search Central (Tell Google about localized versions of your page). These are the parts that cost businesses markets when they are missed.
Every version must point at every other version, including itself
The annotations must be reciprocal. Google's documentation is explicit: "If two pages don't both point to each other, the tags will be ignored." This is the single most common failure we find in audits. A German page that lists its English and French equivalents, while the English page lists only the French one, is a German page whose annotations are discarded. Each page also lists itself, which feels redundant and is required.
Use the right codes
The language part is an ISO 639-1 code (en, de, ja); the optional region part is an ISO 3166-1 alpha-2 code (GB, DE, JP). A region on its own is invalid; "uk" is not the United Kingdom (that is "gb"), and Google ignores reserved codes such as "eu". Script variants use ISO 15924, for example zh-Hant for traditional Chinese and zh-Hans for simplified.
Add x-default
x-default marks the page to show when none of your language versions match the searcher. For most sites it is the language-selector page or the global English homepage. Without it, a searcher in a country you do not target is handed whichever version Google guesses, and the guess is often wrong.
Choose one method: head tags, HTTP headers, or sitemap
Google accepts three ways to declare the annotations, treats them as equivalent, and says there is no benefit in using more than one. Head tags (<link rel="alternate" hreflang="de" href="...">) are easiest to see and easiest to break when a template changes. The XML sitemap method keeps everything in one file that can be generated from your content database, which is why we prefer it for sites with more than a few dozen pages per language: the reciprocity is guaranteed by construction. HTTP headers are for non-HTML files such as PDFs.
Pick one.
Do not redirect by IP or browser language
Google advises against automatically redirecting visitors to a language version based on their assumed location, because it blocks both users and crawlers from reaching all versions. Googlebot usually crawls from the United States, so a site that redirects every US visitor to the English version has hidden its German pages from Google. Offer a visible language switcher with real links instead.
Translation quality, machine translation and the local details
Machine translation is good enough to draft and not good enough to publish, and the gap is widest exactly where it matters most: service pages, pricing, legal text, and anything a customer will quote back to you. Use it to produce a first pass, then have a native speaker who knows your industry rewrite it.
The reason is not only quality. Google's spam policies name "automated transformations like synonymizing, translating, or other obfuscation techniques" as a form of scaled content abuse when they are used to generate many pages that add little value (Google Search Central). A site that machine-translates 400 pages into six languages and publishes them untouched is exactly the pattern that policy describes.
What a native reviewer changes is rarely grammar. It is the things a translation engine cannot know: that your "emergency call-out" is a "Notdienst" in Germany but a "dépannage d'urgence" in France; that a British reader expects "VAT included" and a US reader expects tax to be added at checkout; that a Japanese service page that opens with a hard price reads as blunt where an English one reads as clear. Keyword research also has to be redone per language, because the term a customer actually types is often not the translation of the English term.
A practical rule for budget: translate the pages that earn money first (service pages, pricing, the contact flow, the top ten articles by traffic) and leave the long tail in the source language with a clear note. A half-translated site with the right half translated well beats a fully translated site translated badly.
Localizing the details
A translated page that still shows US dollars, Fahrenheit, and a phone number without a country code tells the reader the brand is not really here. Localization is the set of small corrections that make the page feel native, and most of them are mechanical.
- Prices and currency. Show the local currency with the local symbol placement and separator: €1.299,00 in Germany, €1,299.00 in Ireland, ¥129,900 in Japan. State whether tax is included, because the convention differs by country.
- Units. Metric almost everywhere; imperial in the United States; a mix in the UK, where distances are in miles and most materials are metric.
- Dates and times. 31/10/2026 in most of Europe, 10/31/2026 in the US, 2026-10-31 in much of Asia and in anything technical. Spell the month out where there is any room for confusion.
- Phone numbers and addresses. Use the international format with the country code (+44 20 7946 0000) and the local format on the same page, and make the number tappable. Address fields differ: postal codes come before the city in Germany and after it in the UK; Japan runs the address from largest unit to smallest.
- Names, forms, and payment. A form that requires a "state" blocks most of the world. Offer the payment methods the market actually uses: iDEAL in the Netherlands, SEPA transfers in Germany, PayNow in Singapore, cards almost everywhere.
None of this is difficult. It is a list that has to be worked through for every market, and it is where a first international page most often fails.
Local engines, directories and profiles per country
Google is not the only engine that matters, and in some markets it is not the main one. The work for each market includes the engine and the directories a buyer there actually uses.
Bing matters everywhere because it feeds Microsoft Copilot, DuckDuckGo, and a set of AI products. Verify the site in Bing Webmaster Tools and submit the sitemap; the international annotations carry across.
Yandex is the main engine for Russian-language search. It has its own webmaster tools, its own structured-data preferences, and a strong preference for ccTLDs and local hosting.
Naver dominates in South Korea, and it is closer to a portal than a search engine: results are built from Naver's own properties (blogs, cafés, Knowledge iN, shopping) before the open web. A Korean strategy that ignores Naver's ecosystem is not a Korean strategy.
Baidu is the main engine in mainland China and effectively requires a site hosted in China with an ICP license, simplified Chinese content, and attention to Baidu's own webmaster platform. Google is not a route into that market.
Regional directories carry the same weight for citations that US directories carry at home. Our HyperCare+ explainer covers why citation consistency matters; the set of directories to keep consistent is different in every country, and a list built for one market is useless in another.
Google Business Profile per country
Each physical location needs its own Google Business Profile in the country where it stands, with the address, phone number, and hours in the local format, and with the primary language set to the language customers there use. A single profile cannot represent locations in two countries.
Some things differ by market and catch brands out. Categories are translated and not always one-to-one, so the category you use at home may not exist in the same form abroad. Verification methods vary by country; video verification is common in markets where postcard verification was abused. Review norms differ: review volume per customer is typically higher in the US than in Japan or Germany, so a German location with 30 reviews may be doing well where a US location with 30 would be behind.
Service-area businesses without a storefront can usually list in markets where Google supports service areas, but the rules are stricter in some countries than others. Check the country's own Business Profile help pages rather than assuming the US rules apply, and reply to reviews in the language of the review.
A brand that reaches multi-location across borders is on our Global tier for exactly this reason: the profile work is per country, and the rules are per country.
Schema for international pages
Structured data on international pages has two jobs: say what language the page is in, and say where the business operates. Both are handled with standard schema.org properties, and both are easy to get wrong in a way that quietly contradicts the hreflang.
inLanguage (schema.org/inLanguage) takes an IETF BCP 47 language tag ("de", "fr-CA", "pt-BR") and belongs on the WebPage, Article, or other CreativeWork item for that page. It should match the hreflang for the page. If the hreflang says de-AT and the schema says de-DE, you have told two parts of the same engine two different things.
areaServed (schema.org/areaServed) belongs on the Organization, LocalBusiness, Service, or Offer and states the geographic area the business serves. For a national brand it can be a country ("DE"); for a service business, a set of cities or an administrative area; for a global brand, several countries listed separately. This is the property an assistant reads when it wants to know whether you serve the place the user is asking about.
Keep the rest consistent as well. Each localized LocalBusiness should have its own address in the local format, its own telephone with the country code, its own priceRange in the local currency, and openingHoursSpecification in local time. The organization-level schema stays the same across languages, because it is the same organization; the location-level schema is local. Structured data should always match the visible text on the page, and Google's documentation on AI features repeats that point for AI Overviews (Google Search Central).
Measuring each market on its own
Measure every market as if it were a separate business, because it is. A combined traffic chart hides a market that is failing behind one that is growing, and that is the market where the money was spent.
Set up the measurement before the pages go live.
- Search Console. With a subfolder structure you can filter by page path and by country. With ccTLDs each domain is its own property. Either way, look at impressions, clicks, and average position per market and per language, not for the site.
- Analytics. Segment by country and by browser language, and track conversions per segment. A market with growing sessions and no inquiries has a localization problem, not a traffic problem.
- Rank and assistant tracking. Track your core queries per market, in the local language, from a local location. For AI assistants, ask the questions in the market's language; the answers differ by language even when the question is the same.
- Indexing. Count indexed pages per language and compare with the number published. A language with 200 pages published and 40 indexed usually has a broken hreflang, a mistaken canonical pointing to the source language, or thin translation that Google has chosen not to index.
- Profiles and reviews. Review count, average, and reply rate per location, read against the norms of that country.
We report each market separately for Global clients for this reason.
The mistakes that cost you a market
Most lost markets are lost to one of six mistakes. Each is invisible from inside the business until someone looks at the market's own numbers.
- One-way hreflang. The annotations are ignored, and the wrong version shows in each country. Fix: generate the annotations from one source of truth, such as the sitemap, so reciprocity cannot be missed.
- Canonical tags pointing to the source language. A French page whose canonical URL is the English page is a page that has asked not to be indexed.
- Automatic redirection by IP. Users cannot reach the version they want, and Google cannot reach the versions it needs.
- Raw machine translation. The pages read as foreign, convert poorly, and risk being treated as scaled content.
- Home-market defaults left in place. Dollars, miles, US date formats, a state field in the form, a US-only phone number.
- No one to answer. The market generates inquiries in a language nobody on the team reads, and the leads go cold. This is the most expensive mistake and the least technical; the follow-up gap is wider across a language barrier.
A worked example
Consider an invented outdoor-equipment brand in Vancouver that sells across Canada and has noticed that a fifth of its orders ship to Quebec, where customers browse in French, and that it is getting inquiries from the UK it cannot fulfil yet.
The sensible plan is one domain with three subfolders: /en-ca/, /fr-ca/, and later /en-gb/. The French-Canadian pages are translated by a Quebec-based writer, starting with the 30 product and category pages that earn most of the revenue, with prices in Canadian dollars shown with the French separator and the tax note Quebec customers expect. hreflang is generated in the sitemap from the product database, with x-default pointing to a short language-selector page. The schema carries inLanguage: "fr-CA" on each French page and areaServed: "CA" on the organization. A Bing Webmaster Tools property is added. Search Console is filtered by path and country, and conversions are tracked per language.
The UK is deferred until the brand can ship there at an acceptable cost and quote prices in pounds with VAT included; when it does, /en-gb/ gets its own pricing, phone number, and directories, and the English copy is adapted rather than copied.
What to do next
If you are considering a second language or market, the steps below put the structure in place before the translation budget is spent.
- Confirm the demand in your own data: analytics by country and browser language, inquiries by origin, Search Console queries by country.
- Decide language versus country for each target, and choose the URL structure. Default to subfolders unless you have a specific reason not to.
- Generate hreflang from one source of truth, include x-default, and verify reciprocity with a crawler before launch.
- Translate the money pages with a native speaker in your industry; localize prices, units, dates, phone numbers, forms, and payment methods.
- Claim the engines and directories for the market: Bing at minimum, and Yandex, Naver, or Baidu where the market requires it.
- Set up measurement per market before the pages go live.
If you want to know where you stand first, book a call and we will walk through your site, listings and search with you. If the site itself is not ready for a second market, that is a build rather than a retainer, and it starts with a mission.
Si esto describe tu negocio, una llamada te mostrará qué parte te está costando más.
