IndexerNow

Removal

How to remove or deindex a URL from Google (the right way)

updated 2026-06-01
The symptom

A page is in Google that shouldn't be — and blocking it in robots.txt isn't removing it.

TL;DR — the fix

Two different goals, two different tools. To hide a URL fast (~6 months), use Search Console's Removals tool. To deindex permanently, add a noindex tag (or X-Robots-Tag header) and keep the page crawlable so Google can see it — then push a re-crawl. Never block in robots.txt to deindex: Google can't read a noindex it isn't allowed to crawl.

Getting a page out of Google is the mirror image of getting one in — and people get it wrong constantly, usually by reaching for robots.txt. There are two separate goals here: removing a URL fast (temporarily) and deindexing it permanently. They need different tools.

Fast but temporary: the Removals tool

Search Console's Removals tool hides a URL from Google results within hours — but only for about six months. It's the right tool for emergencies: a leaked page, exposed personal data, a price mistake, content published early. It buys you time; it does not permanently deindex the page.

Permanent: noindex (and let Google crawl it)

  1. Add <meta name="robots" content="noindex"> to the page, or return an X-Robots-Tag: noindex header.
  2. Make sure the page is NOT blocked by robots.txt — Google has to crawl the page to see the noindex.
  3. Wait for Google to re-crawl. The page drops out of the index on the next crawl.
  4. Push the URL through the Indexing API to trigger that re-crawl sooner, so the noindex is seen quickly.
The #1 deindexing mistake: blocking in robots.txt

Blocking a URL in robots.txt does NOT remove it from Google. If Google can't crawl the page, it can't see your noindex tag — so the URL can stay indexed (often with the dreaded "No information is available for this page" snippet) indefinitely. To deindex, allow the crawl and add noindex. Block in robots.txt only after it's already out.

Permanent: 404 / 410 or redirect

  • Return a 404 (Not Found) or 410 (Gone) if the page genuinely shouldn't exist — Google drops it after re-crawling. 410 is a slightly stronger "this is gone for good" signal.
  • 301-redirect the URL to a relevant replacement if the content moved — the old URL leaves the index and equity flows to the new one.
  • Use canonical tags to consolidate near-duplicates so only the canonical stays indexed.

Confirm it's actually gone

Don't trust a single empty site: search — it's unreliable. Run the URL through a status check (URL Inspection API). When it reports the page as not indexed (excluded by noindex, not found, or redirected), it's genuinely out. For a batch of URLs you're retiring, bulk-check them so nothing lingers.

IndexerNow runs on your own Google account, your own Cloud project, and your own quota — we never pool submissions through a shared account. Connect your GSC and push the URL through Google's Indexing API in two clicks.

Connect your own GSC and index now

Frequently asked

How long does deindexing take?

The Removals tool hides a URL within hours but only for ~6 months. A noindex tag drops the page on the next crawl — anywhere from a day to a few weeks depending on crawl frequency. Pushing the URL through the Indexing API brings that crawl forward.

Why is my page still in Google after I blocked it in robots.txt?

Because robots.txt blocks crawling, not indexing. Google can't see your noindex on a page it isn't allowed to crawl, so the URL lingers. Remove the robots.txt block, add noindex, let Google re-crawl, then re-block if you like.

404 or 410 — which should I use?

Both deindex after a re-crawl. 410 (Gone) is a slightly stronger, faster signal that the page is permanently gone; 404 (Not Found) is fine for most cases. Use a 301 instead if the content moved somewhere relevant.

Related fixes