When I audit a website that operates in multiple countries or languages, the technical complexity jumps significantly. Most international sites I look at have at least one major technical issue, usually hreflang implementation, and/or canonical/hreflang conflicts.
URL Structure Decisions
Before launching internationally, pick how you’ll organize different language or country versions. This affects everything else.
| Structure | Example | Best For | Pros | Cons |
| ccTLD | example.de, example.fr | Large companies with resources for multiple markets | Strongest geographic signal, and builds local trust | Expensive, and splits domain authority. |
| Subdirectory | example.com/de/, example.com/fr/ | Most businesses starting international expansion | Consolidates authority, simplifies management. | Weaker geographic signal than ccTLD |
| Subdomain | de.example.com, fr.example.com | Sites needing technical separation per market | Can set different server locations per subdomain | Doesn’t pass authority well, more complex than subdirectories |
I usually recommend subdirectories for most businesses. They’re simpler to manage, consolidate domain authority, and you can still set up separate Search Console properties for each using the URL prefix method.
Hreflang Implementation Mistakes
Google does a decent job figuring out what language users read. The problem isn’t language detection, it’s the code implementation.
Common mistakes I catch repeatedly:
Pointing to non-canonical URLs: Your hreflang points to one URL while your canonical points somewhere else. You’re sending conflicting signals. Hreflang should point to the canonical URL.
Missing return links: If your English page has hreflang pointing to German, the German page needs hreflang pointing back. Every version needs to reference all others, including itself.
Forgetting x-default: This tells search engines which version to show when no language/region matches.
Cross-domain without implementation: Separate domains (example.com and example.de) without hreflang between them. Google won’t figure this out automatically.
For broader technical audit coverage, check out what is a technical SEO audit.
Multilingual Sitemap Setup
You have two options:
Separate sitemaps per language: Create sitemap-en.xml, sitemap-de.xml, etc. Submit each to Search Console separately. Makes tracking indexation per language easier.
Sitemap index file: Master sitemap pointing to all language-specific sitemaps. Cleaner but harder to troubleshoot.
I go with separate sitemaps submitted to separate Search Console properties. Make sure your sitemap URLs match exactly what’s in your hreflang tags.
Google Search Console Setup Changes
Google deprecated the International Targeting report in September 2022. The geotargeting setting had little value since hreflang handles this better.
What to do instead:
Set up separate Search Console properties for each language version using the URL prefix method. So example.com/en and example.com/de become two separate properties.
This gives isolated performance data, indexation reports, and Core Web Vitals per market. When something breaks in your German version, you’ll see it immediately without noise from other markets.
Google Search Central has detailed hreflang documentation that’s actually helpful if you want to understand the technical requirements.
Canonical and Hreflang Working Together
This is one of the most frequent mistakes I catch.
Each language version should have a self-referential canonical pointing to itself. English page canonical points to English URL, German to German URL.
Then hreflang tags on each page point to all alternate versions, including itself.
Where it breaks: someone canonicalizes all pages to one “main” language version but still has hreflang pointing to multiple versions. This sends conflicting signals.
If pages are identical and you don’t need both indexed, use canonical without hreflang. If pages are different enough for separate indexing, use hreflang with self-referential canonicals.
Ahrefs has a good international SEO guide that covers infrastructure considerations in more detail.
Content Localization vs Translation
Translation converts words. Localization adapts content for a specific market: keywords, cultural references, units, examples, and how people actually search.
I worked on a site where they translated “attorney” to German, but Germans search for “Rechtsanwalt” or “Anwalt” depending on context. Direct translation isn’t how people search.
Localization includes local currencies, date formats, culturally relevant examples, and adapted images. From a technical SEO perspective, this affects keyword targeting, title tags, meta descriptions, and URL slugs.
Core Web Vitals by Region
Core Web Vitals matter everywhere, but acceptable thresholds vary by region. Sites that pass in the US can fail in Southeast Asian markets due to slower networks and older devices.
Test performance from actual user locations. Use WebPageTest to test from specific geographic locations or Chrome DevTools to throttle connection speeds.
Don’t assume good Core Web Vitals in one market mean you’re fine everywhere.
Crawl Budget for Multiple Markets
When you have ten language versions, the crawl budget gets complicated. Search engines have finite resources.
Watch for duplicate pages across language versions, parameter handling creating URL variations, pagination implemented differently per market, and redirect chains between international versions.
Understanding when to perform a technical SEO audit is especially important before launching new international versions.
International Technical SEO Audit Checklist
- Verify hreflang implementation using Screaming Frog
- Check hreflang tags point to canonical URLs
- Confirm all return links exist (bidirectional)
- Test x-default is set appropriately
- Review URL structure consistency
- Audit sitemap structure and Search Console submission
- Verify the separate Search Console properties setup
- Test page speed from target market locations
- Check Core Web Vitals per market
- Analyze crawl budget using server logs
- Review content for localization (not just translation)
- Test language/region switchers
- Verify internal linking between versions
- Check for duplicate content across markets
For common pitfalls, see common technical SEO audit mistakes.
Tools That Work
Screaming Frog handles hreflang validation perfectly. Configure it to crawl with hreflang detection enabled. It shows missing return tags, incorrect language codes, and canonical/hreflang conflicts.
Google Search Console remains primary for tracking performance per market with separate properties.
WebPageTest tests page speed from different locations worldwide.
More on technical SEO audit tools for 2025.
Watch This for Hreflang Setup
Aleyda Solis has excellent videos on international SEO implementation.
Why This Matters
The technical foundation determines whether your international SEO works at all. I’ve seen companies invest months building new market websites, only to launch with broken hreflang or canonical conflicts preventing pages from ranking.
Getting the setup right from the start is easier than fixing it later. Why technical SEO is important gets amplified internationally — one mistake affects your entire global presence.
When Professional Help Makes Sense
If you’re running more than two or three language versions, a professional audit probably makes sense. The complexity increases fast, and small errors cascade across markets.
If you’re planning international expansion or existing international sites aren’t performing well, get in touch for a comprehensive technical SEO audit. I’ll analyze your multi-market setup and identify exactly what’s holding your international SEO back.
Leave a Reply