appsSEO Tools
radarProduct Schema Checker

Free Product Schema Checker for Ecommerce Pages

Compare Product and Offer JSON-LD with the price, currency, stock and review evidence on one public product page. See which facts disagree and where to investigate before changing your markup.

check_circleProduct and Offer JSON-LD
check_circlePrice, currency, and availability
check_circleReal review and rating evidence
check_circleVisible vs structured product facts
System Ready
link

No login or app installation required. Reads your public page without changing your store.

From a schema warning to a verifiable fix

Scan one public product detail URL. Compare the captured page with its structured data before editing your store. A score is not a prediction of rankings, traffic or AI citations.

Does the offer match the page?

Evidence to compare
Compare rendered price and currency with Product → offers and the reported field sources.
Where to investigate and verify
Check the product data source, then the theme or schema plugin that emits Offer. Recheck the same currency and variant after clearing relevant caches.

Is there actual review evidence?

Evidence to compare
Compare visible reviews or ratings with Review/AggregateRating. A review form and its five-star options are not feedback.
Where to investigate and verify
Inspect the review provider and schema emitter. If no ratings exist, do not add invented ratingValue or reviewCount fields.

Do multiple blocks disagree?

Evidence to compare
Check entity IDs, names, URLs, prices and stock before treating multiple JSON-LD blocks as a conflict.
Where to investigate and verify
Trace contradictory values to the template or plugin. Linked nodes can be valid; verify the final output again after the change.

Free shows discovery evidence. Copyable implementation examples, export and history comparison follow the existing plan permissions. ShopGox does not edit your store.

Check current requirements in Google’s Product documentation and review guidelines.

Audit Coverage

What This Tool Checks

Product Schema

Detect whether Product markup is present and whether fields such as name, image, brand, SKU, GTIN or MPN, category, and variant attributes describe the same item shoppers see.

Offer Signals

Compare extracted price, priceCurrency, availability and offer URL with the rendered page. Check selected variants and markets separately: one URL scan is a snapshot, not an interactive test of every variation.

Structured Data Consistency

Catch contradictions between rendered HTML, title, H1, metadata, canonical tags, breadcrumbs, review widgets, and JSON-LD blocks that can lower trust in the page.

AI Search Readiness

Review whether the page exposes enough explicit product attributes, merchant facts, and schema alignment for AI answer systems to parse and compare the item.

Schema Entity Map

Product schema examples this checker separates

A strong ecommerce product page does not treat structured data as one generic JSON-LD blob. It separates the product entity, the sellable offer, authentic review signals, and the breadcrumb path so search engines can reconcile the page with Merchant Center, snippets, and shopping surfaces.

Product entity fields

The Product entity should describe the item itself, not the category page, collection page, or marketing campaign around it.

Example signals

Product: name, image[], description, brand, sku, gtin/mpn, category

What to verify

  • check_circleProduct name and image match the visible product page.
  • check_circleBrand, SKU, GTIN, or MPN are present when the store has them.
  • check_circleVariant attributes such as color, size, material, and model are not hidden in vague copy.

Offer and merchant listing data

Offer markup should describe what a shopper can actually buy on this URL, including price, currency, availability, condition, and the canonical product URL.

Example signals

Offer: price, priceCurrency, availability, itemCondition, url, priceValidUntil

What to verify

  • check_circlePrice and priceCurrency match the rendered page and selected market.
  • check_circleAvailability is current and not contradicted by sold-out or preorder messaging.
  • check_circleOffer URL resolves to the same canonical product page Google can crawl.

Review and AggregateRating signals

Review markup is only useful when it represents genuine reviews that are visible to shoppers and consistent with the review widget or platform data.

Example signals

AggregateRating: ratingValue, reviewCount; Review: author, reviewBody, datePublished

What to verify

  • check_circleRatings are shown on the page, not only injected into hidden schema.
  • check_circlereviewCount and ratingValue match the visible review summary.
  • check_circleMultiple review apps are not outputting conflicting aggregateRating values.

BreadcrumbList context

Breadcrumb schema helps crawlers understand where the product sits in the catalog and prevents category context from being inferred incorrectly.

Example signals

BreadcrumbList: Home > Collection > Product with position values and item URLs

What to verify

  • check_circleBreadcrumb names match the visible navigation path.
  • check_circleEach breadcrumb item has a crawlable URL and a stable position value.
  • check_circleBreadcrumbs do not point to filtered or temporary collection URLs by mistake.

Common Blockers

Issues Worth Fixing First

priority_high

Missing or thin Product markup

The page shows product information to shoppers, but JSON-LD leaves out core entity fields such as brand, SKU, images, category, or identifiers.

priority_high

Broken Offer details

Price, currency, availability, condition, or Offer URL fields are missing, stale, or inconsistent with the rendered product page and selected market.

priority_high

Duplicate JSON-LD blocks

Themes, SEO apps, review apps, and tag managers can inject multiple Product, Offer, Review, or BreadcrumbList blocks that disagree.

priority_high

Weak product attributes

Important comparison attributes like material, size, color, compatibility, model, variant, shipping, returns, or inventory signals are absent or too vague.

Workflow

From URL to Fix Plan

01

Paste a product URL

Use the public product page shoppers and crawlers can access, not a preview, cart, or admin URL.

02

Scan the rendered page

ShopGox checks the final product page output, including schema, metadata, content clarity, and crawler-facing signals.

03

Prioritize fixes

Use the report to decide whether the fix belongs in content, theme templates, schema apps, or platform settings.

FAQ

Questions Before You Scan

Is this only a JSON-LD validator?
expand_more
No. Generic validators check whether markup is syntactically valid. ShopGox also compares Product, Offer, Review, AggregateRating, BreadcrumbList, metadata, and visible product content so you can find contradictions that syntax validators miss.
Which schema types matter most on an ecommerce product page?
expand_more
For a sellable product page, start with Product and Offer. Then review BreadcrumbList, Review or AggregateRating when reviews are visible, and merchant listing fields such as price, availability, shipping, and return policy when your store can provide them accurately.
What fields are most often missing from product schema?
expand_more
The common gaps are brand, SKU, GTIN or MPN, image arrays, priceCurrency, availability, canonical URL, variant attributes, and review counts that match the visible review widget.
Should I add Review schema if my product has no visible reviews?
expand_more
No. Review and AggregateRating markup should reflect reviews that shoppers can see on the page. Adding hidden or unsupported ratings can create trust problems and structured data eligibility issues.
Does clean Product schema guarantee rich results?
expand_more
No. Clean structured data improves the inputs search engines can evaluate, but rich results still depend on eligibility, crawlability, policy compliance, page quality, and Google's own display decisions.
How is this different from Google's Rich Results Test?
expand_more
Use Google’s Rich Results Test to check supported rich-result markup, then use ShopGox to compare extracted structured data with visible product facts and inspect potential conflicts. Neither a valid test nor a ShopGox score guarantees Google will display a rich result.