Search Central LiveDeep Dive Europe 2026

Knowledge base v2.13.0 · Community edition · data through 2 October 2026

Topic · Serving and ranking

Query understanding

Google rewrites pretty much every query before looking it up: it detects the language (falling back on location and browser settings for brand-only queries), drops stop words, recognises entities and expands the query with synonyms, so a short query can become a much longer internal one. Its synonyms are learned from search behaviour rather than catalogued by linguists, so words people use interchangeably count as synonyms, while 'siblings' such as Canon and Nikon are kept apart, and spellings with and without diacritics are generally treated as the same. Google's How Search Works page confirms the synonym and spelling systems; stop words, siblings and the rewriting detail were said at the event and are not in Google's docs. Fan-out queries from the AI features pass through the same query understanding, which also predicts which result types a query gets, using historical interaction data for ambiguous queries such as 'orange'. Query processing deliberately mirrors indexing, as Day 2 said of word segmentation, and the diacritics point extends Day 2's statement that Google usually understands words with or without accents; Google's summary slide added that typos and plurals need no attention because Google rewrites them automatically. Day 1's second recording put this at the start of serving: Cherry Prommawin said serving begins by interpreting the query, cleaning it up, detecting its language and expanding it; Gary Illyes contrasted 1990s searchers who had to 'speak machine' with today's natural-language queries, and said MUM helps interpret the context of query words. On Day 2 the non-Latin-script talk added that users may type the same Persian query in their own script or in Latin letters with the same intent, as Google's 2023 post on multilingual searches describes for Hindi.

What to do

  • Write each page in the words its audience uses; do not add synonym lists or every spelling variant, which Google expands itself.
  • Search for each variant of a key term before writing: if the variants bring up the same entity, pick one; if a phrase returns unrelated results, use that phrase where it matters.
  • On multilingual sites, annotate language versions with hreflang, because a brand-only query does not tell Google which language the user wants.

Day 1: Crawling 3

Said on stage 3

StageConsistent with docsD1-C218

Google said MUM helps it understand the context of the words in a query: a search for hiking shoes that mentions Mount Everest rather than Kilimanjaro gets results suited to that climb.

Speaker Gary IllyesIn Day 1, 11:45 · How Search works and where's AI?Evidence transcript

  • Extends D1-C044 Day 1: MUM (Multitask Unified Model) understands information across text, images, audio and video, and processes…

Day 2: Indexing 2

Said on stage 1

StageConsistent with docsD2-C965

Users of non-Latin-script languages do not always search in their own script: the same Persian query may be typed in Persian script or in Latin letters, with the same intent and the same expected results.

Speaker a second community speakerIn Day 2, 14:30 · Lightning session G: InternationalisationEvidence transcript

Used byrequirement DEV-INT-11glossary term Transliterated queries

  • Extends D2-C599 Day 2: Google usually understands non-English words typed 'in English' (probably meaning romanised, Latin-letter…

What Google's documentation says 1

DocsSourceD2-C981

Google's post on multilingual searches (8 September 2023) says that, because of typing difficulty on some keyboards, a person in India might search in Hindi using Latin rather than Devanagari characters and want and receive Hindi results written either way.

Publisher Search Central blog (8 September 2023)Annotates Day 2, 14:30 · Lightning session G: Internationalisation

Used byrequirement DEV-INT-11glossary term Transliterated queries

Day 3: Serving: Ranking, Search Console, and Performance 69

Shown on screen 5

SlideConsistent with docsD3-C001

Google's opening slide for serving day showed serving as the third stage after crawling and indexing, and drew Google's serving infrastructure as query understanding and retrieval leading into the index, then ranking and search features leading back to the user, for the example query 'Where to eat jamon'.

Speaker GoogleIn Day 3, 10:15 · Welcome to serving and ranking day!Evidence slide photo

  • Repeated by D3-C321 Day 3: Google's serving diagram shows the query passing through query understanding and retrieval to the index, then…
SlideConsistent with docsD3-C067

Google's summary slide on query understanding told site owners not to worry about typos and plurals, which Google rewrites automatically.

“Don't worry about typos & plurals!”

Wording checked against the slide or recording

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence slide photo, transcript

SlideNot in docsD3-C069

Google's summary slide on query understanding said Google's synonyms are not always language-based; on stage this was explained as words people use interchangeably counting as synonyms even when they are not synonyms linguistically.

“Google's synonyms aren't always language-based”

Wording checked against the slide or recording

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence slide photo, transcript

Said on stage 55

StageConsistent with docsD3-C004

Google placed query understanding in the traditional part of Search, the part where answers are looked up in an index and then presented and ranked.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

  • Extended by D3-C304 Day 3: Which kinds of results Google shows for a query is decided by query understanding, which tries to predict the…
StageConsistent with docsD3-C006

Google's first step in understanding almost any query is to detect its language, which tells Google roughly what content the user wants: a query in German suggests German content, a query in English English content.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

Used byrequirement DEV-INT-07glossary term Query understanding

  • Extends D2-C654 Day 2: In ranking, country and language signals help Google serve users the right content for their country and…
StageConsistent with docsD3-C007

Query language detection works poorly when someone searches only for a brand name, such as Facebook or Google, because the query does not show which language the user wants results in.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

Used byrequirement DEV-INT-03

  • Extends D1-C215 Day 1: Serving starts with interpreting the query, which includes cleaning it up, detecting its language and…
StageConsistent with docsD3-C008

For brand-only queries Google falls back on other information, such as the user's location and browser settings, to work out the language of the results.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

Used byrequirement DEV-INT-03

StageNot in docsD3-C011

Google named Thai as a language that makes query understanding more complex because it does not separate words with spaces; the speaker added, hedging with 'apparently', that Thai uses spaces to separate sentences.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

  • Extends D2-C320 Day 2: Text in languages written without spaces, such as Thai and Chinese, would end up in the index as long strings…
StageNot in docsD3-C013

Google's query processing deliberately mirrors indexing: a query is transformed into something that can be matched against the index, and stop word removal is part of that transformation.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

  • Extends D2-C321 Day 2: For languages written without spaces, such as Thai and Chinese, Google uses exactly the same word…
  • Extends D2-C737 Day 2: A search query is broken into words with the same segmenter or tokenizer that Google used to build the index.
StageConsistent with docsD3-C015

Google said the difference between words and entities can be seen in Google Trends, where a term can be searched as words or as an entity (Trends calls these a search term and a topic).

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

  • Extends D2-C761 Day 2: The Google Trends Explore page, which Google called the heart of Trends, shows search interest in a query or…
StageNot in docsD3-C019

In Google's example, the query word 'photograph' could be expanded to 'image', 'picture' or 'photo', but one German candidate had to be dropped because the similar German word means 'photographer', so expansions are language-specific.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

StageConfirmed by docsD3-C023

Site owners do not need to list all synonyms of a term on a page, because Google already knows the synonyms and looks for them on pages too.

“you don't have to do that SEO meme of, like, list all the synonyms on your page”

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

Used byrequirement DEV-INT-11

StageNot in docsD3-C026

Google suggested a test: a search that lists a term's synonyms joined with OR will probably return results very similar to the plain query, because Google adds the synonyms itself (part of the sentence is unclear in the recording).

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

StageNot in docsD3-C040

Google learns synonyms and siblings from search behaviour: words people search with in the same way become synonyms, while frequent comparison queries mark words as not interchangeable (the end of the sentence is unclear in the recording).

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

StageConsistent with docsD3-C041

Google does not prefer English words on pages in other languages; the idea that Google, as an American company, wants to see everything in English is wrong.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

StageConsistent with docsD3-C044

When Google already matches a term's variants, there is no need to add them to pages artificially; mention another name only where visitors might not understand otherwise.

“I wouldn't artificially just stuff those variations in there.”

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

Used byrequirement DEV-INT-11

StageConfirmed by docsD3-C048

Google generally treats spellings with and without diacritics as synonyms behind the scenes, for example a German 'ü' written as 'ü', as 'ue' or left out.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

Used byrequirement DEV-INT-11

  • Extends D2-C600 Day 2: Google usually understands a query word whether it is written with or without diacritics (accents).
StageConsistent with docsD3-C056

Google's generative AI features in Search build on the traditional ways of searching, so query understanding also flows into AI Overviews and AI Mode.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

  • Repeats D1-C051 Day 1: Three reasons were given: generative AI features are built directly on the core ranking systems, query…
StageConsistent with docsD3-C059

Google treats fan-out queries generated by the LLM the same way as queries typed by users, so understanding how normal queries work explains fan-out queries too.

Speaker John MuellerIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

  • Extends D2-C727 Day 2: Google said that when AI Overviews or AI Mode run a query fan-out, the generated queries are sent to Google's…
  • Extends D1-C172 Day 1: Google said the Gemini model lets Search understand the user's intent, and query fan-out then adds further…
StageNot in docsD3-C075

At retrieval, Google splits the query into words, applies query understanding and expansion, and matches the words and their expansions against the posting lists.

Speaker Gary IllyesIn Day 3, 10:25 · Making sense of users' queriesEvidence transcript

Used byglossary term Retrieval

  • Extends D2-C736 Day 2: In posting-list retrieval, the posting lists of the query's words are intersected, which yields an unranked…
  • Extends D2-C738 Day 2: At retrieval, Google looks up the posting lists of the query words that are actually important rather than of…
StageConsistent with docsD3-C304

Which kinds of results Google shows for a query is decided by query understanding, which tries to predict the intent behind the query.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

  • Extends D3-C004 Day 3: Google placed query understanding in the traditional part of Search, the part where answers are looked up in…
StageConsistent with docsD3-C305

When the query itself names the wanted result type, as 'pictures' does in 'orange pictures' (or a query asking for videos or news), Google can read the intent directly from that word.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

StageNot in docsD3-C311

Google handles an image used as a search query much like a text query interpreted as an embedding: the image is broken down into vectors (embeddings) that are then searched for in the index.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

  • Extends D2-C740 Day 2: Besides posting lists, Google can retrieve documents through vector embeddings: parts of documents are…
  • Repeats D1-C224 Day 1: For visual search, Google breaks an image down into vectors, sends the vectors to the index and returns…

What Google's documentation says 6

DocsSourceD3-C087

Google's How Search Works page says understanding a query ranges from recognising and correcting spelling mistakes to a synonym system that finds relevant documents without the exact words searched, such as 'adjust laptop brightness' for 'change laptop brightness'.

Publisher Google Search (How Search Works)Annotates Day 3, 10:25 · Making sense of users' queries

DocsSourceD3-C089

Google's SEO Starter Guide advises anticipating the different words readers search with (some search for 'charcuterie', others for 'cheese board') but not worrying about every variation, because Google's language matching systems relate pages to queries without the exact terms.

Publisher Google Search CentralAnnotates Day 3, 10:25 · Making sense of users' queries

DocsSourceD3-C090

Google's Search Help says the language of search results is chosen from the language of the query, the user's Google language setting, the device's languages and the user's location, which helps when a word such as 'taxi' is the same in several languages.

Publisher Google Search HelpAnnotates Day 3, 10:25 · Making sense of users' queries

DocsSourceD3-C091

A 2006 Search Central blog post says Google considers pages with and without accents for a query word (México and Mexico), and that which accented characters count as equivalent depends on the searcher's interface language.

Publisher Search Central blog (1 September 2006)Annotates Day 3, 10:25 · Making sense of users' queries

Analysis by the author 3

Across days and sessions 18

  1. Stage D1-C218 Day 1 · How Search works and where's AI?

    Google said MUM helps it understand the context of the words in a query: a search for hiking shoes that mentions Mount Everest rather than Kilimanjaro gets results suited to that climb.

    extends
    Slide D1-C044 Day 1 · How Search works and where's AI?

    MUM (Multitask Unified Model) understands information across text, images, audio and video, and processes information in more than 75 languages.

  2. Stage D2-C965 Day 2 · Lightning session G: Internationalisation

    Users of non-Latin-script languages do not always search in their own script: the same Persian query may be typed in Persian script or in Latin letters, with the same intent and the same expected results.

    extends
    Stage D2-C599 Day 2 · Focusing on Internationalisation and Localisation

    Google usually understands non-English words typed 'in English' (probably meaning romanised, Latin-letter spellings, which the speaker did not spell out); the speaker said this belongs to query interpretation, a Day 3 (serving) subject.

  3. Stage D3-C006 Day 3 · Making sense of users' queries

    Google's first step in understanding almost any query is to detect its language, which tells Google roughly what content the user wants: a query in German suggests German content, a query in English English content.

    extends
    Stage D2-C654 Day 2 · Calculating (some) signals

    In ranking, country and language signals help Google serve users the right content for their country and language.

  4. Stage D3-C007 Day 3 · Making sense of users' queries

    Query language detection works poorly when someone searches only for a brand name, such as Facebook or Google, because the query does not show which language the user wants results in.

    extends
    Stage D1-C215 Day 1 · How Search works and where's AI?

    Serving starts with interpreting the query, which includes cleaning it up, detecting its language and expanding it.

  5. Stage D3-C011 Day 3 · Making sense of users' queries

    Google named Thai as a language that makes query understanding more complex because it does not separate words with spaces; the speaker added, hedging with 'apparently', that Thai uses spaces to separate sentences.

    extends
    Stage D2-C320 Day 2 · Understanding what's on a page

    Text in languages written without spaces, such as Thai and Chinese, would end up in the index as long strings that might never be searched for, so Google segments it into words with statistical models built from other web content in that language.

  6. Stage D3-C013 Day 3 · Making sense of users' queries

    Google's query processing deliberately mirrors indexing: a query is transformed into something that can be matched against the index, and stop word removal is part of that transformation.

    extends
    Stage D2-C321 Day 2 · Understanding what's on a page

    For languages written without spaces, such as Thai and Chinese, Google uses exactly the same word segmentation when indexing a page as when interpreting the user's query, because otherwise the query could not be matched against the index.

  7. Stage D3-C013 Day 3 · Making sense of users' queries

    Google's query processing deliberately mirrors indexing: a query is transformed into something that can be matched against the index, and stop word removal is part of that transformation.

    extends
    Stage D2-C737 Day 2 · How does the index look like?

    A search query is broken into words with the same segmenter or tokenizer that Google used to build the index.

  8. Stage D3-C015 Day 3 · Making sense of users' queries

    Google said the difference between words and entities can be seen in Google Trends, where a term can be searched as words or as an entity (Trends calls these a search term and a topic).

    extends
    Stage D2-C761 Day 2 · Google Trends

    The Google Trends Explore page, which Google called the heart of Trends, shows search interest in a query or topic and how it changes over time.

  9. Stage D3-C048 Day 3 · Making sense of users' queries

    Google generally treats spellings with and without diacritics as synonyms behind the scenes, for example a German 'ü' written as 'ü', as 'ue' or left out.

    extends
    Stage D2-C600 Day 2 · Focusing on Internationalisation and Localisation

    Google usually understands a query word whether it is written with or without diacritics (accents).

  10. Stage D3-C059 Day 3 · Making sense of users' queries

    Google treats fan-out queries generated by the LLM the same way as queries typed by users, so understanding how normal queries work explains fan-out queries too.

    extends
    Stage D1-C172 Day 1 · Welcome and opening keynotes

    Google said the Gemini model lets Search understand the user's intent, and query fan-out then adds further queries to the first one to enrich the quality of the answer.

  11. Stage D3-C059 Day 3 · Making sense of users' queries

    Google treats fan-out queries generated by the LLM the same way as queries typed by users, so understanding how normal queries work explains fan-out queries too.

    extends
    Stage D2-C727 Day 2 · How does the index look like?

    Google said that when AI Overviews or AI Mode run a query fan-out, the generated queries are sent to Google's Search index and documents come back with their snippets, which then feed the AI-generated answer (part of this passage is unclear in the recording).

  12. Stage D3-C075 Day 3 · Making sense of users' queries

    At retrieval, Google splits the query into words, applies query understanding and expansion, and matches the words and their expansions against the posting lists.

    extends
    Stage D2-C736 Day 2 · How does the index look like?

    In posting-list retrieval, the posting lists of the query's words are intersected, which yields an unranked list of candidate URLs.

  13. Stage D3-C075 Day 3 · Making sense of users' queries

    At retrieval, Google splits the query into words, applies query understanding and expansion, and matches the words and their expansions against the posting lists.

    extends
    Stage D2-C738 Day 2 · How does the index look like?

    At retrieval, Google looks up the posting lists of the query words that are actually important rather than of every word in the query.

  14. Stage D3-C304 Day 3 · How Search results are born

    Which kinds of results Google shows for a query is decided by query understanding, which tries to predict the intent behind the query.

    extends
    Stage D3-C004 Day 3 · Making sense of users' queries

    Google placed query understanding in the traditional part of Search, the part where answers are looked up in an index and then presented and ranked.

  15. Stage D3-C311 Day 3 · How Search results are born

    Google handles an image used as a search query much like a text query interpreted as an embedding: the image is broken down into vectors (embeddings) that are then searched for in the index.

    extends
    Stage D2-C740 Day 2 · How does the index look like?

    Besides posting lists, Google can retrieve documents through vector embeddings: parts of documents are associated with embeddings, which form a vector space used for retrieval.

  16. Stage D3-C056 Day 3 · Making sense of users' queries

    Google's generative AI features in Search build on the traditional ways of searching, so query understanding also flows into AI Overviews and AI Mode.

    repeats
    Slide D1-C051 Day 1 · How Search works and where's AI?

    Three reasons were given: generative AI features are built directly on the core ranking systems, query fan-out expands the original query to find related information, and generative AI features highlight content indexed by Google Search.

  17. Stage D3-C311 Day 3 · How Search results are born

    Google handles an image used as a search query much like a text query interpreted as an embedding: the image is broken down into vectors (embeddings) that are then searched for in the index.

    repeats
    Stage D1-C224 Day 1 · How Search works and where's AI?

    For visual search, Google breaks an image down into vectors, sends the vectors to the index and returns results based on them.

  18. Slide D3-C321 Day 3 · How Search results are born

    Google's serving diagram shows the query passing through query understanding and retrieval to the index, then back through ranking and search features to the user, with the Search Features step highlighted (example query 'Where to eat orange').

    repeats
    Slide D3-C001 Day 3 · Welcome to serving and ranking day!

    Google's opening slide for serving day showed serving as the third stage after crawling and indexing, and drew Google's serving infrastructure as query understanding and retrieval leading into the index, then ranking and search features leading back to the user, for the example query 'Where to eat jamon'.

Built on these claims 3

Developer requirements 3

Sources 14