Google Deprecated These Rich Result Types: What WordPress Site Owners Should Remove, Keep, and Recheck Now
Google simplified Search by deprecating support for several lower-value rich result types and later removing related reporting in Search Console. The key point from Google’s Search Central blog: this change does not directly affect rankings. Pages remain eligible for indexing and ranking as before.
For WordPress and WooCommerce operators, the practical question isn’t “Did we lose rankings?” It’s “Are we still maintaining schema that no longer earns a Search presentation?”
What changed — and why it matters less than many site owners think
Google announced it was simplifying Search results by retiring certain rich result types it considered lower value for users. In follow-up updates and documentation changes, related Search Console enhancement reports were removed or consolidated. Google’s updates changelog confirms these simplifications were part of an ongoing cleanup of Search features.
Two important clarifications from Google:
- There is no direct ranking boost tied to these rich result types.
- Removing support does not mean pages are deindexed or penalized.
This is not a rankings event. It’s a presentation and reporting event.
However, on WordPress sites, deprecated structured data often continues to be generated automatically by:
- SEO plugins with legacy rich result toggles
- WooCommerce extensions outputting older product-related schema
- FAQ or HowTo blocks created before support changed
- Page builders injecting JSON-LD templates
- Custom snippets added years ago and never revisited
Even if unsupported markup is not harmful by itself, it increases maintenance surface area. Every additional schema type means more QA, more template logic, more validation noise, and more confusion when Search Console reports disappear.
I routinely see Looker Studio dashboards and internal SEO reports still filtering by retired Search appearance dimensions. Once Google removes those reports, your trend lines break. That’s an operations issue, not just an SEO one.
Google’s structured data gallery now reflects what is currently supported for rich results in Search. If a schema type no longer appears there, it no longer earns a Search enhancement. Separately, Google’s guidance on succeeding in AI search reinforces that crawlability, indexability, visible content alignment, and valid structured data still matter—but only when they map to supported experiences.
What to do next
Treat this as a structured data audit and cleanup sprint, not a panic response.
1. Inventory what your site actually outputs.
Use URL Inspection and Rich Results testing on representative templates:
- Homepage
- Blog post
- Product page
- Category archive
- Local landing page
Identify schema coming from plugins, theme functions, WooCommerce templates, and custom JSON-LD.
2. Compare against Google’s current structured data gallery.
Keep markup that maps to supported rich results (for example: Product, Review, Breadcrumb, Article, Organization, LocalBusiness, Video where applicable). If a type is no longer supported for Search enhancements, ask: does it serve another real purpose (internal knowledge graph, integrations, third-party consumption)? If not, it becomes optional overhead.
3. Do not strip all non-rich-result Schema.org markup.
Unsupported for rich results does not mean invalid or forbidden. The goal is prioritization, not scorched earth removal.
4. Recheck content alignment.
Markup must reflect visible, indexable content. If your FAQ or HowTo schema remains but the content is hidden, truncated, or blocked from crawling, that’s a quality risk. Google’s AI-search guidance emphasizes that content must be crawlable and actually present in the HTML served with a 200 response.
5. Review Search Console workflows.
If you relied on specific Enhancement reports or Search appearance filters that no longer exist, update your monitoring. Google’s newer Search Console recommendations surface actionable issues differently. Rebuild dashboards that assumed deprecated report types.
6. Test crawl and index fundamentals before expanding schema.
Confirm:
- No accidental noindex directives
- Correct canonicals on paginated and filtered URLs
- 200 status responses for primary templates
- No blocked resources preventing rendering
In 2026, structured data expansion is rarely the bottleneck. Crawl access, rendering stability, template clarity, and clean information architecture usually matter more.
If a schema type no longer earns a Google Search presentation, keeping it should require a deliberate reason. Otherwise, you’re carrying technical debt for a feature that no longer exists.
This is an opportunity to simplify templates, reduce plugin bloat, clean up reporting logic, and refocus on what Google still supports—and what actually drives qualified traffic and revenue.
Sources
- Google retires some schema displays
- Search Central documentation updates
- Supported rich result gallery
- Google AI search guidance
- Search Console recommendations help
- Search Engine Land analysis
Know someone who would benefit from this update? Share this article with them.
This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.
