How to Get Your Site Cited in Google AI Overviews

How does an AI Overview work?

An AI Overview is a short generated answer that Google shows above or among the normal results for some searches. It is written by a Gemini model customised for Search, and it is built from pages that are already in Google's index. Next to the answer, Google shows links to the pages it used to support what it says. Those links are the citations, and they are the part you can win.

Google has described a technique it calls query fan-out: for a single search, the system may run several related searches across subtopics, gather pages from each, and then write an answer from the combined set. That has two practical effects:

• You can be cited for a query you do not rank highly for. If your page answers one of the sub-questions well, it can be picked as a supporting link even when it sits on page two for the main query.
• Passages matter more than whole pages. The system needs a piece of text that answers a narrow question clearly. A page that buries its answer in the fourth paragraph of a story is harder to use than one that states it plainly under a matching heading.

AI Overviews do not appear for every search. Google shows them when it judges a generated summary to be helpful, which tends to mean questions, comparisons and how-to searches rather than brand names or single-word navigational searches. They are also not available in every country or language, so whether you see one depends on where and how you search.

What a page needs to be eligible

Before you think about content, make sure nothing technical rules the page out. Each of these is a hard gate: fail one and no amount of writing will get the page cited.

Note what is not on the list. Blocking the Google-Extended token in robots.txt does not remove you from AI Overviews; it controls use of your content for some Gemini products outside Search. If you have blocked it, you have not hurt your chances here. Blocking Googlebot itself, on the other hand, removes you from Search entirely. The AI crawler blocks guide explains which tokens do what.

Why your site is not being cited

When a page is eligible but never appears as a supporting link, the reason is usually one of the following. Work down the table, because the earlier rows are quicker to rule out.

The last row is easy to forget. If Google does not show an AI Overview for a search, there is nothing to be cited in. Check the search yourself, signed out or in a private window, before deciding a page has failed.

How to check where you stand

Start in Search Console. Use URL Inspection on the page you want cited and confirm three things: the URL is on Google, the user-declared and Google-selected canonicals match, and the crawled page contains your answer text. Then check the snippet controls from the command line:

curl -sI https://www.example.com/guides/sourdough-starter/ | grep -i x-robots-tag
curl -s https://www.example.com/guides/sourdough-starter/ | grep -iE 'name="(robots|googlebot)"|data-nosnippet'

Any nosnippet, max-snippet:0 or a small max-snippet value limits what Google can quote. A data-nosnippet attribute around the main answer has the same effect on that passage.

Confirm Googlebot is actually crawling

Do not assume a page has been crawled since you changed it. Check your server's access log for Googlebot requests to that URL:

grep "Googlebot" /var/log/nginx/access.log | grep "/guides/sourdough-starter/" | tail -5

On Plesk the logs for each domain sit under the domain's logs folder, and on Apache the file is usually access_log or access.log. If there is no recent hit, Google is working from an older copy, and you can request indexing in URL Inspection after you publish changes.

Measuring citations

Clicks and impressions from AI Overviews are counted inside the normal Performance report in Search Console, under the Web search type. At the time of writing there is no separate filter for them, so you cannot see AI Overview traffic on its own there. A practical substitute is to keep a short list of your target questions and check by hand, signed out, once a month, noting whether an AI Overview appears and whether your page is linked. Our AI visibility tool can track mentions across AI answers for you.

How to optimise content for AI Overviews

The changes that help most are about making a passage easy to lift and easy to trust. Write for a reader who wants the answer in one look, then give the detail underneath.

• Use the question as a heading. If people search for how long a sourdough starter takes, a heading that says exactly that is a strong signal of what the next paragraph answers.
• Answer in the first sentence. Put a direct, complete answer of one or two sentences straight under the heading, then explain. The first sentence should still make sense if it is read on its own.
• Be specific. Numbers, times, sizes, prices and named steps are more useful to a summary than general advice. Specific facts that only you publish are the strongest reason to cite you.
• Use lists and tables for steps and comparisons. They split cleanly into parts a summary can use.
• Show who wrote it and why they know. A named author with relevant experience, and a visible date when the page was last checked, both help a page look reliable. See the E-E-A-T guide.

Here is the shape of a passage that works well:

<h2>How long does a sourdough starter take to be ready?</h2>
<p>A new sourdough starter is usually ready to bake with after
7 to 10 days of daily feeding at 22 to 25 °C, once it doubles
within 6 hours of a feed.</p>
<p>In a cooler kitchen, below about 20 °C, allow up to 14 days...</p>

Notice that the first paragraph answers the question fully, with the condition that changes the answer. That is the sentence most likely to be used. The content structure guide goes deeper into heading and passage layout.

Does schema help you get into AI Overviews?

Structured data is not required for AI Overviews, and Google has not said it gives a page priority there. It is still worth having, because it helps Google understand what the page is, who wrote it and when it changed, and it keeps those facts consistent with your visible content. The rule is simple: mark up only what is visible on the page, and keep the values true.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How long does a sourdough starter take to be ready?",
  "datePublished": "2026-03-02",
  "dateModified": "2026-10-10",
  "author": {
    "@type": "Person",
    "name": "Sam Example",
    "url": "https://www.example.com/about/sam/"
  },
  "mainEntityOfPage": "https://www.example.com/guides/sourdough-starter/"
}
</script>

Keep dateModified honest: change it when the content changes, not on every deploy. For questions and answers that are already visible on the page, FAQ markup can describe them, although Google stopped showing FAQ rich results in Search on 7 May 2026. The FAQ schema guide covers when it is still worth adding.

The fix, step by step

Edge cases worth knowing

• Cited but no click. Being a supporting link does not guarantee a visit, because some readers stop at the summary. Pages that offer something the summary cannot, such as a calculator, a full method or a price list, give people a reason to click through.
• Cited for the wrong page. If Google links a thin tag page or an old post instead of your main guide, consolidate them: redirect or canonicalise the weaker page and link internally to the one you want.
• The summary gets your facts wrong. Use the feedback option on the AI Overview to report it, then make the passage on your page clearer, with the condition or exception stated in the same sentence as the answer.
• Your brand is mentioned but not linked. AI Overviews can draw on other sites that write about you. Make sure your own page is the clearest source for facts about your business.
• Local and YMYL topics. Health, money and legal searches get extra scrutiny. Author credentials and sources carry more weight there.

Keeping your citations

AI Overviews change as Google's index changes, so a citation is not permanent. Keep a list of 20 to 30 target questions and recheck them monthly. When a page drops out, look first at what changed: a template update that removed the answer text, a new nosnippet from a plugin, or a competitor who now answers more precisely.

• Review pages you rely on at least twice a year and update facts, prices and dates.
• Check the robots meta tag and X-Robots-Tag header after every plugin or theme update.
• Watch server logs for Googlebot errors, especially 5xx responses, which can drop pages from the index.
• Build out the topic: linked pages on related questions make your site a more likely source for the fan-out searches. Our guide to getting cited by AI search engines covers the other assistants too.