How do required and recommended structured data properties differ?

Definition: A required property is a field that Google's guide for a specific structured data feature lists as necessary for eligibility. A recommended property is an applicable field that can add useful detail, while its absence is handled by the requirements for that feature.

Key facts

• Google's introduction to structured data separates properties into required, recommended, and optional categories for structured data with meaning to Google Search.
• Google says an object must include all required properties to be eligible for an enhanced display in Search. Its general guidelines say an item missing a required property is not eligible for the relevant rich result.
• Google's introduction advises supplying fewer recommended properties that are complete and accurate rather than every possible recommended property with incomplete, badly formed, or inaccurate data.
• In Google's Article structured data guide, there are no required properties. The guide says dateModified and datePublished are only recommended when applicable, so the Rich Results Test does not show a warning for either field when it is omitted.

What makes a property required?

Google Search Central uses the Google feature documentation as the authority for Google Search behavior, even though most Search structured data uses the Schema.org vocabulary. The required fields therefore come from the guide for the particular rich result type, rather than from a general assumption about every property defined by Schema.org.

The requirement is about eligibility for that feature. Google's general structured data guidelines state that site owners should specify every required property listed for the relevant rich result type. An item missing one of those properties is ineligible for rich results. The same guidelines still require the markup to represent the page accurately and to describe content visible to readers.

What happens when recommended properties are missing?

Recommended properties describe information that applies to the page and can make a result more useful. Google says that adding more recommended properties can improve the quality of a result, with extra information considered in rich result ranking. This guidance is separate from the required-property condition.

The Article guide illustrates how a feature can work with recommended fields alone. It tells publishers to include as many applicable recommended properties as possible, then says there are no required properties for Article objects. It also identifies dateModified and datePublished as optional recommendations when those dates are applicable, and says the Rich Results Test does not warn about either property.

Incomplete data still matters when a recommended property is supplied. Google's introduction says that fewer complete and accurate recommended properties are more important than trying to provide every possible property with less complete, badly formed, or inaccurate data. The result is a quality and accuracy decision, not a reason to fill fields with guesses.

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "Recipe",
  "name": "Non-Alcoholic Piña Colada"
}
</script>

How should you check the distinction?

Start with the feature guide and identify which fields it marks as required and which it marks as recommended. Google's Article implementation steps say to validate the code with the Rich Results Test and fix critical errors. The guide describes non-critical issues as potentially useful for improving structured data quality, while they are not necessary for rich result eligibility.

After deployment, Google recommends the URL Inspection tool to check how it sees a page. The page must remain accessible to Google, without an access block from robots.txt, a noindex tag, or login requirements. The general guidelines add that quality rules are difficult for automated tools to test, so a passing syntax check does not replace checking whether the fields accurately describe visible page content.

Related terms

• Structured data
• Article structured data
• Can structured data replace visible page content?
• How do I test a URL or code snippet with Google's Rich Results Test?

FAQ

Can a page be eligible when recommended properties are missing?

Yes, where the feature guide has no required properties and the remaining conditions are met. Google's Article guide gives this treatment for Article objects and says the Rich Results Test does not warn about omitted dateModified or datePublished when each is only applicable as a recommendation.

Should you add every recommended property?

Prioritize the recommended fields that apply and that you can populate completely and accurately. Google's structured data introduction specifically prefers fewer complete and accurate recommended properties over a larger set of incomplete or inaccurate fields.

Does a valid required-property set make a rich result appear?

It makes the object eligible for the relevant feature when the other guidelines are satisfied. Google's general guidelines state that correct markup enables a feature, while the final search presentation depends on Google's systems and the search context.

Sources

1. Google Search Central, "Introduction to structured data markup in Google Search", updated 10 December 2025
2. Google Search Central, "General structured data guidelines", updated 10 July 2026
3. Google Search Central, "Article (Article, NewsArticle, BlogPosting) structured data", updated 8 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer