Free screen
Structured field coverage
Product and Offer objects, parseability, name, image, description, brand, identifiers, price, currency, and availability.
A product-page linter for ecommerce teams
The free browser scan checks whether key Product and Offer fields, identifiers, canonical signals, headings, descriptions, and policy links are present and parseable. The paid defect pack adds selected-variant, visible-versus-structured, cross-page policy, and crawlability verification—without an opaque “AI visibility” promise.
What it inspects
The free scan returns field-presence and discoverability evidence with a repair suggestion. The paid review verifies whether those values are accurate across the visible page, selected variants, policies, feeds, and checkout context.
Free screen
Product and Offer objects, parseability, name, image, description, brand, identifiers, price, currency, and availability.
Free screen
Canonical link, visible H1, meta description, and obvious shipping, delivery, return, refund, or exchange links.
Paid defect pack
Visible-versus-structured values, selected variants, policy conflicts, representative product states, feeds, crawlability, and acceptance checks.
How it works
Paste a product page’s HTML or try a URL. The browser extracts commerce signals without requiring an account.
The free scan weights missing purchase-critical fields more heavily than optional completeness fields. The paid review separately verifies contradictions and commercial risk.
Export the findings or request a deeper audit with affected URLs, repair order, and regression checks.
Paid defect-pack example
The examples below illustrate manual cross-surface checks included in the paid defect pack; the free browser scan does not claim to prove these contradictions.
| Check | Observed | Risk | Repair |
|---|---|---|---|
| Offer availability | Schema says InStock; selected size is sold out | High | Generate availability from the selected purchasable variant. |
| Price currency | Visible £39; structured offer says USD | High | Use the storefront currency in the active offer. |
| Return policy | 30 days in FAQ; 14 days at checkout | Medium | Create one policy source of truth and synchronize every surface. |
Self-serve
Browser-based field-presence checks, parse evidence, a coverage score, repair suggestions, and JSON export.
Scan a pageDeveloper tool
Run the same bounded field checks locally or in GitHub Actions, with JSON, Markdown, text, and deterministic failure policies.
Add it to CIFounding offer
A representative catalog sample converted into an implementation backlog with evidence, repair order, acceptance checks, and one clarification round.
Request a defect packAgencies
Repeatable client reports, repair backlogs, and regression checks. Pricing opens after the first validation cohort.
Join the pilotProof
Review the report structure, evidence fields, repair ordering, and limitations before submitting a store.
Review sample evidenceMethod
See how field coverage differs from cross-surface accuracy and how findings become acceptance checks.
Read the methodologyContinuously maintained
A scheduled system verifies the site, works the highest-value safe task, records what happened, and exposes its operating health. Revenue—not activity—is the score.