What crawlers can read
HTML, robots, structured data, public copy, policy pages, and link paths.
A bounded public-data audit that turns crawlable product evidence into a decision brief, remediation tickets, and a retest path — without pretending to guarantee AI rankings.
Manual fallback: jan@mg5.org. Static page, no server-side intake, no tracking pixel, no raw evidence pack in first touch.
Variant facts, shipping caveats, and citeable policy paths need remediation before monitoring.
The audit separates what exists publicly from what an AI-assisted buyer can safely cite, compare, and hand off.
HTML, robots, structured data, public copy, policy pages, and link paths.
Questions about variants, use cases, shipping, returns, trust, and exact-product routing.
Owner-assigned remediation tickets with acceptance checks and a before/after delta certificate.
Collect only scoped public pages and browser-visible facts.
Separate product facts, policy facts, dynamic facts, and unsupported claims.
Optional point-in-time probes, never represented as platform ranking guarantees.
Readable enough for leadership; specific enough for ecommerce, SEO, and development teams.
Tickets, owner hints, guardrails, and an honest before/after delta path.
The public sample shows artifact quality without exposing raw transcripts, real customer data, named competitor scoring, or local operator paths.
| Dimension | Signals checked | Result |
|---|---|---|
| Answerability | Facts, variants, use cases | partial |
| Citation readiness | Policies, trust, canonical URLs | needs map |
| Purchase handoff | Exact routes, caveats | blocked |
| Retest path | Acceptance checks | ready |
Pricing remains a hypothesis until scoped: starter proof packet €499–999; value pack €1.5k–3k; monitoring only after the first audit proves value.
Adjacent, but narrower. It checks whether AI-assisted buyers and answer engines can extract, cite, compare, and safely route product information.
No. Live checks are method-labeled, point-in-time evidence, not deterministic rankings.
Yes, after one or two scoped pilots prove delivery quality and support load.
For the starter packet, public URLs are usually enough. Permissioned feeds or analytics require explicit scope and data-handling approval.