Elementor Agent Ready and Royal AI Firewall
Elementor's Agent Ready feature can add robots.txt rules that tell AI bots they are welcome. When Royal AI Firewall blocks one of those bots, robots.txt says one thing while the firewall does another. The firewall finds these cases and gives you three one-click ways to settle them. It never edits robots.txt itself.
The Elementor Agent Ready section appears in AI Firewall → Settings when Elementor is active and its Agent Ready settings have been saved at least once.
What Elementor's Bot access control adds to robots.txt
When the bot access controls are on in Elementor Agent Ready, WordPress's robots.txt gets a group for every bot on Elementor's list. Each group says Allow: / and carries a Content-Signal line built from that bot's search, AI input and AI training choices in Elementor, along these lines:
User-agent: GPTBot
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /These rules are only added to WordPress's own robots.txt. If a robots.txt file exists in your site's root folder, the server sends that file instead and Elementor's rules are not in effect.
What the Elementor Agent Ready section shows
Open AI Firewall → Settings and scroll to Elementor Agent Ready. The robots.txt bot rules row shows one of four states:
| Message | What it means |
|---|---|
| A robots.txt file on the server is served instead of WordPress's… | A physical file wins, so Elementor's rules are not in effect. Nothing to do. |
| Elementor's Bot access control is off… | Elementor adds no bot rules. Nothing to do. |
| Elementor's robots.txt bot rules and this firewall agree. | No bot on Elementor's list is blocked by the firewall. |
| Elementor tells these bots in robots.txt that they may crawl the site, but this firewall blocks them: | A list of contradictions, with three buttons below it. |
Each listed bot shows its name, its robots.txt name, and why the firewall blocks it: per-bot policy, default mode: block all AI bots, default mode: block training crawlers, or auto-blocked for ignoring Content Signals. Only blocked bots are listed. Bots you rate limit or paywall can still reach your pages, so they are not counted as a contradiction.
The three choices
Each button applies your choice through Elementor's own setting:
| Button | What changes |
|---|---|
| Remove these bots from Elementor's list | Only the listed bots are taken off Elementor's Bot access control list, so robots.txt no longer tells them Allow: /. Every other bot on the list keeps its rules. This is usually the right choice. |
| Turn off Elementor's Bot access control | Elementor stops adding bot rules to robots.txt. Its other Agent Ready features are not touched. |
| Keep both as they are | Nothing changes in Elementor. The section notes You chose to keep both as they are. Blocking is still enforced. |
Whichever you pick, the firewall keeps blocking the bot. The choice only decides what robots.txt says. You can review or change the list later in Elementor.
Signals in effect
In the Content Signals section of the same Settings page, the Signals in effect row shows which signals the firewall compares bot traffic against:
- Source. SEObolt Pro's Content Signals settings (used for every bot, when that feature is on), the robots.txt file on the server, or WordPress's robots.txt including lines other plugins add, such as Elementor's.
- All other bots. The signals from the
*group, shown assearch=…, ai-input=…, ai-train=…. - Bot groups with their own line. How many robots.txt groups carry their own Content-Signal line. Each bot is compared with the group that names it, otherwise the
*group. - If no source declares signals, it says None declared and bot traffic is logged without a Content Signals verdict.
Because Elementor's groups name individual bots, the signals you set per bot in Elementor are the ones the firewall uses for those bots. The firewall refreshes its copy of robots.txt when Elementor's Agent Ready settings or the WordPress Search engine visibility setting change.
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 Elementor versions
- The message shown in the Elementor Agent Ready section
- The contents of your robots.txt (open
/robots.txton your site) - Which button you clicked, if any