Search Console Page indexing: Why pages aren't indexed
Blocked by page removal tool in Search Console
A Removals request is hiding the URL from Google results. Who filed it, why it is temporary (about six months), and how to keep a page out for good.
A temporary removal request is hiding this URL from Google Search. Open the Removals tool to see the request. Google says a successful request lasts "only about six months", and it hides the page without stopping crawling. To keep it out permanently, use noindex, a 404 or 410, or a password. To restore it, cancel the request.
What "Blocked by page removal tool" means
Google's archived Page indexing help (January 2024) defined it as: "The page is currently blocked by a URL removal request, either by someone who manages this property in Search Console or by an approved request from a site visitor." Google has since removed the entry from the live help page, so treat that definition as historical. The live Removals help says a temporary removal "Blocks the URL from Google Search results for about six months" and "does not prevent Google from crawling your page, only from showing it in Search results".
Is it a problem?
Depends on the URL
Fine if someone meant to hide the page and has a permanent measure in place. A problem if nobody on your team filed the request, or if the page is meant to rank. The archived wording also covers approved requests from site visitors, so check who made it.
Causes, most likely first
- Someone with access to the property filed a temporary removal, often during a leak, a staging incident or a migration.
- An approved removal request from outside the property, which the archived Google definition names.
- A removal filed as a stop-gap while a noindex took effect, and never followed up.
How to confirm it
- Open Indexing > Removals and read the Temporary removals tab for the URL or prefix and the request date.
- Run the indexability checker on the URL to see whether a noindex, a 404 or a robots.txt rule is also in place, which decides what happens when the removal expires.
How to fix it
- If the page should rank, cancel the request in the Removals tool.
- If the page should stay out, make it permanent before the request expires: return 404 or 410, require a password, or add noindex. Google says "Do not use robots.txt as a blocking mechanism."
- Leave the page crawlable if you used noindex, so Google can see it.
How long recovery takes
A temporary removal lasts "about six months" (Google also gives "180 days"). After a cancellation, Google has to recrawl the URL before it appears again. Google also says that if the URL is unreachable (404, 502/3) when you use the tool, "it will assume that the page is gone, and your block request will expire."
After a fix, Validate fix on the issue asks Google to recheck the affected URLs. Google says validation "typically takes up to about two weeks, but in some cases can take much longer". Without it, the count still updates as Google recrawls, and an issue leaves the table once 90 days pass with no instance.
Would monitoring have caught it?
A removal request itself is not visible from outside Search Console, so we would not see it. What we do see is the measure that should replace it: a noindex appearing or disappearing on a monitored URL, or the URL starting to return 404, is reported on the URL check cadence.
stillindexed checks each monitored URL every 30 minutes on Starter and every 15 minutes on Agency, so the change is found on the next check and confirmed before it alerts, rather than waiting for this report to update.
A noindex tag hiding the site from search, platform by platform
Further reading
Related statuses
Sources
Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-22. If Google has changed a page since, Google's page wins and we would like to know.