Remove Cached Page From Google: What Still Works

To remove a cached page from Google, fix the page itself first: delete it so the address returns a not-found or gone response, or change the text so the live page no longer says what you object to. Then, if Google still shows the old copy, use its refresh outdated content form, or the Removals tool in Search Console if you own the site. The old copy cannot be removed while the source still says the same thing.

"Cached" is also a moving target. Google removed the public cached link from search results in 2024, as its own documentation changelog records, so for most people the practical problem is no longer a "Cached" button. It is the stale snippet under a result, a result that still lists a page you deleted, and copies kept by other services. Each has a different owner and a different fix.

This guide separates those three kinds of old copy, gives the order of operations, and says what applies if the page is not yours. It describes the Google help pages read for this guide, and those pages change, so check the live page before you file. It is information, not legal advice.

The short version

Removing a cached copy never starts with Google. It starts with the page: delete it or change it, because a copy of a page that still says the same thing has nothing to be refreshed to.
Google drops an already indexed URL that returns a 4xx status, and treats 404 and 410 the same way. It does this on its own schedule, so a result can linger after the page is gone.
Site owners have the Removals tool: temporary hiding for about six months, or clearing a snippet. Everyone else has a refresh request for pages that have changed or no longer exist.
None of these touches third-party archives or other search engines. They keep their own copies and need their own requests.

What a cached or old copy actually is

A search engine stores a copy of every page it indexes, and shows parts of that copy long after the page changes. The stored copy is what lets it match your search to a page without opening the page. When the live page is edited or deleted, the stored copy and the text shown in results stay as they were until the engine fetches the page again.

Three things get called "the cache", and mixing them up wastes the most time:

The snippet. The two lines of description under a result title. It is built from the stored copy. It is the most common complaint: the page was fixed, but the old sentence still shows in results.
The listing. The result itself, the link and title. A deleted page can keep appearing for a while because the engine has not yet re-fetched the address.
The cached view. A full stored copy that a person could open from the result. Google's Search Liaison confirmed on X on February 1, 2024 that the cached link had been removed. Google's documentation changelog later records that the cache search operator no longer works (September 24, 2024) and that the cached link feature is no longer available in results (October 2, 2024). Read the entries on Google Search Central's documentation updates page. There is no Google cached view left to refresh.

Copies kept by other services, such as web archives, are a fourth kind. They are not Google's and no Google tool reaches them.

Which kind of old copy is yours, and who controls it

Match what you can see to the party that can change it. The first column is what you observe; the last column is the mistake people make most often with it.

What you see	Who controls it	Fix	Common mistake
Old sentence in the snippet, page already edited	Google, until it re-fetches	Refresh request, or Removals tool snippet clear for owners	Filing a removal request when only a refresh is needed
Result for a page that is deleted	Site owner first, then Google	Confirm the address returns not found or gone, then request a refresh	Redirecting everything to the home page, so the address never shows as gone
Page live, content unchanged, you object to it	Site owner or a legal ground	Ask the owner to change it; a refresh will not help	Filing a refresh request on a page that still says the same thing
Page you own, must vanish from results fast	You, through Search Console	Removals tool for temporary hiding, plus a permanent fix	Relying on the temporary block alone
Copy on another site or in an archive	That site or archive	Its own removal process	Expecting Google to reach it

Row three is the one that decides whether your effort will work at all. If the live page still carries the text, a search engine is not showing you something "old": it is showing you something current. No refresh request changes that. The route is a change at the source, a legal route where one exists, or a de-listing request on its own grounds, which the wider removal guides cover.

Fix the source first: the order that works

The sequence matters because each step feeds the next, and skipping one makes the later ones fail. Google's help page describes its refresh form for content that was deleted from a site but still comes up in results, not as a way to change the page.

The order of operations for a stale cached page

Record what Google showsTake dated screenshots of the result, the snippet and the live page. You will need them to see whether a later request worked, and to show the difference to anyone who asks.
Change or delete the live pageEdit the text so it is accurate, or delete the page. If you do not own the site, this is a request to the owner or the host, not to Google.
Check what the address returnsA deleted page should return a not-found or gone status. A page that shows an error message but returns a success status is reported by Search Console as a soft 404 error.
Confirm the page is crawlableIf the page is blocked from crawlers, Google cannot see the change. Unblock it so the new state can be fetched.
Submit the right Google requestA refresh request if you are not the owner or only need the snippet updated, the Removals tool if you own the site and need the result hidden quickly.
Check back and keep the proofSearch the exact phrase and the URL again over the following days. If the old text persists after the refresh is processed, escalate on its real ground.

Step three is where owners lose the most time. Google's documentation says it ignores any content returned with a 4xx status: the status code is the signal, the look of the page is not.

What Google does when a page is deleted

When an indexed page starts returning a 4xx status, Google removes it from the index, and the stored copy goes with it. Google's page on HTTP status codes says that Google does not use the content from URLs that return 4xx status codes, that URLs already indexed and returning 4xx are removed from the index, and that 429 is the exception, treated as a sign the server is overloaded. The page lists 410 among the 4xx codes and gives it no separate rule, so a 404 and a 410 get the same handling there. Read the source for this point on the Google Search Central page on HTTP status codes.

The removal happens when Google next fetches the address, and Google does not state a time for that, so none can be promised. In our experience a deleted page that has been crawled often can drop within days, while a rarely visited page can take weeks, and that is why a result can sit in the listing after the page is gone.

About 6 monthshow long a successful Removals tool request hides a URL

Same handlingfor 404 and 410 on an indexed URL, as Google's status page describes it

Usually a dayfor the Removals tool to process, with no promise

Source: Google Search Central and Search Console help pages on removing a page and on HTTP status codes, read for this guide.

When the page still exists but changed: refresh the snippet

If the live page is now accurate and Google still shows the old text, you ask Google to refresh its copy. Google's Search Help page "Refresh outdated content" covers content that was deleted from a site but still comes up in results, and says the page description or cache might be outdated in that case. It also says that if you have already updated a live page, you do not have to fill out the form, so for a simple edit the first move is to wait for Google to re-fetch and check. It describes the form: use "Request refresh", enter the page URL on the "Page" tab, and submit. For an image, copy the image link from Google Images, choose "New request" then "Image", paste the link and submit. Status is tracked in Search Console under "Refresh outdated content".

The help page does not say who may file and gives no processing time, so none is promised here. It is not a way to remove a page that still says what it said. Read the Google Search Help page on refreshing outdated content for the current wording.

The Search Console help page on the Removals tool adds that requests from people who do not own the site appear in an outdated content history for six months, in two types: outdated snippet removal, where the page still exists but some content was removed, and outdated page removal, where the page no longer exists. Its stated denial reasons are that the flagged content is still on the page, that the submitted URL is not in Google's index, or that a similar request is still pending.

What site owners can do: the Removals tool, noindex and the permanent fix

If you own the site, the Removals tool gives speed and the status code gives permanence, and you need both. Google's help page says the tool hides a page from results on sites you own, with requests usually processed within a day but without a promise, and that a successful request lasts about six months. During that period Google may recrawl the page, but it will not show the updated version until the block expires, unless you make the removal permanent.

The tool offers two different things, and they are easy to confuse. A temporary removal hides the URL, or every URL under a prefix, and the prefix covers www and non-www and http and https. A clear-snippet request removes only the description until Google reindexes the page, and the description may read "No page description available" in the meantime. The page can still appear for searches that match the removed information. The URL must match exactly, including the file extension. The page also states what the tool does not do: it does not remove content from the internet or from other search engines, it does not stop Google crawling, and it does not permanently remove pages.

The permanent options on Google's page about removing a page are these:

Remove or update the content. Google describes this as the most secure option.
Password-protect the page. This keeps crawlers and the public out while letting authorized people in.
Add a noindex tag. Google says a noindex tag stops the page from appearing in Google Search, while users and other search engines can still reach it.
Return 404 or 410. The Removals tool page lists this with the options above as the way to make a removal permanent.

The option that fails is robots.txt. Google's pages warn against using it for removal. The noindex documentation explains why: Google has to fetch a page to see the rule, so if robots.txt blocks the page, the crawler never sees the noindex and the page can still appear in results. The same page says it may take months for Googlebot to revisit a page, which is why the temporary tool is paired with the permanent fix, and it points to the URL Inspection tool for requesting a recrawl. Those two pages are on Google's page on removing a page from Search and its noindex documentation.

A practical detail from the Removals tool page: if you blocked a page before fixing it, unblock and reblock it so the index clears after recrawling. And protect every URL variant, because different addresses can point to the same page.

What applies when you are not the site owner

If the page is not yours, you cannot use the Removals tool, noindex or a status code, so your levers are the owner, the host and Google's own forms. The order is the same, only the first step is a request instead of an edit.

Ask the owner or the host to change or delete the page. A short factual message with the exact URL, the exact text and what is inaccurate or outdated is the version most likely to be acted on. Do not threaten; a heated message tends to produce a refusal and sometimes a second article.
Once the page has changed or gone, check what Google shows, then file a refresh request if the old text persists. Google's Search Console help lists requests from people who do not own the site, and the form asks Google to update what it shows.
If the page has not changed and you have a ground, use that ground. Google's removal families, such as policy requests for private information, are separate from the refresh form and judge the content. Google's page on removing a page from Search points non-owners to its help article on personal information removal.
Do not file a refresh request for text you merely dislike. If the page still says it, the request is denied.

A worked scenario with invented parties shows the sequence. Assume a small business published a post naming a former contractor as having missed a deadline, and the post was wrong. The business edits the post after a written complaint, and the contractor still sees the old sentence in the snippet two weeks later. The contractor, not the site owner, first confirms that the live page no longer carries the sentence, since Google says an updated live page needs no form. The snippet still persists, so the contractor files a refresh request on that exact URL, which now has something to act on. If the snippet persists after Google processes the request, the contractor checks whether the page is blocked from crawlers, which the owner can fix, and asks the owner to confirm. The same facts with an unedited page would end in a denial.

Stage	Who acts	Typical range	What you can check
Day 0: page edited or deleted	Site owner	Same day once asked and agreed	Live page text; status code of the address
Day 0 to 1: request filed	Owner or any user	Minutes to file	Request listed in Search Console history
Day 1 to 7: first re-fetch	Google	Often days for a frequently crawled page	Snippet text for an exact phrase
Week 2 to 6: slow pages	Google	Longer for rarely crawled pages	Whether the URL still lists
Month 6 and later: temporary block expires	Owner	Fixed at about six months	That the permanent fix holds

The ranges are from experience, not from Google, which states no timings for refreshes. A frequently crawled news or business page tends to sit at the short end, a forgotten old page at the long end. The one fixed figure in the table, about six months, is Google's stated length of a successful Removals tool request.

Third-party archives and other search engines keep their own copies

Nothing above touches a web archive or another search engine, so a copy can survive a perfect Google outcome. The Removals tool page says plainly that the tool does not remove content from the internet or from other search engines, and the same is true of a refresh request. The Wayback Machine is the best-known archive and has its own process, handled in a separate guide in this series: the point here is only that it is a different organization, with a different request route, and that archive copies are not fixed by changing the live page. Google no longer offers a cached view, so an old copy of a page now lives mainly in archives and other services. Other search engines and AI assistants keep their own indexes or retrieve pages in their own way. This guide did not read their policies, so treat each as a separate request and check its own help pages.

Mistakes that keep an old copy alive

Most stale copies persist because of a handful of repeatable mistakes, not because Google ignored a good request. Check this list before you refile anything.

Redirecting a deleted page to the home page, or showing a friendly error with a success status. The old address does not show as gone.
Blocking the page in robots.txt. Google cannot fetch the change.
Using the temporary tool as the only fix. The block expires after about six months.
Filing a refresh request on an unchanged page, or on the wrong URL variant. The request has nothing to refresh to.

One boundary matters ethically as well as practically. These tools are for pages that are wrong, outdated or yours. They are not a way to make an accurate, lawful, public-interest page disappear. If a publisher has accurately reported something, editing or deleting is its choice, and a refresh request cannot force it.

The next step if an old copy is hurting you now

Start with the live page, not with a form: confirm what it says and what status the address returns, then choose the one request that matches your position. That sequence takes an afternoon, and it is the one most filings skip.

If this is happening to you now

If the page is not yours and the owner has refused to change it, the route depends on the ground, and filing the wrong form costs weeks. Reputation Partners can review the page, the status and the request history in a private audit and tell you which route fits and where it will fail. Request a private audit.

Questions people ask

How long does a cached page stay in Google after I delete it?

Google gives no fixed time. Its documentation says a URL that already appears in the index and starts returning a 4xx status is removed from the index. The removal happens when Google fetches the address again. A frequently crawled page can drop quickly and a rarely visited one can linger. If it lingers, a refresh request or, for owners, the Removals tool speeds up the visible result.

Can I see Google's cached version of a page anymore?

Not through the search results. Google's Search Liaison confirmed on February 1, 2024 that the cached link had been removed, and Google's documentation changelog says the cache search operator no longer works (September 24, 2024). Google's own cached view is therefore gone. Archives and other services may still hold copies, which are separate requests.

Does the Removals tool delete my page from the internet?

No. Google's help page says the tool does not remove content from the internet or from other search engines, does not stop Google crawling the page and does not permanently remove pages. It hides a URL from Google results for about six months, or clears a snippet until reindexing. To make it permanent, delete or update the page, protect it with a password, or return a not-found or gone status.

Why was my refresh request denied?

The usual reason is that the live page still contains the text you wanted refreshed. Google's Search Console help gives three stated denial reasons for outdated content requests: the content is still on the page, the URL is not in Google's index, or a similar request is still pending. Check the live page and the exact address, then ask the owner to change the page if the text is still there.