sciencePublic example report

Headless commerce rendered HTML drift example report

A public sample showing how rendered product facts can differ from source HTML, API payloads, and structured data on a custom storefront.

Scan your product pagearrow_forward Open Custom/headless scanner

52Audit score

High rendering drift risk

If the priority fixes were completed, this sample report would project a score range of 73-81.

Sample Context

What this example represents

This page demonstrates report output using desensitized fixture data. It is public and indexable, while private user reports stay under noindex `/report/*` URLs.

Example page

Fictional headless furniture product

Platform

Custom storefront with client-side hydration

Scan mode

Raw HTML versus rendered HTML comparison

Data boundary

Fictitious public sample, not a real merchant scan

Score Summary

The report starts with explainable score dimensions

The score is only useful when it points to the evidence and repair path behind the number.

Search visibility

Basic metadata exists, but rendered facts carry most of the product meaning.

Machine-readable facts

Several facts appear only after client-side rendering.

AI crawler access

Crawler access is possible, but raw-source fallback is weak.

Platform confidence

Hydration and client app data layer markers are visible.

Product Signal Matrix

Visible facts versus machine-readable facts

The sample separates what shoppers can see from what crawlers and AI shopping systems can reliably parse.

Visible

7/7

Structured

2/7

Product factVisibleMachine-readableEvidence source

Title

Arc Modular Desk

check_circleDetectedcheck_circleStructured

meta + rendered DOM

Description

Configurable workspace desk

check_circleDetectedradio_button_uncheckedRendered only

rendered DOM only

Price

$690.00

check_circleDetectedradio_button_uncheckedRendered only

hydrated client state

Brand

Gridline Demo

check_circleDetectedradio_button_uncheckedRendered only

rendered DOM only

Image

Rendered gallery image

check_circleDetectedcheck_circleStructured

Open Graph image

SKU

GL-DESK-DEMO

check_circleDetectedradio_button_uncheckedRendered only

client data layer

Structured data checks

This section audits product, offer, review, breadcrumb, and related structured signals without publishing product markup for the sample itself.

Pass

Warn

Fail

Product schema

The product is visible after rendering, but no reliable Product node is available in the rendered inventory.

errorFail

Visible product

Detected

Rendered DOM

Product node

Missing

Rendered JSON-LD

Offer schema

Price and availability depend on hydrated client state rather than durable structured data.

errorFail

Structured price

Missing

Product/Offer schema

Raw versus rendered facts

The raw HTML contains fewer product facts than the rendered page.

errorFail

Raw attributes

Title and image only

Raw HTML

Rendered attributes

7 product facts

Rendered HTML

Breadcrumb schema

Visible navigation exists, but no durable BreadcrumbList was detected.

warningWarning

BreadcrumbList

Missing

Rendered JSON-LD

Platform Diagnostics

Custom/headless specific findings

The platform section explains what the scanner would inspect for the storefront technology involved.

Pass

Warn

Fail

Server-rendered product facts

Important commerce facts depend on client-side rendering.

errorFail

CSR product detection

Detected

rendering comparison

Source versus rendered HTML drift

Raw HTML and rendered HTML expose materially different product facts.

errorFail

Structured drift

Detected

field source comparison

API data drift

The visible product page appears to rely on client payloads for price and SKU facts.

warningWarning

Visible-only fields

Price, brand, SKU

client app data layer

Crawler-readable product facts

Modern crawlers can render the page, but raw-source fallback remains too thin for confidence.

warningWarning

Raw attributes

Incomplete

Raw HTML

Priority Fixes

What the sample report would fix first

Each fix ties evidence to impact, recommendation, confidence, and expected score movement.

3 prioritized fixes

Fix 1criticalrendering

Server-render critical product facts

Impact

+11-16

Confidence

91%

Evidence

Price, brand, SKU, and category are visible only after client hydration in the sample report.

Impact

Crawlers or AI systems that rely on source HTML may miss the purchasable product facts.

Recommendation

Move critical product facts into the server-rendered HTML or static payload available before hydration.

Implementation target

Headless storefront SSR/SSG product detail template

Fix 2highschema

Generate structured product facts from the same source as visible content

Impact

+8-12

Confidence

87%

Evidence

Rendered product facts and structured data do not share one authoritative source.

Impact

Search engines may see one set of product facts while shoppers see another.

Recommendation

Use one product data adapter to feed visible page content and structured product fields.

Implementation target

Product data adapter and schema generation layer

Fix 3mediumnavigation

Add durable breadcrumb and category context

Impact

+4-7

Confidence

79%

Evidence

Visible navigation exists, but BreadcrumbList is not durable in rendered structured data.

Impact

Category context is weaker for search clustering and AI product comparisons.

Recommendation

Expose category path in both visible navigation and machine-readable breadcrumb data.

Implementation target

Headless route metadata and breadcrumb model

Run The Real Scan

Replace the fixture data with your product URL

A real ShopGox scan will inspect your rendered page, structured data, platform signals, crawler access, and priority fixes for the submitted URL.

Start a scanarrow_forward

FAQ

About this public example report

These questions are visible on the page, so the page can safely emit matching FAQPage structured data.

What is rendered HTML drift?

Rendered HTML drift means the final browser-rendered product page contains important facts that are missing or different in the raw source HTML.

Why does this matter for AI shopping agents?

Some crawlers render JavaScript well and others rely on earlier page states, so critical product facts should be durable and consistent.

Is this headless example connected to a real API?

No. The findings are static fixture data that demonstrate the type of report ShopGox can produce for a submitted URL.

More Examples

Compare another public report

Use these samples to see how the report changes by platform, crawler behavior, and schema risk.

Scan your pagearrow_forward

Shopify

Shopify Product Schema Audit Example Report

See a public ShopGox example report for a Shopify product page with visible product facts, schema gaps, platform diagnostics, and priority fixes.

Score 64arrow_forward

Magento

Magento AI Crawler Audit Example Report

Review a public ShopGox example report for a Magento product page covering AI crawler access, configurable product signals, localized schema, and priority fixes.

Score 58arrow_forward

WooCommerce

WooCommerce Product SEO Report Example

View a public WooCommerce product SEO example report showing plugin metadata, product schema, review signals, cache drift, and priority fixes.

Score 67arrow_forward