A real report, anonymised. Written on 28 October 2026 for a small online shop selling design consulting and digital guides; the shop’s name and products are hidden. Yours is researched the same way. Order yours
AI Agent Readiness Report · 28 October 2026
example-studio.com
example-studio.com is half-ready for AI agents. Its product pages are already well built: all seven we read state the name, price in US dollars and availability in their product data, which is more than most shops get right. The biggest gap is that the server turned away Google's, Apple's and Microsoft's crawlers when we asked as them, which can keep the shop out of Google's AI answers, Siri and Copilot. This week, ask your host or security plugin to stop blocking verified search crawlers, and add refund, terms and privacy pages: an AI agent won't recommend buying from a shop whose policies it can't find.
1. Reachable partly
- robots.txt allows every AI crawler; it only keeps WooCommerce's own files and the admin area private, which is correct.
- When we asked the home page as OpenAI's, Anthropic's, Perplexity's, DuckDuckGo's and Mistral's agents, the server answered normally.
- When we asked as Googlebot, Applebot and Bingbot, the server refused with HTTP 403 (forbidden). These three feed Google's AI Overviews and AI Mode, Apple's Siri and Spotlight, and Bing and Microsoft Copilot.
- GPTBot and Meta's training crawler got HTTP 429 (too many requests). Blocking training is your choice and isn't counted against you.
- Caveat: we ask from our own server, not from Google's, Apple's or Microsoft's real addresses. Security plugins and hosts often block requests that use a crawler's name from an unknown address while letting the real crawler through, so the real bots may be fine. Google Search Console will tell you for certain.
What to do
- Open Google Search Console (search.google.com/search-console), add example-studio.com, and use URL Inspection on your home page and one product page. If it says Google can't fetch the page, the block is real. (you, minutes)
- If the block is real: check the WordPress security plugin (Wordfence, Sucuri, All-In-One Security or similar) and the host's firewall or bot protection for rules that block 'bots' or 'crawlers', and switch on the option that lets verified search engine crawlers through (most security plugins and hosts have one; ask your host if you can't find it). (your developer, hours)
- Re-run the free Khanyo check afterwards to confirm all eleven AI search and answer agents get through. (you, minutes)
2. Readable ready
- We found 9 pages in your sitemap that look like products; 7 are real product pages and 2 are category pages.
- All 7 product pages state the product's name, price, currency (USD) and availability (in stock) in schema.org product data, and none of them is empty without JavaScript or marked noindex. Example: the premium consultation package, 497.00 USD, in stock.
- Missing but useful: brand (the studio's name) on every product, and a description on the ebook-design product. Barcodes and shipping don't apply to services and digital guides.
What to do
- Add the studio's name as the brand to the product data of every product (in WooCommerce: a brand attribute, or the free Khanyo product-data plugin, which adds a brand field to WooCommerce's own product data). (your developer, hours)
- Write a short description for the ebook-design product so assistants can say what it is. (you, minutes)
3. Listed unknown
- Most of what you sell is a service (the consulting packages and the visual makeover) or a digital guide or ebook.
- Google Merchant Center, which feeds Google's AI shopping results and its new agent checkout, doesn't accept services, and restricts ebooks and digital books (Google's 'Unsupported Shopping content' policy, checked 28 October 2026). So the usual product feed route mostly doesn't apply to your shop.
- We couldn't check whether you have a Google Business Profile or any listing on a marketplace for designers; these weren't linked from your home page.
What to do
- Create a free Google Business Profile for the studio (business.google.com) as a service business, with your services, prices and website: this is how Google's AI finds and describes services rather than products. (you, hours)
- Skip Google Merchant Center for now; revisit it only if you start selling physical products (printed planners, kits). (you, minutes)
4. Trustworthy not yet
- Your home page links to a contact page (it opens and invites people to describe their project), and PayPal appears as a payment method.
- We found no link from the home page to a refund policy, terms and conditions, or privacy policy. For digital products and services this matters more, not less: buyers (and agents acting for them) want to know what happens if a consultation is cancelled or a guide doesn't suit them.
- Your cart page opens normally, with no CAPTCHA and no forced sign-in, which is good for both people and agents. Prices are shown in US dollars while the site is in Spanish: say who you serve (for example 'clientes en toda Latinoamérica y España') so an assistant can match you to the right shoppers.
What to do
- Publish three short pages and link them in the footer: Refunds and cancellations (what happens if a consultation is cancelled, whether digital guides can be refunded), Terms and conditions, and Privacy policy. WordPress has a privacy-page template under Settings > Privacy. (you, hours)
- Add the refund policy to your product data as a return policy (MerchantReturnPolicy), so assistants can read it from each product; the free Khanyo shipping & returns tool writes the code from your answers. (your developer, hours)
- Add one line on the home page and in each product description saying how the service is delivered (online, in Spanish) and where your clients are. (you, minutes)
5. Checkout not yet
- Agent checkout is arriving through two standards: Google's Universal Commerce Protocol (joined through Merchant Center, for eligible merchants, mostly US so far) and OpenAI and Stripe's Agentic Commerce Protocol.
- For WooCommerce, WooCommerce's own page says agentic checkout is 'coming soon' through the Stripe for WooCommerce extension (checked 28 October 2026); ChatGPT's in-chat checkout is limited to approved merchants.
- Your shop takes PayPal; we found no sign of Stripe. Because you sell services and digital goods, Google's agent checkout is unlikely to cover your shop soon (it is built on Merchant Center, see step 3).
What to do
- No action needed this month. When you next review payments, add the official Stripe for WooCommerce extension alongside PayPal: it is the route WooCommerce has named for agent checkout. (your developer, hours)
Your plan
This week
- Check Google Search Console's URL Inspection for your home page and one product page to see whether Google can really fetch them.
- Publish refund and cancellation, terms, and privacy pages and link them in the footer.
This month
- If the crawler block is real, allow verified search crawlers in your security plugin or host firewall, then re-run the Khanyo check.
- Create a Google Business Profile as a service business.
- Add your brand to every product's data and your refund policy as a return policy.
When agent checkout opens in your market
- Add Stripe for WooCommerce next to PayPal and join the agentic checkout waitlist it offers.
- Re-check which of your products agent checkout accepts: services may stay excluded.
Sources
- Google Merchant Center: Unsupported Shopping content (services, digital content)
- WooCommerce: Make your store visible to AI agents (agentic checkout via Stripe, 'coming soon')
- Google: Universal Commerce Protocol features for retailers
- Agentic Commerce Protocol: get started
- Google Search Console: URL Inspection tool
- Khanyo: AI search vs AI training crawlers
An independent review by Khanyo from what your shop showed on the day we checked it. Not a promise of being recommended or ranked. Questions: hello@khanyo.app.