Check explainer · v1

Product markup: prices must match the visible page

Automated

Last reviewed

A price in structured data that the page never shows is a mismatch — the exact pattern price-abuse spam uses. The check compares every marked price against the page’s visible text.

How this check works

Product and ProductGroup markup is read for offer prices, and each distinct price value is searched for in the page’s visible text. A price that never appears in the content fails; pages without product markup, or markup without price values, are not judged. Variant grouping is graded separately: ProductGroup containers are checked for name, hasVariant, a shared group ID and per-variant identifiers — not for price consistency.

What does a failure look like?

A sale updates the visible price but the JSON-LD keeps the old one; a currency or thousand-separator difference (€1.299,00 versus 1299.00) makes the value unfindable; regional price tests where the markup was cached from another variant.

How to fix it, step by step

  1. Render the price from the same source that feeds the markup, so one update moves both.
  2. Watch formatting: separators and currency symbols must match what the page actually prints.
  3. Re-run the check after price changes and after template edits that touch either the offer block or the visible price element.

What does a pass or fail look like?

Good

2 marked prices (19.90, 449.00) each found in the visible content — markup and page agree.

Fail

The offer block marks 249.00 but the page displays €199.00 after a sale — the marked price is not in the visible text.

Frequently asked questions

Why compare markup prices against visible text?

Because a price that exists only in markup is how price-abuse spam qualifies for rich results. Google requires the displayed price to match the structured-data price; the check applies the same rule mechanically.

Does the check verify stock or shipping data?

No. It grades price consistency only — availability, shipping and returns are separate requirements in Google’s merchant listing documentation and are not judged here.

Do non-commerce pages fail for missing Product markup?

No. Pages without Product or ProductGroup markup are not judged — absence is na, not a failure. Only shipped product markup is graded.

How are product variants judged?

As a separate structure check: a ProductGroup needs name, at least one hasVariant Product, a shared group ID (productGroupID, or inProductGroupWithID on each variant) and sku, gtin or mpn on every variant. The price comparison on this page runs independently of that structure.

This rule is one of the checks the audit runs. Run the full site audit

Free preview; no account needed.

Visdenda check explainers · one page per published ruleProduct markup · v1