Skip to content
SuiteAnalytics
Sign inStart free

A sample report

The same document a verified owner receives, produced by the shipped rules from a storefront we wrote ourselves.

Synthetic storefront

www.deep-synthetic.example is not a real shop. It is a storefront we authored for our own tests — every product, category, extension and defect in it was written by hand, and the hostname is under a reserved domain that resolves nowhere. We do not publish an audit of somebody else’s site as marketing, which is the same commitment the crawler page and the partner clauses make to merchants who are not our customers.

The findings, the scores and the skipped checks below are not written copy: they are what the rules in the product produce from that storefront, at a standard audit depth, rendered at the Enterprise plan so nothing is hidden behind a lock. The executive summary a language model writes is absent, because no model was called to produce this document and we do not fabricate one.

SuiteCommerce health report — www.deep-synthetic.example

Generated 2026-09-15T00:00:00.000Z

Scores

81 / 100Overall health

Host
www.deep-synthetic.example
Platform
sca
Release
2024.1.30 (certain, modern family)
Theme
none detected
Extensions
2
Audit depth
standard
Pages fetched
60
Pages rendered
20
Generated
2026-09-15T00:00:00.000Z
SEO58 / 100

coverage 72%

Exposure80 / 100

coverage 74%

Content90 / 100

coverage 84%

Performance98 / 100

coverage 86%

Accessibility94 / 100

coverage 100%

Platform95 / 100

coverage 86%

Content90 / 100 · coverage 84%

Content findings
SeverityConfidenceStatusFindingAffectedSourceEvidence
WarningCertainUnknownSampled items with no web-store image1 of the 13 sampled item(s) have no web-store image, so their product pages and every listing show the theme placeholder.1 item of 138%rule

Sampled items with no web-store image

1 of the 13 sampled item(s) have no web-store image, so their product pages and every listing show the theme placeholder.

Affected
1 item of 13
Attributed to
cause not attributed
Rule
catalog/no-image
Source
rule

Evidence (1)

  • Item 13 — hasImage = falsecatalog:item:13#hasImage

Fix

Item record › Web Store subtab › Item Images (the image folder per image type) — a content change

  1. Attach a detail image to each item, in the image type the theme reads.
  2. Check that the image folder is marked Available Without Login.
  3. Re-crawl and confirm the product page no longer renders the placeholder.
WarningCertainUnknownLanding pages with no meta description2 of the 83 CMS landing page(s) have no meta description, so their search snippets are taken from the page layout.site-wide—rule

Landing pages with no meta description

2 of the 83 CMS landing page(s) have no meta description, so their search snippets are taken from the page layout.

Affected
site-wide
Attributed to
cause not attributed
Rule
cms/landing-meta-missing
Source
rule

Evidence (2)

  • CMS page cms-draft — 8 fieldscms:cms-draft
  • CMS page cms-last — 8 fieldscms:cms-last

Fix

Site Management Tools › the page › Settings › Meta Description (per page), not the content editor — a content change

  1. Open each page’s settings panel and write a one-sentence description.
  2. Start with the campaign and guide pages that are linked from the navigation.
  3. Check the page title in the same panel while you are there.
  4. Re-crawl and confirm the description is in the served head.
WarningCertainUnknownSampled items with an empty Meta Tag HTML field1 of the 13 sampled item(s) have an empty Meta Tag HTML field, so their product pages carry no meta description.1 item of 138%rule

Sampled items with an empty Meta Tag HTML field

1 of the 13 sampled item(s) have an empty Meta Tag HTML field, so their product pages carry no meta description.

Affected
1 item of 13
Attributed to
cause not attributed
Rule
catalog/metataghtml-missing
Source
rule

Evidence (1)

  • Item 13 — hasMeta = falsecatalog:item:13#hasMeta

Fix

Item record › Web Store subtab › Meta Tag HTML — a content change

  1. Put a `<meta name="description" content="…">` tag in the field, one per item.
  2. Describe the product in a sentence a shopper would read in a search result.
  3. Mass-update the affected items rather than editing them one by one.
  4. Re-crawl and confirm the PDP head carries the description.
InfoLikelyUnknownOut-of-stock items the site still publishes1 out-of-stock item(s) are still published by the site, so search engines and shoppers keep arriving at a product that cannot be bought.1 item of 138%rule

Out-of-stock items the site still publishes

1 out-of-stock item(s) are still published by the site, so search engines and shoppers keep arriving at a product that cannot be bought.

Affected
1 item of 13
Attributed to
cause not attributed
Rule
catalog/oos-indexable
Source
rule

Evidence (1)

  • Item 13 — isInStock = falsecatalog:item:13#isInStock

Fix

Item record › Web Store subtab (Display in Web Store), or the theme’s out-of-stock product page behaviour — a content change

  1. Decide per item: keep the page and offer a back-in-stock signup, or take it down.
  2. To keep it, make the out-of-stock state and the alternative obvious on the page.
  3. To take it down, clear Display in Web Store so the item leaves the sitemap.
  4. Never leave a bought-out seasonal item published with no alternative offered.

Want this for your own storefront? See the plans, or verify a domain and take the free audit.