HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
iorate
ublacklist
TypeScript2020–2026
iorate / ublacklist

ublacklist

Blocks specific sites from appearing in Google search results

42Distinct people
51Mentions
1Explicit recommenders
6.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Blocks specific sites from appearing in Google search results

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I wonder if we'll see a comeback of hand-curated directories of content? I feel like the "awesome list" trend is maybe the start of something there. I would be willing to pay…

charlesdaniels used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year51 dated mentions

Observed mentions: 2020-05-25 01:01:49 UTC to 2026-09-30 05:52:40 UTC.

0510152020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 17 mentions; 2 submissions, 15 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC927
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC17215
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC707
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC918
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC505

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
uBlacklist English | Deutsch | 한국어 | 简体中文 Blocks specific sites from appearing in Google search results Chrome: Chrome Web Store Firefox: Firefox Add-ons Edge: Edge Add-ons Safari: App Store (macOS and iOS, thanks to Group-Leafy) Description This extension prevents the sites you specify from appearing in Google search results. You can add rules on search result pages, or on sites to be blocked by clicking the toolbar icon. Rules can be specified either by match patterns (e.g. *://*.example.com/*) or by expressions including regular expressions, variables and string matchers (e.g. /example\.(net|org)/, path*="example"i, $category = "images" & title ^= "Example"…). You can synchronize rulesets across devices via cloud storage (Google Drive, Dropbox, OneDrive, WebDAV) or browser sync. You can also subscribe to public rulesets. Some public rulesets are listed on the website: https://ublacklist.github.io/rulesets Browser support policy uBlacklist supports the following browser versions: Chrome: Latest stable version only Firefox: Latest stable version and latest ESR only Edge: Latest stable version only Safari: Latest stable version only (macOS and iOS) Support for browsers outside the list above depends on community contributions. Please open a Discussion with a concrete implementation proposal — reports without one are unlikely to be addressed. Supported search engines This extension is available in the below search engines. Web Images Videos News Google ✔️ ✔️ ✔️ ✔️ Bing ✔️ ✔️ ✔️ ✔️ Brave ✔️ ✔️ ✔️ ✔️ DuckDuckGo ✔️ ✔️ ✔️ ✔️ Ecosia ✔️ ✔️ ✔️ ✔️ Kagi ✔️ ✔️ ✔️ ✔️ SearXNG ✔️ ✔️ ✔️ ✔️ Startpage ✔️ ✔️ ✔️ ✔️ Yahoo! JAPAN ✔️ ✔️ ✔️ Yandex ✔️ ✔️ No additional builtin search engine support is planned. You can use SERPINFO to add support for any search engine yourself. Related repositories ublacklist/builtin — Builtin SERPINFO files. The extension periodically downloads the latest SERPINFO from here. ublacklist/packages — npm packages (@ublacklist/match-pattern, @ublacklist/ruleset, @ublacklist/serpinfo) and the ruleset/SERPINFO format specifications ublacklist/store-assets — Store listing descriptions and screenshots ublacklist/ublacklist.github.io — Website and documentation (https://ublacklist.github.io) For subscription providers To publish a ruleset as a subscription, place a ruleset file encoded in UTF-8 on a suitable HTTP(S) server, and publish the URL. Here is an example hosted on GitHub: https://raw.githubusercontent.com/iorate/ublacklist-example-subscription/master/uBlacklist.txt You can prepend YAML frontmatter to your ruleset. It is recommended that you set the name variable. --- name: Your ruleset name --- *://*.example.com/* Authoring rulesets and SERPINFO with AI agents Agent skills for writing rulesets and SERPINFO are published in ublacklist/packages. You can install them into your AI coding agent with the GitHub CLI: gh skill install ublacklist/packages Contributing See our Contributing Guide for detailed development setup and guidelines. Author iorate (X) License uBlacklist is licensed under MIT License.
Read the full README on GitHub

What Hacker News says

9 sources
charlesdaniels·Dec 1, 2021Recommendation phrase
I wonder if we'll see a comeback of hand-curated directories of content? I feel like the "awesome list" trend is maybe the start of something there. I would be willing to pay an annual fee to have access to well-curated search results with all the clickbait, blogspam, etc. filtered out. Until then, I recommend uBlacklist[0], which allows you to hide sites by domain in the search results page for common search engines. 0 - https://github.com/iorate/uBlacklist
In Ask HN: What are these low quality “code snippet” sites?
uBlacklist fully supports blocking results from Google, Bing and DDG, and partially from Startpage and Ecosia [1]. It's been available for Firefox and Chromium derivatives for a while, and there seems to be a third-party Safari port as well [2][3]. There's a bunch of language-specific blocklists on GitHub focused on StackOverflow/GitHub mirrors and wonky machine translations, but I don't know of any mature curation effort yet. [1] https://github.com/iorate/uBlacklist#supported-search-engine... [2] https://github.com/HoneyLuka/uBlacklist/tree/safari-port/saf... [3] https://apps.apple.com/us/app/ublacklist-for-safari/id154791...
In Searx – Privacy-respecting metasearch engine

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.