What’s a “missing recommended” warning, do I need to fix it?

Schema.org marks each property as either required (must have for the type to be valid), recommended (improves rich-result eligibility), or optional (nice-to-have). The validator reports them in three buckets:

  • Errors, missing required, wrong datatype, invalid enum value. These block rich-result eligibility. Fix immediately.
  • Warnings, deprecated property, suspicious value, non-canonical @context URL. Worth fixing but won’t block rich results.
  • Missing recommended, the property is allowed-but-absent. Google’s eligibility rules treat each missing recommended as a soft penalty against your rich-result score.

You don’t need to fix every “missing recommended” to be eligible, but the more you have, the better your chances. For Product specifically: sku, mpn, gtin13, brand, aggregateRating, and review are the high-value ones, adding them moves you from “eligible” to “competitively eligible” for Merchant Listings.

For Article: author, publisher, image at multiple aspect ratios (1:1, 4:3, 16:9), dateModified, and articleSection. Add these and your Top Stories eligibility climbs.

The validator’s 0-100 score weights required-property completeness 60%, recommended-property completeness 30%, and warning count 10%. Fix every error to get to ~60. Add the high-value recommended properties to climb past 85 (rich-result eligible).

Kishan Savaliya
Kishan Savaliya
Adobe Certified Magento Commerce Developer
Ahmedabad [IN]working hours, replies within four hours
When do you need it

Read personally. Never shared. Or email the brief.

More on magento schema validator

Need it fixed, not just explained?

Send the brief with your store URL; the written quote comes back within 24 hours.