The agentic web is here
Your WordPress is being read by AI agents. Make sure it answers them.
Install Animam — your site ships agent.json, llms.txt, an MCP server, Schema.org, agent-detection headers, and a Cloudflare WAF rule for AI fetchers. Out of the box. Score it on isitagentready after install.
What does “agent-ready” actually mean
In 2026, more and more of your website traffic is not human. It’s AI agents — Claude-User, ChatGPT-User, Perplexity-User, GPTBot, ClaudeBot, Gemini agents — visiting, reading, summarizing, citing, and increasingly clicking on behalf of users. When a person asks Perplexity “what’s the best WordPress AI plugin,” Perplexity’s agent visits candidate sites, parses the content, picks who to cite. When ChatGPT shopping mode helps someone book a clinic appointment, an agent crawls the site to find slots.
“Agent-ready” means : when an agent visits your WordPress, it doesn’t bounce off a 403, doesn’t guess your services from random page HTML, doesn’t miss your structured data. It hits machine-readable discoverability files, parses your Schema.org, finds your MCP server endpoint advertised, identifies itself in the chat, and gets accurate answers grounded in your real content.
The shift matters because agent visits compound differently than human visits. A human visit is a one-off. An agent visit is followed by a citation in an AI answer that may be seen by 1000 humans over the next month. Or it’s a click-on-behalf-of-user that converts into a booking, an affiliate sale, an enterprise quote. The asymmetry is enormous and growing.
The six layers Animam ships by default
Each one of these is a Saturday-of-yak-shaving by yourself. They ship together when you install the Animam plugin.
01 · agent.json + llms.txt + mcp.json
Discoverability files at /.well-known/
When an agent visits, it checks /.well-known/agent.json first to know who you are, what you do, what tools you expose, what the chat endpoint is. Animam emits this from your published WP content automatically. Plus /llms.txt for the broader spec, /.well-known/mcp.json for the Model Context Protocol endpoint advertising. All refreshed on every save_post.
02 · MCP server (Model Context Protocol)
Your WordPress callable from Claude Desktop, Cursor, any MCP client
Animam ships an MCP server inside your WordPress at /wp-json/animam/v1/mcp. With public mode enabled, anonymous agents can call tools/list and tools/call to query your products, search posts, recommend services, submit your existing WPForms forms — without going through the visitor chat. Your WordPress becomes a programmatic surface, not just a website.
03 · Schema.org structured data
Article + Product + FAQPage + LocalBusiness + Organization JSON-LD
AI search engines (Perplexity, ChatGPT search, Claude.ai web) parse Schema.org as primary semantic signal. The Animam admin chat bulk-attaches the right schema per page type via wp_set_schema_jsonld, wp_set_faq_schema, and detects RankMath / Yoast meta to coexist cleanly. Your pages move from “summarized by AI” to “directly cited.”
04 · X-Agent-Model header detection
Agents identify themselves in the chat, you see them
When an agent calls your visitor chat (or your MCP server), it sets the X-Agent-Model header (or prefixes its first message with [AGENT:claude-3-5]). Animam logs the conversation as visitorType=agent in the database. You see in your wp-admin which agents visit, what they ask, what they click. Like Google Analytics, but for the agent side of the funnel.
05 · Cloudflare WAF rule for AI fetchers
Bot blocks skipped for legitimate AI agents
Default WAF rules block aggressive bots — including legitimate AI agents like Claude-User, ChatGPT-User, Perplexity-User, GPTBot, ClaudeBot. Animam ships a Cloudflare custom rule that whitelists 10+ verified AI fetcher user-agents so they reach your content. Without this, you’re invisible to AI search engines no matter how good your discoverability files are.
06 · Click tracking + revenue attribution
When agents click on behalf of users, attribution flows
When the chatbot recommends a product (or service, or affiliate link) to an agent, the click goes through /r/:slug/:productId with full attribution. Agent visits + clicks + revenue land in your dashboard. As agents become buyers (Perplexity Comet, ChatGPT shopping mode, Claude with payment mandates), this is how you measure the new channel — and prove the ROI to your boss / accountant.
Why it matters in 2026 (and why the gap closes fast)
Three things are converging :
- AI Overviews swallow top-of-funnel. Google’s 2025 rollout cut commercial-niche traffic by 15-30% across the SEO industry. The clicks that remain go to sites whose content is structured enough to be cited inside the AI answer.
- Agents click on behalf of users. Perplexity Comet, ChatGPT shopping mode, Claude with payment mandates — all 2026 reality. They navigate, parse, click, increasingly transact. Sites that aren’t agent-readable are invisible to this new channel.
- The cost of falling behind compounds. An agent-readable site cited 100 times in AI answers gets soft authority that flows back to its human-side rankings. A site not cited gets weaker by month. The flywheel runs both ways.
The honest version : agent-ready isn’t a feature, it’s a baseline. Like HTTPS in 2017 or mobile-responsive in 2014. The smart sites do it now while it’s a differentiator. The rest do it in 2027 when it’s mandatory.
Score your site after install
isitagentready.com scans any URL and grades it Level 1-4 on agent-readiness. Animam.ai itself sits at Level 2 (“Bot-Aware”) — and we’re actively pushing toward Level 4 (“Agent-First”).
- Level 1 (Static) — your site has HTML and content. That’s it. Most WP sites still here.
- Level 2 (Bot-Aware) — robots.txt is sane, sitemap is present, basic Schema.org. Where Animam install lands you on day one.
- Level 3 (Agent-Friendly) — agent.json + llms.txt + Schema.org coverage on key pages + WAF that doesn’t block AI fetchers. Where Animam admin chat takes you in week one.
- Level 4 (Agent-First) — public MCP server, A2A purchase flows (AP2/x402), conversational APIs, agent-specific telemetry. The endpoint we’re collectively building.
Run the scan on your site before installing Animam, then again a week after. Watch the score climb. Honest feedback to your team that the work is paying off.
What ships now vs what’s on the roadmap
We’re not going to pretend the whole agent-to-agent vision is shipped. Here’s what works today and what’s in flight.
| Capability | Status | Notes |
|---|---|---|
| agent.json discoverability | ✅ Live | Auto-generated from your WP content, refreshed on save_post |
| llms.txt + llms-full.txt | ✅ Live | Same generator, packaged for the broader spec |
| /.well-known/mcp.json advertising | ✅ Live | Points to your plugin’s MCP endpoint with auth model |
| MCP server in plugin (authenticated) | ✅ Live | Bearer-secured, OAuth 2.1 + PKCE on apex |
| MCP public mode (no bearer for read-only) | ⏳ Planned Q2 2026 | Currently 401 for anonymous agents — fix in flight to allow tools/list + read-only calls without auth |
| X-Agent-Model + [AGENT:] detection | ✅ Live | Logs visitorType=agent in the conversation table |
| Cloudflare WAF rule for AI fetchers | ✅ Live | 10+ verified UAs whitelisted (Claude-User, ChatGPT-User, Perplexity-User, GPTBot, etc.) |
| Schema.org bulk attach (Article, Product, FAQ, etc.) | ✅ Live | Via wp_set_schema_jsonld, wp_set_faq_schema, wp_audit_schema |
| Click tracking + revenue attribution | ✅ Live | Product Catalog + RECOMMEND_PRODUCT tool + /r/:slug/:productId redirect |
| Agent traffic dashboard in wp-admin | ⏳ Planned Q2 2026 | Aggregated view : which agents visited, what they asked, what they clicked |
| isitagentready score on plugin Settings page | ⏳ Planned Q2 2026 | Auto-scan after install + recommendations to improve |
| A2A purchase via mandate (AP2 / x402) | ⏳ Planned H2 2026 | When an agent is authorized to buy on behalf of a user, the chat handles the full flow with Stripe |
| WhatsApp / SIP voice for agent escalation | ⏳ Roadmap | Vapi telephony works at apex; plugin-level self-serve in design |
FAQ
Is "agent-ready" a real thing or marketing fluff?
Real. Anthropic, OpenAI, Perplexity, Google all ship agent-style fetchers (Claude-User, ChatGPT-User, Perplexity-User, GPTBot) that visit websites and use the content for AI answers. The Model Context Protocol (MCP) is an Anthropic-published spec for agent-to-tool integration. Schema.org is W3C / Google. AP2 is Stripe’s payment-on-behalf-of standard. None of this is hypothetical — it’s shipping now.
Will I pay extra for "agent-ready" features?
No. The discoverability layer (agent.json, llms.txt, mcp.json), the X-Agent-Model detection, the Schema.org tools, the Cloudflare WAF guidance — all included on the standard Visitors plan (€19/mo) and above. The only thing reserved for higher tiers is the volume of agent conversations and the agent-specific dashboards (planned for Bundle €39/mo).
Does this matter for a small local business?
Yes, and arguably more. AI search engines (Perplexity, ChatGPT, Claude) are increasingly the way locals discover service businesses. A dentist with LocalBusiness schema + FAQ schema + agent-detection gets cited in AI answers ; a dentist without disappears from that channel entirely. The cost of being non-agent-ready is asymmetric for SMBs because their channels are limited.
Will the WAF rule break my regular visitors?
No. The Cloudflare custom rule is allowlist-only : it skips bot-blocking actions for known-good AI fetcher user-agents (Claude-User, ChatGPT-User, etc.), it doesn’t change any other behavior. Regular visitors and other bots are handled by your existing rules.
What about competing AI agents — does Animam play favorites?
No. The agent-detection layer recognizes any agent that identifies itself via X-Agent-Model or [AGENT:] prefix — Claude, ChatGPT, Perplexity, Gemini, Mistral, custom agents. Same with the WAF rule, the discoverability files, the MCP server. We’re neutral infrastructure ; the agent ecosystem is multi-vendor and we treat it that way.
How is this different from just adding a chatbot?
A chatbot answers humans on your site. Agent-ready means the entire site, including the API surface, is callable by autonomous agents that don’t go through your chat widget. They hit your MCP server directly, parse your structured data, follow your discoverability files. The chatbot is one of several surfaces. Agent-ready is the underlying posture.
Open source / standards aligned?
MCP is an Anthropic open spec ; Animam’s implementation is conformant. agent.json follows community-discussed schemas. AP2 is Stripe’s spec. Schema.org is W3C. The Animam WP plugin code is on GitHub, fully readable. The apex backend is closed-source SaaS.
EU hosting + GDPR?
OVH France for both apex (api.animam.ai) and the WP plugin’s outbound calls. Signed DPA with sub-DPAs (Anthropic, OpenAI). GDPR-compliant out of the box.
Be agent-ready before your competitors are.
14-day free trial. No credit card. Five-minute install. EU-hosted.