Skip to content

Deprecated rich results: should you remove the old schema?

Which structured data rich results Google retired, from HowTo and sitelinks search box to FAQ and the 2025 batch, and whether to keep or remove the markup.

By Crawlito · 6 min read

In short

  • Google removed the HowTo rich result in September 2023, the sitelinks search box in November 2024 and FAQ rich results from Search on May 7, 2026.
  • In 2025 Google phased out course info, ClaimReview, estimated salary, learning video, special announcement and vehicle listing results, then announced the end of practice problem and dataset results.
  • Google said the 2025 removals do not affect how pages are ranked, and that use of these types outside Google Search is not affected.
  • Once a rich result is retired, Search Console stops reporting on it, so leftover markup errors go unnoticed unless you audit the HTML yourself.
  • Keep markup that accurately describes visible content and is valid; remove markup that is wrong, invisible on the page or no longer maintained.
On this page

Google has retired a long list of rich results since 2023: HowTo, the sitelinks search box, FAQ, and a 2025 batch that included course info, ClaimReview, estimated salary, learning video, special announcement, vehicle listing, practice problems and datasets. The markup behind them is still valid schema.org, and Google has said the 2025 changes do not affect ranking. So there is no urgent reason to strip it out. Keep markup that is accurate and matches what the page shows, and remove anything that is wrong, hidden or unmaintained, because nobody at Google is checking it for you any more.

Below is the list with dates and sources, how to find leftover markup on your site, and a simple rule for each type.

Which rich results Google has retired

All dates come from Google's Search Central documentation updates page and the posts it links to. Check it for anything newer than this article.

FeatureWhat changedWhen
HowToRich result no longer shown on desktop or mobile; documentation removedSeptember 14, 2023
FAQLimited to well-known, authoritative government and health sitesAugust 2023
Sitelinks search boxDocumentation removed; feature no longer available in SearchNovember 29, 2024
Home activityDocumentation removed; feature no longer shownJune 11, 2024
Special announcementDeprecated from July 31, 2025Announced April 23, 2025
Book actions, course info, ClaimReview, estimated salary, learning video, special announcement, vehicle listingAnnounced as being phased outJune 12, 2025
Course info, estimated salary, learning video, special announcement, vehicle listingDocumentation removed; no longer shownSeptember 9, 2025
Practice problem, datasetAnnounced as being phased out of Search resultsNovember 5, 2025
Practice problemDocumentation removed; no longer shownJanuary 6, 2026
FAQNo longer shown in Search from May 7, 2026; documentation removed June 15, 20262026

A few notes on the 2025 batch, from Google's simplifying search results post:

  • Its September 2025 update says course info, ClaimReview, estimated salary, learning video, special announcement and vehicle listing had been removed from Search results, and that from September 9 those types were removed from Search Console rich result reports, the Rich Results Test and the search appearance filters.
  • The update did not mention book actions, so check that type's own documentation for its current status.
  • Google wrote that the update "won't affect how pages are ranked" and that use of these types outside Google Search is not affected.

Smaller changes also matter if you rely on them. On June 5, 2025 Google removed the online event properties from its event documentation, limiting event markup to physical events, and since January 2025 breadcrumb rich results appear only on desktop.

For FAQ markup specifically, the FAQ schema guide covers what is left and what to do with existing FAQ sections.

Does old structured data hurt your site?

Not directly. Google has said the 2025 removals do not affect ranking, and its August 2023 HowTo and FAQ announcement said there was no need to proactively remove FAQ markup, adding that unused structured data does not cause problems for Search.

The real costs are indirect:

  1. Nobody is checking it. When a type is retired, it disappears from Search Console reports and the Rich Results Test. If a template change breaks the JSON-LD or fills it with wrong data, you will not hear about it.
  2. It can contradict the page. A product page with stale ClaimReview, an old salary figure in leftover Occupation markup, or a special announcement from 2020 sends machine readers facts that are no longer true.
  3. It adds weight and complexity. Large JSON-LD blocks in every template make the HTML heavier and the templates harder to maintain.
  4. It may be invalid. A broken JSON-LD block can stop a parser from reading the whole script, including the parts you still need, such as Organization or Product. JSON-LD errors shows how that happens.

Google's own advice for AI features is short: its guidance on succeeding in AI search asks that structured data match the visible content and be validated, and it does not name any type as required for AI Overviews or AI Mode. OpenAI, Anthropic and Perplexity do not document that their systems read particular schema.org types at the time of writing.

So the honest answer is: markup that accurately describes a page is a clean, machine-readable summary, and that can help any system that chooses to read it. It is not a documented route into AI answers, and a retired type gives you no Google feature in return. Structured data for AI search goes into what is and is not documented.

Keep or remove: a rule for each case

SituationDecision
Markup is valid, accurate and describes content visible on the pageKeep, if it costs little to maintain
Another consumer you care about uses the type, such as a partner feed or your own site searchKeep and keep validating it
Markup describes content the page no longer showsRemove
Data is stale or wrong, such as old prices, dates or salariesFix or remove
JSON-LD is invalidFix now, since it can affect other types in the same block
Type was added only for a Google feature that no longer exists, and nobody maintains itRemove at the next template change

HowTo is a good example of the middle ground. If your steps are already in the HTML as a numbered list, the page reads well to people and crawlers without the markup. Removing it changes nothing in Google Search, and keeping it does no harm as long as it matches the steps on the page.

Where to spend the effort instead

The time you save by not maintaining retired types is better spent on markup Google still documents and that describes core facts about your business and pages. At the time of writing that includes:

  • Organization markup on the home page, with your name, logo and official profiles. See the Organization schema guide.
  • Product markup with prices and availability that match the page, covered in the Product schema guide.
  • Article markup with accurate dates and authors on editorial content.
  • Breadcrumb markup, still documented even though the rich result now shows only on desktop.

These types are still checked by the Rich Results Test and reported in Search Console, so errors surface on their own. That alone makes them cheaper to keep correct than a retired type nobody reports on.

How to find leftover markup on your site

Because Search Console no longer reports on retired types, you have to look yourself. Fetch a page and list the types in its JSON-LD:

bash
curl -s https://www.example.com/guide/ | python3 -c '
import sys, re, json
html = sys.stdin.read()
for block in re.findall(r"<script[^>]*application/ld\+json[^>]*>(.*?)</script>", html, re.S):
    try:
        data = json.loads(block)
    except ValueError as e:
        print("INVALID JSON-LD:", e); continue
    items = data if isinstance(data, list) else data.get("@graph", [data])
    for item in items:
        print(item.get("@type"))
'

Run it on one page per template: home, article, product, category, location, job posting. Then search your codebase for the retired types:

bash
grep -rnE '"@type": *"(HowTo|FAQPage|SpecialAnnouncement|ClaimReview|Course|Dataset|Quiz|Vehicle|LearningResource)"' src/ templates/

Adjust the folders to your project. Plugin-generated markup, such as SEO plugins on WordPress, will not show up in your source, so check the rendered HTML as well.

Frequently asked questions

Will Google penalize pages that still have HowTo or FAQ markup?

Google has not described any penalty. In 2023 it said unused structured data does not cause problems for Search and there was no need to proactively remove FAQ markup, and it said the 2025 removals do not affect ranking.

Is FAQ schema completely dead?

As a Google rich result, yes: Google says FAQ rich results stopped appearing in Search from May 7, 2026. FAQPage remains a valid schema.org type that describes question-and-answer content.

No. Google removed the documentation on November 29, 2024 because the feature is no longer available in Search results.

Google announced in November 2025 that it is phasing dataset structured data out of Search results. Add it only if another consumer you care about uses it, and keep it accurate.

Next step

Pick one page per template, list its JSON-LD types with the script above and decide keep, fix or remove for each. If you would rather have the markup checked against the visible page for every template, an audit includes it, and the free check covers a single page with no account.

Filed under Structure and schema. Topics: structured-data, json-ld, google, search-console