Separate access control from indexing control
The deliverable lists environment URL, access requirements, indexing directives and check owner. Noindex is an instruction about search inclusion; it is not a substitute for authentication that protects unpublished information. Check whether a person who knows the address can open it.
If the environment contains customer information or an unreleased announcement, establish appropriate access restrictions first. An absence from search results is not proof of restricted access. Test the intended boundaries as an unauthorised visitor rather than relying only on the view shown to a signed-in developer.
Define expected settings for every environment
Record the staging and production hosts, authentication requirement, robots metadata, HTTP headers, robots.txt and canonical behaviour. Write the expected public response, not merely the name of an environment variable.
For example, a protected staging environment and an indexable public article have different expectations. If one configuration is distributed to every hostname, ask the developer how environment selection and exceptions work. The goal is to detect an inherited rule before release, rather than discover later that production still behaves like the preview.
Understand when a crawler can see noindex
Google’s documentation explains that a crawler must be able to access a page to read its noindex instruction. A robots.txt block can prevent that observation, so a crawl prohibition and noindex should not be treated as interchangeable.
For an authenticated staging environment, keeping unauthorised crawlers out may be the intended result. Do not remove protection from unpublished material merely to expose a meta tag. Choose controls that match the environment’s purpose and verify access protection separately from the behaviour expected of a publicly accessible page.
| Check | Record | Acceptance |
|---|---|---|
| Staging | Access, viewers and host | Unauthorised access restricted |
| Production | HTML, headers and canonical | No unintended staging rules |
| After release | Sample URLs, inspection and owner | Actual response checked |
Example: moving a preview into public release
Consider fictional hosts preview.example.com and www.example.com. The preview requires authentication, while public articles should be accessible and eligible for search. At release, inspect production response headers and HTML for an accidentally retained staging noindex rule.
Check canonical addresses and sitemap entries for the preview host as well. Do not test only the homepage: sample an article, a listing and relevant resources. A passing root page does not establish that every route inherited the intended production configuration.
Correct an accidental production exclusion
If a production page that should be searchable retains noindex, correct the environment configuration and inspect the released response again. In URL Inspection, verify the exact URL and returned content. An edited local configuration file does not prove that the deployed response changed.
If unpublished information became publicly accessible, restore appropriate access restrictions rather than treating it only as a search issue. Notify the responsible owner and preserve the necessary record. Track the public state separately from search observations; a configuration correction does not guarantee an immediate change in search results.
- After correction：Define indexing policy → Contains unpublished information?
Make environment checks part of release acceptance
Check whether the current host provides the required controls and whether an additional plan is needed for the relevant environments and people. Across providers, testing actual unauthenticated access matters more than relying on a feature name.
Acceptance requires the intended viewers to reach staging, unauthorised access to be handled as designed, and representative production pages to carry the intended search directives. Assign the post-release check and include it in the next release process so the distinction between environments does not depend on one person remembering a manual switch.
Resources for the next step
Publishing and site improvement
Organise article planning, images, launch checks and refresh priorities as your publication grows.
Official sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- Google noindex documentationInformation checked: 2026-10-30
- Search Console URL InspectionInformation checked: 2026-10-30
- About Google Search ConsoleInformation checked: 2026-10-27
- Search Console performance metrics and setupInformation checked: 2026-10-27
- Search Console dimensions and data groupingInformation checked: 2026-10-27