Blocks specific sites from appearing in Google search results
6.6k
Stars
351
Forks
1
Open issues
30
Contributors
AI Analysis
uBlacklist is a browser extension that blocks specific websites from appearing in Google Search and other search engines (Bing, DuckDuckGo, Kagi, etc.). It serves users who want granular control over search result filtering through match patterns, regex expressions, or public rulesets, with cloud synchronization support. It is best suited for privacy-conscious users, researchers filtering low-quality content, and those managing multiple devices.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
uBlacklist: browser extension that lets users manually block unwanted sites from search results
uBlacklist is a browser extension (Chrome, Firefox, Edge, Safari) that lets users block specific domains or URL patterns from appearing in Google, Bing, DuckDuckGo, Brave, Kagi, and other search engine results. It targets power users frustrated by SEO spam, content farms, and low-quality results cluttering searches. Users can write match patterns or regular expressions, sync rules across devices via cloud storage, and subscribe to community-maintained block lists. It has been maintained continuously since 2018 and is available across all major browser stores.
Created in June 2018, likely as a response to the proliferation of SEO-spam and scraper sites in Google results. It has grown steadily over ~8 years from a single-engine tool to supporting 10 search engines with cloud sync.
Growth appears driven by recurring frustration cycles around SEO spam and AI-generated content flooding search results. Periodic viral moments on Reddit/HN (e.g., discussions about content farm dominance) likely generated spikes. The ~6,570 star count built over 8 years reflects slow, organic accumulation rather than sudden virality. Current star velocity (4 per 7 days) suggests the project has reached a stable, mature adoption plateau rather than active growth.
Available on Chrome Web Store, Firefox Add-ons, Edge Add-ons, and macOS/iOS App Store. Chrome Web Store listing exists at a known URL, implying a real install base. Exact install counts are not available from repository metadata alone, but multi-store presence and 8 years of active maintenance strongly suggest meaningful real-world usage. Community-maintained subscription lists published on the project website further indicate an active user ecosystem. Precise install numbers not verifiable from available data.
Appears to be a standard browser extension built in TypeScript. Likely uses content scripts to intercept and modify search result DOM, with background service workers handling sync logic. The SERPINFO system appears to be a pluggable, externally-updated configuration layer for supporting different search engine layouts without extension updates. Sync is handled via third-party cloud APIs (Google Drive, Dropbox, WebDAV) rather than a proprietary backend.
not documented in README
Last push was June 21, 2026 — four days before the evaluation date — indicating very active, ongoing maintenance. The project has been continuously developed for 8 years, spans multiple browser stores, has separate repositories for built-in rules and website, and has a contributing guide, all of which signal mature project hygiene. Browser support policy is explicit and realistic.
ADOPT IF: you are a power user regularly encountering SEO spam, AI-generated content farms, or low-quality results in Google, Bing, DuckDuckGo, or other supported search engines and want a lightweight, cross-browser, cross-device solution with rule-sharing capabilities. AVOID IF: you need automated, AI-based result quality filtering or prefer not to manually curate blocklists; also avoid if your browser or search engine is unsupported. MONITOR IF: you are building search quality tooling and watching whether community subscription lists (similar to ad filter lists) grow into a meaningful shared resource.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
6/10
- Search engine DOM changes can break content script selectors; Google in particular frequently alters result page markup, requiring timely updates from the maintainer or contributors.
- Manifest V3 restrictions in Chrome may limit or complicate content script injection patterns over time, potentially requiring architectural changes.
- The project is maintained primarily by a single author (iorate), creating a bus-factor risk despite 8 years of consistent activity.
- Safari support is a community port maintained separately, meaning iOS/macOS users may experience lagging updates or feature gaps.
- Rule maintenance burden falls entirely on the user or on volunteer subscription maintainers; there is no automated or AI-assisted detection of spam domains.
Likely to remain a stable, well-maintained niche tool for the foreseeable future. AI-generated content spam may increase its relevance and user base modestly, but it is unlikely to see explosive growth given its inherently manual nature.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://ublacklist.github.io
- Language
- TypeScript
- License
- MIT
- Last updated
- 23h ago
- Created
- 98mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Open pull requests
No open pull requests.
Top contributors
Similar repos
eallion/uBlacklist-subscription-compilation
A curated compilation of blocklists for the uBlacklist browser extension,...
uBlockOrigin/uBOL-home
uBO Lite is a privacy-focused content blocker extension built on the MV3 API,...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
iorate/ublacklist
this
|
6.6k | +6 | TypeScript | 8/10 | 23h ago |
|
eallion/uBlacklist-subscription-compilation
|
1.3k | — | Go | 7/10 | 4d ago |
 gorhill/uBlock
|
66.1k | — | JavaScript | 10/10 | 22h ago |
|
uBlockOrigin/uBOL-home
|
3.5k | — | JavaScript | 8/10 | 2d ago |
|
uBlockOrigin/uAssets
|
5.9k | — | Adblock Filter List | 8/10 | 9h ago |
uBlock Origin is a broad content blocker (ads, trackers, cosmetic filters) that can technically block domains from loading entirely, but does not offer targeted search-result-page filtering or the user experience of one-click blocking from a search results page. The two tools are complementary rather than competitive; many users run both.
Google's own Personal Blocklist extension performed a nearly identical function but was discontinued. uBlacklist filled this gap and extended it to multiple search engines, giving it a clear reason to exist post-discontinuation.
Kagi offers native domain blocking/ranking within its paid search product, eliminating need for a separate extension for Kagi users. However, uBlacklist also supports Kagi, making it useful for users who want consistent rules across multiple engines.
Manifest V3-compliant ad blocker with declarative filtering. Does not offer search-result-specific blocking UI or subscription rulesets oriented toward search spam. Different use case.
Self-hosting a meta-search engine allows full control over results at the engine level, but requires significant setup and maintenance. uBlacklist is far lower friction for individual users who want search filtering without infrastructure.