Got something worth sharing? We want to hear from you.Share Your Knowledge →

International SEO Audit: A 10-Point Technical Checklist

Listening to ArticlePlaying
0%
International SEO audit checklist globe graphic

If your site already has translated pages, country folders, or hreflang tags in place, the real question is not whether you did international SEO. It is whether you did it correctly. An international SEO audit answers that question by checking four things: your URL structure, your hreflang markup, your duplicate content exposure, and your country-level performance in Search Console. Get those four right and search engines can tell which page belongs to which audience. Get even one wrong and you risk the wrong country version ranking, or no version ranking at all.

This checklist walks through the audit in the order I’d actually run it on a live site, with the specific errors that cause most of the damage. None of these checks require expensive tooling. A crawler, Search Console access, and an hour of patience will get you through most of it.

What Your International SEO Audit Should Confirm First

Before touching a single hreflang tag, confirm the basics. Are the localized pages actually indexed? Are they returning a 200 status code? Is each one reachable from internal navigation, rather than sitting only in a sitemap entry nobody clicks?

An international SEO audit that skips this step tends to waste time debugging hreflang annotations on pages Google never crawled in the first place. Pull your indexed URL count by directory or subdomain before you look at anything else. If a country folder has far fewer indexed pages than it should, that’s your starting point, not the hreflang code.

Check robots.txt for a disallow rule that accidentally blocks an entire country folder, something that happens more often than it should after a migration or a staging-to-production copy. Also confirm your server renders hreflang tags in the actual HTML response, not only after JavaScript runs. If your CMS injects hreflang client-side, fetch the raw page source (not the rendered DOM) and check it’s there, since some crawlers and some Googlebot passes read the initial HTML before JavaScript executes.

Once the basics check out, move to structure.

URL Structure: Subdirectories, Subdomains, or ccTLDs

Your URL structure decision shapes almost everything else in the audit. Google treats subdirectories, subdomains, and country-code domains as roughly equal options, so there’s no single “correct” answer here. What matters is consistency. I’ve seen sites mix all three (a ccTLD for one country, a subdomain for another, a URL parameter for a third) and the inconsistency alone made the hreflang set harder to maintain and easier to break.

If your structure already works, your audit job is to confirm it’s applied uniformly, not to re-architect it. We cover the trade-offs between these approaches, including setup cost and hosting complexity, in the comparison table further down this guide. For a deeper technical pass on folder naming, trailing slashes, and parameter handling, see our URL structure SEO audit.

Hreflang Implementation: The Checks That Catch Real Errors

Hreflang is where most international SEO audits find their first real problems. Google’s Search Central documentation, updated as recently as September 2026, lays out the same handful of rules it has held for years, and most broken implementations violate at least one of them.

ADVERTISEMENT

Run through these on every localized page:

  • Self-referencing tags. Every page needs to list itself in its own hreflang set, alongside every alternate version.
  • Reciprocal (return) links. If your /de/ page points to /fr/, the /fr/ page must point back to /de/. Google ignores annotations that aren’t reciprocal, which is exactly why one-way hreflang tags do nothing.
  • Valid language and region codes. Use a language code, with an optional region code attached, such as en-GB or fr-CA. A bare region code like “uk” does not work on its own, and reserved codes such as UK, EU, or UN are not valid regions at all. The United Kingdom is GB.
  • Fully qualified URLs. Every href needs the full protocol. A relative path breaks the annotation.
  • One consistent method. Pick HTML link tags, an HTTP header, or an XML sitemap. Google treats the three as equivalent, so using more than one just adds maintenance work for no extra signal.

Most hreflang validator tools in the market will catch missing return links and bad codes automatically. Run one, but don’t stop there. A tool can tell you the markup is syntactically valid; it can’t tell you whether Google is actually acting on it.

Why Hreflang Doesn’t Guarantee Indexing

This is the part a lot of international SEO checklists skip, and it matters. Google’s John Mueller has said directly that hreflang doesn’t guarantee indexing. Adding the tags correctly doesn’t force every language variant to get indexed or ranked on its own. When two versions are nearly identical, such as fr-FR and fr-BE with only minor differences, Google will often pick one as canonical and treat the other as a near duplicate regardless of the hreflang annotation.

In a separate comment reported by Search Engine Roundtable, Mueller also addressed hreflang tags pointing at 301 redirects, saying that’s probably fine, though he recommended pointing hreflang directly at final URLs to avoid canonicalization tracking problems down the line.

What this means for your audit: don’t treat “hreflang is implemented correctly” as the finish line. Check actual indexing status for each language variant in Search Console’s Page Indexing report. If a variant is sitting in “Duplicate, Google chose different canonical” or similar, the fix usually isn’t more hreflang tags. It’s making that page’s core content genuinely different, not just translated.

Duplicate Content and Canonicalization Risk Across Markets

Google’s documentation is specific on this point: localized pages count as duplicates mainly when the main content remains untranslated. A page that’s merely had its header and footer swapped for a different currency symbol, while the body copy stays in the source language, reads to Google as the same content with cosmetic changes.

That’s a canonicalization risk, not an international SEO win.

Check for these patterns during your audit:

  • Country pages where only the currency and phone number changed, with the body content pulled from a shared template.
  • Canonical tags pointing a localized page back to the original-language version instead of self-referencing.
  • Thin regional variants created automatically from one master page with no human review.

Any of these can trigger Google to fold multiple country pages into a single canonical, silencing the hreflang set entirely. If you’re also seeing canonical tags pointing at the wrong pages site-wide, our guide to Google canonicalization fixes covers the diagnostic steps in more depth than we have room for here.

Localized Content Quality: Beyond Translation

An audit that only checks code misses half the problem. Translation converts words. Localization adapts the actual experience, and that distinction shows up in rankings.

ADVERTISEMENT

Ask these questions about each market’s content:

  • Does the local keyword actually match search demand in that country, or is it a literal translation of the English term nobody searches for?
  • Are currency, measurements, shipping terms, and contact details adapted, not just translated?
  • Would a native speaker in that market recognize this as written for them, rather than translated at them?

In my experience, the markets that underperform despite “correct” hreflang are almost always the ones where nobody did local keyword research before translating. A direct translation of a high-volume English keyword can have close to zero search volume in the target language, while the term locals actually use never makes it into the page at all.

Search Console Monitoring: The Ongoing Half of Your International SEO Audit

The audit doesn’t end at launch. Country-level monitoring is what tells you whether the technical setup is actually working in search results, rather than merely passing a validator.

Segment your Search Console data by country and by page, not just globally. A rising total click count can hide a market that’s losing visibility. If German impressions are climbing while German clicks flatline, that’s a titles-and-descriptions problem, not a hreflang problem, and the two call for completely different fixes.

We’ve written a full walkthrough of segmenting Search Console by market in our Search Console country filter audit, which pairs well with the checks in this piece once your hreflang and URL structure are confirmed clean. For a wider view of how international SEO fits into an overall growth strategy, our international SEO strategy guide is a useful next read once this audit is done.

Country Targeting in Search Console: What’s No Longer There

If you learned international SEO a few years ago, you may be looking for the old International Targeting report in Search Console. It’s gone. Google deprecated it, as Search Engine Land reported, and Search Console’s own help documentation confirms the report no longer exists.

That report used to let you set an explicit country target for the whole site or for subfolders. Without it, country association now comes from signals you already control: hreflang, ccTLD or ccTLD-style subdomains, server location, and content language. Practically, this means your audit carries more weight than it used to. There’s no manual override setting left to fall back on if the signals are wrong, so getting hreflang and URL structure right is no longer optional groundwork, it is the targeting mechanism itself.

Comparing Hreflang Implementation Methods

Since URL structure and hreflang delivery method both come up repeatedly in an audit, it helps to see the trade-offs side by side. None of these is universally “best.” The right choice depends on your CMS, hosting setup, and how many markets you’re managing.

Approach Setup Cost SEO Signal Strength Hosting Complexity Best For
Subdirectories (example.com/de/) Low Strong (shares domain authority) Low, single hosting environment Most sites, especially those starting international expansion
Subdomains (de.example.com) Medium Moderate, can be treated semi-separately Medium, can isolate hosting per region Large organizations needing separate regional teams or infrastructure
ccTLDs (example.de) High, separate domains to register and maintain Strong local geo-signal, but no shared authority between domains High, multiple domains, SSL certs, and hosting to manage
URL parameters (example.com/?lang=de) Low Weak, Google generally discourages this method Low Rarely recommended; mainly legacy setups that haven’t migrated yet

In practice, most mid-sized sites running an international SEO audit for the first time find subdirectories easiest to fix and maintain. ccTLDs make sense mainly when there’s a legal, currency, or brand reason to run fully separate domains per country, not purely for SEO.

Frequently Asked Questions

How often should I re-run an international SEO audit?
Check hreflang validity and indexing status quarterly at minimum, and immediately after any site migration, CMS change, or URL structure update. Hreflang errors introduced during a migration are some of the most common and most damaging, since they often go unnoticed until country-level traffic drops.

ADVERTISEMENT

Can hreflang errors cause a page to stop ranking entirely?
Not directly. Google has said hreflang doesn’t affect rankings on its own; it affects which version gets shown to which user. A broken implementation can result in the wrong country version appearing in search results, or one version getting treated as a duplicate and dropped from the index, which has the same practical effect as a ranking loss.

Do I need hreflang if I only have one language but multiple countries?
Yes, if the content differs meaningfully by country, such as different currencies, shipping terms, or product availability for en-US versus en-GB. If the content is identical across English-speaking markets, a single page with no country targeting is often simpler and avoids duplicate content risk altogether.

What’s the fastest way to spot a broken hreflang set?
Check the Page Indexing report in Search Console for variants marked as duplicates with a different canonical selected by Google. That status is usually the clearest signal that a reciprocal link is missing or a language code is malformed, well before a manual code review would catch it.

Run through these checks in order: crawlability and indexing first, then URL structure consistency, then hreflang correctness, then duplicate content exposure, then localized content quality, then ongoing Search Console monitoring by market. Most international SEO problems live in the gap between “the code looks right” and “Google is actually treating each market the way you intended,” and that gap is exactly what a proper audit is built to close.

Responses

Leave a response

Your email address will not be published. Responses are reviewed before they appear.

Join the DevByte Daily list

AI, SEO and paid media coverage in your inbox. No spam.

ADVERTISEMENT

Share This

Questions or story tips?

Contact us

Enjoyed this article?

AI, SEO and paid media coverage in your inbox. No spam.