ConicPlex

Start Your Project

On this Page

Elementor 4.4 Adds Free Tools to Make WordPress Sites Readable by AI Agents

Aftab Memon

November 17, 2026

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.

Sources

Aftab Memon is a Senior WordPress Developer at ConicPlex, working across everything from plugin conflicts and theme customization to full site builds on Elementor and WooCommerce. He spends most of his time in the parts of WordPress that don’t show up in a features list: hosting quirks, hook priority, the difference between a plugin that works in isolation and one that survives a real production stack. He writes here about what actually holds up once a WordPress site is live and being run by a non-technical client, not just what works in a demo.

Leave a Reply

Your email address will not be published. Required fields are marked *

Keep reading

Plugins

Illustration of a calendar with one date circled, connected to a delivery package, representing a WooCommerce delivery date picker

How to Let Customers Choose Their Own Delivery Date in WooCommerce (4 Plugins Compared)

WooCommerce has no built-in delivery date picker. Here are 4 real plugins that let customers choose their own delivery date,…

Husen Memon

November 17, 2026

Guides

Flat illustration of a server block connected to a glowing circuit node representing an AI agent calling an API, with smaller connector shapes orbiting nearby

How to Design APIs That AI Agents Can Actually Use

Agent traffic already makes up a meaningful share of API calls at companies like Stripe. Here’s what actually needs to…

Sajil Memon

November 16, 2026

News & Updates

WooCommerce 11.3 Removes a Deprecated MCP Endpoint and Adds REST API Refund Validation

WooCommerce 11.3.0 removes the deprecated MCP endpoint, validates refund line items before processing, and changes how on_sale filtering works with…

Aftab Memon

November 16, 2026

WhatsApp
Husen Memon
Husen Memon
Typically replies instant