Canonical Pointing to a Redirect, Not the Final URL

A canonical tag tells a search engine which URL should hold a page's ranking signals. When that instruction points at a URL that itself redirects, rather than at the page the redirect actually lands on, the engine has to follow an extra hop before it can act on it, and it may choose a different canonical altogether rather than do the work.

What this finding means

Crawl Cove's canonical-to-redirect check looks at every indexable page (HTTP 200, not itself noindex) whose rel="canonical" is a same-origin, absolute URL pointing at another page in the crawl. It flags the source page when that canonical target turns out to be a redirect with a known final destination, and the canonical is not already pointing at that final URL.

A real finding looks like this:

canonical points to "https://example.com/old", which redirects to "https://example.com/new"

This is a narrower, more specific case than Canonical Pointing to a Noindex Page: that check fires when the canonical target is not indexable at all (noindex or a non-200 status). A redirect that resolves to a real final URL is different, it does land somewhere indexable, so it needs its own fix rather than being folded into that broader finding.

Why it matters

Consolidating ranking signals onto a URL that immediately hands them off again adds a hop the search engine has to follow before it can act on the instruction. Google's own guidance is to point a canonical straight at the destination it actually wants indexed; a canonical that lands on a redirect first works against that, and can lead the engine to disregard the signal and choose a canonical of its own on the page instead.

How to fix it

1. Open the source page's canonical tag and find the target URL named in the finding.
2. Follow that URL's redirect to its real final destination. The finding already names it, so this is a lookup, not a fresh crawl.
3. Point the canonical directly at the final URL, not the intermediate redirecting one.
4. Re-crawl the page to confirm the finding clears.

False positives and edge cases

• A canonical that already points at the final destination is never flagged. Once it matches, there is no extra hop left to fix, and the check does not fire.
• A self-referential canonical never fires this check. A page pointing at itself is the normal, correct pattern.
• A canonical pointing at a redirect with no known final destination is not flagged here. That is Canonical Pointing to a Noindex Page's territory instead, since a bare, unresolved redirect reads as a non-200 target.
• Only same-origin, absolute, already-crawled canonical targets are checked. A canonical that is missing, relative, points off-site, or points at a URL the crawl never reached is out of scope for this specific check by design.

Related reading

For the broader case of a canonical pointing at a target that isn't indexable at all, whether that's a noindex directive or a 404, see Canonical Pointing to a Noindex Page. For pages whose body content is near-identical without a canonical tag consolidating them, see Near-Duplicate Content. For a page with no canonical tag at all, or one that isn't a valid absolute URL, see Missing Canonical Tag.