"Ad-free" is a claim some publishers make and walk back six months later when the metrics don't work. WeSearch's funding model is structured so we don't ever have to walk it back. We are not running display ads, native ads, sponsored content, programmatic auction, or affiliate links inside news pages. Period.
What's not on WeSearch
- Display ads. No banner ads, sidebar ads, or interstitials.
- Native ads. No "story" placements that turn out to be sponsored.
- Sponsored placements in the feed. The home feed is unsponsored, the trending row is unsponsored, the most-discussed row is unsponsored.
- Programmatic auction layer. No header bidder, no SSP, no DSP integration. The tracker stack required to participate isn't on the site.
- Affiliate links inside news pages. If we ever recommend a product on a non-news page, it'll be on a clearly separate page with disclosure.
- "Presented by X" placements. No story-level sponsorship.
- Newsletter ads. WeSearch doesn't run a separate newsletter; the daily editorial lives on-site.
How we survive without ads
WeSearch is community-funded by donations. The whole revenue stack is one Stripe checkout link. Operating costs are intentionally small (single droplet, no third-party SaaS, one human in the ops loop), and donations cover the cost.
Why ad-free
The structural problem with advertising as a news funding model is that it aligns the publisher's incentives with the advertiser's, not the reader's. The advertiser wants engagement metrics; the reader wants information. The two diverge fast. Read more on the engagement-vs-informedness trade.
The other structural problem is the tracker stack. Display advertising at scale requires a programmatic auction layer, which requires sharing reader signal with vendors. Even publishers who try to keep their tracker count small end up loading 15–40 third-party scripts on every page. We didn't want that bill landing on our readers, so we picked a funding model that doesn't require it.
What about an "ad-free version" of the site?
That is the site. Everyone gets it.
What's actually loading on a typical news site
For context: the typical major-publisher news article triggers somewhere between 80 and 250 network requests on first load. Most of those are not the article. They're a programmatic-ad SDK, a header bidder, multiple SSP (supply-side platform) calls, a half-dozen tracking pixels, an analytics suite, a tag manager, a consent-management SDK, a recommendation widget, a comment-platform script, and a video player that lazy-loads its own ad layer. Together they account for the majority of the page weight, the majority of the load time, and roughly 100% of the privacy concerns. The article itself is usually under 50 KB of HTML.
WeSearch loads the article, the typography, the chrome, and nothing else. A WeSearch page is typically under 60 KB on first load and under 5 KB on warm cache. The contrast is visible on the network panel of any browser.
What do we lose by going ad-free?
Money, mostly. Display ads at scale generate $5-30 per 1,000 page views depending on category and audience. WeSearch serves a meaningful number of monthly page views; on a hypothetical advertising stack, the revenue would be enough to cover hosting plus a salary. We've chosen not to take that revenue because the cost — to readers, to load time, to privacy, to editorial integrity — is higher than the benefit. The trade is consistent with how we think the open web should work for news.
What about non-news monetization?
Two structural exceptions. The Conduit API tier (paid) is a separate product for high-volume integrators; it doesn't put ads on the news pages, but it is a paid service. The donor wall at /donors recognizes individual donors who opt in. Neither involves advertising on news content.
Bottom line: who benefits from ad-free news?
- Readers on metered mobile data — pages load 5-10× faster.
- Readers on older devices — JavaScript-heavy ad layers are the main reason cheap phones struggle to load news pages.
- Readers in privacy-sensitive contexts — journalists working with sources, activists, anyone behind aggressive corporate firewalls.
- Readers who want news without distraction — display ads are designed to interrupt; their absence makes long-form reading easier.
- Anyone who's accidentally clicked an ad-blocker-bypass dialog one too many times.
Frequently asked
Are there really zero ads, even on the per-symbol pages or comment threads?
Yes. Every reader-facing page on wesearch.press is ad-free. Verifiable in the network panel.
Will WeSearch ever sell sponsorships, like NPR's "support comes from"?
Possible in principle, but the design constraint is no embedded ad SDK and no engagement-based pricing. If it ever happened, it would be a clearly labeled donor-recognition format with no tracking, on a separate page.
How do you measure if anyone's reading?
Server-side log lines and aggregate per-day counts. No client-side analytics. Resolution is "this page got N requests today" — not "this user did X then Y."
Could ad-free news fund itself at scale?
Open question. Wikipedia, NPR, and the Guardian have all shown that donation/contribution-based models can fund sizable news operations. WeSearch is small and the model fits at our size. Whether it scales depends on whether enough readers value ad-free news enough to fund it.