By [Vikas Verma] | Last updated: October 2026

You launched your site in a new country, but traffic is flat, similar pages compete with each other, and Google keeps showing your UK page to searchers in Australia. An international SEO audit helps you find out why.

It checks how your site is structured for each country and language, whether search engines can crawl and index every version, and whether each page sends the right signals for its market. This guide walks you through the audit in nine steps, and ends with a prioritization table and a checklist you can reuse.

What Is an International SEO Audit?

An international SEO audit is a review of everything that affects how your site appears in search results for people in different countries and languages. It builds on a standard technical audit, but adds questions that only appear once you have more than one market: which version should rank where, and can search engines tell your versions apart?

Google separates two situations. A multilingual site offers content in more than one language. A multi-regional site explicitly targets users in different countries. Many sites are both, for example a site with US and Canadian versions, and English and French content for Canada. Your audit should cover whichever applies to you. You can read Google’s own explanation in its guide to managing multi-regional and multilingual sites.

Before You Start: Tools and Inputs

Gather these before you begin:

• A crawler such as Screaming Frog SEO Spider or Sitebulb, to inspect hreflang, canonicals, status codes and indexability at scale.
• Google Search Console access for every version of the site, to check indexing and performance by country.
• A keyword and backlink tool (Semrush, Ahrefs or similar) that has data for your target countries. If you are still choosing one, our Ahrefs vs KWFinder comparison explains how keyword tools differ.
• Analytics (for example GA4) with country and language reporting turned on.
• A list of your target markets, languages, and the URL of each version of your key pages.

Step 1: Define Your Target Markets and Languages

Start with the business question, not the code. For each market, write down the country, the language, the currency and the search engine your audience mostly uses.

Then ask whether each market really needs its own version. Translating a page into German for Germany, Austria and Switzerland is one decision. Creating three separate German-language versions with different prices and legal text is another. Every extra version adds maintenance work and adds more pages that need links and attention.

What to check:

• Does every live version map to a real business goal?
• Are there versions nobody maintains, or that duplicate another version almost word for word?
• Do you know which search engines matter in each market? In some countries, Google is not the only major player.

Step 2: Review Your URL Structure

Your URL structure tells search engines which version belongs to which market. There are three common options.

Google describes these locale-specific URL options and their trade-offs in the same multi-regional guide. It also lists the signals it uses to work out a site’s target market, such as the country-code domain, server location, local addresses and phone numbers, local language and currency, and links from other local sites.

What to check:

• Is the structure consistent across all markets, or have different teams created different patterns?
• Does each version live at its own URL, rather than changing content on the same URL based on the visitor’s location?
• If your backlink profile is still small, would a single domain with subdirectories make link building easier than managing several ccTLDs? For many smaller sites, it does.

Step 3: Audit Your Hreflang Annotations

Hreflang tells Google that pages are alternate versions for different languages or regions. It is the most technical part of an international audit, and one of the easiest places for mistakes to hide. Google explains the setup in its guide to localized versions of your pages.

Run a full crawl with your crawler and check these points.

1. Return tags

If page A points to page B as its alternate, page B must point back to page A. If the pages do not point to each other, Google can ignore the annotation. Every page in the group should also reference itself.

2. Language and country codes

Use a valid language code, optionally followed by a country code. Language codes come from ISO 639-1 and country codes from ISO 3166-1 alpha-2.

• Correct: en-GB for English in the United Kingdom
• Incorrect: en-UK, because UK is not a valid country code in this standard (the code is GB)
• Incorrect: a country code on its own, such as GB, with no language

3. The x-default value

Add an x-default annotation for visitors who do not match any of your listed versions, such as a language selector page or your main version.

4. Canonical and hreflang must agree

Each localized page should normally have a canonical tag that points to itself. If /uk/shoes has a canonical tag pointing to /us/shoes, you are telling Google that the UK page is not the preferred version, and it may drop that page from the index. For background, see Google’s guide to consolidating duplicate URLs.

A correct setup on the UK page looks like this:

<!-- On https://example.com/uk/shoes -->
<link rel="canonical" href="https://example.com/uk/shoes" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/shoes" />
<link rel="alternate" hreflang="en-US" href="https://example.com/us/shoes" />
<link rel="alternate" hreflang="x-default" href="https://example.com/shoes" />

The same full set of annotations must appear on the US page and on every other version.

5. Pick one place to declare hreflang

You can declare hreflang in the HTML head, in HTTP headers (useful for non-HTML files), or in your XML sitemap. Choose one method and keep it consistent. Mixing methods makes errors harder to spot.

What to check:

• Missing return tags and missing self-references
• Invalid language or country codes
• Hreflang pointing to URLs that redirect, return errors, or are blocked
• Canonical tags that point to a different locale
• Pages in your sitemap with no hreflang set, or hreflang that contradicts the sitemap

Step 4: Check Crawling and Indexing for Every Version

A localized page that Google cannot crawl or index cannot rank. Check each version separately.

Watch out for automatic redirects

Some sites send visitors to a regional version based on their IP address or browser language. This can block search engines. Google notes that Googlebot usually crawls from the USA, so a site that redirects every US visitor to its US version may stop Googlebot from reaching other versions.

The safer approach is to let people choose. Show a banner such as: ‘It looks like you are in Canada. Would you like to switch to our Canadian site?’ Do not force the redirect.

How to test: open your key pages from different locations or with a VPN, and use the URL Inspection tool in Search Console to see what Google actually fetched.

Other indexing checks

• Are any locale folders blocked in robots.txt, or set to noindex by mistake?
• Does every version appear in a sitemap, and is that sitemap submitted in Search Console?
• In URL Inspection, does the Google-selected canonical match the canonical you declared? If Google picks a different version, it often means the pages look too similar or the signals conflict.
• Are important localized pages reachable through normal internal links, not only through a language selector?

Step 5: Check Keyword Localization

People in different countries often search for the same product with different words. A literal translation of your English keywords can miss the terms real users type.

Some examples: UK shoppers say ‘trainers’ where US shoppers say ‘sneakers’. Spanish speakers use different words for the same device in different countries. These differences also exist between English-speaking markets.

How to audit it:

1. List your top 20 pages for each market.
2. For each page, find the main keyword a local searcher would use, using a keyword tool with data for that country.
3. Compare it with the page’s title tag, H1 and headings. If the page uses a translated phrase that has little search demand, or uses another market’s vocabulary, mark it for rewriting.

Step 6: Review Content Localization and Quality

Good localization changes more than words. It adjusts examples, measurements, dates, legal text, product availability and tone.

Google notes that localized versions are only considered duplicates if the main content of the page stays untranslated. A properly translated page is not a duplicate. A page that is only partly translated, or one that keeps most of its text in the original language, is where problems begin.

What to check:

• Pages that are only partly translated, or that mix languages
• Near-identical regional pages in the same language, such as US and UK versions with only a flag changed
• Machine-translated text that nobody has reviewed. If you use AI to help translate or draft, review the output carefully; our guide to AI content and on-page SEO covers what to watch for.
• Large numbers of pages created quickly just to cover more countries. Google’s spam policies include rules on scaled content abuse, and our guide to recovering from the September 2026 spam update is a useful reminder of why quality matters at scale.

Step 7: Check Local Signals and Page Experience

Search engines and users look for signs that a page was made for them.

• Currency and pricing: Does the UK page show pounds with VAT, and does the US page show dollars?
• Contact details: Are there local phone numbers, addresses, support hours and return information for each market?
• Structured data: Does your Organization or LocalBusiness markup match the details visible on each page? Only mark up what users can actually see.
• Business Profile: If you have physical locations, check that your Google Business Profile listings match your website. For more on this, see our posts on how AI Mode affects local SEO and local SEO strategy for AI search.
• Speed in each market: Test pages from the countries you target. A content delivery network (CDN) can help visitors far from your server.

Step 8: Review Local Links and Authority

Technical setup helps search engines understand your versions, but links still matter for competing in each market. Google lists links from other local sites among the signals it can use to understand a site’s target audience.

How to audit it:

• Use your backlink tool to group referring domains by country or country-code domain. For a French version, how many links come from French sites?
• Look for local opportunities: industry associations, local press, local directories and partners.
• Check link quality as well as quantity. Our article on whether backlinks still matter explains why a few relevant links beat many low-quality ones.

Avoid buying links or using mass syndication, which can go against Google’s spam policies. Focus on being genuinely useful to local publishers and communities.

Step 9: Set Up Reporting by Country

You cannot fix what you cannot see. Set up reporting so you can compare markets over time.

• In Search Console, filter performance by country and by the version of the site, and compare clicks, impressions and average position over 28-day periods.
• In GA4, segment traffic and conversions by country and language.
• Track a small set of target keywords for each market.
• Note the date of every change so you can connect results to actions.

Do not judge results from a few days of data. Compare periods of at least several weeks.

Prioritize Your Fixes

An audit can produce a long list. Sort it by impact and effort, and start with issues that block crawling and indexing.

International SEO Audit Checklist

• Target markets, languages and currencies are defined
• URL structure is consistent (ccTLD, subdirectory or subdomain)
• Every localized page has a hreflang set that includes itself
• Return tags are correct on all versions
• Language and country codes are valid (for example en-GB)
• x-default is set
• Each localized page has a canonical tag pointing to itself
• No forced redirects based on IP or browser language
• No locale is blocked in robots.txt or set to noindex by mistake
• Every version is in an XML sitemap and submitted in Search Console
• Google-selected canonicals match your declared canonicals
• Keywords are researched for each market, not just translated
• Content is fully localized, including currency, contact and legal details
• Structured data matches the visible content on each version
• Pages load quickly in each target market
• Local backlinks are reviewed by country
• Search Console and GA4 reporting is set up by country

Common Mistakes

• Treating translation as localization. Translated text with the wrong currency, vocabulary or contact details still feels foreign to users.
• Canonicalizing all versions to one page. This tells Google to ignore the other versions.
• Setting hreflang on one page only. Annotations need to appear on every version in the group.
• Forcing visitors to a regional version. This can lock out both users and Googlebot.
• Launching too many markets at once. More versions mean more pages to maintain, link to and monitor.
• Ignoring the data. An audit is only useful if you track what changes after the fixes.

When to Hire a Specialist

You can run most of this audit yourself. Consider bringing in a specialist if you have many languages and regions, a large site where small template errors affect thousands of URLs, a recent migration, or traffic that dropped after launching a new market and the cause is not clear from your own checks.

Conclusion

An international SEO audit comes down to three questions: can search engines find and index every version of your site, can they tell which version is meant for which market, and does each version give local users what they expect? Start with the technical blockers, then move on to content, local signals and links. Re-run the audit after major site changes or when you add a new market.

VIKAS VERMA

Vikas Verma is an SEO specialist and web designer focused on SEO strategy, website design, and digital experiences.

@VikasVerma | vikas@digimastreys.com | LinkedIn

Vikas Verma

Vikas Verma is an SEO specialist and web designer focused on SEO strategy, website design, and digital experiences.