Critical. An AI agent can barely buy from you.

https://www.notino.nl/

📊 Below the e-commerce (all verticals) median (-24). (median 48 · provisional)

⚔️ Compare against your competitors →

💬 What this means for your business

To an AI shopping assistant, your store is mostly invisible: it can't properly see, understand or buy what you sell.

What's costing you the most right now:

→ Your product pages don't describe products in the format AI assistants read — to them, your catalog looks empty.
→ Sizes and options aren't machine-readable — an assistant can't pick "size M" and finish the order.
→ AI assistants can't see your prices — so they can't quote you, compare you, or complete a purchase.

Get it fixed — pick your path

I have a developer (or I am one)

Pro gives you the step-by-step plan to 24/100, the exact how-to for every fix, ready-to-paste code for your own products, plus daily monitoring, competitor watch and catalog coverage. €49/month, cancel anytime.

Unlock my plan →

I don't — do it for me

We apply the fixes on your store for you, end to end, and hand you the before/after score. No tech knowledge needed on your side.

Ask us to do it →

Breakdown by pillar

🔓 Access & crawlability 24.0/40.0

✓ robots.txt allows agent crawlers ⓘ What we checked: Your site has a small doorman file that tells visiting AI services whether they're welcome. We read what yours says.
Why it matters: Many stores block AI tools by accident — often a copied setting — without ever deciding to.
If ignored: Assistants politely obey the "keep out" sign and quietly shop somewhere that lets them in. · 20.0/20.0
robots.txt allows GPTBot, ClaudeBot, PerplexityBot and Google-Extended.
✗ No blocking / cloaking of AI bots ⓘ What we checked: We visited your store twice — once as a normal shopper, once as an AI assistant — and compared what each one got to see.
Why it matters: If assistants get a blocked or empty page while humans see your shop, to them your store simply doesn't exist.
If ignored: Every sale that starts with "ask your assistant" goes to a competitor, and you never see it happen. · 0.0/8.0
The homepage doesn't respond correctly (status 403).
✗ llms.txt present ⓘ What we checked: We looked for llms.txt — a one-page, plain-text introduction of your store, written for AI assistants.
Why it matters: It's the cheapest way to tell assistants what you sell, in your own words, before they guess from your pages.
If ignored: Assistants describe your store from whatever they piece together — or from what others say about you. · 0.0/4.0
No /llms.txt.
✓ Sitemap available ⓘ What we checked: We checked for a site map — the machine-readable index of every page your store has.
Why it matters: It's how assistants discover products beyond the few your homepage links to.
If ignored: Most of your catalog stays invisible: assistants only ever find your front window. · 4.0/4.0
Sitemap found via robots.txt.
✗ Content accessible without JS rendering ⓘ What we checked: We read your page the way most assistants do: the raw text your server sends, before any visual code runs in a browser.
Why it matters: If your products only appear after that code runs, an assistant reading the raw page sees an empty shop.
If ignored: A full catalog that looks like a blank storefront to every text-reading assistant. · 0.0/4.0
Couldn't retrieve usable HTML.

🏷️ Structured data 0.0/35.0

✗ Product JSON-LD present ⓘ What we checked: We checked whether your product pages carry a structured product sheet — name, price, stock — in the standard format machines read.
Why it matters: Assistants don't "look at" your beautiful page; they read this sheet. No sheet, no product.
If ignored: You're not comparable, not quotable and not buyable — the three things an AI shopper needs. · 0.0/12.0
No product page found to crawl, and no Product JSON-LD on the homepage.
✗ Structured price + currency ⓘ What we checked: We checked whether your price (with its currency) is written in that machine-readable product sheet.
Why it matters: "How much is it?" is the first question every shopper asks — the assistant must answer it with certainty, not guess from the page.
If ignored: Assistants either skip you or show you without a price next to competitors who have one. Nobody picks the mystery price. · 0.0/8.0
No price exposed inside offers.
✗ Structured availability ⓘ What we checked: We checked whether your product sheet says if the item is in stock right now.
Why it matters: An assistant completing a purchase won't gamble on availability — it recommends what it can confirm.
If ignored: Even products sitting in your warehouse get treated as "maybe unavailable" and left out. · 0.0/5.0
No availability field — the agent can't tell if it's in stock.
✗ Structured brand ⓘ What we checked: We checked whether your brand name is part of the machine-readable product sheet.
Why it matters: It's how assistants connect your products to your name when someone asks for you — or for "a brand like X".
If ignored: Your products float around nameless; the reputation you've built doesn't transfer to AI shopping. · 0.0/3.0
No structured brand.
✗ Product identifier (SKU / GTIN) ⓘ What we checked: We looked for a unique product code (like the number under a barcode) in your product sheet.
Why it matters: It's how an assistant is certain it's ordering exactly YOUR item — the 250ml one, not the 500ml.
If ignored: Wrong-item mistakes and cautious assistants that prefer stores where identity is certain. · 0.0/4.0
No identifier (sku/gtin/mpn) — the agent can't disambiguate the product.
✗ Aggregated reviews (aggregateRating) ⓘ What we checked: We checked whether your customer reviews and stars are published in machine-readable form (only if you really have them).
Why it matters: Assistants weigh trust signals when ranking similar offers — invisible reviews count for nothing.
If ignored: A competitor with worse reviews — but readable ones — outranks you in every recommendation. · 0.0/3.0
No aggregateRating — the agent can't compare your reputation.

📦 Catalog & attributes 0.0/25.0

✗ Structured variants ⓘ What we checked: We checked whether your options — sizes, colors, formats — exist as structured choices, not just dropdown menus on the page.
Why it matters: "Order it in size M" only works if size M exists as data the assistant can select.
If ignored: The sale dies at the last step: the assistant found you, chose you, and couldn't finish. · 0.0/10.0
No usable variant data.
✗ Attributes as fields (not prose) ⓘ What we checked: We checked whether your product specifics — material, dietary labels, capacity — are data, not just sentences in a description.
Why it matters: Shoppers ask assistants for "vegan", "cotton", "under 200g" — filters only catch products whose traits are machine-readable.
If ignored: You vanish from filtered searches you should win — the shortlists are built without you. · 0.0/8.0
No structured filterable attribute — the agent can't filter.
✗ Product feed / catalog signals ⓘ What we checked: We looked for a product feed — a single file listing your whole catalog that machines can read in one pass.
Why it matters: It's the difference between an assistant browsing your store aisle-by-aisle or receiving your full catalog instantly.
If ignored: Assistants know three of your products; your competitor's entire catalog is on the table. · 0.0/7.0
No machine-readable product feed nor OpenGraph product tags.

📈 Your roadmap to a higher score

No roadmap needed: your store is already nicely agent-ready 🎉

Get the full report + monitoring

Automatic re-scan, alert if your score drops, and fixes generated for your products (JSON-LD, llms.txt, attribute mapping).

🔗 Shareable link to this report: https://www.agentready.market/r/3

⤓ Export this report as JSON (for your tools)

📛 Your live Agent-ready badge

Rendered by us from your latest scan — it updates when your score does, and it can't be faked or go stale. It links to your live report. Paste it in your site footer or README.

Embed on your site (HTML)

<a href="https://www.agentready.market/verify/www.notino.nl"><img src="https://www.agentready.market/badge/www.notino.nl.svg" alt="AgentReady — can an AI agent buy on this store?" height="28"></a>

GitHub / GitLab README (Markdown)

[![AgentReady — can an AI agent buy on this store?](https://www.agentready.market/badge/www.notino.nl.svg)](https://www.agentready.market/verify/www.notino.nl)

At 80/100 (with agents not blocked) the badge flips to agent-ready ✓ — your fixes above are the way there.

🛠️ Generated fix pack ready to paste

Built deterministically from your own catalog data — copy, paste, ship.

llms.txt free — publish at /llms.txt

# Notino

## Policies
- Shipping: <add your delivery times and zones>
- Returns: <add your return policy>

## Sitemap
- https://www.notino.nl/sitemap.xml

🔒 Product JSON-LD + attribute map are Pro

The catalog-specific artifacts that actually move your score — generated from your products. (Your llms.txt above is free.)

Unlock with Pro

Already Pro? enter your email.

Product JSON-LD — add to your product page <head>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "••••••••••••",
  "brand": "••••••",
  "offers": { "price": "••••", "availability": "••••••" }
}
</script>

Attribute mapping — expose these as structured fields

Your option	schema.org field	Example
••••	`••••`	••••

← Scan another store