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: Real people — visitors we are sure about. Unsure — not clearly a bot, not clearly a person. B
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 5.6 and PHP 7.4.
SourceWordPress plugins · Nov 18, 2026
01 / Source details
Aboutthistool.
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:
Real people — visitors we are sure about.
Unsure — not clearly a bot, not clearly a person.
Bots — confirmed bots.
The six modes
Off — Nothing is checked and nothing is recorded.
Monitor (watch only) — Every visitor is checked and shown on the Live page, and everyone is let in. New installs start here: watch for a few days before you stop anyone.
Protect — Confirmed bots are stopped. Everyone else is let in without noticing anything.
Protect + browser check — Confirmed bots are stopped, and visitors we are unsure about get a short automatic browser check that real people pass in a few seconds.
Strict — Only visitors we are sure about are let in. Some real people on unusual browsers will be stopped too.
Emergency — Only verified Google, Bing, Apple and Meta crawlers get in; every other visitor is stopped, including other search engines, uptime monitors and ad-verification crawlers. Logged-in users are never stopped, so you cannot lock yourself out. Use during an attack, then switch back.
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.
Protection status — whether the site is connected, the current mode, when the last visitor was checked, and your plan usage.
The last 24 hours — visitors checked, let in and stopped, verified search crawlers, a chart by hour, why visitors were stopped, and the top countries.
Ready for Protect mode? — while you are in Monitor mode, the page tells you whether a blocking mode would have stopped real visitors or search crawlers yesterday.
This site’s own history — a live feed of the latest visitors, the addresses seen most as bots, visitor reports, daily totals, and a CSV export of the last 7 days.
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.
External services
This plugin connects to the PureGuard service (https://pureguard.io) to check visits:
What is sent: visitor IP address, user agent, requested URL/campaign parameters and browser-provided headers of the request being checked; your API key authenticates the calls. The Live page also asks the service for this site’s 24-hour summary, sending the site’s host name.
Browser verification (optional, off by default; the two “browser verification” switches under Paid campaign traffic): when on, the visitor’s own browser sends a short anonymous measurement straight to https://pureguard.io — screen size, graphics hardware name, processor count, time zone, language, whether the page became visible and whether there was real scrolling, touch or pointer movement. No cookies are set by it and no names, e-mail addresses or form contents are read. Turn it on only if your privacy notice covers it.
Browser check for cached pages (optional, off by default): when on, the reader’s browser sends one short request per visit straight to https://pureguard.io/page_verdict.php containing four things: the site’s host name, whether the browser shows signs of automation (and which signs), whether the page was visible, and whether the device has a touch screen; the service also sees the reader’s IP address and user agent, as any web request does. No cookie is set; the answer is kept in the browser’s session storage for ten minutes. On a site that uses the WP Consent API nothing is sent until the reader has allowed the “statistics” category. Turn it on only if your privacy notice covers it.
When: on protected page requests (bot check), when you press Test key, when an administrator opens the Live page, and when campaign features are turned on.
Why: the checks run on the PureGuard servers; the plugin only passes on the request details and applies the answer. If the service cannot be reached, visitors are let in.
Service terms: https://pureguard.io/terms — Privacy: https://pureguard.io/privacy
See it in action
Screenshots & previews.
Live page — protection status and the last 24 hoursLive page — this site's own history and live feedProtection mode selector (six modes)Design & Pages — branding and block-page customizationThe branded browser check pageThe branded block page with incident details
02 / Source details
Frequently asked questions.
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.
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati