SEO Features Google Has Switched Off Since 2023 (And What to Do Instead)

Key takeaways
- Google has quietly retired a long list of Search features since 2023. Most were rarely used, and Google has said removing rich results is a display change, not a ranking change.
- The common thread: tricks that make a listing look bigger get removed. Useful, honest, fast pages do not.
- Most of these retirements need no action. A few are worth a ten-minute clean-up, listed in the checklist below.
- Bookmark Google’s own documentation changelog. It is the quickest way to confirm what has actually changed.

Why Google keeps removing features
If you have worked in SEO for a few years you have seen this pattern. A feature launches, the industry builds a tactic around it, usage explodes, and a few years later Google removes it because it is cluttered, rarely used or too easy to game. It is worth keeping a calm head about it, because most of the panic around each removal turns out to be unnecessary. The skill is knowing which changes matter and which are just housekeeping.
The timeline
All dates below come from Google Search Central’s documentation changelog or its blog unless noted. Where a source reports the date the feature stopped, rather than the date Google updated its documentation, we say so.
| When | Feature | What happened |
|---|---|---|
| Aug to Sept 2023 | FAQ and How-To rich results | FAQ results cut back to well-known government and health sites. How-To rich results stopped showing on desktop in September 2023, so they were effectively retired. |
| 1 Dec 2023 | Mobile-Friendly Test and Mobile Usability report | Google updated its documentation to remove references to the test and the report, which were going away. |
| Early 2024 | “Cached” link in results | The cached link was retired. Google later cleaned up its documentation in autumn 2024: the cache: search operator documentation was removed on 24 September 2024 and the noarchive rule was moved to a historical section on 2 October 2024. |
| 12 Mar 2024 | First Input Delay (FID) | Interaction to Next Paint (INP) replaced FID as a Core Web Vital. |
| Mar to Jun 2024 | Guided recipes, home activity markup | Documentation removed after the underlying features disappeared (6 March and 18 June 2024). |
| 29 Nov 2024 | Sitelinks search box | Documentation removed because the feature was no longer in Search results. |
| 12 Jun 2025 | Seven structured data types | Google announced a phase-out of Book Actions, Course Info, Estimated Salary, ClaimReview, Learning Video, Special Announcement and Vehicle Listing. Documentation for several was removed on 9 September 2025. |
| 5 Nov 2025 to 6 Jan 2026 | Practice problems and Dataset markup | Practice problem markup deprecated, its documentation removed in January 2026, and Dataset markup began to be phased out of Search results. |
| 7 May to 15 Jun 2026 | FAQ rich results | Stopped appearing in Search on 7 May. Documentation removed 15 June. |
| 1 Jul 2026 | AMP viewer, AMP Cache, signed exchanges | References removed from documentation. Search links directly to publishers’ pages, and AMP content ranks like any other page. |
What each change means for you
How-To and FAQ rich results
Both are gone. Your pages are not penalised, and you can leave the markup in place or remove it. Keep the visible content if it helps visitors. We wrote a full guide on what to do with your FAQ schema.
Mobile-Friendly Test and Mobile Usability report
The tools went away, but mobile usability did not stop mattering. Google still expects pages to display well on phones. Check your pages on real devices, use Lighthouse for guidance, and watch your Core Web Vitals report. A quick manual test beats an old report every time.
The cached link and the cache: operator
People used cached copies to check what Google last saw, to read pages that were down and to compare versions. That job now belongs to other tools. To see how Google sees a page, use the URL Inspection tool in Search Console, which shows the rendered HTML and indexing status. For historical versions, the Internet Archive and your own backups are better. The noarchive directive is now mostly historical for Google.
FID replaced by INP
If a report still shows FID, it is outdated. INP measures every interaction, and the target is 200 ms or less. We explain how to fix it in our INP guide.
The sitelinks search box
That small search field that used to appear under a brand’s top result no longer appears, and Google removed its documentation. If you added the special WebSite search markup only for that, you can remove it or leave it. It does no harm. Spend the time on a good on-site search and clear navigation instead.
The seven structured data types retired in 2025
If you publish courses, salary pages, fact-check articles, announcements, learning videos, book pages or vehicle listings, check whether you added markup for the retired types. Your content is still indexable and rankable. The markup simply no longer produces the special display. Use the content itself, clear headings and honest titles to compete.
AMP
Still works, no longer special. If you still run an AMP layer, read our guide to retiring AMP safely.
Which of these actually affected rankings?
Almost none of them. Google said at the time of the 2023 FAQ and How-To change that it was not a ranking change. The rich result retirements in 2025 were described as part of simplifying results because the features were not adding much value. The one retirement with real technical consequences is FID to INP, because it changed a metric Google uses in its page experience systems. Everything else changed how listings look.
A ten-minute audit you can do today
- Search your templates for retired markup. Look for FAQPage, HowTo, Course Info, ClaimReview, SpecialAnnouncement, Vehicle and the sitelinks search box markup. Decide to keep or remove each, then apply the decision site-wide.
- Replace FID with INP in any dashboard, report or client template.
- Stop relying on the cached link. Use URL Inspection in Search Console to check how a page was crawled.
- Review any AMP layer. If you still have one, plan its retirement with redirects.
- Check Search Console messages for reports that were removed so your team does not search for them.
- Write down the date. If clicks changed around a retirement date, note it in your analytics annotations so nobody investigates a ghost later.
What stays valuable
Strip away the retired tricks and the durable list is short:
- Useful, specific content that answers a real question better than the next result.
- Clear titles and headings that say what the page is.
- Fast, stable pages that pass Core Web Vitals, including INP.
- Accurate structured data for the types Google still supports, checked in the current Search Gallery.
- Clean technical basics: HTTPS, sensible redirects, one canonical URL per page, a current sitemap and no broken internal links.
Google’s own guidance on its generative search features says the same thing in different words: it is still SEO, built on unique, helpful content and good technical quality, and there is no special file or markup you need. If you want help applying that to your site, our website maintenance and security team runs this kind of audit, and you can talk to us any time.
Frequently asked questions
Do I need to remove structured data for retired features?
No. Google has said leftover markup does no harm; it just no longer produces the special result. Remove it if it is hard to maintain or out of sync with the page, otherwise leave it.
Did these retirements change my rankings?
No, rich result removals change how a listing looks, not where it ranks. The change with a technical effect is FID being replaced by INP as a Core Web Vital.
Where can I see what Google changes in Search documentation?
Google Search Central publishes a documentation updates page listing dated changes. It is the quickest way to confirm whether a feature has been removed.
How do I check how Google sees my page now that the cached link is gone?
Use the URL Inspection tool in Search Console. It shows the crawled and rendered HTML, the indexing status and any detected problems.
Are Core Web Vitals still worth working on?
Yes. Google says its ranking systems use Core Web Vitals, but also that good scores do not guarantee top rankings. Treat them as a real user experience goal, with INP as the responsiveness metric.
Sources and further reading
- Google Search Central: documentation updates
- Google Search Central blog: changes to HowTo and FAQ rich results (2023)
- web.dev: Interaction to Next Paint (INP)
- Google: page experience guidance
- Google: structured data Search Gallery
- Google: optimizing your website for generative AI features on Google Search