Before you start
- Clear URL per language or country version
- Stable HTTPS canonicals
Pick a URL strategy: subfolders, subdomains, or ccTLDs
Subfolders (/en/, /de/) are common on WordPress; ccTLDs (.de) signal geography strongly but cost more to operate.
Document the strategy before hreflang — changing paths later needs redirects.
Official: https://developers.google.com/search/docs/specialty/international/localized-versions
Implement hreflang with reciprocal links
Each language URL must reference all alternates including itself; every alternate must reference back.
Use correct ISO language/region codes (en-GB vs en-US). Add x-default for a fallback when users do not match a locale.
Align canonicals with hreflang targets
hreflang should point to indexable canonical URLs, not parameter variants or staging hosts.
Avoid noindex on one language while hreflang still lists it — signals conflict.
Validate in Search Console International targeting
Legacy reports may be limited; also crawl a sample set with third-party hreflang checkers and view page source on each locale’s <head>.
Translate substance, not only chrome
Menus and footers in the right language help users; body content must match locale intent (currency, units, legal notes).