Because it answers questions nobody asked. Most FAQ sections are written by the marketing team as a place to restate benefits, not by anyone who reads support tickets. Nielsen Norman Group warns specifically against made-up questions, and a made-up question is exactly what a reader recognises and skips.
We see the same six fake questions on site after site. What makes you different. Why should I choose you. How do I get started. Nobody has ever typed those into a search box or a support chat. They are headings pretending to be questions.
A real FAQ section is one of the highest value blocks on a website. It reduces support load, it removes buying objections, and in 2026 it is one of the cleanest formats for getting quoted by AI answer engines. It just has to contain real questions.
It exists to remove the specific doubts standing between a visitor and a decision. Not to summarise your offering, and not to hit keywords. Nielsen Norman Group frames the value plainly, noting that people already know to look for an FAQ when they need a fast answer, which makes it a familiar format worth using well.
That familiarity is the asset. A visitor who wants one specific fact does not want your services page. They want to know whether you work with their industry, how long it takes, what happens if they cancel, and whether their data stays in their country. An FAQ is where those answers can live without cluttering anything else.
Nielsen Norman Group also lists the broader payoffs, including setting the tone of your organisation through public customer interactions, supporting purchase decisions by demonstrating credibility, improving SEO through question formatted content, and reducing the load on your support team.
Note what is not on that list. Nowhere does an FAQ exist to repeat your value proposition. If a reader wanted the pitch, they would still be on the homepage.
Yes, and this is the biggest change to the format in years. Google's Search Central changelog entry of 8 May 2026 added a deprecation notice stating the FAQ rich result feature would no longer appear in Google Search starting 7 May 2026. On 15 June 2026, Google removed the documentation entirely.
This did not come out of nowhere. Google had already narrowed the feature sharply, and its earlier guidance from September 2023 said the FAQ rich result was only shown for well known, authoritative government and health websites. For most site owners the feature had effectively been gone for a while before it was formally retired.
If you built an FAQ section specifically to win those expandable results in the search listing, that reason no longer exists. It is worth saying that clearly, because a lot of published advice still recommends FAQ markup on the promise of a visual result Google no longer shows.
We think this is a good thing on balance. The rich result created an incentive to bolt an FAQ onto every page whether it belonged there or not. Removing the reward leaves the format to the pages that genuinely need it.
Probably not for its own sake, and definitely not expecting a rich result. Google no longer shows the FAQ rich result, so FAQPage markup buys you no visual treatment in search. Adding it is now a neutral act rather than a win, and neutral acts still cost maintenance.
There is a reasonable counter argument, which is that structured data helps machines understand a page regardless of whether a rich result appears. That is true in principle. It is also true that Google explicitly retired this type, so betting your effort on it is betting against the platform's stated direction.
Our position is that your effort goes further into markup Google still supports and still displays. Organisation, Product, Article, and Breadcrumb markup all continue to do real work, and the general case for getting this right is in our guide to what schema markup does for your SEO.
What has not changed at all is the underlying content. A page that asks a clear question in a heading and answers it immediately underneath is legible to every search and answer system, with or without a schema block wrapped around it. The structure was always doing more work than the markup.
From places where people already ask them. Your support inbox, your sales calls, your live chat transcripts, and your Search Console query report. Every one of those is a record of real language from real people, which is the only reliable source of questions worth answering.
Nielsen Norman Group puts the underlying principle better than we can, observing that people do not search for your solution, they search for their problem. Your team describes what you sell. Your customers describe what is going wrong. Those are different vocabularies, and the FAQ has to use theirs.
The sales call is the richest source and the least used. The objections that come up on every call are, by definition, the doubts your website failed to resolve. Writing those down and answering them honestly on the site is the single highest leverage content exercise most businesses never do.
Search Console adds the queries that brought people to you and the ones where you appeared but nobody clicked. Those near misses are often perfectly phrased questions you have not answered yet.
Put them where the question arises. A dedicated FAQ page is fine as a catch all, but the questions that block a decision belong on the page where the decision happens. Pricing objections go on the pricing page. Delivery questions go on the product page. Onboarding questions go next to the signup form.
The dedicated page has one real advantage, which is that it can rank for question queries on its own. It also has an obvious failure mode, which is becoming a dumping ground nobody maintains and nobody reads.
Nielsen Norman Group's structural guidance is useful here. It says the traditional question list followed by the individual questions and answers remains the best underlying design for short and medium length FAQs, which it defines as under about ten pages of content. Past that size, you are building a help centre and should treat it like one.
We usually recommend three or four questions inline on key pages, plus a fuller page for everything else. Contact and enquiry pages benefit most from this, because a small doubt at that moment costs you the enquiry, which is a theme we return to in our guide to designing a contact page that gets real enquiries.
Use an accordion when you have more than about five questions, and show everything when you have fewer. Accordions let a reader scan the questions and open only what they need, which matches how people actually use FAQs. Below five questions, the collapsing adds a click without saving any scrolling.
The critical requirement either way is that every answer exists in the page HTML from the start. An accordion that fetches its answers with JavaScript when clicked is invisible to anything that does not click, which includes a large share of crawlers. Hide with CSS, never with an empty container.
This is worth checking rather than assuming, because plenty of accordion components load content on demand by default. View the page source, search for a sentence from a collapsed answer, and confirm it is there. If it is not, your FAQ content does not exist as far as most machines are concerned.
Beyond that, the usual accessibility rules apply. The question should be a real button, it should be reachable by keyboard, and the open state should be announced. An accordion that only responds to a mouse click excludes people and confuses assistive technology.
Because the format matches how answer engines retrieve. Systems like ChatGPT, Perplexity, and Google AI Overviews look for a passage that directly answers a question. A heading that states the question and a paragraph that answers it in the next forty words is close to the ideal shape for that.
This is the part that survived Google retiring the rich result. The visual reward is gone, but the structural advantage is larger than it was, because more discovery now happens through systems that read for meaning rather than scan for markup.
The requirement is that the answer stands alone. If your answer says it depends on your plan, see above, it cannot be quoted, because the quote would be useless without the surrounding page. Every answer should make sense lifted out of context, which is a genuinely different writing discipline from normal web copy.
Specificity is what gets picked. An answer containing a number, a timeframe, or a named condition is more quotable than one containing reassurance. We go further into what makes content quotable in our guide to getting cited by AI search engines.
Answer in the first sentence, then explain. Lead with yes, no, or a number. A reader who opens a question wants the answer immediately, and a paragraph that builds up to it has already lost them. Everything after the first sentence is for the people who want detail.
Length should match the question. Some answers are one sentence and should stay one sentence. Padding a simple answer to make the section look substantial is the fastest way to make it feel evasive, and readers are good at detecting that.
Honesty is the underrated part. The most valuable FAQ answers are the ones admitting a limitation, because those are the questions people are genuinely nervous about. Saying plainly that you do not do something, or that a process takes longer than clients expect, buys more trust than any amount of reassurance.
Then keep them current. An FAQ is the section of a website most likely to go quietly out of date, because nothing visibly breaks when an answer becomes wrong. We review FAQ content on the same schedule as pricing, since both are places where a stale answer costs real money.
Open your support inbox and your sales notes, and write down the ten questions that come up most. Compare that list against the questions currently on your site. If they do not overlap much, your FAQ section is decoration, and rewriting it against the real list is a half day of work with an immediate payoff.
While you are in there, check whether you are still carrying FAQ schema markup added for a rich result Google no longer shows. It is not doing harm, but it is worth knowing that it is no longer doing the job it was added for.
If you want a second opinion on which questions belong on which page, or you have an FAQ page that has grown into something nobody can navigate, we are happy to work through it with you. Come find us at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.