Skip to content
Raptor home
Menu

Canonical in two places

canonicals.canonical_mismatch
Priority
Note
Severity
Info

What we look for

These pages give a canonical (the preferred address of a page) both in their HTML and in the HTTP Link header (a line the server sends along with the page).

Why it matters

That is valid while the two agree, and then it needs no change. If they ever differ, search engines may ignore both.

How to fix

Keep the canonical in one place, either the page template or the server's Link header, so the two cannot drift apart.

What it cannot know

Raptor keeps only one of the two values, so it cannot tell whether they agree.

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: canonicals.canonical_mismatch
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "canonicals.canonical_mismatch"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=canonicals.canonical_mismatch
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": "canonicals.canonical_mismatch"
}