Official Google Webmaster Central Blog: URL removal explained, Part III: Removing content that you don't own

Webmaster Central Blog

Official news on crawling and indexing sites for the Google index

URL removal explained, Part III: Removing content that you don't own

Selasa, April 20, 2010

expediting the removal of content that's under your controlrequesting expedited cache removalspublic URL removal toolcontact the owner of the website

Removed or blocked content

If the website owner removes a page, requests for the removed page should return a "404 Not Found" response or a "410 Gone" response. If they choose to block the page from search engines, then the page should either be disallowed in the site's robots.txt file or contain a noindex meta tag. Once one of these requirements is met, you can submit a removal request using the "Webmaster has already blocked the page" option.

Sometimes a website owner will claim that they’ve blocked or removed a page but they haven’t technically done so. If they claim a page has been blocked you can double check by looking at the site’s robots.txt file to see if the page is listed there as disallowed.

User-agent: *
Disallow: /blocked-page/

Another place to check if a page has been blocked is within the page’s HTML source code itself. You can visit the page and choose “View Page Source” from your browser. Is there a meta noindex tag in the HTML “head” section?

<html>
<head>
<title>blocked page</title>
<meta name="robots" content="noindex">
</head>
...

If they inform you that the page has been removed, you can confirm this by using an HTTP response testing tool like the Live HTTP Headers add-on for the Firefox browser. With this add-on enabled, you can request any URL in Firefox to test that the HTTP response is actually 404 Not Found or 410 Gone.

Content removed from the page

Once you've confirmed that the content you're seeking to remove is no longer present on the page, you can request a cache removal using the 'Content has been removed from the page' option. This type of removal--usually called a "cache" removal--ensures that Google's search results will not include the cached copy or version of the old page, or any snippets of text from the old version of the page. Only the current updated page (without the content that's been removed) will be accessible from Google's search results. However, the current updated page can potentially still rank for terms related to the old content as a result of inbound links that still exist from external sites. For cache removal requests you’ll be asked to enter a "term that has been removed from the page." Be sure to enter a word that is not found on the current live page, so that our automated process can confirm the page has changed -- otherwise the request will be denied. Cache removals are covered in more detail in part two of the "URL removal explained" series.

Removing inappropriate webpages or images that appear in our SafeSearch filtered results

Google introduced the SafeSearch filter with the goal of providing search results that exclude potentially offensive content. For situations where you find content that you feel should have been filtered out by SafeSearch, you can request that this content be excluded from SafeSearch filtered results in the future. Submit a removal request using the 'Inappropriate content appears in our SafeSearch filtered results' option.

Webmaster Help Forumdetailed removal instructionsURL shortening serviceEdit: Part I: Removing URLs & directoriesPart II: Removing & updating cached contentPart IV: Tracking requests, what not to removeManaging what information is available about you onlineWritten by Jonathan Simon, Webmaster Trends Analyst

Label: advanced , beginner , intermediate , search results

Hey! Check here if your site is mobile-friendly.

Label

Archive

2020
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2019
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2018
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2017
- Des
- Nov
- Okt
- Sep
- Agu
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2016
- Des
- Nov
- Okt
- Sep
- Agu
- Jun
- Mei
- Apr
- Mar
- Jan

2015
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Mei
- Apr
- Mar
- Feb
- Jan

2014
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2013
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2012
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2011
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2010
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2009
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2008
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2007
- Des
- Nov
- Okt
- Sep
- Agu
- Jul
- Jun
- Mei
- Apr
- Mar
- Feb
- Jan

2006
- Des
- Nov
- Okt
- Sep
- Agu

Feed

Give us feedback in our Product Forums.

Subscribe via email

Enter your email address:

Delivered by FeedBurner

Google
Privacy
Terms