Removing URLs from Google: what the Removals tool really does
The Removals tool hides a URL for about six months, then it can return. Here is how to remove pages from Google for good, and what it can't do for AI engines.
You published a page by mistake, or a staging copy leaked, or old pricing is still showing in results. The Removals tool in Search Console looks like the obvious fix. It is a fast one, but it is not a permanent one. Used alone, it only hides a URL for a while.
What the Removals tool actually does
A temporary removal request hides a URL from Google Search results for about six months. It also clears the cached copy and the snippet. It does not delete the page from Google's index, and it does not stop Google from crawling it.
That gap matters. If the page still returns a 200 and has no noindex, Google can show it again once the request expires. Teams file a request, forget about it, and see the URL return months later.
You can request removal for one URL or for every URL that starts with a prefix. You must be a verified owner of the property in Search Console. Requests are usually processed quickly, but Google does not promise a timeline.
How to make a removal permanent
The Removals tool buys time. The lasting fix happens on your server. Pick the option that matches your situation.
- The page is gone for good: return a 404 or 410 status. A 410 is a slightly stronger signal, but both work.
- The page should exist but stay out of search: add a noindex tag or an X-Robots-Tag header, and leave it crawlable so Google can see the instruction.
- The page is private: put it behind a login. Anything that needs a password cannot be crawled.
- The page moved: use a 301 redirect to the closest replacement, not the home page.
Do not block the URL in robots.txt and expect it to disappear. A blocked page can stay in the index as a bare URL, because Google can never fetch it to read a noindex or a 404. If you already blocked it, remove the block first so the crawler can see the new status.
Outdated content and cached snippets
Sometimes the page is fine but the snippet is wrong. Maybe you removed a phone number or a price, and Google still shows the old text. The Outdated Content tool is built for this. It is public, so you do not need to own the site to use it.
Google will only act if the live page no longer contains the text, or if the page is gone. If the old text is still on the page, the request is rejected. Fix the page first, then file.
Within the Search Console tool, a clear cache request does a similar job for your own pages. It refreshes the snippet and cached copy without hiding the URL. Use it when the page is correct and only the preview is stale.
Urgent and sensitive cases
If the content is personal data, such as a leaked document or someone's private details, you may not be the site owner. Google has separate request forms for personal information, legal removals, and some types of explicit content. Those go through a review, and the outcome is up to Google.
If the leak is on your own site, act in this order: take the page down or lock it, file a temporary removal for speed, then confirm the permanent status code. The request covers the gap while crawlers catch up.
AI engines are a separate problem
Removing a URL from Google does not remove it from ChatGPT, Perplexity, Copilot, or any other engine. Each has its own crawler, its own index, and its own process. Some of them rely on Bing's index, so a Bing URL removal may help there. Others may keep a stored copy until their next crawl.
There is no shared removal switch. The most reliable steps are the same ones as above: a real 404, 410, or noindex, plus a correct robots.txt for their crawlers. Whether an engine drops old content already used in a trained model is not something a site owner can control. Treat any promise otherwise with doubt.
A short checklist
- Fix the page: delete it, noindex it, redirect it, or lock it.
- Confirm the status code with the URL Inspection tool.
- File a temporary removal if the page is urgent.
- Remove any robots.txt block on the URL so crawlers can see the change.
- Take the URL out of your XML sitemap.
- Check back in a few weeks and search for the URL to confirm it is gone.
Next time you reach for the Removals tool, treat it as a six-month bandage. Change the status code or add noindex the same day, and the problem will not come back.