Audit Product structured data
Inspect raw HTML for Product and Offer properties on an ecommerce product-detail page.
PDP SEO Checker
Free, no signup. Structurally check the primary Product or ProductGroup, selected offer, buy-box price, currency, availability URL and variant graph. JavaScript-only buy boxes and product feeds are not evaluated.
Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Sample report Deterministic detector example
HTML containing one Product, one USD Offer with price 10, https://schema.org/InStock, and a $10 price beside “Buy now” returns:
Product graph: 1 Product · 0 ProductGroup · 1 Offer. Primary entity: Product.
Primary offer: 10 USD with a valid currency code.
Availability: Valid Schema.org availability URL.
Buy-box consistency: Primary schema price matches the buy-box price.
How to use it
- Enter the canonical product detail page and select Audit.
- Review the Product, offer-price, availability, and consistency rows separately.
- Confirm a mismatch against source HTML and the selected variant before editing.
- Run a complete structured-data and merchant-feed validation afterward.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
What the results mean
- Product graph — totals for Product, ProductGroup and Offer entities, plus the structurally selected primary entity.
- Primary offer — a positive price and recognized ISO 4217
priceCurrencyon the primary product’s offer. - Availability — a recognized Schema.org ItemAvailability URL, not merely an
availabilityproperty. - Buy-box consistency — the selected schema price matches a non-placeholder price found near the product purchase action.
- Variant graph — unusually large variant sets and multiple competing top-level products are called out.
How it works
The protected endpoint supplies public raw HTML. The detector parses JSON-LD as JSON, walks typed entities and linked offers, ranks Product and ProductGroup candidates using page URL, graph position and offer evidence, then searches the bounded buy-box region around the purchase action. Cart totals, financing examples, placeholders and zero prices are excluded.
Features
- Structural JSON-LD parsing rather than regular-expression extraction.
- Product, ProductGroup and Offer totals.
- Primary/selected product and offer identification.
- Currency and Schema.org availability-URL validation.
- Buy-box-scoped price comparison with noisy-price exclusions.
- Variant-entity and competing-primary warnings.
Limitations
The primary-entity and buy-box selection are deterministic heuristics, not access to the store’s internal selected-variant state. The tool does not render JavaScript or inspect Merchant Center, feeds, reviews, shipping, returns, stock truth, or checkout behavior. Confirm warnings against the rendered selected variant before changing production markup.
Frequently asked questions
What does the PDP SEO Checker audit?
It structurally parses every JSON-LD block and Product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. graph, identifies the best primary Product or ProductGroup candidate, validates its selected offer, and compares that non-zero schema price with a price found inside the product buy box.
Does it validate Product rich-result eligibility?
No. It does not cover every required or recommended Product and Offer property or Google policy. Use a full schema validator after this focused consistency check.
Why is price consistency not evaluated?
The detector needs both a usable non-zero price on the primary schema offer and a recognizable price in the raw-HTML buy-box region. Cart totals, financing examples, placeholders, and $0.00 values are ignored.
Can it check JavaScript-rendered buy boxes?
No. The fetch audit reads raw HTML and may miss prices, variants, or availability inserted only after scripts run.
Does it check Merchant Center or product feeds?
No. Feed approval, shipping, returns, variants, identifiers, and Merchant Center diagnostics are separate from this page audit.
Feature requests for Pdp Seo Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Check price consistency
Compare visible and structured prices to find mismatches that need merchandising or template review.
Verify availability signals
Review whether visible stock language and schema availability agree for the fetched page.
Preflight a PDP template change
Test a representative product before rolling a markup, price, or availability update across the catalog.
Watch the full workflow
PDP SEO Checker walkthrough
Read the transcript
PDP SEO Checker
Product detail pages can expose conflicting products, offers, prices, currencies, availability, or variants. This focused audit parses the raw-H-T-M-L product graph, selects a primary product and offer, and compares its non-zero schema price with the buy box. I’ll show the workflow, each finding, limitations, and the production checks to complete next.
Step 1
Use this checker before a product template launch, after schema or pricing changes, or when the visible selected variant appears inconsistent with Product structured data. It evaluates one public product page at a time.
Step 2
Use the canonical public P-D-P for the specific product or product family. The protected endpoint retrieves public raw H-T-M-L, so JavaScript-only buy boxes and variant state may be absent.
Step 3
This walkthrough enters a fictional store dot example product U-R-L and does not make a live fetch. In normal use, select Audit and interpret each finding independently rather than treating one passing row as an overall verdict.
Step 4
This clearly marked fictional report demonstrates five separate findings. Review the selected primary entity and offer before acting on a mismatch; competing top-level products or unusual variant graphs can change which evidence matters.
Step 5
The graph row totals Product, ProductGroup, and Offer entities and identifies the structurally selected primary candidate. Confirm that candidate represents the visible product before editing markup.
Step 6
The primary offer needs a usable non-zero price and a recognized three-letter I-S-O currency code. Placeholders, zero values, financing examples, and unrelated totals are deliberately excluded.
Step 7
Availability passes only for a recognized Schema dot org ItemAvailability U-R-L, not merely any availability property or free-form stock text. Confirm the value matches actual inventory behavior.
Step 8
The detector searches a bounded region near the purchase action for a non-placeholder price and compares it with the primary offer. A mismatch needs confirmation against the rendered selected variant.
Step 9
Unusually large variant sets and multiple plausible top-level products are called out because they can make primary selection ambiguous. Inspect linked variants, page U-R-Ls, and offer ownership directly.
Step 10
When a fetch is truncated or required document evidence is unavailable, observed positives may remain useful, but absence and clean-page claims are not evaluated. Inspect the raw source and rendered page directly.
Step 11
The tool does not render JavaScript or inspect Merchant Center, product feeds, reviews, shipping, returns, inventory truth, or checkout. Primary-entity and buy-box selection are heuristics, so confirm warnings against the rendered selected variant.
Step 12
After confirming the selected entity and fixing real inconsistencies, run a complete structured-data validator, compare the rendered buy box, inspect each variant, verify feed values and Merchant Center diagnostics, and test the actual purchase path.
Confirm every warning against the selected rendered variant.
Resolve confirmed graph, offer, availability, or price conflicts in the authoritative product template. Then validate the complete Product markup, selected variant, rendered buy box, Merchant Center feed, shipping and returns data, stock truth, and checkout behavior. This focused consistency audit is evidence for review, not a rich-result or feed-approval guarantee.
Common issues & how to fix them
- Warning Product schema is missing Fix: Add Product JSON-LD that accurately identifies the visible product and its current offer.
- Warning Offer price is missing from schema Fix: Add the current numeric price and currency to the Product offer and keep them synchronized with visible content.
- Warning Availability is missing from schema Fix: Add the correct schema.org availability URL to the Offer and match the visible stock state.
- Warning Schema and visible prices disagree Fix: Make the visible price, Product JSON-LD, and offer currency represent the same current purchasable offer.