Rich results are enhanced Google Search presentations that may use eligible structured data and visible content; valid markup improves eligibility, never.
A rich result is a search presentation
A rich result is an enhanced presentation in Google Search that can use structured data and other page signals. It may show information such as product details, breadcrumbs or recipe properties. It is not a design component that a publisher can force into the results page.
Google distinguishes valid structured data from eligibility and from actual display. A page can pass the Rich Results Test yet not receive an enhancement, because appearance is chosen by Google and depends on the feature, query, device, country and broader quality conditions.
Choose a supported feature, not a generic schema type
Begin with the page type and the feature documentation. Product pages, recipe pages and breadcrumb paths have different requirements. Schema.org contains many types that are meaningful on the web but are not eligible for a Google rich-result feature; use Google’s feature guide as the decision source.
Map every property to visible content and a source field. If a review, price, image or availability cannot be shown accurately to a visitor, omit it. Markup should explain the published page, not describe what a search snippet might ideally show.
Validate at two stages
Validate a representative URL with the Rich Results Test while building the markup. After release, fetch or view the rendered page and inspect the delivered JSON-LD, because client rendering, caching, templates and feeds may alter production output. Check required properties, warnings, canonical URL and indexability together.
Then monitor the relevant Search Console enhancement report where one exists. Record the URL, implementation version, test date and status. Treat an error as an implementation issue to reproduce; treat the absence of a display as a measurement boundary rather than a failure to be hidden with extra properties.
Avoid rich-result promises
Correct markup can make a page eligible and help Google understand it, but Google explicitly does not guarantee a rich-result appearance. It also does not replace helpful content, a crawlable page or eligibility policies. Do not promise increased click-through rate or a particular visual treatment from schema alone.
A common error is adding every possible type to one page. Use the smallest accurate graph that represents the visible item and its relationships, and remove stale properties when an offer, review or template changes.