Yes. FAQPage schema is still relevant in 2026, and it matters more than it did three years ago. But the reason has changed.
In 2023, FAQ schema was valuable because Google showed it as a visual rich result. That feature is gone for most sites. What replaced it is bigger: AI search engines like ChatGPT, Perplexity, Google AI Overviews, and Claude all read FAQPage schema directly from your HTML and use it to build cited answers.
If you stopped implementing FAQ schema because you heard it was "dead," you gave up a competitive advantage at the worst possible time.
What actually happened in 2023
In August 2023, Google restricted FAQ rich results. The expandable accordion that appeared under search listings, showing your questions and answers directly in Google's results, was limited to government and health websites. Everyone else lost the visual feature.
Google made a specific, narrow change to a SERP feature. They did not stop reading FAQPage schema. They did not remove it from their structured data documentation. They did not deprecate the schema.org FAQPage type. They removed a display element.
But the message got simplified as it traveled through the SEO industry. Blogs framed it as a loss. Audit tools stopped flagging missing FAQ schema as an opportunity. Agencies told clients not to bother. The nuance, that Google still reads the schema even without the accordion, got buried. Within months, "Google reduced a SERP feature" became "FAQ schema is dead."
That misconception is still circulating in 2026. It is still wrong.
Where FAQ schema stands now
Here is the current status of FAQPage schema across the major search and AI platforms.
Google still indexes FAQPage schema. It still uses structured data to understand what your page is about and what questions it answers. The Rich Results Test at search.google.com/test/rich-results still validates FAQPage markup. Google's structured data documentation still lists FAQPage as a supported type. What Google stopped doing in 2023 was showing the accordion widget for most sites. That is a display change, not a data change.
ChatGPT
When ChatGPT retrieves a web page to answer a question, it extracts content and synthesizes a response. FAQPage schema gives it pre-structured question-and-answer pairs in a machine-readable format. The model does not need to parse paragraphs and guess where an answer starts or ends. The schema tells it exactly. OpenAI's GPTBot crawler documentation describes how the bot fetches and reads page content. FAQPage schema makes that content easier to extract and cite.
Perplexity
Perplexity generates answers with numbered citation links. It retrieves pages, reads their content, and synthesizes answers with source attribution. When a user asks a question that matches your FAQ entry, and your page has FAQPage schema, you are the easiest source to cite. Perplexity benefits from structured question-and-answer pairs it can extract cleanly without guessing.
Claude
Claude reads web content through its crawler. The same principle applies. Structured data reduces ambiguity and makes extraction reliable. FAQPage schema is one of the cleanest formats for question-answer extraction.
Google AI Overviews
Google AI Overviews synthesize answers from multiple sources. Pages with FAQPage schema that clearly answer specific questions are strong candidates for inclusion as cited sources, because the synthesis engine can extract the answer without interpretation.
The pattern is the same across every platform. FAQPage schema packages your content in the exact format these systems need to generate a cited answer: self-contained question-and-answer units with no ambiguity about what is being asked or answered.
Why almost nobody has it
This is what makes the opportunity unusual. The misconception that FAQ schema was dead caused widespread abandonment. Most websites removed it or never added it in the first place.
If you add FAQPage schema today, you are ahead of most of your competitors for question-based queries. The field is nearly empty because the SEO industry told everyone to stop bothering.
This is not a gap that requires budget or technical expertise to close. Adding FAQPage schema takes about 10 minutes per page. You write five to ten questions your customers actually ask, write direct answers, put them on the page as visible headings and paragraphs, and add the JSON-LD schema. Google provides a free validation tool. The whole process is documented step by step in our Google FAQ schema markup guide.
Should you implement FAQ schema?
If you are still on the fence, here is the decision framework.
You should implement FAQPage schema if your customers ask predictable questions. Hours, pricing, policies, availability, service areas. If you run a local business, a service company, or a niche B2B firm, your customers are asking AI search engines these questions right now. FAQ schema positions you as the cited answer.
You can skip it if your site has no question-based intent. A pure portfolio site with no FAQ content does not need it. You can also skip it if your robots.txt blocks AI crawlers, because nothing else matters until you fix that. And if you are a major brand whose entity is already deeply embedded in AI training data, FAQ schema is lower priority because the models already know who you are.
For most businesses, the answer is simple. Implement it. The cost is low. The competitive advantage is large. The channel is growing.
What to do right now
- Write five to ten questions your customers actually ask. Check your support emails, your reviews, and your Search Console queries for the real phrasing people use.
- Write direct answers. Start with the core fact. Yes or no first, then detail. Keep each answer to 40 to 60 words for simple questions.
- Put the questions and answers on your page as visible HTML. Use H2 or H3 headings for questions, paragraphs for answers.
- Add FAQPage JSON-LD schema that matches the visible content. Wrap it in a script tag with type="application/ld+json".
- Test with Google's Rich Results Test to confirm the schema is valid.
- Check that AI crawlers are not blocked in your robots.txt. Look for GPTBot, PerplexityBot, ClaudeBot, and Google-Extended in Disallow rules. If any are blocked, remove the block.
For the full implementation walkthrough with code examples, see our FAQ schema markup guide. For the evidence on how FAQ sections affect AI search citation rates, see our analysis of FAQ sections and AI search performance.
Frequently asked questions
Is FAQ schema dead in 2026?
No. Google restricted the FAQ rich result (the visual accordion in search results) to government and health websites in August 2023. They still read and index FAQPage schema. AI search engines including ChatGPT, Perplexity, Google AI Overviews, and Claude all read FAQPage schema from your HTML to build cited answers. The schema is more valuable now than when Google showed the accordion, because AI search is a faster-growing channel.
Does Google still use FAQ schema?
Yes. Google's structured data documentation still lists FAQPage as a supported type. The Rich Results Test still validates it. Google uses structured data to understand page content, and that understanding feeds into how Google generates AI Overviews. What Google stopped doing was showing the expandable accordion widget for most sites. The underlying data pipeline is unchanged.
Will adding FAQ schema help with AI search?
Yes. FAQPage schema gives AI search engines pre-structured question-and-answer pairs they can extract without interpretation. When a user asks ChatGPT or Perplexity a question that matches your FAQ entry, having the schema makes you the easiest source to cite. Most websites do not have FAQPage schema, so adding it puts you ahead of nearly all competitors for question-based queries.
How long does it take to add FAQ schema?
About 10 minutes per page once you have your questions and answers written. The JSON-LD format is straightforward, and Google provides a free validation tool. WordPress users can use the Yoast or Rank Math FAQ blocks, which generate the schema automatically.
What is the difference between FAQ schema and FAQ rich results?
FAQ rich results were a visual feature in Google search: the expandable accordion that showed your questions and answers under your listing. Google restricted this to government and health sites in 2023. FAQ schema (FAQPage schema) is the underlying structured data in your HTML. The rich result was a display layer on top of the schema. Google removed the display layer but kept reading the data. AI search engines never used the display layer. They read the schema directly.
Want to know whether your site has FAQ schema and every other signal that affects AI search visibility? Run a free audit at parceit.com. No signup required. You see your full score and every issue in under 60 seconds.