App Indexing in more languages

Webmaster level: all

In April, we launched App Indexing in English globally so deep links to your mobile apps could appear in Google Search results on Android everywhere. Today, we’re adding the first publishers with content in other languages: Fairfax Domain, MercadoLibre, Letras.Mus.br, Vagalume, Idealo, L'Equipe, Player.fm, Upcoming, Au Feminin, Marmiton, and chip.de. In the U.S., we now also support some more apps -- Walmart, Tapatalk, and Fancy.

We’ve also translated our developer guidelines into eight additional languages: Chinese (Traditional), French, German, Italian, Japanese, Brazilian Portuguese, Russian, and Spanish.

If you’re interested in participating in App Indexing, and your content and implementation are ready, please let us know by filling out this form. As always, you can ask questions on the mobile section of our webmaster forum.

Finally, if you’re headed to Google I/O in June, be sure to check out the session on the “Future of Apps and Search”, where we’ll share some more updates on App Indexing.

Posted by Erik Hendriks, Software Engineer

Rendering pages with Fetch as Google

Webmaster level: all

The Fetch as Google feature in Webmaster Tools provides webmasters with the results of Googlebot attempting to fetch their pages. The server headers and HTML shown are useful to diagnose technical problems and hacking side-effects, but sometimes make double-checking the response hard: Help! What do all of these codes mean? Is this really the same page as I see it in my browser? Where shall we have lunch? We can't help with that last one, but for the rest, we've recently expanded this tool to also show how Googlebot would be able to render the page.

Viewing the rendered page

In order to render the page, Googlebot will try to find all the external files involved, and fetch them as well. Those files frequently include images, CSS and JavaScript files, as well as other files that might be indirectly embedded through the CSS or JavaScript. These are then used to render a preview image that shows Googlebot's view of the page.

You can find the Fetch as Google feature in the Crawl section of Google Webmaster Tools. After submitting a URL with "Fetch and render," wait for it to be processed (this might take a moment for some pages). Once it's ready, just click on the response row to see the results.

Handling resources blocked by robots.txt

Googlebot follows the robots.txt directives for all files that it fetches. If you are disallowing crawling of some of these files (or if they are embedded from a third-party server that's disallowing Googlebot's crawling of them), we won't be able to show them to you in the rendered view. Similarly, if the server fails to respond or returns errors, then we won't be able to use those either (you can find similar issues in the Crawl Errors section of Webmaster Tools). If we run across either of these issues, we'll show them below the preview image.

We recommend making sure Googlebot can access any embedded resource that meaningfully contributes to your site's visible content, or to its layout. That will make Fetch as Google easier for you to use, and will make it possible for Googlebot to find and index that content as well. Some types of content – such as social media buttons, fonts or website-analytics scripts – tend not to meaningfully contribute to the visible content or layout, and can be left disallowed from crawling. For more information, please see our previous blog post on how Google is working to understand the web better.

We hope this update makes it easier for you to diagnose these kinds of issues, and to discover content that's accidentally blocked from crawling. If you have any comments or questions, let us know here or drop by in the webmaster help forum.

Posted by Shimi Salant, Webmaster Tools team

Making more housecalls

Written by Maile Ohye

All of us with Webmaster Central share one passion: a serious love for improving the Internet.

If you're organizing an event with an audience that would benefit from our discussing building search-engine friendly sites and maximizing the resources of Webmaster Central -- such as our Webmaster Tools, Help Center and Discussion Group -- please submit a speaker request. We'll work with our Corporate Communications team to see if we can add your event to our schedule.

With the intention of helping people make great content accessible on the web, we attended over 15 events this year -- including search conferences, business schools and marketing expos. We feel that we can be most helpful to:

• Site owners/webmasters/bloggers who feature original, compelling content or tools, such as their...
• Neighborhood store, restaurant, dentist office, etc.
• Service or product (e.g. freelance photographer or online wizard for house decorating)
• Passion, hobby, opinion (latest from the San Francisco music scene, perspectives on the upcoming election)
• Web developers, web designers, SEOs/SEMs who build sites for others

Submitting a speaking request does not guarantee our attendance, but we'll definitely review each submission with our Communications team. Also, if we can't attend your event this time around, but we feel we could make a positive impact in the future, we'll keep the event on our radar.

Now I'd love to introduce two of our newest speakers who have been active in the Webmaster Help Group for some time: Michael Wyszomierski and Reid Yokoyama.

Hi, I'm Michael, but I go by "Wysz" in the Webmaster Help Group. When I'm not talking to webmasters or doing other search-related work, I like to tinker with my personal blog, take photos, and edit videos. Blogs, videos, podcasts, and other online media often come to my rescue when I'm searching for information online, so I'd love to talk to fellow content providers about how to make sure their sites can be understood by Google.

Hi, I'm Reid. I'm originally from St. Louis, Missouri, but have fallen in love with the weather, biking trails, and culture of the Bay Area. I studied to be a historian and even wrote a Senior honors thesis on Japanese American resettlement in San Francisco after WWII, but as an avid blogger, found myself increasingly interested in the transaction of knowledge and information through the Internet. I'm particularly passionate about helping small businesses build out high quality websites and helping them understand how Google's tools can help them in the process.

Understanding web pages better

In 1998 when our servers were running in Susan Wojcicki’s garage, we didn't really have to worry about JavaScript or CSS. They weren't used much, or, JavaScript was used to make page elements... blink! A lot has changed since then. The web is full of rich, dynamic, amazing websites that make heavy use of JavaScript. Today, we'll talk about our capability to render richer websites — meaning we see your content more like modern Web browsers, include the external resources, execute JavaScript and apply CSS.

Traditionally, we were only looking at the raw textual content that we’d get in the HTTP response body and didn't really interpret what a typical browser running JavaScript would see. When pages that have valuable content rendered by JavaScript started showing up, we weren’t able to let searchers know about it, which is a sad outcome for both searchers and webmasters.

In order to solve this problem, we decided to try to understand pages by executing JavaScript. It’s hard to do that at the scale of the current web, but we decided that it’s worth it. We have been gradually improving how we do this for some time. In the past few months, our indexing system has been rendering a substantial number of web pages more like an average user’s browser with JavaScript turned on.

Sometimes things don't go perfectly during rendering, which may negatively impact search results for your site. Here are a few potential issues, and – where possible, – how you can help prevent them from occurring:

• If resources like JavaScript or CSS in separate files are blocked (say, with robots.txt) so that Googlebot can’t retrieve them, our indexing systems won’t be able to see your site like an average user. We recommend allowing Googlebot to retrieve JavaScript and CSS so that  your content can be indexed better. This is especially important for mobile websites, where external resources like CSS and JavaScript help our algorithms understand that the pages are optimized for mobile.
• If your web server is unable to handle the volume of crawl requests for resources, it may have a negative impact on our capability to render your pages. If you’d like to ensure that your pages can be rendered by Google, make sure your servers are able to handle crawl requests for resources.
• It's always a good idea to have your site degrade gracefully. This will help users enjoy your content even if their browser doesn't have compatible JavaScript implementations. It will also help visitors with JavaScript disabled or off, as well as search engines that can't execute JavaScript yet.
• Sometimes the JavaScript may be too complex or arcane for us to execute, in which case we can’t render the page fully and accurately.
• Some JavaScript removes content from the page rather than adding, which prevents us from indexing the content.

To make things easier to debug, we're currently working on a tool for helping webmasters better understand how Google renders their site. We look forward to making it to available for you in the coming days in Webmaster Tools.

If you have any questions, please feel free to visit our help forum.

Posted by Erik Hendriks and Michael Xu, Software Engineers, and Kazushi Nagayama, Webmaster Trends Analyst

Making your site more mobile-friendly with PageSpeed Insights

Webmaster level: all


To help developers and webmasters make their pages mobile-friendly, we recently updated PageSpeed Insights with additional recommendations on mobile usability.

Poor usability can diminish the benefits of a fast page load. We know the average mobile page takes more than 7 seconds to load, and by using the PageSpeed Insights tool and following its speed recommendations, you can make your page load much faster. But suppose your fast mobile site loads in just 2 seconds instead of 7 seconds. If mobile users still have to spend another 5 seconds once the page loads to pinch-zoom and scroll the screen before they can start reading the text and interacting with the page, then that site isn’t really fast to use after all. PageSpeed Insights’ new User Experience rules can help you find and fix these usability issues.

These new recommendations currently cover the following areas:

• Configure the viewport: Without a meta-viewport tag, modern mobile browsers will assume your page is not mobile-friendly, and will fall back to a desktop viewport and possibly apply font-boosting, interfering with your intended page layout. Configuring the viewport to width=device-width should be your first step in mobilizing your site.
  
  
• Size content to the viewport: Users expect mobile sites to scroll vertically, not horizontally. Once you’ve configured your viewport, make sure your page content fits the width of that viewport, keeping in mind that not all mobile devices are the same width.
  
  
• Use legible font sizes: If users have to zoom in just to be able read your article text on their smartphone screen, then your site isn’t mobile-friendly. PageSpeed Insights checks that your site’s text is large enough for most users to read comfortably.
  
• Size tap targets appropriately: Nothing’s more frustrating than trying to tap a button or link on a phone or tablet touchscreen, and accidentally hitting the wrong one because your finger pad is much bigger than a desktop mouse cursor. Make sure that your mobile site’s touchscreen tap targets are large enough to press easily.
  
• Avoid plugins: Most smartphones don’t support Flash or other browser plugins, so make sure your mobile site doesn't rely on plugins.

These rules are described in more detail in our help pages. When you’re ready, you can test your pages and the improvements you make using the PageSpeed Insights tool. We’ve also updated PageSpeed Insights to use a mobile friendly design, and we’ve translated our documents into additional languages.

As always, if you have any questions or feedback, please post in our discussion group.

Posted by Matthew Steele and Doantam Phan, PageSpeed Insights team

Let visitors recommend your content

Webmaster Level: All

We recently posted about some of the engaging gadgets you can add to your site with Google Friend Connect. Here's one more that may be of interest if you're looking for another way to get feedback from your site's visitors:

The new Recommendation gadgets make it easy for your visitors to let you and the world know which parts of your site they like best. By placing recommendation buttons next to photos, articles or other content, visitors can recommend specific items to others with the click of a button. Your most popular items will surface to the top of the recommendation list.

To install a recommendation gadget on your site, or to check out the other gadgets that are available, please visit www.google.com/friendconnect.

Posted by Mendel Chuang, Product Marketing Manager

Webmaster Tools now in 26 languages

Written by Liza Ma, Webmaster Tools Team

Webmasters come from all corners of the world and we are working hard to reach each and everyone of you. A few months back we introduced you to Googlers who help monitor our Webmaster Help Groups in fifteen languages. Since then, that number has grown to sixteen with the addition of the Chinese Help Group. Today, we're happy to announce that Webmaster Tools is now available in four more languages:

• Arabic
• Hebrew
• Hindi
• Thai

Webmaster Tools is already available in 22 other languages: British English, Czech, Danish, Dutch, Finnish, French, German, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Simplified Chinese, Spanish, Swedish, Traditional Chinese, Turkish, and US English.

We're thrilled to be engaging with such a diverse community of webmasters. Thank you again for your feedback and support!

Becoming Social

Posted by Mussie Shore, Product Manager

Update: The described feature is no longer available.

Wondering how to make your site more social? We'd like to make it easier for you, which is why earlier tonight at Campfire One at the Googleplex, we announced a preview release of Google Friend Connect.

Google Friend Connect is a service that that helps you grow traffic by enabling you to easily provide social features for your visitors. Just add a snippet of code, and, voilà, you can add social functionality -- picking and choosing from built-in functionality like user registration, invitations, members gallery, message posting, and reviews, as well as third-party applications built by the OpenSocial developer community.

Social features can generate buzz and traffic to your pages. Using Google Friend Connect on your site, your visitors will be able to see, invite, and interact with their friends from existing sources of friends, including Facebook, Google Talk, hi5, LinkedIn, orkut, Plaxo, and others. And you'll be able to more actively engage your visitors by adding social features from a growing gallery of social applications.



We've heard from many site owners that even though their sites aren't social networks, they'd still like them to be social. Whether your site sells car parts or dishes out great guacamole recipes -- like the sample site in the YouTube video above -- you can visit http://www.google.com/friendconnect/ or read more on the Official Google Blog to learn about Google Friend Connect. Right now, the preview is available for only a few sites, but soon we'll give the green light to even more. Sign up now to be on the wait list.

Spring time design refresh!

We've been listening to you at conferences, user studies, forums and blogs and we decided to start from the ground up with a brand new Webmaster Tools design! It was much needed, and the end result is beautiful in our eyes:



Highlights

• One-stop Dashboard: We redesigned our dashboard to bring together data you view regularly: Links to your site, Top search queries, Sitemaps, and Crawl errors.
• More top search queries: You now have up to 100 queries to track for impressions and clickthrough! In addition, we've substantially improved data quality in this area.
• Sitemap tracking for multiple users: In the past, you were unable to monitor Sitemaps submitted by other users or via mechanisms like robots.txt. Now you can track the status of Sitemaps submitted by other users in addition to yourself.
• Message subscription: To make sure you never miss an important notification, you can subscribe to Message Center notifications via e-mail. Stay up-to-date without having to log in as frequently.
• Improved menu and navigation: We reorganized our features into a more logical grouping, making them easier to find and access. More details on changes.
• Smarter help: Every page displays links to relevant Help Center articles and by the way, we've streamlined our Help Center and made it easier to use.
• Sites must be verified to access detailed functionality: Since we're providing so much more data, going forward your site must be verified before you can access any features in Webmaster Tools, including features such as Sitemaps, Test Robots.txt and Generate Robots.txt which were previously available for unverified sites. If you submit Sitemaps for unverified sites, you can continue to do so using Sitemap pings or by including the Sitemap location in your robots.txt file.
• Removal of the enhanced Image Search option: We're always iterating and improving on our services, both by adding new product attributes and removing old ones. With this release, the enhanced Image Search option is no longer a component of Webmaster Tools. The Google Image Labeler will continue to select images from sites regardless of this setting.

Go ahead, get started

The new user interface is available at http://www.google.com/webmasters/tools/new. The old user interface will continue to be available for a couple of weeks to give you guys time to adjust and provide feedback.

We did our best to get the product localized; however, you may notice a few missing translations in some areas of the user interface. We apologize for the inconvenience and when we switch everyone over in a couple of weeks, we'll fully support 40 languages. The one exception will be our Help Center, which will be available in 21 languages going forward.

We're really excited about this launch, and hope you are as well. Tell us what you think and stay tuned for more updates!

Posted by Sagar Kamdar, Product Manager, and Josh Teague, Interaction Designer, Webmaster Tools Team

Introducing Rich Snippets

Webmaster Level: All

As a webmaster, you have a unique understanding of your web pages and the content they represent. Google helps users find your page by showing them a small sample of that content -- the "snippet." We use a variety of techniques to create these snippets and give users relevant information about what they'll find when they click through to visit your site. Today, we're announcing Rich Snippets, a new presentation of snippets that applies Google's algorithms to highlight structured data embedded in web pages.

Rich Snippets give users convenient summary information about their search results at a glance. We are currently supporting data about reviews and people. When searching for a product or service, users can easily see reviews and ratings, and when searching for a person, they'll get help distinguishing between people with the same name. It's a simple change to the display of search results, yet our experiments have shown that users find the new data valuable -- if they see useful and relevant information from the page, they are more likely to click through. Now we're beginning the process of opening up this successful experiment so that more websites can participate. As a webmaster, you can help by annotating your pages with structured data in a standard format.

To display Rich Snippets, Google looks for markup formats (microformats and RDFa) that you can easily add to your own web pages. In most cases, it's as quick as wrapping the existing data on your web pages with some additional tags. For example, here are a few relevant lines of the HTML from Yelp's review page for "Drooling Dog BarBQ" before adding markup data:

and now with microformats markup:

or alternatively, use RDFa markup. Either format works:

By incorporating standard annotations in your pages, you not only make your structured data available for Google's search results, but also for any service or tool that supports the same standard. As structured data becomes more widespread on the web, we expect to find many new applications for it, and we're excited about the possibilities.

To ensure that this additional data is as helpful as possible to users, we'll be rolling this feature out gradually, expanding coverage to more sites as we do more experiments and process feedback from webmasters. We will make our best efforts to monitor and analyze whether individual websites are abusing this system: if we see abuse, we will respond accordingly.

To prepare your site for Rich Snippets and other benefits of structured data on the web, please see our documentation on structured data annotations.

Now, time for some Q&A with the team:

If I mark up my pages, does that guarantee I'll get Rich Snippets?

No. We will be rolling this out gradually, and as always we will use our own algorithms and policies to determine relevant snippets for users' queries. We will use structured data when we are able to determine that it helps users find answers sooner. And because you're providing the data on your pages, you should anticipate that other websites and other tools (browsers, phones) might use this data as well. You can let us know that you're interested in participating by filling out this form.

What about other existing microformats? Will you support other types of information besides reviews and people?

Not every microformat corresponds to data that's useful to show in a search result, but we do plan to support more of the existing microformats and define RDFa equivalents.

What's next?

We'll be continuing experiments with new types (beyond reviews and people) and hope to announce support for more types in the future.

I have too much data on my page to mark it all up.

That wasn't a question, but we'll answer anyway. For the purpose of getting data into snippets, we don't need every bit of data: it simply wouldn't fit. For example, a page that says it has "497 reviews" of a product probably has data for 10 and links to the others. Even if you could mark up all 497 blocks of data, there is no way we could fit it into a single snippet. To make your part of this grand experiment easier, we have defined aggregate types where necessary: a review-aggregate can be used to summarize all the review information (review count, average/min/max rating, etc.).

Why do you support multiple encodings?

A lot of previous work on structured data has focused on debates around encoding. Even within Google, we have advocates for microformat encoding, advocates for various RDF encodings, and advocates for our own encodings. But after working on this Rich Snippets project for a while, we realized that structured data on the web can and should accommodate multiple encodings: we hope to emphasize this by accepting both microformat encoding and RDFa encoding. Each encoding has its pluses and minuses, and the debate is a fine intellectual exercise, but it detracts from the real issues.

We do believe that it is important to have a common vocabulary: the language of object types, object properties, and property types that enable structured data to be understood by different applications. We debated how to address this vocabulary problem, and concluded that we needed to make an investment. Google will, working together with others, host a vocabulary that various Google services and other websites can use. We are starting with a small list, which we hope to extend over time.

Wherever possible, we'll simply reuse vocabulary that is in wide use: we support the pre-existing vCard and hReview types, and there are a variety of other types defined by various communities. Sites that use Google Custom Search will be able to define their own types, which we will index and present to users in rich Custom Search results pages. Finally, we encourage and expect this space to evolve based on new ideas from the structured data community. We'll notice and reach out when our crawlers pick up new types that are getting broad use.

Update on November 1, 2009: Check out our update on Rich Snippets!

Written by Kavi Goel, Ramanathan V. Guha, and Othar Hansson

Creating the Right Homepage for your International Users

If you are doing business in more than one country or targeting different languages, we recommend having separate sites or sections with specific content on each URLs targeted for individual countries or languages. For instance one page for US and english-speaking visitors, and a different page for France and french-speaking users. While we have information on handling multi-regional and multilingual sites, the homepage can be a bit special. This post will help you create the right homepage on your website to serve the appropriate content to users depending on their language and location.

There are three ways to configure your homepage / landing page when your users access it:

• Show everyone the same content.
• Let users choose.
• Serve content depending on users’ localization and language.

Let’s have a look at each in detail.

Show users worldwide the same content 

In this scenario, you decide to serve specific content for one given country and language on your homepage / generic URL (http://www.example.com). This content will be available to anyone who accesses that URL directly in their browser or those who search for that URL specifically. As mentioned above, all country & language versions should also be accessible on their own unique URLs.

Note: You can show a banner on your page to suggest a more appropriate version to users from other locations or with different language settings.

Let users choose which local version and which language they want 

In this configuration, you decide to serve a country selector page on your homepage / generic URL and to let users choose which content they want to see depending on country and language. All users who type in that URL can access the same page.

If you implement this scenario on your international site, remember to use the x-default rel-alternate-hreflang annotation for the country selector page, which was specifically created for these kinds of pages. The x-default value helps us recognize pages that are not specific to one language or region.

Automatically redirect users or dynamically serve the appropriate HTML content depending on users’ location and language settings

A third scenario would be to automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content.

Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users.

Note: Think about redirecting users for whom you do not have a specific version. For instance, French-speaking users on a website that has English, Spanish and Chinese versions. Show them the content that you consider the most appropriate.

Whatever configuration you decide to go with, you should make sure all the pages – including country and language selector pages:

• Have rel-alternate-hreflang annotations.
• Are accessible for Googlebot's crawling and indexing: do not block the crawling or indexing of your localized pages.
• Always allow users to switch local version or language: you can do that using a drop down menu for instance.

Reminder: As mentioned in the beginning, remember that you must have separate URLs for each country and language version. 

About rel-alternate-hreflang annotations

Remember to annotate all your pages - whatever method you choose. This will greatly help search engines to show the right results to your users.

Country selector pages and redirecting or dynamically serving homepages should all use the x-default hreflang, which was specifically designed for auto-redirecting homepages and country selectors. 

Finally, here are a few useful reminders about rel-alternate-hreflang annotations in general:

• Your annotations must be confirmed from the other pages. If page A links to page B, page B must link back to page A, otherwise, your annotations may not be interpreted correctly.
• Your annotations should be self-referential. Page A should use rel-alternate-hreflang annotation linking to itself.
• You can specify the rel-alternate-hreflang annotations in the HTTP header, in the head section of the HTML, or in a sitemap file. We strongly recommend that you choose only one way to implement the annotations, in order to avoid inconsistent signals and errors.
• The value of the hreflang attribute must be in ISO 639-1 format for the language, and in ISO 3166-1 Alpha 2 format for the region. Specifying only the region is not supported. If you wish to configure your site only for a country, use the geotargeting feature in Webmaster Tools. 

Following these recommendations will help us better understand your localized content and serve more relevant results to your users in our search results. As always, if you have any questions or feedback, please tell us in the internationalization Webmaster Help Forum.

Posted by Zineb Ait Bahajji and Gary Illyes, Webmaster Trends Analysts.

Google Trends for your website

Webmaster Level: All

In a recent post on the Official Google Blog, we mentioned our Google Trends gadget, and we thought it made sense to also post something here for all the webmasters that might be interested in having Trends on their website. Google Trends is a great way to see what's popular on the web -- people tend to search for what they care about -- and the Trends gadget makes it easy for you to put Trends on your website. Just cut and paste a small snippet of code, input your search terms, and you can show your readers how searches for Obama have changed during the last 30 days or who's the most popular American Idol contestant. So take a little piece of Google with you, and show your readers what's hot on the web.

Posted by Matt Ghering, Product Marketing Manager

Design patterns for accessible, crawlable and indexable content

Written by T.V. Raman, Research Scientist

As a follow-up to my previous posts on accessibility, here are some design recommendations for creating web content that remains usable by the widest possible audience while helping ensure that the content gets indexed and crawled.

Avoid spurious XMLHttpRequests

Pages that enable users to look up information often use XMLHttpRequests to populate the page with additional information after the page has loaded. When using this pattern, ensure that your initial page has useful information on it -- otherwise Googlebot as well as those users who have disabled scripting in their browser may believe that your site contains only the message "loading..."

CSS sprites and navigation links

Having meaningful text to go with navigational links is equally important for Googlebot as well as users who cannot perceive the meaning of an image. While designing the look and feel of navigational links on your site, you may have chosen to go with images that function as links, e.g., by placing <img> tags within <a> elements. That design enables you to place the descriptive text as an alt attribute on the <img> tag.

But what if you've switched to using CSS sprites to optimize page loading? It's still possible to include that all-important descriptive text when applying CSS sprites; for a possible solution, see how the Google logo and the various nav-links at the bottom of the Google Results page are coded. In brief, we placed the descriptive text right under the CSS-sprited image.

Google search results with CSS enabled


Google search result with CSS disabled ("Google" sprited image lost, descriptive "Google" link remains)


Use unobtrusive JavaScript

We've talked about the concept of progressive enhancement when creating a rich, interactive site. As you add features, also use unobtrusive JavaScript techniques for creating JavaScript-powered web pages that degrade gracefully. These techniques ensure that your content remains accessible by the widest possible user base without the need to sacrifice the more interactive features of Web 2.0 applications.

Make printer-friendly versions easily available

Web sites with highly interactive visual designs often provide all of the content for a given story as a printer-friendly version. Generated from the same content as the interactive version, these are an excellent source of high-quality content for both the Googlebot as well as visually impaired users unable to experience all of the interactive features of a web site. But all too often, these printer-friendly versions remain hidden behind scripted links of the form:

<a href="#" onclick="javascript:print(...)">Print</a>

Creating actual URLs for these printer-friendly versions and linking to them via plain HTML anchors will vastly improve the quality of content that gets crawled.

<a href="http://example.com/page1-printer-friendly.html" target="_blank">Print</a>

If you're especially worried about duplicate content from the interactive and printer-friendly version, then you may want to pick a preferred version of the content and submit a Sitemap containing the preferred URL as well as try to internally link to this version. This can help Google disambiguate if we see pieces of the article show up on different URLs.

Create URLs for your useful content

As a webmaster, you have the power to mint URLs for all of the useful content that you are publishing. Exercising this power is what makes the web spin. Creating URLs for every valuable nugget you publish, and linking to them via plain old HTML hyperlinks will ensure that:

• Googlebot learns about that content,
• users can find that content,
• and users can bookmark it for returning later.

Failure to do this often forces your users to have to remember complex click trails to reach that nugget of information they know they previously viewed on your site.

More ways to engage your community

Webmaster Level: All

Over the last few weeks, Google Friend Connect has added several new ways for you to strengthen the community that visits your site. These gadgets help to make your site more engaging and gives your visitors a new way to interact with your content and other visitors.

Here is a quick overview of these new gadgets:

Event gadget - Have an upcoming event you want to promote to your community? Embed this gadget on your site to let members get details about the event, see a map, indicate if they're coming, and see who else is attending. They can even add the event to their personal Google Calendars with just a click.

Polls gadget - Polls are a fun and easy way for your visitors to express themselves and a great tool for you to see what your users like. This gadget makes it easy to publish opinion polls and adds a social element by displaying the faces of the community members and friends who voted on each answer.

Get Answers gadget - Add the Get Answers gadget to your site to encourage visitors to ask questions of the community and answer questions posed by other community members. This gadget lets visitors browse questions, submit answers, and vote on answers they think are the best.

Comments gadget - Bring your site to life by adding the comments gadget to your pages. This gadget enables visitors to post comments and links to videos on your site. Visitors can even use the new translation feature to read comments in their preferred language.

Check out the Friend Connect gallery to see these gadgets along with all the other features Friend Connect has to offer. And keep an eye on the Social Web Blog for additional gadgets we'll soon be launching.

Posted by Mendel Chuang, Product Marketing Manager

Sitemaps offer better coverage for your Custom Search Engine

Rajat Mukherjee, Group Product Manager, Search

If you're a webmaster or site owner, you realize the importance of providing high quality search on your site so that users easily find the right information.

We just announced today that AdSense for Search is now powered by Custom Search. Custom Search (a Google-powered search box that you can install on your website in minutes) helps your users quickly find what they're looking for. As a webmaster, Custom Search gives you advanced customization options to improve the accuracy of your site's search results. You can also choose to monetize your traffic with ads tuned to the topic of your site. If you don't want ads, you can use Custom Search Business Edition.

Now, we're also looking to index more of your site's content for inclusion in your Custom Search Engine (CSE) used for search on your site. We figure out what sites and URLs are included in your CSE, and -- if you've provided Sitemaps for the relevant sites -- we use that information to create a more comprehensive experience for your site's visitors. You don't have to do anything specific, besides submitting a Sitemap (via Webmaster Tools) for your site if you haven't already done so. Note that this change will not result in more pages indexed on Google.com and your search rankings on Google.com won't change. However, you will be able to get much better results coverage in your CSE.

Custom Search is built on top of the Google index. This means that all pages that are available on Google.com are also available to your search engine. We're now maintaining a CSE-specific index in addition to the Google.com index for enhancing the performance of search on your site. If you submit a Sitemap, it's likely that we will crawl those pages and include them in the additional index we build.

In order for us to index these additional pages, our crawlers must be able to crawl them. Your Sitemap will also help us identify the URLs that are important. Please ensure you are not blocking us from crawling any pages you want indexed. Improved index coverage is not instantaneous, as it takes some time for the pages to be crawled and indexed.

So what are you waiting for? Submit your Sitemap!

Survey says...

Webmaster Level: All

Many thanks to the more than 1,600 people who filled out our survey in February. You gave us your feedback on the Webmaster Central Blog, Google Webmaster Tools, the Webmaster Help Forum, and our Webmaster Central videos on YouTube.

You told us what you like and want to see more of:

• Webmaster Central gives users insight into Google: "[I like] being able to access, communicate, and see how my sites relate to Google."
• Webmaster Central provides high quality information: "What I have enjoyed most of all, is reading Google's guidelines for webmasters, which is on-point with what I have been telling customers about SEO."
• Webmaster Central collects several useful tools in one place: "It's an innovative central hub for all the tools supported and provided by the industry leader Google, for free."

We also learned about what you don't like and where we could be doing better. Our top finding is that beginner webmasters (about 20% of the survey respondents) are less satisfied than intermediate or advanced webmasters with Webmaster Central. Open-ended comments suggested that new webmasters want basic, less technical information from us. A common feedback that we received: "Many users like myself are not of the hi-tech, IT-savvy variety and prefer simplicity, whether we create a website for information or to generate revenue." Based on your responses, we've planned some new resources like a series of how-to videos especially for new webmasters (coming soon to YouTube).

We take your feedback seriously and will continue improving Webmaster Central and our other webmaster sites. Again, thanks for your participation in the survey. We want Webmaster Central to continue being a useful resource for you.

Written by Carolyn Wei, User Experience Researcher

MT6592 flashing tutorial

Along with the release of the newest MediaTek octa-core SoC, an updated version of the known flashing tool has also been released. It's now time to publish fresh instructions on how to flash MT6592 based devices. Please note that the images shown on this tutorial are just examples and that you must flash your device with the correct ROM files.

Make sure that you read everything carefully and know what you are doing. Don't blame me for any damage that may occur on your device.

What's needed:

• Computer running Windows XP (or higher)
• USB data cable
• MediaTek USB VCOM drivers 
• SP Flash Tool (v5.1343.1 or higher)

Note: SP Flash Tool is backward compatible with older MTK platforms, which means you can (and should) use the most up to date version.

Let's then start with the tutorial...

• First of all, make sure that you have MediaTek DA USB VCOM drivers installed.

Flashing the whole ROM

• First of all open SP Flash Tool, then click Scatter-loading button to load the correct scatter file (MT6589_Android_scatter_emmc.txt, in this example because it is a MT6589 phone)  for your device and ignore any message that may appear.

• With device disconnected from the computer, turn it off, remove the battery for at least 5 seconds and then put the battery back in place (and don't turn on the device).
• Press CTRL+D (or hit Download button) and connect your device into the computer via USB data cable. The process will start and a red progress bar will appear.

•  After the red progress bar is complete, a purple progress bar will appear and bootloader will be downloaded.

• Right after bootloader is downloaded (i.e. the purple progress bar is complete) the rest of the download will start (you will see the yellow progress bar filling up).

• When the yellow bar is complete, you'll get a popup with a green circle and Download OK message, which means that the process has been successfully terminated.

• You can now safely disconnect your device and turn it on. The process ends here.

Flashing only part(s) of the ROM

• In case you want to flash just one part of the ROM, that is also possible. In the shown example, only recovery image will be flashed. Deselect all parts except the one(s) you want to flash and then press CTRL+D (or hit Download button).

Even if you don't have all the files, you can still flash one or more partitions (depending on which image files you have), but obviously the scatter file is always needed.

• The download of the chosen partition image will start and after the yellow bar is complete, the popup with the green circle should appear.

Attention: Please follow the instructions carefully. I will not take any responsibility on whatever may happen with your device.

Very important warning: Always make sure that you trust the sources of the ROM you download and know that it is meant for your device. In the past, after flashing a wrong preloader, the device would be completely dead (couldn't be powered on, it wouldn't charge and wasn't detected anymore by the computer). In this new platform, there is yet no information about whether or not this is still a problem, so be warned.

Last note: All needed tools and drivers can be downloaded from my MT65xx Tools 4shared folder. The password to login is bm-smartphone-reviews.blogspot.com. Have fun!