Elementor shipped version 4.4 on November 9, 2026, adding a new “Agent Ready” menu that scores how well a WordPress site can be found, read, and acted on by AI agents like ChatGPT, Claude, and Perplexity. It’s free on every site running Elementor and covers llms.txt generation, per-bot access rules, and a handful of read-only WebMCP tools. A follow-up release, 4.4.1, landed a week later on November 16 with security hardening and a batch of stability fixes for the same feature.
What Agent Ready Actually Checks
The feature lives under Elementor > Agent Ready in wp-admin. It runs a set of checks against the site and returns a score, and each failed check comes with a suggested fix you can apply and then rescan. That part is straightforward enough, and it’s also available as a public tool at Elementor’s free scanner if you want to check a site before touching the plugin at all.
Underneath the score sits an “Agent access” screen that generates llms.txt and llms-full.txt, Markdown versions of pages, and a few machine-readable files (agent.json, ai-catalog.json, openapi.json) that are meant to help an agent parse the site faster than crawling raw HTML. There’s also a virtual robots.txt layer where you can set rules per bot, with reading and training treated as separate toggles rather than one blanket allow or block.
On the interaction side, 4.4 bundles four read-only WebMCP tools (business information, site search, site structure, page content), and Atomic forms built in Elementor can now accept submissions through WebMCP as well, so a booking or contact form isn’t limited to a human clicking a button.
Worth Checking, Not Worth Trusting Blindly
None of this is enforcement. Elementor’s own documentation is upfront that the robots.txt rules and access preferences are signals a well-behaved bot is expected to honor, not a technical block on a bad one. A scraper that ignores robots.txt today will keep ignoring it after you flip these toggles. Where Agent Ready earns its keep is with the agents that actually read the rules, ChatGPT’s browsing, Claude’s connectors, and similar first-party integrations that are becoming a real source of referral traffic for some sites.
The 4.4.0 release also quietly extended MCP coverage to older widgets (Counter, Progress Bar, Social Icons, Image Gallery, Image Carousel) and let connected AI tools rename Structure panel elements, toggle experiments, and clear cache directly. That’s a wider surface than most site owners realize they’ve turned on. Then 4.4.1, a week later, tightened code security enforcement and fixed a few MCP-specific bugs, including one where a published page could get overwritten and another around image validation during manual setup. If a client site already has MCP or Agent Ready switched on in production, the overwrite bug is reason enough to update now rather than later.
What to Do on a Live Elementor Site
- Run the free scanner or open Elementor > Agent Ready in wp-admin to see where a site currently stands, and don’t assume the defaults are the settings you actually want.
- Decide the per-bot read and train rules deliberately. A site that depends on organic search still wants most crawlers reading; a site with licensed or paywalled content may want the training toggle off everywhere.
- Update to 4.4.1 before leaving MCP or Agent Ready features running unattended, given the publish-overwrite bug in the prior version.
This sits next to a question we’re already getting from clients outside the WordPress world, covered in our look at whether WooCommerce stores are ready for AI shopping agents, and the broader pattern of giving an agent a defined, read-only surface to work with instead of open access shows up again in how to design APIs that AI agents can actually use. For WordPress sites built on Elementor specifically, deciding what an AI agent should and shouldn’t be able to touch is becoming a normal part of the build, and it’s the kind of plugin-level configuration our Elementor Development team walks clients through alongside the rest of a site’s setup.

