How to remove a page from Google: 404, 410, 301 or noindex?

Short answer: To remove a page from Google, change what your server answers instead of asking Google to forget the address: 404 or 410 if the page is gone for good, a 301 to its direct successor if it has one, noindex if it must stay online but out of search. Never block the page in robots.txt, because then Google cannot see any of these signals. The Removals tool in Search Console hides a page within about a day, but only for about six months, so treat it as a first step and not as the fix.

How do you remove a page from Google? Start with what happened to it

There is no single switch. Google reacts to what your server says when it fetches the address again, so the method depends on the fate of the page. Find your row first, then read the matching section.

Google's own advice for a page without a replacement: “return a 404 (not found) or 410 (gone) response (status) code for the page” (page on troubleshooting crawl errors, last updated 2025-12-18). We read the Google pages linked here on 4 November 2026.

Two rules hold for every option. First, Google can only see an answer from an address it may fetch. Google's old post Do 404s hurt my site? (2 May 2011) says the crawler, to see the status code, “has to be able to crawl that URL”. A robots.txt block hides the answer. Second, cover every spelling of the address. Google's page on removing information says: “Protect or remove all variations of the URL for the content that you want to remove.”

The four options in detail

1. 404: the page is gone and nothing replaces it

404 means “not found”. Google's page on HTTP status codes (last updated 2026-02-04) states what happens next: “URLs that are already indexed and return a 4xx status code are removed from the index.” For an address Google meets for the first time as a 404, it adds: “Newly encountered 404 pages aren't processed.”

A 404 is not a problem in itself. Google's Search Console help on the Page indexing report says: “404 responses are not necessarily a problem, if the page has been removed without any replacement.”

You may show a designed error page, but it must send the status 404. A friendly page with status 200 is a soft 404, and our article on soft 404 errors shows how to find and fix it.

2. 410: the page is gone on purpose

410 means “gone”: you removed the page deliberately and for good. In Google's documentation there is no difference to 404: “All 4xx errors, except 429, are treated the same.” We found no Google page that promises 410 is faster.

Our view, and nothing more: use 410 when you removed something on purpose and your server makes it easy; otherwise 404 is the normal answer. Neither is wrong.

3. 301: the page has a successor

If a page has a replacement on the same topic, a redirect keeps visitors and signals together. The troubleshooting page says to return a 301 when a page “has a clear replacement on your site”. Google's page on redirects (last updated 2026-04-14) explains the effect: “Permanent redirects: Show the new redirect target in search results.” Temporary redirects (302, 307) show the source page instead, so they are the wrong tool for a removal. The status code page calls 301 and 308 a strong signal and 302 and 307 a weak one.

Three details decide whether the redirect helps:

• Send it to the equivalent page, not to the home page. The 2011 post says that redirecting unknown addresses to the home page “can have negative effects on our understanding and indexing of your site”. A 2019 report by Search Engine Roundtable on a post by John Mueller says Google mostly treats such redirects as soft 404s (report); that is second-hand, so take it as a pointer. With no real successor, answer 404.
• Redirect once. Google follows up to 10 redirect hops by default, and its page on crawl errors warns: “Watch out for long redirect chains, which have a negative effect on crawling.” Point the old address straight at the final one.
• Keep it for a while. For site moves with URL changes, Google says: “Keep the redirects for as long as possible, generally at least 1 year.” (site move guide.) Applying that to a single page is our reading.

4. noindex: the page stays online, but not in search

noindex is a rule in a meta tag or an HTTP header. Google's page on blocking indexing with noindex says that once Googlebot has crawled the rule, “Google will drop that page entirely from Google Search results”. Two conditions follow from that page:

• The page must not be blocked in robots.txt. Otherwise “the crawler will never see the noindex rule”. Putting noindex into robots.txt does not work either: “Specifying the noindex rule in the robots.txt file is not supported by Google.”
• Google has to come back. The page says “it may take months for Googlebot to revisit a page”, depending on how important the page is.

noindex is also no lock. Visitors can still open the page, and search engines that ignore the rule may still list it. For anything private, Google's removal page names two safer ways: remove the content, or protect the page with a password.

For HTML pages use the meta tag. For PDFs, images and other files use the header:

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

X-Robots-Tag: noindex

All three server-side cases in nginx (addresses are examples):

# gone on purpose: 410 (or simply let the server answer 404)
location = /old-offer {
    return 410;
}

# replaced: 301 straight to the final address
location = /old-guide {
    return 301 https://example.com/new-guide;
}

# online for visitors, hidden from search
location = /price-list.html {
    add_header X-Robots-Tag "noindex" always;
}

The Removals tool: fast, but only for about six months

Use the Removals tool when a page must disappear quickly, for example after a wrong price or published private data. You need to own the property in Search Console. Google's removal page says it removes a page from search results “within a day”; the tool's help page is more careful: “The request usually takes up to a day to process, and is not guaranteed to be accepted.”

In the English interface: open the Removals tool, select the “Temporary Removals” tab, click “New Request”, choose “Temporarily remove URL” and enter the address. “Remove this URL only” blocks one address, “Remove all URLs with this prefix” a whole folder.

Know its limits:

• It is temporary. “Blocks the URL from Google Search results for about six months.” Afterwards the page can reappear if it is still reachable and nothing else blocks it. The help page puts it plainly: “The Removals tool provides only a temporary removal of about six months.”
• It does not stop crawling. “Blocking a URL does not prevent Google from crawling your page, only from showing it in Search results.”
• It is not for tidying up. Old pages that return 404 “will naturally drop out of our search results”, says the help page. No request needed.

So use the tool as the first step, as the help page itself calls it, and make the removal permanent at once: 404 or 410, a password, or noindex. robots.txt does not do that.

How long until the page is gone? What Google does not say

Google gives no deadline for 404, 410 or noindex; we found none on the pages linked here. What they do say:

• A 404 address is still fetched for a while: “Google continues to crawl all known URLs even after they return 4XX errors for a while.” And: “there is no way to tell Googlebot to permanently forget a URL, although it will crawl it less and less often.”
• noindex waits for the next visit of Googlebot: “it may take months”.
• A recrawl request through the URL Inspection tool does not promise an outcome either: “Crawling can take anywhere from a few days to a few weeks.” (ask Google to recrawl, last updated 2025-12-10.)

So promise no date, to yourself or to anyone else. What you control is that your server's answer is correct today.

How to check that it worked

First, ask your server. Request the address and read the status, not the page. The three commands print the status for a removed page, for a redirect (with its target) and for a noindex header:

curl -s -L -o /dev/null -w "%{http_code} %{url_effective}\n" https://example.com/old-offer
curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" https://example.com/old-guide
curl -s -D - -o /dev/null https://example.com/price-list.html | grep -i x-robots-tag

Then work through the list:

1. Check the status. The first command should print 404 or 410, the second a 301 and the new address, the third the header x-robots-tag: noindex.
2. Ask Google what it gets. The URL Inspection tool in Search Console shows the stored index status, and the live test shows what Google fetches now. Google's crawl error page says to use it “to verify whether your URL is actually returning the correct code”.
3. Clean up what points at the old address. Take the address out of your sitemap: “Include the URLs in your sitemap that you want to see in Google's search results.” Update your own links to the final address.
4. Wait, and check later. The Page indexing report shows only URLs “that have shown 404 errors in the past month”, so an entry there is a snapshot, not a deadline.

How SEOgrinder helps, and a flaw on our own site

SEOgrinder is our tool; we build it. It removes nothing. It checks what decides whether your removal holds. The free scan at SEOgrinder covers these points (names as in the English interface):

• Unknown addresses. In the “Page on Google” tab, the “Indexing” card shows “Unknown addresses return 404 correctly” or “Unknown addresses return 200 instead of 404”. The second case becomes the task “Made-up addresses return 200 instead of 404”. The probe asks your site for an address with a random name; a redirect to the home page counts as the same problem.
• A leftover noindex. If you scan a page that should be in search and it still carries the rule, a task appears: “Page is excluded from Google” for the meta tag, “HTTP header excludes the page from Google” for X-Robots-Tag.
• Redirect chains. A task ending in “redirects in a row” names the number of hops and advises to point the first address straight at the final one.
• What still points at a removed page. Tasks such as “internal links are broken” (up to 60 internal links of the scanned page) and “sitemap URLs not answering 200” (a sample of the sitemap) show the links and sitemap entries you forgot.

“Hand over to AI” turns a task into a briefing for a coding agent, and “Check again” runs a fresh scan afterwards. One limit: SEOgrinder cannot judge whether the page you redirect to is a fitting successor, and it cannot tell you when Google drops a page, because Google names no date. For the state of a single address, use the URL Inspection tool.

We ran the probe on ourselves on 4 November 2026. This command printed 200:

curl -s -o /dev/null -w "%{http_code}\n" https://seogrinder.com/seogrinder-pruefseite-xyz123

So our own site had the flaw we tell you to fix: unknown addresses outside the blog answered 200. We fixed that on 5 November 2026: the same command now prints 404, and the response carries the header x-robots-tag: noindex. The blog already behaved correctly: https://seogrinder.com/en/blog/this-page-does-not-exist-xyz123 answered 404 with the same header.

Common mistakes

• Blocking the page in robots.txt to “remove” it. Google then sees no 404, no 301 and no noindex, and a noindex on a blocked page is never read. Google's removal page: “Don't use robots.txt as a way to block your page.”
• Redirecting every deleted page to the home page. Redirect to an equivalent page or answer 404.
• Treating the Removals tool as the final step. It lasts about six months.
• Removing one spelling only. Capital letters, parameters and other addresses that show the same page count as separate URLs.
• A 302 for a permanent move, or a chain of redirects. Use a 301, once, straight to the final address.
• Leaving the page in the sitemap and in your own menus. Dead addresses there work against you.
• Panic about 404 pages. Google wrote in 2011: “this fact alone does not hurt you or count against you in Google's search results.” We found no current Google page that says the opposite, but the post is old, so it is a pointer and not a promise.

FAQ

How do I remove a page from Google permanently?

Make the page return 404 or 410 (or a 301 to its successor), or keep it online with noindex or a password. The Removals tool alone lasts about six months.

How long does it take until a page disappears from Google?

Google names no time for 404, 410 or noindex. The Removals tool usually takes up to a day, a noindex page may need months until Googlebot returns, and a recrawl request can take a few days to a few weeks.

Can I remove a page that belongs to someone else?

Not with the Removals tool, which needs a property you own. Ask the owner to remove or change the page. For a result that still shows a page that is gone or has changed, Google's Search Console help points to its Refresh Outdated Content tool, which does not require ownership. For personal information, Google points to a separate guide, “Remove your personal information from Google”.

Your next step

Pick your row in the table: deleted, replaced or hidden. Make the change, then run the curl check from this article against the old address. Remove the address from your sitemap and from your own links. Then scan your site with SEOgrinder, open the “Page on Google” tab, look at the “Indexing” card, and press “Check again” after your change. For more of the technical basics, see our SEO audit checklist.

Keep reading

• 301 vs 302 redirect: which to use and how many hops Google follows
• Canonical tag explained: when you need one (+ 5 common mistakes)
• Crawled – currently not indexed: what it means and what to do