Can a canonical point to a noindex page?
Rubric check: canonical that points to a noindexed page (check id canonical_to_noindex)
It shouldn't. Rubric flags pages whose canonical names another page as the main version when that page is set to noindex. The two signals cancel out, and neither page may end up in search.
Why it matters for SEO
A canonical says "index that page instead of this one". A noindex on that page says "don't index me". Google can end up dropping both, or ignoring the canonical and guessing. Either point the canonical at a page that can be indexed, or remove the noindex from the target.
Does this matter for ChatGPT and AI Overviews?
Yes, in the same way. AI search tools mostly cite pages that are in a search index. If the canonical sends search engines to a page they won't index, the content you wanted found may not be in the index at all.
How Rubric scores it
MajorMajor checks cost twice as much as a standard check when they fail.
Why this tier: The canonical says the main page is elsewhere, and that page says don't index me.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 24 points off. Even one failing page costs at least 12 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 0 of 38 sites where Rubric could judge it (0%). That is 0 of 35 judged sites in Rubric's 313-site test set and 0 of 3 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 1 of 1 times. (Engine build bbcec7c.)
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Open the page in the report and check the canonical in your SEO plugin's Advanced tab (Yoast SEO, Rank Math or All in One SEO).
- Open the target page and check whether it is set to noindex in the same tab.
- Either clear the custom canonical, so the page points to itself, or let the target be indexed.
Shopify
- Shopify sets canonicals for you, so this usually comes from an app or a theme edit.
- Check
theme.liquidand any SEO app for custom canonical or noindex rules (for example noindex added to certain templates). - Remove whichever of the two you didn't mean to set.
Webflow
- Open the page's SEO settings and check its canonical field.
- Open the target page and check its Sitemap indexing toggle (off adds noindex) and any custom code with a robots meta tag.
- Fix whichever is wrong and publish.
Custom code
Point canonicals only at pages that return 200 and can be indexed:
<!-- on /boots?colour=red -->
<link rel="canonical" href="https://example.com/boots">
<!-- and /boots must not carry noindex -->