Search visibility
62Canonical and title signals exist, but localized metadata is inconsistent.
A sample report for a configurable product where crawler access, store-view metadata, and parent-child product signals affect AI shopping readiness.
If the priority fixes were completed, this sample report would project a score range of 76-83.
Sample Context
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 score is only useful when it points to the evidence and repair path behind the number.
Canonical and title signals exist, but localized metadata is inconsistent.
Parent product and selected variant facts are not aligned.
Googlebot is clear, but AI crawler policy is only partially confirmable.
Magento runtime, catalog, and asset signals are present.
Product Signal Matrix
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
JSON-LD + rendered DOM
Description
Configurable tablet bundle
meta description
Price
$499.00
rendered DOM only
Brand
Helio Demo
visible product detail
Image
Gallery hero image
Product JSON-LD
SKU
HTAB-DEMO-11
selected variant DOM
Category
Tablets
BreadcrumbList
Schema Deep Dive
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 exists, but selected variant facts are not clearly represented.
Product node
Detected
Rendered JSON-LD
Variant SKU
Missing
Product schema
Structured Offer values do not match the visible selected configuration.
Visible price
$499.00
Rendered DOM
Structured price
Not verified
Product/Offer schema
Store-view language and currency signals need stronger alignment.
Store view
Detected
Magento runtime
Currency
Visible only
Rendered DOM
Category path is available in visible and machine-readable form.
BreadcrumbList
Present
Rendered JSON-LD
Platform Diagnostics
The platform section explains what the scanner would inspect for the storefront technology involved.
Pass
0
Warn
3
Fail
1
The parent product is visible, but selected child product facts are incomplete.
Parent-child signals
Partial
Magento catalog markup
Rendered language, canonical, and currency signals do not fully agree across the store view.
Locale signals
Drift detected
Rendered HTML
Canonical is present, but localized schema values should match the page language and currency.
Canonical
Present
link rel=canonical
Parameterized catalog URLs may create duplicate crawl paths without careful canonical control.
Scanned URL
Parameterized examples detected
URL inspection
Priority Fixes
Each fix ties evidence to impact, recommendation, confidence, and expected score movement.
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
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
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
A real ShopGox scan will inspect your rendered page, structured data, platform signals, crawler access, and priority fixes for the submitted URL.
FAQ
These questions are visible on the page, so the page can safely emit matching FAQPage structured data.
Magento stores often combine configurable products, store views, and catalog parameters, so crawler-readable product facts need explicit verification.
No. Product names, prices, and platform findings are fixture data created for a public example report.
A real scan can inspect the rendered page, canonical, hreflang, currency, schema, and crawler signals visible on the submitted URL.
More Examples
Use these samples to see how the report changes by platform, crawler behavior, and schema risk.
Shopify
See a public ShopGox example report for a Shopify product page with visible product facts, schema gaps, platform diagnostics, and priority fixes.
WooCommerce
View a public WooCommerce product SEO example report showing plugin metadata, product schema, review signals, cache drift, and priority fixes.
Custom/headless
Explore a public ShopGox example report for a headless commerce product page where rendered HTML, source HTML, API data, and crawler-readable facts drift.