The Complete hreflang Guide for HubSpot Content Hub

Hreflang is the most mistyped tag in technical SEO — and on HubSpot, half the work is knowing what the platform already does for you. Here's the full picture.

What HubSpot does automatically

When you create a page's language variant through HubSpot's multi-language tools (and the pages are linked in one language group), HubSpot renders the full reciprocal hreflang set in each variant's head. For a site structured as language folders on one domain — the common case — you mostly need to verify, not build: view source on a few pages and confirm every variant lists all its siblings.

When you need manual hreflang

HubSpot's automation stops at its own language groups. You need manual tags when versions live on separate domains (yoursite.com + yoursite.de), when translations exist but were never linked as variants, or when a regional version lives outside HubSpot entirely. Add the tags via the page's head HTML or your template, listing every version including the page itself:

The five mistakes that break hreflang

• Missing reciprocity — if the German page points to the English one but not vice versa, search engines ignore both annotations.
• Wrong codes — language is ISO 639-1, region is ISO 3166-1: en-gb ✓, en-uk ✗; sv is Swedish, se is the region code for Sweden.
• No x-default — unmatched searchers get a guessed version.
• Pointing at redirected URLs — every hreflang target must return 200, not bounce through a redirect.
• Annotating non-equivalent pages — hreflang links translations/regional versions of the same content, not your German homepage to your English pricing page.

Verifying it works

View source for spot checks; Google Search Console's international targeting reports and any crawler (Screaming Frog's hreflang report is the standard) for systematic ones. Expect weeks, not days, before search results visibly re-sort by market — hreflang is processed as pages are recrawled.