Does adding an FAQ section help depth or just pad the page?
- Published November 6, 2026
- Linked from 3 answers
- In a cluster of 7
It helps when its questions are ones the rest of the page does not answer, and pads the page when it restates the article as questions. An FAQ can be a good home for the edge cases, the “what if” questions and the objections that do not fit the main flow; each of those adds coverage. An FAQ that asks “What is X?” and answers with a sentence the introduction already said adds words and nothing else.
The rich result is gone
One reason FAQ sections spread was the FAQ rich result, which expanded questions under a search listing. Google no longer shows FAQ rich results: they have not appeared since May 7, 2026. FAQ markup no longer changes how a page appears in search, so the only reason left for an FAQ section is the reader. The history of that feature, and of the HowTo result removed in September 2023, is told in whether FAQ schema still earns rich results.
Test each entry
| FAQ entry | Keep or cut |
|---|---|
| Answers a question the body does not cover | Keep |
| Handles an objection or edge case the body skips | Keep |
| Restates a point the body already made | Cut |
| Asks a question no one searches or asks you | Cut |
| Repeats an FAQ copied across dozens of pages | Cut, or rewrite for this page |
The last row has a second cost: an identical FAQ block on dozens of pages makes those pages more alike, which works against the distinct content each page needs.
Where the questions come from
Good FAQ entries come from evidence: the related questions on the results page, the queries in Search Console that bring people to the page, and the questions customers ask after reading it. If a question deserves a long answer, it may deserve its own page instead, a choice covered in when a question keyword is better served by a page than a snippet. A short FAQ of real questions is better than a long one that repeats the page back to the reader.
Add a comment