- On-page SEO
- Tutorial
How to Remove a Blog Post From Google Search
Editorial responsibility: SearchCub
To take a blog post out of Google Search for good, delete it so its address returns a 404 or 410 error, or keep it online with a noindex rule; Search Console's Removals tool only hides a post for about six months.
Google drops the post from its results once it recrawls the address and finds the error or the rule (Google: HTTP status codes; Google: noindex). For an ordinary deleted post, that is all you need. Search Console Help lists old pages that now return 404 among the jobs the Removals tool isn't for: Google's crawlers see the change as they recrawl, and the pages leave the results without an urgent request (Search Console Help: Removals tool, checked on 8 October 2026). Save the tool for a post that has to disappear quickly.
Below are the routes, how long Google says each one takes, and what to do about a post on a site you don't own.
Decide what should happen to the post
Pick the case that fits before you change anything:
The post is gone for good. Delete it, so its address returns a 404 or 410 error.
A newer post replaces it. Point the old address at the new post with a permanent (301) redirect instead. Google's redirects guide (last updated 14 April 2026) names sending visitors from a removed page to a new one as a use for redirects, and says a permanent redirect shows the new address in results.
Readers should still find it on your blog, but searchers shouldn't. Keep it published and add a noindex rule.
Only part of it is wrong or out of date. Update the post instead of deleting it. Google's removal page (last updated 10 December 2025) counts updating a page's content as one of the permanent ways to take information out of its results.
Something in it has to leave the results quickly, such as a personal detail. Edit it out of the post and use the Removals tool to clear the post's snippet; if the whole post must go, make one of the permanent changes below, then use the tool to hide the post.
If you're unsure whether the post still brings readers from search, check how your pages perform in search before you delete anything. An updated post keeps its address, so links to it keep working.
Make the removal permanent
Google's removal page and its Removals tool help list three permanent fixes:
Delete the post, and make sure your server answers its address with a 404 (Not Found) or 410 (Gone) status code. Remove non-HTML files, such as a PDF version, from your server completely.
Put the post behind a password, so only the readers you let in can open it.
Add a noindex rule, which keeps the post out of Google's results while it stays on your blog.
404 or 410? Google treats them the same. Its crawler documentation says Google doesn't index a URL that returns either code, and drops one that was already indexed (Google: HTTP status codes, last updated 4 February 2026). What matters is that your blog really sends one. If a deleted post shows a not-found message but sends a success code, that's a soft 404, and Search Console Help recommends a real 404 code for pages that are truly gone. Also update any of your own posts that link to the deleted one, so readers don't land on an error page.
Noindex or delete? Google's removal page calls removing or updating the content the most secure way to keep it out of search engines that might ignore noindex, and it stops people opening the page too. Noindex only keeps a page out of Google's results; readers and search engines that don't support noindex can still reach it. The Removals tool help also rates noindex as less secure than the other two fixes.
To add noindex, put this line in the post's HTML head, or send the same rule as an X-Robots-Tag: noindex HTTP header (Google: Block Search indexing with noindex, last updated 10 December 2025):
<meta name="robots" content="noindex">On a platform such as WordPress, Wix or Blogger, Google notes that you may not be able to edit the HTML yourself, and the platform may offer a search engine setting instead. Blogging platforms and SEO shows which platforms let you noindex a single post.
Don't block the post in robots.txt. Google's robots.txt guide says the file "is not a mechanism for keeping a web page out of Google" (Google: Introduction to robots.txt, last updated 10 December 2025). A blocked address can still be indexed when other pages link to it, and Google never reads a noindex rule on a page it isn't allowed to crawl.
If the post's images must go too, Google covers them on a separate page about removing images hosted on your site (last updated 10 December 2025). Unlike pages, images can be kept out with a robots.txt rule or a noindex X-Robots-Tag header; if your platform offers neither, Google says you might need to delete the image files. For an urgent case, the Removals tool accepts image addresses too.
Hide a post fast with the Removals tool
The Removals tool hides a post from Google's results for about six months. It works only for an address in a Search Console property you own; if you haven't set one up, what is Google Search Console? walks you through it. These steps follow Search Console Help as checked on 8 October 2026:
Make the permanent change first, if you can. A temporary block doesn't stop Google from crawling the post. If you file the request before making the permanent change, Google's help says to cancel it afterwards and file it again, which clears the page from the index if Google crawled it in between. To cancel, find the request in the tool's history table, click the menu button next to it and choose Cancel request.
Copy the exact address. Google needs the URL exactly as it appears in search results, and a change in capitalization makes a different URL. Open the post's address and copy it from your browser's address bar, leaving out anything after a # sign and any optional parameters.
Open the Removals tool, select the Temporary Removals tab and click New Request.
Choose the removal. Select Temporarily remove URL, enter the address and select Remove this URL only. To hide every address under one folder, Remove all URLs with this prefix blocks every address that starts with what you enter. Check the prefix: Google's help shows that one without a trailing slash, such as
/page, also matches/pageB.Select Next. Google says a request usually takes up to a day to process and isn't guaranteed to be accepted. If it's denied, click Learn more to see why.
Repeat for every other address that shows the post, such as versions with different capitalization or extra parameters. One request already covers the http and https, and the www and non-www, versions of an address, but not other subdomains such as
m..
Search Console Help is blunt about relying on the tool: "Using the tool alone won't work." When the block ends, the post can come back unless a permanent fix is in place. The tool also hides the post from Google Search only; the page itself and other search engines are untouched.
One more detail matters if you reuse addresses. When the address already returns an error such as 404 at the time you file, Google treats the page as gone and lets the block expire. Anything published at that address later counts as a new page that can appear in results.
Clear an outdated snippet after editing a post
If you edited a post to take something out, Google's result can keep showing the old text in its description until the page is indexed again. In the Removals tool, open the Temporary Removals tab, click New Request, choose Clear snippet in search, enter the address and select Next. The address must match exactly, down to an extension such as .html.
Search Console Help says Google then wipes the description under the result until it indexes the page again; in the meantime the result shows something like "No page description available." Until that reindexing, the post can still turn up for searches that match the removed words, but those words won't appear in the snippet.
What about Google's cached copy? There is no cached link to clear any more. Google's robots meta tag documentation (last updated 24 March 2026) says "the cached link feature no longer exists", and the Removals tool offers only the two options above.
When the post is on a site you don't own
A guest post, a copy of your post on another site or an old blog you no longer control can't go through the Removals tool, because the tool needs a property you own. Ask whoever runs that site to delete or update the page first. Then use Google's Refresh Outdated Content tool, which updates results for pages that no longer exist or have lost important content (Search Console Help: Refresh Outdated Content tool, checked on 8 October 2026):
Sign in with a Google account and open the tool.
Search Google for the page, right-click its link in the results and copy the link address. Don't copy the address text shown in the result, and don't click through and copy it from your browser.
Paste it into the tool and click Submit. If the page still exists, the tool asks for more detail; when it asks for text, enter one or two words that were in the result's snippet but are no longer on the live page.
Come back later to check the request in the list at the bottom of the tool. Processing can take a few days, and a denied request links to the reason.
If the content shows at more than one address, file a request for each. An approved request takes a deleted page out of results; for a page that changed, it removes the old snippet until Google's crawler next visits. The tool can't help while the content is still on the live page, so the site has to change first. If a live page copies your work, that's a different route: Google reviews requests to remove content for legal reasons, such as copyright infringement.
How long each fix takes
A 404, 410 or noindex. Takes effect: when Google next crawls the address. Google's noindex guide warns that, depending on a page's importance on the web, "it may take months for Googlebot to revisit a page". Lasts: as long as the address keeps returning it.
Temporarily remove URL. Takes effect: usually within a day, if Google accepts the request. Lasts: about six months.
Clear snippet in search. Takes effect: usually within a day, if accepted. Lasts: until Google indexes the page again.
Refresh Outdated Content. Takes effect: processing can take a few days. Lasts: a deleted page stays out of results while it's gone; for a changed page, the result is refreshed from the new content the next time Google's crawler visits.
Check that the post is gone
In the Removals tool, the request's status in the Temporary Removals history table reads Temporarily removed once the post is hidden, and Removal expired when the block runs out.
With URL Inspection in Search Console, inspect the old address and click Test live URL to confirm Google can see your permanent change. A deleted or noindexed post should come back as URL is not available to Google; for a noindexed post, Indexing allowed? should say No.
After a temporary removal, don't rely on URL Inspection. Search Console Help says the tool doesn't take temporarily blocked URLs into account, so a hidden post can still show URL is on Google. To see whether the post appears, search Google for its address, which Google calls the definitive test.
In the Page indexing report, a post that returns a 404 may show under Not found (404) after Google recrawls it. Search Console Help says a 404 isn't necessarily a problem for a page removed with no replacement. Googlebot will probably keep trying the address for a while, less and less often, and "there is no way to tell Googlebot to permanently forget a URL".
Where to go next
How to check your website's SEO performance: see which of your pages earn search visits before you decide what to remove.
Soft 404: fix a success response with missing content: confirm a deleted post sends a real not-found response, and choose between restoring, removing and redirecting.
Why Google hasn't indexed your page: the opposite problem, when a post you want in Google is missing.