Technical SEO
Technical SEO
Live

Ecommerce Site Auditor

Storefront audit: faceted nav, schema, OOS handling, more.

Source

Fetch a product or category page.

Score

100

Checks

Fetch a page to audit.

Start here · What does this ecommerce audit check?

Ecommerce SEO blends structured data, trust signals near the buy box, and template hygiene on product and category URLs.

After a fetch, the tool parses DOM text and JSON-LD to score patterns: Product versus Collection schema, breadcrumb markup, visible prices, inventory language, review signals, purchase CTAs, image counts on product templates, facet UI on collections, trust copy, and canonical tags.

Scores are heuristic: they help you compare templates, not replace a full crawl or checkout test.

When to use this tool

  • New theme QA

    Run the PDP template and a category template after a redesign to see if Product schema or breadcrumbs regressed.

  • Marketplace seller pages

    Verify price and stock language appears when the CMS hides inventory until JavaScript runs—remember only server HTML is visible here.

  • Review snippet readiness

    AggregateRating in schema or visible star copy triggers the reviews check as a quick sanity pass.

  • Faceted navigation inventory

    CollectionPage or ItemList plus filter cues informs whether faceted navigation is obvious to the parser.

Examples

Walk through these with the form above — they are practice scenarios, not live data.

Product detail page

Try this

Fetch a live https:// product URL with images, Add to cart copy, and JSON-LD.

What to look for

Expect higher scores when Product type, canonical, visible price, and four or more images align.

Category listing

Try this

Fetch a category URL that lists many SKUs.

What to look for

Collection signals and facet counts matter more than Product schema. Expect different check severity.

Short tutorial

Follow in order the first time you use the tool; later you can skip to the step you need.

  1. Step 1 — Pick representative URLs

    Test one bestselling SKU, one long-tail SKU, and one category hub.

  2. Step 2 — Fetch or paste HTML

    Use Fetch a page for public URLs or paste static HTML exports from your render service.

  3. Step 3 — Read the checklist

    OK, warn, and error rows map to concrete merchandising or technical fixes.

  4. Step 4 — Compare left and right columns

    The numeric score summarizes penalty weighting; use individual rows to build tickets.

  5. Step 5 — Fix and rerun

    Ship template changes, purge cache if needed, and fetch again to confirm the delta.

More detail

New here? Skim Start here first, then run one Examples scenario in the form above.

Ecommerce Site Auditor does one job: storefront audit: faceted nav, schema, OOS handling, more. It lives under Technical SEO on SEOToolkits, where the beginner idea is simple: Technical SEO keeps pages crawlable, indexable, fast enough, and understandable to search engines.

FAQ

Why does it say Product schema is missing?
Either JSON-LD lacks a Product @type or parsing failed. Validate JSON syntax and ensure the script is server rendered.
My prices load in JavaScript only
This audit only sees the HTML returned by the fetch. Pair results with a rendered DOM crawl for SPAs.
Can it see my cart or checkout?
Only if the URL returns public HTML without login. Do not paste authenticated pages.
Does the score affect Google rankings?
No. It is an internal rubric to prioritize fixes, not a ranking model.

Same workflow cluster on SEOToolkits — open another module without leaving context.