Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

salam every one, this is a topic from google web master centrale blog:
The Google Webmaster Tools team has code names for each update we release. Today's update is aptly named "Summer Shine".

Here are a few highlights:
  • Our site selector now lists all verified sites that you own, and allows you to search as you type.
  • You can now block non-homepage sitelinks. Before today if you owned example.com, you couldn't block sitelinks for example.com/email.
  • You can now see URL removal requests submitted by other users for any sites you own, and revoke them if necessary. In the past, if another webmaster for your site mistakenly removed a URL on your site and left for vacation it was a difficult process to undo the request.
  • Our "Home" page is much easier to navigate. We now make a clear distinction between verified and unverified sites.
We hope you like the improvements; tell us what you think.

this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
salam every one, this is a topic from google web master centrale blog: Webmaster Level: All

Welcome to the third episode of our URL removals series! In episodes one and two, we talked about expediting the removal of content that's under your control and requesting expedited cache removals. Today, we're covering how to use Google's public URL removal tool to request removal of content from Google’s search results when the content originates on a website not under your control.

Google offers two tools that provide a way to request expedited removal of content:

1. Verified URL removal tool: for requesting to remove content from Google’s search results when it’s published on a site of which you’re a verified owner in Webmaster Tools (like your blog or your company’s site)

2. Public URL removal tool: for requesting to remove content from Google’s search results when it’s published on a site which you can’t verify ownership (like your friend’s blog)

Sometimes a situation arises where the information you want to remove originates from a site that you don't own or can't control. Since each individual webmaster controls their site and their site’s content, the best way to update or remove results from Google is for the site owner (where the content is published) to either block crawling of the URL, modify the content source, or remove the page altogether. If the content isn't changed, it would just reappear in our search results the next time we crawled it. So the first step to remove content that's hosted on a site you don't own is to contact the owner of the website and request that they remove or block the content in question.
  • 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.

If you encounter any issues with the public URL removal tool or have questions not addressed here, please post them to the Webmaster Help Forum or consult the more detailed removal instructions in our Help Center. If you do post to the forum, remember to use a URL shortening service to share any links to content you want removed.

Edit: Read the rest of this series:
Part I: Removing URLs & directories
Part II: Removing & updating cached content
Part IV: Tracking requests, what not to remove
Companion post: Managing what information is available about you online

this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
salam every one, this is a topic from google web master centrale blog:



As the days grow longer and summer takes full stage, many of us are flocking to patios and parks to engage in the time-honored tradition of grilling food. When it comes to cooking outdoors, the type of grills used span a spectrum from primitive to high tech. For some people a small campfire is all that's required for the perfect outdoor dining experience. For other people the preferred tool for outdoor cooking is a quad grill gas-powered stainless steel cooker with enough features to make an Iron Chef rust with envy.



An interesting off-shoot of outdoor cooking techniques is solar cooking, which combines primitive skills and modern ingenuity. At its most basic, solar cooking involves creating an "oven" that is placed in the sun and passively cooks the food it contains. It is simple to get started with solar cooking because a solar oven is something people can make themselves with inexpensive materials and a bit of effort. The appeal of simplicity, inexpensiveness and the ability to "do it yourself" has created a growing group of people who are making solar ovens themselves.
How all this relates to webmasters is that the webmaster community is also made up of a diverse group of people who use a variety of tools in a myriad of ways. Just like how within the outdoor cooking community there's a contingent of people creating their own solar ovens, the webmaster community has a subgroup of people creating and sharing their own tools. From our discussions with webmasters, we've consistently heard requests to open Webmaster Tools for third-party integration. The Webmaster Tools team has taken this request to heart and I'm happy to announce that we're now releasing an API for Webmaster Tools. The supported features in the first version of the Webmaster Tools API are the following:
  • Managing Sites
    • Retrieve a list of your sites in Webmaster Tools

    • Add your sites to Webmaster Tools

    • Verify your sites in Webmaster Tools

    • Remove your sites from Webmaster Tools

  • Working with Sitemaps
    • Retrieve a list of your submitted Sitemaps
    • Add Sitemaps to Webmaster Tools

    • Remove Sitemaps from Webmaster Tools



Although the current API offers a limited subset of all the functionality that Webmaster Tools provides, this is only the beginning. Get started with the Developer's Guide for the Webmaster Tools Data API to begin working with the API.



Webmasters... fire up your custom tools and get cooking!

this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Powered by Blogger.