Botmetria shows what AI assistants can see in your store, fixes what they can't read, and counts the money the AI channel brings — so the first AI orders land with you, not next door.
No sign-up · Score on screen in 60 seconds · We audited 63 MD/RO stores — the rating is public
In three weeks bots, AI crawlers among them, made 1,005,146 requests to the 3 stores on our panel. Ordinary analytics never shows this traffic: crawlers do not run JavaScript.
| Metric | This week | Change |
|---|---|---|
| Human visits from AI sources | 47 | ▲ +34% |
| Fake bots (failed verification) | 182 | ▲ +9% |
| Revenue from AI sources | 486 EUR | ▲ +32% |
Four tools a store usually already runs — and the blind spot in each of them. Each covers just one piece; Botmetria brings the whole AI channel together in one place.
We replace none of them: GA4 stays your web analytics, Cloudflare your perimeter defence, GEO tools watch assistant answers from the outside. Botmetria covers what none of them has: the server side of AI traffic, catalogue readability, and the path from visit to order.
One plugin, one dashboard: sell to agents and count the money from AI — without stitching together separate tools.
The WooCommerce plugin or a storefront from your product feed — about 15 minutes; a Composer or npm SDK — about an hour. Detection adds under 5 ms per request.
The agent finds your catalogue at a standard address, reads prices and availability, builds a cart and brings the shopper into your checkout — the payment stays with you. Bot visits are checked against the vendor's official IP ranges or reverse DNS wherever the vendor publishes them.
A dashboard and a weekly report: AI traffic and, with the WooCommerce plugin, orders and revenue from AI sources. The plugin's bot control decides which bots reach your server.
MD/RO online stores audited against 25+ checks
median AI-readiness score
of them are invisible to AI assistants (score ≤ 40)
The score is not points for the sake of points. At one panel store, out of 606,017 requests from a single AI vendor, 8 reached product pages. At the machine-readable store on the same panel — 73,715 product pages read. The difference is not in points; it is whether your product makes it into the assistant's answer.
JSON-LD Product: the product page has no machine-readable name, price and currency. So to an agent you have no price — and your product may never make it into the assistant's answer. This is not an edge case: most of the market we audited is broken this way.
Product markup, markdown versions of your pages and llms.txt switch on in one click, in 15 minutes. We do not sell a separate service for it.
Send us your store address — we will look at your case and reply by email with what exactly to fix and how. No forms, no calls, no decks.
The score is recalculated weekly and the delta lands in your inbox. A new theme, a plugin update or one robots.txt edit can shut assistants out of your catalogue again — without a recheck you find out months later.
With the WooCommerce plugin we validate your product feed and show catalogue gaps in the weekly report: items with no price, no image or no GTIN/SKU. Items without a price are exactly the ones that may never reach an assistant's answer — the agent has no price to quote.
New bots and new agent storefronts keep appearing. The weekly report shows which AI bots visited you and how your readiness score moved, so a change on the market reaches you as a number, not a rumour.
A one-off check you can do by hand. Monitoring you can't.
A live test against a real store: the agent reads the UCP manifest, opens the catalog, picks a product, builds a cart and reaches checkout. No order is placed — payment always stays with the store.
No store with the Botmetria plugin yet? Leave the field empty — we'll run it on our demo store.
WooCommerce and a feed storefront — 15 minutes · SDKs — about an hour · 4 ways · not just WordPress
A plugin from your dashboard: UCP checkout, analytics, markdown and llms.txt — one click.
Open-source SDK, ~50 lines of adapter around your products and cart.
One order from the AI channel a month pays for the subscription.
Prices start after the beta. No card required, disconnect in one click. Terms for stores that join during the beta are never changed retroactively. Plan comparison and pricing questions →
We check robots.txt, llms.txt, sitemap, JSON-LD, price and stock readability, delivery and return policies, and whether your pages are served to agents as clean Markdown. The check at the top of the page shows a 0–100 score with a status of "invisible / partially ready / ready" and a prioritized fix list right away; leave your email here and we will send a detailed action plan within 1–2 business days.
No. Detection adds under 5 ms and makes no external requests while the page renders. Events are sent asynchronously, after the visitor gets the response.
AI-bot visits (URL, page type, response code, and the bot's IP address to verify it) and pseudonymous shopper data: page views and shop events tied to random browser identifiers, and orders (order ID, total, items, payment method). We never receive shoppers' names, e-mails, addresses or card details. A shopper's IP address is used only on arrival, to determine the country and to tell people from bots, and is then discarded.
Free during the beta. After it: Free €0 (one-off audit and badge), Starter €19/mo, Pro €49/mo. The first 20 connected stores keep these prices forever.
WooCommerce — install the plugin, about 15 minutes. A storefront from a feed — also about 15 minutes, no code. A Cloudflare Worker — about 15 minutes in the Cloudflare dashboard, no server access needed. The PHP or Node.js SDK — about an hour of developer work in your app's code.
Depends which ones. Blocking scrapers is right; blocking OAI-SearchBot, ChatGPT-User or PerplexityBot means vanishing from ChatGPT and Perplexity answers, while blocking GPTBot only keeps your pages out of model training. The audit shows who you're blocking today.
That is the reason. Median AI readiness across 63 Moldovan and Romanian stores is 38/100: the market is still nearly invisible to assistants, and our index records zero AI-attributed orders so far. The first machine-readable stores will take the first orders, and checking costs nothing.
Yes. Besides the WooCommerce plugin there are the PHP SDK (Composer), the Node.js SDK (npm) and an agent storefront built straight from your product feed — no code. A feed storefront takes about 15 minutes, an SDK about an hour. AI-bot analytics works through a Cloudflare Worker or the PHP / Node.js collector; order and revenue attribution currently needs the WooCommerce plugin.
We publish what we measure with: the audit methodology, the public MD/RO store rating and the AI traffic index (issue #1, August 2026) with raw numbers and the method's limits. The site itself is built to its own methodology — it has llms.txt, a markdown version of every page and JSON-LD. Check us with our own audit: put botmetria.com into the form above.
We have just launched — during the beta everything is free: the audit, the connection, analytics and reports. The first 20 connected stores keep beta pricing forever — €19 or €49 once plans switch on. Join now and shape what we build next.
Run the free audit