# Do FAQ pages help you get cited by AI?

> FAQ pages used to win extra space in Google results. That perk is gone. Yet AI assistants still lean on short question-and-answer passages when they build an answer. Here is what Google and Microsoft actually say about FAQs and schema today, why a real FAQ still earns quotes, and how to write answers an AI can lift word for word.

Updated October 12, 2026 · AI Syndicate team · https://www.aisyndicate.com/blog/do-faq-pages-help-ai-citations/

**Quick answer:** Partly. The **questions and answers** help; the FAQ markup mostly doesn't. Google stopped showing FAQ rich results on **May 7, 2026**, and says there is no special schema needed for AI Overviews or AI Mode. Microsoft says assistants can lift clear question-and-answer pairs word for word. So a real FAQ, built from customer questions and answered fully on the page, is still worth writing.

**Our take:** Markup was never the point of an FAQ. The questions you choose are. Google has retired the FAQ rich result and says its AI answers need no special code. What still gets quoted is the thing the markup only labelled: a question a buyer really asks, with a short, complete answer that makes sense when lifted out alone. So we build FAQs from calls and emails, write every answer to stand by itself, and treat the code as a bonus, not the work.

## What are the key facts about FAQ pages and AI citations?

| Fact | Detail | Source |
| --- | --- | --- |
| 2023 cutback | From August 2023, FAQ rich results were shown only for "well-known, authoritative government and health websites" | Google |
| 2026 removal | FAQ rich results stopped appearing in Google Search from May 7, 2026; the docs were removed June 15, 2026 | Google |
| Leftover markup | "Structured data that's not being used does not cause problems for Search" | Google |
| AI Overviews and AI Mode | "No special schema.org structured data that you need to add" | Google |
| Writing for AI | "You don't need to write in a specific way just for generative AI search" | Google |
| Q&A pairs | Assistants "can often lift these pairs word for word" | Microsoft Bing |
| Hidden answers | "Don't hide important answers in tabs or expandable menus" | Microsoft Bing |
| Quote size | Claude's web search citations return up to 150 characters of cited text | Anthropic |
| OpenAI and Perplexity | Their crawler pages give no FAQ or schema advice: unconfirmed either way | OpenAI, Perplexity |
| Mass-made pages | Generating many pages "without adding value for users" is scaled content abuse | Google |

## Does Google still show FAQ rich results?

No. Google stopped showing them for everyone in 2026. It happened in two steps.

**August 2023.** Google announced it was "reducing the visibility of FAQ rich results." From then on, FAQ results built from FAQPage structured data were shown only for "well-known, authoritative government and health websites." For all other sites, the result "will no longer be shown regularly." [Google](https://developers.google.com/search/blog/2023/08/howto-faq-changes)

**May and June 2026.** Google's documentation changelog records a deprecation notice on May 8, 2026, saying the feature "will no longer appear in Google Search starting May 7, 2026." On June 15, 2026, Google removed the FAQ rich result documentation because the feature "is no longer shown in Google Search results." The old FAQPage help page now redirects to that changelog entry. [Google](https://developers.google.com/search/updates)

Do you need to delete old FAQ markup? Google's 2023 post said there's "no need to proactively remove it," because unused structured data "does not cause problems for Search, but also has no visible effects." [Google](https://developers.google.com/search/blog/2023/08/howto-faq-changes) We found no newer Google statement that changes that.

> **In plain words:** FAQ markup no longer buys you anything visible in Google. If it's already on your site, it can stay. Don't pay anyone to add it for Google's sake.

## Do I need FAQ schema to show up in Google AI Overviews?

No. Google says there are "no additional requirements to appear in AI Overviews or AI Mode," and "no special schema.org structured data that you need to add." A page needs to be indexed and eligible to show with a snippet. The same page lists "making sure your structured data matches the visible text on the page" as a general good practice, not an AI requirement. [Google](https://developers.google.com/search/docs/appearance/ai-features)

Google's AI optimization guide goes further. It says "structured data isn't required for generative AI search." It also says "you don't need to write in a specific way just for generative AI search," and there's "no requirement to break your content into tiny pieces." It still recommends structured data because it "helps with being eligible for rich results." [Google](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) Since FAQ is no longer one of those rich results, FAQPage markup has no documented Google benefit left.

What Google does ask for is ordinary good writing. Its helpful content guide asks whether a page gives "a substantial, complete, or comprehensive description of the topic," and whether readers will feel "they need to search again." [Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) A good FAQ answer passes both tests. A one-line teaser answer fails them.

For the bigger picture on markup, see [does schema markup help AI search?](/blog/schema-markup-ai-search/)

## Does Bing or Microsoft Copilot use FAQ content?

Microsoft is the one search company that openly recommends question-and-answer formats for AI answers. In an October 8, 2025 post, a principal product manager at Microsoft Bing wrote that "direct questions with clear answers mirror the way people search," and that assistants "can often lift these pairs word for word into AI-generated responses." [Microsoft](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers)

The same post describes schema as code that "helps search engines and AI systems understand your content." It names FAQ as one label schema can apply, but gives no separate FAQ schema advice. It also asks for:

- **One- to two-sentence answers** that directly address the question.
- **"Self-contained phrasing"**: sentences that make sense even when pulled out of context.
- **Answers in plain view.** "Don't hide important answers in tabs or expandable menus," because "AI systems may not render hidden content."

That last point matters for FAQ pages, which are often built as click-to-open accordions. [Microsoft](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers)

You may have read that a Bing executive said at a March 2025 conference that schema helps Microsoft's language models. We could not open a readable copy of the original report, so we don't rely on it here. Treat it as **unconfirmed** by us. For more on Bing, see [how Bing feeds AI answers](/blog/bing-and-ai-answers/).

## Why do AI answers quote question-and-answer passages?

Because an AI answer is built from small pieces, and a good FAQ answer is already a small, complete piece.

Anthropic's developer docs show how small. When Claude answers with web search, each citation carries a `cited_text` field of "up to 150 characters of the cited content." [Anthropic](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-search-tool) For documents, Claude's citations feature chunks plain text and PDFs into sentences, so it can "cite a single sentence" or chain several together. [Anthropic](https://platform.claude.com/docs/en/build-with-claude/citations) A 150-character quote is about one or two short sentences. If your answer's key fact sits in sentence four, after the warm-up, it is harder to quote cleanly.

Microsoft says the same thing in plainer words: assistants can lift question-and-answer pairs "word for word." [Microsoft](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers)

OpenAI and Perplexity publish no formatting advice. Their crawler pages cover bots and robots.txt only, with nothing on FAQs or schema. [OpenAI](https://developers.openai.com/api/docs/bots) [Perplexity](https://docs.perplexity.ai/guides/bots) So any claim that ChatGPT or Perplexity "prefers FAQ schema" is **unconfirmed** by those companies.

Google, for its part, says its AI "can understand synonyms and general meanings," so you don't need to repeat odd keyword phrasings. [Google](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)

**Our advice, not a vendor statement:** the format helps because it forces two good habits: a heading that matches how a person asks, and an answer that starts with the answer. You can get the same effect with question-style headings on any page, which is how this guide is built.

## What is the difference between a real FAQ and a stuffed FAQ?

A real FAQ answers questions customers actually ask, fully, on the page. A stuffed FAQ is a list of keyword phrases dressed up as questions, with thin answers that exist to catch searches.

| | Real FAQ | Stuffed FAQ |
| --- | --- | --- |
| Where questions come from | Calls, emails, sales chats, reviews | Keyword tools and autocomplete lists |
| Answer length | As long as the answer needs, answer first | One vague line, or a link to "contact us" |
| Facts | Prices, times, areas, limits, steps | General claims anyone could make |
| Placement | Visible text on the page | Hidden in accordions or only in code |
| Scale | A few dozen honest questions | Hundreds of near-duplicate pages |

Google's rules touch the stuffed version in three places:

- **Helpful content.** Google asks whether content is "primarily made to attract visits from search engines." [Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)
- **Scaled content abuse.** Its spam policy covers "many pages" made to manipulate rankings, including using AI tools "to generate many pages without adding value for users." [Google](https://developers.google.com/search/docs/essentials/spam-policies) A city-by-city FAQ page farm with the same answers swapped around fits that description.
- **Structured data rules.** "Don't mark up content that is not visible to readers of the page." A structured data issue "can result in a manual action." [Google](https://developers.google.com/search/docs/appearance/structured-data/sd-policies)

**Our advice, not a vendor statement:** if you can't name a real customer who asked the question, cut it.

## How do I write FAQ answers that AI will quote?

Lead with the answer, keep the first sentence true on its own, and include one specific fact.

1. **Use the customer's words in the question.** Write "How much does a roof inspection cost?" not "Roof inspection pricing information." Our guide to [choosing prompts to track](/blog/how-to-choose-prompts-to-track/) shows how to collect real buyer wording.
2. **Answer in the first sentence.** Start with Yes, No, a number, or a name. Microsoft asks for one- to two-sentence direct answers. [Microsoft](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers)
3. **Make it stand alone.** Name the thing instead of writing "it" or "this." The first sentence should still be true if it's the only line an assistant quotes.
4. **Add a specific detail.** A price range, a time frame, a service area, a limit. Specific facts give an assistant something worth citing.
5. **Then explain.** After the direct answer, add the conditions, exceptions and next steps a customer needs. Google rewards complete answers, not short ones. [Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)
6. **Keep it visible.** Show answers as plain text, not only inside click-to-open panels. [Microsoft](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers)
7. **Keep it current.** Change the answer the day your price or policy changes. An old answer quoted by an AI is worse than no answer.

**Example.** Weak: "Pricing depends on many factors. Contact us to learn more." Strong: "A standard roof inspection costs $150 to $250 for a single-family home in our area. Homes over 3,000 square feet or with steep roofs cost more, and we quote those after a photo review." (Illustrative numbers.)

Should you add FAQPage markup on top? It does no harm if it matches the visible text exactly. It no longer earns a Google rich result, so it is optional. (Our advice.)

## What should be on my FAQ checklist for AI search?

| Check | Done when | Source |
| --- | --- | --- |
| Real questions | Every question came from a customer call, email, chat or review | Google; Our advice |
| Answer first | The first sentence answers the question with no warm-up | Microsoft |
| Self-contained | The first sentence still makes sense if quoted alone | Microsoft |
| Specific fact | Each answer has a price, time, place, limit or step | Our advice |
| Complete | A reader would not need to search again | Google |
| Visible | Answers show as plain text, not only in tabs or accordions | Microsoft |
| Markup matches | Any FAQPage markup repeats the visible text exactly, or is removed | Google |
| No page farms | No near-duplicate FAQ pages made just to catch searches | Google |
| Kept current | Answers updated when prices, hours or policies change | Our advice |

## How do I check whether my FAQ answers are being cited by AI?

Ask the assistants the same questions your FAQ answers, and look at what they cite.

Start with your five most common customer questions. Type each one into ChatGPT, Google AI Mode, Perplexity, Copilot and Claude, worded the way a customer would say it. Note whether your page is cited, and whether the AI repeats your answer correctly. If an AI gets a fact wrong, the fix is usually a clearer first sentence on your page, not more markup.

Our [Prompt Simulator](/prompt-simulator/) runs those questions across the AI engines at once and shows which sources each one cites, so you can compare before and after you rewrite an answer. Our free [AI visibility check](/#tool) also fetches your pages the way AI crawlers do and flags pages that block bots or arrive empty. To decide which questions to keep checking each week, see [how to choose prompts to track](/blog/how-to-choose-prompts-to-track/).

## FAQ

### Does FAQ schema help with ChatGPT citations?

OpenAI has not said. Its crawler page gives no schema or FAQ advice. What is documented elsewhere is that clear question-and-answer pairs are easy for assistants to lift, so the visible answer matters more than the code. [OpenAI](https://developers.openai.com/api/docs/bots) [Microsoft](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers)

### Are FAQ rich results gone from Google?

Yes. Google limited them to well-known government and health sites in August 2023, then stopped showing them in Google Search from May 7, 2026, and removed the documentation on June 15, 2026. [Google](https://developers.google.com/search/blog/2023/08/howto-faq-changes) [Google](https://developers.google.com/search/updates)

### Should I remove FAQPage markup from my site?

You don't have to. Google says structured data that isn't used "does not cause problems for Search." Just make sure any markup matches the visible text on the page. [Google](https://developers.google.com/search/blog/2023/08/howto-faq-changes) [Google](https://developers.google.com/search/docs/appearance/structured-data/sd-policies)

### Do I need schema to appear in Google AI Overviews?

No. Google says there is no special schema.org structured data needed for AI Overviews or AI Mode. A page must be indexed and eligible to show with a snippet. [Google](https://developers.google.com/search/docs/appearance/ai-features)

### Are FAQ accordions bad for AI?

They can be. Microsoft Bing advises against hiding important answers in tabs or expandable menus, because AI systems may not render hidden content. Show key answers as plain text. [Microsoft](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers)

## Sources

1. [Changes to HowTo and FAQ rich results](https://developers.google.com/search/blog/2023/08/howto-faq-changes) — Google Search Central. Read Oct 12, 2026.
2. [Latest Google Search documentation updates](https://developers.google.com/search/updates) — Google Search Central. Read Oct 12, 2026.
3. [AI features and your website](https://developers.google.com/search/docs/appearance/ai-features) — Google Search Central. Read Oct 12, 2026.
4. [AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central. Read Oct 12, 2026.
5. [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central. Read Oct 12, 2026.
6. [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies) — Google Search Central. Read Oct 12, 2026.
7. [General structured data guidelines](https://developers.google.com/search/docs/appearance/structured-data/sd-policies) — Google Search Central. Read Oct 12, 2026.
8. [Optimizing Your Content for Inclusion in AI Search Answers](https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers) — Microsoft Bing. Read Oct 12, 2026.
9. [Web search tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-search-tool) — Anthropic. Read Oct 12, 2026.
10. [Citations](https://platform.claude.com/docs/en/build-with-claude/citations) — Anthropic. Read Oct 12, 2026.
11. [Overview of OpenAI Crawlers](https://developers.openai.com/api/docs/bots) — OpenAI. Read Oct 12, 2026.
12. [Perplexity Crawlers](https://docs.perplexity.ai/guides/bots) — Perplexity. Read Oct 12, 2026.