What it is

uBlacklist is a browser extension that blocks specific sites from appearing in search engine results. It is written in TypeScript, licensed under MIT, and lives in the WebExtensions ecosystem, with published builds for Chrome, Firefox, Edge, and Safari on macOS and iOS. The project has been maintained for roughly eight years and carries 6,636 stars and 347 forks on GitHub, with two open issues at the time of writing. Its homepage and documentation live at ublacklist.github.io.

The concrete problem it solves is unwanted results that keep resurfacing in search. Rather than relying on a search engine's own ranking signals, uBlacklist lets a user declare rules that remove matching sites from the result page. Rules can be added directly on a search result page, or on a site to be blocked by clicking the toolbar icon. Rules take the form of match patterns such as *://*.example.com/*, or expressions that include regular expressions, variables, and string matchers, for example /example\.(net|org)/, path*="example"i, or $category = "images" & title ^= "Example".

Key capabilities

• Blocks matching sites across Google, Bing, Brave, DuckDuckGo, Ecosia, Kagi, SearXNG, Startpage, Yahoo! JAPAN, and Yandex, with per-engine coverage for web, images, videos, and news results.
• Accepts rules as match patterns or as expressions using regular expressions, variables, and string matchers.
• Adds rules from the search result page itself or from the toolbar icon while browsing a site.
• Synchronizes rulesets across devices through Google Drive, Dropbox, OneDrive, WebDAV, or browser sync.
• Subscribes to public rulesets, with a curated list published on the project website.
• Extends to search engines outside the builtin set through SERPINFO, which lets a user add support for any engine.
• Ships supporting npm packages, @ublacklist/match-pattern, @ublacklist/ruleset, and @ublacklist/serpinfo, alongside the ruleset and SERPINFO format specifications.

Who uses it and how

• Everyday searchers who want to permanently suppress content farms, aggregators, or other domains from their results.
• Users who maintain a personal blocklist and sync it between a desktop browser and a phone through cloud storage or browser sync.
• Subscription providers who publish a UTF-8 encoded ruleset file on an HTTP(S) server and distribute the URL, as in the example hosted on GitHub.
• Users of search engines not covered by the builtin list, who write their own SERPINFO definitions to add support.
• Contributors extending browser support, which the project handles through Discussions and requires a concrete implementation proposal.

Getting started

Install from the Chrome Web Store, Firefox Add-ons, Edge Add-ons, or the App Store for the Safari build on macOS and iOS. Rules are then added from search result pages, from the toolbar icon, or by subscribing to a public ruleset.

When to use it — and when not to

uBlacklist is the right tool when the goal is a personal, portable blocklist that works across several engines and browsers without depending on any single search provider. A self

---
name: Your ruleset name
---
*://*.example.com/*

gh skill install ublacklist/packages