This is the lowest-scoring tool in the dataset by a distance, and the reason is structural rather than damning: it looks for an explicit question-and-answer structure, and most pages simply are not written that way. A page can cover its subject thoroughly in flowing prose and score close to nothing here. What the low scores really document is how rare it still is to write the questions down.
Here is where that sits. The median is 0/100, which ranks it 25 of the 25 measures in this dataset. The middle half of results falls between 0 and 0 — a band 0 points wide. That is narrow: sites resemble each other on this measure, which usually means a platform is doing most of the work.
How the scores are distributed
An average on its own misleads. The chart below splits all 534 scans into five score bands, totalling 100%. The distribution banks up against the floor: most pages score badly, so even a modest result here puts you ahead of the majority.
- 0–19
- 20–39
- 40–59
- 60–79
- 80–100
| Score band | FAQ Gaps |
|---|---|
| 0–19 | 87% · 462 |
| 20–39 | 8% · 42 |
| 40–59 | 4% · 21 |
| 60–79 | 0% · 0 |
| 80–100 | 2% · 9 |
| Total runs | 534 |
The grade mix
The same data as letters: A+ 95–100, A 85–94, B 75–84, C 65–74, D 50–64 and F below 50.
Where your score stands
Because so few pages have any Q&A structure at all, almost any score above the floor puts you ahead of the field. Do not read a low number as a content failure — read it as an untaken opportunity. The gap between the median here and the median of every other content tool is the clearest arbitrage in the dataset.
| Tool | 10th | 25th | Median | 75th | 90th | Mean | Lowest | Highest |
|---|---|---|---|---|---|---|---|---|
| FAQ Gaps | 0 | 0 | 0 | 0 | 24 | 5.4 | 0 | 81 |
How to read it: 0 is bottom-quartile, 0 is a typical page, 0 starts the upper quartile and 24 or above is the top 10%. These thresholds apply to this tool only.
The checks that fail most
The checks look for three things: whether questions appear at all, whether the answers sit immediately beneath them, and whether FAQ structured data marks which is which. The third is optional in a way the first two are not — the structure helps a machine, but the questions help the reader, and the reader is why the questions are worth adding.
| Check | Did not pass | Weight |
|---|---|---|
| FAQPage schema | 99% | Partial |
| Answers common user questions | 96% | Hard fail |
| Has a Q&A / FAQ structure | 89% | Partial |
“Hard fail” means the check’s full weighting is lost; “partial” means only part of the score is. Rates are the share of scans in which the check ran and did not pass.
The weakest areas
This tool groups its checks into categories. The chart below shows how often each category was the lowest-scoring one in a scan — which area is most often the weak link. It is not the average score in that category; it is how often it came last.
“Question coverage” was the weakest area in 88% of scans.
What to fix first
Take the three questions people actually ask you about this subject — from support tickets, from sales calls, from the search queries already reaching the page — and answer each in two or three sentences under a heading phrased as the question. That is the entire job. It improves the page for readers and it happens to be the exact format answer engines extract.
A typical scan passes 0.2 of 3 checks and leaves 2.8 open items behind. What drags a score down is usually not one catastrophe but accumulated small omissions.
Run the FAQ Gap Finder on your own page
Month by month
The figures on this page are replaced at every refresh. At the end of each month a permanent edition is published for that month and never edited again — which is the only reason this series can be compared at all. One edition has been published so far; when the second lands this section will set the two months side by side.
| Edition | Median | vs. previous | Scored 80+ | Issues/run | Runs |
|---|---|---|---|---|---|
| August 2026 | 0 | baseline | 2% | 2.8 | 534 |
Frequently asked questions
Where do I find the questions worth answering?
The ones you already receive: support conversations, sales objections, the queries in Search Console that reach the page, and the "People also ask" box for your main query. Invented questions read as invented, and they are the reason so many FAQ sections are useless padding.
Does an FAQ section still earn rich results?
For most sites, no — Google narrowed FAQ rich results to a small set of site types. That changed the visual reward and not the underlying value: a clear Q&A structure is still the format answer engines extract from most readily, and it still helps a reader find the specific thing they came for.
How many questions should a page answer?
Three to six, chosen because people ask them. A long list of thin answers dilutes the page and looks like padding to both readers and engines. If a question needs a substantial answer, that is a sign it deserves its own page, with the FAQ entry pointing to it.
What is a good score on the FAQ Gap Finder?
In this dataset the median is 0/100, so scoring 0 puts you exactly in the middle. 0 is the start of the upper quartile and 24 or above is the top 10%; below 0 is the bottom quarter. Those thresholds are specific to this tool — the 25 measures in this dataset have very different medians, so 70 here and 70 elsewhere do not mean the same thing.
Which check fails most often on the FAQ Gap Finder?
“FAQPage schema”, which did not pass in 99% of scans. The costliest failures, though, are the ones scored as hard fails — this tool has 1, the most common being “Answers common user questions” at 96%.
Questions that govern the whole series — how the sample is collected, how sites are anonymized, how often the figures are refreshed — are answered in the methodology on the hub.
Using this data
The figures, tables and charts on this page are free to reuse under CC BY 4.0; the only condition is a link back to this page. Suggested citation: SeoMods — FAQ Gap Finder benchmarks, 2 September 2026, https://seomods.com/seo-score-benchmarks/faq-gap-finder. If you need to cite by date, use the August 2026 edition instead: this page changes at every refresh and that one never does.