FAQ Schema Lost Its Rich Results for Most Sites — Here's What That Means for Your Structured Data Strategy

Google's rich results for "FAQ" schema used to appear routinely in search results — and then Google quietly removed them for most sites, a reminder that the value of structured data isn't just what it does today but how it positions you for features that exist tomorrow

The previous articles on this site covered which schema types produce rich results, E-E-A-T and structured data, and validation vs rich-results eligibility. This article addresses how structured data's value changes over time — the history of FAQ schema's rise and fall, what this means for schema investment strategy, and why not marking up content is often the less future-proof choice.

The FAQ schema story: a case study in Google changing the rules

FAQ schema (FAQPage) was, for several years, one of the most visually impactful schema types available. When implemented correctly, it could expand a search result to show the question-answer pairs directly in the SERP — dramatically increasing the visual footprint of a single result, which many SEOs credited with significant CTR improvements.

In 2023, Google announced it was limiting FAQ rich results — restricting the expanded FAQ display primarily to "authoritative government and health websites" and removing the expanded display for most other sites. The change rolled out broadly, and the FAQ result enhancements that many sites had carefully implemented effectively disappeared from their results.

Key observations from this episode:

The markup didn't become invalid — pages with FAQPage schema still validate correctly, and Google still processes the markup. It just doesn't display it as expanded FAQ results for most sites.

The investment was partially wasted — time spent adding FAQPage markup specifically to gain SERP expansion benefits didn't pay off for most sites after the change.

But the data may still be used — there's evidence Google continues to use FAQ markup to understand page content and potentially surfaces it in AI Overviews, voice answers, and other non-traditional contexts.

The broader pattern: schema features are added and removed

FAQ's trajectory isn't unique. Authorship markup (linking articles to Google+ author profiles) was heavily promoted, adopted by many publishers, and then entirely discontinued. Rich snippets for ratings and reviews have had their display criteria tightened multiple times. HowTo schema lost its rich result display for most queries.

This creates a strategic tension for schema investment: structured data requires implementation time (adding JSON-LD, testing it, maintaining it as content changes) — and the specific display benefit that justified the investment may be removed at any time.

The pragmatic framework: invest in schema that has multiple value channels, not just SERP display:

Knowledge graph and entity understanding: Organization, Person, LocalBusiness schema help Google understand what your entity is — useful not just for rich results but for knowledge panel inclusion, brand query understanding, and entity association for E-E-A-T purposes.

Core content schema: Article, BlogPosting, Product schema signal what type of content a page contains — relevant for content categorization independently of any specific rich result display.

High-value specific rich results: Product (with pricing and availability), Recipe, Event, and JobPosting schema produce rich results that have remained relatively stable and provide clear value — these remain strong investments.

Implementing schema for longevity, not just current display

The most durable structured data implementations have these characteristics:

They accurately describe the page content. Schema that's a faithful representation of what's actually on the page — actual FAQs that are genuinely answered, actual product prices that are current, actual recipe times that are accurate — remains valid and potentially useful regardless of how Google's display of it evolves. Schema that's gamed or inaccurate tends to get caught and discounted.

They target entity understanding, not just rich results. Organization schema, sameAs properties linking to authoritative external profiles, BreadcrumbList for structural understanding — these contribute to Google's entity knowledge graph in ways that aren't tied to a specific SERP display feature.

They're maintained as the underlying content changes. Stale schema (product prices that are outdated, event dates that have passed, FAQ answers that no longer match the page content) actively hurts — it creates a mismatch between structured signals and page content that Google can detect.

Nested schema: connecting entities across a page

More advanced schema implementations use entity linking — connecting the entities on a page through nested references:

A product page might have Product schema that includes a nested Organization (the brand), Review aggregations, AggregateRating, and Offer details. An article might have Article schema that links to a Person (the author) who also appears in the site's Organization schema.

This web of connected entities helps Google understand not just "this page has a product" but "this product is from this brand, made by this organization, sold at this price, with these reviews" — a richer understanding that contributes to how the page's content is processed.

How to use the Schema Generator on sadiqbd.com

1. Generate accurate schema — the values in your JSON-LD should exactly match what's visible on the page; mismatches between schema and visible content are a validation failure and a trust signal problem
2. Prioritize high-stability schema types first: Product, LocalBusiness, Organization, Article — these have consistent, long-term support and multiple value channels beyond just SERP display
3. Test with Google's Rich Results Test after generation — but remember the previous article's point that valid schema ≠ rich results eligibility; validation confirms technical correctness, not that the rich result will display
4. For FAQ schema: still worth implementing for AI Overview and voice-search value even though the expanded SERP display is limited — but don't implement it primarily for SERP expansion and be surprised when it doesn't appear

Frequently Asked Questions

Should I remove FAQ schema since it no longer shows rich results for most sites? Generally, no. The implementation cost of removing it is similar to the cost of keeping it, and the markup continues to help Google understand your content structure even without the visual SERP expansion. The cases where removal makes sense: if you're auditing your markup and the FAQ entries are outdated/inaccurate (in which case, update the content and markup together or remove outdated entries), or if your technical team needs to reduce template complexity and the FAQ schema is creating maintenance burden without any apparent benefit. If the markup is accurate and current, leaving it in place costs nothing and retains potential value in non-traditional display contexts.

Is the Schema Generator free? Yes — completely free, no sign-up required.

Try the Schema Generator free at sadiqbd.com — generate accurate, validated JSON-LD structured data for any page type.