Content and blogging
FAQ page SEO after Google dropped FAQ rich results
Written by the Top SEO Experts Team
Reviewed by Ritik NamdevLast updated 19 min read
Quick answer
Google stopped showing FAQ rich results on May 7, 2026, so FAQ markup no longer earns dropdown answers under your listing. FAQ page SEO still matters because a good FAQ settles buyer objections, covers question-style searches, and gives readers short, self-contained answers. Write it for the customer first and treat markup as optional.
What did Google change about FAQ rich results?
Google ended the FAQ rich result in May 2026. Its Search Central changelog (accessed 22 Oct 2026) records a May 8 notice that the feature “will no longer appear in Google Search starting May 7, 2026.”
On June 15 the documentation came down, with the note that the feature “is no longer shown in Google Search results.”
- August 2023Google's blog archive lists a post about changes to HowTo and FAQ rich results. We could not open its body.
- May 7, 2026The date the FAQ rich result stopped appearing in Google Search.
- May 8The changelog records the notice.
- June 15The documentation came down, with a note that the feature is no longer shown.
What do we know, and what can’t we confirm?
Google’s blog archive also lists an August 2023 post titled “Changes to HowTo and FAQ rich results.” We could not open its body, so we do not restate it.
Google’s search gallery of supported structured data (last updated 16 Oct 2026) does not list an FAQ feature.
We could not confirm what happens to any FAQ report in your Search Console property, so check your own account.
Did the markup rules change?
The markup rules did not loosen with the feature. Google’s general structured data guidelines still tell site owners not to mark up content readers cannot see.
Watch out Spammy markup can still draw a manual action, which removes rich result eligibility but does not affect ranking in web search.
What do the key terms mean?
Here are the terms this post uses, in plain words. These are common meanings, not Google rules.
| Term | Plain meaning |
|---|---|
| FAQ rich result | The expandable dropdown of answers under a search listing |
| FAQPage markup | Code that tells search engines a page holds questions and answers |
| Structured data | Code that labels what the content on a page is |
| Snippet-eligible | Allowed to show a text snippet in search results |
| Long-tail query | A longer, more specific search, often a full question |
| Manual action | A penalty a Google reviewer applies by hand to a site |
Keep these apart. The rich result, the markup and the content are three different things.
- The rich resultA display feature, and it is gone.
- The markupCode, and the rules about it still apply.
- The contentWhat readers see, and it still does its job.
Should you remove FAQ schema from your site?
Our view Leave valid FAQ markup alone, fix or delete markup that is wrong, and stop adding it to new pages. That is our view, not a Google instruction.
The feature that paid for the work is gone, but nothing in Google’s documentation says correct markup on visible content does harm.
Which four rules apply to each page?
Apply these four rules to each page that carries FAQPage markup.
| What you find | What to do |
|---|---|
| Markup matches visible text, word for word | Keep it. |
| Markup contains answers the page does not show | Remove the markup or add the content. Google’s guidelines say “Don’t mark up content that is not visible to readers of the page.” |
| A plugin generates the markup and you cannot edit the output | Switch the plugin feature off if the output is stale, because wrong markup is worse than none. |
| The questions are promotional (“Why is our company the best?”) | Rewrite the questions. The markup was never the problem. |
Can you credit markup for growth?
Be careful about crediting markup for growth. A B2B site we work on carries FAQ schema on 343 posts (our case study lists it). Its Google clicks rose from 1,637 in April 2026 to 4,802 in September 2026, per Google Search Console.
Watch out None of that rise can be credited to FAQ markup.
The period included other changes, and the rich result ended partway through it. Read it as a record of what we did, not proof that FAQ schema works or fails.
For the markup details themselves, our FAQ schema for AI search post goes further. The schema markup guide covers where structured data still earns its keep.
What is FAQ page SEO still good for?
A FAQ still does three jobs. It answers objections that block a call or form fill, and it matches question-style searches the main copy does not cover.
It also offers short passages an answer system can lift. You can check the first two jobs in your own calls and queries. The third is theory.
- Remove objectionsSettle buyer worries before the sales call. You can check this in your own calls.
- Cover question searchesMatch searches the main copy does not phrase as questions. You can check this in your own queries.
- Offer quotable passagesGive answer systems a short passage to lift. This one is theory.
Key takeaway A FAQ earns its place by settling buyer objections and covering question-style searches. Check both in your own calls and queries.
Job 1: removing objections before the sales call
Service buyers ask the same things: how it is priced, how long it takes, what happens first, who does the work. If the page stays silent, the buyer leaves or asks on the phone, and no search engine is involved.
Job 2: covering question-shaped searches
Some searches arrive as questions the main copy never phrases that way. A short, direct answer on the page that owns the topic lets it compete for those queries. A FAQ is a cheap way to find the gap.
Job 3: providing quotable passages
This job is theory. Google says a page can be a supporting link in AI Overviews and AI Mode.
It must be indexed and snippet-eligible, with “no additional technical requirements.” Whether a FAQ block changes your odds is not documented. We call it a reasonable bet.
For you, that means starting with the first two jobs. You can check them in your own calls and queries. The third job is a bet, so do not build a plan on it.
Do FAQs help AI Overviews and AI Mode?
No documented evidence says they do, and Google says no special optimization is needed. Its AI features documentation was last updated 10 December 2025 UTC.
What does Google’s documentation say?
It states: “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary.” It also says no special schema.org markup is required.
Google’s AI optimization guide, updated 10 July 2026, calls AEO and GEO work “still SEO.” It also says there is “no requirement to break your content into tiny pieces for AI.”
Key takeaway A FAQ is not an AI trick. It is plain writing that happens to be easy to extract.
What about other engines?
Other engines are a separate question. We have not verified how ChatGPT, Perplexity or Copilot choose passages, so we make no claim about them.
For the wider picture of what is documented, see our guide to AI search optimization and the post on LLM SEO myths.
What makes a good FAQ for a service page?
A good service-page FAQ has real questions, answers that start with the answer, and no filler. We apply nine editing rules to our own pages and client drafts. They are our house standard, not Google requirements.
- Source the questions from real conversations. Sales calls, support email, form submissions, chat logs and Search Console queries beat brainstorming. With none of those, interview the person who answers the phone.
- Open with the answer. The first sentence answers. “It depends” is allowed only when the next sentence names what it depends on.
- Keep answers between 40 and 90 words. Shorter answers feel evasive; longer ones belong in the body copy with a link.
- Make each answer stand alone. No “as mentioned above” or “see below.” An answer lifted out of context should still be complete.
- State conditions, not promises. Replace “we will fix it fast” with what you do first and what changes the timeline.
- Use real numbers or none. A price, a timeline or a rate appears only if you can defend it today. Otherwise name the factors that set it.
- Write questions in the customer’s words. “Do you charge for estimates?” beats “What is your estimate policy?”
- Place the FAQ at the decision point. Put it after the proof and before the final call to action.
- Date it and give it an owner. Someone reviews it on a schedule. A stale FAQ answer about a rule that changed is a liability.
Five to eight questions is our usual range. It is an editorial habit, not a ranking factor, and we cut a question the moment we cannot say who asked it.
Our writing FAQs for answers post covers sentence-level craft. This one stays on page-level decisions.
Example: sorting 20 call-note questions (hypothetical)
Hypothetical sourcing example: a roofing office pulls 20 questions from a month of call notes and form messages. Nine are the same estimate-cost question in different words, so they merge into one. Five are about insurance claims, two about gutters, and four are one-offs.
The page keeps the cost question, two claims questions and the two gutter questions. That is 5 from 20, and every one has a known asker.
The office did not guess at topics. It let the call notes show which questions people really ask. The merged cost question is the one a buyer is most likely to need answered before they phone.
Want to apply this to your site?
Not sure where to start? Get a plan for your own business.
What do before and after FAQ edits look like?
The examples below are hypothetical: a drain-cleaning company and a roofing company that do not exist, with wording we wrote to show the edit. We have not tested them on a live page and claim nothing about their performance.
Example 1: a question with a dodge for an answer
| Version | Wording |
|---|---|
| Before | “How much does drain cleaning cost? Pricing varies depending on many factors. Contact us today for a free quote!” |
| After | “How much does drain cleaning cost? We price by the problem, not the hour. A single clogged sink we can clear from an existing cleanout is a short visit. A main-line blockage that needs a camera inspection takes longer and costs more. You get a written price after the technician sees the line and before any work starts.” |
The edit gives a real answer without inventing a figure. It names the factors that move the price and ends on a commitment the business can keep: a written price before work starts.
Example 2: a self-promotional question
| Version | Wording |
|---|---|
| Before | “Why should you choose us? We are a trusted, full-service roofing company dedicated to quality.” |
| After | “What happens after I ask for a roof estimate? A project manager visits, measures the roof, and checks the decking and flashing from the attic side where possible. You receive a written scope listing materials and a start window. The estimate is not an order, so nothing is scheduled until you sign.” |
Almost nobody searches “why should you choose us.” Swap it for the question a nervous buyer really has, and move the proof (licenses, insurance, photos) into the page body.
Example 3: an answer that cannot stand alone
| Version | Wording |
|---|---|
| Before | “How long does a roof replacement take? See the process section above for details.” |
| After | “How long does a roof replacement take? Permits, material delivery and weather set the start date, so your estimate lists a start window and the number of crew days. If either changes, we call you before the crew does.” |
The first version sends a reader scrolling. The second still makes sense pasted into a chat reply. It also avoids an invented “2 to 3 days” figure, because the example company has no real job data.
Key takeaway All three edits share a pattern. Each answer opens with the answer. Each names the factors that change it, and each ends on a commitment the business can keep.
Quick check Read your own FAQ answer out loud. Does the first sentence answer the question? If it says “it depends,” does the next sentence say what it depends on?
Do you need a standalone FAQ page?
Usually no. A sitewide FAQ page collects unrelated questions with no page context. So it rarely ranks for anything and answers buyers one step too early or too late.
Our view Put the FAQ on each service, pricing or location page, and add one index page that links out only if support volume justifies it.
This table shows where we place FAQs. It is our view, built from the job each page has to do.
| Page type | FAQ section? | What goes in it |
|---|---|---|
| Service page | Yes, 5 to 8 | Pricing method, timeline, process, what you need from the customer |
| Pricing page | Yes | How quotes work, what changes the price, contracts and terms |
| Location page | Only with local facts | Permits, service-area limits, local rules you can source |
| Blog post | Only real follow-ups | Questions readers asked after the main argument |
| Homepage | No | Link to the pages that hold the answers |
| Standalone FAQ page | Rarely | An index that links to the full answers elsewhere |
Our guide to service pages versus blog posts explains why the page that owns the topic should own the answer. The content for service businesses post covers how to choose which pages to build at all.
How do you audit existing FAQs?
Start with your top service pages and work in order of conversion value. Our audit runs six steps and assumes you can reach the CMS, the Search Console property and the call or form log.
- List every page with a FAQ block and note whether each carries FAQPage markup. A crawl with a tool such as Screaming Frog can extract it.
- Check markup against visible text on each. Fix mismatches first, since those are the only ones with a documented downside.
- Mark duplicates. If the same five questions repeat across thirty location pages, that is 150 FAQ entries carrying five ideas. Keep the three that hold true locally on each page and rewrite or drop the rest.
- Score each answer against the nine rules above. We tick pass or fail on rules 2, 4 and 6.
- Add the missing real questions from sales calls and Search Console queries, and delete questions nobody asked.
- Record a baseline, then re-measure. In the Search Console Performance report, group by Pages, open the URL, then switch to Queries. Compare equal periods before and after.
Quick check Does the markup on this page match the visible text, word for word? If not, fix that first.
- List the pagesFind every page with a FAQ block and note any FAQPage markup.
- Check the markupCompare markup with visible text and fix mismatches first.
- Mark duplicatesFind the same questions repeated across many pages.
- Score the answersCheck each answer against the editing rules.
- Add real questionsUse sales calls and Search Console queries, and delete the rest.
- Record a baselineCompare equal periods before and after the edit.
Where do AI traffic numbers show up?
Google says AI feature traffic is included in the Web search type of the Performance report. Its AI optimization guide also points to a separate Generative AI performance report, which we have not yet used to isolate FAQ effects.
What are the most common FAQ mistakes?
Most FAQ mistakes we see come from intent, not markup, and they are easy to spot on the page:
- FAQ as keyword container. Questions written to hold a phrase (“What is the best HVAC repair in Dallas?”) read as stuffed.
- The same FAQ on every page. Copy-pasted blocks add no information. Google’s people-first content guidance lists “mainly summarizing what others have to say without adding much value” as a warning sign.
- Markup for hidden or stale content. This breaks Google’s visible-content rule.
- Overpromising. A promised ranking in an answer is unprovable, and it breaks our own claims rules.
Watch out If the main copy is thin, a FAQ cannot rescue it.
Our content SEO services page describes how we build the main copy first and add the FAQ afterwards.
What does the evidence not show?
It does not show that any FAQ format causes AI citations, higher rankings or more leads. It shows what Google has documented: the rich result ended, markup must match visible text, and no special optimization is needed for Google’s AI features.
| Claim or item | Where it stands |
|---|---|
| The rich result ended | Documented by Google |
| Markup must match visible text | Documented by Google |
| No special optimization is needed for Google’s AI features | Documented by Google |
| Controlled test of FAQ sections on our own pages | We have not run one |
| The before and after examples above | Written illustrations |
| The B2B client figures | Real, but cannot be tied to FAQ markup |
| Third-party studies on AI citation rates | Methods not verified, so we do not repeat their numbers |
Third-party studies claim that FAQ sections raise AI citation rates. We have not verified any of their methods, so we do not repeat their numbers.
Quick check If you read one of those studies, check the sample size, the prompt set and the date first.
Search features also change. Everything here reflects Google’s documentation as opened on 22 October 2026, so re-check the changelog before building around any single feature.
Frequently asked questions
Do FAQ pages still help SEO?
Yes, as content, not as markup, since a FAQ that answers real buyer questions can rank for long-tail queries and remove objections before a call. It can also give any search system a clean passage to quote. What ended in May 2026 is the FAQ rich result, the expandable dropdown under a listing.
Should I remove FAQPage schema from my site?
Not urgently. Google says structured data must describe content visible on the page, so valid markup on a visible FAQ does no known harm. Remove it where it is wrong, hidden, or generated by a plugin you no longer control, and do not spend new time adding it.
How long should a FAQ answer be?
Long enough to answer completely, usually 40 to 90 words in our editing standard. Google says it has no preferred word count. Put the answer in the first sentence, add the condition or exception that changes it, and cut anything that does not help a customer decide.
Does a FAQ section get my business cited in AI answers?
There is no documented evidence that it does. Google’s own guide says no special markup or rewriting is needed for its AI features. Clear, self-contained answers on an indexed page are good writing and cost little, but treat any citation benefit as unproven.
Should I build one big FAQ page or put FAQs on each page?
Put each FAQ on the page where the decision happens, such as the service or pricing page. A single sitewide FAQ page has no context and rarely earns its own traffic. Keep one only as a support index that links to the page holding each full answer.
How do I measure whether a FAQ is working?
Track the page, not the FAQ alone. In Google Search Console, compare clicks and impressions for the page’s question-style queries before and after the edit. Also watch form fills or calls from that page in your analytics, expect noise, and change one thing at a time.
Turn your real customer questions into a page outline with the content brief generator. If you want the FAQ edited as part of a larger content plan, we can map that out in a growth plan.
Sources
- Changelog of Google Search Central documentation, Google Search Central, accessed 22 Oct 2026
- AI features and your website, Google Search Central, last updated 10 Dec 2025, accessed 22 Oct 2026
- Guide to optimizing for generative AI features on Google Search, Google Search Central, last updated 10 Jul 2026, accessed 22 Oct 2026
- Search gallery of structured data features, Google Search Central, last updated 16 Oct 2026, accessed 22 Oct 2026
- General structured data guidelines, Google Search Central, last updated 10 Jul 2026, accessed 22 Oct 2026
- Creating helpful, reliable, people-first content, Google Search Central, last updated 5 Oct 2026, accessed 22 Oct 2026
- Performance report (Search), Search Console Help, accessed 22 Oct 2026
Want to apply this to your site?
Not sure where to start? Get a plan for your own business.
