International SEO Audit: How to Evaluate Language Targeting, Hreflang, Architecture, and Regional Content

An international SEO audit should first confirm that each user and crawler can reach the right language or regional URL without confusion. If Google sees duplicate pages, mixed signals, or thin local content, rankings fragment by country. Revenue reports then start to look strange. The fix is not guesswork. Audit language targeting, hreflang, site structure, and regional content as one system.

1. Build a Market and URL Inventory

Start with a full list of languages, countries, domains, subdomains, and directories. Do not inspect pages one by one at random. That wastes time and hides patterns.

Your inventory should include:

• Market: United States, Germany, France, Canada, Australia.
• Language: English, German, French, Spanish.
• URL format: domain, subdomain, or subfolder.
• Canonical URL: the page Google is told to index.
• Hreflang target: the matching regional or language version.
• Index status: indexed, excluded, redirected, blocked.
• Organic traffic and conversions: by country and landing page.

This sheet becomes your source of truth. Without it, teams argue from memory. That usually ends badly.

2. Check Language Targeting Signals

Language targeting is not only a translation issue. Search engines read many signals. Users do too.

Review the HTML language attribute, page title, meta description, headings, body copy, currency, units, address format, phone numbers, legal notices, and trust badges. A page aimed at France should not show US shipping language, dollar pricing, and English customer support details.

Then compare analytics by country. If users from Spain keep landing on English pages, you may have weak local signals or broken internal paths. Check bounce rate, conversion rate, and search queries. A high impression count with a poor click rate can mean the snippet is not written for that market.

Honestly, it feels lazy when a site translates the product name but leaves reviews, FAQs, and delivery terms in another language. Users notice. Google may also decide the page is not the best answer for local intent.

3. Audit Hreflang With Precision

Hreflang tells search engines which version of a page should appear for a language or region. It does not create rankings by itself. It prevents the wrong URL from ranking in the wrong place.

Check four things first:

1. Valid language and country codes: use formats like en-us, en-gb, de-de, and fr-ca.
2. Return tags: if Page A points to Page B, Page B must point back to Page A.
3. Self-references: each localized page should reference itself.
4. Canonical agreement: canonical tags should not point to a different market version.

One ugly mistake is setting all local pages to canonicalize to the US page. That tells Google the US page is the main version. Hreflang then loses strength because the signals conflict.

Also inspect implementation type. Hreflang can sit in HTML headers, XML sitemaps, or HTTP headers. Pick one method when possible. Mixed setups are harder to maintain. They also create more chances for stale tags after launches.

It is maddening when audit tools show “valid” hreflang but take 20 seconds longer per crawl segment because redirects are chained through old market URLs. Test final destination URLs, not only visible tags.

4. Review International Site Architecture

Architecture decides how search engines crawl, understand, and rank regional pages. Three common models exist:

• Country code domains: example.de, example.fr, example.co.uk.
• Subdomains: de.example.com, fr.example.com.
• Subfolders: example.com/de/, example.com/fr/.

Country code domains send strong regional signals but require more maintenance. Subfolders are often easier to manage and consolidate authority. Subdomains sit in the middle, but internal linking and reporting can get messy.

There is no perfect model for every business. The right answer depends on team size, CMS limits, legal needs, product differences, and budget. What matters most is consistency.

Check these architecture risks:

• Regional pages buried too deep in the site.
• Language selectors that use scripts search engines cannot crawl.
• Automatic redirects that block users from switching country versions.
• Internal links pointing to the wrong locale.
• XML sitemaps missing local URLs.
• Robots.txt rules blocking translated sections.

5. Evaluate Regional Content Quality

Translation is not localization. A page can be grammatically correct and still fail because it ignores local search intent.

Compare each regional page against local competitors. Look at keywords, content depth, product filters, delivery terms, payment options, reviews, and examples. The German page may need technical specifications. The US page may need comparison tables. The Japanese page may need stronger proof of reliability and support.

Audit content at three levels:

• Core pages: home, category, service, product, location, pricing.
• Support pages: shipping, returns, warranty, FAQs, legal pages.
• Authority content: guides, case studies, research, local resources.

Thin local pages are a common drag on performance. If ten countries share nearly the same copy with only the currency changed, expect weaker results. Google has little reason to rank each version well.

6. Compare Search Console and Analytics Data

Use data to separate technical issues from demand issues. In Google Search Console, filter by country, page, and query. Look for mismatches.

Examples include:

• UK queries triggering US URLs.
• French pages getting impressions in Belgium but not France.
• German pages indexed but receiving almost no impressions.
• Localized URLs ranking for brand terms only.

In analytics, review organic sessions, engagement, conversions, and revenue by landing page and country. A healthy regional setup should show relevant traffic going to relevant pages. If 40% of Canadian traffic lands on US pages, the audit should flag that as a commercial issue, not a minor tag problem.

7. Test Crawling, Indexing, and Rendering

Run crawls by market section. Then test key URLs with live inspection tools. Confirm that pages return 200 status codes, load indexable content, and contain the correct tags.

Pay close attention to JavaScript. Some language switchers render late. Some regional links appear only after a user selects a country. Search engines may miss those paths. Critical links should be available in plain HTML where possible.

Also test redirects from different locations. Forced redirection based on IP can harm crawling and user choice. A search engine visiting from one location may never see other versions. Offer a banner or selector instead of locking users into one region.

8. Prioritize Fixes by Business Impact

Not every issue deserves the same urgency. Rank fixes by traffic, revenue, crawl risk, and effort.

A practical priority order is:

1. Indexing blockers: noindex tags, robots blocks, broken canonicals.
2. Severe hreflang conflicts: missing return tags, wrong regional targets.
3. Architecture problems: poor internal linking, redirect traps, missing sitemaps.
4. Content gaps: weak local copy, missing trust signals, wrong currency.
5. Reporting cleanup: dashboards, annotations, market tracking.

Document each issue with a URL sample, impact estimate, fix owner, and deadline. Serious audits do not end with a long list of complaints. They end with a controlled work plan.

Final Checklist

• Every regional URL has a clear purpose.
• Hreflang tags are valid, reciprocal, and self-referencing.
• Canonical tags match the intended market page.
• Internal links point to the correct language version.
• Regional pages use local terminology, pricing, and trust signals.
• Search Console data confirms the right countries see the right URLs.
• Analytics shows traffic and conversions by market.

A strong international SEO audit reduces confusion for users and search engines. It also protects revenue. When language targeting, hreflang, architecture, and content work together, each market gets a fair chance to rank and convert.