international-seo.md
230 lines · skills/seo-audit/references/international-seo.md at 88c79f6
International SEO: Evidence & Sources
Detailed evidence backing the International SEO & Localization section of the SEO Audit skill. Organized by topic with source URLs and key quotes.
Raw lines 1 to 6
Hreflang
Raw lines 7 to 8Placement Methods
Google supports three equivalent methods: HTML <link> in <head>, HTTP Link headers, and XML sitemap <xhtml:link> elements. Google confirmed no method is prioritized over another.
Google combines signals from both HTML and sitemaps. If the same language-region pair points to different URLs across methods, Google drops that pair rather than guessing.
Raw lines 9 to 17Reciprocal Requirement
Google's docs: "If page X links to page Y, page Y must link back to page X. If not, those annotations may be ignored or not interpreted correctly."
Every page must include itself (self-referencing) in the hreflang set. Missing self-referencing is the #1 error found by Semrush audits. A study of 374,756 domains found 67% of hreflang implementations had issues.
- Google Search Central: Localized Versions
- Semrush: 9 Common Hreflang Errors
- SE Land: 31% of International Websites Contain Hreflang Errors
x-default
This is a recommended fallback for unmatched language/region users, not a mandatory condition for valid language annotations. Report its absence as a design recommendation when a fallback is useful, rather than declaring the whole hreflang implementation invalid.
Introduced April 2013. Designates the fallback page for users whose language/region matches no declared variant. Can point to the same URL as one of the language-specific alternates. If used, include it consistently in the complete annotation set on each variant page.
Raw lines 28 to 36Language & Region Codes
Language: ISO 639-1 (2-letter). Region: ISO 3166-1 Alpha 2 (2-letter). Format: language[-script][-region].
You cannot specify a region code alone. Common mistakes: en-UK (should be en-GB), es-419 (not ISO 3166-1). A study found 8.9% of sites using hreflang contain invalid language codes.
Hreflang at Scale (20+ locales)
With 20 locales, HTML <head> hreflang adds ~1.5KB per page for zero user benefit. Sitemap-based hreflang has zero runtime performance impact. <xhtml:link> child elements do NOT count toward the 50,000 URL sitemap limit (only <loc> elements count).
John Mueller recommends focusing hreflang on pages receiving wrong-language traffic, not every page: "I wouldn't do it for any of the other pages of the site because it's so complex & hard to manage."
- SERoundtable: Child Elements Don't Count
- SERoundtable: Where To Focus Hreflang
- Yoast: hreflang Ultimate Guide
Google vs Bing
Bing treats hreflang as a "weak signal." Bing relies on content-language meta tag, HTML lang attribute, ccTLDs, and server location. Yandex supports hreflang like Google.
For both engines: implement hreflang (Google/Yandex) + <html lang="..."> + <meta http-equiv="content-language"> (Bing).
Raw lines 56 to 66
Canonicalization & i18n
Raw lines 67 to 68Choose Canonicals by Content and Language
Use self-referencing canonicals for distinct locale pages, including genuinely translated content. Do not consolidate different-language translations merely because they describe the same product.
For similar or duplicate regional pages in the same language, Google recommends choosing a preferred canonical and using consistent hreflang annotations. For example, equivalent German content at example.de/ and example.com/de/ can share a preferred canonical; every regional URL is not required to canonicalize to itself.
Align Canonical and Hreflang Signals
Keep canonical targets and hreflang clusters consistent with the chosen content/language strategy. hreflang identifies localized alternatives; it does not force Google to index each URL independently. Canonicals are signals to Google's selection process, not an indexing guarantee.
The preferred canonical must be a URL inside the hreflang cluster. Google ignores hreflang on a URL that is canonicalized to another one.
Near-Duplicate Regional Variants
Mueller (2023 Office Hours): "If the content is completely the same, and we can't tell any difference, then for simplicity and user experience we may just show one version -- even if hreflang is present."
Google may consolidate identical or near-duplicate regional content despite hreflang. Use the same-language preferred-canonical strategy above where appropriate; do not promise that either self-canonicals or cosmetic differences will keep every regional URL indexed.
Pagination Across Locales
Google: "Don't use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL." Each paginated page in each locale gets self-referencing canonical. rel="next/prev" deprecated March 2019.
Raw lines 95 to 102
International Sitemaps
Raw lines 103 to 104Structure
Each <url> entry includes <xhtml:link> alternates for every locale. Requires xmlns:xhtml="http://www.w3.org/1999/xhtml" namespace.
Split sitemaps by content type, not by locale. Splitting by locale creates maintenance problems because every locale sitemap must reference every other locale (reciprocal requirement).
Raw lines 105 to 113Size Limits
50,000 URLs / 50MB uncompressed per sitemap. Only <loc> elements count toward the 50K limit. But with 20 hreflang alternates per entry, the 50MB file size limit becomes the bottleneck. Plan for 2,000-5,000 URLs per sitemap when using full hreflang.
Submission
Submit the sitemap index in Search Console AND reference it in robots.txt. Individual child sitemaps can be submitted separately for per-sitemap reporting.
Raw lines 121 to 126Next.js Caveat
Next.js alternates.languages does NOT automatically include a self-referencing <xhtml:link> for the <loc> URL. You must explicitly include the <loc> URL's own language in the languages object.
Raw lines 127 to 134
URL Structure
Raw lines 135 to 136Strategies Compared
Google treats subdirectories and subdomains equivalently. Mueller: "From our point of view...they say subdomains and subdirectories are essentially equivalent."
URL parameters (?lang=en) are explicitly "Not recommended" per Google docs.
Default Language
Mueller recommends: set / as x-default, put each language in its own prefix. Without marking / as x-default, "to Google it can look like '/' is a separate page from the others."
Content Negotiation / IP Redirects
Google strongly advises against locale-adaptive pages. Googlebot crawls from US IPs and does not send Accept-Language headers. Separate URLs + hreflang are required.
Raw lines 152 to 157Trailing Slash Consistency
Mueller: trailing slash is "a significant part of the URL and will change the URL if it's there or not." Pick one format for all locale paths, internal links, canonicals, hreflang, and sitemaps.
Mueller (2025): "Consistency is the biggest technical SEO factor."
Raw lines 158 to 165Search Console Geotargeting
The International Targeting report is deprecated. Google now relies entirely on hreflang, content language analysis, and linking patterns. You can add subdirectory properties for per-locale reporting.
Raw lines 166 to 171Framework Locale Modes
Use localePrefix: 'always' (next-intl) or equivalent. Never hide locale from URLs -- Google needs unique URLs per language. Using 'never' mode disables alternate links entirely.
Raw lines 172 to 180
Content Quality Across Locales
Raw lines 181 to 182Auto-Translated Content (2025 Stance)
Google removed longstanding guidance advising against auto-translated content in mid-2025. Current stance: "Our policies do not strictly define content that has been translated by AI as spam." The scaled content abuse policy mentions translation as a possible vector, but does not ban it.
Reddit scaled AI translations to 35+ languages with Google's knowledge. The key distinction is intent and quality, not the method.
Raw lines 183 to 192Thin Locale Pages
Google: "Localized versions of a page are only considered duplicates if the main content of the page remains untranslated." Pages with only translated boilerplate get clustered as duplicates.
Do NOT use noindex for unwanted locale pages (wastes crawl budget). Do not canonicalize distinct translations to another language merely to hide thin content. Best approach: don't create locale pages you can't make genuinely helpful.
Raw lines 193 to 201Helpful Content System Impact
Merged into core ranking March 2024. Site-wide signal: "any content -- not just unhelpful content -- on sites determined to have relatively high amounts of unhelpful content overall is less likely to perform well in Search."
Low-quality translated pages can drag down the entire site. This is the strongest argument against creating locale pages that aren't genuinely helpful.
Raw lines 202 to 210Partial Translation
Google: "Translating only the boilerplate text of your pages while keeping the bulk of your content in a single language...can create a bad user experience." Google uses visible content (not lang attribute) to determine page language.
Translate ALL content on a page if you create a locale version. Untranslated metadata (title, description) in the wrong language reduces CTR.
Raw lines 211 to 218Crawl Budget
Only a concern for 1M+ pages or 10K+ pages changing daily. But alternate URLs (hreflang targets) do consume crawl budget. Broken hreflang links waste budget AND invalidate signals.
Raw lines 219 to 225Locale-Specific Signals
Google identifies audience via: "local addresses and phone numbers on the pages, the use of local language and currency, links from other local sites, or signals from your Business Profile."
Raw lines 226 to 230