Free tool · Answer-engine readiness

AEO Grader for any product page.

Before an answer engine can recommend your product, it has to read the page. The AEO Grader scores any URL 0–100 on the four structural signals that decide whether ChatGPT, Perplexity, or Google AI Overviews can cite it — and ranks the fixes by severity.

Free No signup ~30-second result
Report manifest
Composite AEO score (0–100) with tier: excellent / good / needs-work / at-riskfree
Four-bucket breakdown: structured data, content depth, crawler access, llms.txtfree
Top 3 findings ranked by severity, each with the fixfree
Remaining findings — typically 5 to 10 more, down to low severityemail

Rate limit: 1 run per 30 seconds per IP. The grader reads only public data.


What the four buckets check

Every finding maps to a documented fix. The weights reflect what moves citations in observed audit data, not a marketing scheme.

Bucket · weightWhat it checksFix guide
Structured data · 30Product JSON-LD presence and completeness — name, brand, SKU, GTIN, offers, availability, aggregateRating. Engines use it to resolve identity and price.Schema for AI search
Content depth · 30Description length and answer coverage: does the page answer material, fit, compatibility, and care questions in quotable prose, with FAQ content where it helps.What is AEO
Crawler access · 30robots.txt admittance for AI crawlers, canonical hygiene, and meta directives. A blocked GPTBot zeroes out everything else on the page.Rank products in ChatGPT
llms.txt · 10A curated crawl map at the domain root pointing AI crawlers at the pages that describe the brand and flagship catalog.llms.txt for Shopify

How to read the score

Composite bands: 80–100 means the page is structurally ready and remaining gains come from content and review signal; 60–79 means one or two buckets are dragging, usually thin schema or a robots.txt drift; 40–59 means the page needs a planned fix cycle; below 40 means foundational work has not started and the page is effectively invisible to answer engines regardless of how well it ranks on classic Google.

Two cautions. First, the score measures readiness, not citations — a 90 on a product nobody queries still gets zero citations, and live testing belongs to the ChatGPT checker. Second, AEO practice is still forming; the grader weighs the signals with the strongest observed correlation to citation behavior as of mid-2026 and the weights will move as engines do. Definitions for every term in the report live in the glossary, starting with AI visibility score.

Most teams use the grader as a quarterly snapshot: run it on the best-seller, archive the number, fix the top three findings, re-run. The catalog-wide version of that loop — every SKU, every week, with the fix shipped as a diff — is the eCommerce Insights product, and the per-page methodology is identical, so the free grade you run today is comparable to the tracked score later.

Track the trend

One grade is a snapshot. The trend is the story.

eCommerce Insights runs the AEO checks weekly on every PDP, scores citation and agent-readability separately, and sends a Monday digest with the catalog delta and the week's biggest movers.

Ask AI about the AEO Grader

Have your favorite AI engine summarize this tool for your use case.

Frequently asked questions

What is an AEO score?
A 0–100 composite measuring how ready a page is to be cited by answer engines — ChatGPT, Perplexity, Google AI Overviews, Gemini, Claude, and Copilot. Four weighted buckets: structured data, content depth, crawler access, and llms.txt. Higher scores mean the page gives engines what they need to quote it as a source. See What is AEO.
Does the AEO Grader query AI engines directly?
No — it audits the structural signals engines reward. Live citation testing is the ChatGPT checker's job, and store-wide sampling is the SKU Visibility Grader's. Run this grader as the structural readiness check.
What URL should I grade first?
Your best-selling product page. It carries the most revenue, and its gaps usually repeat across the catalog because they live in the theme template. Answer engines cite specific pages that answer specific questions — for ecommerce, that is almost always a PDP, not the homepage.
When should I use the JS-rendering option?
When your storefront renders product data client-side — common on headless React or Vue builds. If your default score looks implausibly low and the JS-rendered score is much higher, AI crawlers that do not execute JavaScript are seeing the low-score version. See eCommerce Insights for headless.
How often should I re-run the grade?
Quarterly, plus after any theme change, reviews-app migration, or robots.txt edit — the three changes that most often regress scores silently. The paid product re-runs weekly across every SKU so regressions surface in the digest, not in a lost citation.
Is the AEO Grader a generative engine optimization tool?
Yes, by that name too. Generative engine optimization (GEO) and answer engine optimization (AEO) describe largely the same practice — making pages citable by AI-generated answers — and a generative engine optimization tool audits the same signals this grader scores: structured data, content depth, crawler access, and crawl-surface files. The taxonomy is still settling; the what-is-GEO guide maps the terms. What the grader adds is an ecommerce focus: the findings are written for PDPs, not blog posts.

One number for the board. Ten fixes for the team.

The AEO Grader turns "how are we doing on AI search?" into an answerable question.