When you type www.wikipedia.org into your browser's address bar, you expect nothing less than to be taken to Wikipedia. Chances are you're not giving much thought to the work being done in the background by the Domain Name System, or DNS.
Today, as part of our ongoing effort to make the web faster, we're launching our own public DNS resolver called Google Public DNS, and we invite you to try it out.
Most of us aren't familiar with DNS because it's often handled automatically by our Internet Service Provider (ISP), but it provides an essential function for the web. You could think of it as the switchboard of the Internet, converting easy-to-remember domain names — e.g., www.google.com — into the unique Internet Protocol (IP) numbers — e.g., 74.125.45.100 — that computers use to communicate with one another.
The average Internet user ends up performing hundreds of DNS lookups each day, and some complex pages require multiple DNS lookups before they start loading. This can slow down the browsing experience. Our research has shown that speed matters to Internet users, so over the past several months our engineers have been working to make improvements to our public DNS resolver to make users' web-surfing experiences faster, safer and more reliable. You can read about the specific technical improvements we've made in our product documentation and get installation instructions from our product website.
If you're web-savvy and comfortable with changing your network settings, check out the Google Code Blog for detailed instructions and more information on how to set up Google Public DNS on your computer or router.
As people begin to use Google Public DNS, we plan to share what we learn with the broader web community and other DNS providers, to improve the browsing experience for Internet users globally. The goal of Google Public DNS is to benefit users worldwide while also helping the tens of thousands of DNS resolvers improve their services, ultimately making the web faster for everyone.
Showing posts with label faster web. Show all posts
Showing posts with label faster web. Show all posts
Thursday, December 3, 2009
Monday, August 10, 2009
New tools for Google Services for Websites
Earlier this year, we launched Google Services for Websites, a program that helps partners, e.g., web hoster and access providers, offer useful and powerful tools to their customers. By making services, such as Webmaster Tools, Custom Search, Site Search and AdSense, easily accessible via the hoster control panel, hosters can easily enable these services for their webmasters. The tools help website owners understand search performance, improve user retention and monetize their content — in other words, run more effective websites.
Since we launched the program, several hosting platforms have enhanced their offerings by integrating with the appropriate APIs. Webmasters can configure accounts, submit Sitemaps with Webmaster Tools, create Custom Search Boxes for their sites and monetize their content with AdSense, all with a few clicks at their hoster control panel. More partners are in the process of implementing these enhancements.
We've just added new tools to the suite:
As always, we'd love to get feedback on how the program is working for you, and what improvements you'd like to see.
Since we launched the program, several hosting platforms have enhanced their offerings by integrating with the appropriate APIs. Webmasters can configure accounts, submit Sitemaps with Webmaster Tools, create Custom Search Boxes for their sites and monetize their content with AdSense, all with a few clicks at their hoster control panel. More partners are in the process of implementing these enhancements.
We've just added new tools to the suite:
- Web Elements allows your customers to enhance their websites with the ease of cut-and-paste. Webmasters can provide maps, real-time news, calendars, presentations, spreadsheets and YouTube videos on their sites. With the Conversation Element, websites can create more engagement with their communities. The Custom Search Element provides inline search over your own site (or others you specify) without having to write any code and various options to customize further.
- Page Speed allows webmasters to measure the performance of their websites. Snappier websites help users find things faster; the recommendations from these latency tools allow hosters and webmasters to optimize website speed. These techniques can help hosters reduce resource use and optimize network bandwidth.
- The Tips for Hosters page offers a set of tips for hosters for creating a richer website hosting platform. Hosters can improve the convenience and accessibility of tools, while at the same time saving platform costs and earning referral fees. Tips include the use of analytics tools such as Google Analytics to help webmasters understand their traffic and linguistic tools such as Google Translate to help websites reach a broader audience.
As always, we'd love to get feedback on how the program is working for you, and what improvements you'd like to see.
Tuesday, June 23, 2009
Let's make the web faster
From building data centers in different parts of the world to designing highly efficient user interfaces, we at Google always strive to make our services faster. We focus on speed as a key requirement in product and infrastructure development, because our research indicates that people prefer faster, more responsive apps. Over the years, through continuous experimentation, we've identified some performance best practices that we'd like to share with the web community on code.google.com/speed, a new site for web developers, with tutorials, tips and performance tools.
We are excited to discuss what we've learned about web performance with the Internet community. However, to optimize the speed of web applications and make browsing the web as fast as turning the pages of a magazine, we need to work together as a community, to tackle some larger challenges that keep the web slow and prevent it from delivering its full potential:
We are excited to discuss what we've learned about web performance with the Internet community. However, to optimize the speed of web applications and make browsing the web as fast as turning the pages of a magazine, we need to work together as a community, to tackle some larger challenges that keep the web slow and prevent it from delivering its full potential:
- Many protocols that power the Internet and the web were developed when broadband and rich interactive web apps were in their infancy. Networks have become much faster in the past 20 years, and by collaborating to update protocols such as HTML and TCP/IP we can create a better web experience for everyone. A great example of the community working together is HTML5. With HTML5 features such as AppCache, developers are now able to write JavaScript-heavy web apps that run instantly and work and feel like desktop applications.
- In the last decade, we have seen close to a 100x improvement in JavaScript speed. Browser developers and the communities around them need to maintain this recent focus on performance improvement in order for the browser to become the platform of choice for more feature-rich and computationally-complex applications.
- Many websites can become faster with little effort, and collective attention to performance can speed up the entire web. Tools such as Yahoo!'s YSlow and our own recently launched Page Speed help web developers create faster, more responsive web apps. As a community, we need to invest further in developing a new generation of tools for performance measurement, diagnostics, and optimization that work at the click of a button.
- While there are now more than 400 million broadband subscribers worldwide, broadband penetration is still relatively low in many areas of the world. Steps have been taken to bring the benefits of broadband to more people, such as the FCC's decision to open up the white spaces spectrum, for which the Internet community, including Google, was a strong champion. Bringing the benefits of cheap reliable broadband access around the world should be one of the primary goals of our industry.
Thursday, June 11, 2009
Snack time with the new iGoogle for Android and iPhone
(cross-posted with the Google Mobile Blog)We like iGoogle because it lets us "snack" on interesting information all day long. We can read a little bit of news here and there, glance at finance portfolios, take a look at the weather forecast, and then do a Google search. It doesn't require a big commitment of time and energy — it's simply there for us whenever we need it. This kind of availability is even more important on a phone, where it can take a long time to surf. That's why iGoogle is so convenient on mobile devices. When you're waiting in line, you can check iGoogle on your phone for a quick "info snack" — even in areas with mediocre network coverage.
But speed isn't everything. Many of you have told us that you wanted to use more of your iGoogle gadgets on your phone. You wanted to see your tabs, too. We read your blog comments and forum posts and put your requests at the top of our to-do list.
Today, we're excited to roll out an improved beta version of iGoogle for the iPhone and Android-powered devices. This new version is faster and easier to use. It supports tabs as well as more of your favorite gadgets, including those built by third-party developers. Note that not all gadgets — like those with Flash — will work in mobile browsers.
One of our favorite new features is the in-line display of articles for feed-based gadgets. That means you can read article summaries without leaving the page. You can also rearrange gadget order or keep your favorite gadgets open for your next visit. None of these changes will mess up the layout of gadgets on your desktop computer, so feel free to play around and tune your mobile experience.
The new version of iGoogle for mobile is available in 38 languages. To try it out, go to igoogle.com in your mobile browser and tap "Try the new Mobile iGoogle". Bookmark the page or make it your home page so you can return to it quickly. Finally, please fill out our survey by clicking on the "Tell us what you think" link at the top of the new home page. We'll continue to use your feedback to make iGoogle even better.
Update on 6/12 @ 8:50 AM: Video added. Check it out!
Thursday, June 4, 2009
Picasa Web Albums stays big, gets faster
I use Picasa to manage the photos on my computer in part because it's the fastest way to manage all of the pictures I take. When I started working on Picasa Web Albums, the speed and responsiveness of the desktop program were a tough act to follow. Typically, when you move your photos from the desktop to the web, you have to choose between viewing high resolution photos that take forever to download, and tiny photos that lack any detail. For Picasa Web Albums, we thought we could do better.
We chose to show large images, the very biggest we can fit into your browser window. If you open up a slideshow or full-screen view, we can fill your entire monitor. But it wasn't snappy enough for us, so we had a choice to make: either use smaller images, make the Internet faster, or make our code smarter. We think large images are important, because seeing a photo's little details can make a big difference, and as much as we wanted to, making the whole Internet faster was a little impractical in the short term. So we went deep into the code and gave it a thorough tune-up.
The results, I hope, speak for themselves. Take a look at any album or slideshow on Picasa Web (here's one of mine) and you should notice that browsing photos is significantly faster. Give full-screen mode a try to see even bigger photos. If you've got a reasonable connection to the Internet, you should be able to hold down one of the arrow keys and zip through the entire album at a pretty good clip, flip-book style. Of course, while you could zoom past entire albums at ludicrous speed, we hope you'll enjoying spending your time looking at the photos themselves, rather than navigating between them.
We chose to show large images, the very biggest we can fit into your browser window. If you open up a slideshow or full-screen view, we can fill your entire monitor. But it wasn't snappy enough for us, so we had a choice to make: either use smaller images, make the Internet faster, or make our code smarter. We think large images are important, because seeing a photo's little details can make a big difference, and as much as we wanted to, making the whole Internet faster was a little impractical in the short term. So we went deep into the code and gave it a thorough tune-up.
The results, I hope, speak for themselves. Take a look at any album or slideshow on Picasa Web (here's one of mine) and you should notice that browsing photos is significantly faster. Give full-screen mode a try to see even bigger photos. If you've got a reasonable connection to the Internet, you should be able to hold down one of the arrow keys and zip through the entire album at a pretty good clip, flip-book style. Of course, while you could zoom past entire albums at ludicrous speed, we hope you'll enjoying spending your time looking at the photos themselves, rather than navigating between them.
Thursday, May 21, 2009
Put the pedal to the metal with a faster Google Chrome
We introduced Google Chrome back in September, and it's received a great response so far. Since launching, we've been working hard on adding the top requested features and making Google Chrome even faster.
Today, we are updating to a new version of Google Chrome that is faster than ever. JavaScript-heavy web pages will now run about 30% faster. See the chart below or compare scores yourself.
Additionally, we've added some useful features like form autofill, full screen mode, and the ability to remove thumbnails from the New Tab page. Here's a short video demonstrating some of this new functionality:
If you're already using Google Chrome, you'll be automatically updated with these new features soon. If you haven't downloaded Google Chrome, get the latest version at google.com/chrome.
To read more about this update, visit the Google Chrome blog.
Today, we are updating to a new version of Google Chrome that is faster than ever. JavaScript-heavy web pages will now run about 30% faster. See the chart below or compare scores yourself.
Additionally, we've added some useful features like form autofill, full screen mode, and the ability to remove thumbnails from the New Tab page. Here's a short video demonstrating some of this new functionality:If you're already using Google Chrome, you'll be automatically updated with these new features soon. If you haven't downloaded Google Chrome, get the latest version at google.com/chrome.
To read more about this update, visit the Google Chrome blog.
Wednesday, May 20, 2009
Faster is better on Google Suggest
As we prepared to write this post, we discovered a common childhood passion for fast things: high-speed trains, roller coasters, firetrucks, and more. That may be a key part of why we're so excited to be working on Google Suggest, since it saves time by giving suggestions as we're typing our searches.
Today, we're introducing more features to Google Suggest to help you make your searches even faster. These features are rolling out gradually, so you should be able to see them soon.
Suggestions on the results page
Previously, we only showed suggestions based on your original search input. Now, when you make a search from a results page, we provide suggestions that relate to the current results page. As you can see in the example below, if your previous search was for roller coasters, when you begin a new query the first few suggestions are still related to roller coasters — helping you refine your search queries to quickly find what you want.
Personalized suggestions
Trying to remember that query which gave you the best results? You're not alone! We estimate that about a quarter of all signed-in searches are repeats from the past month. Now, if you're signed in with your Google account and have Web History enabled, we may show some of your relevant past searches as you type. Personalized suggestions will make it easier and faster for you to repeat searches that have worked before. Or, if you need to step away in the middle of a search task, this will help you continue your search tasks at a later time.
You can remove a personalized suggestion that you do not like by clicking "Remove", which will remove the search from your Web History. You can also remove searches from your Web History directly, manage Query Suggestions on the preferences page, or sign out of your Google account entirely to stop seeing personalized suggestions.
Navigational suggestions
If your first keystrokes indicate that you may be looking to navigate directly to a specific site, we'll list it and send you straight there if you click on it.
Sponsored links in suggestions
Similar to the navigational suggestions above, sometimes we detect that the most relevant completion for what you're typing is an ad. When an ad is shown, we mark it with the text "Sponsored Link" and a colored background, as on the results page.
We are also introducing a couple more changes to Suggest: we will no longer show the result count for items in the suggest box (we've gotten feedback that the numbers were not helpful in comparing the relevance of the queries) and we now bold the text of suggestions to help you more quickly scan the list. To learn more about Google Suggest, check out the help center.
We hope these new features save you time, so that you can get back to roller coasters, high-speed web surfing, action movies and each other that much faster.
Today, we're introducing more features to Google Suggest to help you make your searches even faster. These features are rolling out gradually, so you should be able to see them soon.
Suggestions on the results page
Previously, we only showed suggestions based on your original search input. Now, when you make a search from a results page, we provide suggestions that relate to the current results page. As you can see in the example below, if your previous search was for roller coasters, when you begin a new query the first few suggestions are still related to roller coasters — helping you refine your search queries to quickly find what you want.
Personalized suggestions
Trying to remember that query which gave you the best results? You're not alone! We estimate that about a quarter of all signed-in searches are repeats from the past month. Now, if you're signed in with your Google account and have Web History enabled, we may show some of your relevant past searches as you type. Personalized suggestions will make it easier and faster for you to repeat searches that have worked before. Or, if you need to step away in the middle of a search task, this will help you continue your search tasks at a later time.
You can remove a personalized suggestion that you do not like by clicking "Remove", which will remove the search from your Web History. You can also remove searches from your Web History directly, manage Query Suggestions on the preferences page, or sign out of your Google account entirely to stop seeing personalized suggestions.
Navigational suggestions
If your first keystrokes indicate that you may be looking to navigate directly to a specific site, we'll list it and send you straight there if you click on it.
Sponsored links in suggestions
Similar to the navigational suggestions above, sometimes we detect that the most relevant completion for what you're typing is an ad. When an ad is shown, we mark it with the text "Sponsored Link" and a colored background, as on the results page.
We are also introducing a couple more changes to Suggest: we will no longer show the result count for items in the suggest box (we've gotten feedback that the numbers were not helpful in comparing the relevance of the queries) and we now bold the text of suggestions to help you more quickly scan the list. To learn more about Google Suggest, check out the help center.
We hope these new features save you time, so that you can get back to roller coasters, high-speed web surfing, action movies and each other that much faster.
Thursday, December 11, 2008
Google Chrome (BETA)
Since we first released Google Chrome, the development team has been hard at work improving the stability and overall performance of the browser. In just 100 days, we have reached more than 10 million active users around the world (on all seven continents, no less) and released 14 updates to the product. We're excited to announce that with today's fifteenth release we are taking off the "beta" label!
Google Chrome is a better browser today thanks to the many users who sent their feedback and the many more who enabled automatic crash reports, helping us rapidly diagnose and fix issues. Some of the areas where we've made great progress include:
Better stability and performance of plug-ins (particularly video). Video and audio glitches were among the most common bugs fixed during the beta period. If you had problems watching videos with Google Chrome in the past, you should be pleasantly surprised with the performance now.
Even more speed. Google Chrome starts up fast, loads pages quickly, and just keeps getting faster. Since the first beta, the V8 JavaScript engine runs 1.4 times faster on the SunSpider benchmark and 1.5 times faster on the V8 benchmark — and there is more speed to come.
Bookmark manager and privacy controls. We heard you! Better bookmark features were a top request from our users. It's now easier to switch between another browser and Google Chrome with the bookmark import and export features, and we added a new simple way to manage large numbers of bookmarks, too. We also wanted to make it even easier for you to control your browsing data, so all of the features in Google Chrome which affect user privacy are now grouped in one place with detailed explanations for each one.
We've taken security very seriously from the beginning and we will continue to look for ways to make Google Chrome and all browsers even more secure. Google Chrome's unique sandbox technology creates an additional layer of defense against harmful software, while the Safe Browsing feature provides protection against phishing and malware attacks for many browser users.
We have removed the beta label as our goals for stability and performance have been met but our work is far from done. We are working to add some common browser features such as form autofill and RSS support in the near future. We are also developing an extensions platform along with support for Mac and Linux. If you are already using Google Chrome, the update system ensures that you get the latest bug fixes and security patches, so you will get the newest version automatically in the next few days. If you haven't used Google Chrome for a while, now might be a good time to give it another spin.
Download Google Chrome and try it out. Let us know what you think.
Google Chrome is a better browser today thanks to the many users who sent their feedback and the many more who enabled automatic crash reports, helping us rapidly diagnose and fix issues. Some of the areas where we've made great progress include:
Better stability and performance of plug-ins (particularly video). Video and audio glitches were among the most common bugs fixed during the beta period. If you had problems watching videos with Google Chrome in the past, you should be pleasantly surprised with the performance now.
Even more speed. Google Chrome starts up fast, loads pages quickly, and just keeps getting faster. Since the first beta, the V8 JavaScript engine runs 1.4 times faster on the SunSpider benchmark and 1.5 times faster on the V8 benchmark — and there is more speed to come.
Bookmark manager and privacy controls. We heard you! Better bookmark features were a top request from our users. It's now easier to switch between another browser and Google Chrome with the bookmark import and export features, and we added a new simple way to manage large numbers of bookmarks, too. We also wanted to make it even easier for you to control your browsing data, so all of the features in Google Chrome which affect user privacy are now grouped in one place with detailed explanations for each one.
We've taken security very seriously from the beginning and we will continue to look for ways to make Google Chrome and all browsers even more secure. Google Chrome's unique sandbox technology creates an additional layer of defense against harmful software, while the Safe Browsing feature provides protection against phishing and malware attacks for many browser users.
We have removed the beta label as our goals for stability and performance have been met but our work is far from done. We are working to add some common browser features such as form autofill and RSS support in the near future. We are also developing an extensions platform along with support for Mac and Linux. If you are already using Google Chrome, the update system ensures that you get the latest bug fixes and security patches, so you will get the newest version automatically in the next few days. If you haven't used Google Chrome for a while, now might be a good time to give it another spin.
Download Google Chrome and try it out. Let us know what you think.
Tuesday, November 4, 2008
A vote for broadband in the "white spaces"
All eyes are on the presidential election today, but another important vote just took place at the Federal Communications Commission. By a vote of 5-0, the FCC formally agreed to open up the "white spaces" spectrum -- the unused airwaves between broadcast TV channels -- for wireless broadband service for the public. This is a clear victory for Internet users and anyone who wants good wireless communications.The FCC has been looking at this issue carefully for the last six years. Google has worked hard on this matter with other tech companies and public interest groups because we think that this spectrum will help put better and faster Internet connections in the hands of the public. We also look forward to working with the FCC to finalize the method used to compute power levels of empty channels adjacent to TV channels (we have a number of public filings before the commission in this area and it is a vital issue in urban areas).
I've always thought that there are a lot of really incredible things that engineers and entrepreneurs can do with this spectrum. We will soon have "Wi-Fi on steroids," since these spectrum signals have much longer range than today's Wi-Fi technology and broadband access can be spread using fewer base stations resulting in better coverage at lower cost. And it is wonderful that the FCC has adopted the same successful unlicensed model used for Wi-Fi, which has resulted in a projected 1 billion Wi-Fi chips being produced this year. Now that the FCC has set the rules, I'm sure that we'll see similar growth in products to take advantage of this spectrum.
As an engineer, I was also really gratified to see that the FCC decided to put science over politics. For years the broadcasting lobby and others have tried to spread fear and confusion about this technology, rather than allow the FCC's engineers to simply do their work.
Finally, I want to applaud and thank FCC Chairman Kevin Martin, the other commissioners, and the FCC Office of Engineering and Technology for their leadership in advancing this important issue. And, thanks to the more than 20,000 of you who took a stand on this issue through our Free the Airwaves campaign, the FCC heard a clear message from consumers: these airwaves can bring wireless Internet to everyone everywhere.
Thursday, October 23, 2008
Introducing Gmail for mobile 2.0
Whether you've lost signal on the subway or turned your phone's wireless connection off on an airplane, you no longer have to wait to read and compose your Gmail or Google Apps email on your phone. Today, we're happy to introduce Gmail for mobile 2.0, designed to be faster and more reliable in low signal areas and to even support basic offline access on phones like the Nokia N95, Sony Ericsson W910i, and BlackBerry Curve. Our latest version of Gmail for mobile also allows you to access multiple Gmail or Google Apps email accounts from the same application.
To find out more about Gmail for mobile 2.0, check out this post on the Google Mobile blog and watch this demo video:
To find out more about Gmail for mobile 2.0, check out this post on the Google Mobile blog and watch this demo video:
Friday, August 1, 2008
Search quality, continued
A few weeks back Udi Manber introduced the search quality group, and the previous posts in this series talked about the ranking of documents. While the ranking of web documents forms the core of what makes search at Google work so well, your search experience consists of much more than that. In this post, I'll describe the principles that guide our development of the overall search experience and how they are applied to the key aspects of search. I will also describe how we make sure we are on the right track through rigorous experimentation. And the next post in this series will describe some of the experiments currently underway.
Let me introduce myself. I'm Ben Gomes, and I've been working on search at Google since 1999, mostly on search quality. I've had the good fortune to contribute to most aspects of the search engine, from crawling the web to ranking. More recently, I've been responsible for the engineering of the interface for search and search features.
A common reaction from friends when I say that I now work on Google's search user interface is "What do you do? It never changes." Then they look at me suspiciously and tell me not to mess with a good thing. Google is fine just the way it is -- a plain, fast, simple web page. That's great, but how hard can that be?"
To help answer that question, let me start with our main goal in web search: to get you to the web pages you want as quickly as possible. Search is not an end in itself; it is merely a conduit. This goal may seem obvious, but it makes a search engine radically different from most other sites on the web, which measure their success by how long their users stay. We measure our web search success partly by how quickly you leave (happily, we hope!). There are several principles we use in getting you to the information you need as quickly as possible:
The start of your search is typing in a query. A common cause of frustration is if you don't know the correct spelling of a word! Spell correction -- which seems like a simple and obvious feature -- hides many technical challenges. No common English dictionaries would ever include the correct spelling of Britney Spears, for instance (who, probably completely unbeknownst to her, has become the poster child example for this feature). We do a huge amount of analysis of the billions of pages on the web and our query logs to determine what are "real words" on the web, and what are likely to be misspellings. The system that gives you the spell correction has to, in a fraction of a second, consider a huge number of possible words you might have meant (vastly greater than any dictionary ever manually constructed) and determine if there is a more likely query you meant to type. When we are confident that you actually meant to type something else, we take a rare liberty with our search results: we try to distract you from looking at the top result on the page. The spelling correction is in your line of sight and colored a bright must-see red. Furthermore, we now make sure that nothing else on the page is red, unless it is as important to you as spelling! (so far, nothing is). The algorithms involved in spell correction are constantly getting better. They now work in a large number of languages and are even better at detecting when you have made a spelling mistake. Getting the spelling of your query right is so important that we are considering showing you the results of the spell-corrected query in the middle of the page (just in case you missed our bright red text at the top and bottom!).
Having formulated your query correctly, the next task is to pick a page from the result list. For each result, we present the title and url, and a brief two line snippet. Pages that don't have a proper title are often ignored by users. One of the bigger recent changes has been to extract titles for pages that don't specify an HTML title -- yet a title on the page is clearly right there, staring at you. To "see" that title that the author of the page intended, we analyze the HTML of the page to determine the title that the author probably meant. This makes it far more likely that you will not ignore a page for want of a good title. Below the title comes the snippet, and a key early innovation was in what Google showed for the snippet. At the time, search engines showed you the first two lines of the web page; Google, instead, showed you parts of the page where your actual search keywords showed up (information retrieval experts call this "keywords-in-context"). Showing keywords-in-context is visually simple and virtually indistinguishable from the simpler style of snippets, but vastly more useful in helping you decide which page to visit. This simplicity belies underlying complexity: when we create a snippet we have to go through the actual text from each result to find the most relevant part (which contain your keywords) rather than just giving you the first few lines.
We have been making improvements to our snippets over time with algorithms for determining the relevance of portions of the page. The changes range from the subtle -- we highlight synonyms of your query terms in the results -- to more obvious. Here's an example screenshot where the user searched for "arod" and you can see that Alex and Rodriguez are bolded in the search result snippet, based on our analysis that you might plausibly be referring to him:
As a more obvious example, we now extract and show you the byline date from pages that have one. These byline dates are expressed in a myriad formats which we extract and present uniformly, so that you can scan them easily:
For one of the most common types of user needs, navigational queries -- where you type in the name of a web site you know -- we have introduced shortcuts (we refer to them as sitelinks). These sitelinks allow you to get to the key parts of the site and illustrate many of the same principles alluded to above; they are a simple addition to the top search result that adds a small amount of extra text to the page.
For instance, the home page of Hewlett-Packard has almost 60 links, in a two-level menu system. Our algorithms, using a combination of different signals, pick the top ones among these that we think you are most likely to want to visit.
What if you did not find what you were looking for among the top results? In that case, you probably need to try another query. We help you in this process by providing a set of query refinements at the bottom of the results page -- even if they don't give you the query that you need, they provide hints for different (likely more successful) directions in which you could refine your query. By placing the query refinements at the bottom of the page, the refinements don't distract users, but are there to help if the rest of the search results didn't serve a user's information need.
I've described several key aspects of the search experience, including where we have made many changes over time -- some subtle, some more obvious. In making these changes to the search experience, how do we know we've succeeded, that we've not messed it up? We constantly evaluate our changes by sharing them with you! We launch proposed changes to a tiny fraction of our users and evaluate whether it seems to be helping or hurting their search experience. There are many metrics we use to determine if we've succeeded or failed. The process of measuring these improvements is a science in itself, with many potential pitfalls. Our experimental methodology allows us to explore a range of possibilities and launch the ones that work the best. For every feature that we launch, we have frequently run a large number of experiments that did not see the light of day.
So let me answer the question I started with: We're actually constantly changing Google's result page and have been doing so for a long time. And no, we won't mess with a good thing. You won't let us.
In the next post in this series, I'll talk about some of the experiments we are running, and what we hope to learn from them.
Let me introduce myself. I'm Ben Gomes, and I've been working on search at Google since 1999, mostly on search quality. I've had the good fortune to contribute to most aspects of the search engine, from crawling the web to ranking. More recently, I've been responsible for the engineering of the interface for search and search features.
A common reaction from friends when I say that I now work on Google's search user interface is "What do you do? It never changes." Then they look at me suspiciously and tell me not to mess with a good thing. Google is fine just the way it is -- a plain, fast, simple web page. That's great, but how hard can that be?"
To help answer that question, let me start with our main goal in web search: to get you to the web pages you want as quickly as possible. Search is not an end in itself; it is merely a conduit. This goal may seem obvious, but it makes a search engine radically different from most other sites on the web, which measure their success by how long their users stay. We measure our web search success partly by how quickly you leave (happily, we hope!). There are several principles we use in getting you to the information you need as quickly as possible:
- A small page. A small page is quick to download and generally faster for your browser to display. This results in a minimalist design aesthetic; extra fanciness in the interface slows down the page without giving you much benefit.
- Complex algorithms with a simple presentation. Many search features require a great deal of algorithmic complexity and a vast amount of data analysis to make them work well. The trick is to hide all that complexity behind a clean, intuitive user interface. Spelling correction, snippets, sitelinks and query refinements are examples of features that require sophisticated algorithms and are constantly improving. From the user's point of view search, almost invisibly, just works better.
- Features that work everywhere. Features must be designed such that the algorithms and presentation can be adapted to work in all languages and countries. Consider the problem of spell correction in Chinese, where user queries are often not broken up into words or Hebrew/Arabic, where text is written right to left (interestingly, this is believed to be an example of first-mover disadvantage -- when chiseling on stone, it is easier to hold the hammer in your right hand!).
- Data driven decisions - experiment, experiment, experiment. We try to verify that we've done the right thing by running experiments. Designs that may seem promising may end up testing poorly.
The start of your search is typing in a query. A common cause of frustration is if you don't know the correct spelling of a word! Spell correction -- which seems like a simple and obvious feature -- hides many technical challenges. No common English dictionaries would ever include the correct spelling of Britney Spears, for instance (who, probably completely unbeknownst to her, has become the poster child example for this feature). We do a huge amount of analysis of the billions of pages on the web and our query logs to determine what are "real words" on the web, and what are likely to be misspellings. The system that gives you the spell correction has to, in a fraction of a second, consider a huge number of possible words you might have meant (vastly greater than any dictionary ever manually constructed) and determine if there is a more likely query you meant to type. When we are confident that you actually meant to type something else, we take a rare liberty with our search results: we try to distract you from looking at the top result on the page. The spelling correction is in your line of sight and colored a bright must-see red. Furthermore, we now make sure that nothing else on the page is red, unless it is as important to you as spelling! (so far, nothing is). The algorithms involved in spell correction are constantly getting better. They now work in a large number of languages and are even better at detecting when you have made a spelling mistake. Getting the spelling of your query right is so important that we are considering showing you the results of the spell-corrected query in the middle of the page (just in case you missed our bright red text at the top and bottom!).
Having formulated your query correctly, the next task is to pick a page from the result list. For each result, we present the title and url, and a brief two line snippet. Pages that don't have a proper title are often ignored by users. One of the bigger recent changes has been to extract titles for pages that don't specify an HTML title -- yet a title on the page is clearly right there, staring at you. To "see" that title that the author of the page intended, we analyze the HTML of the page to determine the title that the author probably meant. This makes it far more likely that you will not ignore a page for want of a good title. Below the title comes the snippet, and a key early innovation was in what Google showed for the snippet. At the time, search engines showed you the first two lines of the web page; Google, instead, showed you parts of the page where your actual search keywords showed up (information retrieval experts call this "keywords-in-context"). Showing keywords-in-context is visually simple and virtually indistinguishable from the simpler style of snippets, but vastly more useful in helping you decide which page to visit. This simplicity belies underlying complexity: when we create a snippet we have to go through the actual text from each result to find the most relevant part (which contain your keywords) rather than just giving you the first few lines.
We have been making improvements to our snippets over time with algorithms for determining the relevance of portions of the page. The changes range from the subtle -- we highlight synonyms of your query terms in the results -- to more obvious. Here's an example screenshot where the user searched for "arod" and you can see that Alex and Rodriguez are bolded in the search result snippet, based on our analysis that you might plausibly be referring to him:
As a more obvious example, we now extract and show you the byline date from pages that have one. These byline dates are expressed in a myriad formats which we extract and present uniformly, so that you can scan them easily:
For one of the most common types of user needs, navigational queries -- where you type in the name of a web site you know -- we have introduced shortcuts (we refer to them as sitelinks). These sitelinks allow you to get to the key parts of the site and illustrate many of the same principles alluded to above; they are a simple addition to the top search result that adds a small amount of extra text to the page.
For instance, the home page of Hewlett-Packard has almost 60 links, in a two-level menu system. Our algorithms, using a combination of different signals, pick the top ones among these that we think you are most likely to want to visit.What if you did not find what you were looking for among the top results? In that case, you probably need to try another query. We help you in this process by providing a set of query refinements at the bottom of the results page -- even if they don't give you the query that you need, they provide hints for different (likely more successful) directions in which you could refine your query. By placing the query refinements at the bottom of the page, the refinements don't distract users, but are there to help if the rest of the search results didn't serve a user's information need.
I've described several key aspects of the search experience, including where we have made many changes over time -- some subtle, some more obvious. In making these changes to the search experience, how do we know we've succeeded, that we've not messed it up? We constantly evaluate our changes by sharing them with you! We launch proposed changes to a tiny fraction of our users and evaluate whether it seems to be helping or hurting their search experience. There are many metrics we use to determine if we've succeeded or failed. The process of measuring these improvements is a science in itself, with many potential pitfalls. Our experimental methodology allows us to explore a range of possibilities and launch the ones that work the best. For every feature that we launch, we have frequently run a large number of experiments that did not see the light of day.
So let me answer the question I started with: We're actually constantly changing Google's result page and have been doing so for a long time. And no, we won't mess with a good thing. You won't let us.
In the next post in this series, I'll talk about some of the experiments we are running, and what we hope to learn from them.
Thursday, July 10, 2008
Google Mobile App: faster, easier search on iPhone & iPod Touch
Our first downloadable iPhone application is here. It's free, and it makes searching faster and easier. It's never as easy to type on a mobile phone as on a full keyboard and the mobile network is rarely as fast as a desktop connection. So Google Mobile App starts working as soon as you type. Smart features mean you'll get what you're looking for in fewer key presses than before. For instance, we've added the power of suggest (type "lost in" and one touch completes "lost in translation") and My Location (type "coffee" and one touch shows cafes right where you are on a map) to help you search.
We've also brought Google search to your iPhone's address book to make it easy to contact the people you call or text most often. To learn more and see a video showing the App in action, check out this post on the Google Mobile Blog.
U.S. users can get Google Mobile App right now. Tap the App Store icon on your iPhone, or open iTunes, and search for 'Google Mobile App'. (You need to have the latest iPhone software update to see it.)
Wednesday, April 16, 2008
A whole new world to explore
On the Google Earth team, we're big fans of Earth Day, so much so that we couldn't hold out until it arrives next week to release our latest labor of love: Google Earth 4.3. With this version, we have completely rethought how you might interact with the 3D world. We've redesigned the navigation to make it much easier to fly from the heavens down to the streets of your town. And with all of the great user-created buildings in the 3D Warehouse, we wanted to make it easy for you to get right up close to see the rich detail.
Here's a sample of what you'll find in this release:
Tuesday, November 6, 2007
The road to better path-finding
Way back at the end of 2005, Google Maps' driving directions were on par with other sites, providing basic driving directions in a few seconds. But the nature of the existing system made it nigh impossible to make it faster, add new features, or improve the quality of the routes. And better directions can yield tangible real-world benefits by saving people time and fuel, alleviating frustration, and making travel more pleasant. For all these reasons, it made sense to take a fresh look at the problem and to try to reinvent things such that we could provide a service markedly superior to the status quo.
It's important to us to solve big problems. Automatically finding routes quickly is a hard problem -- especially at a global scale (there are several hundred million road segments worldwide). Even if a routing program is needed to only look at 10% of the map and only examine each segment for a microsecond, it would take tens of seconds to compute a path. Route-finding has to be done automatically because it would be impossibly time-consuming to compute the best routes between all pairs of locations by hand.
Fortunately, we have the tools, technologies, and expertise that make it easier to tackle such hard problems and to build systems for searching large data sets quickly. A small group of engineers (of which I was a part) created the Google Maps route-finding project in Kirkland, WA with the hope of building a world-class system for route-finding. This is the first project I've worked on at Google, and it has given me the opportunity to learn all about the infrastructure we have to build and launch products and features.
We started with the geographic data sets already in use by other groups at Google. Then we designed, built, tested, and deployed a complete route-finding solution in under 12 months. Commutes across the 520 Bridge from Seattle became a favorite test query. As someone with a background in path planning and robotics, it's been great to work on a problem with such substantial theoretical and practical aspects. It took 10 months of hard work, thousands of MapReduce passes, and an uncountable number of lattes to complete.
And 'complete' doesn't really capture it. Our new route-finding system is hundreds of times faster: it can find and describe a cross-continental shortest path in well under a second. Shorter paths can be found proportionately faster.
As evidenced by our 'draggable directions' launch earlier this year, this kind of performance fundamentally changes your Maps experience. It's now possible for you to change your route by simply dragging it or its endpoints. (Here's an example of the above route adjusted to use I-90 instead of WA-520.) No other planning service provides this feature, and it would have been impossible to ship without the massive speedup provided by the system we created.
In the last few months, we've also added other features, like 'avoid highways' and 'estimated time-in-traffic.' Plus, we now cover about 50 countries worldwide. We've raised the bar for what a route-finding system can and should provide. We're pleased with what we've built, and you can expect further improvements in the coming months.
Just recently, the Google Maps route-finding team moved to our new Fremont Engineering office. I'm happy to report we don't have to commute across Lake Washington at all anymore. In fact, nearly half the team cycles in every day! And we're always looking for great people, so if any of this sounds like the kind of challenge you'd be up for, we'd love to hear from you.
Subscribe to:
Posts (Atom)
