International SEO Audit: A Step-by-Step Checklist for Multi-Country Sites

Your UK page ranks in Australia. Your German content shows up for Swiss searchers with prices in euros. Your Spanish pages exist, but Google keeps serving the English version in Mexico. None of these are content problems. They're signals problems, and an international SEO audit is how you find them.
Most SEO audits assume one site, one language, one market. The moment you target a second country, that assumption breaks. Pages start competing with their own translations, hreflang tags quietly fail, and search engines guess which version to show. Often they guess wrong.
This guide walks through exactly how to run an international SEO audit: what to check, in what order, which tools help, and how to decide what to fix first. It's the same framework we use at KodRank when a client's global traffic doesn't match the effort they've put into expansion.
What Is an International SEO Audit?
An international SEO audit is a review of how well a website signals which language and country each page targets, and whether search engines show the right version to the right audience. It covers hreflang, URL structure, localized content, technical setup, and market-specific rankings and links.
A standard SEO audit asks, "Can Google crawl, understand, and rank this site?" An international audit adds a harder question: "Does Google know which version belongs where?"
That second question is where most multi-market sites leak traffic. A technically healthy site can still underperform abroad if its regional pages cannibalize each other or its translations read like translations.
When do you need an international SEO audit?
Run one if any of these sound familiar:
- You're about to launch in a new country or language. Auditing before launch is far cheaper than cleaning up after.
- The wrong regional page ranks. US pages appear in UK results, or the English version outranks your local-language page.
- International traffic is flat despite new content. You've translated pages, but organic visits in those markets haven't moved.
- You've migrated or restructured. Moving from subdomains to subfolders, or changing CMS, often breaks hreflang and redirects.
- Conversions differ sharply by market. Visitors arrive but leave, which often points to currency, language, or trust mismatches.
International SEO audit vs. regular SEO audit
| Area | Regular SEO audit | International SEO audit |
|---|---|---|
| Scope | One market, one language | Several markets and/or languages |
| Key technical check | Crawlability, indexing, speed | All of that, plus hreflang, canonicals across locales, and redirects by region |
| Keywords | One keyword set | A separate keyword set per market, researched locally |
| Content | Quality and intent match | Localization, currency, units, cultural fit |
| Rankings | Tracked in one country | Tracked per country, per language, sometimes per search engine |
| Backlinks | Overall authority | Authority from sites in each target market |
How to Do an International SEO Audit: 9 Steps
Work through these in order. Each step depends on the one before it, so fixing hreflang before you've settled your targeting strategy usually means fixing it twice.
- Confirm your targeting strategy
- Audit your URL structure
- Validate hreflang
- Check canonicals, redirects, and indexing per locale
- Review localization quality
- Run market-specific keyword research
- Audit on-page elements per version
- Analyze backlinks by market
- Track rankings and traffic per country
Step 1: Confirm your targeting strategy
Before touching a single tag, write down what each version of the site is for. Are you targeting languages (Spanish speakers anywhere), countries (Spain specifically), or language-country pairs (Spanish in Mexico vs. Spanish in Spain)?
This matters because the answer decides everything else. If your "Spanish" section is written for Spain but most of your Spanish-speaking demand comes from Latin America, no amount of technical cleanup will fix the mismatch.
Check Google Analytics and Search Console for where your traffic actually comes from, then compare that to where your business actually sells. Gaps between the two are your first finding.
Step 2: Audit your URL structure
There are three common ways to separate international versions:
| Structure | Example | Strengths | Trade-offs |
|---|---|---|---|
| ccTLD | example.de | Strongest country signal; high local trust | Each domain builds authority separately; more to maintain |
| Subfolder | example.com/de/ | Shares the main domain's authority; simplest to manage | Weaker country signal on its own |
| Subdomain | de.example.com | Can be hosted separately | Authority sharing is less clear-cut than subfolders |
No single option is always right. What the audit checks is consistency. Red flags include mixing structures without a reason (some markets on subfolders, one on a subdomain, another on a ccTLD), and URL parameters like ?lang=de as the only way to separate languages. Google recommends against parameter-based locale URLs.
Step 3: Validate hreflang
Hreflang is where international audits find the most errors. It tells search engines which URL to show for each language or region, and it only works when it's implemented precisely.
For every page with alternates, check that:
- Language codes are valid. Use ISO 639-1 for language (
en,de) and ISO 3166-1 Alpha-2 for region (en-GB,pt-BR). A region on its own, likehreflang="gb", is invalid. So isen-UK: the correct code isen-GB. - Every page references itself. Each version lists its own URL among the alternates.
- Links are reciprocal. If the English page points to the French page, the French page must point back. One-way annotations are ignored.
- Targets return 200 status codes. Hreflang pointing at redirects, 404s, or noindexed pages is wasted.
- Targets are canonical. Every hreflang URL should be the canonical version of that page, not a variant.
- x-default is set. It tells Google which page to show users whose language or region you don't target, often a country selector or your main global page.
Also check where hreflang lives. It can go in the HTML<head>, in HTTP headers (useful for PDFs), or in the XML sitemap. Pick one method. Using several increases the chance they contradict each other.
Here's what a correct set looks like for a page in three versions:
<link rel="alternate" hreflang="en-us" href="https://example.com/us/pricing/" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/pricing/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/pricing/" />
The same block appears on all versions of that page.
Step 4: Check canonicals, redirects, and indexing per locale
This is the most common silent killer we see: a translated page with a canonical tag pointing back to the English original. That tells Google the translation is a duplicate, so it drops out of the index, and the hreflang pointing to it stops working.
In this step, check:
- Self-referencing canonicals on each localized page.
- Automatic redirects based on IP or browser language. Google advises against forcing users to a version based on location. Googlebot mostly crawls from US IP addresses, so aggressive geo-redirects can stop it from ever seeing your other versions. Use a dismissible banner or country selector instead.
- Index coverage by locale. In Search Console, filter the Pages report by subfolder (or check each ccTLD property) and compare indexed counts to published counts.
- XML sitemaps. Each locale's URLs should be included, and none should be blocked in robots.txt.
If these fundamentals are shaky across the whole site, not just its international sections, it's worth reading our breakdown of how SEO performance marketing prioritizes technical fixes before going deeper.
Step 5: Review localization quality
Google determines a page's language from its visible content, not from code. So the words on the page matter more than any tag.
Look for:
- Machine translation left unedited. It often reads correctly but misses how locals phrase things.
- Mixed languages. Navigation, footers, forms, and error messages left in English on a French page.
- Wrong currency, units, date formats, and phone numbers. A German page quoting prices in dollars sends a mixed signal to users and search engines.
- Duplicate content across same-language markets. US, UK, and Australian pages that are word-for-word identical give Google little reason to rank each one. Spelling, pricing, shipping details, and local examples help differentiate them.
- Cultural fit. Imagery, testimonials, and trust signals (local reviews, local payment methods, local contact details) that make sense for that market.
Step 6: Run market-specific keyword research
Translating your English keywords is not keyword research. People in different countries often search for the same thing using different words.
A British searcher looks for "mobile phone contracts"; an American looks for "cell phone plans." A Spanish speaker in Mexico and one in Spain may use entirely different terms for the same product. The audit should confirm that each market's target keywords were researched in that market, with that country's search volume, not just translated.
Also check which search engines matter. Google dominates most markets, but not all of them. Baidu leads in China, Naver is a major player in South Korea, and Yandex is significant in Russia. If a target market leans on a different engine, the audit should include its requirements too.
Step 7: Audit on-page elements per version
For each locale, check that titles, meta descriptions, headings, image alt text, and structured data are localized, not just copied. Common finds:
- English title tags on translated pages
- Identical meta descriptions across every country version
- Schema markup showing the wrong currency, address, or language
- Internal links on localized pages pointing to the English version instead of same-language pages
That last one is easy to miss and matters a lot. Internal links should keep users and crawlers inside the right language section.
Step 8: Analyze backlinks by market
Authority is partly local. A German page with links only from US sites has a weaker case for ranking in Germany than one with links from German publications, directories, and partners.
In your backlink tool, segment referring domains by country (ccTLD or site language) and map them against each target market. Markets with little to no local link equity are where link building should focus next.
Step 9: Track rankings and traffic per country
Finally, measure the right thing. Global average rankings hide market-level problems.
- Set up rank tracking per country and language, on the search engine that matters there.
- In Search Console, use the Country filter in the Performance report to compare clicks and impressions by market.
- Check which URL ranks, not just the position. If your UK page ranks in the US, the problem is hreflang or content differentiation, not authority.
- Tie traffic to conversions per market so you know which fixes are worth the most.
Common International SEO Issues an Audit Uncovers
The same handful of problems shows up again and again. If you only have time for a quick check, start here.
| Issue | What it looks like | Why it hurts |
|---|---|---|
| Missing return links | Page A lists Page B in hreflang, but B doesn't list A | Google ignores the unconfirmed pair |
| Invalid codes | en-UK, es-LA, or a region code on its own |
The annotation is ignored |
| Canonical conflicts | Translated pages canonicalize to the English original | Translations get dropped from the index |
| Forced geo-redirects | Visitors (and crawlers) sent to a version by IP | Other versions may never be crawled |
| Hreflang to broken URLs | Alternates that 404, redirect, or are noindexed | The whole cluster weakens |
| Near-duplicate same-language pages | US, UK, and AU pages with identical copy | Google picks one and filters the rest |
| Half-translated templates | Localized body copy, English nav and forms | Weak language signal, poor user trust |
| Translated, not researched, keywords | Direct translations of English terms | Pages target phrases nobody searches locally |
| English internal links on local pages | Localized content links back to /en/ | Users and crawlers leave the right section |
Notice that only a few of these are purely technical. Most international SEO failures sit where technical setup, content, and market research meet, which is exactly why they slip through a standard audit.
Tools for an International SEO Audit
You don't need a large stack. You need tools that can see your site the way each market sees it.
| Tool type | Examples | What to use it for |
|---|---|---|
| Search engine data | Google Search Console, Bing Webmaster Tools | Index coverage per locale, country performance filters, crawl issues |
| Site crawler | Screaming Frog, Sitebulb, Ahrefs Site Audit, Semrush Site Audit | Hreflang validation, canonical conflicts, status codes, missing return links |
| Analytics | Google Analytics 4 | Traffic and conversions by country and language |
| Keyword and rank tracking | Semrush, Ahrefs | Local search volume, country-level rank tracking, which URL ranks where |
| Backlink analysis | Ahrefs, Semrush, Majestic | Referring domains segmented by country |
| Local SERP checks | A VPN, or a location setting in your rank tracker | Seeing real results as a searcher in that market sees them |
One practical tip: a crawler tells you whether hreflang is valid. Only Search Console and country-level rank tracking tell you whether it's working. You need both views.
How to Prioritize Fixes After the Audit
An international SEO audit on a large site can surface hundreds of issues. Don't fix them in the order you found them. Fix them in the order they block revenue.
- Indexing blockers first. Wrong canonicals, forced redirects, and robots.txt blocks can keep entire markets out of search. Nothing else matters until those pages can be indexed.
- Hreflang errors next. Once pages are indexable, make sure the right version shows in the right market.
- Your highest-value markets before the rest. Rank markets by revenue potential, not by traffic. A small market that converts well may deserve attention before a large one that doesn't.
- Localization and keyword gaps. Rewrite the pages that matter most using researched terms locally.
- Local authority building. Start earning links in the markets where content and technical setup are now solid.
This mirrors how we approach any SEO engagement at KodRank: measure what each market is worth, fix what's blocking it, then build. We cover that thinking in more depth in our guide to turning SEO rankings into revenue.
Should you audit in-house or hire help?
If you have one or two markets and a developer who can edit templates, you can handle much of this checklist yourself. It gets harder with many locales, multiple domains, or a CMS that generates hreflang automatically. Those setups tend to fail in ways that are hard to spot without a full crawl.
If you're comparing providers, look for experience with country targeting, hreflang, and link building in your target markets. Our guide on choosing an SEO services company lists the questions worth asking before you sign anything.
Want a second pair of eyes on your global setup? KodRank's team handles technical SEO, on-page optimization, and site architecture as one package. Book a free site audit, and we'll show you what's holding your international rankings back, with a prioritized plan to fix it.
International SEO Audit FAQs
How long does an international SEO audit take?
It depends on the number of markets, languages, and pages. A small site with two or three locales can often be audited in a few days. A large ecommerce site across many countries and domains can take several weeks, mostly because each market needs its own keyword, content, and ranking review.
How often should you run an international SEO audit?
Run a full audit before entering a new market and after any migration, redesign, or CMS change. Between those, a lighter quarterly check of hreflang errors, index coverage per locale, and country-level rankings catches most problems before they cost traffic.
Does hreflang improve rankings?
Not directly. Hreflang doesn't make a page stronger. It helps search engines swap in the right language or regional version for each searcher, which improves relevance and click-through in each market.
Is hreflang required if my site only uses one language?
No, unless you have different versions of the same language for different countries, such as separate US and UK pages. In that case hreflang helps Google tell them apart.
Which is better for international SEO: ccTLDs, subfolders, or subdomains?
There's no universal winner. ccTLDs send the clearest country signal but split your authority across domains. Subfolders keep authority on one domain and are easiest to manage. The right choice depends on budget, team size, and how different each market's offering is. Consistency matters more than the choice itself.
Can I just auto-translate my site for international SEO?
You can, but it rarely performs well on its own. Machine translation misses local search terms and phrasing, and unedited output can read as low quality. Use it as a first draft, then have native speakers edit it and align it with local keyword research.
What's the difference between international SEO and multilingual SEO?
Multilingual SEO targets different languages. International SEO targets different countries, which may or may not speak different languages. A site targeting the US, UK, and Australia is international but not multilingual. Most international SEO audits cover both.