Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Site ops

Hreflang Implementation

Hreflang is an HTML signal that tells search engines which URL version to show for a specific language or region.

Beginner3 min readUpdated 2026-07-27Notes by Callum Bennett

Start here

  • Audit your existing pages for language/region variants before adding tags.
  • Use absolute URLs and ensure every target returns a 200 status.
  • Include self-referencing hreflang tags on every page.
  • Verify reciprocity: all variants must link to all others.
  • Test with Google Search Console's International Targeting report.

What I'd do first

  • Check if your site serves the same content in multiple languages or regions. If yes, hreflang is for you.
  • Pick one implementation method: HTML <link> tags in the <head>, XML sitemaps, or HTTP headers. Stick with it across all pages.
  • For each page, list every language/region variant (including the page itself) using ISO 639-1 language codes and optional ISO 3166-1 Alpha-2 region codes (e.g., en-US, fr-CA).
  • Add an x-default tag for a fallback page when no language/region matches.
  • Verify reciprocity: every URL in the cluster must link back to every other URL. No broken chains.

Plain-English take

Think of hreflang as a signpost for search engines. If you have an English page for the US (en-US) and a French page for Canada (fr-CA), hreflang tells Google: "Show the US version to users in the US, and the Canadian French version to users in Canada." Without it, Google might guess wrong—or treat the pages as duplicates. The tag itself lives in the page's HTML head, like this:

<link rel="alternate" hreflang="en-US" href="https://example.com/us/" />
<link rel="alternate" hreflang="fr-CA" href="https://example.com/ca-fr/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Every variant must include tags for all others, including itself. No shortcuts.

When it actually matters

  • Same content, different languages: A product page translated into Spanish, French, and German.
  • Same language, different regions: A blog in English for the US, UK, and Australia with region-specific spelling or currency.
  • Near-identical content: Landing pages that differ only by country (e.g., /uk/ and /us/).
  • After a site migration: If you restructure URLs or add new language versions, hreflang prevents temporary ranking drops.

It doesn't matter if you have only one language or one region. Skip it if your site is purely local.

What I got wrong

  • Missing reciprocal links: I once had a cluster where page A linked to B and C, but B only linked to A. Google ignored the whole set. Every page must link to every other page.
  • Forgetting self-referencing tags: Each page needs a tag pointing to itself. It feels redundant, but Google requires it.
  • Using relative URLs: Hreflang URLs must be absolute (full https:// path). Relative URLs break the signal.
  • Pointing to redirects or 404s: If the target URL redirects or returns a 404, the hreflang annotation is useless. Always verify the target returns a 200.
  • Mixing implementation methods: Using HTML tags on some pages and XML sitemaps on others can cause inconsistencies. Pick one method and apply it everywhere.

Next step

SchemaAfter hreflang, learn how structured data can further clarify your page's content for search engines.

Quick answers

Do I need hreflang if my site uses subdirectories for each language?

Yes. Even with clear URL structures, hreflang explicitly tells Google which version to serve, reducing the chance of wrong-language results.

Can I use hreflang with JavaScript-rendered content?

Yes, but Google must be able to render the page. Use server-side rendering or dynamic rendering to ensure the tags are visible in the initial HTML.

Where to go next

More from Site ops

A step sideways

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

Notes from Callum Bennett.