sciencePublic example report

Magento AI crawler audit example report

A sample report for a configurable product where crawler access, store-view metadata, and parent-child product signals affect AI shopping readiness.

58Audit score

Crawler-readable, but structurally incomplete

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

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 configurable electronics product

Platform

Magento catalog page with store views

Scan mode

Crawler access plus rendered structured-data 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

62

Canonical and title signals exist, but localized metadata is inconsistent.

Machine-readable facts

44

Parent product and selected variant facts are not aligned.

AI crawler access

71

Googlebot is clear, but AI crawler policy is only partially confirmable.

Platform confidence

91

Magento runtime, catalog, and asset signals are present.

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

4/7

Title

AeroTab Pro 11

check_circleDetectedcheck_circleStructured

JSON-LD + rendered DOM

Description

Configurable tablet bundle

check_circleDetectedcheck_circleStructured

meta description

Price

$499.00

check_circleDetectedradio_button_uncheckedRendered only

rendered DOM only

Brand

Helio Demo

check_circleDetectedradio_button_uncheckedRendered only

visible product detail

Image

Gallery hero image

check_circleDetectedcheck_circleStructured

Product JSON-LD

SKU

HTAB-DEMO-11

check_circleDetectedradio_button_uncheckedRendered only

selected variant DOM

Category

Tablets

check_circleDetectedcheck_circleStructured

BreadcrumbList

Schema Deep Dive

Structured data checks

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

Pass

1

Warn

2

Fail

1

Product schema

Product schema exists, but selected variant facts are not clearly represented.

warningWarning

Product node

Detected

Rendered JSON-LD

Variant SKU

Missing

Product schema

Offer schema

Structured Offer values do not match the visible selected configuration.

errorFail

Visible price

$499.00

Rendered DOM

Structured price

Not verified

Product/Offer schema

Localized schema

Store-view language and currency signals need stronger alignment.

warningWarning

Store view

Detected

Magento runtime

Currency

Visible only

Rendered DOM

Breadcrumb schema

Category path is available in visible and machine-readable form.

check_circlePass

BreadcrumbList

Present

Rendered JSON-LD

Platform Diagnostics

Magento specific findings

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

Pass

0

Warn

3

Fail

1

Configurable product schema

The parent product is visible, but selected child product facts are incomplete.

warningWarning

Parent-child signals

Partial

Magento catalog markup

Store-view metadata drift

Rendered language, canonical, and currency signals do not fully agree across the store view.

errorFail

Locale signals

Drift detected

Rendered HTML

Canonical and localized schema

Canonical is present, but localized schema values should match the page language and currency.

warningWarning

Canonical

Present

link rel=canonical

Layered navigation risk

Parameterized catalog URLs may create duplicate crawl paths without careful canonical control.

warningWarning

Scanned URL

Parameterized examples detected

URL inspection

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 1highplatform

Tie selected variant price and SKU to structured product output

Impact

+9-13

Confidence

89%

Evidence

Visible selected variant price and SKU are not reliably reflected in machine-readable product fields.

Impact

AI crawlers may summarize the parent product without the active purchasable variant.

Recommendation

Ensure the structured product layer receives the same selected child product data shown in the Magento PDP.

Implementation target

Magento configurable product template and schema extension

Fix 2highinternational SEO

Normalize store-view language, currency, and canonical signals

Impact

+7-11

Confidence

85%

Evidence

The sample report finds store-view metadata drift between rendered page signals.

Impact

Search engines may struggle to cluster localized product variants correctly.

Recommendation

Audit each store view so canonical, hreflang, currency, and structured data agree with the visible page.

Implementation target

Magento store-view metadata and localized schema configuration

Fix 3mediumcrawler access

Clarify AI crawler access policy for public product pages

Impact

+4-6

Confidence

78%

Evidence

Googlebot access is clear, but AI crawler access is only partially confirmable from page-level signals.

Impact

AI answer engines may avoid using product content if crawler access is ambiguous.

Recommendation

Review robots policy and sitemap coverage for public product pages and important catalog paths.

Implementation target

robots.txt, sitemap, and product URL crawl policy

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.

Why does the Magento example focus on crawler access?

Magento stores often combine configurable products, store views, and catalog parameters, so crawler-readable product facts need explicit verification.

Is the sample product data real?

No. Product names, prices, and platform findings are fixture data created for a public example report.

Can ShopGox test localized Magento store views?

A real scan can inspect the rendered page, canonical, hreflang, currency, schema, and crawler signals visible on the submitted URL.