If a page still appears in Google search results after you add noindex, that does not necessarily mean the setting has failed: Google may not have recrawled the page yet, or robots.txt may be blocking access to the rule. Troubleshoot by checking, in order, whether the directive is being served correctly, whether Googlebot can access the page, whether it has been recrawled since the change, and whether its indexing status has been updated. Seeing noindex on the current page is not, by itself, proof that the page has been removed from the index.
First, confirm that Googlebot actually receives noindex
Do not rely solely on whether the “prevent search engines from indexing” option is checked in your CMS. Google’s official documentation recommends using Search Console’s URL Inspection tool to examine the HTML Googlebot received when crawling the page and confirm that the directive is present.
- If you are targeting only Google, you can add <meta name=”googlebot” content=”noindex”> to the head section of the HTML.
- If you use an HTTP response header, check that X-Robots-Tag: noindex is returned; this approach also works for non-HTML resources such as PDFs.
- When using a CMS, confirm that its search engine settings actually generate the corresponding tag, rather than merely saving an option in the admin interface.
The googlebot tag above targets Google; it should not be taken to mean that other search engines have also removed the page.
Remove robots.txt blocks so the directive can be read
Google must crawl the page to see its noindex tag or response header. If robots.txt prevents Googlebot from accessing the target URL, the crawler may be unable to retrieve the directive even if it has been added.
For example, if a page has noindex but its directory also blocks Googlebot from crawling, this is not an extra layer of protection—it may block the necessary retrieval process. The official documentation recommends adjusting robots.txt to allow Google to access the page; do not treat blocking crawling as a way to confirm removal from the index.
Check the timing of the change against recrawl records
Next, record when noindex went live and check whether the page has been recrawled since then. Public technical discussions have suggested checking server logs. This can help determine whether the process is still waiting for Google to revisit, but it is not proof that removal is complete.
Google officially states that, depending on a page’s importance on the internet, it may take months to revisit it; you can also request a recrawl through the URL Inspection tool. This is not a fixed waiting period, and submitting a request does not mean the index has been updated.
Track configuration validation separately from removal confirmation
Verification should happen on two levels: first confirm that Googlebot can read noindex, then track the indexing status. Google’s official guidance recommends using Search Console’s Page indexing report to monitor pages for which Googlebot has retrieved a noindex directive.
- If the directive has not yet been read: recheck the tag output and crawling restrictions.
- If the directive can now be read: continue checking the indexing report rather than reporting the page as removed simply because its current configuration is correct.
If you need immediate removal from search results, Google’s official documentation points separately to removal instructions. This is a different need from waiting for a routine recrawl and should not be treated as the same step.
Pages still indexed after adding noindex: perspectives from across the web
If the live URL test says a page is excluded by noindex, does that mean it has left the index?
Not necessarily. A 2024 implementation guide explains that a Search Console live test showing exclusion by a “noindex” tag can confirm that the setting is working. It does not, however, confirm that the index has been updated. After checking the setting, you can use the Page indexing report to track whether Google has retrieved the noindex directive.
Other pages left the index quickly, so why is this one still visible after two weeks?
How quickly other pages were removed does not tell you when this page will leave the index. In a public discussion, one person reported seeing other pages leave the index in about a day or two. However, roughly two weeks after adding the tag to the target page, they were still unsure whether it had been removed. This is only an individual account. Google states that the time before it revisits a page depends on the page’s importance and may be several months.
If you urgently need a page to disappear from search results, can you rely solely on the Removals tool?
For a lasting effect, you should not rely solely on the Removals tool. Public discussions recommend keeping noindex on the page itself rather than using robots.txt as a permanent removal method, since robots.txt may also prevent crawlers from reading the tag. If you need immediate removal from search results, consult the separate removal instructions linked from Google’s official documentation. Treat this separately from waiting for a routine recrawl.
References
- 使用「noindex」禁止 Google 搜尋建立索引 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: If the live URL test says a page is excluded by noindex, does that mean it has left the index?; Other pages left the index quickly, so why is this one still visible after two weeks?
- Noindex是什麼?了解3種設定方法與使用時機,讓你提升網站排名!welly.tw · 2024-11-11T08:07:06.770Z — Discusses: If the live URL test says a page is excluded by noindex, does that mean it has left the index?
- How to de-index pages from google using robots.txtwebmasters.stackexchange.com — Discusses: If you urgently need a page to disappear from search results, can you rely solely on the Removals tool?
- De-indexing pages and checking with Google's site: commandwebmasters.stackexchange.com — Discusses: Other pages left the index quickly, so why is this one still visible after two weeks?
- De-indexing pages and checking with Google's site: commandwebmasters.stackexchange.com — Source used in the article above.



