Google Makes A Bunch Of Changes To Autocomplete

Google released a big list of 65 changes it has made over the course of August and September, and quite a few of them were tweaks to its autocomplete feature. This is all part of Google’s goal of getting you to what you’re looking for more quickly, and with less steps, something the search engine […]
Google Makes A Bunch Of Changes To Autocomplete
Written by Chris Crum

Google released a big list of 65 changes it has made over the course of August and September, and quite a few of them were tweaks to its autocomplete feature.

This is all part of Google’s goal of getting you to what you’re looking for more quickly, and with less steps, something the search engine has made tremendous strides on over the years.

The following 10 changes deal specifically with autocomplete:

  • #83197. [project ā€œAutocompleteā€] This launch introduced changes in the way we generate query predictions for Autocomplete.
  • essence. [project ā€œAutocompleteā€] This change introduced entity predictions in autocomplete. Now Google will predict not just the string of text you might be looking for, but the actual real-world thing. Clarifying text will appear in the drop-down box to help you disambiguate your search.
  • #84259. [project ā€œAutocompleteā€] This change tweaked the display of real-world entities in autocomplete to reduce repetitiveness. With this change, we don’t show the entity name (displayed to the right of the dash) when it’s fully contained in the query.
  • TSSPC. [project ā€œSpellingā€] This change used spelling algorithms to improve the relevance of long-tail autocomplete predictions.
  • Dot. [project ā€œAutocompleteā€] We improved cursor-aware predictions in Chinese, Japanese and Korean languages. Suppose you’re searching for “restaurants” and then decide you want “Italian restaurants.” With cursor-aware predictions, once you put your cursor back to the beginning of the search box and start typing “I,” the prediction system will make predictions for “Italian,” not completions of “Irestaurants.”
  • #84288. [project ā€œAutocompleteā€] This change made improvements to show more fresh predictions in autocomplete for Korean.
  • espd. [project ā€œAutocompleteā€] This change provided entities in autocomplete that are more likely to be relevant to the user’s country. See blog post for background.
  • #83391. [project ā€œAnswersā€] This change internationalized and improved the precision of thesymptoms search feature.
  • #82876. [project ā€œAutocompleteā€] We updated autocomplete predictions when predicted queries share the same last word.
  • #80435. [project ā€œAutocompleteā€] This change improves autocomplete predictions based on the user’s Web History (for signed-in users).

Last month, Google Autocomplete stopped excluding the term “bisexual,” attracting some headlines for the feature – probably the most positive headlines the feature has seen in recent memory, given that they didn’t involve Google getting in trouble for making controversial suggestions about specific people.

Subscribe for Updates

SearchNews Newsletter

Search engine news, tips, and updates for the search professional.

By signing up for our newsletter you agree to receive content related to ientry.com / webpronews.com and our affiliate partners. For additional information refer to our terms of service.

Notice an error?

Help us improve our content by reporting any issues you find.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us