Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# Why doesn't Google AI Overview mention my brand

Google AI Overview does not mention your brand because, for the queries you checked, one of three things happened: the overview never appeared, your page was not eligible to be a supporting link, or your page was eligible but another page gave Google a better passage to quote. Google says AI Overviews only appear when its systems judge them additive to classic Search, and often they do not trigger at all. Google also says there are no additional technical requirements to appear, and no special schema markup you need to add. The bar is the ordinary one: a page must be indexed and eligible to be shown in Google Search with a snippet. Past that bar, the overview quotes passages that answer the question and the subquestions behind it. If a competitor's page has those passages and yours does not, the competitor gets the link.

## The four ways a brand goes missing

1.  The overview never triggered. You cannot fix a missing mention for a query that produced no overview. Check the query in Search first, with no assumptions, and log whether an overview appeared at all.
2.  The page is not indexed or not snippet eligible. A page Google has not indexed cannot be a supporting link. A `nosnippet` rule prevents the content from being used as a direct input for AI Overviews and AI Mode. A `max-snippet` rule limits how much of it can be used. A `data-nosnippet` attribute excludes a section of the page. A `noindex` rule removes the page from Search entirely, which also removes it from AI Overviews. Any of these can be set site wide by a plugin, so check the page itself.
3.  The page is eligible but says nothing quotable. Google describes the process as retrieval-augmented generation: it retrieves relevant, up-to-date pages from the Search index, reviews the specific information on those pages, and generates a response grounded in what it retrieved, with links to the pages that support the answer. A citation attaches to a passage, not to a whole page. A product page that lists a name and a price, with no direct answer and no specifics, gives the overview nothing to quote.
4.  The page is a copy of what everyone else says. Google's guide says content with a unique point of view and first-hand experience stands out, while commodity content that restates common knowledge adds little. A page that repeats the same advice as ten other sites loses the quote to the page that adds a test, a measurement, or a detail only the seller would know.

## Step 1: Check whether the overview triggers, then check eligibility

Run the query yourself and record whether an overview appeared. If it did not, the work is not on that page yet. It is on finding the queries where overviews do appear for your category, and building pages for those. If it did appear, check the page in the URL Inspection tool in Search Console and confirm Google has indexed it. Then read the page source for `nosnippet`, `max-snippet`, and `data-nosnippet`, and confirm the page is not set to `noindex`. Two mistakes live here. First, blocking Google-Extended does not remove a page from AI Overviews. Google-Extended governs AI training and grounding in some of Google's other systems, not Search. The control that matters for AI Overviews is Googlebot access plus the snippet controls above. Second, a site can be excluded from Search generative AI features in Search Console, so confirm that setting includes your site.

## Step 2: Let Googlebot reach the page

Confirm crawling is allowed in robots.txt and by any CDN or hosting infrastructure in front of the site. A firewall or bot protection rule that blocks Googlebot keeps the page out of the index, and an unindexed page cannot be cited. Google's own checklist for AI features adds the rest: make the content findable through internal links, keep important content in textual form, give the page a good page experience, and make sure structured data matches the visible text on the page. If the page sells products or serves local customers, keep Merchant Center and Business Profile information up to date, since Google says that information can appear in AI responses as well as in regular results. For the full crawler reference, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search).

## Step 3: Write the passage the overview needs

Put a short, direct answer under each question heading, then support it with specific facts: a price, a condition, a measurement, a first-hand detail. Cover the follow-up questions on the same page, since Google says its systems issue multiple related searches across subtopics and data sources to build a response, and identify more supporting pages while the answer is being written. A page that answers the follow-up questions well has more chances to be picked than a page that answers only the headline question. Do not create a separate thin page for every variation of a question to chase those subqueries. Google warns that creating pages mainly to manipulate rankings or generative responses violates its scaled content abuse policy, and that a high quantity of pages does not make a site higher quality. Google also says you do not need new machine-readable files, AI text files, markup, or special schema to appear in AI Overviews, and that Google Search does not use llms.txt. There is also no requirement to break content into tiny pieces. Google's systems can find the relevant section of a longer page, so page length should fit the audience, not a supposed AI format.

## Step 4: Fix the FAQ shape, not the rich result

Add a visible FAQ section to the pages where buyers ask the same questions, with one question and one direct answer each, written in plain text a visitor can read. Then, if you want, label those questions and answers with FAQPage markup from schema.org, keeping the markup identical to the visible text. Here is the part the old advice gets wrong: Google has removed the FAQ rich result feature from Search, and it has removed the FAQ rich result documentation. Do not add FAQPage expecting a dropdown rich result in Google. That visual result is gone. What remains is the schema itself, which is still a valid schema.org type, and the question-and-answer shape, which is still the shape AI systems extract most easily. Add it as an extraction aid, not as a rich-result play. There is no Google FAQPage document to link to, because Google removed it. The schema.org page in Sources defines the type.

## Step 5: Measure it in Search Console

Google points site owners to the Generative AI performance report in Search Console to see how content performs in generative AI features on Google Search. Traffic from AI features is also included in the ordinary Performance report, under the Web search type. Check the vendor docs in Sources for the current path to the report. Google also reports that clicks from pages with AI Overviews are higher quality, meaning users are more likely to spend more time on the site. A mention that brings fewer clicks can still bring better visits. Log which queries show an overview, which of your pages were cited, and which competitor pages were cited instead, then repeat the check on a schedule instead of judging from one run.

### Say you run a kitchenware brand

Say you run a kitchenware brand that sells cast-iron skillets. You search for how to season a cast-iron skillet and an overview appears, citing a competitor's care guide and a cooking site, but not you. Your care page is indexed, Googlebot can reach it, and no snippet control blocks it, so eligibility is not the problem. The problem is the page itself. It opens with a paragraph about your brand history, then lists three care tips with no specifics. The competitor's guide opens each section with a direct answer, then gives a temperature, a time, an oil, and a mistake to avoid, all from first-hand use. You rewrite your page the same way, with a short answer under each heading and the specific numbers a cook needs, and you add a visible FAQ section answering the three questions buyers ask most, with matching FAQPage markup. You rerun the query and check Search Console. The competitor does not disappear. Your guide starts appearing as a supporting link on the subquestions your passages answer.

### The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

-   •llms.txt: the file format, a complete sample, and per-platform publish steps, see our [guide to writing a good llms.txt file](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)
-   •Product schema: the JSON-LD markup models read to verify price and availability in structured form, see our [product schema guide for AI search](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •Every AI crawler in one reference table, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

## What this guide does not cover

This guide covers Google AI Overviews only. ChatGPT, Perplexity, Claude, and Gemini each run their own crawlers and indexes, so a mention here says nothing about the others. It also does not cover keeping a mention favorable over time, or the transaction layer that turns a mention into a sale.

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows exactly where your site stands with every AI crawler today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   Google Search Central, AI features and your website (specific): [https://developers.google.com/search/docs/appearance/ai-features](https://developers.google.com/search/docs/appearance/ai-features)
-   Google Search Central, Optimizing your website for generative AI features on Google Search (specific): [https://developers.google.com/search/docs/fundamentals/ai-optimization-guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)
-   Google Search Central, Latest documentation updates, FAQ rich result removal (specific): [https://developers.google.com/search/updates](https://developers.google.com/search/updates)
-   Google Search Central, Robots meta tag specifications (specific): [https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag)
-   Schema.org, FAQPage type (general standard): [https://schema.org/FAQPage](https://schema.org/FAQPage)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
