Why the product page matters more than the feed
In real stores, failures often look like this: the feed is “correct”, but the product page (or structured data) communicates something else.
When price and stock are dynamic, when variants don’t update markup, or when two plugins output Product JSON-LD, contradictions show up.
Those contradictions are a fast path to disapprovals (and sometimes broader trust issues).
What Google compares
- Feed attributes (price, availability, shipping, identifiers).
- Visible content (what the user sees).
- Structured data (what the page declares to machines).
Most common breakpoints
- Variants (size/color/memory) not updating price/stock.
- Caching/CDN serving stale values.
- Duplicated Product/Offer JSON-LD.
Practical rule: stabilize your product page + policies first, then refine the feed.
Price & promotions: consistency and edge cases
- Visible price: must match structured data Offer price and (when applicable) your feed price.
- Sale pricing: avoid “ghost discounts” (UI shows a struck-through price but markup remains unchanged, or vice versa).
- Currency: currency switchers and geo-pricing are mismatch machines. Use one stable rule and apply it consistently to page + feed + markup.
- Taxes/fees: be explicit about VAT/taxes included, and ensure final checkout totals don’t contradict the product page.
- Shipping costs: if shipping materially changes the final total, make the logic clear and consistent with your shipping policy page.
Quick test (2 minutes)
Open the product page in incognito, refresh, switch variants (if any), refresh again.
Repeat from a second browser or network (to catch cache/CDN differences).
If you can reproduce different prices for the same URL, you have a stability issue.
Availability & variants: avoiding contradictions
The classic scenario: the page says “In stock”, but structured data says “OutOfStock” — or stock is correct only for one variant.
Variants are where many stores break consistency.
- Variant selection: switching variants must update price, images and availability consistently.
- Preorder/backorder: if you allow it, label it clearly and align the availability message (and structured data).
- Out-of-stock behavior: if a variant is unavailable, the UI should make it obvious (disable selection, show “sold out”).
- Bundles/configurators: ensure the “final” price is stable and readable on the product page (not only at the last step).
If one URL represents multiple variants, you must ensure that the “current selected offer” is consistently represented (UI + markup).
Trust signals: what must be obvious before checkout
Trust is built with “micro-certainties”. A buyer (and a reviewer) should find the essentials without effort:
returns/refunds, shipping, warranty, and how to contact support.
Near the buy button
- Estimated delivery time (or shipping window).
- Return policy link + 1-line summary.
- Warranty/support link + 1-line summary.
In the info section
- Condition (especially if refurbished/used).
- Included / not included accessories.
- Policies for defects/DOA and support process.
Reviewer shortcut
If it takes effort to find returns/shipping/contact pages, risk increases.
Surface the essentials on product pages and ensure footer links are consistent site-wide.
Content & images: “invisible” mistakes that cost approvals
- Images with heavy watermarks, promo overlays, or accessories shown but not included without a clear note.
- Generic descriptions that feel like dropshipping or don’t match the actual product configuration.
- Aggressive claims (“best in the world”, “full warranty”) without conditions or policy references.
- Fake-looking reviews or reviews that can’t be verified (few real reviews beat many suspicious ones).
- Hidden conditions only revealed at checkout (fees, exclusions, restrictions).
Clarity beats persuasion. Especially for sensitive categories and refurbished products.
schema.org Product/Offer: what to verify (for real)
Structured data helps when it is consistent. It hurts when it is duplicated or contradictory.
Your goal is not “more markup” — it’s “one truthful markup”.
- Single main Product: avoid multiple Product entities with conflicting Offer values.
- Offer.price & currency: must match the visible price logic (taxes/currency rule).
- Offer.availability: must match the UI and the real inventory state.
- Identifiers: brand + SKU/GTIN (when applicable) should be consistent and stable.
- Dynamic pricing via JS: if UI changes but JSON-LD stays static, you create mismatches.
Most common markup failure
SEO plugin + ecommerce plugin + theme each output their own Product JSON-LD.
You end up with 2–3 Offers with different price/availability.
Fix duplication before changing feed values.
Final checklist (30 checks)
Price & promos
- Visible price = structured data Offer price.
- Sale price logic is correct (no inverted strike-through).
- Single currency or a clear geo-pricing rule.
- No price embedded in images.
- Price stable across cache/CDN tests.
- Taxes/VAT logic is consistent with checkout totals.
- No hidden fees discovered only at checkout.
Stock & variants
- Availability message matches reality.
- Offer.availability matches the UI.
- Variant selection updates price/stock.
- Out-of-stock variants are clearly shown/disabled.
- Preorder/backorder is explicitly labeled.
- Bundles/configurators show a stable final price.
- Product URL represents the correct offer/variant.
Trust signals
- Shipping info visible (cost/time or link + summary).
- Returns/refunds visible (link + summary).
- Warranty/support visible (link + summary).
- Support contact is reachable and works.
- Condition is explicit (new/used/refurbished).
- Included/not included accessories declared.
- No misleading photos (accessories, bundles, variants).
- Checkout flow is not opaque or confusing.
Schema Product/Offer
- No duplicated Product entities with conflicts.
- Offer price/currency reflect visible logic.
- Offer availability reflects UI + inventory.
- Brand is consistent.
- SKU/GTIN present when applicable.
- Variant behavior doesn’t leave stale JSON-LD.
- No conflicting markup from multiple plugins.
- Canonical URL is correct and stable.
Want a product-page checklist for your store?
Generate a free report: trust signals, policy visibility, price/stock consistency and a baseline structured-data check — in ~60 seconds.
No credit card · Audit ~60s · Shareable link