Agent-Readiness Checklist
Agent-readiness checklist parts
Agentic Readiness
The chain rule: order matters more than effort
This is not a grab bag of improvements to work through in any order. The chain is:
Access → Readability → Data → Visibility → Protocol → Transaction → Measurement
Skip a link and the spend above it is wasted. A site with a flawless feed that blocks crawlers is never found in the first place. A store that appears in AI answers but carries stale stock data loses the agent’s trust in a way that is slow to recover.
Scope: the checks are split so they work for product businesses and for service and B2B businesses. A B2B firm with no product feed can skip Parts 3 and 5. Parts 1, 2, 7, 8 and 9 apply to everyone.
Scoring and maturity tiers
Critical items are worth 3 points, important items 2, maturing items 1. Drop any part that does not apply to you out of the denominator and score as a percentage. The full list is worth 354 points across 70 critical, 66 important and 12 maturing items.
| Percentage | Tier | What it means | Next move |
|---|---|---|---|
| 0-25% | Tier 0 · Invisible | The agent cannot read the site or cannot understand the product | Parts 1 and 2 |
| 26-50% | Tier 1 · Accessible | The agent can read it, but the data is not trustworthy | Parts 3 and 6 |
| 51-75% | Tier 2 · Feed-Ready | The data is trustworthy, but there is no visibility or measurement | Parts 8 and 9 |
| 76-90% | Tier 3 · Agent-Native | The channel is live and measured | Parts 4 and 10 |
| 91%+ | Tier 3+ · Reference | Mature, governance and trust layers included | Lead a pilot |
The rule that overrides the score: you have not reached a tier until every critical item in that part is met, however high the percentage. If OAI-SearchBot is blocked in robots.txt, a score of 80% still means Tier 0.
A 0-30-60-90 day sequence
Days 0-30 · Access and readability. All of Part 1, then 2.1 to 2.12, then 9.1 to 9.3 and 9.9 for the baseline, then 8.1 and 8.2 for the prompt set and first measurement. Outcome: a site open to crawlers with validated schema, and a measurement baseline.
Days 30-60 · Data and reliability. All of Part 3, then 6.1 to 6.4 and 6.7, then 5.1 to 5.3 for unit economics, then 12.1 and 12.2. Outcome: a validated feed, 98% stock accuracy, and a decision on which SKUs belong in the channel.
Days 60-90 · Channel, visibility and governance. Items 4.1, 4.4, 4.5 and 4.9, the rest of Part 8, then 7.3, 7.5, 7.6 and 7.9, then Part 10 if you are targeting export markets, and a review of Part 11. Outcome: live products in at least one agentic channel, a measured visibility change, and a written authority and rollback policy.
Red flags
If any one of these is true, stop everything else:
- The WAF or robots.txt blocks legitimate search and agent crawlers.
- Price or stock differs between the feed and the site.
- Product information renders only through JavaScript.
- The feed contains invented GTINs. A fabricated barcode is a permanent account risk.
- Reviews or AggregateRating are fabricated.
- Stock accuracy is below 90%.
- No logs are kept for agent transactions.
- Commission plus processing fees exceed product margin, and the channel is open anyway.
- Budget was allocated for the domestic market without knowing ChatGPT Ads does not target Turkiye.
- The vendor contract is billed by the hour with no verifiable milestone.
Honest limits
What should be said out loud when this list is presented:
- It does not guarantee sales. Agentic commerce today is mostly a discovery and visibility channel; the first wave of embedded checkout was pulled back for behavioural reasons. Most of the investment belongs in feed quality and AI visibility, not checkout integration.
- The Turkiye asymmetry is real. Part 10 and some of Part 4 currently return nothing in the domestic market. The value is in export markets.
- Measurement is incomplete. A meaningful share of AI traffic cannot be captured by any setup. Treat the numbers as a floor.
- The protocols move. ACP, UCP and AP2 specifications change quarterly. This list reflects August 2026; the checks will hold, the technical detail will not.
- Be sceptical of industry statistics. Claims like “AI traffic converts X times better” are usually single-source and selectively sampled. Your own baseline is the only evidence that counts.
Technical specifications should be re-verified quarterly against primary sources: developers.openai.com/commerce, agenticcommerce.dev, the Universal Commerce Protocol repository and ap2-protocol.org.
A ten-minute field audit
Reading the result
9 or more yes: Agent-Native candidate · 6-8: Feed-Ready · 3-5: Accessible · 0-2: Invisible
These twelve questions are one critical item drawn from each part of the 148-item list. They place a business quickly; they do not replace the full audit. Work through every critical item in the relevant part before assigning a tier.