This week in search 10/16/09

This is part of a regular series of posts on search experience updates that runs on Fridays. Look for the label "This week in search" and subscribe to the series. - Ed.

This week, we made a few improvements to help webmasters better understand how their pages interact with Google search. Here's an overview:

Fetch as Googlebot
As a webmaster, have you ever wondered what Google "sees" when we visit your site? Our understanding of your web page affects which searches your page is returned for and its relevance rank. New this week, we're providing a tool as part of our Webmaster Tools Lab that lets you to see what Googlebot sees in the hope that this will help site owners better understand why we think your pages are relevant, and to what. We think this can help webmasters design pages that are easier for Googlebot to understand, and more importantly, easier for users to understand.

Malware details
You may occasionally see on Google a notice that says "This site may harm your computer." We place this warning in search result snippets when we see signals that a particular web page may be spreading malware. Webmasters occasionally will see this warning on one of their pages that wasn't intended to be malicious. This is because sometimes your site could be distributing malware — and you might not even know it or be able to easily find it. Malware details is designed to help webmasters track down what on their site is triggering this label and clear the problem — thus, making their page (and the web) safer for users.

Hope you enjoyed this week's features. Stay tuned for what's next!

Posted by Marissa Mayer, VP, Search Products & User Experience

A new home for accessibility at Google

Information access is at the core of Google’s mission, which is why we work to make the world's content available to people with disabilities, such as blindness, visual impairment, color deficiency, deafness, hearing loss and limited dexterity. Building accessible products isn't only the right thing to do, it also opens up Google services to very significant populations of people. According to the United Nations, 650 million people live with a disability, which makes them the world's largest minority.

We regularly develop and release accessibility features and improvements. Sometimes these are snazzy new applications like the a new talking RSS reader for Android devices. Other times the changes aren't flashy, but they're still important, such as our recent incremental improvements to WAI-ARIA support in Google Chrome (adding support for ARIA roles and labels). We also work on more foundational research to improve customization and access for our users, such as AxsJax (an Open Source framework for injecting usability enhancements into Web 2.0 applications).

We've written frequently about accessibility on our various blogs and help forums, but this information has never been easily accessible (pun intended) in one central place. This week we've launched a handy new website for Accessibility at Google to pull all our existing resources together: www.google.com/accessibility. Here you can follow the latest accessibility updates from our blogs, find resources from our help center, participate in a discussion group, or send us your feedback and feature requests. Around here, we often say, "launch early and iterate" — meaning, get something out the door, get feedback, and then improve it. In that tradition, our accessibility website is pretty simple, and we expect this site to be the first of many iterations. We're excited about the possibilities.

The thing we're most excited about is getting your feedback about Google products and services so we can make them better for the future. Take a look and let us know what you think.

Posted by Jonas Klink, Accessibility Product Manager

Street View: We can trike wherever you like

With Street View on Google Maps, you can take a virtual drive over the Golden Gate Bridge or see the bustle of Times Square from the comfort of your own home. But some of the country's most interesting and fun places aren't accessible with our Street View car. What if you want to tour the campuses of prospective universities, scout a new running trial, or plan the most efficient route to your favorite roller coasters in a theme park?

I first started thinking about this question around two years ago. My day job is working as a mechanical engineer on the Street View team, but I do a lot of mountain biking in my spare time. One day, while exploring some roads less traveled, I realized that I could combine these two pursuits and build a bicycle-based camera system for Street View. The result? The Street View trike:



I've already had a chance to take the Street View trike out to photograph some hard-to-reach places for Google Maps, like the Arastradero Open Preserve and LEGOLAND California. When I'm out riding — and once people understand what exactly I'm up to — I'm often asked if we can come to their alma mater, local bike trail or favorite beach boardwalk. Now, we're giving everyone a chance to tell us exactly where in the U.S. they'd like the trike to go next.

At www.google.com/trike, you can suggest interesting and unique spots in six categories:

• Parks & Trails
• University Campuses
• Pedestrian Malls (e.g., outdoor shopping areas, boardwalks)
• Theme Parks & Zoos
• Landmarks 
• Sports Venues (e.g., golf courses, racing tracks, stadium grounds)

Nominations will be open until October 28. We'll then comb through all of the suggestions and let all of you cast your final votes on a winner from each category for the Street View trike to visit. For any privately-owned or operated location, like a campus or theme park, we'll work directly with the relevant organization prior to collecting the imagery.

When we unveiled the Street View trike in the U.K., we received more than 10,000 nominations and 35,000 votes; Stonehenge and Warwick Castle were two of the top vote-getters. We can't wait to see what you'll come up with in the U.S. — head to www.google.com/trike to submit your most inspired ideas.



Posted by Dan Ratner, Senior Mechanical Engineer