A per-user block list that filters personal results and, when many users block the same site, becomes a denoised crowd-sourced negative quality signal that influences ranking for everyone. The structural precursor to Chrome's Personal Blocklist, the Penguin era, and the disavow tool lineage.
Patent Overview
- Inventor
- Simon Tong, Sanjay Ghemawat, John Piscitello, Matt Cutts
- Assignee
- Google LLC
- Filed
- 2005-08-22
- Granted
- April 9, 2013
The Challenge
The Challenge
Search engines surface results that individual users find irrelevant, deceptive, or low quality. There is no clean way to let a user remove a result they hate, and no clean way to turn that dislike into a system-wide quality signal without inviting manipulation by competitors and coordinated abusers.
- No Per-User Suppression — Per user, there is no first-class way to hide a domain or URL from personal results once it has been deemed unhelpful.
- Dislike Signal Is Lost — Per visit, when a user clicks then bounces and never returns, the negative judgment leaves no durable record the ranker can learn from.
- Spam And Low Quality Persist — Per query, spammy or deceptive sites keep ranking because traditional link and text signals do not capture user disgust.
- Manipulation Risk Is Real — Per signal, any user-driven block input can be gamed by competitors mass-blocking rivals, so naive aggregation is unsafe.
- Personal Versus Global Tension — Per system, a block must serve the blocking user immediately and also contribute to global ranking without leaking private intent.
Innovation
How The System Works
Users mark documents or domains for removal from their own search results. The system stores per-user block lists for personal filtering and, separately, aggregates blocks across the population into a denoised negative quality signal that down-weights commonly-blocked sites for all other users.
- Expose A Block Control — Per result, the user is offered a control to remove that URL or its host from their future searches.
- Record Per-User Block List — Per user, blocked URLs and domains are persisted to a personal list keyed to the account.
- Filter Personal Results — Per query, the user's personal block list is consulted and matching results are removed before display.
- Aggregate Blocks Across Users — Per document, blocks from many independent users are summed into a global count and rate.
- Denoise The Aggregate — Per signal, suspicious patterns such as competitor-cluster blocking or coordinated bursts are filtered out before counting.
- Derive Negative Quality Score — Per document, the denoised aggregate becomes a negative quality input feeding the ranker for the broader population.
- Apply To Ranking For Others — Per query for any user, commonly-blocked documents are demoted even when the searching user has never blocked them.
Personal Block Becomes A Global Signal
The patent's load-bearing idea is that a single user action serves two purposes at once: it cleans that user's own results, and, after denoising and aggregation, it contributes to a crowd-sourced quality signal that down-ranks disliked documents for everyone.
Two Layers From One Action
Per block, the personal layer fires immediately for the blocking user. Per population, the aggregate layer accumulates a denoised dislike score that propagates into global ranking once enough independent users agree.
- Personal Filter — Per user, immediate suppression of disliked documents.
- Aggregate Quality Signal — Per document, population-wide blocks feed ranking.
- Denoising Layer — Per signal, coordinated and competitive blocks are excluded.
Technical Foundation
Technical Foundation
The patent specifies the block control surface, the per-user block store, the personal filter pass, the aggregate counter, the denoiser, and the ranking integration.
- Block Control Surface — Per result, a control records the user's intent to remove that URL or its host.
- Per-User Block Store — Per user, a persistent list of blocked URLs and domains scoped to the account.
- Personal Filter Pass — Per query, results are filtered through the user's block list before presentation.
- Aggregate Counter — Per document, independent blocks are counted across the user population.
- Denoiser — Per signal, coordinated bursts, brand competitors, and abuse patterns are excluded from the count.
- Ranking Integration — Per document, the denoised aggregate enters the ranker as a negative quality input.
The Process
The Process
A block flows from a single user action into both a personal filter and a population-wide ranking signal, with denoising sitting between the raw event and any global effect.
- User Marks Document — Per result, the user clicks the block control on a URL or its host.
- Persist To Personal List — Per user, the block is stored against the account immediately.
- Suppress In Future Queries — Per personal query, the filter pass removes blocked documents before ranking is shown.
- Stream Event To Aggregator — Per block, the event is forwarded to the population-level counting layer.
- Run Denoising Filters — Per event, suspected coordination, competitor blocks, and abuse patterns are stripped.
- Update Document Score — Per document, the surviving denoised blocks update the global negative quality score.
- Feed Ranking For All — Per future query, the ranker reads the document score and demotes commonly-blocked documents for everyone.
Quality Control
Quality Control
Letting users influence ranking invites manipulation. The patent specifies safeguards to keep the aggregate signal honest.
- Competitor-Cluster Filtering — Per signal, blocks that cluster around known brand competitors are excluded from aggregate counts.
- Coordination Detection — Per event burst, suspiciously synchronized blocking is treated as abuse and dropped.
- Independence Weighting — Per user, only independent organic blocks count toward the population score.
- Threshold Gating — Per document, the global signal applies only after enough independent users agree.
- Personal Versus Global Separation — Per layer, the personal filter fires immediately while the global signal waits for denoised confirmation.
Real-World Application
This patent is the structural blueprint for Google's Personal Blocklist Chrome extension launched in 2011. Block data from that extension fed early signals that informed the 2012 Penguin algorithm era. Matt Cutts as co-inventor ties the patent directly into Google's spam-policy lineage, and the same logical pattern survives in disavow-style and implicit-dislike signals today.
- 2 layers Personal Plus Global — One block serves the user and the population.
- Denoised Aggregate Quality Signal — Coordinated abuse and competitor noise are filtered out.
- 2005 to today Signal Lineage — Filed in 2005, deployed via Chrome in 2011, lives on as implicit dislike signals.
Why The Block Signal Outlived The Extension
Per surface, the Personal Blocklist extension was retired in 2018, but the underlying signal pattern survives. High SERP CTR followed by immediate pogo-stick and low return rate function as implicit block-equivalents, and the denoising and aggregation logic remains useful regardless of the input channel.
Why This Is The Crowd-Sourced Spam Lineage
Per generation, this patent sits upstream of Penguin-era penalties, of the disavow tool, and of modern implicit-dislike learning. It is the load-bearing prior art for the idea that user dissatisfaction at scale is a first-class ranking input rather than a UX afterthought.
<\/section>What This Means for SEO
What This Means for SEO
If many users actively remove a domain from their results, that signal degrades how the domain ranks for other users. Designing for user satisfaction at the visit level is not a soft branding concern, it is a direct defense against a crowd-sourced demotion signal that has been in the patent record since 2005.
- Aggregate Blocks Become A Ranking Penalty — When a population of users blocks a domain, the denoised aggregate feeds the ranker as a negative quality input that affects ranking for other users too. Earning user dislike at scale is not a cosmetic problem, it is a direct ranking drag visible to people who have never blocked the site themselves.
- Crowd-Sourced Spam Labeling Is Built In — Genuinely poor user experience aggregates into a penalty visible to all. The system treats consistent user rejection as evidence of low quality, which means the cheapest defense is to be a site that users do not want to remove from their results.
- The Chrome Personal Blocklist Was The Visible Tip — The 2011 Personal Blocklist Chrome extension was an explicit deployment of this patent's data-collection layer. Its 2018 retirement did not retire the underlying signal, because implicit equivalents such as high SERP CTR followed by immediate pogo-stick and low return rate carry the same information.
- Matt Cutts As Co-Inventor Anchors The Spam Lineage — Having Matt Cutts on the inventor list links this patent to Google's spam-policy work in the same era. The block-signal sits in the same family as manual-review and classifier-driven spam filters, which means treating it as a webspam-class concern rather than a UX detail.
- Visit-Level Satisfaction Is The Real Defense — Designing for satisfaction at the visit level, with no deceptive bait, clear value delivery, and low pogo-sticking, protects against the block-equivalent ranking signal. Users who get what they came for do not block, and the absence of blocks is itself a positive trust input.
- Snippet Honesty Reduces Wrong-Click Blocks — High-quality SERP listings with clear titles, accurate snippets, and content matching that promise reduce the wrong-click-then-block pattern that this system penalizes. The cheapest block to avoid is the one that was caused by misleading metadata in the first place.
- Foundational To The Crowd-Sourced Spam Lineage — The 2005 filing predates the 2011 Personal Blocklist extension, the 2012 Penguin update, and the 2016 disavow tool. This patent is the load-bearing ancestor of Google's crowd-sourced spam-signal stack, so strategies built around user satisfaction age better than strategies built around isolated ranking factors.