# The Removals tool: how to take a page out of Google, properly

You want a page gone from Google, fast, without causing more damage. This guide shows you what each Removals option does, how to pair it with noindex or a 404 or 410, and the traps to avoid.

Updated 2026-09-14 · Source: https://porteur.ai/guides/search-console-removals-tool

## What the Removals tool actually does

Temporary removal hides a URL or a prefix from Google results for about six months. It also clears the cached copy. It does not remove the page from the index.

If a page must go, pair the request with a noindex, a 404 or a 410. That is what removes it from the index. Without that, it can return after the hide expires.

Clear cached URL keeps the result but drops the snippet until the next crawl. Use it to scrub a wrong summary or a leaked price that you have already fixed on the page.

Outdated content is for pages you do not own. You request removal of content that is no longer on the live page. It does not manage your own site’s URLs.

SafeSearch filtering lists your URLs reported as adult. It is a review surface, not a delete button. It helps you see why some users may not see your pages in filtered results.

## When to use each option

- Temporary removal: you need a result hidden now while you add noindex, return a 404 or 410, or fix a misconfigured page like "/private/beta" accidentally linked.
- Clear cached URL: the live page is fixed, but the Search result snippet still shows old or sensitive text. Example: yourproduct.com/pricing showed a wrong plan. Clear the cache to drop the old snippet.
- Outdated content: you want search results cleaned for a page you do not control. Example: an old partner page mentions your legacy brand name, but they already removed it from their page.
- SafeSearch filtering: check if an educational guide like "/guides/getting-started" has been flagged as adult content in error, which limits its visibility for some users.

> Temporary removal is a hide, not a delete. Make removals permanent with noindex, 404 or 410.

## Run a Temporary removal without breaking things

1. **Confirm the exact URL** Case and protocol matter. https://www.yourproduct.com/pricing is different from http://yourproduct.com/pricing. Copy the URL from your site or Search Console’s URL Inspection.
2. **Decide URL vs prefix** Pick URL if it is one page or one file like /media/leak.pdf. Pick prefix if you must hide a folder like /private/. A prefix covers everything under that path.
3. **Open Search Console, Removals** Choose your property. Click Temporary removals. Click New request. Paste the URL or prefix.
4. **Submit and document** Write down what you removed and why. Keep a short log so you can reverse mistakes fast.
5. **Pair it with a permanent action** Add a noindex to the page, or return a 404 or 410 from your server. Do this now, not six months from now.

What a fixed page looks like: yourproduct.com/private/beta now returns a 410, and the prefix /private/ is removed from the sitemap. The result is hidden now and gone for good on recrawl.

> Prefix requests are powerful. A wrong slash can remove a section you did not mean to hide.

## Make it permanent: noindex, 404 or 410

Use noindex when the URL should work for users but not be in Google. Example: /guides/print-friendly stays accessible but should not rank. Keep the page 200 OK and add a noindex tag in the head.

Return a 404 when the page is gone by mistake or for a while. Return a 410 when it is gone on purpose and not coming back. Both remove the URL from the index over time, once crawled again.

1. **Remove or update internal links** Find and edit links to the removed page. Change /pricing-old to /pricing. Remove links to /private/beta.
2. **Clean your sitemap** Do not list removed URLs in your sitemap. If you keep lastmod, make sure it is consistently accurate. Google ignores changefreq and priority.
3. **Test the response** Load the URL in your browser and with curl. Confirm 404 or 410. If using noindex, view source to confirm the tag is in the head.
4. **Submit in URL Inspection if needed** Request indexing to speed up seeing the change. Then wait for the next crawl to reflect it in results.

For a folder like /careers/archive/, keep working pages and remove only the closed roles. Return 410 on /careers/archive/designer-2019 and keep /careers/ live with noindex if it is not for search. Update the sitemap index if you split sitemaps by section. A sitemap may hold up to 50,000 URLs or 50 MB uncompressed and can only list URLs on its own host, as of 2026.

## Property scope: avoid removing the wrong site

Search Console removals act on the selected property. A Domain property, verified by DNS, covers every subdomain and both protocols. A URL-prefix property covers one exact prefix like https://www.yourproduct.com/.

- Check you are in the right property before you submit.
- Prefer a Domain property if you serve on both www and non-www, or both http and https.
- Add extra owners if more than one person manages removals. Verification lapses if the token is removed.

> Never guess a pattern. Paste the exact URL. A prefix request on /blog can also hide /blogroll if the slash is missing.

## Clear cached URL: fix snippets after a content change

Clear cached URL keeps the result, but drops the snippet until the next crawl. Use it after you remove sensitive or wrong text from the live page. Example: you removed a leaked plan name from /pricing. Clear cached URL to stop that line showing in results today.

1. **Edit and publish the page** Remove the text or image you do not want in the snippet. Save the change.
2. **Open Removals and pick Clear cached URL** Paste the exact URL. Submit.
3. **Request indexing** In URL Inspection, request indexing for the URL to get it crawled again sooner.

What a fixed page looks like: /pricing now shows the corrected plan names. The search result keeps the title and URL, but the snippet is blank or updated on the next crawl. No hide is applied, so the page still gets clicks while the cache refreshes.

## Pages you do not own: use the Outdated content path

If an external page’s result shows text that is no longer on their live page, use Outdated content. You are asking Google to update that result. You are not managing their site.

- Copy the result URL from Google.
- Check that the text you want gone is really not on the live page any more.
- Submit the request in Outdated content.

This does not remove live content. If the text is still on their page, ask the site owner to remove or update it first. Then use Outdated content to clean the result more quickly.

## Links and redirects: tidy up before you remove

Removing a page that still has links wastes equity and confuses users. Fix links first, then remove. Use Search Console’s Links report to find internal and external links Google knows for your property, up to 1,000 rows in each table and export.

1. **Find internal links** Open Links, Internal links. Check Top linked pages. Update templates and navs that still point to /pricing-old.
2. **Choose the redirect or removal** If there is a clear replacement, 301 /pricing-old to /pricing. If the page must die, return 410 and remove links.
3. **Audit external links** In Links, External links shows Top linked pages and Top linking sites. Reach out to high-value referrers if a redirect is not an option.

What a fixed page looks like: /blog/2021/launch-note now redirects to /blog/our-launch-story. Your sitemap drops the old URL. Internal menus no longer point to the removed path. Performance report no longer shows impressions for the old URL after recrawl, and clicks shift to the new one.

> The Links report is a sample. Counts differ from third-party indexes. Use it to spot problem links Google knows, not to reconcile totals.

## Sitemaps and index hygiene after removals

Keep your sitemap clean. Do not list URLs you removed or noindexed. Submit your sitemap or a sitemap index by URL in the Sitemaps report. Watch Status, the date last read and the number of URLs discovered.

- A sitemap may list up to 50,000 URLs or 50 MB uncompressed.
- It can only list URLs on its own host, or an approved cross-host setup.
- Google reads lastmod when it is consistently accurate. It ignores changefreq and priority.

If you run a temporary removal on /private/, remove that folder from the sitemap now. If you later bring back a page under /private/ with noindex, keep it out of the sitemap to avoid mixed signals.

## Monitor the fallout and recover safely

Use the Performance report to check that impressions and clicks for the removed URL drop as expected. Filter by Page. Compare periods to confirm traffic moved to the new URL, not just vanished. You have 16 months of data and regular expressions for filters, as of 2026.

Check Settings, Crawl stats for spikes in 404 or 410 responses if you removed many pages. The report shows total crawl requests, total download size and average response time over 90 days, plus breakdowns by response code and Googlebot type. This helps you spot server strain or misconfigured removals early.

If a removed URL still shows in results after you added noindex or a 404 or 410, wait for the next crawl. You can request indexing in URL Inspection to nudge it. Do not submit repeated Temporary removals as a substitute for the permanent fix.

> Do not block robots.txt to remove indexed pages. Google cannot see your noindex behind a block. Return a 404 or 410, or serve the page with noindex.

## Questions

### How long does a Temporary removal last?

About six months. It hides the result and clears the cached copy. It does not remove the URL from the index. Pair it with a noindex, a 404 or a 410 to make it permanent.

### Should I use noindex or 404 to remove a page?

Use noindex if the page should load for users but not appear in search. Use 404 or 410 if the page is gone. 410 signals it will not return. All three remove the URL from the index after a recrawl.

### What if I accidentally hid a whole section with a prefix request?

Undo the mistake by cancelling the request in Removals, then wait for results to return. If you added noindex or 404s in the meantime, fix those first. Always paste exact URLs, and keep a Domain vs URL-prefix property check before you submit.

### Will Clear cached URL remove sensitive text from Google forever?

No. It drops the snippet until the next crawl. You must remove the text from the live page first. When Google crawls again, it will build a new snippet from the updated content.

### Can I remove a page I do not own?

You cannot manage their URLs. You can request Outdated content when a result shows text that is no longer on the live page. If the text is still live, ask the site owner to change it first.

### Do I need to edit my sitemap after removals?

Yes. Do not list gone or noindexed URLs. Submit the sitemap URL in the Sitemaps report. Watch Status, last read date and URLs discovered to confirm Google picked up the change.

## Read next

- [How to use Google Search Console in ten minutes a week](https://porteur.ai/guides/how-to-use-google-search-console): A quick weekly routine: set four filters, compare 28 days, check pages then queries, and fix three findings, without getting lost in noise.
- [How to use the URL Inspection tool in Search Console](https://porteur.ai/guides/url-inspection-tool): Read each panel, run Test live URL, and know when to request indexing. Fix new pages, dropped pages, and canonicals Google ignores.
- [How to fix 404 errors reported in Search Console](https://porteur.ai/guides/how-to-fix-404-errors-in-google-search-console): Decide which 404s to fix, find the ones with links or traffic, choose redirect, restore or 410, clean internal links and sitemaps, and revalidate.
- [Excluded by noindex tag: check it is what you meant](https://porteur.ai/guides/excluded-by-noindex-tag): Search Console shows Excluded by noindex tag when a page says not to index. This guide shows how to confirm the cause, fix it, and get the right pages back.
- [The Links report in Search Console: what it shows and what it hides](https://porteur.ai/guides/search-console-links-report): What Google’s Links report really shows, why counts differ from Ahrefs or Semrush, and two jobs it is good at on a small site.
- [The Sitemaps report: what Success, Has errors and Couldn’t fetch mean](https://porteur.ai/guides/search-console-sitemaps-report): How to submit your sitemap URL, read Success, Has errors and Couldn’t fetch, and fix invalid XML, 404s, cross‑host URLs and missing child sitemaps.

Paste your URL to get a free check that reads your site, the searches around it and who ranks on them, and shows three findings in about thirty seconds. Free check: https://porteur.ai/