International SEO: URL Structure, hreflang, Localisation and AI Visibility, Country by Country

Rolling out a website across several countries is not about simply translating a few pages. International SEO means choosing a URL structure, serving each audience the version intended for it, localising rather than translating, and staying consistent for the generative engines that answer in the language of the query. Here are the choices to make, the errors that cancel out the work, and the checks to run country by country.

What Is International SEO: Multilingual or Multi-Country?

International SEO comprises the practices that help a site appear in search results across several languages or countries, with a version adapted to each market.

First, distinguish two approaches. A multilingual site targets languages: fr, en, de. A multi-country site targets geographical areas, sometimes with a shared language: fr-FR and fr-BE, en-US and en-GB. One language can serve several countries, and one country can require several languages, as in Belgium or Switzerland.

Search intent varies even when the language is identical, because regulations, offers and competition change from one country to the next. Each version therefore has its own indexable URLs. Two failures recur in audits: the wrong version being served to users, such as an English page ranking ahead of the local version, and signal dilution across versions that are too similar.

Before Translating: Choose Your Markets

Opening a version costs production, review and maintenance time. Prioritising prevents you from spreading these resources over markets that will bring nothing back. Assess each candidate country using a simple grid:

• Demand: volumes and intents measured in the target language and country, never inferred from your home market.
• Competition: local players, quality of results, dominant formats (comparison sites, videos, product pages).
• Feasibility: ability to localise the offer (pricing, currency, delivery, legal notices) and to bring in native reviewers.
• Risk: technical complexity of the CMS, existing debt, recent migration.

Start with one or two markets where demand is measured and the offer is available, stabilise the method, then expand. Never open a version "per language" without measured traction.

Check That Each Market Is Serviceable

International strategies sometimes fail for reasons unrelated to SEO. Before investing in architecture and content, check four points:

• Offer: actual availability by country, range, pricing, taxes and commercial terms.
• Support: ability to respond in the language, on channels and at hours aligned with the country.
• Logistics: shipping, returns, lead times and excluded areas, which directly affect conversion.
• Compliance: legal notices, cookie policy, warranties and sector constraints specific to the country.

These prerequisites also set the level of localisation: if the offer differs from one country to another, pages need to diverge more (proof, calls to action, reassurance).

URL Structures: ccTLD, Subdomain or Subdirectory

Your URL structure is a long-term decision: it determines how authority is shared between versions, the maintenance cost and the readability of reports. Three options are standard, and a fourth should be avoided. The table compares them.

The subdirectory remains the default choice. A ccTLD is justified when local trust comes first and each country has its own team; the price is paid in maintenance and in authority to rebuild.

Country Targeting: ccTLD or hreflang, Nothing Else

At the time of writing, country targeting relies on only two signals. The first is the ccTLD, which Google associates with its country; domains such as .io or .co are treated as generic and target no country. The second is hreflang. The International Targeting report in Search Console was removed in 2022: a subdomain or subdirectory can no longer be assigned to a country in the interface.

Whatever the structure, map your page types, decide which ones exist in each version and replicate the same hierarchy per market: hreflang, sitemaps and reports all become simpler.

Hreflang in Brief: What It Does, What It Does Not Do

The hreflang tag tells Google about the equivalent language or regional versions of a page. It serves the right version to the right user and prevents similar versions from competing, but it is not a ranking factor. Google only applies it between genuinely equivalent pages, and Bing relies instead on content-language, the <html lang> attribute and URL signals.

Syntax, Return Tags and Self-Referencing

Each version declares, in its <head>, every version in the group, including itself. Codes combine a language in ISO 639-1, in lower case, and where needed a country in ISO 3166-1 alpha-2, in upper case. For an offer available in France, Belgium and the United Kingdom, with a country selection page, the block looks like this:

• <link rel="alternate" hreflang="fr-FR" href="https://www.example.com/fr-fr/offer/" />
• <link rel="alternate" hreflang="fr-BE" href="https://www.example.com/fr-be/offer/" />
• <link rel="alternate" hreflang="en-GB" href="https://www.example.com/en-gb/offer/" />
• <link rel="alternate" hreflang="x-default" href="https://www.example.com/choose-country/" />

The same block appears on all three versions: these are the return tags, and listing the page itself makes it self-referencing. URLs are absolute, canonical and indexable. x-default designates the selection page or the default version. The HTTP Link: header (for PDFs) and the XML sitemap are the two other methods.

Three Errors That Cancel Out the Tags

Most faulty implementations involve one of these three errors:

• Missing return tags: page A references B, but B does not reference A, and Google ignores the pair.
• Invalid code: es-LATAM, es-EU or en-UK; Latin America is written es-419, the United Kingdom GB, and uk means Ukrainian.
• Non-indexable target: hreflang pointing to a URL that redirects, is noindexed or is canonicalised to another version.

Methods, valid codes and fixes are covered in our guide to implementing and checking hreflang tags.

Keywords by Country: Do Not Translate a List

Translating a keyword list produces content that is correct in form but off-target in intent: the translated term is not necessarily the one people in that country type. Use a three-step approach:

• Start from intent: informational, commercial, transactional or navigational, as it is expressed in the country.
• Validate local vocabulary: variants, false friends, units, industry terms specific to the market.
• Study the local results page: dominant formats, competitors' angles, recurring questions.

One Intent, One Page, One Version

The mapping of an intent to a page must be explicit in each version. Without it, three problems appear: two pages within the same version competing, an en-US version ranking for British queries, or a transactional intent with no dedicated page. To prioritise, cross business potential, local difficulty, seasonality and delivery capacity.

Translation or Localisation: What to Adapt

A clean translation is enough for navigational queries. As soon as the page targets generic, competitive queries, you need to localise, that is, adapt the substance to the country's habits. The table distinguishes the two.

The rule follows intent: reviewed translation for navigational queries, localisation for informational ones, strong localisation for transactional ones.

Same-Language Countries: Differentiate or Merge

Hreflang distinguishes two countries that share a language, but it only helps if the pages genuinely differ. Without a useful difference, one version is better than two near-copies. The table covers the common cases.

Duplicate content between versions is managed through clear signals and real differentiation, never through a canonical from one version to another.

One Language, Several Markets: The Spanish Example

Vocabulary changes between Spain and Latin America (ordenador or computadora, móvil or celular), so does register, and keywords differ from one country to another. When the offer is identical across Latin America, a shared es-419 version complements an es-ES version for Spain. Variants and codes are covered in our guide to Spanish SEO.

Multi-Country Technical SEO: Indexing, Redirects, Canonicals

International sites rarely fail because of content alone. Six technical rules cover the essentials:

• Sitemaps: one sitemap per version, or an index grouping them, without creating isolated islands that internal linking does not connect.
• No automatic IP-based redirect to another language: show a banner suggesting the local version and let users choose.
• No geo-blocking of Googlebot: it crawls mainly from the United States and must be able to reach every version.
• Canonicals per version: each page declares its own URL as canonical.
• Performance: a CDN and latency monitoring by region, so that no market is penalised by infrastructure.
• Structural duplicates: http and https, www and non-www, parameters multiply across versions; fix them once and for all.

Canonical and hreflang: Two Signals to Align

The canonical designates the primary version of the same content; hreflang links equivalent versions intended for different audiences. Canonicalising the Belgian version to the French one means only the French version gets indexed, which cancels out hreflang. Keep canonicals for duplicates within a version (parameters, facets) and use URL Inspection to check that Google keeps the declared canonical. The language selector, for its part, leads to the equivalent page, not to the homepage.

Local Authority: Links and Mentions From the Country

Links from French media carry less weight on a foreign results page: their context is less aligned with the target market. Each version needs links and mentions from sites in the country: media, partners, professional organisations. Keep natural anchors in the version's language, target the pages that carry value and avoid artificial networks, which are quickly spotted when patterns repeat from one country to another. The method is set out in our netlinking guide.

International GEO: Being Cited in the Right Language

Generative engines (ChatGPT, Perplexity, Gemini, AI Overviews and AI Mode, available in France since summer 2026) answer in the language of the query and cite sources written in that language. A brand without a Spanish version therefore has little chance of being cited in an answer in Spanish, even if its French version is authoritative. A version per language becomes a condition of eligibility, beyond traffic.

This concerns your markets abroad as much as France: AI Overviews are rolled out in 200 countries (Sebastien Vallat, 2026). AI visibility is therefore handled market by market.

These answers are no longer a marginal format: AI Overviews appear on >50% of Google searches (Squid Impact, 2025). Benchmarks are gathered in our GEO statistics. For a version to be eligible in its language, apply four rules:

• One version per language, indexable and linked by hreflang, rather than a translation generated on the fly in the browser.
• Consistent entities: same organisation name, same facts, same figures from one version to another.
• Structured data with the inLanguage property filled in for each version.
• AI crawlers not blocked: check that your robots.txt file does not close any version to their user agents.

Structuring Citable Content by Market

Standardise extractable blocks in each version: short definitions, steps, tables, sourced data. The structure stays identical from one language to another; the proof and vocabulary change. The general principles are covered in our guide to Generative Engine Optimization.

Measuring AI Visibility by Country

Track brand presence on a set of questions per language, the pages cited and the change after each update. Answers vary by model and period: read trends, and treat any increase as a correlation, never as causation.

Managing by Market: Indicators and Governance

Each version is managed as a market in its own right: the same indicators, read country by country, linked to conversions. The table matches each indicator with its source.

Create one Search Console property per version (URL prefix by subdirectory or subdomain) and attribute each conversion to its version in Google Analytics 4. How these reports work is explained in our guide to Google Search Console.

Governance: Who Produces, Who Approves, Who Updates

Without clear ownership, gaps appear quickly: unreviewed translations, hreflang tags forgotten on a new template. Three models coexist:

• Centralised: a global team drives priorities, templates and production, which ensures consistency and speed, at the risk of losing local nuance without native reviewers.
• Decentralised: each country manages its own content, which allows close market fit, at the risk of fragmenting quality and duplicating effort.
• Hybrid: the central team standardises architecture, templates, indicators and quality control, while local teams adapt vocabulary, proof and offers.

The hybrid model proves the most robust. In every case, formalise the production chain, from writing to native review, and an update rule by criticality.

Depending on Your Situation

Depending on your context, these resources take the approach further:

• You sell online in several countries: our guide to e-commerce SEO covers categories, product pages and facets.
• You target specific cities or areas within each country: see our guide to local SEO.
• You are starting from an existing site that needs consolidating: begin with an SEO audit carried out version by version.

To check hreflang tags, canonicals, the indexing of each version and the brand's presence in AI answers country by country, the Incremys 360 GEO & SEO audit module brings these checks together in a single audit.

International SEO FAQ

Should you use a ccTLD or a subdirectory to open a new country?

A subdirectory works in most cases: it shares the main domain's authority, is managed in a single CMS and costs little to maintain. A ccTLD gives a strong country signal and builds local trust, but it means rebuilding authority and maintaining one site per country. Reserve it for markets with a dedicated team and budget.

Do you need to translate the whole site for each country?

No. Translate first the pages that carry the market's demand and offer: homepage, offers, categories, legal pages and content answering local queries. Pages with no equivalent or no demand in the country can wait. Hreflang only links existing pages: a partial version remains valid as long as each declared page has its equivalent.

How do you target a country without a ccTLD?

With hreflang. Since Search Console's International Targeting report was removed in 2022, a subdirectory or subdomain can only be tied to a country through hreflang annotations combining language and country, such as fr-BE. Add real localisation (currency, delivery, legal notices) and local links to strengthen the version's consistency.

Can you keep the same content for the United States and the United Kingdom?

Yes for the baseline, provided you add meaningful differences: spelling, vocabulary, units, currency, delivery and legal notices. Without these differences, two near-identical versions compete with each other and bring nothing to users. If the offer is the same and sold at the same price, a single English version may be enough.

Should you automatically redirect visitors based on their country?

No. An IP-based redirect prevents users from choosing their version and can block crawling, since Googlebot crawls mainly from the United States. Instead, show a banner offering the local version, let users decide and remember their choice. Every version must remain accessible from any country.

Is an English version enough to be cited by AI engines abroad?

Rarely. Generative engines answer in the language of the query and preferably cite sources written in that language. An English version covers queries in English, not those asked in German or Spanish. For each priority market, a version in the local language, with consistent entities, remains the condition for being cited.

How long does it take to measure the effects of a new version?

Allow several months. A new version must first be crawled, indexed and correctly associated through hreflang before it gains rankings. Annotate the launch date, track indexing per version and then impressions filtered by country, and compare trends rather than weekly variations, which remain too noisy to base decisions on.