How rich snippets work
Rich snippet was the phrase Google used for an ordinary search listing shown with extra detail pulled from structured data on the page: a star rating beneath a review, a price and availability beneath a product, a photograph and cooking time beneath a recipe. The mechanism has not changed. You describe the page in schema.org vocabulary, usually as JSON-LD, and Google may use that description to display more than a title, a URL and a line of text.
What changed is the name. As the display formats multiplied well beyond a couple of extra lines under a blue link — carousels, image tiles, whole panels — the word snippet stopped describing them, and Google’s documentation and tools settled on rich result instead. The tool many people still call the rich snippet tester is now the Rich Results Test. When someone uses either phrase today, they almost always mean the same thing.
Why rich snippets matter
Terminology sounds trivial until it costs money. A proposal, audit template or training course that still talks about rich snippets was usually written when the guidance was different, and the advice attached to it may be out of date in ways that matter: self-serving review stars, question markup on every page, or types Google has since stopped displaying.
Knowing the older name also helps you read the good material. Plenty of accurate technical writing predates the change, and dismissing it over vocabulary would throw away useful explanation. The name tells you roughly when something was written, which is a useful thing to know before you act on it.
Where rich snippet goes wrong
The commonest confusion is between a rich snippet and a featured snippet. They sound alike and are unrelated. A rich snippet is your normal listing decorated with data you supplied; a featured snippet is a passage Google lifts from a page and shows at the top of the results to answer a question directly. One you influence with markup, the other with clear writing.
The second problem is treating the phrase as a service. “Rich snippets” as a line on an invoice usually means adding structured data, which is worth doing when it describes the page truthfully — but eligibility has never been a guarantee of display, whatever the item on the invoice is called.
What to do about it
Use the current name when briefing anyone, so you and your supplier are reading the same documentation. When you meet the old term, check the date of the source and confirm any specific instruction against Google’s current guidance before following it.
Practically, the work itself is unchanged. Describe your pages accurately with markup that matches what a visitor can see, test the important templates, and watch the enhancement reports in Search Console for errors across the site. Judge the result by whether clicks on the affected pages improve, not by how many types you have installed — that is the honest measure of any schema markup work. And if a supplier promises a specific appearance in results, whether stars, prices or images, in exchange for markup alone, treat it as a sign the advice is old, because eligibility and display have never been the same thing.
