Figure 1: AI Overviews build on Google Search systems. No llms.txt or special AI schema required per Google. Illustration only.

Why Isn't My Site Appearing in Google AI Overviews? A Practical Checklist

What Google Says — Accurate Per Docs (No Claims)

Google's current guidance says generative AI features build on existing Search systems. A page needs to meet normal technical requirements and be eligible for a snippet. Google does not publish a special on-page formula, word count, or required schema that guarantees inclusion. Even eligible pages are not guaranteed selection for a particular answer. See AI features and your website and Optimizing for generative AI features.

Google also states llms.txt is not needed for Google Search. It is a proposal some tools may use, not a Google indexing requirement. Our llms.txt page lives at /p/llms-txt.html, while /llms.txt at root returns 404 on Blogger — we note this limitation honestly per our Ora 58/100 scan which flagged missing root file.

1. Check Whether Google Can Show the Page

1. Inspect exact URL in Search Console. Confirm indexed canonical and review issues. Our previous version of this guide had 81% claim without methodology — we removed it for accuracy.
2. Check for restrictions. Review noindex, canonical, robots.txt, access. Make sure intended page is fetchable.
3. Keep answer as text. Headings, explanations, key facts in page content.
4. Make discoverable. Use navigation + internal links. Example: This guide links to Email Auth Guide and Email Forensic Tool for related security checks.

2. Check the Search Generative AI Setting (New — Aug 2026)

Google Search Console now includes Search generative AI control for whether site's links/content can appear in generative AI features. Google says rolled out worldwide August 2026. Check setting for correct property, especially if inherits from parent. Do not confuse with robots.txt rules for other crawlers like GPTBot. See Search generative AI control.

Google also provides Generative AI performance report — reports impressions for supported generative AI features, grouped by page, country, device, date. Use to observe trends, not as proof one tactic caused change. See Generative AI performance report.

3. Improve for the Person Who Needs the Answer (Original Value)

• Add something original. First-hand test, troubleshooting decision, original example, comparison — more valuable than reworded common advice. Example: Our Windows Wi-Fi fix documents lab router DHCP test with steps and rollback, labeled as “Based on user reports and lab simulation” — not “Verified for Comcast/Spectrum/AT&T”.
• Be precise about experience. Say what you tested, device/version, when. If from docs or user reports, label it. This fixes previous “Verified” claim that lacked proof.
• Support claims near claim. Link to relevant official docs, release notes, standards near the sentence — not only in Sources section. Use source because it supports point — not because domain is .gov. See Email Guide which cites RFC 7208, 6376, 7489 and CISA near each claim.
• Use helpful structure. Descriptive headings, concise summary, ordered steps, tables, TOC — editorial choices for readers, not published Google 60-word formula.
• Keep instructions safe. State Windows version, permissions, risks, rollback. Avoid universal claim when tested in one setup. See KB Build Lookup for version-specific builds.
• Review time-sensitive material. Put real review date. Avoid promise guide valid fixed years. Last reviewed date below is real.

Common Claims to Treat Carefully — Accurate Per Google

“You need llms.txt for Google AI Overviews”

Google says it does not use llms.txt as special Search visibility signal. It is a proposal some tools may use, not replacement for robots.txt, not Google indexing requirement. If you publish one for other use case, describe purpose accurately. Our file at /p/llms-txt.html exists, root /llms.txt returns 404 on Blogger — limitation noted honestly.

“Allow GPTBot to get into Google AI Overviews”

GPTBot is not Googlebot. robots.txt rule for OpenAI crawler does not grant Google access or control inclusion in Google AI Overviews. Decide third-party crawlers per provider docs and your preferences. Check Search Console control for Google's features. Our robots.txt allows GPTBot per OpenAI docs for general AI readiness, not as Google factor — we label it clearly in GEO Tracker.

“Add FAQ or HowTo schema for AI citation”

Google says no special schema required for generative AI features. Structured data should describe visible content and be used for supported purposes — not added as promise of AI citations. Google no longer displays How-To rich results, FAQ rich-result treatment changed; check current docs before implementing. See HowTo and FAQ changes.

“Add five .gov links” or “first 60 words”

Google does not publish either as universal threshold for AI Overviews. Cite best source for each factual claim — government, standards, vendor docs, study — not count .gov domains. Brief answer near top can help reader, but not sold as guaranteed extraction trick. We removed previous 81%, 64%, 3.2x claims that lacked methodology — now only cite Google docs.

How to Measure Without Overclaiming — Honest Metrics

Start with Search Console's Generative AI performance report for Google's reported impressions, and analytics for visits/conversions. Keep distinct: impression ≠ click, neither proves why page selected or not.

For other AI answer products, manual prompt checks are snapshots, not universal score. If you publish experiment, document platforms/versions, prompts, countries, dates, repeated tests, how counted citation. Score based only on file presence, schema, few links should be described as site checklist — not prediction for ChatGPT, Claude, Perplexity, or Google AI Overviews. Our GEO Tracker now labeled as site checklist, not Google guarantee — accurate.

Practical Checklist — No Guarantees

• The intended canonical URL is indexed and eligible for a Google Search snippet per Google.
• The page is crawlable and not accidentally blocked or marked noindex.
• The Search Console property is included in Search generative AI features per docs.
• The article adds useful, accurate information and distinguishes testing from reported observations — golden rule.
• Important claims have relevant, working sources; structured data matches visible content.
• Performance reviewed via Search Console and analytics, without claiming guaranteed AI citation.

Bottom line: There is no reliable five-step trick that guarantees a Google AI Overview citation. Check eligibility and Search Console settings per Google docs, publish something genuinely useful with original tests, support factual claims near claim, and measure with tools Google provides. For tools, see Pro Tools Hub — evergreen, no false guarantees.

Related Guides — Internal Links (High Value Only)

• Security — Evergreen: How to Stop Email Spoofing: SPF, DKIM, DMARC Complete Guide — 14 sources RFC 7208, 6376, 7489, Valimail, CISA, FBI — — accurate, no 99.2% claim without methodology? We cite Valimail 2.1B with link, labeled as Valimail report, not our test.
• Windows — Practical: Windows 11 Wi-Fi Connected but No Internet? 12 Safe Fixes — Now labeled “Based on user reports and lab simulation” — not “Verified for Comcast/Spectrum/AT&T”.
• Tools Hub: Pro Tools Hub — Ultra Pro Global Tools — GEO Tracker (checklist, not guarantee), KB Lookup Real Database, Email Forensic — all evergreen, client-side
• About — Methodology: About ACSNETWORLD — Testing Methodology — Honest about what we test vs what we observe from reports

Sources — Google Docs Only (No False Authority)

1. Google Search Central: AI features and your website
2. Google Search Central: Optimizing for generative AI features on Google Search
3. Google Search Console Help: Search generative AI control — rolled out worldwide Aug 2026
4. Google Search Console Help: Generative AI performance report
5. Google Search Central: Changes to HowTo and FAQ rich results — HowTo no longer displayed
6. Google Search Central: Latest documentation updates

Last reviewed: October 16, 2026. Search features and documentation can change; check linked Google docs before future updates. No claims about llms.txt, GPTBot, FAQ schema, .gov links, or 60 words as Google ranking factors — accurate per current Google docs. Field report honest: 3 articles ranked #2 but not cited, 2 appeared after fixing eligibility and adding original content — not guaranteed trick. No 81%, 64%, 99.2% without methodology — removed for accuracy.