FAQ Schema in 2026: When It Helps, When It Hurts

FAQ Schema was the highest-ROI rich-result deployment from 2018 through 2022. Add the markup to any page with a question-answer block, and Google would show expandable FAQs directly in the SERP — taking up double or triple the visual space of a normal result and lifting CTR meaningfully. Many SEO playbooks still treat it as a universal lift.

That era ended in August 2023, when Google narrowed FAQ rich-result eligibility to "authoritative government and health websites" only. The 2025 update broadened it slightly but kept most service-business pages excluded. The result: most pages with FAQ Schema deployed today get zero rich-result benefit. This article maps which pages still benefit, which pages waste the markup, and which alternatives now outperform FAQ Schema for typical service businesses.

What Google Changed in 2023 and 2025

Pre-August 2023: FAQ rich results displayed for nearly any well-formed FAQ Schema. Post-August 2023: Google restricted display to recognized "authoritative" sources, primarily government domains, healthcare institutions, and major reference sites. The 2025 update added a narrow class of certified-expert content but did not return broad eligibility.

Importantly, Google still reads FAQ Schema on all sites — for AI Overviews citation, People Also Ask candidacy, and internal indexing. The change was specifically in the rich-result visual display, not in the schema's underlying parsing.

Pages Where FAQ Schema Still Works

For service businesses, FAQ Schema still delivers measurable value in these cases:

• Content under a recognized expert author profile. Sites with named, credentialed authors visible in the page and structured data have a chance at the rare authority eligibility.
• Pages targeting "People Also Ask" boxes. Even without rich-result eligibility, FAQ Schema raises PAA appearance probability significantly.
• AI Overviews citation pages. Google's AI models use FAQ Schema as a structured signal when selecting which sources to cite.
• Voice search assets. Google Assistant and Alexa both parse FAQ Schema for spoken answers.

Pages Where FAQ Schema Has Zero Impact Now

Adding FAQ Schema to these pages is wasted markup:

• Generic service or product pages with no underlying expert credential.
• E-commerce category and product detail pages — these are explicitly out of eligibility scope.
• Blog posts on commercial brands without identifiable expert authorship.
• Marketing landing pages built primarily for conversion.

Keep the underlying FAQ content (still useful for the user), but skip the schema. Investing engineering time in FAQ markup here has no measurable return.

Pages Where FAQ Schema Can Backfire

In rare cases the markup actively hurts. Two patterns we have audited:

• FAQ Schema declaring content not visible on the page. Violates Google's content-and-markup-must-match policy. Manual actions sometimes follow.
• FAQ Schema on transactional commerce pages. Google may interpret the page as informational rather than transactional, reducing its ranking for purchase-intent queries.

Both are avoidable. Always mark up only what is actually shown, and never inject FAQ Schema on hardcore commerce pages where transactional intent is the goal.

What to Use Instead of FAQ Schema

For service-business pages that previously relied on FAQ Schema for SERP space, two alternatives:

• Clear H2-structured questions. Even without FAQ Schema, well-structured H2 questions can be picked up by AI Overviews as citation sources.
• HowTo Schema. Step-by-step content still earns rich-result display, with looser eligibility constraints than FAQ.

Combine these with the SeoMata technical SEO service structured-data strategy. The right schema choice now depends heavily on page type — there is no universal answer.

How to Verify Your FAQ Schema Is Being Honored

1. Google Search Console → Search Appearance → FAQ. See which pages actually display FAQ rich results.
2. Google Rich Results Test. Validate your schema syntax for errors.
3. Test in incognito mode. Search the target query and watch whether your FAQ unfold actually appears in the SERP.

If after 6 weeks of deployment GSC still shows zero FAQ rich-result impressions, the page is outside Google's current eligibility class. Keep the schema (still helps AI citation and PAA), but stop investing additional content effort specifically for FAQ rich results.

FAQ

Should I remove FAQ Schema from pages that no longer get rich results?

No. The schema still helps AI Overviews citation and PAA candidacy, even when rich-result display is unavailable. Removing it loses indirect benefits with no upside.

Will FAQ Schema return for non-authority sites?

Probably not in the same broad form. Google's stated direction is to favor authority-graded content. Plan for the new eligibility class as permanent.

How do I make my site "authoritative" enough to qualify?

Add explicit author profiles with credentials, link to verifiable third-party recognition, build long-form expert content, and accumulate authoritative inbound links via the SeoMata local SEO service link-building approach.

Does HowTo Schema have similar restrictions?

HowTo restrictions tightened in late 2023 (mobile-only display), but eligibility remains broader than FAQ. For step-by-step instructional content, HowTo is still the preferred schema.

Conclusion and Next Steps

FAQ Schema is no longer a universal rich-result lever. Use it where it still works (authority content, AI citation, voice), skip it where it doesn't, and migrate effort to alternative schemas where appropriate. For deeper reading, see the SeoMata SEO guides library or the official Google FAQPage structured data documentation.

1. Audit your site for FAQ Schema usage this week. Match each page against the eligibility classes above using the SeoMata technical SEO service schema audit.
2. Migrate non-eligible FAQ pages to clean H2 structure plus HowTo Schema where applicable. Track with the Google review growth service visibility dashboards.
3. If FAQ rich-result impressions remain zero after 60 days post-cleanup, accept the schema is information-only and invest content effort elsewhere. Book a 30-minute diagnostic on our case studies page for a tailored schema roadmap.

Bottom line: FAQ Schema went from universal lift to niche tool. Treat it that way.