International technical SEO helps users and search engines reach the correct language, market and page version reliably. Technical compliance does not guarantee ranking, but status, canonical, localisation and rendering errors can prevent useful content from being discovered and understood.
1. Crawlability, status and rendering
- Priority pages return 200 with core copy in the initial HTML
- Robots rules allow indexable pages and essential resources
- Error pages do not return soft-404-style 200 responses
- Navigation and body use crawlable standard links
- Logs and Search Console verify access rather than assumption
2. Canonicals, redirects and URL consistency
Choose one stable canonical URL per page and align internal links, sitemap entries, canonical tags and redirects. Handle HTTP, non-preferred hosts, duplicate paths and trailing-slash variants consistently. Canonical is a signal, not access control; removals and migrations still require correct status and redirects.
3. Multilingual and multiregional architecture
Use stable crawlable URLs for each language and localise body copy, metadata, navigation and CTA. Hreflang should be reciprocal, self-referencing and point to indexable canonical pages; x-default can identify a fallback. Do not rely solely on IP or browser-language swaps, and do not treat machine translation as market research.
4. Sitemaps and internal discovery
Include only preferred canonical URLs in the sitemap, use absolute addresses and update lastmod for meaningful changes to content, structured data or links. Make services and insights reachable through navigation, clusters or related content. Sitemaps support discovery; they do not guarantee crawling, indexing or ranking.
5. Mobile experience, performance and accessibility
Test navigation, type, forms, images, tables, overflow and touch targets across real devices and widths. Optimise image delivery, fonts, scripts and caching without hiding core content behind delayed execution. Keep lab performance separate from field data.
6. Structured data, analytics and release QA
Structured data must match visible content and use real entities, dates and relationships. Before and after launch, verify status, canonical, hreflang, metadata, body, forms and key events, with a change log and rollback. Deployment is implementation—not proof of search or business outcomes.
Does hreflang guarantee the correct language page will rank?
No. Hreflang explains language/market relationships; pages still need indexability, coherent canonicals and genuine localisation.
How often should sitemap lastmod change?
Only after meaningful changes to content, structured data or important links—not through daily automatic freshness.
Must mobile and desktop expose the same links?
Priority discovery paths should remain equivalent. Removing key links on mobile can hurt users and discovery under mobile-first crawling.
Source：Google Search Essentials
Source：Google: Managing multilingual and multiregional sites