The noindex + canonical contradiction

The noindex + canonical contradiction

"Add a canonical AND a noindex to be safe."

You just sent two opposing orders.

A canonical says 'this page is a duplicate of that one, consolidate signals there.' A noindex says 'drop this page entirely.' Combine them and Google has to guess which you meant — and the guess is unstable. Worse, if the canonical target eventually inherits the noindex interpretation, you can deindex the page you were trying to keep.

Here's what actually happens: this combo appears constantly on faceted-nav and pagination pages where a plugin adds one rule and a developer adds the other. Nobody owns the conflict, so it ships.

Fix: pick one intent. Want it consolidated and crawlable? Canonical only. Want it gone? Noindex only, and remove the canonical pointing elsewhere. Run a crawler and flag every URL carrying both directives — there are always more than you think. (Belt-and-suspenders works on trousers, not on indexing.)