Hreflang Implementation Checklist with Auditite

Overview

Hreflang tags tell search engines which language and regional version of a page to show to users in different locations. Incorrect implementation is one of the most common international SEO errors, leading to wrong language versions appearing in search results. This checklist ensures correct implementation.

Hreflang Tag Syntax

<link rel="alternate" hreflang="en-us" href="https://example.com/page" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/page" />
<link rel="alternate" hreflang="de" href="https://example.com/de/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page" />

Language-Region Code Reference

Code	Language	Region	When to Use
en	English	All regions	One English version for all countries
en-us	English	United States	Separate US English version
en-gb	English	United Kingdom	Separate UK English version
de	German	All regions	One German version
de-at	German	Austria	Separate Austrian German
fr	French	All regions	One French version
fr-ca	French	Canada	Separate Canadian French
es	Spanish	All regions	One Spanish version
es-mx	Spanish	Mexico	Separate Mexican Spanish
ja	Japanese	Japan	Japanese version
zh-cn	Chinese	China	Simplified Chinese
zh-tw	Chinese	Taiwan	Traditional Chinese
x-default	Fallback	All	Default/language selector page

Format rules: Language code is ISO 639-1 (2 letters, lowercase). Region code is ISO 3166-1 Alpha-2 (2 letters, uppercase in standard but lowercase in hreflang). Always use en-us not en-US in hreflang tags.

Page Mapping Worksheet

Page	en-us URL	en-gb URL	de URL	fr URL	es URL	x-default URL
Homepage
About
Product 1
Blog post 1

Implementation Methods

Method	Best For	Pros	Cons
HTML <link> tags	Small to medium sites	Easy to implement	Adds to page size
XML sitemap	Large sites (1000+ pages)	No page size impact	Harder to audit visually
HTTP headers	Non-HTML files (PDFs)	Works for any file type	Requires server config

Recommendation: Use HTML <link> tags for most sites. Switch to XML sitemap method for sites with 10+ language versions or 10,000+ pages.

Implementation Checklist

Tag Configuration

• Every page includes hreflang tags for ALL language versions (including itself)
• Self-referencing hreflang is present (page references its own URL)
• x-default is set for the fallback version
• Language codes follow ISO 639-1 format
• Region codes follow ISO 3166-1 Alpha-2 format (lowercase)
• All URLs are absolute (include protocol and domain)
• All URLs are the canonical version (not redirected URLs)

Bidirectional Confirmation

• If page A references page B, page B also references page A
• All pages in a hreflang set reference all other pages in the set
• No orphan references (referencing a page that doesn’t reference back)

URL Consistency

• Hreflang URLs match canonical URLs exactly
• No trailing slash mismatches between hreflang and canonical
• No protocol mismatches (http vs https)
• No www vs non-www mismatches
• URLs return 200 status (not 301, 302, or 404)

Content Alignment

• Each language version has genuinely translated/localized content
• Pages with hreflang serve content in the declared language
• Currency, dates, and formatting match the target region
• No auto-translated thin content pages

Common Hreflang Errors

Error	Impact	How to Detect	Fix
Missing return tag	Hreflang ignored by Google	Crawl all language versions	Add bidirectional tags
Wrong language code	Wrong version shown in SERPs	Validate codes against ISO	Correct the code
Hreflang on non-canonical URL	Hreflang ignored	Compare with canonical tags	Align hreflang with canonical
Missing self-reference	May be ignored	Check each page references itself	Add self-referencing tag
Missing x-default	No fallback for unsupported regions	Check for x-default presence	Add x-default tag
URL returns redirect	Hreflang ignored	Crawl all hreflang URLs	Point to final destination URL
Conflicting with canonical	Confusion about preferred URL	Compare hreflang and canonical	Ensure consistency

Validation Process

Step	Action	Tool
1	Crawl all language versions of the site	Auditite
2	Extract all hreflang tags from every page	Crawler output
3	Verify bidirectional confirmation	Automated check
4	Verify URL status codes (all must be 200)	Crawler
5	Compare hreflang URLs with canonical tags	Automated check
6	Validate language/region codes	ISO code validator
7	Check x-default presence	Manual or automated
8	Test in Google Search Console International Targeting	GSC

Monitoring

Check	Frequency	Action on Failure
Hreflang errors in GSC	Weekly	Fix within 7 days
New pages have hreflang	On publish	Add to deployment checklist
Return tags still valid	Monthly	Re-crawl all versions
Language versions returning 200	Monthly	Fix broken URLs

Auditite’s technical audit automatically validates hreflang implementation across all language versions of your site, detecting missing return tags, invalid codes, and URL mismatches.