Rich snippet

A rich snippet is a search result with extra elements beyond the blue link and description. Think stars, price, breadcrumbs, FAQ toggles, or sitelinks search. For a small site, these can lift click through and show trust in the results you already win.

By , founder of Porteur · Updated 13 September 2026 · Markdown

What a rich snippet is and why it matters

A rich snippet is Google’s enhanced result pulled from structured data on your page. It can show price, rating, stock, FAQ questions, breadcrumbs, or a how to step.

For a small site, a single enhancement can change how your result looks against bigger rivals. It helps the right searcher qualify fast. It can raise clicks without new content.

Example: yourproduct.com/pricing with Product schema can show price and availability. The result is clearer than a plain snippet that hides key details in the meta description.

Which markup earns which rich result

Schema typeTypical elements shownGood pages to mark up
ProductPrice, rating, reviews, availability/pricing, /product/widget
Review or AggregateRatingStar rating, countCase studies, product pages with reviews
FAQPageExpandable Q and A/guides/getting-started, /support/billing
HowToSteps, time, toolsSetup guides, DIY instructions
BreadcrumbListBreadcrumb trailAll indexed pages
Article or BlogPostingLogo, date, headline/blog/post-title
EventDates, location, availabilityWebinars, launches
Organization or LocalBusinessLogo, social profilesHomepage, /about

How to add and test rich snippets

  1. Pick the search to improve

    Open Search Console, Performance. Filter to a target query like "pricing yourproduct" or "your niche software". Pick the landing page that already gets impressions.

  2. Choose the matching schema

    Map intent to type. Product for sale pages. FAQPage for support answers. HowTo for step by step guides. BreadcrumbList for navigation across the site.

  3. Add JSON LD

    Add JSON LD to the HTML of the page. Keep values identical to what users see. Match the on page price, rating and availability in the markup.

  4. Validate

    Use Google’s Rich Results Test to check eligibility. Fix all required fields. Resolve errors first, then warnings that matter for what you want to show.

  5. Ship and request indexing

    Ship to production. In Search Console, Inspect URL, Test live URL, then Request indexing.

A fixed page matches on page content and schema, passes the Rich Results Test, and shows no errors in Search Console’s Enhancements section once crawled.

How to measure impact

  • Search Console, Performance: compare 28 days before and after. Use the Search appearance filter for the specific rich result type when available.
  • Track clicks, CTR and average position for the marked page and its main queries. A lift in CTR at similar position is the signal you want.
  • Enhancements reports: watch for new valid items, and rising valid counts after deploys. Errors and drops often come from template changes or CMS updates.
  • Spot check the live result. Search your exact query in an incognito window. Do not rely on one view. Rich results appear by query and device.

Common traps to avoid

  • Marking up content that is not visible. Google can ignore or penalise mismatches.
  • Wrong type for the intent. Do not force FAQPage on a sales pitch. Put real questions and answers a user would read.
  • Copied boilerplate on every page. Duplicate FAQs or fake reviews reduce trust and can be removed from results.
  • Forgetting required fields. Each type has required and recommended properties. Miss the required ones and you are not eligible.
  • Assuming permanence. As of 2026, Google shows some rich results less often in some verticals. Expect variability and test over time.

Questions

Sources

Check my site, free

Want to see which pages on your site could earn rich results next, and why, from a URL in about thirty seconds for free? Run the check.

  • Free check, no card
  • Read-only, your own accounts
  • Readable by your agent

Read next