Hreflang changed: your declared languages are no longer the same

In brief

An hreflang changed alert flags that the list of languages declared in your tags changed — normal if you added or removed a language, worth fixing if it was accidental. Compare the new list against your strategy and validate the change.

WarningP1 — Direct ranking

What is it?

The languages declared in the hreflang tags changed.

Why it hurts SEO and AI

Normal if you are adding/removing a language. If accidental, it can derail the targeting of an entire market. The change needs to be seen and validated.

When it is NOT a problem

  • You just deliberately added or removed a language and the change reflects that decision.
  • You fixed a malformed language code (e.g. en-us to en-US) and the list is now valid.
  • A test or staging version was removed from the annotations, which is the intended effect.
Before
<link rel="alternate" hreflang="fr" href="..." />
<link rel="alternate" hreflang="en" href="..." />
<link rel="alternate" hreflang="de" href="..." />
After
<link rel="alternate" hreflang="fr" href="..." />
<link rel="alternate" hreflang="en" href="..." />

The German version dropped off the list: intended if you are closing that market, accidental if it should have stayed.

How to fix it

  1. Get the list of declared languages before and after the change.
  2. Confirm it matches a product decision (language added or removed).
  3. If it is accidental, restore the expected list in the template or generator.
  4. Check the reciprocity of the annotations across all affected versions.

This scan checks technical compliance: viewport, charset, HTTPS, hreflang

Is this issue on your site?

Did your hreflang language list shift without you knowing? Enter a URL: Seogard tracks your language annotations and flags any change to validate. Free, no credit card.

By clicking Scan, I certify that I own this site or have permission to crawl it.

  • No credit card
  • Result in ~30 s

What you get back

International targeting stays under explicit control.

Seogard catches this regression automatically — through its continuous SEO monitoring.

Frequently asked questions

Is an hreflang change always a problem?

No: adding or removing a language changes the list legitimately. The risk only exists if the change is accidental and derails the targeting of a market.

How do I know if the change was intentional?

Compare the new language list against your roadmap: if a language disappeared with no matching decision, it is probably a template or deploy bug.

Related rules

Page redirectedA page still declared in your sitemap has started redirecting to another URL: the sitemap presents an address that bounces as canonical. Intentional removal — take it out of the sitemap; otherwise, often a broken route. A page that is redirected AND removed from the sitemap is a clean removal: no alert. JavaScript redirectThe page responds 200 but its JavaScript redirects the browser elsewhere. Google only follows it after rendering (delayed, or never if rendering fails) and AI systems read the original HTML, not the destination: machines and humans see two different pages. Broken redirectA cleanly removed page (redirect + removed from the sitemap) now returns a 4xx error: its redirect broke. Link equity from backlinks pointing to the old URL is no longer passed — typically a refactor that deleted the redirect rule or its target.

Updated July 10, 2026