GuardPress and Royal AI Firewall together
GuardPress and Royal AI Firewall are built to run side by side, and there is nothing to set up. GuardPress protects the site from attacks; Royal AI Firewall decides what AI bots may do. Both work inside WordPress, at different moments of each request, and each keeps its own logs.
Install and activate both. Royal AI Firewall detects GuardPress and lists it under AI Firewall → Settings → Security plugin compatibility as a first-party Royal Plugins integration.
Which one runs first
GuardPress's firewall checks run as soon as plugins load. Royal AI Firewall decides at the start of request routing, a moment later. So for each request:
GuardPress checks the request
IP blocks, firewall rules and fake-crawler checks. If GuardPress blocks the request, it stops here.
Royal AI Firewall checks AI bots
If the user agent is a recognized AI bot, its policy applies: block, rate limit, paywall, or log only.
WordPress builds the page
Everything else goes through as normal.
A request GuardPress blocks never reaches Royal AI Firewall, so it does not appear on the AI Firewall dashboard. That is expected: the two layers do not conflict.
The bot access self-check passes GuardPress
Twice a day, Royal AI Firewall checks that search engines can still reach your site. It requests your home page from your own server twice, once as a browser and once with a Googlebot user agent, and compares the answers.
GuardPress blocks requests that claim to be a search crawler but fail its reverse DNS check, and your own server is not Google. To pass, the self-check signs each request with a short-lived signature made from a secret stored on your site. GuardPress 1.6.51 or later recognizes the signature and lets the self-check through; Royal AI Firewall also skips its own bot rules for it. Without the secret the signature cannot be made, and every other request that claims to be Googlebot is checked as usual.
The free GuardPress plugin has no fake-crawler check, so there is nothing for the self-check to pass.
Update both plugins first (Royal AI Firewall 1.0.12 or later, GuardPress 1.6.51 or later). If the alert stays, the block is coming from another layer, such as your host or CDN: see Bot Access shows alert or fail.
Search engines stay protected in both
Both plugins confirm Googlebot, Bingbot and Applebot with reverse DNS before trusting them. In Royal AI Firewall, verified search engines cannot be blocked unless you turn on Settings → General → Search engine override; a request that only claims to be Googlebot gets no special treatment.
Where each one logs
| Plugin | What it records | Where to look |
|---|---|---|
| Royal AI Firewall | AI bot requests it saw, with the policy decision; Royal MCP tool calls; verified search engine visits | AI Firewall → Dashboard, Activity Log and Bot Access |
| GuardPress | Requests its firewall blocked, login activity and other security events | GuardPress's own logs in its admin menu |
If an AI bot seems to be missing from the AI Firewall dashboard, check GuardPress's logs: GuardPress may have stopped it first.
Still stuck? Two support paths
Community support (free): wp.org plugin forum
Post a new thread at wordpress.org/support/plugin/royal-ai-firewall/. The Royal Plugins team monitors the forum regularly.
Premium support (paid)
For direct one-on-one help with a 24-hour SLA, see Premium Support ($149/year).
Information to include (either path)
- Your Royal AI Firewall and GuardPress versions
- What the Bot Access page shows, if you have an alert
- Whether a CDN or host firewall sits in front of the site
- Any matching entries in GuardPress's logs