Linux 软件免费装
Banner图

PureGuard – Bot & Ad-Fraud Protection

开发者 chanmyayaung
pureguard
更新时间 2026年11月18日 00:24
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

security firewall bot detection waf traffic quality

下载

6.0.14 6.0.22 6.3.6 5.0.7 6.0.0 6.0.9 6.3.5 6.5.0 6.0.1 6.2.0 6.4.0

详情介绍:

PureGuard checks every visitor to your WordPress site, lets real people in and stops bots. You pick one of six modes and the plugin sets everything else for you. Every visitor is put in one of three groups: The six modes Visitors on VPNs If your real audience uses VPNs or proxies to get around censorship, choose "My readers use VPNs to get around censorship". A visitor is then never stopped for their network alone. With the browser check they get the quick check instead (people pass it, bots cannot). Visitors with real bot evidence are still stopped. Your own look on the browser check and block pages Add your own logo, brand name, accent color, and dark or light theme. Change the block-page heading and message, show stopped visitors their IP and an incident ID, and let real people report a mistake with one click ("I am human"). Preview both pages from the settings before anything goes live. Live page These numbers cover visits that reach WordPress. Pages served from a page cache or CDN cache are not seen by the check. The history is kept in your own database (last 30 days). Browser check page in several languages The browser check page picks the visitor's browser language by itself. English, Thai, Bahasa Indonesia, Vietnamese, and Burmese (Myanmar) are built in, and every line can be edited in the settings. Visitor engagement (off by default) Optional: when you turn it on, the plugin measures anonymous time on page and scroll depth for real visitors. Off by default — no measurement script is added unless you turn it on. No personal data is collected.

屏幕截图:

  • Live page — this site's own history and live feed
  • Protection mode selector (six modes)
  • Design & Pages — branding and block-page customization
  • The branded browser check page
  • The branded block page with incident details

升级注意事项:

6.0.0 Big upgrade: five security modes (new Strict and Lockdown), censorship-friendly VPN filter, branded challenge/block pages with logo and previews, and the new PureGuard Live dashboard. Your existing settings are kept; review Settings → PureGuard after updating.

常见问题:

Will this stop my real visitors?

In Off and Monitor mode, never: nobody is stopped. In Protect mode, only confirmed bots. In Protect + browser check mode, visitors we are unsure about briefly see an automatic browser check. In Strict mode, unsure visitors are stopped too. In Emergency mode everyone is stopped except logged-in users and verified Google, Bing, Apple and Meta crawlers. Start in Monitor and use the "Ready for Protect mode?" card on the Live page before you switch.

My readers use VPNs. Will they be stopped?

Under Settings → Protection → Visitors on VPNs, choose "My readers use VPNs to get around censorship". Visitors marked only for their network are then never stopped; at most they see a quick automatic browser check that real people pass in seconds.

Do I need a PureGuard account?

Yes. Add your API key under Settings → PureGuard and press Test key. Get a key at https://pureguard.io/register.

Does it slow down my site?

A visitor's result is remembered (1 hour for visitors let in, 5 minutes for visitors stopped), so the service is asked at most once per visitor in that time. Logged-in users are skipped. In Monitor mode the page is sent first and the check runs afterwards where the server supports it. If the service cannot be reached, visitors are let in.

My site is cached. Does the plugin still see my readers?

Only some of them. The server check runs when WordPress builds a page. A reader who is served a stored copy from a page cache or a CDN never reaches it, and on a well-cached site that is most readers. To see those readers too, turn on "Check readers in their browser" under Settings → Protection → Readers on cached pages. The check then runs in each reader's own browser, also on cached pages, and the Live page shows the result. It stops nobody; it tells your pages whether the reader looks real. If you choose, it also passes the result to Google Ad Manager as a key-value, or holds AdSense ad requests for confirmed bots.

Where is the traffic data stored?

In a small table in your own WordPress database, cleaned up automatically after 30 days. You can turn this history off in Settings → General.

更新日志:

6.5.0 A check that also works on cached pages. 6.4.0 Security hardening and a clearer admin area. 6.3.6 6.3.5 6.3.4 6.3.3 6.3.2 6.3.1 6.3.0 6.2.9 6.2.8 6.2.7 6.2.6 6.2.5 6.2.4 6.2.3 6.2.2 6.2.1 6.1.0 6.0.23 6.0.22 6.0.21 6.0.20 6.0.19 6.0.17 6.0.16 6.0.15 6.0.14 6.0.13 6.0.12 6.0.11 6.0.10 6.0.9 6.0.8 6.0.7 6.0.6 6.0.5 6.0.4 6.0.3 6.0.2 6.0.1 6.0.0 5.0.7 5.0.4 5.0.3 5.0.2 5.0.1 5.0.0 4.0.1 4.0.0 3.0.0 2.0.0 1.0.0