Property Coverage Scorecard

Four property coverage examples

1. Product with name only: Paste a Product containing @type and name. The scorecard identifies which properties are present and which documented fields may be absent for the selected Google feature.
2. Product with Offer: Add a truthful Offer containing price and priceCurrency. Compare the score with the previous version, but remember that field presence alone cannot establish eligibility.
3. Article with author and dates: Inspect an Article containing a headline, author, and actual publication date. Check whether nested properties are recognized for the selected feature and whether the page displays matching information.
4. Multiple @graph entities: Paste an @graph with Organization, WebSite and Product nodes. Use the entity selector to inspect the intended entity rather than assuming every graph node has the same requirements.

Common mistakes and fixes

A high percentage does not mean Google will show a rich result. This tool compares against a dated, curated local catalogue, not the complete or live Google policy system. Do not add invented reviews, prices, availability or author identities just to improve a score. Do not treat recommended fields as universally required; rules vary by feature and can change. If the wrong entity is selected, switch the entity selector before drawing conclusions.

Review workflow: Confirm the feature, check the dated catalogue source and required/recommended field labels, inspect real on-page facts, and then test the published page with the Google Rich Results Test. A scorecard is a planning aid, not a certificate.