FAQ Schema in 2026: What Still Works for AI Citations

Written by: Content & GEO Research

Fastlook Team

Posted: 10/11/20265 min read

Google stopped displaying FAQ rich results in 2026, so many teams now ask whether FAQ schema is worth maintaining at all. The answer depends on who you expect to read the markup. For human searchers, the expanded listing is gone; for machines, including AI answer engines, structured question-and-answer data still clarifies what a page says.

Quick answer

Yes, as a machine-readable signal. **Rank Math reports Google ended FAQ rich result display in 2026**, but the structured question and answer data still helps AI platforms and crawlers understand the page. Its value now lies in clarity and eligibility for certain features, not in the expanded listing.

Topic: faq schema
Last updated: Nov 10, 2026
Read time: 5 min

Key Takeaways

Yes, but for a different reason than before.
FAQ schema is structured markup that AI-driven search features can read.
FAQPage markup is structured data that describes a list of questions and answers on a page.
A valid FAQPage JSON-LD block requires a mainEntity array of Question items.
FAQ schema is implemented with a JSON-LD block that Google's Rich Results Test can validate.

How it works: blog guide

1
Key Takeaways
2
What FAQ schema is and how it differs from QAPage markup
3
How does FAQ schema affect AI Overviews, LLMs, and voice search?
4
Where can FAQ schema go, and what content rules apply?
5
How do you build the JSON-LD for FAQ schema?
6
How do you implement and validate FAQ schema on WordPress, Shopify, or plain HTML?

What FAQ schema is and how it differs from QAPage markup

Yes, but for a different reason than before. According to Rank Math, Google ended support for FAQ rich result display in 2026, so the expanded listing with questions beneath a search result no longer appears. However, FAQ schema markup remains useful because it states questions and answers in a machine-readable form that AI platforms can parse.

Website owners should plan for the loss of the click-through lift that SEOClarity associated with expanded listings. For example, a brand should treat FAQ schema as a content-understanding signal rather than a visual search feature. Specifically, the markup helps AI platforms interpret the page's question-and-answer content accurately.

How does FAQ schema affect AI Overviews, LLMs, and voice search?

FAQ schema is structured markup that AI-driven search features can read. Neil Patel reports that Google's AI Overviews and other LLM-driven features draw answers from FAQ schema. Specifically, Patel observes the markup can raise visibility in People Also Ask and AI-driven results even when rankings stay flat.

However, this is a practitioner's observation, not a guarantee. No public Google statement in these sources confirms how AI Overviews weight FAQ markup. Rank Math adds that FAQ schema can make a site eligible for a Google Assistant voice search action.

For example, a site with FAQ markup may become a source of answers for voice queries. Citation gains in ChatGPT or Perplexity are not documented in the sources reviewed, so measure your own results.

Where can FAQ schema go, and what content rules apply?

FAQPage markup is structured data that describes a list of questions and answers on a page. It can sit on any page that shows real questions and answers, not only a dedicated FAQ page.

Sanctuary MG notes that Google supports links inside answers to other pages on the same site. However, the rules are strict. According to SEOClarity, summarising Google's documentation, each question requires a single answer. Specifically, the markup must describe content visible to the user on that page.

SEO Bot AI adds that markup should cover only FAQs visibly present on the page. Hidden text, invented questions, or answers that exist only in the code violate these rules and risk being ignored.

How do you build the JSON-LD for FAQ schema?

A valid FAQPage JSON-LD block requires a mainEntity array of Question items. Each Question needs a name holding the full question text and an acceptedAnswer object containing the answer text. According to Schema App, these are the required properties, and JSON-LD is the recommended deployment format.

For example, a minimal FAQPage block declares the context, the FAQPage type, and one Question inside mainEntity. The name and text values in the JSON-LD must match the visible page copy exactly. The JSON-LD should never contain wording that the reader cannot see on the page. Validate the finished FAQPage block with Google's Rich Results Test before publishing, as Google recommends.

How do you implement and validate FAQ schema on WordPress, Shopify, or plain HTML?

FAQ schema is implemented with a JSON-LD block that Google's Rich Results Test can validate. Neil Patel reports that FAQ schema can be implemented in under 30 minutes using simple tools or plugins, with JSON-LD as the recommended format. On WordPress, Rank Math and similar SEO plugins generate the block from a question-and-answer field.

On Shopify, add the JSON-LD to the theme template for the page type, or use an app that outputs it. On plain HTML, paste the script into the head or body of the page. Then run the URL through Google's Rich Results Test. Schema App notes that validation should be part of every deployment.

Sources & further reading

The specific figures and claims on this page are grounded in the following sources, reviewed at the time of writing:

Frequently asked questions

Does FAQ schema still help after Google removed FAQ rich results?

Yes, as a machine-readable signal. **Rank Math reports Google ended FAQ rich result display in 2026**, but the structured question and answer data still helps AI platforms and crawlers understand the page. Its value now lies in clarity and eligibility for certain features, not in the expanded listing.

Does schema markup help with AI search citations?

Schema markup can support AI citations by making questions and answers explicit. However, the sources reviewed do not prove that ChatGPT or Perplexity cite FAQ markup directly. Neil Patel reports that AI Overviews draw on FAQ schema, which is a practitioner observation rather than a confirmed mechanism. Specifically, measure citations on your own pages before assuming a lift from the markup.

What is the difference between FAQPage and QAPage schema?

FAQPage applies to a page with a list of questions, each with one authoritative answer. QAPage applies to a single question that receives multiple user-submitted answers, such as a forum thread. Schema App recommends choosing the type that matches how many answers each question actually has.

Can FAQ schema go on a page that is not a dedicated FAQ page?

Yes. According to Sanctuary MG, FAQPage markup can be placed on any page containing questions and answers. Google also supports links within answers to other pages on the same site. However, the questions must be visible to users on that page.

What properties does valid FAQPage JSON-LD require?

Valid FAQPage JSON-LD requires a mainEntity array of Question items. Specifically, each Question needs a name containing the full question text and an acceptedAnswer. Schema App identifies these as the required properties and recommends JSON-LD deployment.

How long does it take to add FAQ schema?

Neil Patel reports FAQ schema can be implemented in under 30 minutes using simple tools or plugins. However, real time depends on how many questions you mark up. For example, a page with many questions takes longer. Specifically, implementation is faster when your CMS already supports structured data fields.

How do I validate FAQ schema?

Run the page URL through Google's Rich Results Test after deployment. Check that each Question and acceptedAnswer parses without errors. According to Schema App, validation should be a standard step. However, recheck the markup after any template or content change, because edits can break it.

Which questions should an FAQ include to avoid duplicate or thin markup?

Include only distinct questions that users actually ask, each with one clear answer that matches visible page text. **Avoid repeating the same question across multiple pages**. Padding the list with filler questions creates thin markup. According to SEO Bot AI, markup should reflect only FAQs visibly present on the page.

Faq Schema