AntiAdBlockCore – AdBlock Recovery
| 开发者 | antiadblockcore |
|---|---|
| 更新时间 | 2026年11月13日 06:46 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Install and activate the plugin.
- In Settings > AntiAdBlock Core, click Click here to connect your AntiAdBlock Core account. Sign in or create your free account (no payment method needed), check the security code and approve.
- The plugin verifies your domain and the detection script goes live on every page once the CNAME record of your subdomain is active.
- Optional: turn on Maximum detection in Configuration, with one click and nothing to upload.
- Detects the ad blockers your visitors actually use: browser extensions such as uBlock Origin, AdBlock, AdBlock Plus and AdGuard, browsers with built-in blocking such as Brave, and network-level blockers.
- Built to avoid false positives: visitors without an ad blocker are left alone.
- Always up to date: detection is maintained on the service side, so it keeps up when ad blockers change, without plugin updates.
- First-party delivery: the script is served from a subdomain of your own site with a single CNAME record, so it stays first-party. The plugin walks you through the record step by step (on Cloudflare, keep the orange cloud on) and switches over by itself when it is active.
- Maximum detection: one click adds a second way in through your own domain. When a visitor cannot reach your subdomain, the script loads through a short list of addresses on your domain that change every day, answered by the plugin itself. Nothing to upload and no file to edit; turn it off at any time.
- A clear notice that explains why ads matter to your site. By default it works as an adblock wall: visitors allow ads on your site to keep reading, with step-by-step instructions for their ad blocker and a button that checks again right away.
- The built-in text is in English or Spanish, following the visitor's browser.
- Customize the message, colors, logo and look from your dashboard, depending on your plan, and preview it without installing an ad blocker.
- Show the message (recovery) or, on eligible plans, run in detection-only mode, and exclude any page or path, such as checkout or privacy pages.
- Ad blocker rate, detections and recoveries, per site.
- Pages, countries, browsers and ad blocker types in the dashboard (detailed analytics on the Max and Business plans).
- A monthly summary right on the plugin's settings page.
- Overview: site, account, delivery and status at a glance, with a Check button and a link to the step-by-step guide.
- Protection level: Standard or Maximum detection, with a check that confirms from outside that it works and plain-language help when something on your server needs a change.
- Your account inside WordPress: account name, plan, usage of the current cycle, a monthly chart and your latest notifications from AntiAdBlock Core.
- Protection switch: turn ad block protection on or off on this WordPress.
- Installation check: opens your home page and your latest posts and pages as an anonymous visitor and confirms the script is on each one, and off the pages you excluded.
- Logged-in users who can edit posts are skipped by default (contributors, authors, editors and administrators), so your team never sees the message and their visits stay out of the stats.
- Manual code option for headless front ends or builders that serve their own HTML.
- Any theme, including themes that do not call wp_head().
- Caching and optimization plugins: WP Rocket, LiteSpeed Cache, Autoptimize, SiteGround Optimizer, Perfmatters, Flying Press and W3 Total Cache. The script is excluded from their JavaScript optimization (minification, deferral or delay). When something changes, the plugin purges the page cache of WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer and WP Engine.
- Cloudflare, including Rocket Loader.
- AMP pages and feeds are skipped automatically.
- Multisite: each site connects on its own.
- When you connect: nothing is sent until you click the connect button. Then the plugin sends your site address and name, the WordPress, PHP and plugin versions, your admin language and whether the site is a multisite, a subfolder install or a non-production environment to https://antiadblockcore.com. It receives a token limited to this site, used to read the site's status, usage and plan and to verify your domain. No user accounts, emails or content of your site are ever sent.
- In the background: while connected, the plugin reads that status once an hour so the script address, the verification state and your quota stay current. It stops when you disconnect.
- On your pages: once the domain is verified, your pages load the detection script from a subdomain of your own domain that points to the service (you create that DNS record yourself; nothing is changed for you). Sites that connected before 1.2.0 with the older third-party delivery keep loading it from antiadblockcore.com until they switch.
- Maximum detection (only if you turn it on): the plugin receives a key for this site from the service and answers a short list of daily addresses on your domain. For a visitor who cannot reach your subdomain, it forwards that request (the script, and the same reports the script sends) to the service (https://antiadblockcore.com), signed with the key, together with the visitor's IP address and country (from Cloudflare when your site is behind it) and the same request headers a browser sends to the subdomain (user agent, language, accepted content types, origin, the page address without its query string, and the script's own signed report headers), so the service can protect itself and count the visit as it would through the subdomain. It does not pass on cookies and does not set any. The service can also send this WordPress signed requests to check that it works. Turning it off, disconnecting or uninstalling removes the key. For each page view the script reports whether an ad blocker was detected and which kind, the page path, the browser type and the country derived from the visitor's IP address. The IP address is used in transit to derive the country and to protect the service; it is not stored in the statistics and is deleted from the service's server access logs after 14 days. To count recoveries correctly, the script keeps a few small first-party entries on your own domain: in the browser's local or session storage and, when your site spans several subdomains, in a first-party cookie on your domain. They hold when an ad blocker was last seen and which kind, a few flags for the current visit (such as the page and whether the message was closed) and, for up to 24 hours, reports that could not be sent yet. They contain no identifier of the visitor, are not used for advertising, profiling or tracking across sites, and are ignored after 30 days; the cookie expires then. Describe them in your privacy or cookie policy and decide, under the rules that apply to you, whether your consent tool should cover them.
- Credit: the message shown to visitors who have an ad blocker carries a small "powered by AntiAdBlock Core" link. It appears only inside that message, only for visitors with an ad blocker, and higher plans can switch it off.
- Terms of service: https://antiadblockcore.com/terms
- Privacy policy: https://antiadblockcore.com/privacy
安装:
- Install the plugin from the Plugins screen (search for AntiAdBlockCore) or upload it to
/wp-content/plugins/antiadblockcore. - Activate it.
- Go to Settings > AntiAdBlock Core and click Click here to connect your AntiAdBlock Core account. AntiAdBlock Core opens in a new tab.
- Sign in or create your free account, check that the security code matches and click Connect.
- Back in WordPress, create the DNS record shown in the setup steps; the plugin verifies your domain and the script goes live once the record is active.
- Optional: in Configuration > Protection level, turn on Maximum detection.
example.com/blog), the settings page shows a one-time manual verification step. First-party delivery covers that case too: the DNS record verifies the domain without touching any file.屏幕截图:
常见问题:
Is it free?
Yes, there is a free plan for one site with 5,000 detections per month and no payment method required. A detection is a page view where an ad blocker is detected; page views without one never count. Paid plans add detections and sites; Max and Business also add full message customization and detailed analytics.
What is Maximum detection?
An optional second way in for the detection script, through your own domain. With it on, a visitor who cannot reach your subdomain still gets the script, through a few addresses on your domain that change every day and that the plugin answers. Turn it on in Configuration > Protection level: it takes up to a minute while the service checks from outside that it works. If your server serves .js addresses itself (some Nginx setups), the plugin shows the block to add. If a firewall or security plugin (Wordfence, ModSecurity, Cloudflare WAF) blocks the check, allow POST requests to your home page with ?aabc_max. A page cache or CDN set to cache everything regardless of headers must not cache those daily addresses; they answer with Cache-Control: no-store.
Do I need to paste any code?
No. The plugin adds the script to every page for you, whatever your theme. A Get code option is there only for setups that bypass WordPress, such as headless front ends.
Will it slow down my site?
The script loads asynchronously, so it never blocks your page from rendering, and it is excluded from the common caching and optimization plugins so they do not break it.
Why do I not see the message on my own site?
Logged-in users who can edit posts (contributors, authors, editors and administrators) are skipped by default. Log out or open your site in a private window with an ad blocker on. You can change this in the plugin settings.
What is first-party delivery, and do I have to use it?
It serves the script from a subdomain of your own site, which keeps it first-party for ad blockers. It takes one DNS record, shown with copy buttons and step-by-step status. It is how every new site works since 1.2.0; sites still on the older third-party delivery see a button to switch. If the record is not created in time, the reserved subdomain is released and the plugin offers to reserve it again.
I created the DNS record. What now?
Nothing else. Press Check to verify it right away, or leave it: the plugin checks every hour and switches over by itself. On Cloudflare, leave the orange cloud on (Proxied).
How do I know the script is on my pages?
Use Check pages in the Ad block protection section. It opens your home page and your latest posts and pages as an anonymous visitor and tells you, page by page, whether the script is there. If a page misses it, purge your page cache and check again.
Does it work with my caching plugin?
Yes. The script is excluded from the JavaScript optimization of WP Rocket, LiteSpeed Cache, Autoptimize, SiteGround Optimizer, Perfmatters, Flying Press and W3 Total Cache. When you connect or change settings, the plugin purges the page cache of WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer and WP Engine. With any other cache, such as Flying Press or a CDN, purge it yourself after changes.
What happens if my plan has no room for another site?
The approval page and the plugin both tell you that you have reached the site limit of your account, with a button to upgrade or manage your sites. The connection request stays valid for 30 minutes.
Can I pause it or exclude pages?
Yes. Turn off the Ad block protection switch to stop the script on this WordPress, or list the paths and page slugs to exclude in the settings. AMP pages and feeds are always skipped.
What data does the plugin send?
Only what is described under "Third-party service": your site address and name, software versions, admin language and basic install details when you connect, and afterwards the site status. The detection script does not read personal data from your pages; see "Third-party service" for what it reports and for the small entries it keeps in the visitor's browser, with no identifier and for 30 days at most.
Can I disconnect?
Yes. Disconnect in the plugin settings and the script stops right away. If you disconnect this WordPress from your AntiAdBlock Core dashboard instead, it stops at the plugin's next hourly check, or when its settings page is opened. Either way the site and its statistics stay in your account, and a tag pasted into your theme by hand has to be removed there.
更新日志:
- Maximum detection: if an ad blocker strips the tag's fallback before it can run, a separate check starts it once the page has loaded, so the notice still shows.
- Domains that cannot have a first-party subdomain can now be protected: turn on Maximum detection and the script loads through your own domain, served by this plugin, with no DNS record to create.
- On those sites the plugin explains what to do instead of asking you to contact support, and "Check pages" recognises the new tag.
- Maximum detection: when an ad blocker answers the script with an empty file instead of blocking it, the plugin now notices and loads it through the daily addresses on your domain, as it already did when the script was blocked.
- Third-party delivery ended on November 15, 2026. A site that still used it now says so clearly and connects its domain with one button, then follows the usual DNS steps.
- Clear message when the domain is already verified on another account.
- The two protection levels are now called Standard and Maximum detection, as in your AntiAdBlock Core dashboard.
- Maximum detection: the plugin now forwards to a fixed address of the service instead of your subdomain, so your own Cloudflare firewall or bot protection can no longer block it, and it keeps working if your subdomain is renewed. Nothing to do: it switches over by itself.
- Maximum detection: if every address on your domain fails for a visitor (for example, the service is down), that browser stops trying them for 10 minutes, so your server never gets extra load from it. The plugin also gives up sooner and waits longer before trying the service again.
- Maximum detection: the visitor's address is read correctly when Cloudflare and a local proxy are both in front of WordPress.
- Clearer messages when a firewall blocks the check, when Maximum detection was set up with a file from the dashboard, and when you go back to Standard with the tag pasted by hand.
- New look: the settings page now has the same design as your AntiAdBlock Core dashboard, in four tabs (Home, Configuration, Account and usage, Statistics), with the monthly chart, cycle usage and your latest notifications.
- New: Maximum detection. One click adds a second way in through your own domain, answered by the plugin, with nothing to upload. A check confirms from outside that it works.
- First-party delivery is now the only option for new connections; sites still on third-party delivery can switch with one button. The DNS step now tells Cloudflare users to keep the orange cloud on.
- The plugin bundles the Inter, Space Grotesk and JetBrains Mono fonts (SIL Open Font License) for its settings page.
- Settings page: the caching note now separates the plugins that keep the script out of their JavaScript optimization from the page caches the plugin purges for you. Purge any other cache, such as Flying Press or a CDN, yourself after changes.
- Removed a call to an Autoptimize function that no longer exists. The script is still excluded from Autoptimize's JavaScript optimization.
- Clearer wording on who is skipped by default: every logged-in user who can edit posts (contributors, authors, editors and administrators), as the plugin already did.
- Disconnecting this WordPress from your AntiAdBlock Core dashboard now stops the script and the verification tag on your pages at the plugin's next hourly check (or when its settings page is opened), until you reconnect, and purges the page caches it supports. A tag pasted into the theme by hand has to be removed there. Disconnecting a copy of the site, such as a staging site, or changing your password does not stop it.
- Clearer wording on the connect screen (no payment method needed), in the suggested privacy policy text and in this readme.
- The monthly summary on the settings page now shows Recoveries, the same figure as your AntiAdBlock Core dashboard.
- First-party setup: the DNS step appears once the service has sent the record to create.
- Readme wording updated.
- Fix: with first-party delivery, the exclusion entries the plugin adds to caching and optimization plugins now match your whole first-party subdomain. The first-party script address changed and the previous entry no longer matched it.
- First public release on WordPress.org.
- One-click connection: the button opens the approval page in a new tab, with numbered steps, a security code to check and a clear notice (with an upgrade link) when the plan has no room for another site.
- Settings page in sections: overview (site, account, delivery, status), first-party setup steps, protection switch, installation check, monthly summary, shortcuts and settings.
- First-party or third-party delivery, switchable from the plugin; guided DNS steps with a Check button.
- Installation check across the home page, latest posts and pages, and excluded pages.
- Script added to every page whatever the theme, including themes without wp_head().
- Cache and optimization plugin compatibility. Translation ready.
- A clear notice when the first-party subdomain reserved for the site expires, with a button to reserve it again.
- The readme and the suggested privacy policy text describe the small first-party entry the script keeps in the visitor's browser.