A search presentation enhanced with supported information, such as recipe details, star ratings, or product attributes. Valid markup does not guarantee display.

A rich result is a search presentation enhanced with supported information or visual elements beyond an ordinary text result. Depending on the feature, it may display details about a product, recipe or another eligible content type. The exact supported features and their requirements belong to the search engine’s documentation.

A page’s structured data can help establish eligibility for a supported feature, but validity alone does not guarantee display. Search systems also consider policies, relevance and the circumstances of the search. A general Schema.org type is not evidence that a corresponding Google rich-result format exists.

Separate implementation progress from search outcomes when reviewing an agency report. “Markup added,” “validation passed,” “eligible feature detected” and “feature observed in search” describe different stages. Clear reporting makes it easier to identify whether the remaining issue is technical, editorial or simply an expectation that was never guaranteed.

Takeaway: Choose a rich-result feature only when the page genuinely qualifies. Verify implementation and actual appearance separately, without promising stars or another display simply because markup was installed.

Example

A retailer adds supported product information and resolves validation errors. That is a technical improvement, but it does not establish that every search will show the product with the same enhanced display. The team records the valid implementation and monitors the actual results rather than calling the feature permanently secured.

What to check

Use the current feature guide and relevant testing tools. Keep values consistent with visible content and review policy requirements, not only missing-field messages. A warning, an error and an unobserved search enhancement are different findings and should not be reported interchangeably.

For more detail, see General structured data guidelines.