Finding indexing directives added by a shared page template
Repeated indexing instructions often originate in shared code or configuration. Compare affected and unaffected templates before editing individual pages one by one.
Map the repeated value
Record the exact directive, its delivery location and the routes where it appears. Group pages by template, renderer or response handler. Include one known intentional exception. This comparison helps an operator distinguish a page-specific setting from a common layout or header rule without assuming that every repeated value is wrong.
Repair once and verify broadly
After confirming the intended behavior, change the shared source that produces the incorrect instruction. Recheck at least one route from every affected group and the intentional exception. If individual overrides remain, document their purpose. Do not merely patch generated output when the next build would restore the same shared defect.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Why include an unaffected page?
It provides a useful comparison for locating the source of the instruction and checking that the repair does not expand beyond its intended scope.