What we look for
In their hreflang tags (lines in <head> listing a page's versions in other languages), these pages label a crawled version with one language code while that version labels itself with another.
Why it matters
Search engines cannot resolve a group whose pages contradict each other, and may ignore the language tags for all of them.
How to fix
Use the same code for each version on every page of the group, in the page template or the plugin that writes the tags.
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 crawlprints the id under it.Check: hreflang.
conflicting_ lang_ declarations - 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. conflicting_ lang_ declarations" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= hreflang. conflicting_ lang_ declarations - MCP
raptor_findingswith thischeck_idreturns 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. conflicting_ lang_ declarations" }