The agent selection maturity model sorts where your store sits in the work of getting picked by AI shopping agents, on a five-level ladder that runs from invisible to an agent up to consistently selected and measured. It is our editorial framework for deciding what to fix next, not a validated or measured maturity scale, so read the levels as a way to prioritize work rather than a score anyone has benchmarked.Hypothesis (our analysis)
Key takeaways
- The five levels ascend from level 1 (an agent cannot fetch or find you) to level 5 (you run the win-rate protocol and iterate), and each level is a prerequisite for the one above it.
- Levels 1 and 2 are eligibility, the ground official validators and protocol docs already cover; levels 3 to 5 are the selection work this handbook exists for, which no validator scores for you.
- This is an editorial framework for prioritizing work, so there are deliberately no 'percent of stores at level N' figures and no win-rate numbers on this page.
- Each level maps to specific Agent Selection Checklist categories and selection signals, so you can turn 'we are at level 3' into a concrete next task.
How to read the ladder
Treat each level as a floor for the next. Review depth and price position (level 4) do you little good if an agent still cannot read your delivery terms (level 3), and none of it matters if your pages are blocked or unparseable (level 1). So the useful question is never "how many boxes can we tick," but "what is the lowest level we have not fully cleared," because that is your real ceiling until you fix it.
The failure mode we expect most often is stopping at level 2, because that is exactly where eligibility validators stop reporting: they confirm you are readable and then fall silent on whether you win.Hypothesis (our analysis) Everything from level 3 up is judgment an agent makes when it compares you against a competitor who is equally eligible, which is the layer covered in how AI shopping agents choose products.
The five levels at a glance
| Level | What an agent sees | Checklist focus | Signal coverage |
|---|---|---|---|
| 1: Unreachable | Cannot fetch or find you (blocked crawlers, no feed, JS-only pages) | Readiness: crawler access, feed presence | Crawl directives, origin serveability, crawlable content |
| 2: Eligible | Fetches you and reads a valid, parseable feed | Readiness: product identity, offer markup, validation | Product identity, offer markup completeness, validation hygiene |
| 3: Legible | Reads a complete, comparable offer without starting checkout | Selection: offer legibility, delivery & returns, product content | Offer cost legibility, delivery ETA, returns, facts per token |
| 4: Preferable | Has reasons to pick you over an equally legible peer | Selection: trust & policy, price position | Review depth, endorsement (not sponsored), price awareness |
| 5: Measured | You know whether agents pick you, and iterate | Selection: measurement | Win-rate measurement, answer presence, retest on updates |
Level 1: Unreachable
At level 1 the agent gets nothing usable: a blocked request, a page that renders only after JavaScript an agent never runs, or a catalog that appears in no product feed. The most common self-inflicted version is blocking the wrong bot. OpenAI documents distinct agents for distinct jobs: GPTBot (crawls to train models), OAI-SearchBot (surfaces and links sites inside ChatGPT), and ChatGPT-User (the fetch triggered by a user's own request), so a blanket disallow can hide you from the very agent that decides whether a shopper sees you.Spec-factOpenAI, Bots documentation
The work here is eligibility groundwork, not selection: confirm verified agents get a 200, publish a feed, and render content server-side. The crawler-access items in the Agentic Shopping Readiness Checklist cover it, serving agent traffic explains how to afford being open instead of reaching for a block, and the AI shopping crawlers reference lists which token to allow. If you suspect you are stuck here, start the diagnosis at why your store is not in ChatGPT shopping.
Level 2: Eligible
Level 2 is table stakes: an agent can fetch you, and your feed and markup validate. Product identity, price, and availability parse cleanly, and a rich-results or feed validator passes. This is the ceiling that official docs and validators are built to certify, and it is a real, necessary achievement.
It is also where the guidance most sites follow runs out. A validator confirms your data is present and well-formed; it never tells you whether an agent, comparing you against three equally valid competitors, has any reason to choose you. Getting a feed and schema clean is covered in make your product feed AI-readable and product schema for AI shopping. Everything past this point is the layer this handbook owns, and the rest of the ladder is about earning the pick, not passing the check.
Level 3: Legible
At level 3 an agent can read your complete, comparable offer without starting checkout: all-in landed cost, a delivery estimate to a real destination, the return window and who pays, complete category specs, and descriptions that answer the questions buyers actually ask. The mechanism for the fulfillment half is documented. Google's shipping structured data expresses handling time and transit time as ranges an agent assembles into an "arrive by" estimate, rather than as literal dates.Spec-factGoogle: Shipping policy structured data Return-policy structured data carries the return window (merchantReturnDays), return fees, and refund type, so an agent relaying "can I return it?" has a machine-readable answer.Spec-factGoogle: Return policy structured data
This maps to three Agent Selection Checklist categories: offer legibility, delivery and returns signals, and product content for comparison. The density discipline behind it, packing verifiable facts into each surface, is information density for agents, and the page-level version is the product detail page anatomy. A store can pass every validator (level 2) and still fail here, because legibility is about completeness and comparability, which no validator grades.
Level 4: Preferable
Level 4 is where you give an agent a reason to choose you over a peer who is equally legible: genuine review depth and distribution, legitimate platform endorsement, a known all-in price position, a reachable seller identity, and awareness that each engine weights those differently. The strongest public evidence for these levers is a controlled study. In the ACES simulation, agents rewarded genuine platform endorsement, penalized a self-applied "Sponsored" tag, and showed a large but provider-specific grid-position effect.ReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17) Read that as a simulation across a fixed model set, not live sales, so treat the direction as the signal and the exact magnitudes as provisional.
The honest move at this level is to earn the signals, not fake them: a self-designed lookalike "verified" badge is neither legitimate endorsement nor durable. This maps to the trust and policy and price position categories of the Agent Selection Checklist; the mechanics are in how AI shopping agents choose products, the price-specific case in lowest price but not recommended, and one engine's take in Gemini and Google AI Mode ranking.
Level 5: Measured
Level 5 is the only level you cannot reach by shipping features, because it is defined by measurement: you run the manual win-rate protocol across ChatGPT, Gemini, and Perplexity, track whether each engine names your store for your category queries, record where you land when results render as a grid, and re-test on a cadence. The re-test discipline is not optional. ACES documents that model updates can drastically reshuffle which products agents pick, so a win measured last quarter can quietly evaporate.ReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17) That is a simulation finding, not a measured claim about your catalog, which is exactly why you measure your own.
This maps to the measurement category of the checklist. The protocol itself is the agent-selection measurement methodology, the metric it produces is agent win rate, and when a change does not move that number, the diagnostic path is shown but not selected. A store at level 5 is not "finished"; it has simply replaced guessing with a measured range it can act on.
Where the validators stop, and this ladder begins
The single most useful line to draw on this ladder sits between levels 2 and 3. Below it, eligibility validators and protocol docs do the grading, and we link out to them rather than restate them. Above it, no external tool scores you, and the judgment is comparative: an agent weighing you against an equally eligible competitor. That gap is why we treat agent selection as its own discipline, and why the levels above 2 are the whole reason this handbook exists. The full catalog of the signals referenced across these levels lives in the signals database.
What to measure
Turn the ladder into a repeatable check, not a one-time self-rating.
- Place yourself honestly. Run both tools: the Agentic Shopping Readiness Checklist scores levels 1 and 2, and the Agent Selection Checklist scores levels 3 to 5. Your lowest category with unmet items, not your highest, is your current level.
- Fix the lowest gap first. Adding a level-4 signal while a level-3 gap remains open is wasted effort, because the agent stalls at the missing floor. Sequence bottom-up.
- Convert "we reached level 5" from a claim into a measurement. Run the win-rate protocol per engine and report a range with a stated sample, never a single confident number, since no measured data exists to back a point figure.
- Re-score on a cadence and after every major model update, and log the date each time. A level you cleared last quarter can slip when either your data or the model changes.