Anticipates and composes likely search queries from context (recent activity, current page, calendar, location) so users see relevant queries surfaced for them before they type, shifting search from reactive to proactive.
Patent Overview
- Filed
- 2022-01-31
- Granted
- 2023-08-03 (published application)
- Application Number
- US 17/588,729
The Challenge
The Challenge
Search has historically been reactive: the user types, the system responds. But many information needs are predictable from context. Anticipating those needs and composing the queries proactively reduces effort and surfaces relevant content sooner.
- Typing Is Friction — Every keystroke is a small cost. For predictable queries, eliminating the typing entirely is a substantial UX improvement.
- Context Predicts Information Need — What page the user is on, where they are, what is on their calendar, all hint at what they might want to know. Mining these signals predicts queries.
- Query Composition Must Stay Relevant — Bad anticipated queries waste screen space. Composition must hit a high accuracy bar or the feature feels intrusive.
- User Must Stay In Control — Proactive surfaces feel invasive if they assume too much. Users must be able to dismiss, edit, or disable the suggested queries.
- Privacy Constraints Are Real — Context signals include sensitive data. The composition pipeline must respect access controls, consent settings, and retention policies.
Innovation
How The System Works
The system gathers context signals (current activity, location, calendar, recent queries), composes candidate queries that fit those signals, scores them for likely usefulness, and surfaces the top candidates proactively in search-adjacent surfaces (Assistant, Discover, search-box pre-typing).
- Gather Context Signals — Available signals (with consent): current page, location, time, calendar events, recent queries, app activity. Signals form the input to composition.
- Generate Candidate Queries — From the signal set, generate candidate queries that fit each signal. A travel-related calendar event might generate 'flight status', 'weather at destination', 'hotel reviews'.
- Score Candidates — A scoring model rates each candidate on likely usefulness, considering signal strength, historical click-through patterns, and recency.
- Filter For Quality And Diversity — Top-scoring candidates are filtered: minimum quality threshold, diversity across signal types. The output is a small, useful set.
- Surface In Appropriate UI — Filtered candidates appear in Discover cards, Assistant suggestions, or search-box pre-typing prompts. Each surface has its own rendering pattern.
- Capture User Reaction — Click-through, dismiss, edit actions feed back into the scoring model. The system learns which composition patterns work for which users.
- Honor User Controls — Users can disable proactive composition entirely, restrict it by signal type, or clear underlying signal data. Controls are first-class.
Proactive Composition From Context
The patent's load-bearing idea is to flip search from reactive to proactive for predictable information needs. Context becomes the input; composed queries become the output; the user benefits from queries they did not have to think to type.
Anticipate, Don't Just Respond
When context predicts a likely query, surfacing it proactively saves the user the effort of formulating and typing. The pattern works only when the predictions are accurate; that is the engineering challenge.
- Context Aggregation — Many small signals (page, location, calendar, history) aggregate into a context model. Each signal alone is weak; together they are strong.
- Generative Composition — Candidate queries are composed, not just retrieved from a fixed set. Composition uses templates plus context substitution to produce natural-sounding queries.
- User-Controlled Surface — Proactive surfaces respect user controls. Disable, restrict, clear are all first-class.
Technical Foundation
Technical Foundation
The patent specifies the signal aggregator, the candidate generator, the scoring model, the diversity filter, and the rendering surfaces.
- Context Signal Aggregator — Per-user signal collector ingests available signals subject to consent and access. Aggregator output is a structured context vector.
- Candidate Generator — Template-based and neural composers produce candidate queries from the context vector. Templates ensure naturalness; neural composers add flexibility.
- Scoring Model — Learned model rates candidates on signal strength, historical click-through, and recency. Trained on labeled and weakly-labeled data from past compositions.
- Diversity Filter — Filters selected candidates to ensure diverse signal coverage. Prevents the surface from showing multiple variations of the same composition.
- Rendering Layer — Per-surface (Discover, Assistant, search box) rendering of candidates. Each surface has its own layout and interaction pattern.
- User Control Layer — Settings for disabling, restricting, and clearing. Settings respect access policies and retention bounds.
The Process
The Process
The pipeline runs as a continuous background process plus on-demand composition when the user opens a search-adjacent surface. The compute is moderate; latency is hidden behind UI loading patterns.
- Aggregate Context Signals — Available signals stream into the aggregator. Aggregator output updates continuously as signals change.
- Generate Candidates — Composer produces candidate queries from the current context. Multiple candidates per signal type.
- Score And Rank — Each candidate gets a score. Ranking orders them by predicted usefulness.
- Apply Diversity Filter — Top-ranked candidates are filtered for diversity. Output is a small set covering different signal types.
- Surface In UI — Filtered candidates render in the appropriate surface (Discover, Assistant, search box pre-typing).
- Capture Reaction — Click, dismiss, edit are logged. Logs feed back into scoring model training.
- Update Context — As signals change, the candidate set refreshes. The surface stays current with the user's evolving context.
Quality Control
Quality Control
Bad anticipated queries feel intrusive. The patent specifies safeguards.
- High Quality Threshold — Candidates below the quality threshold are suppressed. Better to surface nothing than to surface a wrong guess.
- Diversity Enforcement — Multiple variations on the same theme are filtered to one. The user sees diverse coverage rather than redundant suggestions.
- User-Visible Reason — Each suggested query can show why it was suggested (location, calendar, recent search). Transparency builds trust.
- Disable And Restrict Controls — Users can disable proactive composition entirely or restrict it to specific signal types. Controls are surfaced visibly, not buried.
- Privacy Boundary Enforcement — Sensitive signals are excluded by default. Health, finance, location at sensitive sites are subject to stricter rules.
Real-World Application
Query composition powers Google Discover cards, Assistant proactive suggestions, search-box pre-typing prompts, and the contextual surfacing in Chrome and Android.
- Context-driven Composition Source — Queries compose from current user context, not from a fixed candidate pool. Composition is dynamic and personalized.
- User-controlled Privacy Model — Disable, restrict, and clear controls are first-class. The user is in charge of which signals contribute and what surfaces.
- Diverse Surface Coverage — Composition feeds Discover, Assistant, and search-box surfaces with shared underlying primitives but per-surface rendering.
Why Discover Is A New Surface For SEO
Pages that align with the context patterns proactive composition responds to (timely topics, location-relevant content, calendar-adjacent material) surface in Discover. Discover is now a meaningful traffic source for many publishers, driven by the patent's composition primitives.
Why Contextual Relevance Compounds
Content that aligns with predictable user contexts (morning news, travel planning, evening entertainment) earns repeated proactive surfacing. The content does not need to win individual queries; it wins by being the content the system chooses to surface when context predicts the need.
<\/section>What This Means for SEO
What This Means for SEO
Query suggestion and composition systems shape which queries even get typed, so being inside the suggestion set captures traffic the user did not know they wanted.
- Autocomplete Is A SERP Before The SERP — Brands and topics that appear in autocomplete capture traffic at the point of intent formation. Aim for the entity to be one of the first suggestions for its category.
- Long-Tail Suggestions Reveal Composition Patterns — The compositions the system surfaces are the queries it thinks the user is most likely to compose. Each is a content gap worth filling.
- Brand-Plus-Modifier Slots Are Defendable — Once your brand owns the suggestion for "[brand] reviews" or "[brand] alternatives", competitors cannot easily displace you. Earn the slot with consistent content on those modifiers.