How to add the required property that this schema type expects?

jsonld-missing-required-property page

The issue

A JSON-LD object missing a property its type requires doesn’t earn the search result it was written for. A product with no name, or an event with no start date, is marked up and still ignored, and the page gives no sign of it.

The cause is that every schema.org type has properties it can’t do without. A search engine that finds one missing treats the entity as incomplete and won’t build a result from it.

Scope

Each object is checked against its own type, including objects nested inside others, such as the offers of a Product. A missing property on one object doesn’t affect the others.

How to check you have it

In probeo: the page reports Missing required property "<name>" for <Type>, naming the property and the type.
By hand: look up the type on schema.org or in Google’s structured data documentation and compare its required properties with what the block holds.
With a validator: Google’s Rich Results Test lists missing required fields for the result types it supports.

The fix

Add each required property with a real value from the page.

Take the value from what the page shows: the product’s name, the event’s date, the article’s headline.

Done when: every object carries the properties its type requires, and the check above comes back clean.

Do not

Do not fill a required property with a placeholder.
Do not count on recommended properties making up for a missing required one.
Do not give a property a value of the wrong kind, such as text where a date belongs.

FAQ

What distinguishes required properties from recommended properties?

Required properties must be present for rich result eligibility. Recommended properties enhance results but their absence does not cause validation failure or disqualification.

Can placeholder values satisfy required property requirements?

No. Values must accurately represent the entity. Placeholder or dummy values violate structured data guidelines and may result in manual actions or rich result removal.

How do required properties change when @type includes multiple types?

The union of all required properties from each type must be present. Multiple types increase requirements rather than offering alternatives.

What happens when required properties exist but contain incorrect data types?

Validators report type mismatch errors. A property expecting a URL but receiving plain text, or expecting a number but receiving a string, causes validation failure identical to missing properties.

Do all schema.org types have required properties?

No. Some generic types like Thing have no required properties. Most specific types like Product, Event, or Article have explicit requirements. Check schema.org documentation for each type.

Should all available properties be added even when not required?

Add properties when data is available and accurate. More properties provide more context but adding properties without accurate data introduces noise rather than clarity.

Which product detects this

Probeo checks this on every page of your site as part of Site Clarity. This page explains one instance; the product tells you every page that has it.