Your earnings are capped before you start
AdSense, Mediavine and Ezoic only pay for ads that load. If 25-40% of your page views carry a blocker, your ceiling sits well below your traffic, on desktop and on phones.
WordPress blogs and magazines typically see 25-40% of page views with an ad blocker, and most of those page views earn nothing from AdSense, Mediavine or Ezoic. AntiAdBlock Core measures your own rate and asks readers with a blocker to allow ads on your site, on desktop and mobile. No code, no developer.
Typical range from our ad-blocking statistics. Your own rate shows in your dashboard from the first day.
AdSense, Mediavine and Ezoic only pay for ads that load. If 25-40% of your page views carry a blocker, your ceiling sits well below your traffic, on desktop and on phones.
A blocked page view usually never reaches your ad network, so your AdSense or network reports simply show fewer page views and impressions than your traffic. Google's own ad blocking rate counts only desktop page views with a blocker extension. Without your own rate on every device, it is hard to tell blocking from a seasonal dip.
Google documents its ad blocking recovery message as desktop-only, so readers on phones never see it. The Acceptable Ads recovery some networks offer skips uBlock Origin users and rarely carries animated or video ads.
WordPress sites typically land between 25% and 40%, and the range hides big gaps. Blocking follows the audience: a tech or gaming blog read on desktop by younger readers tends to block more, while a recipe or lifestyle blog with mostly mobile, mainstream readers tends to block less, because ad blocking is less common on phones.
AntiAdBlock Core shows it from the first day, on the free plan too: the share of your page views with a blocker for each site and your detections day by day, with network-level blocking such as Pi-hole or NextDNS counted in your rate and shown as its own count. On Max and Business you also see it by type of blocking, device, browser and country.
Add AntiAdBlock Core from WordPress.org, or paste one async tag in your theme header if you prefer.
Approve the connection in your AntiAdBlock Core account and the plugin verifies your domain. With first-party delivery, the default, detection starts once you add the DNS record it shows you and the record is active.
Visitors with a blocker are asked to allow ads on your site; everyone else never sees it.
Many WordPress publishers already have one of two options at hand: Google's ad blocking recovery message in AdSense or Ad Manager, or the Acceptable Ads recovery some networks switch on, such as Mediavine's. What each one reaches, according to Google's help, Mediavine's own pages and the Acceptable Ads program:
On WordPress the quickest route is the official WordPress anti-adblock plugin, free on WordPress.org: it connects your site to your AntiAdBlock Core account, verifies your domain and adds the detection for you, with no code to paste. With first-party delivery, the default, the script runs from a subdomain of your own for maximum detection, once you add the DNS record the plugin shows you and the record is active. If you prefer code, one async tag in your theme header does the same job.
A free anti-adblock plugin that ships its detection inside its own files stays as it was at its last release while blockers keep changing. The official plugin carries no detection code: it is a plugin connected to a maintained service, so the detection is kept current for you without waiting for a plugin update.
AntiAdBlock Core detects uBlock Origin and uBlock Origin Lite, AdBlock Plus, AdGuard, Brave Shields and Ghostery on desktop and mobile. The free plan covers 5,000 detections a month for one site with no payment method, and only page views with a blocker count toward it. Paid plans add sites and volume, your color from Pro and your logo and message from Max, at a flat price with no revenue share.
Other types of site, each with its own ad-block problem and its own fix.
The other blogging platform, with the same AdSense economics.
Review and deal sites built on WordPress.
Communities run on bbPress or BuddyPress.
Anti-adblock for news sitesAnti-adblock for gaming sitesAnti-adblock for video sitesAnti-adblock for ad networks and agencies
On WordPress sites and blogs, typically 25-40% of page views arrive with an ad blocker, according to our ad-blocking statistics. The share is higher with young or technical readers and on desktop, and lower on blogs read mostly on phones. The free plan shows your own rate from the first day.
Sites that earn mainly from display ads, because a blocked page view usually shows none of your AdSense, Mediavine or Ezoic ads, and sites with young, technical or desktop-heavy readers, such as tech, software or gaming blogs. Recipe and lifestyle blogs read mostly on phones tend to lose less.
Yes. AntiAdBlock Core never serves, reinserts or edits ads. Once a reader allows ads on your site, your AdSense, Mediavine, Ezoic or Google Ad Manager tags load normally. If you use Google's ad blocking recovery message or another ad-block message, turn it off so readers get one request, not two; to keep Google's reports, leave Google's tag on your pages with the message as a draft.
Google's Ad Manager help says its ad blocking recovery messages only appear in desktop browsers, not in mobile browsers or apps, so readers on phones never see them. The AntiAdBlock Core notice shows in desktop and mobile browsers alike (the plugin skips AMP pages), and our AdSense ad blocking recovery comparison has the details.
Either works. The anti-adblock plugin for WordPress is the easiest: you connect your site from its settings, approve the connection in your AntiAdBlock Core account, and the plugin verifies your domain and adds the detection with no code to paste; with first-party delivery, it also shows you the DNS record to add. If you prefer code, paste one async tag in your theme header; our WordPress setup guide shows where it goes.
No. The script loads asynchronously and never blocks rendering. The plugin keeps it out of the minification and delay of WP Rocket, LiteSpeed Cache, W3 Total Cache, Autoptimize, SiteGround Optimizer, Perfmatters and Flying Press, and purges the page cache of WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer and WP Engine when something changes. With any other cache, purge it by hand after a change, such as when the script goes live. Search engines do not run ad blockers, so they index your posts as before.
Yes. The free plan covers 5,000 detections a month for one site, with no payment method and no time limit. A detection is a page view where a blocker is found; page views without one never count.
Start free up to 5,000 detections a month. No payment method, no developer.