Short answer: to appear in Google AI Overviews you do not apply, submit or allow a special crawler, because none exists. Overviews are part of Google Search, the fetching behind them is done by Googlebot, and the work you control is being crawlable and indexable, putting the answer in the HTML as a passage that stands on its own, and keeping pages dated and current for questions that need a current answer. The only AI Overviews-specific control Google offers runs the other way: a Search Console setting, announced in June 2026, that lets a site opt out. Google-Extended, often mistaken for an Overviews switch, governs Gemini training and grounding and does not affect Search.

Nothing below guarantees that an Overview will name or cite you; Google decides that per query. What you can do is remove the reasons you would be ineligible, write pages that are easy to quote, and measure presence honestly so you know whether anything changed.

How Google AI Overviews choose pages: eligibility starts in Search

When people ask how to "let AI Overviews in", they usually expect an agent name to add to robots.txt, the way OAI-SearchBot works for ChatGPT search. Google is built differently. In Google's crawler documentation the agents that matter here are Googlebot, which does the fetching, and Google-Extended, which is not a crawler at all but a usage control: it decides whether content Googlebot already crawled may train Gemini models and ground answers in Gemini Apps and Vertex AI. The same documentation states that it does not affect inclusion or ranking in Google Search.

Being highly ranked is not the requirement either. Ahrefs analysed 863K keyword results pages and 4M URLs cited in AI Overviews and found that 37.9% of cited URLs also appeared in the first 10 result blocks; 31.2% came from positions 11 to 100 and 31.0% from beyond the top 100. Ahrefs compares this with roughly 76% in its July 2025 study, notes that it improved its parsing in between and that AI Overviews moved to Gemini 3 in January 2026, and suggests Overviews now lean more on sources surfaced by query fan-out, the technique Google describes for AI Mode of issuing several related searches at once. Indexing is the entry ticket; a page-one ranking is not.

That leaves four controls that people confuse. They do very different things:

Which Google control does what you actually want?Documented effects only. None of these makes an Overview more likely to show you.WHAT YOU WANTWHAT DOES ITAppear in AI OverviewsNo control existsBe indexable, quotable and current; Google decides per queryStay in Search, but keep content outof Gemini training and groundingDisallow Google-ExtendedSearch inclusion and ranking explicitly unaffectedStay in Search, but leaveAI Overviews and AI ModeSearch Console AI opt-outAnnounced June 2026; first a subset of UK site ownersLeave Google entirelynoindex, or block GooglebotRemoves Search and Overviews together
Figure 1. The four Google controls people confuse, matched to the outcome each one actually produces. Only removal has a switch; appearing in AI Overviews does not. Source: Google’s crawler documentation and Google’s June 2026 announcement of new controls for website owners.
ControlGoogle SearchAI Overviews and AI ModeGemini Apps and Vertex AI
Do nothing (indexable page)EligibleEligible; Google decides per queryEligible
Disallow Google-ExtendedExplicitly unaffectedNot described as affectedNo training, no grounding
Search Console AI features opt-outNot used as a ranking signal outside those featuresNo traffic or impressions from themNot described
noindex, or blocking GooglebotRemovedRemoved, since Overviews sit on SearchNot described

The Search Console control lets a site opt out of appearing in, and helping ground, AI Overviews, AI Mode and AI Overviews in Discover; Google says it was first rolled out to a subset of website owners in the UK. Blocking Googlebot to keep content away from AI is the one move that costs you everything. If you decide to disallow Google-Extended, record it with a comment, because no request ever arrives under that name and the next person will not see why it is there:

# Gemini training and Gemini grounding only.
# Googlebot rules are unchanged, so Search is unaffected.
User-agent: Google-Extended
Disallow: /

Our post on Gemini and Google-Extended covers the Gemini side of that decision.

Step 1: make sure Google can index the page at all

Since Overviews sit on top of Search, a page that is not indexable is not a candidate. The causes are rarely exotic. They are platform settings that quietly do more than their label suggests:

PlatformWhat silently removes pagesHow to check
WordPress"Discourage search engines from indexing this site" emits noindex and also disables core XML sitemaps, so /wp-sitemap.xml returns 404. A staging site promoted with the box ticked loses both.Settings, Reading; then load /wp-sitemap.xml and /robots.txt.
ShopifyA password-protected store's sitemap is not reachable by crawlers. The default robots.txt also disallows /search and filtered collection URLs, which is intended but worth knowing.Remove the password before launch; read /robots.txt on the live domain.
WebflowThe webflow.io staging subdomain can serve a blocking robots.txt that your custom domain does not.Audit robots.txt on the custom domain, never on the staging URL.
HubSpotSystem domains containing hs-sites are permanently no-index, and landing pages are not added to the sitemap automatically.Add landing pages to the sitemap by hand; check each connected domain.

The WordPress case is documented in the WordPress 5.5 sitemaps announcement. Page-level directives can override everything else, so check the response headers as well as the HTML: an X-Robots-Tag header sent by a CDN rule is invisible in view-source. Our guide to meta robots and X-Robots-Tag walks through both.

Step 2: put the answer in the HTML, as a passage that stands alone

An Overview is assembled from passages, not from whole pages. Two things decide whether your passage is usable: whether it is in the page at all, and whether it still makes sense once it is lifted out.

On the first point, aim for the answer being in the initial HTML. Whatever Google's own renderer manages, server-delivered text is the version every agent receives, including the AI crawlers that do not execute JavaScript. Watch the platform-specific gaps: on Shopify, content fetched through the Ajax Section Rendering API and blocks that apps inject client-side, such as reviews and Q&A, are not in the server HTML; on HubSpot, text that lives inside an embedded form is filled in client-side.

On the second point, three habits do most of the work:

  1. One question per heading, phrased the way a person would type it into Google.
  2. The answer in the first sentence under the heading, with the subject named in full rather than a pronoun that only works next to the heading.
  3. Facts with units and dates. "Delivery to Canada takes five to eight working days" can be quoted. "Shipping times vary" cannot.

If you use FAQ markup, the questions and answers must also be visible text on the page; markup describes content and does not replace it. Writing for extraction has before-and-after rewrites of real passages.

Step 3: write for the query shapes that trigger AI Overviews

Not every query gets an Overview, and the shape of the question matters a great deal. In Seer Interactive's tracking of 30,842 informational queries, comparison queries triggered an AI Overview 95.4% of the time and question-format queries 85.9% of the time.

How often a query shape triggered an AI OverviewShare of tracked informational queries showing an AI Overview. Seer Interactive, 30,842 queries, April 2026.Comparison queries267 of 280 queries95.4%Question-format queries1,214 of 1,413 queries85.9%
Figure 2. Comparison and question-shaped queries almost always showed an AI Overview in Seer’s tracked set, which is why comparison pages and question-led headings deserve the most care. Source: Seer Interactive, AI Overview impact on Google CTR, 2026 update, published April 2026.

For a site, that points to two kinds of page worth getting right. The first is the comparison page: it matches the shape of a comparison question directly, and one that states its method and criteria is far more quotable than one that only lists products, because the method is itself a passage that can be lifted. The second is the page that answers a full question under a heading that repeats it, which is the shape Step 2 describes.

Many of these questions also imply a current answer: prices, comparisons, "best" lists, policies. Pages that state a real published and modified date have an advantage on those over undated pages, and over pages whose modified date is bumped by every deploy. The second case is worse than it looks, because a date that changes while the content does not is a claim a crawler can check. Our guide to content freshness and dates explains how to stop a build pipeline from rewriting dates.

Step 4: measure presence in AI Overviews, then clicks separately

There is no tenth place in an Overview. For each question, record three outcomes separately: whether an Overview appeared, whether your brand was named, and whether your page was cited as a source. Being cited and being recommended differ too: your page can be a source while the summary points the reader to someone else.

  • Use a fixed question set without your brand name in it. A question that names you will be answered about you. In one of our own runs, 13 of 15 generated questions contained the brand name, and the score read 13% when the honest value was zero.
  • Never record a failed check as zero. A query where no Overview appeared, or the check timed out, produced no evidence. Counting it as "absent" drags the rate down and invents a decline.
  • Believe a change only after two consecutive runs. AI answers vary between runs even when nothing changed.

Google now gives you a first-party count as well. Search Console's generative AI performance reports, announced on June 3, 2026 and open to all websites as of August 31, 2026, show impressions in AI Overviews, AI Mode and generative features in Discover by page, country, device and date. The announcement lists no click metric, so it tells you where you appeared, not what that was worth.

Clicks need their own section in any report, because presence and traffic move differently. Seer Interactive's data across 53 brands shows how far apart they sit:

Organic click-through rate with and without an AI OverviewSeer Interactive: 53 brands, 5.47M tracked queries, published April 2026.AI Overview shownDecember 2025, the low point1.3%AI Overview shownFebruary 20262.4%No AI OverviewFebruary 20263.8%
Figure 3. Click-through on queries with an AI Overview recovered from its December 2025 low but stayed below queries without one. Presence and clicks are separate outcomes and belong in separate sections of a report. Source: Seer Interactive, 2026 update, published April 2026.

Seer also found that pages cited in the Overview earned +120% more organic clicks per impression than uncited pages on informational queries, while still trailing queries with no Overview by -38%. Seer is explicit that this is directional and does not prove that being cited causes the extra clicks. The practical reading is modest: being cited is better than not being cited, and neither restores the clicks of a results page without an Overview. The glossary entry on AI Overviews defines the terms used here.

Sources