How to Remove a Page From Google Search Results
By Neha
To remove a page from Google for good, change the page itself: delete it so it returns a 404 or 410 error, add a noindex tag, or put it behind a password. If it is urgent, also use the Removals tool in Search Console, which hides the page within about a day, but only for about six months. Blocking the page in robots.txt does not remove it.
That is the whole method for a page on your own website. The details matter, though, because each option does something slightly different, and the most common reaction (adding a line to robots.txt) can keep an old page in Google longer, not shorter.
This guide covers pages on your own site, pages on someone else's site, and the mistakes that bring a removed page back.
Short answer: For your own page, pick a permanent method first: delete it (404 or 410), add a noindex tag, or password-protect it. For speed, add a temporary request in Search Console's Removals tool, which Google says lasts about six months. For a page on a site you do not own, ask the site owner to change it, then use Google's Refresh Outdated Content tool once it is gone. Never rely on robots.txt.
Which removal method fits your situation?
People who search "remove page from Google" usually mean one of a few different jobs. The right method depends on two questions: do you own the site, and should the page still exist for visitors? Start with this table.
| Your situation | Best method | Permanent? |
|---|---|---|
| The page should not exist any more | Delete it so it returns 404 or 410 | Yes |
| The page must stay for visitors but not appear in Google | Add a noindex tag | Yes, while the tag stays |
| The page is private (staff list, invoices, test site) | Put it behind a password | Yes |
| The page moved to a new address | 301 redirect to the new page | Yes, the old address is replaced |
| You need it gone from results today | Removals tool, plus one of the above | No, about six months |
| The page is on someone else's website | Ask the owner, then Refresh Outdated Content | Depends on the owner |
| It shows your personal details | Google's personal information removal request | Depends on Google's review |
Google's guide to removing a page hosted on your site lists the same three permanent choices for your own page: remove or update the content, password-protect it, or add a noindex tag. It calls removing the content "the most secure way", because a noindex tag only keeps the page out of Google Search while visitors with the link can still open it.
How do you remove a page from your own website permanently?
Change what Google finds at the address, then let Google see the change. Here are the steps.
- Decide whether the page should exist. An old offer, a closed branch or a duplicate draft can usually be deleted. A thank-you page or a members' page must stay for visitors, so use noindex instead.
- If you delete it, check the error code. The address should return a 404 (not found) or 410 (gone). Google's page on HTTP status codes says that for these errors "the indexing pipeline removes the URL from the index if it was previously indexed." Do not redirect it to your home page, which Google may treat as a soft 404, a page that behaves like an error without saying so.
- If it moved, redirect it. When the content now lives at a new address, a permanent 301 redirect is the right answer, not removal. The Redirect Generator turns old and new addresses into rules for your server.
- If it must stay, add noindex. Put
<meta name="robots" content="noindex">in the page's head section, or send the matching X-Robots-Tag header for PDFs and images. The Meta Robots Tag Generator builds the tag and the header, with a plain-English check of what each does. - Make sure Google can still read the page. It must not be blocked in robots.txt, or Google never sees the noindex. The Robots.txt Tester shows whether Google is allowed to read an address and which line decides.
- Confirm the result. Run the address through the Indexability Checker. It checks for a noindex tag, an X-Robots-Tag header, a canonical pointing elsewhere and an error status code.
- Ask Google to recrawl. In Search Console, inspect the address and request indexing so Google visits sooner.
How do you use the Removals tool in Search Console?
The Removals tool hides a page from Google quickly, but it is temporary. Google's Removals tool help page says it lets you "temporarily block pages from Google Search results on sites that you own", and that "a successful request lasts only about six months." Only verified owners of the Search Console property can use it.
To make a request:
- Open Search Console for your site and choose Removals from the menu.
- Start a new request and choose Temporarily remove URL.
- Enter the address. Choose Remove this URL only for one page, or Remove all URLs with this prefix for a whole folder, such as
/old-offers/. - Submit. Google says the request "usually takes up to a day to process, and is not guaranteed to be accepted."
There is a second option, Clear snippet in search, which Google says "wipes out the page description snippet in Search results until the page is indexed again." Use it when the page stays but its old text, such as a former price, still shows under the result.
Three points from the same help page are easy to miss:
- The request matches every version of the address: "All variations of http and https, www and non-www match."
- It does not stop crawling. Google says blocking "does not prevent Google from crawling your page, only from showing it in Search results."
- When it ends, the page "is eligible to appear in Search results again unless you file another removal request." So the permanent fix in the section above is not optional.
The tool "removes content only from Google Search", so Bing and other engines need their own steps. Our Bing Webmaster Tools guide covers Bing.
Why doesn't robots.txt remove a page from Google?
Because robots.txt controls reading, not showing. Google's robots.txt introduction says it "is not a mechanism for keeping a web page out of Google", and that a blocked page's "URL can still appear in search results, but the search result won't have a description."
The trap works like this. You add Disallow: /old-page/ to robots.txt. Google stops visiting the page, so it never sees that you deleted it or added noindex. If other sites still link to it, the address can stay in results, now with no description. The page you wanted gone is harder to remove than before.
Google's guide to blocking indexing with noindex says it plainly: "For the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file." The Removals help page adds: "Do not use robots.txt as a blocking mechanism." And if you blocked the page before fixing it, Google's advice is to "unblock and then reblock the page."
Our robots.txt guide explains what the file is actually for. The short version: use it to keep bots out of areas that waste their time, never to hide a page.
404, 410, noindex or redirect: what is the difference?
All four can take a page out of Google, but they suit different cases.
| Method | What visitors see | What Google does | Use it when |
|---|---|---|---|
| 404 Not Found | An error page | Drops the address from the index once it recrawls | The page is gone with no replacement |
| 410 Gone | An error page | Google's status code page applies the same rule to all 4xx errors | Same as 404; either is fine |
| noindex tag | The normal page | Drops the page from results once it recrawls | The page must stay for visitors |
| 301 redirect | The new page | Replaces the old address with the new one | The content moved |
| Password | A login screen | Cannot read the content | Private pages, staging sites |
On 404 versus 410, Google's status code page treats them under one rule for 4xx errors, so do not spend time choosing. What matters is that the page really returns the error code, not a page saying "not found" with a normal 200 code. Our guide to fixing broken links and redirects shows how to check this.
The time it takes is the weak point of every permanent method: Google has to revisit the page first. Google's noindex guide warns that "it may take months for Googlebot to revisit a page" in some cases, which is why the Removals tool exists for urgent cases.
How do you remove a page that is on someone else's website?
You cannot remove it from Google directly, because only the site owner controls the page. The usual path has two steps.
- Ask the owner to change or delete it. This works for old directory listings, a former employer's staff page, an outdated news mention or a copy of your content. Be polite and specific: give the exact address and what needs to change. For Justdial, IndiaMART and similar directories, use their own listing settings or support channel.
- Once it has changed, ask Google to refresh. Google's Refresh Outdated Content tool is for pages you do not own. Its help page says it works when "the page or image no longer exists or is significantly different from the current version", and that it "will not remove a page or image that still exists and has not changed."
If the page shows your personal information, such as your phone number, home address or identity documents, Google has a separate process. Its personal information removal page lists the kinds of content it considers, and notes that "even if Google removes something from Google Search, it might still be on the internet." For anything with a legal angle, such as defamation, speak to a lawyer; this guide covers search only.
A worked example: a coaching centre's old fee page
An imaginary coaching centre in Pune ran a 2025 batch page listing old fees and a teacher's personal mobile number. The teacher has left, and parents keep calling her about admissions. The page still appears when people search the centre's name.
The owner does three things on the same day:
- Deletes the page so the address returns a 404, and checks it with the Indexability Checker.
- Files a Temporarily remove URL request in Search Console for the exact address, so it drops out of results within about a day.
- Removes the old address from the sitemap and from the menu.
The owner does not touch robots.txt. When Google next crawls the address and sees the 404, the page should leave the index, so there is nothing to renew when the temporary removal ends after about six months.
One more check: the same number appeared on an old directory listing. The owner edits that listing through the directory's own dashboard, then uses Refresh Outdated Content so Google updates the result. If you need to see which of your pages Google has saved, the Google Index Checker lists them using your Search Console data. Our Search Console guide shows the rest of the setup.
Frequently asked questions
How long does it take to remove a page from Google?
With the Removals tool, Google says a request usually takes up to a day to process. Permanent methods such as a 404 or noindex take effect only after Google recrawls the page, which can be days for busy pages and much longer for rarely visited ones. Use both together if the page is urgent.
Is the Removals tool permanent?
No. Google says a successful request lasts only about six months. After that, the page can appear again unless it now returns 404 or 410, carries a noindex tag or sits behind a password.
Can I remove a page from Google without deleting it?
Yes. Add a noindex tag and keep the page live. Visitors with the link can still open it, but Google drops it from results once it recrawls the page. Make sure robots.txt does not block it, or Google will not see the tag.
Can I remove someone else's page from Google search results?
Not directly. Ask the site owner to change or delete it, then use Google's Refresh Outdated Content tool. If the page shows personal details such as your phone number or address, use Google's personal information removal request instead.
How do I remove an old image or PDF from Google?
Delete the file so it returns a 404, or send an X-Robots-Tag noindex header with it, since a PDF or image cannot hold a meta tag. For speed, add a temporary request in the Removals tool for the file's address.
