Decide between ccTLD and subdirectory structure for a new market launch and configure the geotargeting signals now that Search Console's country-target setting is gone

domain: developers.google.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Weigh ccTLD (strongest but costliest per-market geotargeting, one domain's authority does not transfer to others) against subdirectories/subdomains (shared authority, faster to launch, weaker inherent geo-signal)
  2. For subdirectory/subdomain setups, rely on hreflang annotations, content language, and server location/CDN choice as geotargeting signals, since Search Console's manual 'target country' setting was removed in September 2022
  3. Register each ccTLD as its own verified Search Console property, since ccTLDs are treated as fully separate properties with no shared settings
  4. Check hreflang health via the Enhancements/International section of Search Console (where hreflang errors now surface) rather than looking for a dedicated International Targeting report, which no longer exists
  5. Use consistent, market-appropriate currency, address formats, and local business signals on each market variant regardless of URL structure, since Google increasingly infers geo-relevance from on-page content, not just URL structure
  6. Document the choice per market, since mixing structures (some markets on ccTLD, others on subdirectory) is common and requires per-market Search Console properties either way

Known gotchas

Related routes

Configure international multi-region site architecture by choosing between ccTLD, subdomain, and subfolder approaches
google-search-console · 5 steps · unrated
Choose between ccTLD, subdomain, and subfolder site structures for international and multi-region SEO
developers.google.com · 5 steps · unrated
Validate hreflang health now that Search Console's International Targeting report no longer exists
international-seo · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans