FAQ SEO Now Means Writing Answers Google and ChatGPT Will Quote
Last year a client showed me their FAQ page like it was a trophy. Forty questions, every one marked up with schema, the whole thing built to win those expandable FAQ results in Google. By the time we talked, the results were gone, and so was the traffic they had pinned to them. They wanted to know if they should just delete it.
The answer was no, and the reason is the most useful thing I can tell you about FAQs right now. Google took away the rich result. It did not take away the reason FAQs work. The format that earned the accordion snippet is the same format AI search reaches for when it needs a quick, quotable answer. The job changed underneath us.
What FAQ SEO actually means now
FAQ SEO is the practice of structuring your frequently asked questions and answers so that search engines and AI systems can find and quote them. Since Google stopped showing FAQ rich results for most sites in 2023, FAQ SEO is no longer about winning the snippet. It is about writing self-contained question-and-answer pairs that Google's AI Overviews, featured snippets, and tools like ChatGPT can lift as a direct answer.
That is a real change in what FAQ SEO is for. For years the payoff of an FAQ was visual: the expandable result that pushed competitors down the page. Now the payoff is being the source a machine pulls from when it answers your customer's questions, whether that machine is a Google AI Overview or a chatbot that never shows ten blue links at all. Same content type, completely different finish line.
What happened to the FAQ rich result
It helps to be precise about what Google actually changed, because a lot of people heard "FAQ schema is dead" and overcorrected. In August 2023, Google FAQ rich results limited to government and health sites. For everyone else, the expandable FAQ vanished from the search results. The schema still validates, and search engines still read the structured data. The display is what went away.
The drop was not subtle. Portent FAQ results fell from 54% to 17% almost immediately. Pages that had won space in the search results with a fat block of questions suddenly looked like everyone else's. If your FAQ SEO was built to capture that real estate, the return you were counting on is gone, and cleaner schema will not bring it back.
If your FAQ SEO was built to capture that real estate, the return you were counting on is gone, and cleaner schema will not bring it back.
Here is where people make the wrong move. They read the news as "FAQs do not matter," then delete them or stop writing new ones. That is a mistake. The Search Engine Land account of the rise and fall of FAQ schema puts it well: the rich result was always a bonus on top of the real work. The questions your customers actually ask, answered clearly on the page, were doing quiet work for you the whole time. FAQ schema was never the magic button, which is the same thing I keep telling people about schema markup in general.
Why questions and answers are what AI search retrieves
To see why FAQs still earn their keep, you have to know how the systems pulling answers actually read your content. They do not read a page the way you do, top to bottom. They break it into passages and grab the chunk that best matches the question.
This is older than the AI search panic. One of Google's own patents, text indexing and passage retrieval, describes scoring individual passages of a document against a query instead of judging the page as a whole. Go Fish Digital, continuing the kind of patent analysis the late Bill Slawski was known for, walked through how Google selects candidate answer passages: it scores sections of a page for how well they answer a question, then surfaces the best one. A question with a tight answer underneath it is already shaped like exactly what that system is hunting for.
AI search runs on the same principle. Retrieval systems chunk your content and embed each chunk, then match chunks to the query, which is why iPullRank keeps arguing that how your content gets chunked decides whether you get retrieved at all. A frequently asked question with a self-contained answer is a near-perfect chunk. It states one idea, resolves it, and still makes sense lifted off the page. Most FAQ content is already written as these short question and answer pairs, which is why FAQ pages punch above their weight when search engines and AI tools go looking for a passage to quote.
There is evidence that the quotable answer wins. A Princeton-led study on generative engine optimization tested what makes language models cite a source and found that adding clear statistics, quotations, and citable phrasing could lift a page's visibility in AI answers by as much as 40 percent. An FAQ answer that says something specific is doing exactly that. An FAQ that restates the page in vaguer words is not, which is the whole argument I made about information gain: if your answer adds nothing a model could not already generate, it has no reason to quote you.
How to write FAQ answers that get quoted
Once you see the FAQ as a retrieval unit, the FAQ SEO rules get obvious, and most of them come down to discipline.
Lead with the answer. The first sentence should resolve the question before any setup, because the first sentence is the part most likely to be pulled. When I rewrite a client's FAQ, the first thing I cut is the throat-clearing, the "great question, it depends on a few factors" opening that makes a reader and a machine wait for the point.
Keep one question to one answer to one idea. If an answer is secretly covering three things, split it into three questions. A chunk that tries to do too much matches the query worse than a tight one, and it reads worse too.
Keep answers short and self-contained, roughly two to five sentences. Write each one so it still makes sense if someone lifts it out and drops it into a chatbot reply with no other context, because that is literally what happens. Name the specific thing: the number, the policy, the timeframe. Vague answers do not get quoted because they do not actually answer.
Phrase the questions the way your users actually ask them. Pull from your People Also Ask boxes, your support tickets, and your Search Console queries, then match the wording of the real searches. Google's own guidance for FAQ content still describes FAQs as a plain question-and-answer format, and the closer your questions match what people actually search, the easier the match is to make.
Do not paste the same FAQ block onto forty pages. Duplicated answers compete with each other and add nothing, and "adds nothing" is the fastest way to get ignored. This is the same bar the quality rater guidelines hold every page to: the answer has to read like someone who actually knows the topic wrote it.
Where to put your FAQs and how they connect
Placement matters as much as wording, and the old instinct to dump every question onto one buried FAQ page is part of why so many FAQ pages underperform.
Put the questions where they come up. Pricing questions belong on the pricing and service pages, next to the thing they are about, not three clicks away. The answers are more useful to your users there, and more useful to a search engine trying to work out what those pages are about. A standalone FAQ page can still exist, but treat it as a hub, not a graveyard for questions nobody links to.
Then connect them. Every substantial answer is a natural entry point to a deeper page, so link the questions to the content that expands on them with real anchor text. This is the internal linking discipline I am always pushing, because FAQ content sitting in a sealed room does nothing for the pages that need the authority, the same problem I described in content silos being a house without hallways. Local businesses get an extra payoff here: clear FAQs that answer "do you serve my area" or "what are your hours" feed the exact short, factual answers that local search and AI results reach for.
This is the structural work our content strategy team does first, because a brilliant answer in the wrong place, with nothing linking to it, still loses.
FAQ SEO is now a content discipline, not a schema trick
So should you keep your FAQs? Yes, and you should probably take them more seriously than you did when they were a snippet play.
The rich result was a display feature, and display features come and go at Google's discretion. What does not go away is the value of answering a real question clearly enough that a person trusts it and a machine can quote it. That is content strategy, and it survives algorithm changes precisely because it is not gaming one. The FAQ format just happens to be the cleanest way to package that kind of answer. The structured data behind your FAQs costs almost nothing to keep, so leave it in place where search engines and AI crawlers can still read it.
If you want the longer version of how this fits a plan that does not break every time Google ships an update, I laid it out in our SEO content strategy. For FAQ SEO, the move is simple to say and harder to do. Stop optimizing for a result that is gone. Start writing answers worth quoting, and let Google and ChatGPT find them.
By Katrina Kendall
Katrina Kendall
Content Strategist at Right Thing SEO, where she helps business owners sound like the experts they already are. Her focus is on translating real-world experience — the kind that lives in a founder's head but never makes it onto the page — into content that satisfies Google's E-E-A-T standards and actually converts. Before joining Right Thing, she spent six years in B2B content strategy, where she got tired of watching brilliant operators get outranked by generic blogs written by people who'd never done the work.