Remove ads for subscribers

This is the step for website publishers whose site still shows ads, cookie banners, or a paywall. Serving subscribers a clean page is the website integration side of the deal, and this is how you hold it up: your server recognises a paying subscriber and serves them the clean page — while everyone else sees the site exactly as before.

If your site is already clean and unrestricted, there's nothing to switch off — you already give subscribers that clean page, and adding your Publisher ID is all it takes to earn.

The idea

Your site announces you with a Better-Web-Publisher response header or meta tag. On top of that:

  1. For a subscriber, the extension attaches a Better-Web-Token header to the request.
  2. Your server hands that token to the SDK, which verifies it locally — no call back to us — and tells you, simply, whether this is a genuine subscriber.
  3. For a verified subscriber, render without ads, non-essential third-party trackers, cookie consent screens, or marketing popups (including newsletter signup prompts). If you sell access, grant your base subscription or a custom level that unlocks paid content or functionality. Higher tiers can remain restricted. Otherwise, keep your normal page and access rules.

Freedom is the only membership. Both official SDKs recognize its plan byte (1); all subscriber benefits belong to that same membership. There are no separate ad-free and paywall-access plans to handle.

Verification gives you a simple yes-or-no answer: is this visitor a Zero Ad Network subscriber? The integration guides below show how to use that answer in your application or WordPress site.

Why it's safe and fast

  • Bound to your hostname. A token only verifies on the site it was issued for, so it can't be copied from your page and replayed on another.
  • No verification network call. The SDK checks the signature locally against the network's public key. Performance depends on the runtime and caching configuration.
  • Fails closed. Missing, malformed, wrong-host, or invalidly signed tokens do not grant access. Expiry checks include the SDK's clock tolerance. Your application must enforce the result and keep subscriber responses out of shared page caches.

Try it before you ship

Open your website's page in the dashboard and use Test in your browser. You do not need a paid subscription. Your account must own the registered hostname; an inactive website can be tested while you finish integration, but a removed or banned website must be restored first. Administrators and reviewers can also request test access for other hostnames.

Test access delivers the Freedom experience only on the selected hostname. Each token lasts seven days and renews automatically while you remain eligible, so you can continue testing without buying a subscription. A network outage can interrupt access after the token expires; the extension retries, or you can reopen the test page. An issued token remains valid until its expiry even if permission changes before renewal.

The extension saves test access separately from your paid subscription. Dashboard syncs and worker/browser restarts preserve it; switching accounts or resetting the extension clears it. Use Stop testing in the popup to restore your latest subscription state. Without a live paid subscription, normal subscriber access ends when testing stops.

Reload the website after starting or stopping. Turn Freedom off/on lets you compare both experiences. A website's own login, cookies, or cache may preserve access independently.

Test mode and demo access do not record payable visits or time, even if you also have a paid subscription. Previously recorded paid usage is retained and can still upload while your paid subscription remains active. Hostname ownership checks use the platform's current registration records; independent ownership verification remains a separate concern.

Get the SDK

  • Node, Bun & Deno — the official @zeroad.network/token package.
  • PHP — the zeroad.network/token Composer package for PHP applications.
  • WordPress — plugin setup, supported integrations, and page caching.

The token format is open, so other servers that can read HTTP headers and check an Ed25519 signature can implement verification too.