International SEO Audit: A Step-by-Step Framework for Multi-Market Sites

Here’s what happens when companies “do international SEO” without auditing first: they translate 500 pages into four languages, set up hreflang tags based on a blog post they skimmed, and then wonder why their German site gets zero traffic while their English pages are cannibalising themselves across three markets.

We’ve audited international sites that were losing six figures in annual organic revenue from hreflang errors alone. Not complex algorithmic issues. Not competitive pressure. Just broken implementation that nobody checked.

An international SEO audit isn’t optional. It’s the difference between knowing where you stand and guessing while your budget burns.

The Audit Framework

This is the same framework we use on every multi-market engagement. It’s structured in order of impact, so start at the top and work down.

Step 1: Hreflang Validation

Hreflang errors are the #1 technical issue on international sites. They’re also the most impactful to fix because they directly control which page Google shows in which market.

What to Check

Reciprocal tags: Every hreflang relationship must be bidirectional. If your English page declares a German alternate, the German page must declare the English page back. Pull every hreflang annotation across your site and check for missing return tags.

Self-referencing tags: Every page must include a hreflang tag pointing to itself. It sounds redundant but Google requires it. Missing self-references cause Google to treat the entire hreflang set as ambiguous.

Language/region code accuracy: The number of sites using en-uk instead of en-gb is staggering. Or zh-cn when they mean zh-hans. Google silently ignores incorrect codes. No error message, just broken targeting.

x-default presence: Every hreflang set should include an x-default tag pointing to a fallback page (usually the English or primary language version). Without it, users from untargeted regions may see unpredictable results.

URL accuracy: Hreflang annotations must point to live, indexable URLs. Not redirected pages. Not 404s. Not URLs blocked by robots.txt. Crawl every URL referenced in your hreflang tags and verify they return 200 status codes.

How to Audit It

For smaller sites (under 5,000 pages): Use Screaming Frog with the hreflang extraction configured. It will flag missing reciprocal tags, invalid codes, and broken URLs automatically.

For larger sites: Use Ahrefs Site Audit or Sitebulb for hreflang analysis at scale. Both tools cross-reference hreflang annotations across the entire crawl and surface errors in bulk.

Manual verification: Pick 20 pages across different markets and manually check their hreflang annotations in the page source. Automated tools catch most issues but miss edge cases like JavaScript-rendered hreflang that bots don’t see.

Common Errors and Fixes

Error	Impact	Fix
Missing reciprocal tags	Google ignores both pages’ hreflang	Add return tags on the missing side
Incorrect language codes	Silent failure, targeting doesn’t work	Correct to ISO 639-1 / ISO 3166-1 Alpha 2
Hreflang pointing to redirected URLs	Weakened signal, potential misattribution	Update annotations to point to final destination URLs
Hreflang in HTML conflicting with sitemap	Google gets confused, picks one randomly	Use one implementation method consistently
Missing x-default	Users from untargeted regions see wrong page	Add x-default pointing to your primary language version

Step 2: Duplicate Content Across Markets

When content exists in multiple languages or regional variations, Google needs clear signals about which version belongs to which market. Without them, it picks winners and losers on its own, and it often picks wrong.

Types of International Duplicate Content

Same-language regional variants: An English page for the UK, US, and Australia. The content may be 95% identical with only pricing, spelling, and minor references differing. Google may consolidate these into a single result, showing the wrong country’s page.

Untranslated content: Sections of your site that exist in one language but have empty or placeholder pages in other languages. Some CMS platforms generate these automatically, creating dozens of thin pages per locale that dilute your crawl budget and create duplicate content signals.

Machine-translated thin pages: Content that was run through translation software without review, producing grammatically awkward pages that add no value over the original. Google can identify machine-translated content and may devalue or deindex it.

How to Find It

Run a crawl comparison between your English site section and each localised section:

Export all URLs per locale with their title tags, H1s, meta descriptions, and word counts
Flag pages where the localised version matches the English version. These are untranslated or partially translated
Check for URL-level canonicals pointing cross-locale, e.g., your German page canonicalising to the English version (this tells Google the German page is a duplicate, not an alternate)
Use Copyscape or Siteliner to check for content similarity percentages across locale sections

Fixes

For same-language variants: Ensure hreflang is correctly implemented. Add unique content where possible: local case studies, market-specific data, regional pricing. Even 20-30% unique content per variant significantly reduces consolidation risk.

For untranslated pages: Either translate them properly or noindex them until translated. Do not leave placeholder pages or English content behind locale-specific URLs. It confuses both users and search engines.

For machine-translated content: Either invest in human review and editing, or remove the pages. Low-quality translations actively hurt your site’s perceived quality in that market.

Step 3: Geo-Targeting Signal Audit

Google uses multiple signals to determine which country a page targets. Your audit should verify that these signals are consistent, not contradicting each other.

Signals to Check

Search Console geo-targeting: For generic TLDs (.com, .net, .org), check that Search Console’s International Targeting feature is set to the correct country per section. For ccTLDs, this is automatic.

Server location / CDN configuration: Where your content is served from matters less than it used to, but it’s still a signal. Verify your CDN is serving content from nodes in your target markets. Run speed tests from each target country using tools like WebPageTest (select test locations in your target markets).

Contact information: Local addresses, phone numbers, and business registration details on market-specific pages reinforce geo-targeting. If your German pages show a US phone number and address, that’s a conflicting signal.

Currency and language declarations: The lang attribute on your HTML tag should match the page’s language. Content showing prices in USD on a UK-targeted page sends mixed signals.

Local business schema: If you have physical presence in a market, implement LocalBusiness structured data with the local address. This reinforces geo-targeting at the schema level.

Internal linking patterns: Pages within a locale should primarily link to other pages within the same locale. If your German product page links to English category pages, you’re bleeding authority across locales and confusing Google about the site’s structure.

Step 4: Local Ranking Performance Per Market

Your site might rank #3 in the UK and #47 in Germany for the same keyword (localised). Market-by-market ranking data tells you where you’re winning, where you’re invisible, and where you have untapped opportunity.

How to Measure

Google Search Console: Filter by country in the Performance report. Compare impressions, clicks, CTR, and average position across markets. This is your most reliable data source because it’s Google’s actual data.

Rank tracking tools: Set up keyword tracking per target country in Ahrefs, SEMrush, or AccuRanker. Track both local-language keywords and English keywords in English-speaking markets. Most tools let you select specific Google regional domains (google.de, google.fr, etc.) for accurate local results.

Competitor benchmarking: For each market, identify who ranks in the top 5 for your target keywords. Are they local businesses? International competitors? User-generated content sites? The competitive landscape varies dramatically by market.

What to Do With the Data

Build a market-level scorecard:

Market	Target Keywords	Avg Position	Monthly Impressions	Monthly Clicks	Top Competitor
UK	45	8.2	120,000	9,800	localcompetitor.co.uk
Germany	38	23.4	45,000	1,200	konkurrent.de
France	42	31.7	38,000	680	concurrent.fr

This immediately shows you where to focus. A market with high impressions but low clicks has a CTR problem (likely wrong page ranking, or poor title tags). A market with low impressions has a visibility problem (likely authority or content gaps).

Step 5: Content Gap Analysis Per Country

Different markets have different search behaviours, different questions, and different content needs. Your English content strategy doesn’t automatically translate.

The Process

For each target market:

Export your ranking keywords for that market from Search Console or your rank tracker
Export competitor keywords for the top 3 local competitors using Ahrefs or SEMrush
Identify gaps: Keywords competitors rank for that you don’t have content for
Categorise gaps: Are they language-specific terms? Market-specific topics? Product categories you offer but haven’t localised?
Prioritise by volume and commercial intent: A gap on a 10,000-volume transactional keyword is worth more than a gap on a 100-volume informational keyword

Common Gap Patterns

Product/service terms that don’t translate directly: Different markets use different terminology for the same thing. Your keyword mapping needs to account for this. Not just translate, but research what people actually search.

Local regulatory or industry content: German users searching for products in regulated industries want content that references German regulations. UK users want UK-specific compliance information. This content doesn’t exist in your English version because it’s market-specific.

Cultural content gaps: Some markets have content expectations that others don’t. Japanese users often expect more detailed product specifications. German users expect thorough comparison content. UK users value reviews and editorial recommendation content.

Step 6: Technical Health Per Locale

Technical issues can affect your entire site or be isolated to specific locales. An audit needs to check each market section independently.

Per-Locale Technical Checks

Crawlability: Is each locale section accessible to Googlebot? Check robots.txt for accidental blocks on locale directories. Verify XML sitemaps per locale are submitted and processing correctly in Search Console.

Indexation: How many pages per locale are indexed vs submitted? A significant gap suggests crawlability or quality issues. Check the Coverage report in Search Console per property.

Page speed per region: Run Core Web Vitals tests from each target market. A site that loads in 1.5s from London might take 4.5s from Tokyo if your CDN doesn’t have Asian edge nodes. Use PageSpeed Insights with different geographic settings, or CrUX data filtered by country.

Mobile experience: Mobile search share varies by market. In many Asian and African markets, mobile accounts for 80%+ of searches. Test your localised pages on mobile devices and verify there are no locale-specific layout issues (different text lengths in different languages can break responsive layouts).

Structured data per locale: Verify schema markup exists on localised pages with correct local values: language, currency, regional pricing. Schema should not simply be copied from the English version with English values. For a complete guide to implementing structured data correctly, see our technical SEO checklist.

Internal link structure: Map internal links within each locale. Are there orphan pages? Are key pages receiving sufficient internal links? Is the locale self-contained, or do links leak to other language versions unnecessarily?

Step 7: Compile the Fix List

After completing steps 1-6, you’ll have a list of issues across multiple markets and multiple categories. Prioritise them using this framework:

Priority 1: Revenue-Impacting Technical Issues

Hreflang errors causing wrong pages to rank in wrong markets
Canonical errors consolidating locale pages into the wrong version
Indexation blocks preventing entire locale sections from ranking
Duplicate content causing cannibalisation between locales

Priority 2: Market-Specific Performance Issues

Missing content for high-volume keywords in key markets
Geo-targeting signal conflicts
Page speed issues in target markets
Missing or incorrect structured data

Priority 3: Maintenance and Optimisation

Content quality improvements on underperforming localised pages
Internal linking improvements within locales
Local authority building recommendations
Content gap coverage for lower-volume opportunities

Each issue should include: the problem, which market(s) it affects, estimated traffic/revenue impact, the fix, and implementation effort. This turns an audit into an actionable roadmap.

Running This Audit on an Ongoing Basis

International SEO isn’t a one-time setup. Markets change, content gets added, redirects break, CMS updates introduce issues. If you’re planning a platform migration or domain restructure, multi-market signals are the first casualty - our SEO migration strategy guide covers how to preserve international rankings during structural changes. Schedule recurring checks:

Monthly: Hreflang validation (automated crawl), index coverage per locale, ranking trends per market Quarterly: Full content gap analysis, competitor benchmarking, geo-targeting signal review, per-locale technical crawl Annually: Complete audit using this full framework, market prioritisation review, strategy reassessment

The companies that maintain their international SEO performance are the ones that audit continuously, not the ones that did it once and hoped for the best.

Want to skip the manual audit? Get a free teardown and we’ll show you which markets are underperforming and why.

Go Further

This audit framework tells you where you stand. The next step is building the strategy to fix what’s broken and expand what’s working.

Want the full system? Read our complete International SEO guide.