Rich results that still exist: how to earn them
Google retired many rich results. These are the ones that still show, the schema each one needs, and how to add JSON-LD without breaking your site.
Most of the rich results people still chase no longer exist. Google retired HowTo results, retired FAQ results after narrowing them to a handful of institutional sites, and dropped the sitelinks search box entirely. What still earns visible space in the results is a much shorter list — products, reviews, breadcrumbs, video, recipes, events, job postings and local business details — and each one needs a specific schema type to qualify. You can build the JSON-LD for the common ones with the structured data generator in a couple of minutes. The rule that governs all of it: markup buys eligibility, not the result itself.
What Google retired, and when
The last few years have been a steady contraction of search features, not an expansion. Three changes account for most of the confusion in old SEO checklists:
- FAQ rich results (August 2023 and May 2026). Narrowed in 2023 to well-known, authoritative government and health websites and, since May 7, 2026, no longer shown in Google Search. In 2023 Google said existing
FAQPagemarkup causes no problems, but it has no visible effect. - HowTo rich results (2023). Removed outright. The type still validates, but it produces no visual treatment in Google search.
- Sitelinks search box (late 2024). Retired: Google removed its documentation in November 2024 because the feature is no longer available. Any
WebSite+SearchActionmarkup written for it is now dead weight in a lot of templates.
If a guide tells you to add FAQ schema to "take up more SERP space" or to add a SearchAction block, it was written before these changes and the rest of its advice deserves the same suspicion. Meanwhile, the additions have been narrow and vertical-specific, such as discussion forum and profile page markup for community sites, and some types have gone the other way: in September 2025 Google removed the documentation for course info, estimated salary, learning video, special announcement and vehicle listing because they no longer show in results. Useful if you run that kind of site, irrelevant otherwise.
The rich results that still show
Sorted roughly by how much visible payoff they deliver for the effort.
Product snippets — Product with Offer
Price, currency, availability and aggregate rating can appear directly under your result. This is the highest-value markup left, and also the most policed. The price in the JSON-LD must match the price the visitor sees (Google's general guidelines ask for exactly that), the currency must be explicit, and ratings must come from real reviews that are visible on the page.
Review snippets — AggregateRating or Review
The star rating shown next to products, recipes, books, software and local businesses. It cannot be self-serving: a business rating its own products, or a rating stored in markup but nowhere in the HTML, is exactly what the structured data spam policies target.
Breadcrumbs — BreadcrumbList
Replaces the raw URL in the result with a readable path. Low effort, near-universal support, no downside. It also nudges you into keeping a consistent URL hierarchy, which pairs with writing clean, readable slugs in the first place.
Video — VideoObject
Thumbnail, duration and key moments in the results and in the Video tab. Worth it if video is genuinely part of the page rather than a decorative embed.
Recipes, events and job postings
Three verticals where the rich result is still strong and, in the case of events and job postings, where the markup is effectively the entry ticket to a dedicated search experience. Highly specific: if you do not publish recipes, events or jobs, skip them.
Local business — LocalBusiness
Name, address, phone, opening hours and geo coordinates. It rarely produces a dramatic snippet on its own, but it reinforces entity consistency across your site, your Business Profile and third-party citations. The details must match everywhere — a mismatched address does more damage than no markup at all.
Article — Article / NewsArticle
Google lists it in its rich results gallery, but its documentation says no markup is required to be eligible for features like Top stories. What Article does is state the title, the author and the last-modified date in a form machines do not have to guess at. Cheap to add, sensible to keep.
Eligibility is not a guarantee
This is the part most guides skip. Valid markup means your page qualifies for a feature, and Google does not guarantee that it will show. Whether the feature actually renders depends on the query, the device, the quality of the page and Google's own judgement — and it can appear one week and vanish the next without anything changing on your side.
So treat a missing rich result as a maybe, not a bug. Validate the markup, confirm eligibility in the Rich Results Test, then stop tuning. The same logic applies one layer up: Google frequently rewrites the title and description it shows, which you can sanity-check with a SERP preview tool before you publish, but never fully control.
Adding JSON-LD without breaking anything
JSON-LD lives in its own script block. It can sit in the <head> or the <body>, and it never touches your visible HTML — which is precisely why it survives redesigns that shred microdata attributes:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "The exact product name on the page",
"image": "https://example.com/product.jpg",
"offers": {
"@type": "Offer",
"price": "49.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
}
</script>Four rules cover almost every mistake worth avoiding:
- One block per entity. Separate scripts for Article, BreadcrumbList and Organization are easier to debug than one giant object, and you can remove one without touching the others.
- Never mark up what the visitor cannot see. Hidden prices, ratings and Q&A are the fastest route to a manual action.
- ISO 8601 dates, absolute URLs, canonical host. If your canonical uses
www, so should every URL inside the markup. - Generate it from your data. Hand-written JSON-LD goes stale the moment a price or a date changes. If your CMS can populate it, let it.
One prerequisite that gets skipped: none of this matters if the page cannot be crawled. Check that robots.txt is not blocking the path and that the URL appears in your XML sitemap before you spend an afternoon on schema.
What is not worth marking up
- HowTo, if you are starting from zero and targeting Google.
- WebSite + SearchAction for the sitelinks search box — the feature is gone.
- Deep type hierarchies nobody consumes. There is no bonus for using the most specific subtype available.
- Boilerplate
Organizationrepeated on 5,000 pages with identical values. Once, on the pages where it means something, is enough.
Validate in two places
The Rich Results Test answers "is this page eligible for a Google feature?". The Schema Markup Validator at schema.org answers "is this valid schema?", including types Google ignores. After publishing, Search Console's rich result status reports are the only source that reflects what Google actually parsed on crawled pages — warnings mean missing recommended properties and do not block eligibility; errors do.
Frequently asked questions
Does structured data improve rankings?
It is not a ranking factor. Structured data makes a page eligible for specific search features and describes the page in a machine-readable way. A thin page does not rank better because it has JSON-LD, but a good page can win more space in the results.
Why did my FAQ rich result disappear?
Google narrowed FAQ rich results in August 2023 so they only showed for well-known, authoritative government and health sites, and since May 7, 2026 it no longer shows them at all. Nothing is broken in your markup; the feature is gone. In 2023 Google said existing FAQPage markup causes no problems, it just has no visible effect.
Is HowTo schema worth adding in 2026?
Not if your goal is a visible search feature. Google retired HowTo rich results in 2023 and they no longer appear. The vocabulary is still valid and other consumers may read it, so keeping existing markup costs nothing, but adding it from scratch for Google visibility will not pay off.
How long until a rich result appears after I add markup?
Google has to recrawl and reprocess the page first, which can take days or weeks depending on how often the URL is crawled. Requesting indexing in Search Console can speed up the first check. If the page is eligible and the feature still does not show after several weeks, the likely answer is that Google chose not to display it for that query.
Can invalid markup hurt my site?
Syntax errors mostly just make you ineligible for the feature. What genuinely hurts is marking up content the visitor cannot see, such as prices, ratings or reviews that are not on the page. That breaks Google's structured data guidelines and can trigger a manual action, under which the page loses eligibility for rich results while its ranking in web search stays the same.
Which validator should I use?
Use both, because they answer different questions. Google's Rich Results Test tells you whether the page qualifies for a Google search feature. The Schema Markup Validator at schema.org checks syntax and vocabulary even for types Google does not support. After publishing, the Search Console enhancement reports show real errors on crawled pages.
Generate your JSON-LD now
Fill in a form, copy the block, paste it in. Runs entirely in your browser.
Open Schema generator →Related tools
- Schema markup generator — JSON-LD for Article, FAQPage, Product, LocalBusiness and HowTo.
- Meta tag generator — Title, description and Open Graph for the same page.
- SERP preview — See where your title and description get truncated.
- XML sitemap generator — Make sure the page you marked up can be found.
You might also like: free SEO tools that do not ask for your data.
Sources
Reviewed on October 13, 2026.
- Google Search Central, introduction to structured data: JSON-LD recommended, the three valid formats, the Rich Results Test and the Search Console rich result status reports (accessed October 13, 2026).
- Google Search Central, general structured data guidelines: do not mark up content readers cannot see, or fake reviews; a structured data manual action removes a page's eligibility, not its ranking; Google does not guarantee that markup will show (accessed October 13, 2026).
- Google Search Central, Article structured data: no markup is required for Top stories, and
datePublishedanddateModifieduse ISO 8601 (accessed October 13, 2026). - Google Search Central, search features gallery: the structured data types Google documents today, including Article, Product, Local business and Breadcrumb (accessed October 13, 2026).
- Google Search Central, documentation updates: the FAQ rich result stops showing on May 7, 2026 and its documentation is removed on June 15, 2026; sitelinks search box documentation removed in November 2024; course info, estimated salary, learning video, special announcement and vehicle listing removed in September 2025; HowTo documentation removed in September 2023 (accessed October 13, 2026).
- Google Search Central Blog, changes to HowTo and FAQ rich results (August 8, 2023, updated September 14, 2023): FAQ only for well-known government and health sites, HowTo no longer shown, and unused markup causes no problems (accessed October 13, 2026).
- Google Rich Results Test: checks whether a page is eligible for Google search features (accessed October 13, 2026).
- Schema Markup Validator: validates schema.org markup even for types Google does not use (accessed October 13, 2026).