Agents are the new shoppers
ChatGPT, Claude, Gemini, Perplexity and Copilot now discover, compare and recommend products on behalf of their users — before a human ever opens your site.
Loading…Loading…Loading…Odoo module · website_agent_ready
“AI agents are already shopping. Can they read your store?”
Make your Odoo webshop legible, verifiable and measurable for AI shopping agents — the new SEO. No API keys, no external SaaS, no risk to your storefront — and a readiness score that proves the work.
Why now
ChatGPT, Claude, Gemini, Perplexity and Copilot now discover, compare and recommend products on behalf of their users — before a human ever opens your site.
No llms.txt, incomplete structured data, no bot policy, no way to verify agent traffic — and zero visibility into any of it. A default webshop is a closed book.
Complete JSON-LD also powers Google rich results — so merchants get human-SEO value on day one, even before agent traffic grows.
What's in the box
Everything Phase 1 promises — legibility, verification and measurement — installed in one shot and scored on one dashboard.
A 100-point checklist dashboard that scores how legible your store is to AI agents — with a fix-it link on every missing item. A fresh store is built to reach 85+ within about ten minutes of install.
A concise, AI-readable storefront summary — categories, featured products, policies, support and core links — computed from live store data, cached and invalidated automatically. Optional /llms-full.txt lists every published product.
Product and ProductGroup markup with per-variant Offers, shipping details and return policies, plus ItemList on categories and Organization/WebSite site-wide. Prices respect pricelists, currencies and tax display.
One plain-language form for shipping regions, handling and delivery windows, returns and support contacts. Filled once, it powers both llms.txt and JSON-LD — and is never fabricated when left empty.
An editable registry of known AI crawlers and agents — GPTBot, ClaudeBot, PerplexityBot and 12 more — with per-bot allow/deny policy appended straight into your robots.txt.
Requests carrying HTTP Message Signatures are cryptographically verified against the agent's published keys and labelled verified — log-first, never blocking, always fail-open.
See which agents visit, what they read and how that trends — bots only, no cookies, hashed IPs, configurable retention. Your first agent-visit rows usually appear the day you install.
The scoring
Not a vanity metric — a weighted checklist of exactly what AI agents need from a store, each item with a fix-it link in the dashboard.
The design bar
A fresh Odoo store should reach 85+ within about ten minutes of installing — one form, one review of the bot registry, done.
JSON-LD valid on sampled products
Internal validator runs against random published products.
Policy Facts complete
Shipping, delivery, returns and support facts all present.
llms.txt live
The AI-readable summary serves correctly on your domain.
AI bots configured
Registry reviewed with an explicit allow/deny posture.
Sitemap reachable & includes products
Sanity checks on the sitemap agents will crawl.
Organization / WebSite markup
Site-level identity markup present on public pages.
First agent visit recorded
Proof the pipeline works: a real agent read your store.
total= 100
Screens
Readiness Score
Setup
No developer, no config files, no keys. If you can fill one form, you can be scored by lunch.
One click on apps.odoo.com. Depends only on website_sale — no extra Python packages, no API keys, no LLM subscription.
Five minutes in one plain form: where you ship, handling days, delivery windows, return policy, support contacts.
Open the AI Bot Registry, keep or adjust the sensible defaults, and your robots.txt updates itself.
The Readiness Score dashboard shows every remaining point with a fix link — then agent visits start appearing in analytics.
Privacy & safety
Everything runs inside the merchant's own Odoo server. GDPR-lean by default — because EU merchants are exactly who this is for.
Datasheet
The details a sysadmin — or an AI agent — wants before recommending a module.
| Technical name | website_agent_ready |
|---|---|
| Odoo versions | 17.0 · 18.0 · 19.0 |
| Dependencies | website_sale — soft-detects stock, review & brand modules |
| Extra Python packages | None — standard Odoo stack |
| License | OPL-1 (Odoo Proprietary License) |
| Price | $85 per Odoo version, one-time |
| Distribution | Odoo Apps Store, git-synced releases |
| Public routes | /llms.txt · /llms-full.txt · robots.txt policy blocks |
| Backend menu | Website → Configuration → Agent-Ready |
| Outbound calls | Agent key discovery (JWKS) only — 2s timeout, fail-open |
| Analytics data | Bot visits only · hashed IPs · 90-day default retention |
Roadmap
Buy Phase 1 today; the next phases arrive as updates to the same module — no repurchase, no migration.
Phase 1
shippedllms.txt, complete JSON-LD, Policy Facts, bot registry + robots.txt, Web Bot Auth verification, agent analytics and the Readiness Score. Available now for Odoo 17–19.
Phase 2
in developmentA UCP-compatible product feed and a storefront MCP endpoint so agents can query your catalogue directly — shipping as an update to this same module.
Phase 3
researchMandate-based agent checkout (AP2-style): let a verified agent complete a purchase within rules the merchant sets.
FAQ
The things merchants and partner agencies ask before installing.
Something else on your mind? Ask the lab directly.
No. Agent-Ready is fail-open by design: every feature degrades silently rather than interrupting a shopper. Bot matching is a single compiled-regex pass with a performance budget under one millisecond on normal traffic, and the one outbound call it can make is timeout-guarded.
No. The module has no LLM runtime — it makes your store readable to other people's AI agents. Zero keys, zero per-request costs.
Nothing, except an optional cryptographic key lookup when a signed agent announces itself (cached, 2-second timeout, fail-open). There is no external dashboard, no third-party analytics, and no cookies.
Fifteen seeded, editable registry entries at launch — including GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Google-Extended, GoogleOther, Meta-ExternalAgent, Amazonbot, Applebot-Extended, Bytespider and CCBot. The list ships as editable data, so it keeps pace as the ecosystem churns.
Yes. Every feature is website-scoped: per-website llms.txt, policies, bot posture, analytics and score. Multi-company setups are supported.
Yes. The same complete JSON-LD that agents need also powers Google rich results (prices, availability, shipping and returns in search) — so there is day-one value even before agent traffic grows.
llms.txt and JSON-LD go live at install. The module is built so a fresh store reaches a Readiness Score of 85+ within about ten minutes — install, fill one policy form, review bots. First agent-visit rows typically appear the same day.
OPL-1, $85 one-time per Odoo version, sold through the Odoo Apps Store. Per store rules each Odoo series (17 / 18 / 19) is purchased separately, and updates within your series arrive as normal module updates — Phase 2 lands as one of them.
Get Agent-Ready
One-time purchase, sold and fulfilled via the Odoo Apps Store. Each Odoo series (17 / 18 / 19) is a separate store purchase — that is how the Apps Store works for every vendor.