What Are Rich Snippets, Exactly?
A rich snippet is a search result that shows more than a title, URL, and description. Star ratings under a recipe, a price and stock status next to a product, a video thumbnail with a play button, a breadcrumb trail instead of a raw URL — all of these are rich snippets, and all of them come from the same source: structured data, usually written as schema.org markup in JSON-LD format on the page.
The mechanism is simple. You add a script to your page that describes, in a machine-readable format, what the page actually is — a recipe with a rating of 4.6 from 210 reviews, a product priced at ₹2,499 and in stock, a video that's 8 minutes long. Google reads that markup and, if it's eligible, may choose to display some of those facts directly in the search result.
That word "may" is doing a lot of work, and it's the part most explanations skip. Adding schema markup makes a page eligible for a rich result. It does not guarantee one. Google's own documentation is explicit that eligibility depends on the markup being valid, matching the visible content on the page, and meeting quality guidelines — and even then, display is Google's discretion, not an automatic outcome of adding code.
A rich snippet (also called a rich result) is an enhanced search listing generated from structured data markup on a page. It adds visible information — ratings, price, images, steps — beyond a standard blue-link result. It is a display feature, not a ranking mechanism.
Do Rich Snippets Directly Improve Rankings?
Here's the answer most SEO content dances around: no, not directly. Google has said this plainly and repeatedly — structured data and the rich results it enables are not a ranking factor. A page with immaculate schema markup does not outrank an otherwise-identical page without it. The mechanism simply doesn't work that way.
What structured data can influence is what happens once a page is already ranking. If your listing shows a 4.8-star rating and a competitor's doesn't, at the same position, more of the people scanning that page of results are likely to click yours. That's a click-through rate effect, not a ranking effect — and click-through rate is a genuinely different thing from rank.
Where it gets more nuanced: there's long-standing, reasonable debate in the SEO community about whether sustained CTR at a given position can indirectly influence a page's performance over time, since search engines do observe user behaviour signals in various ways. Google has not confirmed CTR as a direct ranking input, and has pushed back on the idea that "just get more clicks" is a reliable ranking tactic. The honest position is: the direct effect of rich snippets is on visibility and clicks, not rank — any downstream ranking effect, if it exists, is indirect and unconfirmed.
"Add schema and you'll rank higher" is not an accurate claim, and treating it as one leads to disappointment and wasted priority. The accurate claim is: "Add schema and, if it's eligible for a rich result, you may get more clicks at your current position." That's still valuable — just not the mechanism most people assume.
Plain Result vs Rich Result — What Changes
Since the effect is on the listing itself rather than its position, it helps to be precise about exactly what changes and what doesn't.
| Dimension | Plain Result | Rich Result |
|---|---|---|
| Ranking position | Determined by normal ranking factors | Unchanged — schema is not a ranking input |
| Visual space on the SERP | Title, URL, description only | Additional space for stars, price, images, or steps |
| Information visible pre-click | Whatever fits in the meta description | Concrete facts — rating, price, availability, duration |
| Effect on click-through rate | Baseline for that position | Often higher, for schema types Google actively displays |
| Implementation effort | None | Low to moderate — JSON-LD markup matching visible content |
| Reliance risk | None — nothing to lose | Google can restrict or retire eligibility at any time, as it has done before |
| Should you still implement it? | Yes, for schema types with genuine content behind them — treat the rich result as a bonus, not the reason the content exists. | |
"Structured data doesn't get you to the top of the page. It just gives you a better shot at the click once you're already there."
— Codos Technology Technical SEO Framework, 2026The Schema Types Still Worth Implementing
Not all structured data produces a visible result, and among the types that do, some matter far more than others depending on what your site actually is. Here are the schema types most worth the implementation effort right now.
The common thread across every schema type that still works is that it describes something concrete and genuinely present on the page — a real rating, a real price, a real video. Schema that describes content the page doesn't actually have, just to chase a rich result, is exactly what Google's guidelines are designed to catch.
What Google Has Quietly Retired
Two schema types deserve a specific, current callout, because a lot of SEO advice still floating around online is out of date on this point.
Google restricted FAQ rich results to well-known government and health sites back in August 2023, and on 7 May 2026, retired FAQ rich results from Google Search entirely. FAQPage remains a valid schema.org type and the markup causes no harm if left on a page — but it no longer produces any visible rich result for any site, in any category. If you're implementing FAQ schema specifically to chase a Google SERP feature, that feature no longer exists.
HowTo rich results were limited to desktop only in August 2023, then removed from desktop as well shortly after. As of 2026, HowTo structured data produces no visible rich result on any surface in Google Search. Like FAQPage, it remains valid schema.org markup — it just doesn't do what it used to.
None of this means FAQ or HowTo content is worthless — a genuinely useful FAQ section still helps human readers, and well-structured Q&A content is still readable by other crawlers, including those behind AI systems that cite web sources. What's gone is specifically the Google SERP dropdown. Keep FAQPage schema only where it accurately reflects real, visible FAQ content on the page and is cheap to maintain — not because it will earn you a rich result, because it won't.
How to Start — 6 Steps to Add Rich Snippets
Implementing structured data well is less about covering every schema type and more about matching the right type to what your page genuinely is. Here's the order we'd actually work through it.
Audit What You Already Have
Before adding anything, find out what's already on your pages and whether it's actually working.
- Run key pages through Google's Rich Results Test to check current eligibility
- Check Search Console's Enhancements reports for existing structured data and any errors
- Note anything that used to produce a rich result but no longer does — especially FAQ and HowTo markup
This baseline tells you what to fix versus what to build from scratch.
Match Schema Type to Actual Content — Not Aspiration
Pick schema based on what the page genuinely is, not what rich result looks appealing.
- Product pages with real prices and stock status → Product schema
- Pages with genuine, verifiable customer reviews → Review/AggregateRating schema
- Pages where video is the primary content → VideoObject schema
Schema describing content that isn't visibly on the page is a guideline violation, not a shortcut.
Implement Organization or LocalBusiness Schema Sitewide
This is the one type worth adding everywhere, regardless of page type, as a baseline layer.
- Business name, logo, address, contact details, and social profiles
- Keep it identical to how you're described elsewhere — Google Business Profile, directories, social bios
- This feeds knowledge panels and local search features, not just individual result listings
Low effort, low risk, and it doesn't depend on any single rich-result feature staying available.
Add Breadcrumb Schema for Navigation Clarity
Replaces a raw URL string in the result with a clean navigation trail, and costs almost nothing to implement.
- Mirror your actual site navigation structure — don't invent a hierarchy that doesn't exist
- Straightforward to automate site-wide through most CMS platforms
Minor visual improvement, but consistent and low-maintenance once set up.
Retire or Skip FAQ and HowTo Schema Built Solely for Rich Results
If FAQ or HowTo markup exists purely to chase a Google SERP feature, that feature is gone — reconsider the effort spent maintaining it.
- Keep FAQPage schema only where it reflects genuinely useful, visible FAQ content for readers
- Don't invest new effort building HowTo markup expecting a visible Google result — it won't appear
Redirect that effort toward schema types that still produce a visible outcome.
Validate, Then Monitor Monthly
Structured data errors are common and often invisible until checked directly.
- Validate new markup with the Rich Results Test before publishing
- Check Search Console's Enhancements reports monthly for new errors or warnings
- Re-check eligibility periodically — Google has changed rich result policies before and will again
Structured data isn't a one-time task — it needs the same light ongoing maintenance as any other technical SEO element.
Not sure which schema types actually apply to your site?
We'll check what's currently implemented, what's producing real rich results versus dead weight, and what to prioritise first — based on your actual pages, not a generic checklist.
💬 WhatsApp Us for a Free Schema Audit →Schema Priorities — Ranked
Structured data effort should follow impact, not completeness. Here's the priority order based on what actually produces a visible result today.
Tier 1 — Implement First (Clear, Durable Impact)
Tier 2 — Worth Adding (Moderate, Reliable Impact)
Tier 3 — Situational (Only If It Genuinely Applies)
How to Measure the Impact
Since the effect of structured data is on click-through rate rather than ranking, measuring it correctly means looking at the right metric — not checking whether a page's position moved.
Ways to Actually Measure Rich Snippet Impact
Search Console — Search Appearance filter. The Performance report lets you filter by search appearance type, including specific rich result categories. Compare click-through rate for pages with a given rich result against similar pages without one, at comparable positions.
Before/after CTR on the same page. When you add schema to an existing page, note the CTR for the weeks before and after implementation, at a similar average position. This isolates the effect of the rich result from unrelated ranking movement.
Rich Results Test and URL Inspection. Confirm eligibility directly — don't assume markup is working just because it validates. A page can have technically valid schema and still not display a rich result, for reasons ranging from quality guidelines to Google's own discretion.
Enhancements reports for error tracking. Search Console flags structured data errors and warnings by type. A rich result that stops appearing is often explained by an error introduced in a recent page update, not a policy change.
A page that gains a genuine rich result — a real star rating or product price — typically sees a visible CTR increase at the same ranking position within a few weeks, once the result starts displaying consistently. If ranking position hasn't changed but CTR has, that's exactly the effect structured data is supposed to produce.