Skip to content
Raptor home
Menu

Hreflang to a non-200 page

hreflang.non_200_urls
Priority
Medium
Severity
Warning

What we look for

The hreflang tags (lines in <head> listing the page's versions in other languages) on these pages point to a crawled page whose status code (the server's three-digit reply) is not 200 OK, such as a 404 error.

Why it matters

Search engines expect every listed version to load normally, and may ignore a language group that points at a missing or failing page.

How to fix

Point each hreflang tag at the working address of that language version, in the page template or the plugin that writes the tags, or remove versions that no longer exist.

What it cannot know

Raptor checks only versions this crawl fetched, and matches addresses as written, so a version reached through a redirect is not checked.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: hreflang.non_200_urls
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "hreflang.non_200_urls"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=hreflang.non_200_urls
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "hreflang.non_200_urls"
}