How do rich results work?
Rich results usually depend on structured data: machine-readable markup, most often JSON-LD using the schema.org vocabulary, that describes what a page contains. A product page can declare its name, price, currency, availability and review rating; a recipe can declare its ingredients and cooking time; an event can declare a date and venue. Google lists the types it supports in its Search Central documentation, along with the required and recommended properties for each.
Valid markup makes a page eligible, but it does not guarantee a rich result. Google decides whether to show one based on the query, the page and its own guidelines, and it has reduced or retired some rich result types over time. Google's Rich Results Test and the reports in Search Console show whether your markup is valid and which enhancements Google detected on your pages.
Why do rich results matter?
A listing with stars, a price or an image takes up more space and gives searchers more information to judge before they click. That can make it stand out against plain listings around it, and it can also answer part of the question directly on the results page. Whether it brings more visits to a given page is something to measure on your own data, for example by comparing click-through rate in Search Console before and after Google starts showing the enhancement.
Can you collect rich result data with an API?
BestSERP's web search returns each organic result with position, title, link, snippet, displayedLink, source, domain and favicon. Those are the fields: there is no separate field for review stars or other enhancements on organic results today, so it is not a tool for auditing which competitors show stars in the web results.
Structured product and business data is available from other endpoints, though. /shopping returns products with price, priceValue, rating and delivery, and /places returns businesses with rating and ratingCount. For price monitoring or review tracking, those are often more direct sources than the enhancements on a web listing, because the values arrive as separate fields you can store and compare.
Example
Product structured data in JSON-LD that can make a page eligible for price and rating enhancements.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Burr Grinder",
"offers": {
"@type": "Offer",
"price": "129.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"reviewCount": "87"
}
}
</script>