Find content gaps with live search demand
A good FAQ answers the questions people actually ask — not the ones we guess they might. Find content gaps closes that distance: it checks live search demand around your post's topic and surfaces the questions your article doesn't answer yet. You decide which ones deserve a spot in the FAQ, and you write the answers.
What it does
When you run it, the tool:
- Works out what people would search for around the post's title and topic.
- Checks live Google search suggestions — the completions Google offers as real people type, which is direct evidence of what's being searched right now.
- Compares that demand against your article and the FAQ you already have.
- Returns up to six questions the post doesn't currently answer.
Run it
- Open the post and click the TL;DR & FAQ tab.
- Click Find content gaps.
- A Content gaps panel appears. Its header tells you what the suggestions are based on: from live Google search demand when real suggestion data was available, or based on the topic (search demand unavailable) when it wasn't (more on that below).
- For each suggested question, either click Add to FAQ or dismiss it with the ×.
If the panel says "Nothing missing — the post already covers the questions people search", that's the good outcome: your article and FAQ already cover the demand it found.
See the evidence
When suggestions are demand-grounded, the panel offers "Show the live Google searches this is based on." Expand it to see the literal search queries the suggestions were derived from — so you're not taking the tool's word for it, you're looking at the same demand it saw.
You write the answers — on purpose
Add to FAQ inserts the question with an empty answer for you to fill in. The tool never writes answers, and that's deliberate: it can tell you what people ask, but only you know what's true for your community, your market, and your process. An FAQ answer carries your name — it should carry your knowledge.
One consequence to know: FAQ items are only kept if they have both a question and an answer. A gap question you added but never answered is dropped when the post saves — write the answer before you save.
Troubleshooting
The header says "based on the topic (search demand unavailable)"
Live Google suggestions couldn't be reached this time, so the tool fell back to proposing questions from the topic alone. They're still worth reviewing, but they aren't backed by demand data — run it again later if you want the grounded version.
The suggestions feel off-topic
Search demand mirrors what people actually type, and topics sometimes pull in neighboring questions — pricing, comparisons, logistics. Dismiss what doesn't fit; the point is that you choose. If most suggestions feel wrong, the post's title may be broader or more ambiguous than its content.
A question I added disappeared after saving
It had no answer yet. Unanswered rows are dropped when the post saves — add the question again, write the answer, then save.
Can it answer the questions for me?
No — by design. Generation from the article (Generate a post's TL;DR and FAQ) drafts answers from what the post already says; content gaps surface what the post doesn't say. Often the best move is to also address the gap in the article body itself, then let the FAQ answer be its short version.