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

Loading...
salam every one, this is a topic from google web master centrale blog:
Webmaster Level: All

We launched a preview of our new Webmaster Tools interface three weeks ago, and received a lot of valuable feedback. Most of you liked the update, appreciating features such as the one-stop dashboard, more top search query data, and the improved menu and navigation.

You offered some constructive feedback as well:
  • You missed the option to switch listing 25, 50, or 100 rows in features such as links to your site. We did not add the option back to select how many rows you would like to see but increased our default to 100!
  • Top search query information differed between the old and new versions. We expected this since we went through a lot of re-engineering to improve the new top search queries backend. We reviewed many of the issues posted on our forums, and verified that the new backend is far more accurate and reliable.
  • Initially, the Sitemaps downloaded and indexed URL counts differed between the two versions. We resolved this issue quickly.
  • Backlinks numbers between the old and the new user interface (UI) may differ since our new UI shows the original anchor (not following redirects) as it's linked on the web. Let's say example.com links to http://google.com, then http://google.com 301s to http://www.google.com/:
    • In the new UI -- only verified site owners of google.com will see examples.com's backlink (because we show the original link prior to any redirects)
    • In the old UI -- verified site owners of www.google.com could see example.com's backlink
  • The new site switcher lists only five sites, and some of you who manage a large number of sites found this limiting. We appreciate the feedback and will work on addressing this limitation in a future release.
From today, only the new user interface will be available (http://google.com/webmasters/tools)! You'll see that in addition to fixing many of the issues users addressed, we took some time to launch a new feature: Change of Address. The Change of Address feature lets you notify Google when you are moving from one domain to another, enabling us to update our index faster and hopefully creating a smoother transition for your users.

Thanks to all the users that took time to give us feedback on the new user interface. To those users using it for the first time today, we hope you enjoy it. As always, your feedback is appreciated.

Posted by Sagar Kamdar, Product Manager, Webmaster Tools Team
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

from web contents: Out with the old, in with the new 2013

salam every one, this is a topic from google web master centrale blog: Webmaster Level: All

To build a great web search engine, you need to:
  1. Crawl a large chunk of the web.
  2. Index the resulting pages and compute how reputable those pages are.
  3. Rank and return the most relevant pages for users' queries as quickly as possible.
For the last several months, a large team of Googlers has been working on a secret project: a next-generation architecture for Google's web search. It's the first step in a process that will let us push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions. The new infrastructure sits "under the hood" of Google's search engine, which means that most users won't notice a difference in search results. But web developers and power searchers might notice a few differences, so we're opening up a web developer preview to collect feedback.

Some parts of this system aren't completely finished yet, so we'd welcome feedback on any issues you see. We invite you to visit the web developer preview of Google's new infrastructure at http://www2.sandbox.google.com/ and try searches there.

Right now, we only want feedback on the differences between Google's current search results and our new system. We're also interested in higher-level feedback ("These types of sites seem to rank better or worse in the new system") in addition to "This specific site should or shouldn't rank for this query." Engineers will be reading the feedback, but we won't have the cycles to send replies.

Here's how to give us feedback: Do a search at http://www2.sandbox.google.com/ and look on the search results page for a link at the bottom of the page that says "Dissatisfied? Help us improve." Click on that link, type your feedback in the text box and then include the word caffeine somewhere in the text box. Thanks in advance for your feedback!

Update on August 11, 2009: [ If you have language or country specific feedback on our new system's search results, we're happy to hear from you. It's a little more difficult to obtain these results from the sandbox URL, though, because you'll need manually alter the query parameters.

You can change these two values appropriately:
hl = language
gl = country code

Examples:
German language in Germany: &hl=de&gl=de
http://www2.sandbox.google.com/search?hl=de&gl=de&q=alle+meine+entchen

Spanish language in Mexico: &hl=es&gl=mx
http://www2.sandbox.google.com/search?hl=es&gl=mx&q=de+colores

And please don't forget to add the word "caffeine" in the feedback text box. :) ]

Posted by Sitaram Iyer, Staff Software Engineer, and Matt Cutts, Principal Engineer this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

from web contents: Help test some next-generation infrastructure 2013

salam every one, this is a topic from google web master centrale blog:
Recently we mentioned some updates in the Webmaster Tools GData API: we've just launched a whole new API, the Message Center GData API, as part of the Webmaster Tools API. The Message Center is the way that Google communicates to webmasters important issues regarding their sites—for example, if there's a problem crawling your site, or if someone has requested a change in crawl rate. Until now it was only possible to access these messages through the Message Center section of Webmaster Tools; but now you can also use GData to access it as a feed. This way you don't need to continually check your messages in Webmaster Tools, you can retrieve the messages feed automatically and be informed as soon as possible of any critical issues regarding your site.
What can I do?
The Message Center GData API lets you retrieve all messages, mark the messages as read or unread, and delete messages. You can do these tasks using the provided Java client libraries, or you can create your own client code based on the protocol information.
  • Retrieve messages: The messages feed contains all the messages sent to your account. These messages have important information about your verified sites. Examples of messages include infinite spaces warnings and crawl rate change notifications.
  • Mark messages as read or unread: In order to keep track of new communications from Google, you can mark your messages as read or unread, the same way that you would manage your inbox. If you retrieve a single message, this message will be automatically marked as read.
  • Delete mesages: It's possible to delete messages using the GData API. However, be careful because if you delete a message through the API it will also be deleted in your Webmaster Tools account, as both interfaces share the same data.
How do I do it?
You can download code samples in Java for all these new features. These samples provide simple ways to use the messages feed. The following snippet shows how to retrieve the messages feed in a supported language and print all the messages:
  // Connect with the service and authenticate
  WebmasterToolsService service
      = new WebmasterToolsService("exampleCo-exampleApp-1");
  try {
    service.setUserCredentials(USERNAME, PASSWORD);
  } catch (AuthenticationException e) {
    System.out.println("Username or password invalid");
    return;
  }
  // Retrieve messages feed
  MessagesFeed messages;
  try {
    URL feedUrl;
    if (USER_LANGUAGE == null) {
      feedUrl = new URL(MESSAGES_FEED_URI);
    } else {
      feedUrl = new URL(MESSAGES_FEED_URI
          + "?hl=" + USER_LANGUAGE);
    }
    messages = service.getFeed(feedUrl, MessagesFeed.class);
  } catch (IOException e) {
    System.out.println("There was a network error.");
    return;
  } catch (ServiceException e) {
    System.out.println("The service is not available.");
    return;
  }
  // Print the messages feed
  System.out.println(messages.getTitle().getPlainText());
  for (MessageEntry entry : messages.getEntries()) {
    if (entry.getRead()) {
      System.out.print("   \t");
    } else {
      System.out.print("new\t");
    }
    System.out.print(entry.getDate().toUiString() + "\t");
    System.out.println(entry.getSubject());
  }
Where do I get it?
If you want to know more about GData, you may want to start by checking out the GData website. The homepage of the Webmaster Tools GData API contains a section on the messages feed, with details about the protocol. You can also download the sample Message Center client form the GData download site. It will show you how to use all the Message Center GData API features.

Written by Javier Tordable, Software Engineer
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

from web contents: Message Center info through our API 2013

Powered by Blogger.
Design by Dev Nasser