# Bad Website Blocklist removes search results that are ads wearing a lab coat

> BadWebsiteBlocklist is a CC0 licensed uBlacklist subscription that filters AI generated articles, low effort spam sites and advertising disguised as information out of your search results, with a closed issue for every domain it blocks.

**popcar2/BadWebsiteBlocklist** — A filter that blocks spam & misleading websites from appearing in search results via uBlocklist

- Repository: https://github.com/popcar2/BadWebsiteBlocklist
- Stars: 748 · Forks: 19
- Language: Unknown
- License: CC0-1.0
- Published: 2026-10-21 · Updated: 2026-10-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/popcar2-badwebsiteblocklist

## A subscription that edits the search page, not the web

BadWebsiteBlocklist is a filter that blocks spam and misleading websites from appearing in search results, and the delivery mechanism is a browser extension rather than a network proxy or a DNS resolver. The project is a single text file, uBlacklist.txt, hosted in a repository that is otherwise almost empty, with a README, a LICENSE, a CONTRIBUTING.md and a .github directory for the issue templates. The licence is CC0-1.0, so the list is a public domain dedication that anyone can copy, remix or redistribute without conditions, and the repository metadata agrees on that. The last push was on 2026-10-10 and there are no GitHub releases, which is consistent with a project whose entire output is one continuously updated file. The user is anyone whose search results have been colonised. The stated targets are AI generated articles, low-effort spam sites, and thinly veiled advertisements acting as information, and the author is explicit that the motivation is not only the AI slop but also a stated hatred of bad tech support articles, the kind of page that exists to route a visitor to a support line rather than to answer anything.

## Every blocked domain comes with a written reason

The more interesting claim in the README is about organisation rather than coverage. The project says that another big goal is to try to be as organized as possible, and that every website that gets blocked has an issue explaining why it was added to the list for future reference, with the link pointing at the closed issues filtered by a query. That is a meaningful design choice for a blocklist, because most blocklists are opaque. A domain appears, the user is told it is blocked, and nobody can find out why, so a legitimate site that gets caught cannot appeal. Here the reason is written down, which means a maintainer can be argued with in the open and a future contributor can check whether the justification still holds. It also means the repository is a corpus of editorial decisions rather than a bare data dump, and reading a hundred of those issues is a reasonably efficient way to understand what the project considers a bad website. The contributing route is the same mechanism. If you want a site added, you create an issue, using the issue templates in the .github directory, and the contributing guide explains the details.

## Installing it means adding a subscription URL

The setup is a browser configuration rather than a build, and the documentation lists five steps. First, install the uBlacklist extension. Second, click the extension in the browser toolbar and then click on Options. Third, click on SERPINFO and enable the search engines you use. Fourth, scroll down to subscriptions and click Add a subscription. Fifth, give it a name and add the URL of the list:

```text
https://raw.githubusercontent.com/popcar2/BadWebsiteBlocklist/refs/heads/main/uBlacklist.txt
```

That is the whole installation. The subscription URL means the list is fetched and kept current by the extension, so there is no download to refresh by hand, and the documentation makes the same point in one line, that the websites in the list should no longer appear when searching and that the subscription means the blocklist will always stay up to date. The SERPINFO step is the part people get wrong. The extension needs that permission before it can read the search results page at all, so a subscription added without it will look installed and do nothing. A naming inconsistency in the project is worth noting while you are in the settings, since the repository description says the filter works via uBlocklist while the instructions are for the uBlacklist extension, and the repository topics list ublacklist.

## A shared list versus a private one

The realistic alternative is a blocklist you maintain yourself in the same extension, and the difference in approach is mostly about trust and upkeep. A shared subscription is curated by other people, arrives with reasons attached, updates itself, and inherits their judgement, including the cases where you would have made a different call. A local list is entirely under your control, contains exactly the domains you have been annoyed by, and never changes under you, but it is also a list of one, it does not benefit from a wider set of eyes spotting the same pattern in different sites, and it rots because the sites you blocked have changed or vanished. The middle path is the one this project points at. The AI blocklist it says it was inspired by, the huge AI blocklist, takes the same shape but with a different scope, and the inspiration is acknowledged directly in the README. The point for an adopter is that the list is a set of opinions about web quality, and the issues are where those opinions are visible, so you can disagree with a specific entry rather than with an opaque file.

## One text file, no releases, and a list that keeps moving

The operational picture is simple. The repository contains a handful of entries, the uBlacklist.txt file at the root being the product, and the raw URL that the extension subscribes to points into the main branch of that same repository. The consequence is that the list is updated by the same push that changes the issues and the documentation, with no tagging, no release notes and no version pinning, so there is no way to freeze the list at a known state, and no way for the extension to be pinned to a particular version of it. The topic list is telling about the intent as well, with ai-blocker, blacklist, blocklist, search-engine and ublacklist, which frames this as a search quality project rather than a privacy or tracking blocker. For a person who spends their working day in a search engine, the value of removing a layer of machine generated filler from the result page is immediate and easy to judge, and the cost of getting it wrong is low, because the blocked sites are still reachable by URL and the extension lets you unblock a domain on the spot when it turns out to matter.

## Conclusion

Adopt this subscription if your search results are full of machine written articles and thin advertorial pages and you would rather filter them at the browser than at the query level. Do not adopt it expecting a general web filter, because it targets search result pages, and do not treat the blocked set as a permanent truth, since the list changes as sites change shape. Before you subscribe, read a few of the closed issues to see the standard the project applies, and remember that uBlacklist needs the SERPINFO permission enabled before it can hide anything at all.

## FAQ

### How do I install the Bad Website Blocklist?

Install the uBlacklist extension, open its Options from the browser toolbar, click SERPINFO and enable the search engines you use, then scroll to subscriptions, click Add a subscription, name it and add the URL https://raw.githubusercontent.com/popcar2/BadWebsiteBlocklist/refs/heads/main/uBlacklist.txt. The subscription keeps the list up to date automatically.

### What kinds of sites does this blocklist remove?

The list targets AI generated articles, low effort spam sites, and thinly veiled advertisements acting as information. The README also frames the project as a reaction to bad tech support articles, the kind of page that exists to point a visitor at a support line rather than answer the question.

### How do I report a website that should be blocked?

Open an issue using the issue templates, and read the contributing guide for the details. The project asks for the same discipline in reverse, since every blocked website already has a closed issue explaining why it was added.

### What licence is the Bad Website Blocklist published under?

It is released under the CC0-1.0 public domain dedication, with the licence text in the LICENSE file at the root of the repository, so the list can be copied and redistributed without conditions.

## Sources

- [Issues](https://github.com/popcar2/BadWebsiteBlocklist/issues)
- [License: CC0-1.0](https://github.com/popcar2/BadWebsiteBlocklist/blob/main/LICENSE)
- [popcar2/BadWebsiteBlocklist on GitHub](https://github.com/popcar2/BadWebsiteBlocklist)
- [README](https://github.com/popcar2/BadWebsiteBlocklist/blob/main/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/popcar2-badwebsiteblocklist