Does FAQ Schema Still Help SEO After Google’s Updates?
Table of Contents
For years, FAQ Schema was considered one of the easiest ways to enhance search listings. Adding a structured list of common questions and answers could earn eye-catching FAQ rich results beneath your page, increasing visibility and potentially improving click-through rates. For many SEO professionals, it became a standard part of technical optimisation.
That changed when Google significantly reduced the display of FAQ rich results, limiting them primarily to well-known government and health websites. Suddenly, businesses that had invested time implementing FAQ Schema saw those enhanced search listings disappear, leading many to question whether the markup was still worth using at all.
The short answer is yes – but probably not for the reason you think.
Today, FAQ Schema should no longer be viewed as a shortcut to gaining extra space in the search results. Instead, its value lies in helping search engines better understand your content, providing machine-readable context and supporting structured information that may become increasingly important as AI-powered search experiences continue to evolve.
In this guide, we’ll examine what Google’s updates actually changed, whether FAQ Schema has any direct impact on rankings, where it still provides genuine value, and when implementing it is simply unnecessary. By the end, you’ll have a clear framework for deciding whether FAQ Schema deserves a place in your technical SEO strategy in 2026 and beyond.
What Is FAQ Schema?
FAQ Schema is a type of structured data that helps search engines understand that a page contains a series of questions and answers. Rather than relying solely on the visible text and page layout, search engines can read a standardised, machine-readable format that clearly identifies each question and its corresponding answer.
Most websites implement FAQ Schema using JSON-LD (JavaScript Object Notation for Linked Data), Google’s preferred format for structured data. JSON-LD is added to the page’s source code and doesn’t affect how the content appears to visitors, making it easier to maintain than embedding structured data directly into the HTML.
The specific schema type used is FAQPage, which is part of the Schema.org vocabulary. It defines one or more questions, each paired with an accepted answer, allowing search engines to interpret the content consistently.
It’s important to distinguish between the structured data and the content itself. FAQ Schema does not create new information for search engines—it simply labels content that is already visible on the page. Google’s guidelines require that any questions and answers included in the markup are also available to users, helping prevent misleading or hidden content from being indexed.
In short, FAQ Schema doesn’t change what your page says; it changes how search engines understand what your page says. That distinction is more important than ever as search engines increasingly rely on structured, machine-readable data to interpret content across traditional search and emerging AI-powered search experiences.
What Changed With Google’s FAQ Rich Results?
For several years, FAQ Schema was one of the most widely adopted forms of structured data. When implemented correctly, it could generate expandable question-and-answer sections directly beneath a search result, allowing websites to occupy more space on the search engine results page (SERP) and potentially improve click-through rates.
That changed in August 2023 when Google announced a significant reduction in the display of FAQ rich results. Rather than showing them broadly across websites, Google limited FAQ rich results to well-known, authoritative government and health websites. The change formed part of Google’s wider effort to simplify search results and present users with more relevant, less cluttered information.
The update affected millions of websites overnight. Although the underlying FAQPage structured data remained valid, the enhanced search appearance that many businesses had relied upon largely disappeared. For most commercial websites, adding FAQ Schema no longer results in visible FAQ rich snippets in Google Search.
Importantly, Google did not deprecate FAQ Schema itself. The Schema.org specification remains fully supported, and Google continues to recognise the markup. What changed was Google’s decision about when and where it chooses to display FAQ rich results.
Today, eligibility for FAQ rich results is extremely limited. In Google’s own documentation, rich results are generally reserved for trusted government organisations and health-related websites where accurate, verified information provides clear value to users. Most businesses, ecommerce stores, agencies and publishers should no longer expect their FAQs to appear as expandable results in the SERPs, regardless of whether the structured data is implemented correctly.
This shift has changed the conversation around FAQ Schema. Instead of asking, “Will this give me a larger search listing?”, SEO professionals should now ask, “Does this structured data help search engines understand my content better?” That is a far more relevant question in today’s search landscape.
Industries Still Most Likely to Display FAQ Rich Results
Although exceptions are rare, Google is most likely to display FAQ rich results for websites in sectors where trustworthy information is essential, including:
- Government departments and public services.
- National and regional healthcare providers.
- Public health organisations.
- Official guidance and advisory websites.
For the vast majority of commercial websites, including local businesses, ecommerce stores, SaaS companies and digital agencies, FAQ rich results are no longer a realistic objective. Instead, the focus should be on creating genuinely helpful FAQ content that improves the user experience and supports broader technical SEO efforts.
Does FAQ Schema Still Improve Rankings?
One of the biggest misconceptions surrounding FAQ Schema is that it directly improves search rankings. Despite years of speculation, Google has consistently stated that structured data is not a ranking factor. Simply adding FAQ Schema to a page will not cause it to rank higher than a competitor with similar content.
That doesn’t mean it has no SEO value.
Ranking Factors vs Search Enhancements
It’s important to separate ranking factors from search enhancements.
Ranking factors are signals Google uses to determine where a page should appear in the search results. These include factors such as content quality, relevance, backlinks, page experience and search intent.
Search enhancements, on the other hand, affect how a page is understood or displayed after it has been indexed. Structured data falls into this category. It helps Google interpret the purpose and structure of a page, but it does not override the core ranking systems.
Think of FAQ Schema as a way of making your content easier for machines to understand, rather than a way of increasing your authority.
Better Content Understanding
Although FAQ Schema doesn’t improve rankings directly, it provides additional context about your content. By explicitly identifying questions and answers, you reduce ambiguity and make it easier for search engines to understand the relationships between different pieces of information on the page.
This can be particularly useful on pages where multiple topics are discussed or where customer questions are central to the content, such as service pages, product support documentation and knowledge bases.
The structured format also helps search engines distinguish genuine FAQs from headings, lists or other page elements that might otherwise require interpretation.
Eligibility for Search Features
Before Google’s 2023 changes, implementing FAQ Schema could make a page eligible for expandable FAQ rich results in Google Search. While that opportunity is now largely restricted to trusted government and health websites, the principle remains the same: structured data is primarily about eligibility, not entitlement.
Google decides whether to display enhanced search features based on its own quality signals and the search context. Adding valid FAQ Schema simply makes a page eligible where those features are supported—it does not guarantee they will appear.
Supporting AI-Powered Search
Structured data is also becoming increasingly relevant as search evolves beyond the traditional list of blue links. AI-powered search experiences, including Google’s AI Overviews and other generative search technologies, aim to understand content at a much deeper level.
While Google has not confirmed that FAQ Schema directly influences AI-generated answers, providing clear, structured and machine-readable information aligns with the direction of modern search. Well-organised content is generally easier for automated systems to interpret, connect with related entities and surface when it is relevant to a user’s question.
For that reason, implementing FAQ Schema should be viewed as part of a broader technical SEO strategy focused on improving content clarity and semantic understanding—not as a tactic for chasing ranking gains.
The Bottom Line
FAQ Schema is not a shortcut to higher rankings, and it never has been. Its value lies in helping search engines understand your content more accurately, making your pages eligible for supported search features and preparing your website for an increasingly AI-driven search ecosystem.
The businesses that continue to benefit from FAQ Schema are those using it to organise genuinely helpful information—not those expecting it to deliver an automatic SEO boost.
Where FAQ Schema Still Makes Sense
Although FAQ rich results are no longer widely displayed in Google Search, there are still many situations where implementing FAQ Schema is worthwhile. The key is to use it where it naturally reflects the purpose of the page rather than adding it simply because it was once considered an SEO best practice.
The most effective implementations are those that help organise information users are already looking for, while also making that information easier for search engines to interpret.
Support Centres and Help Articles
Support centres are one of the strongest use cases for FAQ Schema. Users visit these pages with specific questions, and the content is already structured around clear answers.
Examples include:
- Troubleshooting guides
- Account management questions
- Shipping and returns information
- Technical support documentation
- Frequently reported issues
Adding FAQ Schema reinforces the existing page structure and provides search engines with clear relationships between each question and answer.
Product FAQ Pages
Many ecommerce businesses answer common purchasing questions directly on product pages. These FAQs often cover information that doesn’t fit naturally into product specifications but is still important to customers.
Examples include:
- Delivery times
- Installation requirements
- Compatibility
- Warranty information
- Returns policy
- Product care and maintenance
When these questions are unique to the product and genuinely help customers make informed decisions, FAQ Schema can provide additional semantic context without adding unnecessary content.
Service Pages
Service-based businesses often receive the same questions from prospective customers before they enquire.
For example, a web design agency might answer questions such as:
- How long does a website project take?
- What’s included in a maintenance package?
- Do you work with businesses outside the UK?
- Can you migrate an existing website?
These questions support user decision-making while helping search engines better understand the services being offered. The FAQs should always be relevant to the specific service page rather than duplicated across every page on the website.
Documentation and Knowledge Bases
Software companies, SaaS platforms and technology providers frequently publish documentation that explains features, processes and troubleshooting steps.
FAQ Schema works well alongside:
- API documentation
- User guides
- Installation instructions
- Configuration walkthroughs
- Feature explanations
These resources are already highly structured, making them a natural fit for machine-readable markup.
Healthcare and Government Websites
Healthcare providers and government organisations remain the primary websites where Google still displays FAQ rich results.
These websites often publish authoritative information covering:
- Public services
- Medical guidance
- Eligibility criteria
- Legal requirements
- Official procedures
Because users depend on these pages for accurate, trustworthy information, Google continues to surface FAQ rich results more frequently in these sectors than in commercial industries.
Complex Service Pages
Some services involve multiple stages, technical terminology or regulatory requirements that naturally generate customer questions.
Examples include:
- Financial services
- Commercial insurance
- Legal services
- Manufacturing
- Industrial engineering
- B2B software solutions
Rather than forcing users to search elsewhere for answers, well-written FAQs can remove uncertainty and improve the overall user experience. Adding FAQ Schema helps reinforce this logical structure for search engines, even if no enhanced search result is displayed.
Focus on User Value First
The common theme across all of these examples is that the FAQs exist because they are genuinely useful—not because they provide another opportunity to insert keywords or structured data.
If visitors regularly ask the same questions before making a purchase, submitting an enquiry or using a product, those questions probably belong on the page. FAQ Schema simply helps search engines understand that structure more clearly.
In 2026, successful implementation isn’t about marking up every page on your website. It’s about identifying where questions naturally exist and using structured data to organise valuable information in a way that’s helpful for both users and search engines.
Where FAQ Schema Is Usually Wasted
One of the biggest mistakes businesses make is assuming that if FAQ Schema is beneficial on one page, it should be added everywhere. That mindset may have been common when FAQ rich results appeared frequently in Google Search, but today’s search landscape demands a far more selective approach.
Adding FAQ Schema to pages that don’t genuinely need it rarely provides any measurable SEO benefit. In many cases, it simply creates additional content to maintain while offering little value to users or search engines.
Every Blog Post
It’s common to see websites automatically append a FAQ section to every blog article, regardless of whether readers are actually asking those questions.
For example, an article explaining how to optimise Core Web Vitals might finish with generic questions such as:
- What is SEO?
- Why is SEO important?
- How do websites rank on Google?
These questions add little to the article because they aren’t specific to the topic being discussed. Instead of improving the page, they often dilute the quality of the content and interrupt the reader’s journey.
If an article naturally answers common questions that haven’t already been covered, then a FAQ section can be useful. Otherwise, it simply becomes unnecessary filler.
Keyword Stuffing
Some websites use FAQs as another opportunity to insert target keywords repeatedly.
Questions such as:
- Best web design company in Manchester?
- Affordable web design company in Manchester?
- Professional web design company in Manchester?
provide little value because they’re variations of the same query rather than genuine customer questions.
Google’s systems are increasingly effective at recognising manipulative or repetitive content. FAQs should answer real questions from customers, not act as another place to target keyword variations.
Hidden FAQs
Google’s structured data guidelines are clear: content marked up with FAQ Schema should also be visible to users.
Attempting to hide FAQs behind CSS, collapsed elements that are never intended to be opened, or content generated solely for search engines violates the purpose of structured data.
If a visitor can’t reasonably access the questions and answers, they shouldn’t be included in the schema markup.
Duplicate FAQs Across Hundreds of Pages
Another common issue is copying the same FAQ block across an entire website.
For example, a business might place identical questions about pricing, delivery or guarantees on every service page, regardless of whether they’re relevant to the specific service.
This creates several problems:
- Users repeatedly see the same information.
- Pages become less unique.
- Content maintenance becomes more difficult.
- Updating a single answer requires changes across numerous pages.
Where a question genuinely applies to every service, consider linking to a dedicated FAQ or help page rather than duplicating the same content throughout the site.
AI-Generated FAQ Sections With Little Value
Generative AI has made it easy to create FAQ sections in seconds, but quantity should never replace quality.
Many automatically generated FAQs simply restate information already covered in the article or produce generic questions that few users would actually ask.
Examples include:
- What is this article about?
- Why is this important?
- How can this help me?
These add little informational value and often make pages feel longer without making them more useful.
Instead, use customer enquiries, sales conversations, support tickets, search queries and tools such as Google’s “People Also Ask” as inspiration for questions that reflect genuine user intent.
The Hidden Cost of Overusing FAQ Schema
Beyond the lack of SEO benefit, excessive implementation creates an ongoing maintenance burden.
Every FAQ section needs to remain accurate as your products, services, pricing, policies and industry guidance evolve. If you’ve added FAQ Schema indiscriminately across hundreds of pages, even a small business update can become a time-consuming project.
A focused approach is far more sustainable. By implementing FAQ Schema only where it genuinely improves the page, you’ll spend less time maintaining structured data while providing a better experience for both users and search engines.
Ultimately, FAQ Schema should solve a problem, not create one. If the questions aren’t helping your audience make decisions or understand your content more clearly, they’re unlikely to provide meaningful SEO value either.
Best Practices for FAQ Schema in 2026
With Google no longer displaying FAQ rich results for most commercial websites, the goal of implementing FAQ Schema has shifted. Success is no longer measured by earning expandable listings in the SERPs but by creating clear, accurate and machine-readable content that improves the overall quality of your website.
Following current best practices will help ensure your structured data remains compliant with Google’s guidelines while providing long-term value.
Only Mark Up Visible Questions
Google expects any content included in FAQ Schema to be visible on the page. The questions and answers in your JSON-LD should match the content that users can actually read.
Avoid creating hidden FAQs solely for search engines or marking up content that isn’t displayed to visitors. Structured data should reflect the page—not extend it.
Write Unique, Helpful Answers
The best FAQ sections answer real questions in a clear and concise way. Rather than copying the same generic response across multiple pages, tailor each answer to the specific product, service or topic.
Ask yourself whether the answer genuinely helps a customer make a decision or solve a problem. If it doesn’t, it probably doesn’t belong in your FAQ section.
Avoid Duplicate FAQs Across Your Website
Reusing identical FAQ blocks on dozens or even hundreds of pages creates unnecessary duplication and increases maintenance.
Instead, write questions that are relevant to each page. Where the same information applies site-wide, consider linking to a dedicated FAQ or support page rather than repeating identical answers everywhere.
This approach keeps your content more useful for users while making each page more distinct.
Answer Genuine Customer Questions
One of the easiest ways to create valuable FAQs is to use the questions your customers already ask.
Good sources include:
- Sales enquiries
- Customer support tickets
- Live chat conversations
- Contact forms
- Product reviews
- Google’s “People Also Ask” results
- Internal site search data
These questions reflect genuine user intent, making them far more valuable than keyword-focused or AI-generated FAQs.
Validate Your JSON-LD
Even well-written FAQs won’t provide value if the structured data contains syntax errors or invalid properties.
Before publishing, validate your implementation using tools such as Google’s Rich Results Test and the Schema Markup Validator. These tools help identify missing fields, formatting issues and other problems that could prevent search engines from interpreting the markup correctly.
Validation should also be part of your website’s ongoing QA process whenever templates or plugins are updated.
Monitor Google Search Console
Although FAQ rich results are now uncommon for most websites, Google Search Console remains an important tool for monitoring structured data.
Regularly check for:
- Structured data errors
- Invalid items
- Warnings
- Indexing issues
- Changes after website updates
Fixing these issues promptly helps ensure your structured data continues to be recognised correctly.
Keep Your Schema Updated
Structured data should evolve alongside your website.
If you update product information, pricing, delivery details, policies or service offerings, make sure the corresponding FAQ content and schema remain accurate.
Outdated answers can create a poor user experience and reduce trust, even if the technical implementation is valid.
Focus on Quality, Not Quantity
The temptation to add FAQ Schema to every page is understandable, but it’s rarely the right approach in 2026.
Instead, prioritise pages where visitors genuinely benefit from additional context. A handful of well-researched, user-focused FAQ sections will usually provide more long-term value than hundreds of generic FAQs generated purely for SEO.
Ultimately, the best FAQ Schema implementations are almost invisible—they simply reflect high-quality content that already deserves to exist. Structured data should support your content strategy, not define it.
Common FAQ Schema Mistakes
Implementing FAQ Schema is relatively straightforward, but small technical mistakes can prevent search engines from interpreting your structured data correctly. In some cases, they may even cause your markup to be ignored altogether.
Here are some of the most common mistakes SEO professionals and website owners should avoid.
Hidden Content
Google’s structured data guidelines are clear: any questions and answers included in your FAQ Schema should also be visible to users on the page.
Avoid marking up:
- Hidden text
- Content loaded only for search engines
- FAQs that don’t appear in the visible page content
If users can’t reasonably access the information, it shouldn’t be included in your structured data.
Mismatched Markup
One of the most common implementation errors is when the structured data doesn’t match the visible content.
For example, your page might display:
Q: Do you offer free UK delivery?
But your JSON-LD contains:
Q: Do you offer worldwide shipping?
Even small differences between the page content and the schema can create inconsistencies. Your markup should always reflect exactly what users see.
Duplicate IDs
When FAQ Schema is generated automatically by themes or plugins, duplicate identifiers can sometimes be introduced.
Duplicate IDs may occur when:
- The same FAQ block is copied multiple times.
- Templates generate identical identifiers across pages.
- Multiple schema plugins output the same markup.
While visitors won’t notice this issue, it can make structured data harder for search engines to interpret and complicate debugging.
Invalid JSON
Because most FAQ Schema is written in JSON-LD, even a minor syntax error can invalidate the entire block.
Common issues include:
- Missing commas
- Incorrect brackets or quotation marks
- Invalid property names
- Missing required fields
- Broken nesting of questions and answers
Always validate your implementation before publishing. A schema validator can identify problems in seconds that might otherwise go unnoticed.
Outdated Plugins
Many WordPress themes and SEO plugins generate FAQ Schema automatically. However, plugins that haven’t been updated may continue using deprecated methods or produce markup that no longer follows Google’s recommendations.
Regularly update your plugins and periodically review the structured data they generate. Don’t assume that because a plugin worked a few years ago, it’s still producing optimal markup today.
Marking Promotional Content as FAQs
FAQ Schema should answer genuine questions—not advertise your products or services.
Poor examples include:
- Why are we the best agency in the UK?
- Why should you buy from us today?
- Why is our product better than everyone else’s?
These aren’t authentic customer questions and provide little informational value.
Instead, focus on questions users are actually asking, such as:
- How long does delivery take?
- What is included in the service?
- Do you offer ongoing support?
- Is there a warranty?
These are far more useful for both visitors and search engines.
Test Before You Publish
Even if your FAQ content is well written, technical errors can prevent search engines from understanding it correctly.
Before publishing, make it standard practice to:
- Validate your JSON-LD.
- Check that all questions and answers appear on the page.
- Ensure only one version of the FAQ Schema is being output.
- Confirm there are no duplicate or conflicting schema blocks.
- Re-test after updating your theme, SEO plugin or page builder.
A few minutes spent testing can prevent hours of troubleshooting later and helps ensure your structured data continues to support your technical SEO strategy effectively.
Should You Still Use FAQ Schema?
The answer for most websites is yes—but only where it adds genuine value.
FAQ Schema is no longer something that should be applied automatically to every page. Instead, it should be implemented strategically on pages where it helps users find answers and helps search engines understand the structure of your content.
Before adding FAQ Schema, work through the following checklist.
FAQ Schema Decision Checklist
Answer each question with Yes or No.
Question | Yes | No |
Does the page genuinely answer common customer questions? | ✅ | ❌ |
Are the questions based on real user enquiries rather than keyword variations? | ✅ | ❌ |
Are all questions and answers visible on the page? | ✅ | ❌ |
Is the FAQ content unique to this page? | ✅ | ❌ |
Will the FAQs genuinely help visitors make a decision or solve a problem? | ✅ | ❌ |
Can the content be kept up to date as products, services or policies change? | ✅ | ❌ |
Is the structured data technically valid and free from errors? | ✅ | ❌ |
Does adding FAQs improve the page instead of making it longer for the sake of SEO? | ✅ | ❌ |
How to Interpret Your Answers
Mostly Yes
You’re probably looking at a strong candidate for FAQ Schema. The questions are relevant, useful and sustainable, meaning the structured data is likely to support both users and search engines.
A Mix of Yes and No
Review whether a dedicated FAQ section is actually needed. It may be better to improve the existing content or create a standalone help page rather than forcing FAQs onto the page.
Mostly No
Skip FAQ Schema.
Adding structured data to pages without meaningful questions rarely provides value. Instead, focus on improving the page’s primary content, internal linking and overall user experience.
Think Beyond Rich Results
The biggest mindset shift since Google’s 2023 update is recognising that FAQ Schema is no longer about earning more space in the search results.
Instead, ask yourself:
- Does this help users find answers more quickly?
- Does it make my content easier for search engines to interpret?
- Would this FAQ still be worth publishing even if no rich result ever appeared?
If the answer is yes, then FAQ Schema is likely worth implementing.
A Practical Rule of Thumb
A simple way to decide is to imagine removing the schema markup entirely.
If the FAQ section would still improve the page because it answers genuine customer questions, then you’ve created valuable content that deserves structured data.
If the FAQ only exists because you hope Google might display it as a rich result, it’s probably unnecessary.
In 2026 and beyond, the most effective SEO strategies prioritise clarity, relevance and user experience. FAQ Schema should support those goals—not replace them. By implementing it selectively and maintaining high-quality, user-focused content, you’ll create pages that are easier for both people and search engines to understand, regardless of how Google’s search results continue to evolve.
Final Thoughts
FAQ Schema has evolved from being a tactic for earning larger search listings into a tool for creating better structured content. While Google’s 2023 updates significantly reduced the visibility of FAQ rich results for most commercial websites, they didn’t make FAQ Schema obsolete. Instead, they shifted the focus from chasing SERP features to improving how search engines understand and interpret your content.
For SEO professionals, agency owners and business owners, the takeaway is straightforward: implement FAQ Schema because it improves the quality and organisation of your website—not because you expect an immediate ranking boost or enhanced search result.
When your FAQs answer genuine customer questions, reflect the visible content on the page and are implemented using valid structured data, they contribute to a clearer, more machine-readable website. That benefits search engines today and positions your content for the continued evolution of AI-powered search experiences.
Rather than adding FAQ Schema to every page, take a selective approach. Prioritise pages where users naturally expect questions and answers, keep the content accurate and up to date, and ensure the structured data follows Google’s current guidelines.
Ultimately, the most effective SEO strategies are built around creating genuinely helpful content. FAQ Schema should enhance that content—not exist for its own sake. By focusing on quality over quantity, you’ll build a website that is easier for users to navigate, easier for search engines to understand and better prepared for whatever changes come next.
Free SEO Tools
Check out the Techomatic SEO FAQ Schema Generator tool: it’s free!