Canonical points to a noindex page
Pointing a canonical at a noindex URL tells Google two contradictory things at once. Pick one direction and remove the conflict.
Page A declares a canonical pointing at Page B. Page B then returns a noindex directive (meta robots noindex or X-Robots-Tag: noindex). The canonical asks Google to consolidate Page A's signals onto Page B, but the noindex tells Google to drop Page B from the index entirely. The two pages effectively cancel each other out.
Canonical consolidation is how Google decides which URL represents a group of duplicates. If the canonical target cannot be indexed, Google may ignore your canonical and pick a different URL, drop the whole cluster from the index, or keep re-evaluating the conflict on every crawl. Either outcome is worse than a clean self-referencing canonical on an indexable URL.
- Templates canonicalize filtered/faceted URLs back to a category page that was noindex for staging reasons.
- Paginated lists canonicalize to a "view all" page that is marked noindex.
- A migration changed canonical URLs to a redesigned section that is still noindex during rollout.
- An X-Robots-Tag noindex header on the canonical target is added by a CDN without the app team knowing.
- Canonicals point at author or tag archives that the CMS treats as noindex by default.
- Open Canonical Checker and run Page A (the page with the canonical).
- Note the resolved canonical target URL.
- Run the target URL through the Noindex Checker.
- If Noindex Checker shows noindex via HTML, header, or both, this is the conflict.
- Walk any redirect chain on the canonical target, since noindex can appear only on the final hop.
- 1
Decide which direction you want
Either the canonical target should be indexable, or the original page should not canonicalize there. Pick the target that you want ranking and keep it indexable.
- 2
Remove the noindex from the canonical target
If the target is supposed to be the indexed version, remove any meta robots noindex on the page and any X-Robots-Tag: noindex header on the response.
- 3
Point the canonical elsewhere
If the target genuinely should stay out of the index, canonicalize to a different URL that is indexable, or use a self-referencing canonical on the original page.
- 4
Avoid canonicalizing to noindex category pages
Category, author, tag, and filter pages are common noindex targets. Do not canonicalize deep content to those pages, they cannot carry the signals.
- 5
Re-check both pages
After changes, re-run Canonical Checker on the original page and Noindex Checker on the target. The conflict should be gone before you ask Google to recrawl.
Which wins, canonical or noindex?
Neither cleanly. noindex is a strong directive on the page it applies to, so Google will try to drop it from the index. That breaks the purpose of the canonical. In practice Google often ignores the canonical or keeps both pages in an inconsistent state.
Should canonical target be indexable?
Yes. A canonical target should return 200, be crawlable, not be noindex, and ideally self-reference. That is the only configuration where signal consolidation works as intended.
How do I test both pages?
Run Canonical Checker on the source page to get the target, then run Noindex Checker on that target. If either tool shows a problem, the canonical chain is broken.
Ready to diagnose your URL?
Canonical Checker runs the exact checks discussed above.