Auditing a product page against its structured data
Compare visible product price, currency and availability with the structured offer on the same page, including regional promotions and member pricing.

A shopper sees the product page. A search system may also read embedded product data. If a price changes in one representation before the other, a merchant can publish two answers to the same question.
Inspect the same response
Choose one public product page you manage. Record its visible price, currency, availability, seller and variant. Inspect the structured product offer from that same observation. Avoid comparing yesterday’s raw HTML with today’s rendered price. If location changes the offer, repeat the check from an approved regional session and record the destination URL. Google Search merchant listing documentation.
Assign the fix to the right layer
A matching price with a different currency points to localization. A stale availability state on both the page and markup points back toward the feed. A mismatch limited to structured data belongs with the publishing template. Use XtremeProxy when the question involves a regional view. Fixing the underlying offer record will often solve more pages than adjusting individual tags.
For example, a details page may advertise a sale price of 80 while its embedded offer still says 100 in the same currency. Check whether the sale applies to a loyalty member, a time-limited promotion or every visitor. The correct public structured value depends on the offer actually represented.
Two versions of the same offer
A signed-out visit shows a lamp at 42 dollars. The offer embedded in the same response declares 39 dollars, and a separate data feed has already moved to 42. Check that the embedded value names the same variant and seller before reporting a mismatch. On an owned staging copy, publish a coordinated update and retrieve the rendered page and its underlying document again. This isolates an outdated markup template from a visible price that changed while the report was running.
Match the offer scope
A product group can legitimately display a range while one selected variant has a single amount. Determine whether the markup describes the group, a specific offer or several sellers. Extract both the declared scope and the shopper's selected scope. A discrepancy that vanishes after aligning them belongs in the matching rules.
A product page may describe several offers in one structured record. Follow the offer identifier, currency and selected seller for the rendered variant rather than comparing the first numeric price found in the document. An aggregate minimum can be accurate while differing from the individual offer the customer selected.
Review price and stock independently
A markup revision corrects the selected variant's amount but leaves its availability field tied to the parent group. Run the two checks independently using one in-stock and one unavailable variant. A page can be correct on price and wrong on availability. Report those outcomes separately so a publishing fix in one field does not prematurely close both issues.
Separate the markup delivered in the original response from markup inserted after the page runs. On an owned product page, save the original structured record and inspect the rendered record after selecting a specific variant. Give each observation the same timestamp window and release identifier. If the original document describes the default blue item and the rendered record still describes blue after the visible page switches to green, the variant update handler becomes a narrower place to investigate than the catalogue feed.
Check when the observed markup was created. On a configurable item the delivered HTML may describe the default variant, while the browser later renders another selection from a client-side response. Save both the original HTML offer and the rendered offer after selecting the test variant. Compare each with the visible price and availability at that same point in the sequence. This gives a developer two concrete places to investigate, including whether a stale script still describes a color that the shopper can no longer buy.
Related fieldwork
After a template correction, check the requested product, one sibling variant and an unavailable option. Each should keep its own identifier and correct availability. Product image revision checks supplies a parallel review for images using product revisions. For a selected option that repeatedly changes under the collector, Matching color and size variants in a digital shelf audit follows the matching problem from the shopper's side. Review XtremeProxy plans and allowances.
Frequently asked questions
Is a successful structured-data validation enough?
A validator can confirm that a price field has an acceptable shape. Compare its currency, amount, availability and variant against the purchasable offer to establish whether the content is accurate.


