How Google applies it
Google has to crawl the page to see the rule, so the page must not be blocked by robots.txt. Google acts after it next crawls the page, which its documentation says may take months for pages that are rarely visited. Google does not support noindex written in robots.txt.
The usual failure
A staging site is correctly set to noindex, and the setting travels to production with a database copy, a template or a server rule. The site works for visitors and slowly disappears from search.
A quick audit
Run curl -s https://example.com/ | grep -i 'name="robots"' to see the meta tag and curl -sI https://example.com/ | grep -i x-robots-tag to see the header. Run both for production and for staging: staging should show noindex, production neither. Put the two commands in the release checklist, because the setting that protects staging is the one most often copied to production by mistake.
Noindex removes a page from search results but does not hide it: anyone with the address can still open it, and a page that must stay private needs authentication, not a meta tag. When the rule is removed, the page returns to the index after its next crawl, not instantly.
What to check
The meta tags in the source, the response headers (which the source does not show), and Search Console’s URL Inspection and Pages report, for at least one URL per template, after every release.
Sources
Read on . Standards and vendor pages change; confirm the current text before you rely on it.
- Google Search Central, Block Search indexing with noindex (developers.google.com)