Navigating the Post-FAQ Rich Results Era: To Keep or Remove FAQPage Schema?
The Evolving Landscape of FAQ Rich Results and Structured Data
The digital marketing world is constantly shifting, and recent changes from Google have once again prompted content strategists and SEO professionals to re-evaluate established practices. A significant point of discussion has been the fate of FAQ rich results and, by extension, the utility of FAQPage schema. With Google discontinuing the display of FAQ rich results for most sites in May 2023, the question arises: should this structured data still be maintained on our pages?
Understanding the Shift: What Happened to FAQ Rich Results?
For years, FAQPage schema was a valuable tool for enhancing search engine visibility. By marking up frequently asked questions and their answers, websites could earn prominent rich results in search engine results pages (SERPs), often appearing as expandable sections directly beneath a listing. This provided an immediate visual advantage, increasing click-through rates and offering users quick answers.
However, in May 2023, Google announced a significant change: FAQ rich results would largely cease to appear for most websites, with the exception of specific, highly authoritative sites (like government and health websites) and a limited number of product pages. This move was part of a broader effort to streamline SERPs, reduce clutter, and ensure that search results prioritize the most relevant and high-quality information.
The Debate: Keep the Schema or Remove It?
The immediate aftermath of this change led to a critical discussion within the SEO community. Many content creators found themselves with existing FAQPage schema implemented across numerous pages, prompting a core dilemma:
- Argument for Keeping: Some argued that retaining the schema, even without visible rich results, might still offer subtle benefits. The theory was that structured data could aid search engines and advanced AI tools in better understanding the page's content, context, and relationships between questions and answers. It was seen as potentially 'harmless' and a way to provide additional signals.
- Argument for Removing: Others advocated for immediate removal. The primary rationale was that if the schema no longer yielded a direct, visible benefit (like rich results), it simply added unnecessary markup to the page. The emphasis here was on lean, efficient code and removing anything that doesn't contribute tangibly to SEO or user experience. Some even suggested that
FAQPageschema was deprecated much earlier, though this is a misunderstanding of Google's 2023 update which specifically targeted the *display* of rich results, not the validity of the schema.org markup itself.
Our Recommendation: Prioritize User Experience and Lean Markup
Based on current understanding and Google's stated intentions, our analysis leans towards a pragmatic approach:
1. Retain Visible FAQ Sections for Users
The deprecation of FAQ rich results does not diminish the value of a well-crafted, visible FAQ section on your webpage. Users still appreciate readily available answers to common questions. These sections improve on-page user experience, reduce bounce rates, and can directly address user intent, which remains a critical ranking factor. Ensure your on-page FAQs are clearly structured, easy to read, and genuinely helpful.
2. Remove FAQPage Schema for Most Pages
For the vast majority of your content, especially informational blog posts or general service pages, the FAQPage schema no longer offers a direct SEO advantage. While structured data generally helps search engines understand content, modern AI and natural language processing capabilities are increasingly adept at extracting information directly from well-structured on-page text. The marginal benefit of redundant schema for 'understanding' is likely outweighed by the benefit of a cleaner, more efficient codebase.
Consider exceptions: If you operate an e-commerce site, Google may still occasionally display FAQ snippets for specific product pages. In such niche cases, testing and monitoring are crucial. However, for general content, the overhead of maintaining schema without a clear return is not advisable.
3. Focus on Semantic HTML and Content Quality
Instead of relying on hidden schema for basic Q&A, ensure your visible FAQ content is structured using appropriate semantic HTML elements. Use or tags for questions and clear tags for answers. This provides inherent structure that both users and search engines can easily interpret without the need for additional FAQPage markup.
Moving Forward with Content Strategy
The evolution of structured data requirements underscores a broader trend: Google's algorithms are becoming more sophisticated, prioritizing genuine user value and clear, well-organized content over technical signals that might be redundant. The focus should always be on creating authoritative, comprehensive content that directly answers user queries and provides an excellent on-page experience.
In this dynamic environment, leveraging an AI blog copilot can be instrumental. Platforms like CopilotPost (copilotpost.ai) empower content strategists and bloggers to efficiently generate SEO-optimized content, ensuring your articles are not only well-written but also structured to meet modern search engine expectations. By automating aspects of content creation and publishing, an AI content generation platform allows you to focus on high-level content strategy and user intent, rather than getting bogged down in deprecated technical details. This approach helps scale your blogging efforts and maintain a competitive edge in SEO.