International SEO Audit (2026): Hreflang, Canonicals, and a Free Checklist
Short answer: An international SEO audit checks whether each language or country version can be crawled, indexed, canonicalized, and matched to the right searcher. Start with representative URLs, then verify status codes, self-referencing canonicals, reciprocal hreflang, lang attributes, localized content, internal links, and sitemap coverage.
International SEO Audit (2026): Hreflang, Canonicals, and a Free Checklist
Run the free international SEO audit tool while you work. Paste the rendered HTML from one localized page and it will flag missing hreflang, self-reference, x-default, language, and canonical signals. It is a fast first pass; it does not replace a crawl of every locale.
Updated September 10, 2026 · By Seobase · 9 min read
Use Google’s localized-versions guidance for hreflang, its canonical documentation for duplicate URL signals, and its sitemap documentation for discovery. The checklist below turns those requirements into a repeatable review.
What an international SEO audit should prove
A translated or regional page is only useful when search engines can fetch it, understand its language and audience, and select it for the right searcher. An audit should answer five practical questions:
- Does the final URL return a crawlable
200response? - Does the page identify itself as the preferred URL for that locale?
- Does it list every relevant alternate, including itself?
- Do the alternates return the same relationship back?
- Are the content, links, sitemap, and measurement signals actually localized?
Hreflang is a signal, not a ranking guarantee. Google can still choose a different URL when pages are unavailable, poorly localized, redirected, canonicalized elsewhere, or otherwise unsuitable. Treat the audit as a way to remove contradictory signals, not as a promise of international rankings.
Free international SEO audit checklist
1. Test the final URL and response
Choose one representative URL for each important language or country version. Follow redirects and inspect the final response. The page should be publicly fetchable, return 200 OK, and not depend on a cookie, IP redirect, login, or JavaScript-only navigation to reveal the locale.
Record the final URL, response code, canonical URL, detected language, and last crawl date. Repeat this for a sample of product, category, article, and homepage templates; checking only the homepage can hide a template-wide mistake.
2. Check the canonical URL
Each substantially equivalent locale should normally have a self-referencing canonical:
<link rel="canonical" href="https://example.com/fr/produit/">A French page that canonicals to the English page tells search engines that the French URL is not the preferred version. That can remove the very regional page you want considered. Keep the canonical on the final, indexable URL and check for conflicts between HTML, HTTP headers, redirects, and your sitemap.
Canonicalization and hreflang solve different problems: canonical selects the preferred URL for one page, while hreflang describes equivalent alternatives for different languages or regions. Do not use a canonical from every locale to the default language as a shortcut.
3. Verify a complete, reciprocal hreflang set
Every page in a set should reference itself and its alternates. For example:
<link rel="alternate" hreflang="en-us" href="https://example.com/">
<link rel="alternate" hreflang="fr-fr" href="https://example.com/fr/">
<link rel="alternate" hreflang="x-default" href="https://example.com/">The French page should emit the same set, not only a link back to the English page. Missing return links are one of the most common reasons a set appears correct in one source file but has no effect. Use lowercase language and region values consistently, and never reverse the order: en-GB, not GB-en.
You can place the relationship in HTML, an XML sitemap, or HTTP headers for non-HTML files. Choose the method that matches how your site is maintained and keep it consistent. The free hreflang tag generator can produce the full HTML or sitemap set after you have decided which URLs belong together.
4. Check language and actual localization
The root lang attribute helps describe the document, but it is not a substitute for translated content:
<html lang="fr-FR">Review the visible title, headings, navigation, structured data, currency, units, shipping information, and support details. A page with French tags around English copy is not a useful French result. Do not create country pages that differ only by a city or currency token; give each version a genuine audience reason to exist.
5. Inspect internal links and navigation
Localized pages should link to the right localized products, categories, articles, and navigation. Avoid forcing every locale through the English navigation or using automatic language redirects that prevent crawlers and users from choosing a different version. Add a visible language selector when it helps users, and make each option a normal crawlable link.
6. Validate sitemap and indexability signals
Include final, canonical, indexable URLs in the XML sitemap. Remove redirects, blocked URLs, duplicates, and noindex pages from the set. Check that robots.txt does not block the localized paths and that the sitemap itself is submitted in Search Console. A sitemap cannot make a blocked or noncanonical page rank, but it makes the intended URL set easier to discover and audit.
7. Compare performance by country and device
After fixing markup, segment Search Console by country, page, query, and device. Look for impressions landing on the wrong locale, a country with no impressions despite a valid page, or a sudden drop isolated to one template. Keep a baseline before changes and review again after Google has had time to recrawl the set.
Common international SEO failures
| Failure | Why it hurts | What to change |
|---|---|---|
| Every locale canonicalizes to English | The regional URLs may be treated as duplicates | Use a self-referencing canonical on each indexable locale |
| Only the default page lists hreflang | The relationship is not reciprocal | Emit the complete set on every page |
| Redirect by IP or browser language | Crawlers and users may never reach the intended URL | Keep stable URLs and offer a selectable language path |
| Country pages contain unchanged copy | There is little localized value to rank | Localize the offer, facts, terminology, and customer context |
| Hreflang points to redirects or 404s | Search engines cannot use a broken alternate | Point to final URLs returning 200 |
| Sitemap includes noncanonical variants | It sends mixed URL instructions | List only final canonical URLs |
How to use the free audit tool
- Open the international SEO audit tool.
- Paste the rendered
<html>and<head>markup from one locale. Add the page URL if you want the result compared with the canonical. - Review missing self-reference, x-default, alternate links, language, and canonical mismatches.
- Fix the template, then repeat the check on another locale and confirm the reciprocal set.
- Use a crawler and Search Console to validate response codes, redirects, coverage, and country performance across the whole site.
The browser audit intentionally checks the markup you provide. It does not fetch every alternate, prove reciprocal return links, verify redirects, or tell you which canonical Google selected. Those limitations are useful boundaries: use the tool for a quick markup review, then use a crawl and Search Console for site-wide evidence.
International SEO audit FAQ
What is an international SEO audit?
It is a review of the technical, content, and measurement signals that help search engines serve the right URL to users in different languages or regions. It commonly covers crawlability, canonicals, hreflang, language, localization, internal links, sitemaps, and country-level performance.
Do I need hreflang for every international site?
Hreflang is useful when substantially similar pages target different languages or regions. It is not a replacement for translated content, self-referencing canonicals, correct redirects, or pages that return 200 and can be indexed.
Should every localized page have a self-referencing canonical?
Usually, yes. Each locale should point its canonical at its own final URL, then use hreflang to describe the alternate set. Confirm the rule against your actual duplication and indexing strategy before changing a large site.
Is the international SEO audit tool a full crawler?
No. It checks one pasted page’s rendered markup in the browser. Use a crawler, server logs, and Search Console to verify all locales, redirects, reciprocal links, and selected canonicals.
What should I fix first?
Fix inaccessible or redirected URLs first, then canonical conflicts, incomplete reciprocal hreflang, and missing localized content. Recheck the template before scaling the fix to every locale.
Next step
Run one representative page through the free international SEO audit, repair the highest-impact template issue, and record the affected URLs. If the site publishes localized content regularly, Seobase can help turn the same research, briefing, linking, and publishing workflow into a repeatable content process—but keep the technical audit and human review in the loop.
Put this on autopilot
Seobase runs the whole loop for you: it finds the keywords worth ranking for, writes and publishes the articles, and reports back from Search Console on what actually moved.
See how Seobase works