FAQ Page SEO in 2026: What Still Works After FAQ Schema Ended

FAQ page SEO in 2026 comes down to writing answers people need, as plain text on the page, because FAQ rich results are gone. Google stopped showing them on May 7, 2026, so FAQPage markup no longer changes how a page looks in Search, and no study shows that FAQ formatting or markup gets a page cited by AI.

FAQ content still earns its place. It answers buying questions, it is ordinary indexable text that can rank for the questions it answers, and a good FAQ is the one place you state each fact once. This guide covers what changed, what to do with your existing markup, how to build an FAQ page that holds up, and how to check that AI crawlers can read it.

What changed: the end of FAQ rich results

FAQ rich results, the expandable questions under a search listing, were wound down in two steps over three years. Many guides that still rank for this topic describe only the first step.

The 2023 change is in Google's announcement of the HowTo and FAQ changes; the 2026 entries are in the Search Central documentation changelog. As of October 2026, Google's structured data gallery lists 25 supported features, and FAQ is not one of them.

Should you remove FAQ schema?

There is no need. Google's 2023 post says: "While you can drop this structured data from your site, there's no need to proactively remove it. Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search."

There is also no reason to add it. Google's guide to its generative AI features says "Structured data isn't required for generative AI search," and the largest controlled test of schema and AI citations we found, Ahrefs' study of 1,885 pages, found no lift across all schema types pooled, FAQ included.

One case where you should remove it: markup that describes questions and answers not visible on the page. Google's structured data policies say "Don't mark up content that is not visible to readers of the page," and that rule outlived the rich result.

Do FAQ pages help AI search?

Nobody has shown that the format helps. There is no evidence either way that a question-and-answer layout makes AI more likely to use a page, and the two big operators disagree without data.

• Google: you "don't need to write in a specific way" for generative AI search, and "There's no requirement to break your content into tiny pieces for AI to better understand it."
• Microsoft: its Microsoft Advertising blog post of October 8, 2025 says Q&A pairs can often be lifted "word for word into AI-generated responses" and advises "Use schema, clear headings, and modular layouts." It publishes no test or data.
• A lab study: a 252,000-trial study across six language models found that "formatting-only edits have little impact," while "topical relevance and list position are the biggest drivers of being cited first."

The same study found that "including explicit price information and a recent timestamp also helps consistently." Note the setup: two candidate sources placed directly in the model's context, not a live search. It is a reason to state prices plainly, and to keep any date you show current, not proof that an FAQ page gets you found.

So an FAQ page helps AI the way any accurate page does. If the answer is correct, readable in the raw HTML, and not blocked, it is one more place a model can read the right fact.

What FAQ content is actually good for

• Answering buying questions before they become sales calls. Price, contract terms, integrations, security, cancellation.
• Stating each fact once. When your site states a price three different ways, the FAQ answer can be the version every other page is checked against.
• Ranking for question queries. A clear answer to "does X integrate with HubSpot" is ordinary text that can rank for that question like any other page.
• Cutting support load. The questions your support team answers every week belong on the page, in their words.
• Routing readers. Each answer can link to the page that covers it in depth.

Standalone FAQ page or FAQ sections on each page?

Most sites need a short section on the pricing page and one standalone page for company-wide questions. Our guide to pricing page GEO covers the pricing side in detail.

FAQ page best practices

1. Source questions from real people. Support tickets, sales call notes, your on-site search log, Search Console queries and Google's "People also ask" box. Skip questions nobody asks.
2. Answer in the first sentence. Then add one or two sentences of detail. Most answers need two to four sentences.
3. One fact per answer, with a date if it changes. "As of October 2026, the Team plan costs $119 per month" can be checked; "affordable plans for every team" cannot.
4. Use the same words everywhere. If the pricing page says "$119/month, billed monthly," the FAQ says the same and links to it.
5. Put the answers in the HTML. Accordions keep the text in the source, which crawlers that do not run scripts can still read. Microsoft still advises "Don't hide important answers in tabs or expandable menus," so keep your most important answers open. Answers fetched by JavaScript when someone clicks are invisible to crawlers that do not run scripts; Vercel found in December 2024 that ChatGPT's and Claude's crawlers fetch JavaScript files but "don't execute them."
6. Do not hide answers by accident. Bing says content marked data-nosnippet is "excluded from snippets and AI summaries" (Bing, October 2025), and Google says nosnippet applies to AI Overviews and AI Mode.
7. Write questions as headings so a reader can scan them, with the answer as the paragraph underneath.
8. Review when a fact changes, not on a calendar. Tie the FAQ to your price and plan changes. Changing a date without changing an answer fixes nothing; see why in our post on content freshness.

An FAQ template that stays accurate

Plain HTML, with the answer in the source. Swap in your own facts:

<h2>Pricing questions</h2>

<h3>How much does Example Analytics cost?</h3>
<p>As of October 2026, Starter costs $39 per month and Team costs
$119 per month, billed monthly. Enterprise is priced on request.
<a href="/pricing">See every plan and its limits</a>.</p>

<h3>Can I cancel at any time?</h3>
<p>Yes. Monthly plans end at the close of the current billing period,
and there is no cancellation fee.</p>

<details>
  <summary>Does it integrate with HubSpot?</summary>
  <p>Yes. The HubSpot integration syncs events to contact records
  every 15 minutes on all paid plans.</p>
</details>

The details element folds the answer away for readers, but the text is still in the HTML a crawler receives. That is the difference between a collapsed answer and a missing one.

How to check AI crawlers can read your FAQ

1. View the source. Press Ctrl+U on the FAQ page and search for one sentence from an answer. If it is not there, the answer is loaded by JavaScript.
2. Request the page as a crawler. The command below asks for your page with the user agent of OpenAI's search crawler and prints the status code. A 200 is a pass; a 403 or a challenge page means your firewall is turning the bot away.
3. Check for snippet blocks. Run curl -sI https://www.example.com/faq and look for an X-Robots-Tag header, then search the source for nosnippet and noindex.
4. Check robots.txt per bot. OAI-SearchBot, PerplexityBot and Claude-SearchBot each need to be allowed. OpenAI says sites opted out of OAI-SearchBot "will not be shown in ChatGPT search answers" (OpenAI crawler documentation).

curl -s -o /dev/null -w "%{http_code}" -A "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36; compatible; OAI-SearchBot/1.4; +https://openai.com/searchbot" https://www.example.com/faq

One honest limit on step 2: a firewall that verifies crawlers by IP address will treat your test differently from the real bot, so this catches user-agent rules, not IP rules. OpenAI's ChatGPT search help page says eligibility needs both: robots.txt permission and a host or CDN that "allows traffic" from its published IP addresses.

For the rest of the page around your FAQ, the same evidence standard is in our guides to schema markup for AI and how to optimize content for AI search.

Frequently asked questions

Is FAQ schema deprecated?

The rich result is. Google stopped showing FAQ rich results on May 7, 2026, and removed the documentation on June 15, 2026. The FAQPage type still exists on schema.org, but it no longer produces anything visible in Google Search.

Should I remove FAQ schema from my site?

You do not have to. Google says structured data that is not being used "does not cause problems for Search." Remove it only if it describes questions and answers that are not visible on the page, and do not add new FAQPage markup.

Do FAQ pages help AI search?

No study shows Q&A layout or FAQ markup earns AI citations; the closest lab test found that reorganizing dense paragraphs into sections made little difference. An FAQ helps the way any page helps: when its answers are accurate, in the raw HTML and reachable by AI crawlers.

Are FAQ pages good for SEO?

They are good for readers, and that is what makes them worth having. An answer to a real question is ordinary text that can rank for that question. The extra listing space FAQ markup used to earn is gone.

How many questions should an FAQ page have?

As many as real customers ask, and no more. Start with the questions your support and sales teams answer every week, and cut any question you invented to fill the page.

To find which facts AI gets wrong about your brand, so you know which answers your FAQ needs most, run a free 99Visibility audit and its hallucination detection will flag them.