Troubleshooting guide · search-console · Published 2026-08-16 · 3 min read
Search Console Removals tool explained
The Search Console Removals tool temporarily hides URLs for about six months; make removal permanent with 404, 410 or noindex before the window lapses.
- ·What it hides
- ·The six month window
- ·Make it permanent
The tool hides, it does not delete
The Removals tool in Search Console (previously "URL Removals") suppresses a URL from Google search results quickly, typically within a day. Its most common and useful job is hiding a page fast while a slower, permanent fix takes effect. The name misleads: a removal request does not delete the page from Google's index, does not stop Google from crawling it, and does not force a recrawl. It only hides the URL from results, and it is temporary.
That distinction matters constantly. A request "removes" the page from the visible results without touching the underlying index entry, so if the page stays live and nothing else changes, the page returns to results once the request lapses. This is the mechanism behind most "I removed it but it came back" confusion. The indexing basics draw the crawl-versus-index-versus-results boundary that the tool sits inside.
The six month window
Google documents a successful request as lasting about six months. After roughly 180 days the URL is eligible to appear in results again, and Google recrawls the page before it can show again. During the window the page is hidden even if search engines can still fetch it. If the underlying problem is unresolved by then, file a new request to extend the block, but at that point you should have completed a real removal instead.
Later you must make it permanent
The tool is explicitly a stopgap. To remove content permanently, whichever matches your case:
- Delete the page so it returns a 410 Gone (preferred for gone-forever) or 404 Not Found. Google then drops it naturally.
- Add a
noindexto the page and keep it crawlable so Google can see the directive (see noindex meta). Blocking it in robots.txt does the opposite here: it keeps Google from seeing the noindex, so the URL can linger. - Password-protect the page so it cannot be fetched as public content.
The classic trap is pairing a temporary removal with a robots.txt block and expecting a permanent drop. Because the page is then blocked from crawling, Google never reads a noindex, and once the 180 day window expires the still-live page returns. Keep the page reachable to the crawler if you want the noindex to be honoured.
When to reach for it
- A genuinely sensitive or mistaken URL surfaced and you want it gone from results fast, while you fix or delete the content permanently.
- Cleaned-up hacked or spam pages that are still showing in results; hiding them immediately protects visitors and ranks while Google recrawls (see malware removal for the fuller recovery flow).
- You need to suppress an existing URL that is already removed but lingering in results.
Do not use it as a routine deindexing method or as a substitute for requesting a recrawl when you updated a page you want kept. Requesting indexing re-fetches and refreshes a page you are keeping; removals is for temporarily withholding one you are taking down. Finish with the permanent measure during the window, and the page's eventual drop needs no repeated requests.