Public storefront evidence

See what the scan can actually check.

Your submitted page is checked first, followed by up to four discovered pages. Every supported finding points back to the affected public pages.

Start free scan Open a saved example

Your submitted page is firstIts path is kept. Up to four same-store pages may be discovered.

HomeProductCollectionArticleInformationOther

Page clarityTitle, heading, preferred URL

Image alternativesPublic image markup

Structured dataDeclared JSON-LD syntax

Public responseCompleted or unavailable request

Finding tied to exact affected pagesObservation, public URL, practical action, and limits stay together.

Private data stays outsideNo Admin, orders, customers, analytics, or private theme source

Up to five public pages total may be checked. Fewer pages may be available. Supported evidence does not establish overall storefront quality or private business outcomes.

Questions tied to proof

What each supported check can establish.

These focused checks are not a complete SEO, accessibility, content, or technical audit.

Can a sampled page clearly identify itself?

Public evidence: Page title, primary heading, and preferred public URL in retained HTML.
A supported result: Whether the sampled page exposes the supported identity signals.
Still unknown: Indexing, rankings, search demand, and pages outside the sample.

Do sampled images expose useful text alternatives for review?

Public evidence: Public image markup, missing alt attributes, and affected references.
A supported result: Whether sampled image elements expose reviewable alternative text.
Still unknown: The intent of every image and private theme or app configuration.

Can a declared machine-readable block be parsed?

Public evidence: Retained public JSON-LD and the declared value format.
A supported result: Whether the supported structured data can be parsed as written.
Still unknown: Rich-result eligibility, indexing, or which private source produced it.

Did a bounded public page request complete?

Public evidence: Public response status plus failed or unavailable request evidence.
A supported result: Whether the bounded request completed for that sampled page.
Still unknown: Private uptime systems, customer experience, and unsampled requests.

Only completed checks can support a finding. A skipped, failed, or unavailable check is not a pass.

Read the result correctly

Status and confidence do not grade the whole store.

Did it run?

Completion

Completed, failed, skipped, or unavailable.

How strong is the proof?

Confidence

How directly retained evidence supports the finding.

What does it mean overall?

Not a quality score

Neither status automatically describes the whole storefront.

Unavailable is not a pass, and confidence does not predict business impact.

Read the technical methodology

The methodology explains observation, scope, evidence coverage, confidence, limitations, formulas, and verification without turning missing data into a pass.

Open the methodology

The free scan gives you

Proof you can inspect and a next step you can use.

Prioritized findingsRetained public evidencePractical next actionsStated limitationsNo email requiredNo Shopify Admin access

Start free scan See the report first