Skip to content
goflag
Documentation
Rule catalogue

robots.conflict

robots, googlebot, and X-Robots-Tag must not contradict each other

errorper pagevendor-spec

Why it matters

Three places can declare indexing policy, and a header injected by a proxy outranks the tag a developer reads in the source. This is what a staging header left on a production route looks like from the outside.

What the finding looks like

The message goflag prints, with example values substituted.

error robots.conflict Conflicting indexing directives: X-Robots-Tag header say noindex, meta robots say index.

How to fix it

This rule ships no snippet, because the remedy is a judgement rather than a line of code: the finding tells you what is out of range, and what to put there is yours to decide.

Says who?

This rule is vendor-spec, and it cites the documentbelow. Nothing here is goflag’s opinion of what a good page looks like — if you disagree with a finding, this is what you are disagreeing with.