Quick answer
Use a canonical to identify a preferred URL among duplicates; use noindex when the current URL should stay out of search results. Google advises against using noindex as a way to choose a canonical, because the directives express different goals. See Google’s canonical guidance.
What the issue means
noindex asks a crawler that can access the page not to include that URL in search results. A canonical is a hint about which duplicate URL should represent a group. A page excluded with noindex is not thereby consolidating its signals into the canonical target.
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
If one URL should represent a duplicate set, keep the duplicate pages crawlable and use consistent canonical signals; do not add noindex just to force that choice. If a URL should be excluded for another reason, use noindex and verify it is crawlable so search systems can see the directive. Align templates, headers, sitemaps, and internal links with the intended outcome.
For example, a tracking-parameter version of an indexable product page can point to the clean URL without a noindex directive:
<link rel="canonical" href="https://example.com/products/blue-shoe">
A private account page should instead rely on authentication and may also send noindex; its canonical does not make private content safe or consolidate it into another page.
When this is intentional or does not need fixing
Some applications emit both directives for independent reasons, but this is not a reliable canonicalisation strategy. Private content needs access control regardless of indexing directives; search and filter variants need a deliberate URL policy. Document the reason and verify the canonical target rather than changing a protected page to clear an audit finding.
Related issues
Review noindex directives, missing canonical URLs, and query variants together.
Run a NOTABIS audit
Use the finding’s page evidence to compare canonical, robots, status, and URL-variant measurements before changing anything.