Need deeper analysis? See the related editorial article for background and trade-offs. Use this guide for the practical steps.
Google expects structured data to describe what readers can actually find on the page. A lightweight local comparison can flag missing product names and surprising prices, but it is a clue rather than proof.
Use this checklist alongside the local checker. Every step is free and can be repeated without an account or daily quota. Only approve corrections that reflect the real page. Where Google eligibility matters, follow the linked official documentation rather than treating a local result as certification.
Step 1: Why visible content matters
Compare product name, description and price against the content supplied in the same HTML file before assessing rich-result eligibility.
Look for: A valid Product object can describe a different item from the visible page. That mismatch is not fixed by adding more schema properties.
Example: A page titled Blue Jacket should not advertise a schema name for an unrelated laptop.
Keep in mind: Do not use structured data to claim unavailable inventory or fabricated ratings.
Step 2: Extract only meaningful page text
Remove non-content blocks before searching for visible names and prices, but describe the remaining result as an approximate text extraction.
Look for: HTML contains scripts, styles, templates and markup that do not represent the visible reading experience. A raw string search can give false confidence.
Example: A product name appearing only inside an unrelated JavaScript variable should not count as clear visible evidence.
Keep in mind: CSS, hydration and client-side rendering can still change what users actually see.
Step 3: Review price formatting
Treat a textual mismatch as a prompt for human review and inspect currency, variants, quantities, taxation and the selected offer.
Look for: Schema pricing may use 1499.00 while the page displays Rs 1,499 or a discounted amount. Naive exact matching can report false positives.
Example: Compare 1,499.00 PKR with a markup price of 1499.00 and confirm they represent the same real offer.
Keep in mind: Do not automatically change commercial values because a string search failed.
Step 4: Handle variants and multiple offers
Review the Product and Offer relationship and the HTML around the selected variant; use appropriate schema for the actual product configuration.
Look for: A page may legitimately show several sizes, colors, package options or seller offers. A single price field may not summarize them all.
Example: A shoe page can show different prices for sizes while an AggregateOffer summarizes a range.
Keep in mind: A simplified local tool cannot infer inventory policy or variant selection.
Step 5: Check claims about reviews and ratings
Make sure reviews come from real, relevant content and conform to Google feature restrictions before adding structured ratings.
Look for: Ratings are especially sensitive because markup can look convincing even when no supporting reviews appear on the page.
Example: A product with no user reviews should not acquire an invented AggregateRating purely to satisfy a validator.
Keep in mind: Never generate reviews from generic text or a fabricated score.
Step 6: Understand limitations of pasted HTML
Clearly label local text matching as a heuristic and recommend a rendered-page inspection for final confirmation.
Look for: An uploaded HTML file is a snapshot, not a complete browser session. It may lack CSS, JavaScript execution, linked data or content loaded from an API.
Example: A React app can render product details after hydration even when its initial HTML body has little readable content.
Keep in mind: Do not call missing local HTML content a proven Google policy violation.
Final review checklist
Recheck syntax and warnings after editing, compare the corrected file against the original, export a report, and validate applicable features using official tools. If a result is unclear, keep the original data instead of guessing business facts.
Official sources: Google documentation and additional reference. For more detail, read the complete article.
Frequently asked questions
Answers are educational. FAQ markup does not guarantee Google FAQ rich results.
Can static HTML prove what users see?
Not always. Client-side rendering and product variants can change visible content.
What should I do with a possible price mismatch?
Inspect the actual rendered page and selected variant before changing markup.
