International SEO checklist for 2026

An international SEO checklist covers choosing markets, picking a URL structure, adding hreflang with x-default, avoiding IP redirects, localising content and measuring by country. Google's docs changed in 2025 and 2026, so check that your hreflang lists every version, including itself, and that no page relies on geo meta tags.

Most checklists ranking for this term were written before those changes. Some still tell you to set a target country in Search Console, a report Google has deprecated; others never mention x-default. This one follows the order the work actually happens in, and quotes Google's own documentation at each step. Every source was checked on 24 Oct 2026 and is linked at the end.

The checklist at a glance

1. Choose markets and languages

Start with data, not a map. Look at which countries already send impressions in Search Console, where enquiries and orders come from, and which languages your sales and support teams can actually serve. A market you can't support after the sale isn't worth ranking in.

Separate country from language. Spanish for Spain and Spanish for Mexico may need different prices, shipping rules and vocabulary, while a single English version may serve several countries perfectly well. Write down, for each target, whether you need a language version, a country version or both. That list drives every later step.

For each market, do keyword research in the local language with native speakers. Direct translation of your English keywords misses how people really search, and it often lands on terms nobody uses.

2. Pick a URL structure: ccTLD, subdirectory or subdomain

Google's Managing multi-regional and multilingual sites guide (updated 10 Dec 2025) sets out the options with their trade-offs:

Google doesn't name a ranking winner. The right choice depends on legal entities, hosting, the teams who will run each version and how much separate investment each market can carry.

Subdomain vs subdirectory for SEO

This is the most argued-over line on any checklist. You'll read that subdomains "dilute" authority; Google's guide doesn't say that, and we couldn't find a primary source that does. What is true in practice: a subdirectory keeps every version on one domain, so internal links, redirects and monitoring are simpler, and one team can run it. A subdomain makes sense when a market needs separate hosting or a separate platform. Our default for most companies is a subdirectory unless a legal, hosting or organisational reason points elsewhere.

3. Add hreflang and x-default

Hreflang tells Google which URL is the right one for a given language or region. Google's Localized versions of your page guide (updated 21 Sep 2026) is the reference. The rules that trip up most sites:

• Three methods, all equivalent. HTML link tags in the head, HTTP Link headers (useful for PDFs) or an XML sitemap. Pick one per URL set and use it consistently.
• Self-reference. "Each language version must list itself as well as all other language versions." A page that lists only the others is incomplete.
• Return tags. If page A points to page B, page B must point back to A. One-way annotations may be ignored.
• Valid codes. Language in ISO 639-1 format (en, de, es), optionally followed by a region in ISO 3166-1 Alpha-2 format (en-GB, es-MX). A region code on its own isn't valid.
• x-default. Google describes x-default as the version used when no other language or region matches. Point it at a language-selector page or your main international version.
• Hreflang isn't language detection. Google says it doesn't use hreflang or the HTML lang attribute to detect a page's language; it reads the content. Hreflang only connects the versions.

Validate after every release. Hreflang breaks quietly: a new template drops the self-reference, a redirected URL stays in the annotations, or a staging domain leaks into production tags.

4. Don't redirect by IP or browser language

It's tempting to send visitors to "their" version automatically. Google's Locale-adaptive pages guide (updated 10 Dec 2025) explains why that's risky: Googlebot doesn't send an Accept-Language header, and its crawls mostly come from US-based IP addresses. If your server adapts content by IP or language, Google may only ever see the US English version. Google recommends separate locale URLs with hreflang instead.

The multi-regional guide is blunter: "Don't use IP analysis to adapt your content." Ahrefs' international SEO guide gives the same advice. A better pattern is a banner suggesting the local version, plus a language switcher on every page, so people and crawlers can reach every version by URL.

5. Localise, don't just translate

Google's localized-versions guide says translated pages are only treated as duplicates if the main content stays untranslated. Translating the menu and footer while leaving the body in English gives you near-duplicates that are unlikely to rank in the new market.

Localisation goes further than translation: currency, prices, units, date formats, shipping and returns, legal pages, examples, images and calls to action. Use native-language writers and a shared glossary for product terms. Machine translation is a useful first draft for some content; publish it unreviewed and it shows. Our content writing team works with native-language writers on the pages that sell in each market.

You don't need to translate the whole site on day one. Start with the pages that earn revenue in each market (category, product, pricing, contact) and expand from there.

6. Use canonicals carefully for same-language regional pages

When you run several versions in the same language, such as en-US, en-GB and en-AU, the pages can be nearly identical. Google's multi-regional guide says that if you provide similar content in the same language for different users, you should "pick a preferred version" and canonicalise to it, unless the versions genuinely differ. If prices, spelling, shipping and legal details differ, keep each version self-canonical and connect them with hreflang.

The common mistake is pointing every regional page's canonical at the US page while also listing them in hreflang. That sends mixed signals: hreflang says "these are alternates", the canonical says "only index this one".

7. Ignore what Google ignores

Two old habits still appear on checklists:

• Geo meta tags. The multi-regional guide says "Google ignores locational meta tags" such as geo.position or distribution. They do no harm, but they do no work.
• The International Targeting report. Search Console Help confirms that the International Targeting report has been deprecated; Google continues to use hreflang. Any guide telling you to "set a target country in Search Console" is out of date.

Also note Google's 11 Jun 2025 "spring cleaning" of its multilingual documentation, logged on the Search Central updates page: it removed the section on using robots.txt to block automatically translated pages. Google called it a docs-only change with no change in behaviour, so judge machine-translated pages on quality, not by blocking them.

8. Sitemaps, internal links and a language switcher

• Sitemaps. If you use the sitemap method for hreflang, each URL entry lists every alternate, including itself. Keep sitemaps per language or per section if the site is large.
• Internal links. Each version should link to its own-language pages, not back to English. Check navigation, breadcrumbs and related-content blocks after translation.
• Language switcher. Use plain links to the equivalent page in each language, not a script that only changes content in place. Label languages in their own language ("Deutsch", not "German").
• Redirects. When you move or retire a language version, update the hreflang set and the sitemap in the same release. For full domain or structure changes, follow a website migration checklist.

9. Measure by country

Set up reporting before launch so you can see the effect. In Search Console, filter Performance by country and by page path (for example /de/) to see clicks and impressions per market. In GA4, report by country and by language. A separate Search Console property per subdirectory or subdomain is optional, but it makes per-market reporting and permissions easier.

Watch for hreflang mismatches in the data: German users landing on English pages, or UK searches showing US prices. Those point straight at broken annotations or canonicals.

10. AI search in each market

AI answers in Google draw on the same indexed pages, so steps 1–9 are also your AI search work. On 15 Jun 2026 Google clarified its guidance on llms.txt files: they "won't negatively or positively impact your visibility or rankings" in Google Search, though keeping one for other services is fine. You don't need special files per market. What helps is clear, localised content that answers the questions people ask in each language. For the wider picture, read GEO vs SEO.

What changed in 2025–26?

All dates checked 24 Oct 2026. We'll refresh this checklist in January 2027.

A one-page checklist to copy

• Markets and languages chosen from your own data, with native-speaker keyword research.
• URL structure chosen on purpose; no URL-parameter locales.
• Hreflang on every version: self-reference, return tags, valid ISO codes, x-default.
• No automatic IP or browser-language redirects; a visible language switcher.
• Main content localised, not just navigation; local prices, units and legal pages.
• Same-language regional pages either genuinely different or canonicalised to one preferred version.
• No reliance on geo meta tags or the deprecated targeting report.
• Sitemaps and internal links updated per language; hreflang validated after each release.
• Country and language reporting in Search Console and GA4.

How Elgrith can help

Elgrith has delivered 1,000+ projects for 250+ clients since 2015, from our New Delhi HQ and client-partnership centres in New York, London and Shanghai. Our international SEO services cover market research, URL structure, hreflang and x-default fixes and localised content, and our technical SEO engineers ship the fixes in your codebase. For London teams who want an audit first, see our technical SEO agency in London. We don't sell link building: the work is technical SEO, localised content and reporting, and your Search Console, analytics and CMS stay in your name. See all our SEO services, book a call or start a project.

General guidance based on Google's public documentation, checked 24 Oct 2026.