How to check if AI agents can read your PDPs.

The slow way: read your PDP like a bot

The manual audit is doable for a handful of pages. Fetch the PDP with curl or a browser's "view source" — not the rendered DOM — and ask four questions. Is there a complete Product JSON-LD block with price, availability, sku, and brand in the raw HTML? Does /robots.txt admit GPTBot, ClaudeBot, PerplexityBot, and Google-Extended? Could a parser extract the price without executing JavaScript? Can you reach the returns policy through a plain link an agent would follow?

Most teams find at least one surprise per page: the price exists only after a JavaScript hydration pass, the size chart is a JPEG, the returns policy lives in a modal with no crawlable URL. The method breaks down at catalog scale — checking four signal groups across 1,500 SKUs by hand is not a job anyone finishes — and it goes stale the next time the theme updates or an app injects markup.

The eCommerce Insights way

1. Grade one PDP free. Run the Agentic Readiness Grader on a hero SKU. The score lands in about 30 seconds with per-bot crawler access shown as an allow/deny ledger.
2. Read the four signal groups. Product JSON-LD completeness; robots.txt admittance for the AI crawlers; machine-readable price and availability; discoverable returns and shipping policies. Where applicable, the grader also flags agentic-checkout wiring (Shopify Agentic Storefronts, ACP discovery files — hedged, since the protocols are in pilot as of mid-2026).
3. Scan the catalog. On a paid plan every SKU gets the agent-readability score alongside its citation score on each refresh — weekly on Starter, daily on Growth — so a theme update that breaks JSON-LD shows up within a cycle, not a quarter.
4. Ship fixes as diffs. Missing schema fields, robots.txt lines, and metafield values arrive as reviewable diffs. Approve and push to Shopify via the admin API (Growth, early access) or export the CSV.
5. Re-test. Rerun the grader after shipping, and spot-check with the AI Crawler Simulator — it renders the plain-text view a non-JS crawler extracts. The pass condition is simple: everything an agent needs to draft a cart — price, availability, variant, policy — present in machine-readable form on first fetch.

The wider context — what agents do with readable PDPs, and what ACP and UCP change — is covered in the agentic commerce solution and the ACP guide. Schema.org's Product type reference is the canonical field list.

What "good" looks like

An agent-readability score above 80 generally means an agent can complete the research-and-draft loop on the page. Scores below 50 almost always trace to one structural cause — blocked crawlers or client-side-only rendering — rather than many small ones.

Related jobs