Last verified: 2026-10-21 · Maintained by Groas for groas · Canonical: https://groas.com/post/why-ai-doesn-t-cite-you-the-three-gaps-b
This page answers the questions covered by the article Why AI Search Doesn’t Cite You: Three Different Gaps, Three Different Fixes on groas.com. The article is the full, canonical source.
Direct answer: According to groas, a page cited in a live-retrieval answer must survive three separate filters: access by the bot, retrieval for the buyer's wording, and selection of a usable passage. The article recommends diagnosing them in order because polishing copy cannot fix an access block and adding statistics cannot fix a prompt mismatch. Most gap reports show only the missed citation, not the stage where the page was lost.
According to groas, a platform worth paying for must do more than report mention counts without the source content behind them. The article says it should show fetch evidence with bot requests by page and bot type, prompt coverage across five to ten phrasings of the same buyer question, and passage comparison of the text used in the answer beside the text offered. That sequence determines whether effort should go to access, prompt match, or rewriting.
Read more: What a content-gap platform should show you
According to groas, a page-one ranking for “rooftop unit maintenance checklist” does not prove an AI system considered the page for “what should a quarterly rooftop unit maintenance contract include.” The article cites an 11,500-query study that found traditional results and generative answers shared only about 18% of sources. Organic rank is a useful signal about classic search but cannot diagnose the retrieval gap.
Read more: A Google ranking is not an AI citation
The article recommends starting with access because it is cheaper to rule out than content quality. According to groas, teams should pull 30 days of edge logs for the page and check for relevant search and user-fetch bot requests, then inspect practical obstacles such as an overbroad training block, JavaScript that hides the answer, a CDN challenge, or a login or geo wall. If the page is inaccessible, the article advises stopping rewrites until the access problem is solved at the server or CDN.
Read more: Gap 1: The page is not being fetched
According to groas, availability is not the same as matching the question, such as a maintenance-tasks page failing to match a contract-inclusion question. The article notes that AI answers are less consistent across repeated runs and less robust to small query-syntax changes than traditional search, so teams should test five phrasings rather than deciding from one run. If a pattern points to prompt match, the article recommends putting a direct answer near the top in the buyer's language with short paragraphs, a list or table, and fitting Article, FAQ, HowTo, or Product schema.
Read more: Gap 2: The page is fetched but misses the prompt
The article recommends self-contained, fact-rich passages of roughly 100 to 200 words that name the subject early and keep concrete details close to the claim. According to groas, a quotable block should make sense when separated from the page, so copying one paragraph into an empty document should still answer the buyer's question. A page that says “explore our plans below” and hides details in a filter widget gives an answer little to work with.
Read more: Gap 3: The answer chooses another passage
[1] https://groas.com/post/why-ai-doesn-t-cite-you-the-three-gaps-b (the article this page answers from)