en
/login
Koval SEO

A marked-up price has no matching static page price

In the reportMarked-up price has no qualified static content match

structured_data_price_not_visible · Review item

Short answer

We could read one current-page Product and one unrestricted Offer price, but found no qualified matching price in the initial HTML main content. Check the actual price and currency before changing the page. This is a static review signal; it does not confirm a policy violation or what a rendered browser shows.

Severity: Medium. Review the intended price and currency when you next work on this product page.

Why it matters

Google requires structured data to represent the page content. An old or hidden marked-up price can describe a different offer from the one visitors see. Our static comparison helps locate a possible discrepancy; it does not establish a manual action.

What to do

  1. Compare the finding’s raw price, currency, product and offer sources with the current offer on the page.
  2. Correct the markup to describe that offer, or show the intended current price in the initial page content. Preserve its currency and eligibility conditions.
  3. Run a full audit after publishing the change. If the price appears only after JavaScript or depends on membership or quantity, inspect that behaviour separately.

When to leave it as it is: Leave the page as it is if the reported price is correctly presented in rendered content and you have checked that the markup describes the same offer. You can hide this optional review item.

What we read

Complete original HTML 200 responses that are indexable, server-classified and have one unique main, role=main or article region. We read the original JSON-LD, Microdata or RDFa graph and full bounded known-visible main text, excluding hidden, inert and inline-style-hidden text.

One Product explicitly associated with this page and one Offer. Direct Offer.price takes precedence; when absent, one unrestricted UnitPriceSpecification may supply the scalar price and currency. An unresolved or contradictory association is not a checked price.

Exact amounts with supported decimal and grouping forms and explicit currency codes or unambiguous euro/pound symbols. A positive match comes from visible text of the actual price property in the same Product and effective Offer/specification, or an unambiguous local product-name/price label. Reviews, unrelated products, shipping, member, unit and previous prices do not supply that proof.

Example & evidence

Illustrative same-product price correction, not a live audit.

Page: https://shop.example/lamp/
Product.url: https://shop.example/lamp/
Product.name: Lamp
Offer.price: 19.00
Offer.priceCurrency: USD
<main><h1>Lamp</h1><p>The lamp description.</p></main>
The same Product and Offer:
<main><h1>Lamp</h1><p>Lamp USD 19.00</p></main>

Confirm & check again

Check for yourself: View the initial response and the rendered product page. Compare the current offer, amount, currency and eligibility conditions with the source markup; use Google’s Rich Results Test for eligibility separately.

Check again: Full audit — Run a full audit. A complete supported same-page price comparison can clear the finding. Removing the Product, Offer, price, main region or source coverage does not prove a fix.

Limits & sources

This check does not execute JavaScript or measure external CSS. Its initial-HTML absence is not proof of rendered absence.

Scheduled, member, quantity, tax, billing, compound or unit restrictions without supported exact proof remain unverified. PreOrder or PreSale alone does not invalidate the price.

Unclear currency, a bare amount, signed expressions, ambiguous dollar symbols, a lone 1,234 or unsupported formats remain unverified; no locale or currency conversion is guessed. A matching number beside an unsupported local currency marker, or even an unrelated count, conservatively blocks an absence finding.

Incomplete captures, unknown context, multiple subjects, hidden or ambiguous roots and resource limits cannot prove a fix.

Confidence: Low Low: a bounded static heuristic with high false-positive risk, not rendered confirmation.

Sources

  • Google, General structured data guidelines — Structured data should represent relevant content available to users; our supported static comparison is a product heuristic. Checked 7 October 2026.

Editorial review: 2 November 2026