Myrah
What Google documents about becoming a supporting link in AI Overviews and AI Mode, and which tactics are not requirements.
Key takeaways
- AI Overview and AI Mode links come from Google Search, so a page must be indexed and snippet-eligible to be shown.
- Google names llms.txt, artificial chunking, and special AI schema as things it does not need.
nosnippet,data-nosnippet, andmax-snippetlimit AI use of your text and cut your Search snippet too.- Google-Extended controls Gemini model development, not Search inclusion or ranking.
- Search Console exposes no AI Overview dimension, so proxies and prompt-level auditing fill the gap.
The short version: links inside a Google AI Overview are drawn from Google Search, and Google LLC's AI features documentation says there is no extra technical requirement, no special markup, and no separate submission. A page has to be indexed, allowed to show a snippet, and the best answer available. So how to improve visibility in Google AI Overviews is the same job as ranking, aimed at the passage a machine can lift.
Most searches about AI Overviews come from people trying to switch the feature off. This guide is the opposite: it is for SEO managers and content leads watching clicks slide on informational queries who want to be shown inside the answer. For the multi-engine version, see brand visibility across AI search engines, and for the category, what AI visibility means.
AI Overview visibility is how often your pages appear as supporting links inside Google's AI-generated answers, in Search and in AI Mode. It matters because those links are selected from Google Search results, so the indexing, snippet eligibility, and answer quality behind a ranking decide whether Google shows you.
Where AI Overview links come from, and how AI Mode differs
An AI Overview is a generated summary shown on the results page with links to the pages behind it. Those links are not drawn from a separate AI corpus: Google's AI features documentation is explicit that they come from Google Search, which is why every eligibility rule below is an ordinary Search rule.
AI Mode is the conversational surface. Google describes it as breaking a question into several related searches and drawing on all of them, so a page can surface for a sub-question you never targeted.
Covering the cluster of things a reader needs therefore beats exact-match targeting of a head term. Answer the main question but skip the three follow-ups, and the page that answered all four wins the fan-out.
The AI Overview eligibility checklist
Confirm the page can be shown before touching the copy. Every row is a pass/fail gate: fail one and the page cannot appear as a supporting link.
| Check | How to verify | What a failure looks like |
|---|---|---|
| Indexed in Search | URL Inspection, live test | "URL is not on Google", or an unexpected canonical |
| Crawlable in robots.txt | Test the path against the Googlebot group |
A Disallow: rule matching the path, often left from staging |
| Snippet allowed | Check source and headers for snippet directives | max-snippet:0, or data-nosnippet around the answer |
| Answer renders server-side | Compare raw with rendered HTML | The answer exists only in JavaScript, or behind a paywall |
| Structured data matches the page | Rich Results Test plus a manual read | Markup for an FAQ, price, or rating a reader cannot find |
| Coverage is unique and substantive | Compare against your own pages on the query | Near-duplicate URLs on one topic; 200 words where a procedure belongs |
Table 1 — AI Overview eligibility checklist. Each item gates whether you can be shown, not where you rank.
In most audits the expensive problem is not prose quality but a page that was never eligible.
Snippet directives: effects on AI Overviews and on Search
This is where teams do accidental damage. Directives controlling preview text control it everywhere, and Google documents no way to sit out AI Overviews while keeping a normal Search snippet.
| Directive | What it does | Effect on AI Overviews and AI Mode | Effect on regular Search |
|---|---|---|---|
noindex |
Drops the URL from the index at the next fetch | Cannot be shown | Removed from results |
nosnippet |
Blocks all preview text for the page | Your text is not used in the answer | No snippet; a bare title and URL |
data-nosnippet |
Blocks preview for the wrapped element only | That passage is excluded; the rest stays usable | That passage cannot appear in a snippet |
max-snippet:[n] |
Caps preview text at n characters (0 none, -1 unlimited) |
Caps available text; no per-feature breakdown published | Truncates the snippet at the cap |
robots.txt Disallow |
Blocks crawling of the path | Content cannot be read, so cannot be used | May stay indexed URL-only |
Google-Extended |
Robots.txt token for Gemini model development | None | None |
Table 2 — Directive effects. The missing per-feature breakdown is a real unknown; re-check the linked docs, verified mid-2026.
The tradeoff is blunt: use nosnippet to keep content out of AI Overviews and you give up your ordinary Search snippet too, leaving a listing people scroll past. data-nosnippet is the surgical option, wrapping only the block you want excluded.
Does schema markup help you rank in AI Overviews?
Structured data is not a requirement for AI features. Google's AI optimization guide names llms.txt, artificial chunking, AI-only rewrites, and special AI schema as things it does not need, pointing instead at crawlability, technical clarity, and unique useful content.
Structured data still helps Google understand a page and qualify it for rich results. The hard rule is that markup must describe content a person can see: FAQPage markup on a page with no visible questions and answers is a mismatch, and a mismatch is a quality problem, not a shortcut.
Google-Extended does not affect your Search rankings
This is the most misread setting in the industry. Google documents Google-Extended as a standalone robots.txt token controlling whether your content helps improve Gemini models and grounds certain non-Search Google products. It is a control token, not a crawler making fetches in your logs.
It does not change Google Search. Disallowing Google-Extended does not remove you from the index, change rankings, or take you out of AI Overviews or AI Mode. Teams that blocked it hoping to opt out of AI answers blocked something else entirely. Other assistants use separate tokens: OpenAI splits search eligibility from model improvement in its bot documentation, and Anthropic and Perplexity AI do likewise.
What changed in May 2026: Preferred Sources and Highly Cited labels
On 2026-05-27 Google announced changes meant to send more visible traffic to original publishers. Preferred Sources, which lets searchers pick sites they want to see more of, expanded into AI Overviews and AI Mode. Some queries now show a prominent link carousel, and "Highly Cited" labels appear more widely.
Read these as presentation changes: Google described no new ranking factor and offered no lever beyond the eligibility and quality work already covered. One dynamic is new: Preferred Sources is a reader-side choice, so people who already look for you can tell Google to show you more.
How to improve visibility in Google AI Overviews at the passage level
Once a page is eligible, AI Overview optimization is a writing problem: make the answer easy to find and safe to quote. How to show up in AI Overviews is an SEO question with a passage-level emphasis. How to optimize for AI Overviews comes down to four shapes: a direct answer near the top, question-shaped headings, tables with explicit units, and ordered procedures with prerequisites stated first.
A weak paragraph, rewritten
Before:
Payment terms are something a lot of businesses think about, and the options vary depending on your client relationship and the norms in your industry. Net 30 is one of the more common arrangements.
After:
Net 30 means the full invoice amount is due 30 calendar days after the invoice date. Not 30 business days, and the clock starts at the invoice date, not delivery. On an invoice dated 3 March, payment is due 2 April.
The rewrite answers in the first sentence, states the unit, and adds a worked example. It can be quoted whole without surrounding context, which is what a generated answer needs.
A six-step pass
Prerequisites: Search Console access, a way to view rendered HTML, and 20 to 30 informational queries the page should own.
- Run the checks in Table 1 and fix every failure before editing copy.
- Rewrite the first 60 words under the H1 into a direct answer, with units stated.
- Turn vague headings into the question wording readers use, so each H2 stands alone.
- Add a 40 to 60 word definition block for the central term, set off to be lifted whole.
- Replace comparison paragraphs with tables carrying explicit units, marking unknowns as unknown.
- Rebuild each how-to section as a numbered procedure with prerequisites before step 1, then confirm the rendered HTML contains it.
Start with your ten highest-intent informational pages. Myrah's visibility workflow turns these gaps into ranked actions when auditing dozens.
How to measure Google AI Mode visibility without a Search Console breakout
Search Console gives you no "AI Overviews" filter. Clicks and impressions from AI features are counted with the rest of your Search performance data rather than split out, so you cannot isolate them. Re-check Google's AI features documentation, verified as of mid-2026, since reporting changes.
What AI Overviews trackers can and cannot tell you
Rank trackers that flag SERP features are the usual proxy, and roundups of the best AI Overviews trackers mostly differ on sampling frequency and location coverage. Every AI Overviews tracker samples: it records what one automated query saw at one moment, from one location, without your reader's account state. Treat the output as a trend line, paired with click-through rate on affected queries. For citation counting, see AI citation tracking.
Prompt-level auditing fills the rest. Myrah's four-stage methodology runs Prompt Construction, Provider Selection, Query Execution, and Response Parsing across four engines, including Google Gemini, scoring each on presence at 55%, prominence at 30%, and citation at 15% on a 0 to 100 scale. Be clear what that measures: assistant answers to buyer-intent prompts, not AI Overviews directly. Gemini grounding returns inline citations through the Gemini API, a different surface. The math sits in measuring visibility in AI.
Honest limits: eligibility never guarantees selection
Passing every check here makes you eligible. It does not make you chosen. Google generates these answers per query: the same question can produce different summaries and different links depending on phrasing, locale, device, and the searcher's own settings, which now include Preferred Sources.
A single observed answer is not a rule. Check one query on one laptop, conclude a tactic works, and you have a sample of one from a system built to vary. Sample the same questions over weeks before calling anything a pattern.
Frequently asked questions
How do I get my site into Google AI Overviews?
Get the page indexed, keep it crawlable, allow snippets, and make it the clearest answer to the question. Google's AI features documentation states the links come from Google Search, so there is no separate submission, no AI-specific schema, and no step beyond ordinary Search eligibility.
Do AI Overviews use different ranking than regular search?
They draw on the same Google Search systems. Google documents AI Overview and AI Mode links as coming from Search results, which is why eligibility is defined by indexing and snippet permission. AI Mode adds a fan-out across related queries, so sub-question coverage matters more there.
Does schema markup help AI Overviews?
Not as a requirement. Google's AI optimization guide lists special AI schema among the things it does not need. Structured data still helps Google understand a page and qualify it for rich results, but it must describe content visible on the page. Mismatched markup is a problem.
Should I block AI Overviews with nosnippet?
Rarely. nosnippet removes your preview text everywhere, so you lose the regular Search snippet along with any AI use, leaving a bare title and URL. To protect one licensed passage, wrap that element in data-nosnippet and leave the rest of the page eligible.
Does Google-Extended affect my Search rankings?
No. Google documents Google-Extended as a robots.txt control token for Gemini model development and grounding in certain non-Search products. Disallowing it does not remove pages from the index, change rankings, or take you out of AI Overviews or AI Mode.
Can I track AI Overview appearances in Search Console?
Not as a separate dimension. AI feature clicks and impressions are counted with the rest of your Search performance data, so no filter isolates them. Teams use rank trackers that flag the feature, click-through changes on affected queries, and prompt-level auditing as proxies.
Conclusion
The question was how to improve visibility in Google AI Overviews, and the answer is narrower than the internet suggests: be indexed, be snippet-eligible, be the best answer, and write passages a machine can lift without distorting them. Google has published what it does not require, and that list covers most of what is sold as AI-specific.
Your next step is Table 1: run the eligibility checklist against your ten highest-intent informational pages this week, and fix the gates before rewriting a paragraph. For the same diagnosis across every assistant, run an AI visibility audit.
Sources
- Google, AI features and your website: https://developers.google.com/search/docs/appearance/ai-features
- Google, AI optimization guide: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Google, Google-Extended: https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers#google-extended
- Google, New ways Search is connecting people with original, high quality content, 2026-05-27: https://blog.google/products-and-platforms/products/search/original-high-quality-content-search/
- OpenAI, Bots: https://developers.openai.com/api/docs/bots
- Google, Grounding with Google Search: https://ai.google.dev/gemini-api/docs/google-search
- Schema.org, FAQPage: https://schema.org/FAQPage