Remove Pages and Outdated Content From Google

Something is in Google that should not be. Maybe it is a price list that went live a week early, a staff member’s phone number on an old contact page, a staging site that leaked into the index, or a product you discontinued two years ago that still pulls clicks and disappoints people. Whatever it is, you want it gone today, not whenever Googlebot gets round to it.

The trouble is that Google offers several removal mechanisms, they work at different speeds, and some of them are temporary in ways that catch people out. A request in Search Console can hide a page within a day, yet the page quietly returns six months later if nothing else changed. A robots.txt block looks like a fix but can actually keep a URL in the index longer.

This guide sorts the options by situation: content on your own site versus someone else’s, urgent versus permanent, pages versus images and files, and personal information about you. It covers the exact steps in each tool, the status codes that make removals permanent, and a worked example of a real-world clean-up sequence.

Matching your removal problem to the right Google mechanism

Before opening any tool, answer two questions: do you control the site the content lives on, and do you need it gone from Google only, or from the web as well? Google is explicit that hiding a result and deleting content are different things. Its documentation on removals calls deleting or updating the content itself the most secure permanent fix, because it also stops people reaching the page directly and keeps it out of search engines that ignore noindex.

Your situation	Mechanism to use	Typical speed	Permanent?
Your page, urgent (leak, legal, privacy)	Search Console Removals tool, then a permanent signal	Usually within a day	Only if paired with 404/410, noindex or password
Your page, not urgent	Delete (404/410) or add `noindex`	After next recrawl	Yes
Your page should stay live for users but not appear in Google	`noindex` meta tag or X-Robots-Tag header	After next recrawl	Yes, while the tag stays
Someone else’s page that has changed or been deleted	Refresh Outdated Content tool	A few days	Reflects the live page
Images on your site	robots.txt rule for Googlebot-Image, or noindex header on the image	After next crawl of the image	Yes
Your phone, address or email on any site	Results about you	Request-based review	Hidden in Google; still on the source page
Copied content on another site	Copyright (DMCA) removal request	Review-based	Depends on outcome

The last row deserves its own guide, so if a competitor or scraper has lifted your text, see our walkthrough on dealing with copied content and DMCA takedowns.

Hiding a URL within a day using the Search Console Removals tool

The Removals tool lives in Search Console under Indexing, and it only works for properties you have verified as an owner. If you are not sure whether you are set up as an owner or a full user, sort that out first using our guide to Search Console property setup and permissions, because only owners can submit removal requests.

Copy the exact URL. Google’s help page says you need the precise URL including case, file extension and any parameters that matter. Leave off anything after a #.
Open Indexing > Removals in the correct property and choose the Temporary removals tab, then New request.
Choose “Temporarily remove URL” to hide the page from results, or the snippet-clearing option if the page should stay listed but with its description wiped until Google recrawls it.
Decide between “Remove this URL only” and “Remove all URLs with this prefix”. A prefix request covers every URL that begins with the path you enter, across http, https, www and non-www. It does not cover subdomains, so a staging subdomain needs its own property and request.
Submit separate requests for variants. If /Price-List.pdf and /price-list.pdf both serve the file, each one needs a request.
Check the status the next day. Requests usually process within a day but are not guaranteed to be approved.
Apply a permanent signal straight away (next sections), so the page stays gone after the request expires.

Entering the root of your domain as a prefix hides the entire site. That is occasionally what you want, for example when a development copy was indexed under a separate property, but it is a dangerous button on a production property. Double-check the property selector before you submit.

Why the six-month expiry catches people out

The single most misunderstood fact about the Removals tool is that it hides rather than removes. Google says so plainly:

“A successful request lasts only about six months.”
— Search Console Help, Removals and SafeSearch reports tool

When the six months are up, Google shows whatever its index holds for that URL. If the page still returns a 200 status with indexable content, it can reappear. Google’s own help text frames the tool as the first step in a permanent block, not the whole job. The permanent options it lists are returning a 404 or 410, putting the content behind a password, or adding a noindex tag.

There is one more subtlety. If you used the Removals tool and then made a permanent change, Google’s guidance is that you may need to clear the temporary block and resubmit after the permanent change is in place, so its systems pick up the new state. In practice, set a calendar reminder for five months after any removal request to confirm the page now returns 404, 410 or carries noindex, using the URL Inspection tool live test.

Removals tool alone: hidden for about six months, then may return.
Removals tool plus 404/410: hidden immediately, then dropped for good once recrawled.
Removals tool plus noindex: same outcome, and the page stays available to visitors with the link.
Removals tool plus robots.txt block: risky, because Google can no longer see the noindex or the 404.

404, 410, noindex or a password: choosing the permanent signal

Once the urgent request is in, pick the signal that matches what you want the page to be. Google’s status code documentation removes one common myth here: there is no special fast lane for 410.

“All 4xx errors, except 429, are treated the same.”
— Google Search Central, How HTTP status codes and network errors affect Google Search

The same page explains that Google doesn’t index URLs returning a 4xx code and that already indexed URLs returning 4xx are removed. So choose 404 or 410 based on what is clearer for your own team; many developers use 410 for deliberate deletions so that log analysis can separate them from accidental broken links. For a full reference on codes, see our guide to HTTP status codes for SEO.

Signal	What users see	Google outcome	Best for
404 Not Found	Error page	Dropped after recrawl	Pages deleted with no replacement
410 Gone	Error page	Same as 404 per Google	Deliberate bulk deletions you want to label in logs
301 redirect	The replacement page	Old URL replaced by target	Content that has a genuine successor
`noindex` meta tag	The page as normal	Dropped after recrawl	Pages needed by users (thank-you pages, internal tools)
X-Robots-Tag: noindex header	The file as normal	Dropped after recrawl	PDFs, images and other non-HTML files
Password / login	Login prompt	Crawler cannot access; drops out	Sensitive material that must stay online for some people
robots.txt disallow	The page as normal	May stay indexed as a bare URL	Not suitable for removal

The robots.txt row is where most DIY removals go wrong. Google’s robots.txt introduction warns that a page that is disallowed can still be indexed if other sites link to it, and that robots.txt is not a mechanism for keeping a page out of Google. Its removal guide is shorter still: “Don’t use robots.txt as a way to block your page.” If you need the background, our explainer on robots.txt versus meta robots covers the difference. Implementation details for the tag are in our noindex tag guide.

A redirect only belongs on this list when the old URL has a true replacement. Redirecting a deleted product to the homepage tends to be treated as a soft 404 anyway, so you gain nothing and confuse users. If you are on a platform that cannot send server-side redirects, read our piece on how Google handles meta refresh and JavaScript redirects before improvising.

When the page changed but Google still shows the old snippet

A common variant of the problem: the page is fine now, but Google’s result still shows the old title or description, perhaps an outdated price or a name that was corrected. For your own site, the quickest fix is to request indexing through URL Inspection so Google recrawls the updated page. If the old text is sensitive, the Removals tool’s snippet option wipes the description until the next crawl.

For pages on sites you do not own, Google provides the Refresh Outdated Content tool. Anyone with a Google account can use it, and it handles two cases:

The page or image no longer exists. If Google confirms the URL is gone, an approved request removes the result.
The page still exists but important content was removed or changed. You enter one or two words that appeared in the old snippet but are no longer on the page. Approval removes the snippet until Google recrawls and refreshes the result.

“This tool only updates Google's search result, it does not remove a page from the web.”
— Search Console Help, Refresh Outdated Content tool

Requests move through Pending, Approved, Denied, Expired and Cancelled states. Approved requests expire after 180 days or when the URL no longer exists. If the tool denies your request because the content is still live, the only routes left are asking the site owner to change it, a legal removal request, or one of Google’s personal information policies.

Getting images, PDFs and other files out of results

Images and documents do not have a <head> section, so a meta robots tag is not an option for the file itself. Google’s image removal guide gives two approaches.

The first is a robots.txt rule for Google’s image crawler. Google’s own example blocks a single file:

User-agent: Googlebot-Image
Disallow: /images/dogs.jpg

Google explains that the next time it crawls that image it will see the rule and drop the image from results. You can use wildcards to match several files, or Disallow: / to block every image on the host. This is one of the few cases where robots.txt is the recommended removal method, because image results are built from the crawler’s access to the file.

The second approach is a noindex X-Robots-Tag HTTP header on the image response. This blocks the image wherever it is embedded, including on other sites, but Googlebot must be able to fetch the image to see the header, so do not combine it with a robots.txt block. The page-level noimageindex tag is narrower: it stops images on that one page being indexed, but the same image can still be indexed via other pages that use it.

PDFs, Word documents and spreadsheets follow the same header logic. Add X-Robots-Tag: noindex to the file’s response in your server or CDN configuration, or delete the file so it returns 404. Our guides to the X-Robots-Tag header and PDF SEO show the Apache and Nginx syntax. For urgent cases, put the file URL through the Removals tool first, because header-based removal waits for a recrawl.

Removing your phone number, home address or email with Results about you

When the problem is personal information on a site you do not control, the Search Console tools are no help. Google’s consumer-facing route is Results about you, available in the Google app and on the web. Google’s blog post announcing it was published in May 2022 and updated in September 2022 as the tool rolled out.

According to Google’s help page, removal requests may be approved for results showing your phone number, home address or email address. The workflow:

Open Results about you and select Get started or Settings.
Enter your name and the contact details you want monitored. You can add nicknames, maiden names and several phone numbers, addresses or emails.
Review matches in the “To review” tab and choose Request to remove, or mark a result as reviewed.
Alternatively, search your name, open the three-dot “About this result” panel on a specific result, choose Remove result and follow the contact-info prompts.
Track requests under Removal requests, where statuses include in progress, approved, denied and undone.

Two caveats matter. Results on government, educational and news sites are generally not removed, and an approved removal does not touch the source page:

“Whether your request is approved or denied, the info still exists on the source web page.”
— Google Search Help, Find and remove personal contact info in Google Search results

Turn on notifications so Google alerts you to new matches. For businesses dealing with a wider set of unwanted results, such as old reviews or negative press that is accurate and therefore not removable, the work becomes reputation management rather than removal; see our brand SERP management guide and our online reputation management service.

A worked clean-up: a leaked price list and an indexed staging site

The following is a hypothetical example, but it reflects the sequence we use. A retailer discovers on Monday morning that two things are in Google: a PDF of next season’s trade prices at /downloads/trade-prices-2027.pdf, and roughly 40 pages from staging.example.com, which a developer left open without authentication.

Time	Action	Why
Monday 09:00	Removals tool request for the exact PDF URL, plus its uppercase variant found in a supplier email	Hides it within about a day; each variant needs its own request
Monday 09:15	Delete the PDF so it returns 404 (or move it behind the trade portal login)	Makes the removal permanent once Google recrawls
Monday 09:30	Verify `staging.example.com` as its own Search Console property and submit a prefix removal for the root	Prefix removals do not cross into subdomains, so the main property cannot do this
Monday 10:00	Put HTTP basic authentication on the staging host	Password protection blocks crawlers and people; robots.txt alone would not de-index
Tuesday	Check request status; live-test both URLs in URL Inspection	Confirms 404 and 401 responses are what Googlebot sees
+5 months	Calendar reminder: search `site:staging.example.com` and re-inspect the PDF URL	Catches anything that might return when the six-month requests expire

Notice what the team did not do: add Disallow: / to the staging robots.txt and stop there. That would have stopped Google recrawling the 40 URLs, which means it would never see the authentication response, and the bare URLs could linger. Our guide to keeping staging sites out of Google covers prevention, and for sites with thousands of URLs to retire, our article on managing crawling on large sites explains how bulk 404s and 410s interact with crawl scheduling.

Questions site owners ask about pulling pages out of Google

How long does it take for a removed page to disappear from Google?

A Removals tool request usually takes effect within about a day. A permanent signal such as a 404, 410 or noindex only works after Googlebot recrawls the URL, which can take days for busy pages and weeks or longer for pages Google rarely visits.

Is a 410 faster than a 404 for removing pages?

Google’s documentation says all 4xx errors except 429 are treated the same, so there is no documented speed advantage. Use 410 if it helps your team distinguish deliberate deletions from broken links in logs, but do not expect Google to act on it differently.

Can I remove a page from Google that is on someone else’s website?

Not with the Removals tool, which only works for properties you have verified. If the page has changed or been deleted, use the Refresh Outdated Content tool. If it shows your personal contact details, use Results about you. For copied content, a DMCA notice is the route.

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

Robots.txt stops crawling, not indexing. Google can keep a blocked URL indexed if other pages link to it, and because it cannot crawl the page it never sees a noindex tag. Remove the block and let Google see a noindex or a 404 instead.

Does removing a URL from Google also remove it from Bing?

No. Google’s Removals tool only affects Google Search. Bing has its own content removal tools inside Bing Webmaster Tools, and permanent fixes such as deleting the page or adding noindex work for both engines once they recrawl.

Your Google removal plan for this week

If something urgent is live in Google right now, the order of operations is simple: submit a Removals tool request for every URL variant, apply a permanent signal on the server (404, 410, noindex or a password), live-test with URL Inspection, and set a reminder before the six months run out. If the content is on someone else’s site, choose between Refresh Outdated Content, Results about you and a legal request depending on what the content is.

The prevention side is where most of the value lies: authenticated staging environments, a release checklist that catches documents published to public folders, and a monthly look at the Page indexing report for URLs you do not recognise. If you would rather have a specialist audit what Google holds for your domain and handle the clean-up, our technical SEO team can help. Request a free quote and tell us what needs to come down.

Sources for this Google content removal guide

#removals tool #noindex #search console #technical seo

Written byRohit ChoudharyCo-Founder, My SEO Experts

Rohit Choudhary is the co-founder of My SEO Experts and has more than 14 years of hands-on experience in SEO, paid advertising and digital marketing. Since starting out in 2011 he has helped hundreds of businesses grow through practical, data-driven search strategies, and he also serves as a consulting Digital Marketing Director for several US-based companies.

Website All articles by Rohit →

Keep reading

Ready to grow your business online?

Get a free, no-obligation proposal tailored to your goals and budget.

Get a Free Quote Call Us

How to Remove Pages and Outdated Content From Google Search