Old Page Still Appears in Google? How to Remove Outdated Search Results

Why an old or deleted page can still appear in Google

Google does not watch every page continuously. It crawls the web on a schedule that reflects how often a site usually changes, how important the page appears to be, and how much crawl capacity the site can absorb. A busy news homepage may be revisited many times a day. A quiet page on a small business site may go weeks between visits. Until Google returns to a page, what you see in search reflects the last time it looked, not the state of the page right now.

• Deleting a page from a website and removing it from Google are two separate events, and the second follows the first with a delay.
• A changed title or description can keep showing the old wording until the page is crawled again and the new version is processed.
• A URL can stay indexed while the content on it changes, which is why you sometimes see an old snippet attached to a page that now says something entirely different.
• The same content may exist on more than one address, for example with and without www, http and https, tracking parameters, or a print version.
• Redirects, canonical tags and duplicated pages can send Google to a version of the URL you did not intend to check.

None of this requires technical knowledge to work with. It only means that before you submit anything, you need to know exactly which URL Google is showing and what that URL returns today.

First check whether the page actually still exists

Start with the result itself, not with a removal form. Copy the exact URL shown in the Google result, including any subfolder or parameters, and work through the following checks. This takes a few minutes and it decides everything that follows.

1. 1 Open the URL directly in a private or incognito window so your own history and cache do not colour the result.
2. 2 Decide what loads: the old content unchanged, the same page with the sensitive text removed, a completely different page, an error, or a redirect.
3. 3 If you see an error page, note whether it is a genuine 404 or 410 response, or a friendly page that still returns a normal status. Some sites show a not found message while technically returning a working page, and Google treats those differently.
4. 4 If it redirects, note the address you land on and whether the old information appears there.
5. 5 Search a distinctive sentence from the old content in quotation marks to see whether another copy is indexed under a different address.
6. 6 Check Google Images separately, because images are indexed on their own and can survive the removal of the page that hosted them.

Write down the outcome for each URL. If several results are involved, treat each one as its own case, because they will not all need the same request.

Choose your next step: deleted, changed or still live?

Use the checks above to identify the state of the exact indexed URL. A deleted page, a changed page with a stale snippet, and live unwanted content need different responses. Then follow the owner or non-owner guidance below.

I own or manage the website

If you control the source, fix it there first. The Google Search Console Removals tool can temporarily hide a result for about six months for a verified property. It does not delete the page or provide a permanent fix; the result can return unless you also make an appropriate lasting change.

• For a page that is genuinely gone with no suitable replacement, return a real HTTP 404 (Not Found) or 410 (Gone) response at that URL. Removing a menu link or showing a 'page not found' message is not enough.
• If the page should stay accessible to visitors but not appear in Google Search, use a noindex robots meta tag or X-Robots-Tag response header. This is not privacy protection: anyone with the link can still open a public page.
• If only some text needs changing and the page should stay indexed, update it at the source and check titles, headings, captions and other visible copies. A recrawl request in Search Console is a prompt, not a guaranteed update or deadline.
• Check for soft 404s: an error or empty page that still returns 200 OK can be classified by Google as a soft 404. Do not rely on that classification; return the correct 404 or 410 status for a removed page.
• Do not block the URL in robots.txt before Google can crawl and see the removal status or noindex directive. A robots.txt block prevents that check and does not itself remove an indexed URL.

Keep the lasting change in place and check the result and Search Console reports over time. Google's permanent removal guidance and noindex guidance explain the technical requirements. Neither temporary hiding nor a recrawl request promises a particular processing time.

I do not control the website

You cannot change another site's HTTP status, noindex settings or Search Console property. If the page has gone or the relevant information has genuinely been removed, use Google's Refresh Outdated Content tool. If it is still live, contact the publisher with a specific correction or removal request, or check whether Google's personal information removal policies apply. Search removal and deleting the source page are separate outcomes.

If a lawful, accurate article stays online and no removal ground applies, a refresh request will not solve it. Search suppression may be an option, but it strengthens other results rather than deleting the article, and ranking changes cannot be guaranteed.

How to request a refresh for a page you do not own

For a page you do not own, follow Google's official Refresh Outdated Content guidance. The free tool is for a page or image that no longer exists, or a page whose relevant content has significantly changed. It brings search results into line with the source; it is not a complaints channel or a way to remove a live page because it feels unfair.

1. 1 Confirm the source has changed. The wording you want gone must no longer be on the live page, or the page itself must be gone.
2. 2 Open Google's Refresh Outdated Content tool and sign in with a Google account. If you own the page, use the Search Console guidance above instead.
3. 3 Submit the exact URL as it appears in the search result. If the indexed URL differs from the one you normally use, submit the indexed one.
4. 4 Indicate whether the page has been removed entirely or has changed, and where asked, point to the specific words that are no longer present.
5. 5 Submit one request per URL, then keep a record of each submission so you can track which results have been dealt with.
6. 6 Re-check the result in a private window a few days later rather than relying on a previously loaded result in your browser.

Google's tooling, eligibility rules and interface change from time to time, so treat its own help documentation as the authority rather than any third-party walkthrough, including this one. What has stayed constant is the underlying principle: the tool aligns the index with reality, it does not overrule reality.

What happens after you submit a request?

Requests are assessed automatically and, in some cases, by review. There are several realistic outcomes and it is worth knowing them in advance so you can read the response correctly.

• Google updates or drops the stale result, and the stale title, snippet or outdated indexed information stops appearing.
• Google checks the live page, finds the information still present, and declines the request.
• The request is rejected for a procedural reason, most often the wrong URL or a page that has not actually changed.
• The page is recrawled naturally before your request is processed, and the result updates on its own.
• The result changes for the URL you submitted while another indexed copy of the same content keeps appearing.

Processing time varies and is not something Google commits to. Straightforward refreshes on a deleted page are often handled quickly, while others sit for longer. Treat any specific number of days you read online as an anecdote rather than a service level, and check the result yourself rather than assuming nothing has happened.

Why Google may reject an outdated content request

Rejections are common and they are usually informative. In practice, nearly all of them fall into a handful of patterns.

• The information is still visible somewhere on the live page, including in a comments section, an image caption, a related-articles module or the page title.
• A slightly different version of the wording remains, so the page has not changed in the way the request claims.
• The URL submitted is not the URL Google has indexed, for example a version with parameters stripped or a mobile or AMP variant.
• The content exists on another version of the same page, such as a category archive, a tag page or a paginated listing.
• Google has already updated the result, so there is no remaining stale information for the tool to refresh. Check the current result rather than a previously loaded results page.
• The real issue is privacy or safety rather than staleness, which means a different policy and a different form apply.
• The request is an attempt to remove an entire live article using a tool designed to refresh stale information.

A rejection does not close the door. It usually means the diagnosis needs revisiting: either the source has not changed as much as assumed, or the correct route was never the outdated content one.

What if the page was removed but another result still shows the information?

Removing one URL rarely finishes the job, because content on the open web tends to exist in more than one place. Each indexed copy is its own case and needs its own assessment.

• Copied or republished content on aggregator sites and blogs that lifted the original text.
• Syndicated versions where a publisher licensed the article to other outlets, each with its own address.
• Scraped versions that reproduce the page automatically, often with the same wording and a different domain.
• Alternative URLs for the same page, such as archive copies, AMP versions, print views or parameterised links.
• Different publisher URLs where the same story was updated, re-slugged or moved into an archive section.
• Images indexed independently of the page, which can keep appearing after the article itself is gone.
• Snippets generated from other text on the page, such as a sidebar or a list of related headlines, which can keep an old phrase visible.

Work from a written list of every indexed URL rather than from what you remember seeing. Clearing three results and missing a fourth leaves the problem intact for anyone searching your name.

What if Google will not remove the result?

When a refresh request is not available or has been declined, there are still legitimate routes. None of them is a shortcut, and the right one depends on who controls the content.

• Correct or update the source. If you control the page, remove the wording, then use Search Console to request a recrawl where available once the change is live.
• Contact the publisher or site owner with a specific, verifiable request. Corrections and updates succeed far more often than demands for deletion.
• Use the applicable Google removal process if the content genuinely qualifies under a published policy, for example exposed contact details or non-consensual imagery.
• Use privacy or legal channels where they truly apply. In Australia that can mean a correction request to an organisation covered by the Privacy Act 1988, a complaint to the OAIC, or a report to the eSafety Commissioner for online abuse categories.
• Consider suppression when lawful, accurate content cannot be removed, so that stronger results outrank it over time.

It is also worth being precise about what suppression does. It does not delete the source page and it does not remove the result from the index. It changes what ranks above it. Anyone who tells you otherwise is selling something.

When professional help may make sense

A single stale URL on a page you control is a do-it-yourself job, and you should not pay anyone for it. Outside help earns its place when the diagnosis is genuinely unclear or the volume makes careful handling difficult.

• Several URLs are involved and they are not all in the same situation.
• The wrong removal route has already been attempted and the record needs untangling.
• A publisher is involved and the approach needs to be documented and specific.
• Requests keep failing and it is not obvious which assumption is wrong.
• Personal information appears across multiple sources, including data brokers and directories.
• Harmful results remain live and cannot be dealt with through an outdated content request at all.

Not sure whether your result is outdated, removable or still live? Search Cleanup Australia can review the URLs and identify the most realistic next step, including telling you when the answer is to wait for a recrawl and do nothing else.