Configure international multi-region site architecture by choosing between ccTLD, subdomain, and subfolder approaches
domain: google-search-console · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Map your geotargeting requirements: ccTLDs (e.g., example.de) provide the strongest geo-signal but require separate Search Console properties and separate link-building; subdomains (de.example.com) allow separate property targeting with shared root domain equity; subfolders (example.com/de/) share all domain authority but require a single server infrastructure
Register the chosen URL structure and set up separate Search Console properties for each regional variant; for subdomains and subfolders, configure geotargeting in the International Targeting report
Implement hreflang annotations across all regional variants so Google understands the language-region mapping and surfaces the correct variant to each user
Ensure each regional variant has distinct, locally relevant content rather than machine-translated copies of the same page, which Google may treat as duplicate content
Monitor the International Targeting report in Search Console for hreflang errors and verify that each regional variant is being indexed under the correct property
Known gotchas
ccTLDs cannot have geotargeting overridden in Search Console because the country association is inherent to the domain extension; this makes ccTLDs the strongest geo-signal but also the least flexible if you decide to restructure
Subdomain geotargeting must be explicitly set in Search Console's International Targeting report; Google does not automatically infer geotargeting from subdomain naming conventions alone
Serving identical content across regional variants without differentiation, even with correct hreflang, may result in Google consolidating the variants into a single canonical across regions, defeating the purpose of the multi-region structure
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?