Search Console Removals Tool: When to Use It and When Not To

You found a page in Google that should not be there. Maybe it is a staging page, an old price list, or a customer file that went live by mistake. The Search Console Removals tool can hide that URL from Google Search in about a day. But it only hides it for about six months, and it does not delete anything from Google’s index for good.

So the short answer is this. Use the tool when you need a page out of Google results fast. Then fix the page itself so it stays out. For almost everything else, the tool is the wrong choice, and using it can cause more harm than good.

In this guide I explain what each part of the tool does, when I use it, when I’d skip it, and how to make a removal permanent.

What the Search Console Removals Tool Does

Google launched the current version of the Removals tool in Search Console in January 2020. You find it in the left menu under Index > Removals. It has three tabs, and only the first one is something you act on.

• Temporary removals: requests you, the site owner, make to hide URLs from Google Search.
• Outdated content: requests that anyone on the web made through Google’s public Remove Outdated Content tool for pages on your site.
• SafeSearch filtering: URLs on your site that Google users reported as adult content.

The tool only works on sites you have verified in Search Console. Google’s help page says you must own the property to submit a temporary removal. If the page is on someone else’s site, you need a different route, which I cover further down.

It Hides, It Does Not Delete

This is the part most people get wrong. A temporary removal blocks the URL from showing in Google results. It does not remove the page from your server, from the internet, or from Bing and other search engines.

Google also keeps crawling the page while the block is active. If the page is still live when the block ends, it can come straight back into results. That is why I treat every removal request as step one of two.

The Two Request Types

When you click New request on the Temporary removals tab, you choose between two options. They do very different things.

Temporarily Remove URL

This hides the URL from Google Search results for about six months. It also clears the cached copy and the snippet (the short description under the title in results).

You then pick how wide the request should be:

• Remove this URL only: hides one exact URL.
• Remove all URLs with this prefix: hides every URL that starts with what you typed. For example, https://example.com/old-shop/ would cover every page inside that folder.

Be careful with the prefix option. If you type https://example.com/blog without the trailing slash, it can also match /blog-tips/ or /blogger-guide/. I always double-check the prefix against a list of real URLs before I submit.

Clear Cached URL

This one does not hide the page. It clears the cached copy and the snippet until Google crawls the page again. The page itself still ranks.

I use it when the page is fine but the snippet in Google is out of date or shows something you already removed from the page. A common example is a wrong phone number or an old price in the description. Fix the page first, then clear the cache, so Google builds the new snippet from the updated page.

How Google Matches the URLs You Submit

Small details in the URL matter a lot here. Google’s help page explains a few rules that are easy to miss.

• Case matters. /Dragon and /dragon are two different URLs.
• Protocol and www are covered together. A request for one URL also covers its http, https, www and non-www versions.
• Other subdomains are not covered. Hiding a URL on staging.example.com does nothing for www.example.com, and the other way round.
• Parameters count. If the URL in Google has ?id=12 on it, include that. The text after a # is ignored.
• Duplicates need their own request. If the same content shows at several URLs, submit each one.

The second point surprises people. Some site owners try to use the tool to remove the http version of their site after moving to https. That request hides the https pages too, because Google treats them as the same URL for this tool. Use redirects and canonical tags (a line of code that tells Google which version of a page is the main one) for that job instead.

How to Submit a Removal Request, Step by Step

Here is the process I follow when a page really does need to come out of Google quickly.

1. Confirm the URL is really in Google. Search for it with the site: operator or inspect it in Search Console. Copy the exact URL that shows in results, including case and parameters.
2. Open the tool. In Search Console, pick the right property, go to Index > Removals, and stay on the Temporary removals tab.
3. Click New request. Choose Temporarily remove URL, paste the URL, and choose either this URL only or the prefix option.
4. Submit and watch the status. Google says requests are usually processed within a day, but that is not guaranteed. The status column will change to “Temporarily removed” once it works.
5. Fix the page so it stays out. Delete it, password-protect it, or add a noindex tag. I explain each option in the next section.
6. Check before the six months end. Inspect the URL again to confirm Google has seen the permanent fix. I put a reminder in my calendar a few months out.

If you want to check many URLs at once instead of one by one, the Search Console URL Inspection API can pull index status in bulk. That is handy after a large cleanup.

How to Make a Removal Permanent

The temporary block buys you time. What happens to the page during those six months decides whether it comes back. You have three solid options.

Delete the Page

Remove the page and have your server return a 404 (not found) or 410 (gone) status code. Once Google recrawls it and sees the error, it drops the page from the index. For PDFs and other non-HTML files, just remove the file from the server.

If the page has a natural replacement, a 301 redirect to that page is also fine. Just know that the old URL will then pass its signals to the new one rather than disappear.

Password-Protect the Page

If the content needs to stay online for some people, put it behind a login. Google cannot crawl what it cannot see, so it will not index the content. This is my first choice for client portals, internal documents and staging sites.

Add a Noindex Tag

A noindex tag is a line in the page’s code that tells Google not to show the page in results. You add it in the page head:

<meta name="robots" content="noindex">

For PDFs and other files, you can send the same instruction as an X-Robots-Tag: noindex HTTP header. Most CMS platforms and SEO plugins have a simple switch for this.

Why Robots.txt Is Not a Removal Method

Google says not to use robots.txt to block pages from search. Robots.txt stops crawling, not indexing. A blocked URL can still show in results with no description if other pages link to it.

Worse, if you block a page in robots.txt, Google cannot crawl it to see your noindex tag. I see this clash often: a page has both a noindex tag and a robots.txt block, and the owner cannot work out why it is still in Google. Pick noindex and let Google crawl the page.

When to Use the Removals Tool

In my experience, most sites never need this tool. When it is the right call, it is usually urgent. These are the cases where I reach for it.

• Private or sensitive data went live. Customer details, internal files, or anything that could cause harm while you wait for Google to recrawl.
• A staging or test site got indexed. Verify the staging subdomain as its own property, use the prefix option on its root, and then put the whole thing behind a password.
• Hackers created spam URLs on your site. Once you have cleaned the site, you can use the tool to hide the new spam pages the attacker made while Google catches up.
• A page shows information that is wrong in a way that matters. A recalled product, a legal problem, or an offer you can no longer honour.
• An outdated snippet causes real confusion. Here, Clear cached URL is the better option, not a full removal.

The common thread is speed. If the page can wait a few days or weeks for Google to recrawl it on its own, I let it.

When Not to Use It

Google’s own documentation lists several jobs the tool should not be used for. These match the mistakes I see most often.

• Cleaning up old 404 pages or crawl errors. Pages that return 404 drop out of the index on their own. Removing them by hand adds nothing.
• Fixing duplicate or canonical issues. As I explained above, the tool covers all protocol and www versions, so you can hide the page you wanted to keep.
• Site moves and URL changes. Use 301 redirects. Removing the old URLs during a move can hide pages before Google has followed the redirects.
• Pruning thin or low-quality content. Hiding a page does not change how Google sees your site. Improve, merge, redirect or delete those pages instead.
• Trying to recover from a ranking drop. If your traffic fell after the May 2022 core update, hiding pages will not fix it. Core updates are about overall content quality, not single URLs.
• Removing content from other people’s sites. You cannot submit requests for pages you do not own.

One more warning. I would never use the prefix option on a whole live site unless the site really needs to vanish from Google. A single wrong submission can hide every page you have. If you make a mistake, cancel the request right away (see below).

Choosing the Right Tool for Your Situation

This table is the quick reference I use when someone asks me how to get a page out of Google.

Removing Content From Sites You Don’t Own

The Removals tool in Search Console is only for your own properties. For other sites, Google offers separate public routes.

Outdated Content on Another Site

If a page on another site has been deleted or changed, but Google still shows the old version, use the Remove Outdated Content tool. You can ask Google to drop a page that no longer exists or to refresh a snippet that no longer matches the page.

It only works if the change has already happened on the live page. If the content is still there, Google will deny the request. In that case, the first step is to contact the site owner.

Personal Information

Google has had a policy for years for removing some kinds of personal data, such as ID numbers and bank details. In late April 2022, Google expanded it so people can also ask to remove results that show their contact details, like a phone number, email address or home address. These requests go through Google’s own form, not Search Console.

Keep in mind that this only removes the result from Google Search. The page itself stays live on the other site.

Legal Requests

Copyright complaints and other legal issues have their own request forms at Google. They follow a separate review process, and the Removals tool plays no part in them.

Reading the Other Two Tabs

Even if you never submit a request yourself, I recommend checking the other two tabs a few times a year. They show things you would not otherwise know about.

Outdated Content

This tab lists requests that other people made about your pages through the public Remove Outdated Content tool. You will see two types: outdated snippet removal (the page still exists but changed) and outdated page removal (the page is gone).

Most entries are harmless. But if you see a lot of requests for live, important pages, it is worth a closer look. It can be a sign that pages are returning errors to some visitors, or that someone is unhappy with what a page says.

SafeSearch Filtering

SafeSearch is the setting that filters explicit results in Google. This tab lists URLs on your site that users reported as adult content. If Google agrees after review, the URL is marked as “Filtered” and hidden for people with SafeSearch turned on.

If your site is not adult in nature and pages show up here, check whether images or user comments might have caused it. For a medical, art or education site, a SafeSearch filter can quietly cut traffic, so I’d check this tab after any traffic dip I can’t explain.

Checking, Cancelling and Renewing Requests

The Temporary removals tab keeps a history of your requests from the past six months. Each one shows a status.

• Processing request: Google is working on it.
• Temporarily removed: the URL is hidden. Make the fix permanent before it ends.
• Request denied: often because the same request already exists.
• Removal expired: the block has ended, and the page can show up again if it is still live.
• Request canceled: someone ended it early.

To end a request early, open the menu next to it in the history table and choose Cancel request. You would do this if you hid the wrong URL, or if the page is fixed and you want it back in Google. Pages usually return to results soon after.

If six months pass and you still can’t make the removal permanent, you can submit a new request when the old one expires. Honestly, though, if I’m doing that, it means something went wrong with the permanent fix. I’d rather sort that out.

Also note that while a URL is hidden, Search Console’s indexing report can list it under “Blocked by page removal tool”. That is expected, not an error to fix.

For the full list of statuses and rules, Google’s Removals tool help page is the most reliable reference.

Final Thoughts

The Search Console Removals tool is an emergency brake, not a cleaning tool. Use it when a page must leave Google fast, and then delete, password-protect or noindex that page so it stays out after six months. For duplicates, old 404s, site moves or ranking drops, leave it alone.

A good next step is to look at your Temporary removals history today and check that nothing important is hidden by mistake. If you are planning a wider site review, my SEO checklist for 2022 covers the other technical checks I’d run alongside it.