MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

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

We’ve been hearing this question for many years from webmasters. That’s why we built features such as the Safe Browsing API, the malware review form, and our Malware details Labs feature.

As of today, once we notice your site is infected, we’ll do our best to send an e-mail to the address you have associated with your account in Webmaster Tools. We believe malware is such an important issue for site owners that being quickly informed is beneficial to you and your website’s visitors.

In addition, we’ve promoted our Malware details feature out of Labs and placed it under Diagnostics. The malware data is now updated four times faster than before, we’ve updated our algorithms for identifying injected content, and we’re now able to identify exploits which we were unable to catch earlier.



We hope this allows you to stay up-to-date with any malware issues we detect on your site, and to fix them quickly.

As always, please let us know if you have any feedback or questions about how to fix malware-related issues in our Webmaster Help Forum.


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

Seo Master present to you: Google I/O just recently came to a close, but it won’t be long before we start gearing up for next year. And we’d like to make sure it’s on your calendars!

May 10-11, 2011
Moscone West, San Francisco

We’ll keep you updated when registration opens for I/O 2011 on the Google Code Blog, Twitter, and Buzz.


Posted by Christine Tsai, Google I/O Team
2013, By: Seo Master

salam every one, this is a topic from google web master centrale blog: 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

At Google, we continually strive to improve our algorithms to keep search results relevant and clean. You have been supporting us on this mission by sending spam reports for websites that violate our Webmaster Guidelines, using the spam report form in Google Webmaster Tools. While you might not see changes right away, we take your reports seriously and use them to fine-tune our algorithms -- the feedback is much appreciated and helps us to protect the integrity of our search results. We also take manual action on many of these spam reports. A recent blog post covers more information on how to identify webspam.

For those of you who regularly report spam, or would like to do so, we’ve now published a Chrome extension for reporting spam that makes the process more convenient and simple. The extension adds “Report spam” links to search results and your Web History, taking you directly to the spam report form and autocompleting some form fields for you. With this extension, Google’s spam report form is always just one click away.

The Google Webspam Report Chrome extension provides further tools to help you quickly fill out a spam report:

• a browser button to report the currently viewed page
• an option to retrieve recent Google searches from your Chrome history
• an option to retrieve recently visited URLs from your Chrome history

As before, you need to be logged into your Google Account to report spam. You can find a more detailed walkthrough of the use cases and features in this presentation and on the Chrome Extensions Gallery page, where you can also provide feedback and suggestions. We hope that you find this extension useful and that you continue to help us fight spam.

The extension is available in 16 languages. If your Chrome browser is set to a language supported by the extension, it will automatically use the localized version, otherwise defaulting to English.

Note: We care about your privacy. The Google Webspam Report Chrome extension allows you to access your personal Chrome history for the purpose of reporting spam, but does not send data retrieved from it to our servers. The source code of the extension has been published under an open source license.

Posted by Manuel Holtz, Support Engineer, Search Quality teamthis is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

Seo Master present to you:
By Yang Li, Research Scientist

Gesture Search from Google Labs now has an API. You can use the API to easily integrate Gesture Search into your Android apps, so your users can gesture to write text and search for application-specific data. For example, a mobile ordering application for a restaurant might have a long list of menu items; with Gesture Search, users can draw letters to narrow their search.


Another way to use Gesture Search is to enable users to select options using gestures that correspond to specific app functions, like a touch screen version of keyboard shortcuts, rather than forcing hierarchical menu navigation.

In this post, I’ll demonstrate how we can embed Gesture Search (1.4.0 or later) into an Android app that enables a user to find information about a specific country. To use Gesture Search, we first need to create a content provider named CountryProvider, according to the format required by Android Search framework. This content provider consists of 238 country names.

Then, in GestureSearchAPIDemo, the main activity of the app, we invoke Gesture Search when a user selects a menu item. (Gesture Search can be invoked in other ways depending on specific applications.) To do this, we create an Intent with the action "com.google.android.apps.gesturesearch.SEARCH" and the URI of the content provider. If the data is protected (for example, see AndroidManifest.xml), we also need to grant read permission for the content URI to Gesture Search. We then call startActivityForResult to invoke Gesture Search.

public boolean onCreateOptionsMenu(Menu menu) {
    super.onCreateOptionsMenu(menu);
    menu.add(0, GESTURE_SEARCH_ID, 0, R.string.menu_gesture_search)
        .setShortcut('0', 'g').setIcon(android.R.drawable.ic_menu_search);
    return true;
  }

  @Override
  public boolean onOptionsItemSelected(MenuItem item) {
    switch (item.getItemId()) {
      case GESTURE_SEARCH_ID:
        try {
          Intent intent = new Intent();
          intent.setAction("com.google.android.apps.gesturesearch.SEARCH");
          intent.setData(SuggestionProvider.CONTENT_URI);
          intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
          intent.putExtra(SHOW_MODE, SHOW_ALL);
          intent.putExtra(THEME, THEME_LIGHT);
          startActivityForResult(intent, GESTURE_SEARCH_ID);
        } catch (ActivityNotFoundException e) {
          Log.e("GestureSearchExample", "Gesture Search is not installed");
        }
        break;
    }
    return super.onOptionsItemSelected(item);
  }

In the code snippet above, we also specify that we want to show all of the country names when Gesture Search is brought up by intent.putExtra(SHOW_MODE, SHOW_ALL). The parameter name and its possible values are defined as follows:

/** 
   * Optionally, specify what should be shown when launching Gesture Search.
   * If this is not specified, SHOW_HISTORY will be used as a default value.
   */
  private static String SHOW_MODE = "show";
  /** Possible values for invoking mode */
  // Show the visited items
  private static final int SHOW_HISTORY = 0;
  // Show nothing (a blank screen)
  private static final int SHOW_NONE = 1;
  // Show all of date items
  private static final int SHOW_ALL = 2;

  /**
   * The theme of Gesture Search can be light or dark. 
   * By default, Gesture Search will use a dark theme.
   */
  private static final String THEME = "theme";
  private static final int THEME_LIGHT = 0;
  private static final int THEME_DARK = 1;

  /** Keys for results returned by Gesture Search */
  private static final String SELECTED_ITEM_ID = "selected_item_id";
  private static final String SELECTED_ITEM_NAME = "selected_item_name";

As you can see in the code, when Gesture Search appears, we can show a recently selected country name, or nothing. Gesture Search then appears with a list of all the country names. The user can draw gestures directly on top of the list and a target item will pop up at the top. When a user taps a country name, Gesture Search exits and returns the result to the calling app. The following method is invoked for processing the user selection result, reading the Id and the name of the chosen data item.

@Override
  protected void onActivityResult(int requestCode, int resultCode, Intent data) {
    if (resultCode == Activity.RESULT_OK) {
      switch (requestCode) {
        case GESTURE_SEARCH_ID:
          long selectedItemId = data.getLongExtra(SELECTED_ITEM_ID, -1);
          String selectedItemName = data.getStringExtra(SELECTED_ITEM_NAME);
          // Print out the Id and name of the item that is selected 
          // by the user in Gesture Search
          Log.d("GestureSearchExample", selectedItemId + ": " + selectedItemName);
          break;
      }   
    }
  }

To use the Gesture Search API, you must be sure Gesture Search is installed. To test this condition, catch ActivityNotFoundException as shown in the above code snippet and display a MessageBox asking the user to install Gesture Search.

You can download the sample code at http://code.google.com/p/gesture-search-api-demo.

Yang Li builds interactive systems to make information easily accessible anywhere anytime. He likes watching movies and spending quality time with his family.

Posted by Scott Knaster, Editor

2013, By: Seo Master

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

Including a rel=canonical link in your webpage is a strong hint to search engines your preferred version to index among duplicate pages on the web. It’s supported by several search engines, including Yahoo!, Bing, and Google. The rel=canonical link consolidates indexing properties from the duplicates, like their inbound links, as well as specifies which URL you’d like displayed in search results. However, rel=canonical can be a bit tricky because it’s not very obvious when there’s a misconfiguration.


We recommend the following best practices for using rel=canonical:

• A large portion of the duplicate page’s content should be present on the canonical version.

One test is to imagine you don’t understand the language of the content—if you placed the duplicate side-by-side with the canonical, does a very large percentage of the words of the duplicate page appear on the canonical page? If you need to speak the language to understand that the pages are similar; for example, if they’re only topically similar but not extremely close in exact words, the canonical designation might be disregarded by search engines.

• Double-check that your rel=canonical target exists (it’s not an error or “soft 404”)
• Verify the rel=canonical target doesn’t contain a noindex robots meta tag
• Make sure you’d prefer the rel=canonical URL to be displayed in search results (rather than the duplicate URL)
• Include the rel=canonical link in either the <head> of the page or the HTTP header
• Specify no more than one rel=canonical for a page. When more than one is specified, all rel=canonicals will be ignored.

Mistake 1: rel=canonical to the first page of a paginated series

Imagine that you have an article that spans several pages:

• example.com/article?story=cupcake-news&page=1
• example.com/article?story=cupcake-news&page=2
• and so on

Specifying a rel=canonical from page 2 (or any later page) to page 1 is not correct use of rel=canonical, as these are not duplicate pages. Using rel=canonical in this instance would result in the content on pages 2 and beyond not being indexed at all.


In cases of paginated content, we recommend either a rel=canonical from component pages to a single-page version of the article, or to use rel=”prev” and rel=”next” pagination markup.



Mistake 2: Absolute URLs mistakenly written as relative URLs


The <link> tag, like many HTML tags, accepts both relative and absolute URLs. Relative URLs include a path “relative” to the current page. For example, “images/cupcake.png” means “from the current directory go to the “images” subdirectory, then to cupcake.png.” Absolute URLs specify the full path—including the scheme like http://.

Specifying <link rel=canonical href=“example.com/cupcake.html” /> (a relative URL since there’s no “http://”) implies that the desired canonical URL is http://example.com/example.com/cupcake.html even though that is almost certainly not what was intended. In these cases, our algorithms may ignore the specified rel=canonical. Ultimately this means that whatever you had hoped to accomplish with this rel=canonical will not come to fruition.

Mistake 3: Unintended or multiple declarations of rel=canonical

Occasionally, we see rel=canonical designations that we believe are unintentional. In very rare circumstances we see simple typos, but more commonly a busy webmaster copies a page template without thinking to change the target of the rel=canonical. Now the site owner’s pages specify a rel=canonical to the template author’s site.


Another issue is when pages include multiple rel=canonical links to different URLs. This happens frequently in conjunction with SEO plugins that often insert a default rel=canonical link, possibly unbeknownst to the webmaster who installed the plugin. In cases of multiple declarations of rel=canonical, Google will likely ignore all the rel=canonical hints. Any benefit that a legitimate rel=canonical might have offered will be lost.

In both these types of cases, double-checking the page’s source code will help correct the issue. Be sure to check the entire <head> section as the rel=canonical links may be spread apart.


Mistake 4: Category or landing page specifies rel=canonical to a featured article

Let’s say you run a site about desserts. Your dessert site has useful category pages like “pastry” and “gelato.” Each day the category pages feature a unique article. For instance, your pastry landing page might feature “red velvet cupcakes.” Because the “pastry” category page has nearly all the same content as the “red velvet cupcake” page, you add a rel=canonical from the category page to the featured individual article.

If we were to accept this rel=canonical, then your pastry category page would not appear in search results. That’s because the rel=canonical signals that you would prefer search engines display the canonical URL in place of the duplicate. However, if you want users to be able to find both the category page and featured article, it’s best to only have a self-referential rel=canonical on the category page, or none at all.


Mistake 5: rel=canonical in the <body>

The rel=canonical link tag should only appear in the <head> of an HTML document. Additionally, to avoid HTML parsing issues, it’s good to include the rel=canonical as early as possible in the <head>. When we encounter a rel=canonical designation in the <body>, it’s disregarded.

This is an easy mistake to correct. Simply double-check that your rel=canonical links are always in the <head> of your page, and as early as possible if you can.


Conclusion

To create valuable rel=canonical designations:

• Verify that most of the main text content of a duplicate page also appears in the canonical page.
• Check that rel=canonical is only specified once (if at all) and in the <head> of the page.
• Check that rel=canonical points to an existent URL with good content (i.e., not a 404, or worse, a soft 404).
• Avoid specifying rel=canonical from landing or category pages to featured articles as that will make the featured article the preferred URL in search results.

And, as always, please ask any questions in our Webmaster Help forum.

Written by Allan Scott, Software Engineer, Indexing Teamthis 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: 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
(Cross-posted on the Custom Search Blog)

Using Custom Search Engine (CSE), you can create rich search experiences that make it easier for visitors to find the information they’re looking for on your site. Today we’re announcing two improvements to sorting and filtering of search results in CSE.

First, CSE now supports UI-based results sorting, which you can enable in the Basics tab of the CSE control panel. Once you’ve updated the CSE element code on your site, a “sort by” picker will become visible at the top of the results section.


By default CSE supports sorting by date and relevance. In the control panel, you can specify additional “sort by” keys that are based on the structure of your site’s content, giving users more options to find the results that are most relevant to them. For example, if you’ve marked up pages for product rich snippets, you could enable sorting based on price as shown below:


Second, we’re introducing compact queries for filtering by attribute. Currently you can issue a query like
[more:pagemap:product-description:search more:pagemap:product-description:engine]
which will only show pages with a ‘product-description’ attribute that contains both ‘search’ and ‘engine’.

With a compact query, you can issue the same request as:
[more:p:product-description:search*engine]

We hope these new features help you create richer and more useful search experiences for your visitors. As always, if you have any questions or feedback please let us know via our Help Forum.

Posted by Roger Wang, Software Engineerthis 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

We've just released updates to several features in Webmaster Tools to provide you with more detail and more control of how your site appears in search results.

Search queries: Time does not stand still and neither should your site. With that in mind we've added a "Change" column next to the impressions, clicks, clickthrough rate (CTR) and position columns, making it easier to identify trends for each of these important metrics. The change column is tied to the date range you specify, which should help when you're trying to pinpoint when a particular change occurred.



Each query listed in Search queries now links to a query details page which includes a graph of impressions and clicks for that specific query, providing a quick visual of its performance in the search results over time. Below the graph is a table listing of the pages returned in search results for that query, along with impressions, clicks and CTR. Each column in the table is sortable, offering a quick way to re-sort the data based on what's most interesting to you. If you'd rather use your own favorite tool to slice and dice the data you can use the "Download this table" link to export all the information from the main Search queries page or from each individual query details page.



Better Parameter Handling: We've moved this feature under its own tab in the Settings section of Webmaster Tools, and introduced a new action to manage parameters. When we introduced Parameter Handling last year, we allowed you to specify URL parameters and whether they should be ignored or not. When you choose to ignore a parameter, you are telling us that this parameter has no impact on the displayed content. For example, consider a session id parameter, like “sid” in the following URLs:

http://example.com/product.php?item=swedish-fish
http://example.com/product.php?item=swedish-fish&sid=1234
http://example.com/product.php?item=swedish-fish&sid=5678

Assuming that these three URLs display exactly the same product page for tasty Swedish fish candy, Google only needs to crawl and index one of them. You can simply select action “Ignore” for parameter “sid” in Webmaster Tools and Google will just crawl and index one of these URLs, avoiding duplicates.

In addition to the old functionality, you now have the ability to choose a specific value among the known values for a given URL parameter. This is important when a parameter is relevant to the content, but different values of this parameter lead to similar pages. For example, consider a sorting parameter, like “sort-by” in the following URLs:

http://example.com/shop.php?category=candy&sort-by=asc-price&page=1
http://example.com/shop.php?category=candy&sort-by=desc-price&page=1
http://example.com/shop.php?category=candy&sort-by=asc-price&page=2
http://example.com/shop.php?category=candy&sort-by=desc-price&page=2

These four URLs show products in the candy category. There are enough items in this category to fill two pages, and the products shown can be sorted by price, in ascending or descending order. Selecting action “Ignore” for parameter “sort-by” would be incorrect and could potentially limit our indexing of the site. This is because, after ignoring “sort-by”, we would consider the first two URLs equivalent and may choose to index the URL with ascending sort order. We would also consider the last two URLs equivalent and may choose to index the URL with descending sort order. In this scenario, we would be indexing the candy category inconsistently, with some candy products appearing in both of the pages selected for the index, while other candy products not appearing in either of them. The right solution comes from the new action “Use specific value” now available in Webmaster Tools. To avoid duplicates but still keep our indexing consistent, you can simply select action “Use specific value” for parameter “sort-by” and choose one of the valid values, say “asc-price”. After this, our indexing would be fully consistent, as we would focus only on the pages with products sorted by ascending price.



Messages: Some sites receive lots of messages in the Webmaster Tools Message Center. With this update we've added the ability to "star" specific messages that you deem important. There's now a separate "Starred" view where you can see all the messages that you’ve starred, making tracking and finding the most important messages for your site a breeze.



We hope these updates make Webmaster Tools even more useful for your site. Please post a comment if you have feedback on any of these updates; or if you have questions, post them in our Webmaster Help Forum.

Posted by Jonathan Simon, Webmaster Trends Analystthis 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

Last October, we launched Webmaster Tools Labs and it has been a huge success. Malware Details have helped thousands of users identify pages on their site that may be infected with malicious code, and Fetch as Googlebot has given users more insight into our crawler.

Today, we're happy to announce two additional Labs features:

• Fetch as Googlebot-Mobile
• Create your Sidewiki page owner entry

Fetch as Gooblebot Mobile (developed by Ryoichi Imaizumi)

After we launched Fetch as Googlebot, many users with mobile-specific sites asked if we could provide the ability to fetch their pages as Googlebot-Mobile. We thought it was a great idea, and added it as an option to our Fetch as Googlebot feature. We have two mobile options: cHTML (primarily used for Japanese sites), and XHTML/WML.





Create your Sidewiki page owner entry (developed by Derek Prothro)

Sidewiki allows users to contribute helpful information to any webpage using a sidebar in Google Toolbar or a Chrome extension. Webmasters can create a special entry, called a page owner entry, that appears above all entries written by users.



After Sidewiki launched webmasters kept asking, "How can I put a Sidewiki page owner entry on all pages of my site quickly?" With the feature that we're introducing today, you can now create these page owner entries directly within Webmaster Tools for any site you own.



We're really happy about these new features, and hope you enjoy them as much as we do. Let us know what you think!

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

Seo Master present to you: 2009 has been a busy year for the App Engine team, but all along we've looked forward to Google I/O and the excitement it brings to Google's developer community. At I/O last year, App Engine was brand new and many attendees were just getting familiar with the project. Well, what a difference a year makes - this year, in addition to sharing new information about our project, we got to learn about an amazing host of App Engine projects from you, our developers!

First, the big news - we are excited to announce open signups for our Java language runtime. During Wednesday's keynote, Engineering Manager Kevin Gibbs and Product Manager Andrew Bowers demoed the combined power of App Engine and GWT, all with easy deployment from the Eclipse IDE. If you've not tried our new language yet, please head over to the Admin Console to signup, then download the SDK and get programming.

The engineers behind Google App Engine for Java presented two sessions. First, Toby Reyelts and Don Schwarz introduced the new runtime with App Engine: Now Serving Java, including details of how our Java language layer exposes the power of Google's infrastructure. Be sure to check out the interactive game they demo'd with audience participation! Digging a bit deeper, Max Ross showed us The Softer Side of Schemas - how he mapped Java Persistence Standards to App Engine's datastore.

In addition to the new Java runtime, App Engine developer Brett Slatkin previewed some eagerly anticipated functionality: offline tasks. In his talk Offline Processing on App Engine: a Look Ahead, Brett revealed the first few milestones of App Engine's plan for offline processing with our upcoming Task Queue API. Leveraging the power of a web hook (an HTTP request body and URL) as the fundamental unit of execution on the web, this new API will allow you to organize and enqueue tasks for efficient background processing. Stay tuned to the App Engine blog for this feature's launch.

The App Engine team is always eager to share information about our infrastructure and how things work under the hood. Alon Levi kicked things off Wednesday morning with From Spark Plug to Drive Train: Life of an App Engine Request, in which he showed new information about how an application's incoming requests are received, scheduled, and executed by App Engine. Ryan Barrett presented some of the theoretical, yet practical challenges faced by the App Engine team with Transactions Across Datacenters (and Other Weekend Projects). Finally, Brett Slatkin took the stage once again, with Building Scalable, Complex Apps on App Engine, to give you insights on advanced data structures and algorithms.

In addition to the App Engine team, we were thrilled to have App Engine customers and partners present about their experience with the platform:

• The Walk Score team shared their experience combining App Engine with other products in App Engine Nitty-Gritty: Scalability, Fault Tolerance, and Integrating Amazon EC2.
• Ola Bini gave a language implementor's view of our new Java runtime with JRuby and Ioke on Google App Engine for Java.
• Daniel Wilkerson presented distributed database theory in A Design for a Distributed Transaction Layer for Google App Engine.
• Guillaume Laforge from SpringSource did a rapid walkthrough of Groovy and how to write Groovy applications for App Engine with Groovy and Grails in App Engine

Last but not least, more partners joined our Developer Sandbox to share their experience building projects on Google App Engine: 3scale, Best Buy, BuddyPoke, EZAsset, Gigapan, LifeAware, Salesforce.com, SpringSource, and ThoughtWorks.

Thanks for making this year's Google I/O a fantastic success! We have much more in store for 2009, so be sure to watch the App Engine blog for updates!

By Mike Repass, App Engine Team

Java is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.2013, By: Seo Master

Seo Master present to you:
By Scott Knaster, Google Developers Blog Editor

340 trillion trillion trillion is our new favorite number. This past Tuesday was World IPv6 Launch, a huge step forward in making sure the Internet doesn’t run out of IP addresses in the near future. Until now, the universe has been using 32-bit addresses for devices on the Internet. The new version, IPv6, uses 128 bits, which increases the number of available addresses from a mere 4.3 billion to more than 340 undecillion, or more precisely, 340,282,366,920,938,463,463,374,607,431,768,211,456. So, that’s a lot.



From astronomical numbers to a rare astronomical event: the transit of Venus across the sun. This event was a big deal for NASA’s Solar Dynamics Observatory (SDO), a spacecraft that studies the sun. The SDO and its humans produced this breathtaking video made up of images from the transit. This is way better than what you saw with your welder’s goggles.

Finally, with all this advanced technology, it’s nice to go retro now and then. You can do that by enjoying these animated GIFs of video games, for when you just can’t find your 8-bit game system. (Hat tip: Boing Boing).


Each week we publish Fridaygram, featuring stuff from Google and beyond that you might have missed during the week. Fridaygram items aren't necessarily related to developer topics; they’re just interesting to us nerds. This week we say goodbye to Ray Bradbury as he departs Earth.

2013, By: Seo Master

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

Seo Master present to you: The Google Enterprise team was really energized to see the strong turnout for the 8 enterprise-track sessions at Google I/O last week. It was a treat to meet developers face to face and share stories about how things like Google App Engine, gadgets, GWT, Enterprise Search, and HTML 5 are impacting the industry's move to cloud computing. We were also pleased to announce Google Apps Script, a new feature that allows customization and automation in Google Apps, starting with spreadsheets, and to see the positive press coverage it has received.

The reality is that despite a formal "enterprise" track, the majority of the sessions were interesting and relevant to commercial developers, particularly Google Apps developers, who are rapidly uncovering a diverse set of commercial opportunities using these developer tools. This is something we want to continue to spread the word about!

The Google I/O team is busy uploading content from the event to the Google I/O site, and today we're happy to share a few highlights from last week:

Practical Standards-based Security and Identity in the Enterprise: Eric Sachs gave an overview of how Google is incorporating today's open identity and authorization standards into both consumer applications as well as enterprise software. Eric demonstrated inter-service communication using OAuth: from extranet to intranet, from platform to platform, and even from Google App Engine to Google App Engine.

Growing a SaaS-based services business around Google Apps: Jeff Ragusa of Google and Daniel Jefferies of Newmind Group gave a talk on how system integrators and developers can partner with Google to build a strong business reselling Google Apps and complementary services. Jeff highlighted the the myriad opportunities that emerge when the money spent on licenses, maintenance and upgrades can instead be spent on solving specific business problems and building custom apps an gadgets. Daniel, a Google Apps Authorized Reseller, talked about his experience bringing cloud computing to his customers.

Building Scalable, Complex Apps on App Engine: Brett Slatkin gave an informative presentation on the advanced techniques and data structures developers can leverage to build complex apps with App Engine. Areas of discussion included list properties and merge-joins, and how developers can use these tools to maximize performance of their apps.

Salesforce, Appirio and ThoughtWorks on App Engine for Java: Ron Hess of Salesforce and Iein Valdez of Appirio presented Connecting The Clouds: Integrating Google App Engine for Java with Force.com, and announced a new open source SOAP library for App Engine that helps connect App Engine apps to Force.com apps. Martin Fowler and Rebecca Parsons presented a session titled ThoughtWorks on App Engine for Java: An Enterprise Cumulonimbus?, which provided an overview of App Engine and the move to cloud computing from the perspective of larger enterprises.

Using the Google Secure Data Connector to Access Behind-the-Firewall Data from Google's Cloud: In this session, Jun Yang of Google showed how enterprises can bring a behind-the-firewall relational database into Google Apps using the Google Secure Data Connector and Google Feed Server. Jun demonstrated how developers can do this without the need for special code to access the SQL data or complex firewall configuration.

We hosted a mixer for enterprise developers and IT decision makers on the first day of I/O, and were thrilled at the turnout. The event was our first face to face outreach to commercial developers, covering all Enterprise product lines and touching on several recent developer announcements like Google Apps Script and the Google Apps Reseller program.

No, this is not people queuing up for free Android phones, just the line for the Enterprise Mixer.

All told, a great two days thanks to all of you. Since we're just getting started with tools and topics of interest to enterprise developers, please stay in touch. We have more tools and APIs on the way. The easiest way to do that is to subscribe to our Solution Provider announcements, and if you're tweeting, follow us on Twitter at GoogleAtWork.

By Scott McMullan, Google Apps Team2013, By: Seo Master

Seo Master present to you: 2013, By: Seo Master

Seo Master present to you: Another Google I/O has come and gone, and speaking personally I think it's going to be hard to top this year's conference. Free Android unlocked developer devices and the unveiling of a very cool new product built with developers in mind? I already don't envy the planning team taking on next year.

There was a ton of Google Web Toolkit (GWT) related content this year, including an incredibly nice shout-out from Lars Rasmussen during the Google Wave keynote - if you haven't heard, Google Wave is built using GWT so if you want some inspiration as to what's possible, check out the keynote.

The GWT-related sessions have now been posted, so if you missed one you'll be able to catch it here. Here's a quick overview of the many sessions:

GWT Can Do What? A Preview of Google Web Toolkit 2.0: Start thinking about how you will take advantage of new features like runAsyc in the next version of Google Web Toolkit. Bruce Johnson, Co-creator of GWT, goes into the details of what's coming and the philosophy behind the new features.

Google Wave - Powered by GWT: This one's for the skeptics in your engineering department. As an adept JavaScript developer, Adam Schuck, Google Wave's Client Lead was initially skeptical about using Google Web Toolkit. Many lines of code later, he will openly tell you he's changed his mind about that. In this session, Adam discusses the Wave team's decision to use GWT and other facets of their client-side code.

Google Web Toolkit Architecture: Best Practices for Architecting your GWT App: A common question people ask is how to architect a GWT app. Ray Ryan discusses real-world learnings and patterns from the Google AdWords team and elsewhere which you can use in your apps.

Measure in Milliseconds: Performance Tips for Google Web Toolkit: Want some best practices for speeding up your app? Kelly Norton shares a few concrete issues and how to solve them.

Effective GWT: Developing a Complex, High- performance App with Google Web Toolkit: Alex Moffat and Damon Lundin from Lombardi are back again for a second year at Google I/O. Similar in theme to Ray Ryan's talk above, but with additional perspective and content, they'll take you through how they've successfully architected Lombardi Blueprint. I recommend watching both if you are laying out a new GWT app, or refactoring an existing one.

The Story of your Compile: Reading the Tea Leaves of the GWT Compiler for an Optimized Future: What if your app isn't as fast as you like it to be? While GWT tries to make your app as optimized as possible when you drive it off the lot, applications sometimes need to be tuned for racing by the developers themselves. Lex Spoon and Bruce Johnson talk about tools and techniques for understanding what's going on with your code and how to use that information to optimize your app.

Progressively Enhance AJAX Applications with Google Web Toolkit and GQuery: Ray Cromwell, from Timefire is one of my personal favorite speakers and commentators on GWT and web development. When he broke out his horse race demo in this session to measure performance deltas between different JS libraries, I knew why. Ray takes JQuery's power approach to manipulation and implements it in GWT. Learn about Ray's tool and how you can use this in your own projects to give designer's tools they can use directly in the HTML, without coding Java.

Building Applications with Google APIs: Did I mention Ray is an entertaining technical speaker? The title of this session, as Ray noted, doesn't do it justice. Related to GWT, this session outlines how he's used Google APIs and tools together to create an amazing integrated experience at Timefire. His demonstration of the interactive graph that syncs with the YouTube video is very compelling. Want to dispute Al Gore's claim of carbon emissions? Add your own dataset to the graph via a comment. Impressive.

We had a great time meeting many of you at I/O. Many of us were on hand, and talked to a lot of 'familiar email addresses' - it's nice to make that familiar faces. For those of you who didn't make it to I/O or want to revisit the GWT sessions, we hope you enjoy the session videos and presentations!

By Andrew Bowers, Google Web Toolkit Team2013, By: Seo Master

salam every one, this is a topic from google web master centrale blog: Posted by Jen Lee and Alissa Roberts, Search Quality Teamthis 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: Written by Ríona MacNamara, Webmaster Tools Team

Common feedback we hear from webmasters is that you want us to improve the freshness of the data in Webmaster Tools. Understood. :) We've increased the update frequency for your verified sites' data, such as crawl, index, and search query stats. Much of this data depends on the content of your site. If your content doesn't change very often, or if you're not getting new links to your site, you may not see updates to your data every time you sign in to Webmaster Tools.

Please continue to post your Suggestions & feature requests in the Webmaster Help Group. It's one of our most important sources of feedback from the webmaster community. We seriously take it seriously.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

Webmasters, you may notice some changes in you Search queries data due to the launch of Google Instant. With Google Instant, the page updates dynamically to show results for the top completion of what the user has typed, so this means people could be seeing and visiting your website much faster than before, and often without clicking the search button or hitting “enter.”


With Google Instant, you may notice an increase in impressions because your site will appear in search results as users type.


Impressions are measured in three ways with Google Instant:

1. Your site is displayed in search results as a response to a user’s completed query (e.g. by pressing “enter” or selecting a term from autocomplete). This is the traditional model.
   
   With Google Instant, we also measure impressions in these new cases:


2. The user begins to type a term on Google and clicks on a link on the page, such as a search result, ad, or a related search.


3. The user stops typing, and the results are displayed for a minimum of 3 seconds.

To give an example, let’s say your site has lots of impressions for [hotels] and [hotels in santa cruz]. Now, because Instant is quickly fetching results as the user types, the user could see your site in the search results for [hotels] after typing only the partial query [hote]. If a user types the partial query [hote] and then clicks on any result on the page for [hotels], that counts as an impression for your site. That impression will appear in Webmaster Tools for the query [hotels]. The term 'hotels' would also be included in the HTTP referrer when the user clicks through to visit your website.

It’s likely that your site will still see impressions for queries like [hotels in santa cruz], but because Instant is helping the user find results faster, your site may see an increase in impressions for shorter terms as well.

Let us know if we can help you better understand how these changes impact Webmaster Tools, measured Search queries and impressions, CTR, or anything else. We’d love to hear from you in our blog comments or Webmaster Help Forum.

Guest post by Doantam Phan, Instant Search Teamthis is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

Seo Master present to you: By Dion Almaer, Google Developer Programs

This week it felt like the day after the wedding. The developer day was complete, and now we need to move on, gather up the feedback from the community, and start on the real work of producing APIs and tools for you all.

In API and developer-product news...

DragZoomControl v1.0: Easier zooming, coming right up!

Andre Lewis has contributed his GZoom control to the Google Maps Utility Library which is a set of useful additions to the Maps API, distributed under an open source license. The new control is DragZoomControl, and does what it says on the box.

New KML Developments and Documentation

Mano Marks told us about the new documentation available that tells us about how to get Google to search your KML files, and the release of KML 2.2 beta reference material. KML will now support use of the Atom Syndication format atom:author and atom:uri elements for attribution.

AJAX Feed API Slide Show Enhancements

Mark Lucovsky upgraded the AJAX Feed API Slide Show to allow you to tweak the experience by using various callbacks that let you hook slide transitions, clicks, etc. For an example, he created a slideshow view
of PodTech that allows you to play videos inline as the appropriate image shows up.

Around Google

Google Calendar Gallery

The Google Calendar Gallery helps you find public calendars that may interest you. Plug in the Red Sox schedule, or the Netflix release dates, directly into your calendar.

FeedBurner Acquisition

FeedBurner lets you manage your feeds in interesting ways. You offload the traffic to the service, can add features on top of your own feed (enable Podcast on the fly, advertising, etc), and see great statistics on how your users are using it. We are proud to have the FeedBurner team part of the Google family.

Featured Projects

San Francisco Giants Mashup

Paul McDonald, of the Google Mashup Editor team, has put together a nice mashup on all things SF Giants. As with all Google Mashups, everyone is open source, and you can "view source" on anyones application. Take a peak at this example to see how you can use the mashup editor to do some sophisticated application building.

Remember The Milk Offline

The Remember The Milk team had an advantage. They were in Sydney where we released Gears, and they were obviously on the case. They quickly released an offline version of their TODO list application.

Google Tech Talks

Java on Guice: Dependency Injection, the Java Way

Bob Lee has been traveling the world speaking on Guice recently. This week he got to give his talk right here in Mountain View, and it was recorded for your viewing pleasure.

Hey, What's That? A Map Hack

Michael Kosowsky came to chat about his cool Maps application that lets you see what you could see from a high point (e.g. Longs Peak). Fun math and visualizations indeed.

Podcasts

Google Developer Podcast Episode Three: Mike Tsao on Google Gears

We got to interview Mike Tsao of the Google Gears team on how Gears came about, the design decisions, and lessons for developers as they go about offline-enabling their applications.

The Mono Project

Miguel de Icaza was joined by three former students for Mono: Aaron Tomb, Alan McGovern and Michael Hutchinson. They chat about the past, present, and future of Mono and what the summer of coders are working on now.2013, By: Seo Master

Seo Master present to you: 2013, By: Seo Master