Testing an accidental sitewide noindex after a release
After a release, test representative public pages for accidental noindex instructions. A shared template can affect many routes even when the site looks normal to visitors.
Sample by template
Inspect the homepage, a service page, an article and any separately rendered archive. Save their response headers and delivered HTML. Record which templates show the restriction and which do not. A single successful sample cannot establish the state of every page family, while a repeated instruction across a family points the developer toward a shared source.
Verify the deployed correction
Confirm which pages should be public before removing directives. Correct the relevant environment variable, template or response rule, then repeat the same route set on the public domain. Preserve intentional restrictions on private or utility pages. Report the delivered instruction as repaired without claiming that providers have already updated their indexes.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Should every noindex be removed during a cleanup?
No. Establish the purpose of each page family. Some pages are intentionally excluded and should retain that behavior.