Your page sits in position three for a query that matters. Above it, an AI Overview answers the question in four sentences and links to two pages that are not yours. The traffic you forecast from that ranking is leaking out through an answer box you do not control, and nothing in your rank tracker shows it.
Being not cited in AI Overviews despite a strong ranking is a common and fixable situation. A citation is a separate selection made after retrieval: the system picks passages it can lift, verify and attribute, and a high-ranking page can fail all three. AskEO is an SEO and Answer Engine Optimization analyzer that audits a page against 60+ checks, so this article uses the same checks as a diagnostic order.
Why does a top-ranking page still not get cited?
Ranking decides which pages are candidates, while citation decides which passages are quoted. Those are two different jobs, and a page can win the first and lose the second.
Ranking rewards the whole page: links, intent match, freshness, and a long list of other signals. Answer generation works at the passage level. The system needs one clear chunk of text that resolves the query, and it prefers chunks that make sense when copied out of the page with no surrounding context.
That is why a 3,000-word guide with the answer spread across eight paragraphs can rank well and still lose to a 700-word page that states the answer in its second sentence. The long guide is a better document, but the short page is a better quote.
What are the five most common causes?
Five causes account for most of the cases: the answer is buried, the page is not snippet-eligible, the key content is not in the served HTML, the claims are unverifiable, and the entity is unclear. The table below pairs each one with a test you can run today.
| Cause | How to check it | Fix |
|---|---|---|
| Answer is buried | Read the first two sentences under each heading. Do they answer it? | Rewrite so the answer comes first, context second |
| Not snippet-eligible | Search the source for nosnippet, max-snippet and data-nosnippet | Remove directives that block the passage you want quoted |
| Content missing from served HTML | View the raw response, not the rendered DOM | Server-render the answer and the headings |
| Claims cannot be verified | Highlight every number, and check each has a named source | Add the source in the sentence, or cut the claim |
| Entity is unclear | Ask whether a stranger knows who wrote the page and what the brand does | State the brand, author and scope in plain text |
Work through them in that order. The first is the most common and the cheapest to fix, and the last takes the longest to show results.
How do you check whether your answer is buried?
Test it by reading only the first two sentences under every heading and asking whether a stranger could act on them. If the answer starts in sentence four, it is buried.
Buried answers usually come from habit. Writers set the scene, define terms, and then deliver the point. A passage-level system reads the scene-setting as the chunk and ranks it accordingly.
Run this short procedure on your highest-value page:
- Pick the one query you want to be cited for and write it down as a full question.
- Find the heading on the page that matches it, or add one phrased as that question.
- Write a one- or two-sentence answer directly under the heading, with the specific number, threshold or name in it.
- Copy that answer into a blank document and read it alone. If it needs the paragraph above it to make sense, rewrite it.
- Put the supporting detail, caveats and examples after the answer, not before it.
The copy-and-paste test in step four is the most useful one. A quotable sentence survives being moved, and a sentence that begins with "This means that" does not.
Could a snippet directive or a crawler rule be blocking you?
Yes, and it is worth checking before you rewrite anything. Google's documentation on AI features in Search says a page must be indexed and eligible to be shown with a snippet to appear as a supporting link, with no extra technical requirement beyond that (see the Google Search Central page on AI features).
That makes snippet controls the first thing to rule out. A nosnippet robots directive, a very low max-snippet value, or a data-nosnippet attribute wrapped around your answer paragraph can each take the passage out of play. Teams often add these for one reason, such as protecting a paywalled section, and forget them when the template spreads to other pages.
Crawler rules are a different layer and are easy to confuse with this one. Blocking an AI crawler in robots.txt affects whether that crawler can fetch your pages, but it is not the same control as snippet eligibility in Google Search. Check each system's own documentation for which token governs which product, and do not assume a single robots.txt line covers all of them.
Is your answer actually in the HTML the crawler receives?
Not always. If your answer, headings or FAQ are injected by JavaScript after load, a crawler that does not execute scripts receives an empty shell where your best passage should be.
The check takes under a minute. Request the page with a plain HTTP client, search the response for the first sentence of your answer, and see whether it is there. If it is not, the passage exists only for browsers.
The fix is to render the answer on the server, or to pre-render the pages that matter most. You do not need to rebuild the whole site, only the templates that hold your answer passages, headings and structured data.
Why do unverifiable claims lose citations?
Answer engines are built to attribute, so a passage with no checkable support is a liability to quote. A sentence such as "most teams see big gains" gives the system nothing to verify and nothing to attribute.
Compare it with "the Google Search Central documentation states that no additional requirements apply beyond indexing and snippet eligibility." The second sentence names a source, states a specific claim, and can be checked in a minute. That is the shape that gets lifted.
Audit your page for three things: numbers without a named source, adjectives doing the job of evidence, and claims that contradict another page on your own site. Each one lowers how safe the passage is to repeat.
How do you find which cause is yours without guessing?
You audit the page against all five causes at once, because the manual version means opening source code, robots rules, raw responses and schema in four different tools. That is tedious for one URL and impractical for fifty.
AskEO fetches the page, parses meta tags, JSON-LD, headings and AI crawler permissions, adds Core Web Vitals from Google PageSpeed Insights, and returns a report in roughly 30 seconds. The free tier covers 3 lifetime homepage audits, and paid plans, listed on the AskEO pricing page, add AI-written fix instructions and full-site crawling. Use the free scan to see which of the five causes shows up first.
What if you fix all five and still are not cited?
Then the likeliest reason is competition for the same passage, not a defect on your page. Citations are limited in number, and an established source with a clearer answer may hold the slot.
Do not respond by publishing more of the same. Respond by being more specific than the incumbent: a narrower question, a number they omit, a failure mode they skip, or a decision table where they only have prose. Original substance gives a system a reason to choose you over a page that says the same thing.
Also be honest about the limit of what you can influence. No one outside the search provider can guarantee a citation, and any vendor who promises one is selling something they do not control. What you can do is remove the reasons for exclusion and make the passage easy to quote.
What should you do next?
Pick the one page that earns the most from a top-three ranking and audit it today. Create a free AskEO account, run the homepage scan, and read the issue list in the order the table above uses. You will have the first fix identified before your next meeting.
Frequently asked questions
Why is my page not cited in AI Overviews even though it ranks first?
Ranking and citation are separate selections. Your page may rank first because of links and intent match, while the answer passage is buried, blocked by a snippet directive, missing from the served HTML, or unsupported by named sources. Fix those four before assuming the ranking itself is the issue.
Does a nosnippet tag stop my page from appearing in AI Overviews?
It can. Google's AI features documentation says a page must be eligible to be shown with a snippet to be a supporting link, so a nosnippet directive or a restrictive max-snippet value can remove it from consideration. Check page-level robots meta tags, HTTP headers and any data-nosnippet attributes around your answer.
How long should the answer under a heading be?
Aim for one or two sentences that resolve the question, followed by supporting detail. Short enough to quote whole, specific enough to stand alone. The test is simple: copy the sentence into a blank document and see whether a stranger understands it without the paragraph that came before it.
Can I check whether my content is in the HTML without developer tools?
Yes. Fetch the page with a plain HTTP client such as curl and search the response for the first sentence of your answer. If the text is absent, it is injected by JavaScript after load. Crawlers that do not run scripts will not see it, so server-render that content.
Will adding FAQ schema get me cited in AI Overviews?
No, schema alone does not guarantee a citation. Structured data helps a system understand the page, but the passage still has to be a clear, verifiable, quotable answer. Treat FAQ markup as a way to label good answers, not as a substitute for writing them.