Quick answer
A canonical and noindex can coexist, but it should be deliberate. Decide whether the page should be indexed as a representative, excluded while consolidating signals, or treated as an intentional variant, then make the directives consistent with that policy.
What the issue means
noindex asks search systems not to include the current page. A canonical points to a preferred URL. Combining them can create ambiguity because the page is simultaneously excluded and asked to communicate a preferred representative.
Why it matters for SEO
Conflicting signals can make indexing and consolidation harder to diagnose. The right answer depends on whether the current URL is a public representative, a duplicate, a filter, a search result, or a private route.
How NOTABIS detects it
The canonical-noindex-conflict rule is a page-scoped high-severity finding when a page declares a canonical while also sending a noindex directive. NOTABIS reports the observed combination; it does not assume every combination is wrong.
How to check it yourself
Inspect both the canonical link and meta name="robots" or X-Robots-Tag. Check redirects, page purpose, internal links, sitemap inclusion, and whether the canonical target is indexable.
How to fix it
For a page that should represent itself, remove noindex and retain a suitable canonical. For a page that should not be indexed, remove or reconsider the canonical unless it is part of a documented consolidation strategy. Align templates, headers, sitemaps, and internal links.
When it may be intentional
Search/filter variants, duplicate URLs, private routes, and migration states may intentionally combine signals. Document the reason and verify the canonical target rather than changing a protected page for cosmetic audit results.
Related issues
Review noindex directives, canonical tags, query variants, and canonical redirect conflicts.
Run a NOTABIS audit
Use the finding’s page evidence to compare canonical, robots, status, and URL-variant measurements before changing anything.