Quick answer
The canonical URL and the final URL after redirects should normally agree. NOTABIS reports canonical-redirect-conflict when the first measured canonical resolves to a different URL from the response’s final URL. Fix accidental disagreement by linking and canonicalising to the same final address, while keeping intentional variants documented.
What the issue means
Suppose /old-guide redirects to /guides/tyre-storage, but its HTML declares:
<link rel="canonical" href="https://example.com/old-guide">
The requested URL, final URL, and canonical now tell different parts of the story. A redirect is a server response; a canonical is a hint in the HTML of the response that was fetched.
Why it matters for SEO
Conflicting URL signals make it harder for search engines to choose and consolidate the preferred representative. Google may follow the redirect or choose another canonical based on content, links, and other signals. This is a consistency problem, not a guaranteed penalty, and a deliberate query-variant strategy may be correct.
How NOTABIS detects it
The canonical-redirect-conflict rule resolves the first canonical against the requested page URL and compares it with the final_url recorded after permitted redirects. It records a page-level issue when the values differ. It does not decide whether the redirect or canonical is the intended signal, or whether the target is reachable and equivalent.
How to check it yourself
Request the URL with and without redirect following:
curl -sS -D - -o /dev/null https://example.com/old-guide
curl -sS -L -D - -o /dev/null https://example.com/old-guide
Inspect the final HTML’s canonical, the redirect chain, and the target’s status and content. Check trailing slashes, HTTP/HTTPS, host variants, query parameters, and locale routing.
How to fix it
For a moved page, redirect directly to the final URL and emit a self-consistent canonical on the destination. Update internal links and sitemaps to the final address. For a query or filter variant, decide whether the variant should be indexable; if not, use a deliberate canonical and indexability policy rather than letting redirects and templates disagree.
Recheck both the response headers and final body after deployment, then allow search engines time to recrawl the signal.
When this is intentional or does not need fixing
The audit classifies some query variants whose canonical points to a clean page as intentional. A migration can also use a redirect from an old address while the destination has its own self-canonical. Do not remove a valid redirect merely to make the values match on the old response; make the destination and link graph clear instead.
Related issues
Compare redirected URLs, redirect chains, canonical URLs present, and canonical and noindex conflicts.
Run a NOTABIS audit
NOTABIS records the requested URL, final URL, and canonical value so you can identify which signal needs to change.