Removals Tool

What Google Search Console's Removals tool does — and what it doesn't. Temporary removals hide a URL for ~6 months; permanent removal needs noindex, a 404/410, or a password.

First published: Jun 23, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #12 in Search Engine Tools#15 in Tools#240 in Technical SEO#324 on the site

Search Console's Removals tool is the fastest way to hide a URL from Google — results often disappear within a day. But a Temporary Removal is exactly that: it hides the URL for about six months and clears the cached snippet without removing the page from the index. When the clock runs out, the page comes back unless you've paired it with a real permanent method: delete it (404/410), add noindex, or password-protect it — and the page must stay crawlable so Google can see the noindex. The classic mistake is blocking the URL in robots.txt and expecting it to deindex; that does the opposite.

TL;DR — The Removals toolA Google Search Console feature for verified owners to manage how their URLs appear in Search. A Temporary Removal hides a URL for about six months — it does not delete the page from the index. is a verified-owner GSCA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. feature with three tabs. The one that matters most, Temporary Removals, hides a URL (or a whole prefix) from Search for ~6 months and clears the cached snippet — it does not remove the page from the indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.. Permanent removal needs a real method: 404/410, noindex, or password protection — and the page must stay crawlable or Google never sees the noindex. The single most expensive mistake is blocking the URL in robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. and expecting deindexingDeindexing means getting a URL to stop appearing in Google's search results. There's no single delete button — the right method depends on whether you own the page, whether removal is temporary or permanent, and whether the content should still exist.; that blocks crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., not indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and prevents Google from ever seeing your noindex. Temporary removal

  • robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. block = the page comes back at the six-month mark.
Evidence for this claim Search Console's Temporary Removals request can hide a URL from Google Search for about six months but does not permanently remove the content. Scope: Current Removals tool behavior. Confidence: high · Verified: Google Search Console: Removals tool Evidence for this claim Permanent removal requires removing or restricting the content or using noindex; robots.txt alone is not a permanent indexing-removal method. Scope: Google's current removal methods and robots.txt caveat. Confidence: high · Verified: Google Search Central: Remove a page from Google

What the tool actually is

The Removals tool sits in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. and only works on properties you’ve verified. Google’s own framing is precise about its scope: “The Removals tool enables you to temporarily block pages from Google Search results on sites that you own.” Note the two load-bearing words — temporarily and block. It blocks display; it doesn’t delete from the index. And it’s owner-only: “The URL must be in a Search Console property that you own.”

There are three tabs. Temporary Removals is the one most people come for; the other two (Outdated Content and SafeSearch filtering) are surfaces for public requests filed by people who don’t own the site.

Tab 1 — Temporary Removals

This is the fast lever. Submit a URL and it typically disappears from results within a day. Two things happen: the URL is hidden from Search, and the cached snippet/description is cleared — though clearing the snippet doesn’t stop the page from appearing for a query that matches the removed information before Google reindexes it; the old text just won’t show in the description anymore.

Scope note: this only affects Google Search. It doesn’t touch other Google properties — Google’s own guidance is to use each product’s own removal process for those — and it has no effect on other search engines.

You get two scopes:

  • A single URL — hide exactly one page.
  • A prefix“Remove all URLs with this prefix.” This blocks everything under that path, and it covers both the www and non-www versions. It’s the right tool for nuking a leaked subdirectory or a rogue subdomain quickly — and it’s blunt, so scope it carefully. A prefix that’s too broad takes down more than you meant.

The duration is the whole point of the “temporary” label. Google: “A successful request lasts only about six months.” The Search Central docs say the same in different words: “Requests made in the Removals tool last for about 6 months.”

And critically: “Blocking a URL does not prevent Google from crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. your page, only from showing it in Search results.” The index entry persists. The page can reappear after the window closes. (Bing has an equivalent block-URL tool; as I cover in my URL removal guide, Bing’s temporary block runs about three months versus Google’s six.)

The big caveat: temporary is not permanent

This is the centerpiece. A Temporary Removal is a stopwatch, not a delete key. If the only thing you did was submit the URL to the Removals tool, here’s the sequence that bites people roughly six months later:

  1. You temporarily remove the URL — it vanishes from results. Great.
  2. You assume the job is done and move on.
  3. The ~6-month window expires.
  4. Nothing permanent was ever applied, so the still-indexed page reappears.

The fix is to pair the removal with a permanent method every single time. Use the Removals tool to make the page disappear today, while the durable change propagates on Google’s slower recrawlCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. schedule.

How to remove a page permanently

Google lists three real methods, and the Removals tool is none of them:

  • Delete it (404/410). Remove the page and make sure the server returns a 404 (Not FoundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore.) or 410 (Gone). After Google recrawls it, the page drops out of the index. (410 tends to clear a hair faster than 404 in practice, but both work.)
  • noindex. Add a noindex rule via the meta robotsThe robots meta tag is an HTML element in a page's head — <meta name=\"robots\" content=\"noindex\"> — that tells search engines how to index and serve that page. It's crawl-then-obey: a page blocked in robots.txt is never fetched, so the tag is never seen. tag or the X-Robots-Tag HTTP header. As Google puts it: “A noindex tag only blocks your page from showing up in Google search results.” This is the standard way to keep a live page out of the index. The mechanics live in the meta robots and X-Robots-TagThe X-Robots-Tag is an HTTP response header that carries the same indexing and serving directives as the robots meta tag (noindex, nofollow, nosnippet, and the rest). Because it lives in the header rather than the HTML, it's how you control indexing for non-HTML files like PDFs, images, and videos. write-ups.
  • Password-protect it. “Limiting access to your page enables the right users to view your page, while preventing GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. and other web crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. from accessing it.” Good for content that should exist but never be public.

The non-negotiable condition on the noindex route: the page has to stay crawlable. Google has to be able to fetch the page to read the noindex. Which brings us to the mistake.

The robots.txt mistake (crawling is not indexing)

The most common self-inflicted wound here is blocking the URL in robots.txt and expecting it to deindex. It does the opposite. Both of Google’s docs say so flatly: “Do not use robots.txt as a blocking mechanism.” and “Don’t use robots.txt as a way to block your page.”

The reason is the crawl-versus-index distinction. A robots.txt disallow blocks crawling, not indexing. A blocked URL can stay in the index — often shown as a bare URL with no snippet — if anything links to it. Worse, because Google can no longer crawl the page, it can never see a noindex you add. So the belt-and- suspenders move people reach for — noindex plus a robots.txt disallow — actually cancels itself out.

Now connect it to the six-month clock. If your “removal” was a Temporary Removal plus a robots.txt block, then when the window expires Google has never been able to crawl the page, has never seen any noindex, and the still-indexed URL comes straight back. That’s exactly where this mistake becomes visible. The decision rule is simple: want it gone? allow crawling and add noindex (or return 404/410, or lock it). Never use a robots.txt disallow as your removal method. (The blocked-by-robots.txt status in the Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. is the other place this shows up.)

Tab 2 — Outdated Content

The Outdated Content tab shows requests filed through the public Remove Outdated Content tool — the tool used by people who do not own the site. It’s for when a page or its snippet no longer reflects what’s actually live: the content changed or the page was taken down, but Google’s results still show the stale version. If you own the site, you generally don’t need this tab — you’d use Temporary Removals (and a permanent method) instead. It’s mainly visibility into what outside parties have requested against your URLs.

Tab 3 — SafeSearch filtering

The SafeSearch filtering tab surfaces pages on your site that users have reported as adult content through the public SafeSearch report. Google reviews them: “URLs submitted using this tool are reviewed, and if Google feels that this content should be filtered from SafeSearch results, these URLs are tagged as adult content.” Once tagged, those pages get filtered out when SafeSearch is on.

Verifying a removal

Submit the Temporary Removal for speed, apply your permanent method, then confirm it took. The URL Inspection tool tells you how Google last crawled and indexed a specific URL. The Page Indexing report is where you watch a page’s status settle over time — including whether it’s correctly marked noindex or, if you made the mistake above, sitting in the blocked-by-robots.txt bucket.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.