FAQ Schema Deprecated for Google Rich Results: What to Use Instead
Google FAQ rich results are no longer a broad SEO growth lever. Learn when FAQPage still makes sense and which schema types to use instead.
Google's FAQ rich result story has changed. FAQPage markup used to be an easy structured data win for many publishers, but Google now says FAQ rich results are no longer appearing in Search and that related Search Console/API surfaces are being removed in June 2026.
That does not mean every visible FAQ should disappear from your site. It means FAQ schema should stop being treated as a broad SEO growth hack.
What changed with FAQ schema
FAQPage structured data can still describe a real page that is primarily a curated list of questions and answers. The problem is the promise many SEO tools made: add FAQ schema, get more SERP real estate, win more clicks.
That promise is deprecated for broad Google rich results.
If your page uses FAQ content, the safer framing is:
- Keep helpful visible FAQs for users.
- Keep markup only when the page is truly an FAQ page and the content matches exactly.
- Do not build an SEO roadmap around FAQ rich result eligibility.
- Prioritize schema types that clarify the main entity, page purpose, products, services, articles, and local business facts.
Why FAQ schema demand still exists
People still search for
The right answer is not “never use FAQPage.” The right answer is “use FAQPage narrowly, and use stronger schema types for the actual page goal.”
When to keep FAQPage markup
Keep FAQPage only when all of these are true:
- The page is primarily a publisher-curated FAQ page.
- Each question and answer is visible to users.
- There is one official answer per question.
- The markup exactly matches the visible content.
- You are using it for machine clarity, not expecting broad Google FAQ rich results.
If the page is a forum thread, use QAPage. If the page is a how-to tutorial, use HowTo where eligible. If the FAQ is just a section on a service/product page, the main schema type should usually be Service, Product, WebPage, LocalBusiness, or Organization.
What to use instead
WebPage schema
Use WebPage to clarify the page identity, canonical URL, language, breadcrumb context, and relationship to the site.
Article schema
Use Article, BlogPosting, NewsArticle, or TechArticle when the page is editorial or educational content.
QAPage schema
Use QAPage for user-generated question-and-answer pages where multiple answers may exist.
HowTo schema
Use HowTo for eligible step-by-step instructional content where the steps are visible and central to the page.
Product schema
Use Product when the page sells or describes a specific product, offer, aggregate rating, shipping policy, or return policy.
Organization and WebSite schema
Use Organization and WebSite to establish brand identity, entity relationships, site URL, logo, and search behavior. These are especially important for AI-ready structured data because answer engines need to understand who owns the content.
Generate Organization schema · Generate WebSite schema
LocalBusiness schema
Use LocalBusiness or a subtype when location, service area, NAP, hours, reviews, and local trust matter more than a generic FAQ block.
Quick checklist
Before adding FAQPage markup, ask:
- Is this page really an FAQ page?
- Are all questions and answers visible?
- Would WebPage, Article, Product, Service, LocalBusiness, or Organization better describe the page?
- Does the page have a title, H1, canonical, meta description, and Open Graph coverage?
- Have you validated the JSON-LD syntax before deploying?
Run the free tools
Use SwiftSchema to check and clean up your implementation:
- AI Schema Readiness Checker — see whether a URL has useful JSON-LD, metadata, and entity coverage.
- JSON-LD Formatter + Validator Lite — format pasted JSON-LD and catch parse errors.
- Schema Markup Generators — generate page-specific structured data instead of relying on deprecated FAQ rich result advice.
FAQ schema is not the center of the strategy anymore. Accurate, page-specific, AI-ready schema markup is.