The symptom
Your page has a canonical tag pointing at itself (or another URL) AND a meta robots noindex. You are telling Google both "index this URL" and "do not index this URL" at once.
Why it happens
- Templates that inject robots noindex for duplicate content but keep the canonical self-reference from the main template.
- A developer added noindex while a page was a draft and it stayed on after launch.
- Plugins that set noindex automatically (for thin content, pagination) while the canonical logic remains enabled.
- A redirect target page carries over both tags from the source page.
Diagnose it — in order
- 1
Look at the Signals category
The URL Debugger explicitly checks "Canonical vs noindex" and reports the conflict as an error with both values shown as evidence — no guessing.
- 2
Check the final URL after redirects
If the page redirects, the canonical/noindex that matters is on the final URL. The debugger shows the redirect chain and the tags on the final response.
- 3
Decide which signal you intend
Do you want the page indexed, or not? The fix depends on intent — you cannot keep both.
How to fix it
- 1
If you want the page indexed: remove noindex
Delete the meta robots noindex (and any X-Robots-Tag: noindex header — the debugger surfaces headers too). Keep the canonical self-reference.
- 2
If the page should not be indexed: remove the canonical
For truly non-indexable pages, prefer noindex plus a working internal link to the canonical alternative. A canonical on a noindex page is contradictory and ignored in conflicting-signal cases.
- 3
Redirect instead of noindex when possible
If a page is a duplicate of another, a 301 redirect is usually cleaner than noindex. The debugger redirect chain report confirms the redirect reaches the right final URL.
- 4
Re-audit and re-request indexing
Re-run the URL Debugger until the conflict check passes, then request indexing for the canonical URL in Search Console.
Free tools that help
Still not sure what your page is sending?
Run your URL through the free URL Debugger — it shows the raw HTML evidence, redirects, headers, and what Googlebot and Facebook each receive.
Debug a URL free