What Do Hreflang Mistakes Look Like on a Webflow Site?

How do you know if your Webflow site has hreflang mistakes?

You usually find out from the wrong visitors, not an error message. A buyer in Germany lands on your English page, or Google shows your Spanish page to English searchers. Hreflang mistakes rarely break a page. They quietly confuse which version Google shows to whom, so you have to audit for them on purpose.

Hreflang is the annotation that tells Google which pages are language or regional versions of each other. On a localized Webflow site, it is what connects your English pricing page to your German and French pricing pages, so each searcher sees the right one.

I have written before about when a Webflow site needs hreflang at all and how to set the tags up. This piece is the audit version. It covers what goes wrong after launch and how to spot it.

What is hreflang supposed to do?

Hreflang helps Google send each searcher to the right language or regional version of a page. Google's documentation describes the purpose as helping Google Search point users to the most appropriate version of your page by language or region. It is a routing signal between versions, not a ranking boost for any single page.

That distinction matters when you audit. If your localized pages are not ranking, hreflang is rarely the cause on its own. Content quality, links, and relevance still drive rankings. Hreflang only decides which of your versions shows up once Google has decided your site deserves to appear.

So the symptom of a hreflang problem is almost always mismatch. The right page exists and ranks, but searchers in the wrong market see it, or searchers in the right market see a different version.

Why are missing return links the most common mistake?

Because hreflang only works when pages confirm each other. Google's documentation says each language version must list itself as well as all other language versions, and that if two pages do not both point to each other, the tags will be ignored. One missing link in the set can make Google discard the annotation between those pages.

This breaks easily on sites that grow over time. Someone adds a French version of a landing page but not a German one. A localized page gets unpublished while the others still point to it. A CMS item exists in one locale but has been turned off in another. Each case leaves a one-way reference.

The check is mechanical. For each page in a set, list the hreflang URLs it declares. Then open each of those URLs and confirm it declares the same set, including itself. Any page that is missing from another page's list is a broken pair.

What goes wrong with language and region codes?

Codes in the wrong format get ignored. Google's documentation says only language codes from ISO 639-1 and region codes from ISO 3166-1 Alpha 2 are supported, and that you cannot specify a country code by itself. Region codes reserved for other purposes are also ignored, so a small typo can quietly cancel the signal.

The classic errors are easy to make. Using a country code alone, such as a bare region code with no language. Using the wrong code for a language, such as a country code where a language code belongs. Mixing up the order of language and region. Each of these looks reasonable to a human and means nothing to Google.

When I audit, I export every hreflang value on the site into a spreadsheet and check each one against the standard lists. It takes minutes and catches mistakes that have often sat unnoticed since launch.

When should you use x-default?

Use x-default for the page you want people to see when no language or region matches. Google's documentation describes the reserved x-default value as the one used when no other language or region matches the user's browser setting. For most B2B sites, that is the main English page or a language selector page.

The mistake is leaving it out entirely or pointing it at the wrong page. If your site targets English, German, and French speakers, a visitor whose browser is set to Japanese still needs somewhere to land. Without x-default, you leave that choice to Google.

I also check that x-default is consistent across the set. Every page in a group should point to the same x-default URL. If the English page names one fallback and the German page names another, the set is inconsistent.

How does hreflang clash with canonical tags?

Hreflang and canonical tags should agree. Each localized page should usually have a canonical pointing to itself, and its hreflang tags should point to the canonical URLs of the other versions. If a hreflang tag points to a URL that redirects or that names a different page as canonical, you are sending Google mixed signals.

This clash is common on localized CMS collections. A collection page in one locale has its canonical pointing back to the primary locale, while its hreflang says it is a separate version. Google has to guess which signal you meant.

If your site has a large CMS, audit canonicals and hreflang together. My guide to auditing canonical tags on a Webflow CMS collection covers the canonical side. Run both checks on the same export so you can see conflicts side by side.

What should you check if you use Webflow Localization?

Check where your hreflang tags actually come from. On a localized Webflow site, hreflang can appear in the page head, in the sitemap, or both, depending on your settings and any custom code. Confirm which source is active, make sure there is only one set of rules, and read Webflow's localized SEO documentation for the current options.

A common risk on Webflow is duplication. A team adds hreflang through custom code in the page head while Webflow is also generating it, and the two sets disagree. Google then sees two different versions of the truth on the same page.

Also check locales that are not published. If a locale is switched off but other pages still list it in hreflang, you have created a return link that cannot be confirmed. Every locale in your hreflang set should be live, indexable, and pointing back.

How do you audit hreflang on a Webflow site step by step?

Crawl the site with a tool that reports hreflang, such as Screaming Frog or Sitebulb. Export every page with its hreflang values and canonical. Check return links, code formats, x-default consistency, and canonical agreement. Then spot-check the live sitemap and a few page heads by hand to confirm what the crawler saw.

Start with your money pages. Pricing, demo request, and top product pages matter far more than old blog posts. If those are correct in every locale, you have protected most of the value. Then work outward to the rest of the site.

Use Google Search Console as a reality check. Look at which countries and queries each localized section receives impressions from. If your German pages get most of their impressions from searchers outside Germany or Austria, something in the routing is likely off.

How often should you rerun the audit?

Rerun it after any change to locales, URL structure, or templates, and on a fixed schedule otherwise. I suggest a quarterly check for most B2B sites. Hreflang breaks through ordinary site changes, such as new pages, renamed slugs, and unpublished locales, so a one-time audit at launch is not enough.

Add hreflang to your publishing checklist. Any time someone launches a new localized page, they should confirm it is listed in every other version of that page and that every other version lists it. That one habit prevents most return link errors.

Keep the export from each audit. Comparing this quarter's hreflang map to last quarter's shows you exactly what changed and when, which makes problems far easier to trace.

What should you do next?

Run a crawl this week and export hreflang and canonical data for your most important pages. Fix missing return links first, then code format errors, then x-default and canonical conflicts. Confirm whether Webflow or custom code generates your tags and remove any duplicates. Then add a hreflang check to your publishing routine.

Hreflang is not glamorous, but on a site that sells into several markets, it decides whether buyers see your offer in their own language. That is worth an afternoon of careful checking.

If you want help auditing a localized Webflow site or cleaning up hreflang and canonicals across a large CMS, reach out. I am happy to take a look.