When the HTML tag and the HTTP header disagree, Google applies the most restrictive instruction. So a permissive meta tag does not save a page if the header says noindex. HTML and header directives disagree. Google applies the most restrictive, so an unintended noindex/nosnippet can win.
Why does meta robots and x-robots-tag conflict matter for AI search?
Google applies the most restrictive, so an unintended noindex/nosnippet can win.
How do you fix it?
Reconcile the two sources to a single intended directive.
How do you find it on your site?
- Read both the meta robots tag in the HTML and the X-Robots-Tag header with curl -I.
- Write down each directive side by side.
- Remember the most restrictive directive wins, not the one you prefer.
- Make the two agree, and set the intended behaviour in one place.
Which ranking and citation factors does it touch?
Because the restrictive side wins, conflicts almost always resolve against visibility. I reconcile them so nothing is suppressed by accident.
What is the impact?
High, restrictive rule may suppress a wanted page. Direct (documented precedence).
What is the evidence?
With conflicting robots rules, the most restrictive applies. Google Search Central, Robots Meta Tags Specifications
Frequently asked questions about meta robots and x-robots-tag conflict
What does "Meta robots and X-Robots-Tag conflict" mean?
HTML and header directives disagree.
How do you fix meta robots and X-Robots-Tag conflict?
Reconcile the two sources to a single intended directive.