How to run a hreflang audit on a multilingual site
Run a hreflang audit to find broken language links, verify matching pages and canonical URLs, and prepare exact fixes for each group of translations.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a hreflang audit is
A hreflang audit checks whether a site correctly identifies equivalent pages for different languages or regions. Hreflang is a label on an alternate link that tells a search engine which audience the target serves. An English pricing page and its French counterpart form a group if they serve the same purpose. Each page should point to the appropriate versions in that group. The audit verifies both the links and the pages they connect, then gives you specific changes to make where they disagree.
For international SEO, a group of language versions is the unit of work. A page can contain valid tags while pointing to a page that redirects, has the wrong canonical URL, or explains a different product. A canonical URL is the address a page declares as its preferred version. Read the content and inspect the preferred address alongside the language links. Keep a record of what you could verify and which groups still need inspection so a clean result for the pages you checked has a clear scope.
What it does for the business
- Keep buyers on a page that serves their marketUse the audit to repair links between pages that have the right offers, prices, and vocabulary for their audience. If a switcher sends visitors from a product page to a general home page, a direct link to the equivalent product can preserve their place in the buying journey.
- Fix a shared template onceUse repeated faults across page types to decide where to investigate the source. When a common template emits the same wrong URL pattern, a developer can repair the generator and verify the affected groups in one release.
- Give localization work a concrete briefTurn missing equivalents and untranslated blocks into assignments with named source pages. The team can then weigh the value of each translation against the cost of maintaining it.
- Make a site migration easier to verifyGive the release team a list of complete groups to check once addresses change. They can see which old paths still appear in language links and which new paths lack a return link before closing the migration.
Hreflang audit, step by step
Find the translation groups and capture their pages
Start with the reader task that every member of a translation group should serve.
What to do
- Find the language sitemaps and inspect the home page switcher. Collect examples from your main offer, pricing, and listing pages as well as articles published at different times. Record whether the sitemaps themselves declare alternate links.
- Use a translation registry or supplied map if you have one. Verify doubtful matches by reading the pages. Similar paths are a clue. Read the offers to establish whether the pair belongs together.
- Set a page allowance and finish whole groups within it. Start with the largest groups, then reserve time for pages that declare no alternates and listings in different languages. Mark any group you cannot finish as partial.
- Capture the requested and final addresses, response status, indexing directives, canonical URL, and language declarations. Record all alternates from the HTML, response headers, and applicable sitemap entries, together with the heading, opening text, and switcher targets.
Why
A list of language codes from a single page gives you only that page's account of the group. If a template leaves a locale out on some pages, a crawl that follows those links alone may miss it. Using several entry points gives you a way to find omitted translations. Save the raw declarations and content so a reviewer can reproduce the finding.
Check reciprocal links and eligible targets
A return link only helps when it connects the right addresses.
What to do
- Make a table with one row per member. Compare the declared targets across rows. Check self-referencing hreflang and reciprocal links. If the English version lists the French version, the French version should list the English version in return.
- Check that each intended language or language-region has one destination. Use a language code such as en and add a region where it matters, as in en-GB. Verify that x-default, if used, goes to the intended fallback for visitors whose locale has no match.
- Open each target at the address given in the declaration. Confirm it returns a successful response directly, is eligible for indexing, and declares the intended preferred address. Trace any redirect to see whether the final page is a valid alternate.
- Compare the declarations wherever the site publishes them. If the HTML and sitemap list different URLs for a locale, record both values and the source of each so the owner can reconcile them.
Why
Many hreflang errors only show up across pages. One member may still link to an old address after a migration, while the replacement omits the return link. A cross-language canonical can also send conflicting signals about which page should be indexed. Keeping the declared and observed addresses side by side shows whether the repair belongs in the alternate tags, the canonical, or both.
Read the pages and follow the switcher
A correct locale code can still point to the wrong page.
What to do
- Read the title, main heading, section headings, and opening of each version. Compare what a visitor can learn or do. Two versions of an offer can differ in currency and examples while still answering the same buying question.
- Compare the declared language with the visible language. Look beyond the main article at calls to action, form instructions, and listing cards. A translated category heading can still sit above a list of articles in the wrong language.
- Follow the language switcher from an inner page such as a guide or pricing page. Record the destination and any redirects. Check whether unrelated parameters or a return to the home page interrupt the user's task.
- Compare each suspect region label with the market the page serves. Check whether a suitable alternate already exists elsewhere in the sitemap or registry before proposing a change to the group.
Why
A mechanically complete set can pair a broad buying guide with a narrowly targeted article. Visitors who switch languages then lose the answer they came for. Page content, the switcher and the sitemap give you independent evidence of what the site treats as an equivalent. If you cannot inspect the destination, keep the finding open until you can check what it serves.
Write an exact repair for each conflict
Give the implementer enough detail to change every affected declaration in one release.
What to do
- State the current link, the intended link and the evidence that supports the replacement. For a missing return link, show the corrected set on the affected page. For a wrong canonical, name the page that should declare itself preferred and explain why.
- If the problem repeats, trace the declarations to the shared source if you can read it. Check the translation records and the template that turns them into alternate links. A wrong registry entry may affect multiple output locations.
- Keep each recommendation as small as the evidence allows. If a label points to an unrelated article and there is no verified equivalent, remove that assignment wherever it appears and record the content gap for the localization team.
- Review each proposed block as a group. Check that the replacement addresses are direct and appropriate, and that their resulting lists match. Add priority and confidence so the team can start with the fixes that affect the most important pages.
Why
Telling someone to fix missing return tags leaves them to reconstruct the group. Exact old and new declarations give them a change they can check. Reviewing the full group before release also catches repairs that resolve a faulty link on one page while leaving an old link on another.
Verify the repairs and report the audit coverage
Close a language-link repair after reading the full group again.
What to do
- Reopen the pages behind each finding and confirm the recorded evidence. Ask a second reader to check the proposed blocks against the observed group and make sure each destination still serves the intended audience.
- After an authorized change, retest using the same entry points. Confirm the status, canonical and alternates on every member, then follow the switcher in both directions. If the fix is in a shared template, include another group that uses it.
- Report which groups were checked completely, which were partial, and which were outside the sample. List any unavailable pages, state whether the evidence was live or saved, and record the next test that would settle open findings.
Why
A shared change can fix the tested cluster and introduce a fault in another. Use the same checks on the neighboring group to catch that. Stating the boundaries also lets a client assign further audit time where the result is still unknown.
Common mistakes
- Grouping pages by slug aloneRead the pages or consult a translation map before connecting them.
- Checking only the English source pageOpen every member to confirm it lists itself and returns the links.
- Leaving URLs that redirect in the alternate listsUpdate the declarations to the intended direct URLs after checking the final pages.
- Using the home page as a substitute for a missing translationLeave the locale entry out until an equivalent exists.
- Calling an unread target brokenRecord what prevented the check and keep the target's status open.
What a good result looks like
- Each complete group has a verified set of equivalent pages.
- Every fault names the affected page, the evidence, and the exact proposed change.
- Alternates, canonicals, switcher destinations, and sitemap entries agree where inspected.
- Each proposed tag block preserves valid language versions and identifies the intended fallback where used.
- The audit lists partial and unchecked groups and gives a retest for each repair.
And then what? Using the result
- Give the developer the highest-priority group repairs with the affected source files or paste-ready links.
- Assign untranslated blocks and missing equivalents to the localization owner, with the corresponding source pages.
- Add the repaired groups to the migration or release checklist and check them at their public addresses after release.
- Use the list of groups still open to scope the next audit pass.
When to run it
- A new locale is about to launchCheck that the new pages and the existing versions know about each other before you add the locale to public navigation.
- A platform migration moves URLsCompare old alternate targets, canonicals and switcher links with the new addresses, then retest the complete groups after the move.
- Visitors land on the wrong regional offeringInspect the pages serving the affected product first and check whether their links point to the intended market versions.
- A site has several teams publishing translationsSample groups across templates to see where translation records, editorial practices and generated tags have diverged.
Questions people ask
What does a hreflang audit check?
A hreflang audit checks whether equivalent language or regional pages use valid, reciprocal alternate links to eligible URLs. It also checks what those pages actually say and where the sitemap and language switcher send readers.
Does every page need self-referencing hreflang?
Each page in a hreflang group should list its own language version along with the other members. An English and French pair should carry both labels on both pages.
Is x-default required for hreflang?
No, x-default is optional and identifies a fallback for users whose language or region has no match. A language selector can serve that role if it gives those users a useful next page.
Can hreflang point to a redirected URL?
Use the direct, indexable address of the intended alternate in the hreflang entry. When an old address redirects, check what the final page contains before replacing that address across the group.
What if a translation is missing?
Leave the missing version out of the group until a real equivalent exists. If a translation is already published and omitted from the links, check its language, content and canonical before connecting it.
Can you audit a site from saved pages?
Yes, saved pages can support findings about the declarations and content they contain. Record the capture date and verify live status or redirects separately when those checks matter to the repair.
More jobs in SEO agencies
Hreflang audit, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac