Ecommerce SEO Audit — Website Evidence
See what your storefront declares about products.
Inspect a small page sample for product, offer and variant declarations. Review each observation alongside its page, JSON block and field path.
When enabled, the same fetched HTML also provides observed filter-link patterns. Parameter destinations are not requested; name-based hints do not establish facets, duplicates or indexing.
Product evidence in your page sample
Coverage and request sources
Downloads include the full returned report, regardless of the selected view or search.
Methodology and limitations
- Only the initial HTML of a bounded same-origin sample is inspected. JavaScript-rendered content, styles, images, profiles, external contexts and search engines are not requested.
- Only supported Schema.org JSON-LD declarations are interpreted. Aliases, custom contexts and reference-only values can remain unsupported. Missing means not observed in supported declarations, not absent from the product.
- Only exact Product, ProductGroup, Offer and AggregateOffer types are recognized. Structured values outside the supported subset remain unknown. Price/currency values are not independently verified.
- Occurrences and nested variants remain separate, even when IDs or names match. IDs are not dereferenced. Query values are removed from declared URLs; query/action URLs and redirected robots rules are not requested.
- Robots instructions, page limits and shared request, byte and time budgets can reduce coverage. An uninterrupted sample is never proof of complete site coverage.
- No ranking, inventory, eligibility or store quality score is invented. No report is saved in browser storage.
Review the product information your pages declare
Enter a public storefront or product URL. The tool checks robots instructions and inspects a small same-origin initial-HTML sample. Review supported Product, ProductGroup, Offer and AggregateOffer declarations alongside source pages, JSON blocks, field paths and extraction limits.
Inspect coverage before interpreting the fields. A failed, excluded or unsupported page cannot establish that products are absent. Nested offers and variants stay separate; repeated IDs are not merged. Prices, currencies and availability are website declarations, not independently verified stock or purchase information.
A focused storefront evidence check
No paid API is needed. This is not a Merchant Center, checkout, sales, indexing or rich-result eligibility audit. It does not run target JavaScript, load product images, follow query/action URLs or submit carts. Redirected robots instructions are conservatively declined. For broader technical evidence, use the existing Website SEO Analyzer. For fuller supported JSON-LD processing, use the Structured Data Checker.
Questions about ecommerce website evidence
Does this audit Google Merchant Center or verify stock?
No. It reads public initial HTML, not Merchant Center, checkout, inventory, live prices, sales, rankings or Google indexing. Markup is a website declaration, not proof of current business operation or search eligibility.
How many pages are checked?
Three page outcomes by default, with an administrator maximum of five. Failed, excluded and redirect-alias outcomes count toward the limit. Robots rules and shared request, byte and time budgets can reduce coverage.
What markup is interpreted?
A limited Schema.org JSON-LD subset for exact Product, ProductGroup, Offer and AggregateOffer types. Custom contexts, aliases, references, Microdata, RDFa and rendered JavaScript can remain unknown. Missing means not observed on a supported declaration, not absent from the product.
Does it follow every product variant or checkout link?
No. Only observed eligible same-origin content links are scheduled. Query strings, cart, checkout and action paths are excluded from collection. IDs are not dereferenced, variants are not merged, and no purchase, form or conversion event is submitted.
Are APIs or saved reports required?
No paid API or account is required. Raw page bodies and reports are not saved by this module. Shared CAPTCHA and usage protections apply; destination servers and ordinary infrastructure may log requests. Exports remain under your control.