Finder
FAQ Gap Finder
Every support inbox and search log is a list of things your site failed to answer. Paste those questions and your FAQ, and this tells you which ones are genuinely uncovered rather than merely worded differently.
- Matches on meaning-ishNot exact strings
- Ranks by how uncoveredWorst first
- Both inputs stay localNothing is transmitted
Check it
Paste it here
Result
- Questions checked —
- Covered —
- Partly covered —
- Least covered —
- Coverage —
- Do next —
Matching is by distinctive word overlap, so a question answered in very different words may show as a gap. Read the list before acting on it.
What the result means
A gap is a page, not a prompt problem
If your content does not answer a question, no model setting will make the assistant answer it correctly. The only honest fix is to write it down.
Use real questions, not imagined ones
Questions you invent are questions you have already answered. The valuable list is your search log, your support inbox and your chat transcripts.
Partly covered is the dangerous category
A question your content half-answers is the one an assistant will complete from general knowledge. Fully uncovered questions at least produce an honest refusal.
Write short answers, not new pages
Most gaps close with three sentences in an existing FAQ. Creating a new page per question is how a site becomes too large to keep true.
Questions
Site search logs, the subject lines in your support inbox, and — once you run an assistant — the conversations where it refused. That last one is the best source.
Matching is by distinctive word overlap. If you answer it in very different vocabulary, it can read as a gap — which is itself worth knowing, because retrieval has the same problem.
Twenty to a hundred is a useful sample. Enough to see a pattern, few enough that you will actually read the output.
Want this run against your whole site?
Tell us the page your assistant lives on and the questions you care about. A person runs them and sends back the raw answers.