AEO for E-commerce
Review product facts, offers, variants and category navigation, and do not promise AI shopping inclusion.
What to check yourself
Check the relevant search product’s documentation and the results you observe yourself. Query coverage and product selection vary. AEOprobe has no verified current industry-wide AI Overview percentage for e-commerce. Product markup does not guarantee a shopping recommendation.
Recommended schemas
- Product and Offer
- Real products, prices and availability
- ProductGroup and hasVariant
- Product variants such as size, model or configurationFollow the search feature’s documentation.
- aggregateRating
- Ratings that are genuine and visibleIt is not mandatory for every product.
- BreadcrumbList
- Breadcrumb navigation shown on the page
Use only markup that applies and matches content visitors can see.
Google FAQ rich results stopped appearing from 7 May 2026.
Write helpful Q&A on the page and do not promise a rich result.
Common AEO issues
| Issue | Impact | Fix |
|---|---|---|
| Offer data differs from the visible page | ImpactCustomers and tools receive inconsistent price, currency or availability details. | FixKeep visible product facts and any applicable Product and Offer markup in sync. |
| Variants are ambiguous | ImpactA price or availability may attach to the wrong size, model or configuration. | FixGive variants clear identifiers. Follow the ProductGroup and hasVariant guidance that applies. |
| Review markup is unsupported by real reviews | ImpactMarkup can misrepresent the product. It can also break a search feature’s data policies. | FixUse only genuine displayed reviews and ratings that apply. Do not invent testimonials or review totals. |
| Important offer facts depend on JavaScript | ImpactCrawlers that do not run JavaScript may miss those facts. | FixKeep essential offer details in accessible text. Compare the initial and rendered HTML. |
Key tools
- AEOprobe
Reports technical page findings and JSON-LD checks. Then gives source-backed repair instructions and supports scoped rechecks.
- Schema Markup Validator(opens in a new tab)
Checks Schema.org markup. Valid markup does not guarantee a Google rich result or an AI citation.
- Google Rich Results Test(opens in a new tab)
Checks markup for supported Google rich-result features. Passing does not guarantee display.
Step-by-step guide
- 1
Select representative product pages
Include a simple product, a product with variants and a category page. Record the exact URLs and the review scope.
- 2
Check public access
Decide which uses of your public content you intend to allow.
- Check each relevant crawler’s current documentation.
- Search and training bots have different roles. For example, OAI-SearchBot is for search and GPTBot is for training.
- Check robots.txt and hosting or firewall access separately.
- Protect private content with authentication and authorization. Robots.txt is not access control.
- 3
Verify product facts and variants
Compare names, identifiers, currency, prices and stock status with the actual offer. Fix any conflict between visible and structured information.
- 4
Validate applicable markup
Use Product, Offer and ProductGroup where they fit. Check supported search features and generic Schema.org markup with the right tools.
- 5
Publish source-backed changes
Keep buyer questions, policies and comparisons accurate. Publish the repair yourself or with your developer.
- 6
Recheck the same observations
Review the repaired URLs and keep before and after evidence. Measure visits and sales separately. AEOprobe claims no conversion lift.
From a finding to a checked repair
The free audit covers up to 3 pages and needs no sign-up. A saved-site audit costs 20 credits. It covers up to 10 pages on Free, 50 on Watch and 100 on Pro. A free account shows 5 findings for each site, and a paid plan shows them all.
A saved-site finding becomes a to-do with the evidence, what to change and how to check it. You or your developer publish the edits, then run a scoped technical recheck. Claude Code and Codex can work in the same flow. After a coding agent reports a fix, its recheck runs by itself within your weekly credit limit. Every other action that spends credits asks for your confirmation first.
AEOprobe plans are Free at €0/month, Watch at €7/month and Pro at €21/month. Credit packs add extra credits to a Watch or Pro plan. Only customers with an active Watch or Pro plan can buy them. Credits that expire soonest are used first, usually the monthly ones. Bought credits stay valid for 12 months after purchase, even if your plan ends. They can still pay for audits and checks after your plan ends. They do not open the full lists without an active Watch or Pro plan. A page capture or recheck costs 1 credit. Your account shows what you can buy. See plans and credits and the coding-agent workflow.
Sources and technical guidance
Checked Oct 2026
- Google guidance for generative AI search (opens in a new tab)
- Google documentation updates (opens in a new tab)
- Google robots.txt guidance (opens in a new tab)
- Google JavaScript SEO guidance (opens in a new tab)
- Google structured-data policies (opens in a new tab)
- OpenAI crawler roles (opens in a new tab)
- Google product snippets (opens in a new tab)
- Google product variants (opens in a new tab)
Questions
Will Product schema increase conversion rates?
AEOprobe has no evidence of a conversion lift for your store. Accurate markup can support the search features that apply. Measure sales and AI referrals separately.
Does structured data guarantee AI search inclusion?
Google does not require special schema for generative search. Markup does not guarantee a citation.
What does AEOprobe check?
The audit checks robots.txt policies for AI crawlers and other technical page findings. For structured data it reads JSON-LD only. See the audit methodology.
How do I turn a finding into a published fix?
A saved-site finding becomes a to-do with what to change and how to check it. You publish the edits, then run a recheck. See the steps and costs on this page.
Check what AI crawlers can actually reach
Run a free audit to find public crawler, indexing, markup, and page-structure issues.
Run free audit