# heybuffy.com — full content for LLMs
> Concatenated Markdown of Buffy's glossary + articles for AI ingestion. Canonical pages at https://heybuffy.com. Generated at build time from source Markdown.

# Glossary (98 terms)

## Action Plan
Source: https://heybuffy.com/glossary/action-plan

Measurement is only useful if it tells you what to do next. The Action Plan turns the metrics into a prioritised, regularly-refreshed to-do list. Ranked by likely impact. Across three pillars:

- **Owned**: publish or improve content on your own domain (the pages you fully control).
- **Earned**: engage with third-party publications, community threads, and creator content where you should be present but aren't ([why earned coverage matters](/blog/why-ai-loves-listicles)).
- **Optimize**: improve prompts where you're already mentioned but rank, sentiment, or product detail need work.

The pillars map to *how* AI builds answers: it pulls from your pages (Owned), from third-party sources it trusts (Earned), and weighs how clearly each describes you (Optimize). Rather than a dashboard you have to interpret, it's the prescriptive layer. The specific next moves, in order, that separates monitoring from actually improving.

## Agentic browser
Source: https://heybuffy.com/glossary/agentic-browser

An agentic browser is a web browser with a built-in AI **agent** that can act on the web, not just render it. Alongside ordinary browsing, it can read and summarise a page, hold several open tabs in context to compare options, fill forms, and carry out multi-step tasks from a natural-language instruction, closer to [conversational search](/glossary/conversational-search) with hands. Perplexity's Comet and The Browser Company's Dia are leading standalone 2026 examples; OpenAI retired its standalone ChatGPT Atlas browser in August 2026 and moved the same agentic browsing into the ChatGPT app.

Agentic browsers matter for AI visibility because they are a **distinct surface**. Where an AI chatbot answers inside its own app from a retrieval index, an agentic browser reads the live, visible page of the real sites it opens and acts across them, so the current, extractable state of your site decides whether the agent can use you. Each browser also routes through a different underlying model, so brand recall varies; monitoring only one engine understates your exposure.

In practice, being usable by an agentic browser means the same discipline as AI-search visibility, sharpened: expose prices, specs, and availability as server-rendered plain text; add [structured data](/glossary/structured-data); keep task flows completable; and make sure AI agents aren't blocked before they arrive. It overlaps heavily with [agentic commerce](/glossary/agentic-commerce), because shopping and checkout are exactly the tasks these agents carry out, often via a [shopper agent](/glossary/shopper-agent) fanning one request into many.

## Agentic Commerce Protocol (ACP / UCP)
Source: https://heybuffy.com/glossary/agentic-commerce-protocol

An agentic commerce protocol is an open standard that lets an AI agent not just *recommend* a product but actually *buy* it. By defining how a merchant exposes product data, pricing, availability, and checkout in a machine-readable form an agent can act on.

As of mid-2026 the prominent examples are the **Agentic Commerce Protocol (ACP)**, developed by OpenAI with Stripe, and Google's **Universal Commerce Protocol (UCP)**. They differ in shape and naming but point the same way: a structured product feed plus a checkout an agent can complete. Payment and distribution layers (such as Stripe's Agentic Commerce Suite) are emerging to bridge across protocols so a merchant integrates once.

The protocols handle the *plumbing* of the transaction. They don't decide *which* product an agent recommends, that still comes down to catalog quality, [entity clarity](/glossary/entity-authority), and corroboration. Protocol details are moving quickly; the durable takeaway is that a clean, structured catalog feeds whichever standard wins.

## Agentic Commerce
Source: https://heybuffy.com/glossary/agentic-commerce

Agentic commerce is shopping carried out by an AI agent on a person's behalf. Instead of browsing a store, the shopper tells an assistant what they need, and the agent discovers options, compares them, and. Increasingly. Completes the purchase.

The shift is from *human browsing* to *machine selection*. That changes what it takes to get bought: an agent can only choose products it can find, understand, and act on. A catalog locked in images or JavaScript, or thin on [structured data](/glossary/structured-data) and attributes, is invisible to it. No matter how good the product is.

Winning here means making your catalog legible to machines: complete, structured product data; clear pricing and availability; and the kind of detail an agent needs to match your product to a shopper's intent. The emerging [commerce protocols](/glossary/agentic-commerce-protocol) standardize how that data and the checkout itself are exposed to agents.

## AI content licensing deal
Source: https://heybuffy.com/glossary/ai-content-licensing-deal

An AI content licensing deal is a paid agreement in which a content owner grants an AI company permission to use its material — for training a model, grounding live answers, or both — in exchange for money or other terms. It is the negotiated alternative to an AI company obtaining content by crawling it for free or by scraping it against the owner's wishes.

These deals became a distinct market by 2026. Reported examples include News Corp's licence with OpenAI (over $250M across five years), News Corp with Meta (up to $50M/year), Amazon with The New York Times ($20–25M/year), and Google with Reddit for Gemini training. Most deals publish no financial terms, so figures are those a publisher or filing disclosed, dated mid-2026.

The defining feature of the moment is that licensing runs **alongside litigation**. The same publisher may license to one operator and sue another: News Corp licenses to OpenAI and Meta while suing Brave over allegedly disguised crawlers. So a licensing deal is best read as one of three postures a content owner can take toward AI crawlers — license, litigate, or block — not a settled norm.

For a brand thinking about AI visibility, licensing matters because it keeps content **readable, and therefore citable**, while capturing value from access — the opposite trade-off to blocking. Direct deals are largely a large-publisher lever today; metered access over standards like [x402](/glossary/x402) is the emerging equivalent for smaller sites.

## AI Crawler (bot)
Source: https://heybuffy.com/glossary/ai-crawler

An AI crawler is an automated bot that fetches your web pages on behalf of an AI company. Each one identifies itself with a **user-agent** name. `GPTBot` and `OAI-SearchBot` (OpenAI), `ClaudeBot` (Anthropic), `PerplexityBot` (Perplexity), `Google-Extended` (Google).

They do one of three jobs, and the distinction matters: **training** crawlers gather text to teach future models, **indexing/search** crawlers build the index an engine searches at answer time, and **live-answer** fetchers pull a specific page the moment a user's question needs it. Blocking the wrong one can quietly remove you from AI answers.

You control which crawlers may access your site through [robots.txt](/glossary/robots-txt) (and signal structure with an [llms.txt](/glossary/llms-txt)). But access alone isn't enough. A bot that *can* reach a page still needs clean, [structured](/glossary/structured-data) HTML to understand and [cite](/glossary/citation) it.

## AI Hallucination
Source: https://heybuffy.com/glossary/ai-hallucination

A hallucination is when an AI states something that sounds confident and plausible but is simply wrong. An invented statistic, a feature you don't offer, a product that doesn't exist, or a fabricated source.

For brands this is a real risk, not a curiosity: an engine working from stale or thin information can describe you inaccurately. Wrong pricing, a discontinued product, a capability you've never had, and present it as fact to a buyer. Because the answer reads authoritatively, users rarely question it.

The fixes are the same ones that improve visibility generally: make accurate, current, well-structured information about your brand easy to retrieve, so the engine [grounds](/glossary/grounding) its answer in your facts instead of guessing from memory. You can't stop hallucination entirely, but you can starve it. The more clearly the truth is reachable, the less room there is for the model to invent.

## AI Mode ads
Source: https://heybuffy.com/glossary/ai-mode-ads

AI Mode ads are Google's paid text advertisements shown inside [Google AI Mode](/glossary/google-ai-mode) answers, placed by the ad auction rather than by the answer's retrieval step. They appear as labelled sponsored slots alongside or within the AI-generated response, most often on commercial, high-intent queries.

They are common on such queries but distinct from citations. In a July 2026 SE Ranking study of 50,032 commercial keywords (US, data collected 30 June 2026), about 29% of the sampled commercial queries showed a text ad, and 71% of those placements displayed two competing ads side by side. Crucially, buying an ad bought no citation advantage: for the keywords a brand advertised on, its domain appeared among the cited sources only about 11.5% of the time, and once domain strength and organic standing were controlled for, advertisers were cited no more often than non-advertisers (single-vendor, one snapshot, directional).

The practical point for AI visibility: an AI Mode ad is paid media (advertising you buy), a demand-capture slot, while a [citation](/glossary/citation) is [earned media](/glossary/earned-media), won by extractable, corroborated content and entity strength. The two are decided by different systems, so ad spend and citation share should be budgeted and measured separately, as they are for [AI Overviews](/glossary/ai-overviews) too.

## AI Overviews
Source: https://heybuffy.com/glossary/ai-overviews

AI Overviews are Google's AI-generated answer blocks that appear at the top of search results. A synthesised response, assembled from multiple sources and citing them, instead of (or above) the familiar list of links.

They matter because they sit on the highest-traffic surface in search: for many queries, the Overview is the first thing a user reads, and often all they read. That compresses the classic "ten blue links" into one answer naming a few sources and brands, and shifts the goal from ranking a link to being **cited inside the Overview**.

Crucially, Overviews lean heavily on Google's existing search index and ranking signals, so strong classic SEO authority carries over here more than it does on some other AI surfaces. That makes them a bridge: the structured, authoritative content that earns featured snippets and good rankings also tends to earn Overview citations. Related: Google's conversational **AI Mode** takes this further into a full chat experience.

## AI-Readiness Audit
Source: https://heybuffy.com/glossary/ai-readiness-audit

An AI-readiness audit checks whether AI engines can **reach, read, understand, corroborate, and quote** your site. The chain that has to hold before a page can be cited in an AI answer. Unlike a classic SEO audit, which grades a page's ability to rank a blue link, a readiness audit grades a page's ability to be lifted into a synthesized answer.

A typical audit scores several pillars: crawler access (do [AI crawlers](/glossary/ai-crawler) get HTTP 200, not a 403, past your [robots.txt](/glossary/robots-txt) and CDN?), extractability (semantic structure, valid [structured data](/glossary/structured-data), content visible without JavaScript), product data (Product/Offer schema for shopping agents), off-site [corroboration](/glossary/corroboration) (Wikipedia, Reddit, reviews), and quotability (is the answer stated first, in fact-dense, self-contained prose?).

One caveat: an audit measures *readiness*. The supply side. It tells you the doors are open, not that engines are walking through. Whether you're actually named and cited is a separate, more volatile signal you track over time.

## AI Visibility Score
Source: https://heybuffy.com/glossary/ai-visibility-score

AI visibility isn't a single thing. It's presence, position, and sourcing at once. The AI Visibility Score rolls those into one 0-100 headline so you can track the overall trend at a glance, then drill into the parts.

It blends the core signals: [Share of Voice](/glossary/share-of-voice) (do you appear?), [Top-Ranked %](/glossary/top-ranked-percent) and [Average Rank](/glossary/average-rank) (how prominently?), and [Citation Coverage](/glossary/citation-coverage) (is your own site the source?). Higher is better; treat 70+ as strong.

The point of a composite is *direction*, not diagnosis. The score tells you whether you're gaining or losing ground overall; the underlying metrics tell you *why*, for example, a dip driven by slipping rank even as presence holds steady. Read together, across engines and over time, they turn "how are we doing in AI?" into something you can actually act on.

## Answer Engine Optimization (AEO)
Source: https://heybuffy.com/glossary/answer-engine-optimization

Answer Engine Optimization is about being **the answer**. When someone asks an AI a direct question. "What's the best fragrance-free moisturizer for eczema?". AEO is the work that makes an engine pull your product, page, or brand into its reply.

An "answer engine" responds with a synthesized answer instead of a list of links, so the optimization target changes: structure content so a model can lift a clean, self-contained answer from it. In practice that means answer-first paragraphs, clear question-style headings, schema markup, and verifiable, specific claims.

AEO overlaps heavily with [Generative Engine Optimization](/glossary/generative-engine-optimization): AEO leans toward *being the direct answer to a question*, while GEO is the broader practice of being mentioned and recommended across engines. Day to day the distinction is academic. The same content and structure improvements serve both.

## Answer Poisoning
Source: https://heybuffy.com/glossary/answer-poisoning

Answer poisoning is the deliberate planting of false or manipulated content into the web sources an AI engine retrieves, so that the model repeats the falsehood in its synthesised answer. It targets the *retrieval corpus* — the pages an engine gathers to build an answer — rather than the model itself, and it works because answer engines lean on agreement across sources far more than they verify any single claim. Seed enough independent-looking sources saying the same false thing and a model can adopt it, sometimes even against an official denial on the affected brand's own site.

It is distinct from neighbouring terms. [Prompt injection](/glossary/prompt-injection) smuggles hidden instructions into a model's input; [astroturfing](/glossary/astroturfing) fakes grassroots praise for yourself; a [citation hallucination](/glossary/citation-hallucination) is an honest model error with no attacker. Answer poisoning is adversarial and corpus-level: real (false) sources, an honest engine, a corrupted answer.

For brands it matters because a single first-party correction is often outweighed by the poisoned sources — most AI mentions of an established brand come from third parties. The durable defence is the same signal that earns citations: [corroboration](/glossary/corroboration) from independent, credible [earned media](/glossary/earned-media), plus correcting the false content at its source so it drops out as the cited pool churns.

## Answer Volatility
Source: https://heybuffy.com/glossary/answer-volatility

Answer volatility measures how much an AI engine's response shifts between observations. Specifically the set of brands it names and the sources it cites. When you ask the **same question again**, or a **slightly reworded** one.

It exists because AI answers are probabilistic, not fixed. The model samples a different response each time, live retrieval pulls a different mix of pages, and small wording changes route to different sub-queries. A 2026 study (Zaprev, reported via LinkedIn) found an identical question asked 30 times in a day returned the same brand list only 50-61% of the time, and a synonym swap cut overlap below 30%. An academic preprint measured day-to-day cited-source overlap at roughly 0.34-0.42 (Jaccard). Both are directional, single-method readings.

Volatility is why a single citation-rate snapshot is unreliable. A trustworthy [share of voice](/glossary/share-of-voice) or [citation coverage](/glossary/citation-coverage) reading comes from many prompts, sampled repeatedly across every engine, read as a distribution and trend rather than one number.

## AP2 (Agent Payments Protocol)
Source: https://heybuffy.com/glossary/ap2

AP2, the Agent Payments Protocol, is an open standard from Google for letting an AI agent pay on a person's behalf while proving the person authorised it. Before an agent spends, the human signs a tamper-proof digital contract — a *Mandate* — that records exactly what was approved. A merchant or bank can then verify, cryptographically, that the payment reflects genuine human intent rather than an agent acting alone or on a hallucinated order.

AP2 uses three Mandates, each carried as a W3C Verifiable Credential: an **Intent Mandate** (the rules of engagement a user pre-signs for when they are away), a **Cart Mandate** (the exact items and price the user approves), and a **Payment Mandate** (a signal to the network that an agent initiated the transaction). Together they build a non-repudiable audit trail answering three questions — authorisation, authenticity, and accountability — that arise the moment a machine, not a person, initiates a payment.

Google announced AP2 in September 2025 with more than 60 payment and commerce partners. It builds on the Agent2Agent (A2A) and Model Context Protocol (MCP) standards, and is rail-agnostic: it supports cards and bank transfers directly, and stablecoins and crypto through the A2A x402 extension. AP2 sits at the payment-authorisation layer — above the [card and stablecoin rails](/blog/cards-vs-stablecoins-agent-payments) that settle the money, and alongside checkout standards like the [Agentic Commerce Protocol](/glossary/agentic-commerce-protocol). Partners and adoption are dated to mid-2026 and will move.

## Astroturfing
Source: https://heybuffy.com/glossary/astroturfing

Astroturfing is the practice of manufacturing fake grassroots support. Using coordinated fake accounts, sockpuppets, planted posts, or paid engagement to make brand promotion look like genuine, spontaneous community consensus. The name is a pun on "grassroots": it's synthetic turf made to resemble the real thing.

It matters for AI visibility because engines lean heavily on community-edited, experience-rich sources like Reddit and Quora, treating them as authentic human signal. That makes fabricating consensus tempting. Seeding threads with brand mentions or [buying aged accounts](/blog/why-buying-aged-reddit-accounts-backfires) to plant citations. It rarely works. Platforms deploy sophisticated anti-spam detection, and AI engines are learning to discount gamed and injected content, so the manufactured signal dilutes the very [corroboration](/glossary/corroboration) it tries to fake.

Astroturfing overlaps with [site reputation abuse](/glossary/site-reputation-abuse) and, when it targets AI answers directly, with [prompt injection](/glossary/prompt-injection). The durable alternative is earned mentions from real users. The one signal manipulation cannot replicate.

## Attribute Query
Source: https://heybuffy.com/glossary/attribute-query

An attribute query is a search that names the specific, granular properties an answer must satisfy, instead of a broad topic keyword. "Waterproof jacket under a set price", "family-friendly hotel with a pool", and "vegan restaurant with outdoor seating" are attribute queries; "jackets", "hotels", and "restaurants" are keyword queries.

Attribute queries became common as AI answer engines changed how people search. Google reports that the average Google AI Mode query is about triple the length of a classic search and that follow-up queries grew more than 40% per month (mid-2026, platform-reported), so people state full requirements in natural language and refine them turn by turn. The [query fan-out](/glossary/query-fan-out) then splits one request into attribute-level sub-questions, and the engine assembles its answer from pages that satisfy each attribute.

The practical consequence: a page is only citable for an attribute query if it names the same attribute in extractable form. Facts stated in text, tables, and [structured data](/glossary/structured-data) can be matched and lifted; attributes buried in images or implied by vague copy ("great for families") cannot. This is why exposing concrete attributes, rather than adjectives, is central to getting cited in [conversational search](/glossary/conversational-search).

## Average Rank
Source: https://heybuffy.com/glossary/average-rank

When an AI answer recommends several brands, where do you land? Average Rank is your mean position across the prompts where you're mentioned, and **lower is better**. An average near 1 means you're consistently the top pick; an average around 6 means you usually sit mid-list.

It completes the picture that [Top-Ranked %](/glossary/top-ranked-percent) starts. Top-Ranked % is the binary "how often am I #1"; average rank captures the *whole* distribution. A brand that's rarely first but reliably 2nd-3rd has a strong average rank and a modest Top-Ranked %, a very different position from one that's occasionally #1 and otherwise nowhere near the top.

Because it only counts prompts where you appear at all, read it next to [Share of Voice](/glossary/share-of-voice): a great rank across few mentions is a narrower win than a solid rank across many.

## "Best of" List (Listicle)
Source: https://heybuffy.com/glossary/best-of-list

A "best of" list. A listicle. Is a ranked roundup like "the 10 best moisturizers for dry skin." For AI shopping answers, it's a disproportionately important page type: independent research (Ahrefs, 2026) found "best X" lists made up roughly **44% of the page types ChatGPT cited** in its analysis.

Engines favor them because they read as neutral, comparative, and comprehensive. A pre-digested shortlist the model can lift directly. The catch for brands: these citations overwhelmingly go to **third-party** lists (publishers, reviewers), not to a brand's own "why we're the best" page.

That shapes strategy. Writing your own self-serving roundup rarely earns citations and can read as promotional. The durable play is **earned placement**: getting included in the independent lists engines already trust, and keeping that coverage fresh (the same research found recently-updated lists were cited far more). Owned content should instead target educational and brand/feature questions, where your own pages legitimately win the [citation](/glossary/citation).

## Brand-Citation Rate
Source: https://heybuffy.com/glossary/brand-citation-rate

Brand-citation rate is the share of an AI engine's answers, across a defined set of questions, that name a specific brand. It answers "how often does this engine mention us at all?" and is the demand-side counterpart to a [citation](/glossary/citation) count, which measures how often your *pages* are used as sources. A brand can have a high citation rate on one engine and a near-zero rate on another for the same questions, so the metric is only meaningful once you fix the engine and the question set.

The rate varies enormously by engine because engines retrieve differently. In a 2026 analysis of 34,234 AI responses by AI-visibility platform Leapd.ai, ChatGPT named a brand in about 0.59% of answers, Perplexity in about 13.05%, and Grok in about 27% — roughly a 46-times spread (single-vendor, directional; attribute "Leapd.ai, 2026" and hedge). Engines that search the live web on more queries, and that foreground their sources, tend to name more brands.

Brand-citation rate is distinct from three neighbours. It is not [total mentions](/glossary/total-mentions) (a raw count rather than a share), not [share of voice](/glossary/share-of-voice) (your rate relative to competitors'), and not a [first-party citation](/glossary/first-party-citation) (which is about *whose page* is cited, not whether the brand is named). It also differs from being recommended: an answer can name a brand without endorsing it. Because a single blended figure hides the wide per-engine spread, treat brand-citation rate as a per-engine, over-time line rather than one number.

## Brand Perception
Source: https://heybuffy.com/glossary/brand-perception

Visibility tells you *whether* AI mentions you; Brand Perception tells you *how*. It's a qualitative read of the way AI platforms describe and position your brand when asked about it directly. The strengths they reach for, the considerations they raise, and the weaknesses they flag.

The tone follows the balance of those: a brand AI consistently frames as "premium and reliable" reads very differently from one painted as "affordable but basic" or "a dated incumbent", and that framing shapes a buyer's impression before a human ever weighs in.

Because it's drawn from branded queries across multiple engines, it surfaces disagreements too: ChatGPT might emphasise your value while Claude leads with a caveat. Tracking perception over time shows whether your narrative is improving, and where a specific engine has picked up a description you'd want to correct.

## Citation Coverage
Source: https://heybuffy.com/glossary/citation-coverage

There's a difference between an AI **mentioning** your brand and **citing your own pages** as the evidence. Citation Coverage measures the second: of the answers that mention you, how often the engine also links your own domain as a source.

It's a trust-and-grounding signal. High coverage means the AI is pulling from *your* content. Your product pages, your docs. Rather than naming you from training memory or from a third-party page. That gives you more influence over how you're described, because the source is yours.

One important caveat: read it **alongside mention volume**. A 100% figure on a brand that's mentioned only a handful of times is far less meaningful than 60% across hundreds of mentions. Small denominators flatter and mislead. Treat it as "share of own-domain citations," not a standalone grade.

Improving it is mostly about being reachable and well-structured enough to get [cited](/blog/how-to-get-cited-by-ai) in the first place.

## Citation fingerprint
Source: https://heybuffy.com/glossary/citation-fingerprint

A **citation fingerprint** is the distinctive blend of page types AI engines rely on when they cite sources for questions in one industry. It is a per-vertical pattern rather than a per-engine one: it describes *what kind of page* wins the [citation](/glossary/citation) — a listicle, an article, a homepage, a product page, a program page — not which engine does the citing.

The term comes from a July 2026 study by Brandon Kidd of DeltaV Digital, which analysed 25,337 citations across five AI engines and found the dominant cited page type varied sharply by category: listicles took about 61% of citations in B2B technology services, homepages about 55% for a local medical-aesthetics brand, and program pages about 53% in higher education (single-vendor data, eight brands, one per vertical — directional, not an audited benchmark). A related cut, own-domain citation share, ranged from about 74.7% in higher education to 0.0% in B2B technology services, showing that some verticals reward owned pages while others force earned placement.

For AI visibility, the citation fingerprint matters because it means the "right" content format is a property of your industry, not a universal rule. Mapping which page types get cited for your category's questions — and whether your own domain is ever among them — tells you what to publish and whether to pursue owned or earned coverage, which you then track as [citation coverage](/glossary/citation-coverage) and [share of voice](/glossary/share-of-voice) over time.

## Citation Gap (Source Gap)
Source: https://heybuffy.com/glossary/citation-gap

A citation gap is the space between the sources AI engines actually cite when answering your category's questions and the sources that include *you*. Run the audit and it shows where the answer is being built from pages you're not on. The specific places winning the citations you're missing.

It comes in two related lenses. A **source gap** asks: which domains and pages do the engines repeatedly cite for my topic, and am I present on (or referenced by) them? A **mention gap** asks: in answers where competitors appear, why am I absent? Both turn a vague "we're not very visible" into a concrete target list.

It's one of the most actionable things to measure because it points straight at work: the third-party lists to earn placement in, the questions your own pages don't yet answer, the corroborating coverage you lack. Tracking it alongside [citation coverage](/glossary/citation-coverage) and [share of voice](/glossary/share-of-voice) turns AI-visibility monitoring into a prioritized to-do list rather than a scoreboard.

## Citation Hallucination
Source: https://heybuffy.com/glossary/citation-hallucination

Citation hallucination is a specific, checkable form of [AI hallucination](/glossary/ai-hallucination): a reference that has the familiar shape of a scholarly or factual source but fails when you try to resolve it. It comes in two forms. *Fabrication*, where no work matching the cited title and authors exists at all, and *author-identity corruption*, where a real work is credited to a substantially wrong author list. Ordinary drift, like a changed year or venue, is not counted.

It matters because references are the currency of trust. LLM tools make it trivial to generate polished bibliographies and confident-looking sources that were never verified, and a 2026 Microsoft audit found such references surviving peer review into published papers. The defense is the same mechanism AI search uses to decide what to [cite](/glossary/citation): resolve each claim against multiple independent authorities and distrust what can't be [corroborated](/glossary/corroboration). For anyone publishing AI-assisted content, the lesson is direct. Verify before you publish, because unverifiable claims are exactly what retrieval systems are built to discount.

## Citation hero page
Source: https://heybuffy.com/glossary/citation-hero-page

A **citation hero page** is one of the handful of pages on your own site that earns most of your AI [citations](/glossary/citation), while the majority of your pages earn none. It names the lopsided, within-site shape of citation distribution: engines cite a tight shortlist per answer, and your buyers ask a bounded, recurring set of questions, so citations compound onto whichever of your pages already win those recurring questions rather than spreading evenly across your site.

A citation hero page is defined by what actually gets cited, not by traffic, seniority, or being your homepage. The pages that win tend to answer one recurring question answer-first, carry high evidence density, stay fresh, and match the page format your category rewards. Which of your URLs qualify is frequently surprising, which is why hero pages are identified from [measured cited pages](/glossary/cited-pages) rather than assumed.

This is a different axis from cross-web *domain* concentration — the finding that a few domains dominate all AI citations across the web. Hero-page concentration is inside your own site: of the pages you control, only a few get cited. Both are real; one is about which domains win the internet, the other about which of your pages win. Finding your hero pages and concentrating maintenance on them — while sending questions you can't win to earned coverage — is a core AI-visibility move, tracked over time as [citation coverage](/glossary/citation-coverage) and [share of voice](/glossary/share-of-voice) per engine.

## Citation Turnover
Source: https://heybuffy.com/glossary/citation-turnover

Citation turnover measures how fast the pool of pages an AI engine [cites](/glossary/citation) changes across repeated observations. High turnover means the sources behind an engine's answers are largely replaced within weeks; low turnover means the same URLs keep getting cited.

It is a longitudinal, population-level metric, and that distinguishes it from its neighbours. [Answer volatility](/glossary/answer-volatility) is about *one moment* — the same prompt returning a different answer each time it is asked. Turnover is about *time* — aggregate across many prompts and weeks, what fraction of the cited set survives. A 2026 study (Digital Authority Partners) tracked 1,127 cited URLs in three waves over six weeks and found only about 10.6% appeared in all three, with roughly 40-60% of cited sources rotating monthly; it is single-vendor and directional, but the churn is large by any read.

Turnover is driven by three compounding forces: probabilistic sampling (answers vary from one sampling to the next), freshness weighting (retrieval favours recently-updated pages, displacing older ones), and a continuously changing index. For AI visibility, the implication is that a citation is a position you defend, not a win you bank: track [citation coverage](/glossary/citation-coverage) and [share of voice](/glossary/share-of-voice) as smoothed trends across many prompts and engines, and keep re-earning the citations that matter rather than assuming a single snapshot holds.

## Citation (AI / LLM)
Source: https://heybuffy.com/glossary/citation

A citation is when an AI answer references, and usually links. A source it drew from. It's the AI-search equivalent of a ranking *and* a backlink at once: the engine is both using your content and vouching for it to the reader.

Being **cited** is stronger than being **mentioned**. A mention names your brand; a citation points the user to your page as the evidence, which builds trust and drives the [AI-referred traffic](/glossary/grounding) that clicks through from answers.

Citation rates vary a lot by engine. Some (like Perplexity) are citation-heavy and link-forward, others surface fewer sources per answer, so the same content can be cited on one engine and merely referenced on another. How often your *own domain* gets cited (versus a retailer or competitor) is captured by [Citation Coverage](/glossary/citation-coverage); how to earn more is covered in [how to get cited by AI](/blog/how-to-get-cited-by-ai).

## Cited Pages
Source: https://heybuffy.com/glossary/cited-pages

When an AI grounds an answer about your brand, it links to sources. Cited Pages is the set of unique URLs it pulls from. Your own product pages and docs, plus the third-party pages (retailers, reviews, roundups, forums) the engines lean on.

It answers two useful questions at once: *which of your own pages are doing the work* (so you can double down on them), and *which third-party pages the engines trust in your category* (so you know where earned coverage actually moves the needle). Often the most-cited pages aren't yours at all, which is exactly the signal that you need to get included in those independent sources.

One counting note: a URL cited by several engines is still one unique page, so per-engine counts can sum higher than the overall unique total. Read alongside [Citation Coverage](/glossary/citation-coverage), which turns this into a percentage.

## Commodity Content
Source: https://heybuffy.com/glossary/commodity-content

Commodity content is content that repeats what many other pages already say without adding first-hand experience or knowledge no one else has. It may be technically accurate and well-written, but it is easily replaceable: a reader who saw the existing results gains nothing new from it.

The term became load-bearing in mid-2026 as generative AI lowered the cost of producing pages. When anyone can generate a competent article on any topic, generic coverage stops being scarce, and both search and AI engines raise the bar for what earns a place. Google guidance reported from an April 2026 Search Central event described leaving such pages in the "Crawled – currently not indexed" bucket: fetched, judged not useful enough, and not added to the index. Because AI Overviews and AI Mode draw only from that index, commodity content is invisible to them by extension, and other AI engines tend to skip it as a [citation](/glossary/citation) for the same reason.

The fix is not stylistic. It is to add what a commodity lacks: original data, testing, first-hand experience, and specifics that raise [E-E-A-T](/glossary/e-e-a-t) and [entity authority](/glossary/entity-authority). Content that only rehashes is also prone to faster [decay](/glossary/content-decay), since anything newer and more original displaces it.

## Content Chunk
Source: https://heybuffy.com/glossary/content-chunk

A content chunk is a self-contained passage, typically a single section of roughly 100 to 300 words, that answers one question without depending on the rest of the page. It is the unit AI engines work in: retrieval and [citation](/glossary/citation) happen at the passage level, not the page level, so an engine lifts the chunk that best answers a sub-query wherever it sits, and may cite several chunks from different pages in one answer.

Chunking comes from how [retrieval-augmented](/glossary/retrieval-augmented-generation) systems index the web. A page is split into passages, each embedded and stored, and when a query [fans out](/glossary/query-fan-out) into sub-questions, the engine matches each sub-question to the closest chunk. A passage buried in a wall of prose, or split awkwardly across sections, is harder to retrieve cleanly, which is why answer-first, self-contained sections outperform undifferentiated text.

Read the chunk, not the page, as your unit of optimisation. A short page that fully answers one question can be a perfect chunk; a long page that answers eight questions is really eight chunks competing on their own merits. The practical work is to give every real sub-question its own liftable section, and the practical way to know it worked is your measured [retrievability](/glossary/retrievability) and citation coverage per engine, since no engine reports chunk-level selection directly.

## Content Decay (Citation Cliff)
Source: https://heybuffy.com/glossary/content-decay

Content decay is the gradual loss of AI citations as a page gets older. Because live retrieval favors recently-published or recently-updated sources, a page that earned [citations](/glossary/citation) when fresh tends to be cited less over time. Often falling off noticeably after roughly three months (the "citation cliff").

This makes freshness a real ranking lever, not a vanity metric. Practitioner data has repeatedly found that AI citations skew heavily toward content updated in the last several months, and that a visible "last updated" date correlates with more citations.

The fix is a **refresh cadence** on your competitive pages, but the update has to be *substantive* (corrected facts, new data, added sections), not a bumped date with no real change. Definitional and evergreen content (like glossary terms) decays slowly and shouldn't be churned; reserve the effort for time-sensitive, competitive pages where staying current keeps you in the answer.

## Content Graveyard
Source: https://heybuffy.com/glossary/content-graveyard

The content graveyard is the majority of the web that an AI engine [cites](/glossary/citation) exactly once and then drops — sources that surface in an answer for a moment and never return. It is the flip side of the small minority that earns a *durable* citation position, and naming it reframes the goal of AI visibility from getting cited to *staying* cited.

The term comes from Somantra AI's 2026 "Content Graveyard" analysis, which tracked 2,437,107 citations across 28,725 domains on ChatGPT and Google over seven months and found 57.2% of domains were cited in a single month only, against 2.7% cited in all seven. The study is single-vendor and single-sector (Australian insurance), so read the exact figures as directional — but the split is large by any measure.

What separated the graveyard from the survivors was format, not brand size: comparison, FAQ, how-to and pricing pages persisted at roughly twice the rate, while "complete guide" pages were about 3.5x more common among the vanished. The content graveyard is closely related to [citation turnover](/glossary/citation-turnover) — turnover measures *how fast* the cited pool is replaced; the graveyard is *what ends up in* the discarded pile. The practical implication is the same: treat a first citation as a position to defend with specific, structured, self-contained content, not a win to bank.

## Conversational Query
Source: https://heybuffy.com/glossary/conversational-query

A **conversational query** is one turn in a multi-turn AI search conversation that the engine treats as its own independent query, rather than as part of the opening question. It's the individual *unit* of a [conversational search](/glossary/conversational-search) session — where that term names the dialogue-style mode, a conversational query is a single measurable turn inside it.

The concept became concrete in mid-2026 when Google confirmed how [AI Mode](/glossary/google-ai-mode) records conversations. Per Google's documentation, when a user asks a follow-up question within AI Mode, they are essentially performing a new query, and its impression, position, and click data are attributed to that new query. So a five-turn conversation produces five conversational queries, each logged separately.

Because follow-ups are replies, not fresh searches, conversational queries surface as short, dependent fragments — "yes, pricing", "go on", "the cheaper one" — that only make sense in context. In Google Search Console they land in the main performance report mixed with classic queries and carry no AI Mode label, so they can be spotted by shape but not cleanly segmented. For measurement, the implication is that AI visibility is now earned turn by turn: a brand can be cited at the opening query and dropped three turns later, which single-query tracking would miss entirely.

## Conversational Search
Source: https://heybuffy.com/glossary/conversational-search

Conversational search is the shift from typing terse keywords ("running shoes flat feet") to asking a full, natural-language question ("which running shoes are good for a heavy runner with flat feet who mostly uses a treadmill?"), and often following up in a back-and-forth.

It's how people now use ChatGPT, Google's AI Mode, Gemini, and Perplexity. Queries are longer, more specific, and carry context a keyword search never did. Behind the scenes, the engine usually breaks one conversational question into several sub-queries. See [query fan-out](/glossary/query-fan-out), and assembles an answer from many sources.

For brands, this changes the target. Thin pages tuned to one keyword win a shrinking slice of these questions; content that answers the *whole* intent. Uses, comparisons, who-it's-for, edge cases. Gets pulled into more of the answer. And because the answer often resolves in-chat, much of this traffic is [zero-click](/glossary/zero-click-search).

## Correlation vs causation
Source: https://heybuffy.com/glossary/correlation-vs-causation

Correlation vs causation is the difference between two things moving together and one of them causing the other. In AI visibility it is the most common reasoning error: a factor is found more often on cited pages, so it is assumed to *cause* the [citation](/glossary/citation), when it may simply travel alongside the real cause.

The worked example is [structured data](/glossary/structured-data). Pages cited by AI are far likelier to carry JSON-LD schema, a strong correlation, yet a controlled 2026 experiment that added schema to matched pages found no citation uplift. The resolution is that well-built sites tend both to add schema and to earn citations, so schema correlates with citation without causing it. The same trap lurks behind claims that a word count, a freshness date, or any single on-page trait "gets you cited."

Telling them apart takes a controlled comparison: change one variable, hold a similar control group unchanged, and see whether the treated group moves *beyond* the control. A raw "cited pages have X" count never can, because it cannot separate X from everything else those pages share. Reading GEO research through this lens, favouring controlled evidence over correlational counts, and hedging single-vendor findings, is what keeps a content strategy anchored to signals that actually move citations rather than ones that merely accompany them.

## Corroboration
Source: https://heybuffy.com/glossary/corroboration

Corroboration is when several independent, credible sources say the same thing. AI engines lean on it heavily: a fact repeated across reputable places is safer to assert than one found in a single spot, so corroborated claims are more likely to be stated confidently and [cited](/glossary/citation).

This is why you can't simply *declare* your way to AI visibility. A brand that calls itself "the leading X" on its own site, with nothing echoing it elsewhere, gives the engine one uncorroborated claim. The same positioning reflected in reviews, press, retailer listings, and community discussion becomes consensus the model will repeat.

For brands, corroboration is the strategic case for **earned coverage** alongside owned content, and for consistency: your facts, names, and claims should match across your site, marketplaces, and profiles, because contradictions read as untrustworthy. It's a core component of [entity authority](/glossary/entity-authority) and overlaps with the trust signals in [E-E-A-T](/glossary/e-e-a-t).

## Crawl-to-refer ratio
Source: https://heybuffy.com/glossary/crawl-to-refer-ratio

The crawl-to-refer ratio is the number of pages an AI operator's crawler fetches from a site (or the web) for every visitor its assistant refers back. You compute it by dividing total crawl requests by total referral sessions over the same window. A ratio of 217:1 means the bot crawled about 217 pages for each click it sent.

The ratio exists because AI operators crawl for jobs that mostly precede any visit: building the training data a model learns from, and maintaining the [retrieval](/glossary/retrieval-augmented-generation) index that grounds live answers. Neither guarantees a referral. So a high ratio is expected, not a malfunction.

The number splits cleanly by operator type. As of a 28-day window ending 21 July 2026 (Cloudflare Radar data, single-source and directional), pure-AI crawlers such as Anthropic's ClaudeBot sat around 2,237:1 and OpenAI's GPTBot around 217:1, while search-backed Google sat near 4.6:1, close to parity because it has always paired crawling with a click-sending search engine. The pure-AI ratios have fallen sharply since early 2026 as assistants began sending more traffic.

Read the ratio as evidence a crawler can reach and learn from you, not as a measure of success. Because much AI-referred traffic hides as [direct traffic](/glossary/dark-traffic), the referral side is usually undercounted, making real ratios lower than raw logs suggest. And because reading rarely turns into a click (the [Dark Library Effect](/glossary/dark-library-effect)), the right scorecard is citations, not referrals.

## Dark Library Effect
Source: https://heybuffy.com/glossary/dark-library-effect

The Dark Library Effect is the divergence between how much an AI engine *reads* a page and how little traffic it *sends* to that page. AI crawlers absorb the content, summarise it in an answer, and satisfy the user in place, so the page is heavily read yet rarely clicked. The term was coined by Orbit Media (Andy Crestodina, mid-2026) for the page type where the gap is widest: articles and blog posts.

In their analysis of 560,000+ AI crawl requests across 74 sites (Cloudflare AI Crawl Control data, single-vendor and directional), article pages received about 8.7 percentage points less referral share than their crawl share predicted, homepages about 10.4 points more, and 47% of all pages earned zero referral visits despite being crawled.

The effect does not mean article content is worthless. It gets [cited](/glossary/citation) and trains what the model knows about a brand. Value a click counter never captures. It is distinct from [dark traffic](/glossary/dark-traffic) (real visits misfiled as "direct"): the Dark Library Effect is about visits that never happen at all, a form of [zero-click](/glossary/zero-click-search) discovery. The lesson is to judge articles by citations, not clicks.

## Dark Traffic
Source: https://heybuffy.com/glossary/dark-traffic

Dark traffic is real, often high-intent traffic whose origin your analytics can't see. The visit arrives with no referrer attached, so a tool like GA4 has nowhere to file it but **"Direct"**: the same bucket as someone typing your URL.

It's a growing problem for AI visibility because many AI-driven visits lose their referrer in transit: links opened from inside the ChatGPT or Perplexity apps, redirect hops, and stripped referrer headers all land as "Direct." The result is that the *visible* AI referrals in your reports are only a fraction of the real total. The rest is hiding in plain sight.

You can't fully reclaim a missing referrer, but you can **estimate** the dark portion using behavioral signals. Deep landing pages, new-user share, and timing that tracks your known AI referrals. Counting it matters: AI traffic that converts well looks like worthless "Direct" until you unmask it, which is why much AI impact is also [zero-click](/glossary/zero-click-search).

## Decision-Grade Measurement
Source: https://heybuffy.com/glossary/decision-grade-measurement

**Decision-grade measurement** is AI-visibility data rigorous enough to support high-stakes actions — reallocating budget, reviewing an agency, setting executive strategy — rather than merely signalling a trend. The distinction comes from the IAB's 2026 framework *Measuring Visibility in the AI Era*, which splits AI-visibility data into two tiers: **directional** and **decision-grade**.

Directional data is fine for early signals, internal briefings, and competitive awareness. Decision-grade data meets a higher bar across sample size, query volume, prompt-type coverage, testing cadence, reproducibility, data validation, and platform coverage. In the framework's criteria matrix, decision-grade means (among other things) covering all four query intent types, sampling each query enough times to characterise a distribution rather than reading a single response, defining acceptable variation within a 7-day window, and reporting per-platform results instead of one blended score.

Both tiers are legitimate. The failure the framework warns against is treating directional data as decision-grade without noticing the gap — spending decision-grade money on a confident guess. Because AI answers are [non-deterministic](/glossary/answer-volatility), even decision-grade data is reported as a range with a stated variability, not a false-precise single number. The practical test: can the provider disclose the method behind the number? If not, it isn't decision-grade.

## Domain Authority
Source: https://heybuffy.com/glossary/domain-authority

Domain Authority is a third-party score — most familiar as Moz's 0–100 metric, with Ahrefs' Domain Rating (DR) a close cousin — that estimates how likely a domain is to rank in classic Google search. It is built mostly from the quantity and quality of a site's backlinks, and it is a proxy, not a Google metric.

For AI visibility it is a weak signal. Because AI engines retrieve and cite at the passage level, weighing relevance, extractable structure, freshness, and [corroboration](/glossary/corroboration) over backlink count, a high Domain Authority does not reliably earn citations and a low one does not prevent them. In Featured's 2026 analysis of 22,881 AI citations, 34.5% came from sites with a Domain Authority under 40 (single-vendor, directional; attribute "Featured, 2026").

Do not confuse it with [entity authority](/glossary/entity-authority), which is how strongly AI associates your brand with a topic. Entity authority — driven by brand mentions, knowledge-graph presence, and topic co-occurrence — is repeatedly found to predict AI citations more than backlinks do, and Ahrefs' 2026 data put branded mentions about three times ahead of raw backlink count for AI Overview presence. The two often rise together, which is why they get muddled, but it is the mentions and topic association doing the work for AI, not the link-based score. Track your per-engine [citation](/glossary/citation) share, not your DA number, to know your AI visibility.

## E-E-A-T
Source: https://heybuffy.com/glossary/e-e-a-t

E-E-A-T stands for **Experience, Expertise, Authoritativeness, and Trustworthiness**: the framework Google's guidelines use to judge content quality. It isn't a single score; it's a cluster of signals about whether the people and brand behind a page can be trusted on the topic.

It matters beyond classic SEO because AI engines lean on the same kinds of signals when deciding which sources to ground an answer in and [cite](/glossary/citation). Content with visible authorship, real first-hand experience, corroboration from reputable places, and clear trust markers (accurate information, transparency, a credible site) is safer for a model to quote.

For brands, E-E-A-T overlaps heavily with [entity authority](/glossary/entity-authority): being a well-established, consistently described, widely-corroborated entity is exactly what makes both Google and AI engines comfortable presenting you as the answer. It's a slow, compounding lever. Built through genuine expertise and third-party validation, not on-page tricks.

## Earned Media
Source: https://heybuffy.com/glossary/earned-media

Earned media is coverage a brand earns from independent sources. Journalists, reviewers, community forums, and third-party best-of lists, as opposed to paid media (advertising you buy) or owned media (pages you publish). It is not purchased and not fully controllable, which is exactly why AI engines and readers trust it more.

Earned media matters for AI visibility because engines lean on third-party [corroboration](/glossary/corroboration) when they decide who to cite. Muck Rack's 2026 State of PR report found that roughly 99% of AI citations come from non-paid, earned sources (a single-survey figure, directional). It aligns with the wider pattern that independent [best-of lists](/glossary/best-of-list) are cited far more often than brand-owned pages for commercial "best X" queries, so earned placement, not self-promotion, is what wins those [citations](/glossary/citation).

The caveat: earned media can be influenced but not dictated, and faking it backfires. Manufactured reviews or planted mentions read as [astroturfing](/glossary/astroturfing) and can trigger [site reputation](/glossary/site-reputation-abuse) penalties. The durable route is genuine credibility. Real coverage, real reviews, strong [E-E-A-T](/glossary/e-e-a-t), that engines can find and quote.

## Embeddings
Source: https://heybuffy.com/glossary/embeddings

An embedding is a way of turning text into a list of numbers (a vector) that captures its *meaning*, so a model can measure how related two pieces of text are by how close their vectors sit. Words and passages about similar concepts land near each other, even when they share no exact words.

This is the machinery behind [semantic search](/glossary/semantic-search) and the retrieval step in [RAG](/glossary/retrieval-augmented-generation): when an engine looks for sources to answer a question, it compares the question's embedding to the embeddings of candidate passages and keeps the closest matches.

The practical takeaway for content: relevance is now *conceptual*, not keyword-frequency. A page about "engine misfires" should also naturally cover spark plugs, rough idling, and check-engine lights, so its embedding spans the full topic and gets matched to more of the questions people actually ask. Covering a topic's real vocabulary also strengthens your [entity association](/glossary/entity-authority) with it.

## Entity Authority
Source: https://heybuffy.com/glossary/entity-authority

Entity authority is how well-established and credible your brand is *as a recognised entity* for a given topic, and analyses repeatedly find it predicts AI citations more strongly than backlink volume or classic technical SEO.

It's built from signals AI can read across the whole web: brand search volume, presence in knowledge graphs (Wikipedia, Wikidata, Google's Knowledge Graph), and how often your brand co-occurs with your category. A brand with high entity authority for "expense cards" gets recommended for expense-card questions almost by default. Its authority is inherited, not earned per page.

The catch: it compounds slowly and can't be faked overnight, which also makes it durable. It's the long-game lever behind why AI "already knows" some brands. Covered in depth in [Entity strength: why AI already knows some brands](/blog/entity-strength-ai).

## Extractability
Source: https://heybuffy.com/glossary/extractability

Extractability is how cleanly an AI engine can lift a single, self-contained answer out of a page. Retrieval and [citation](/glossary/citation) happen at the passage level, so a page an engine has already fetched still only gets quoted if it contains a passage the engine can pull whole — a statistic line, a definition, a table row, a direct answer — rather than a fact tangled in flowing prose. It is the difference between a page being *available* and a page being *quotable*.

Extractability sits between two neighbours. [Retrievability](/glossary/retrievability) is whether an engine can find and fetch the page at all; extractability is whether, once fetched, a clean unit can be lifted from it. The unit itself is the [content chunk](/glossary/content-chunk) — a self-contained section answering one question. The practical markers of an extractable passage are consistent: answer-first, one fact per sentence, roughly 15 to 45 words, led by the direct answer, and set in real headings, lists, and tables rather than a wall of text.

Extractability is a writing choice you control on every page, unlike authority or [corroboration](/glossary/corroboration), which build slowly off-site. In MaxAEO's 2026 analysis, statistic lines and table rows were lifted verbatim far more often than narrative prose — directional, single-vendor evidence for the durable rule that structured, self-contained passages get quoted and buried ones do not. Because no engine reports which passage it lifted, the way to know a page is extractable is to track its citation coverage per engine after you restructure it.

## Featured Snippet
Source: https://heybuffy.com/glossary/featured-snippet

A featured snippet is the boxed, direct answer Google has long shown at the top of results. "Position zero". Lifting a sentence, list, or table straight from a page to answer a query without a click.

It's worth knowing because it's the direct ancestor of [AI Overviews](/glossary/ai-overviews) and AI answers, and the same content mechanics win both. Google earned snippets by extracting a clean, self-contained answer from a well-structured page; AI engines do a richer version of exactly that. The page that gets lifted is the one that states the answer plainly, near the top, in a format (short paragraph, list, table) a machine can pull out whole.

So the snippet-era playbook still pays off: answer the question directly and early, use clear headings that match how people ask, and put facts in lists and tables. The difference is that snippets sent a (shrinking) click, while AI answers are often fully [zero-click](/glossary/zero-click-search). Making it even more important to be the *cited* source.

## First-Party Citation
Source: https://heybuffy.com/glossary/first-party-citation

A first-party citation is a [citation](/glossary/citation) whose source is the brand's own domain — its product page, pricing page, docs, or blog — rather than a third-party page about the brand. It is the counterpart to a third-party or [earned](/glossary/earned-media) citation, where the engine cites a review site, an independent [best-of list](/glossary/best-of-list), a comparison page, or a community thread. The distinction is about *whose page got cited*, not whether the brand was named.

The split matters because the two are won differently. First-party citations are earned by making your own pages the clean, extractable, authoritative source for facts about you — specs, pricing, official details — served as crawlable text. Third-party citations are earned indirectly, through [corroboration](/glossary/corroboration) and placement in the independent sources engines trust. For brand- and feature-specific questions ("how does X work", "X pricing"), engines tend to want the first-party source; for commercial-intent "best X for Y" questions, they lean on third-party roundups.

Which way an engine leans is shifting and version-specific. As of mid-to-late 2026, ChatGPT was reported to be resolving more of its citations to first-party sources — using the [`site:` operator](/glossary/site-operator) to target named domains — while third-party roundups still carried discovery and other engines. Treat the balance as something to measure per engine over time, not a fixed rule.

## Generative Engine Optimization (GEO)
Source: https://heybuffy.com/glossary/generative-engine-optimization

Generative Engine Optimization is the discipline of staying visible when customers ask an AI instead of searching. Where SEO optimized for ranking a link in a list, GEO optimizes for being **named, cited, and recommended** inside a synthesized AI answer. Across ChatGPT, Gemini, Claude, and Google's AI surfaces.

It builds on SEO rather than replacing it: clean, crawlable, well-structured, authoritative content still wins. But the goal shifts from earning a click to being the source the model quotes and the brand it suggests.

In practice GEO spans being reachable by [AI crawlers](/blog/ai-crawler-lifecycle), being parseable (clean semantic structure and schema), being specific and corroborated enough that engines trust your claims, and being measured across engines over time. It's often used interchangeably with [Answer Engine Optimization](/glossary/answer-engine-optimization). Most teams pursue both with the same work.

## Ghost Citation
Source: https://heybuffy.com/glossary/ghost-citation

A ghost citation is when an AI engine draws a fact from your page and links it as a source, but never names your brand in the answer. The reader gets the claim and maybe a link icon, not who said it. The term was coined by Kevin Indig in a study Semrush published in June 2026, which found roughly 61.7% of brand appearances across four engines were ghost citations: cited, not named.

It matters because a citation is widely assumed to build brand awareness, and a ghost citation doesn't. In a [zero-click](/glossary/zero-click-search) answer most readers never open the link, so an unnamed source leaves no memory of you. You supplied the answer and stayed anonymous. The same study found the [citation](/glossary/citation) rate (~74.9%) far outran the mention rate (~38.3%), and the two barely travel together: Gemini names brands more than it links them, ChatGPT the reverse.

A ghost citation is distinct from a [citation gap](/glossary/citation-gap), which is being *absent* from the sources entirely. Here you *are* the source. Your name just isn't. The fix is an entity job, not a content one: bind your brand name to your facts on the page and build the [entity authority](/glossary/entity-authority) that makes engines attribute claims to you. Track your mention rate separately from your citation rate, per engine, to see the gap close.

## Google AI Mode
Source: https://heybuffy.com/glossary/google-ai-mode

AI Mode is Google's full conversational search experience: a Gemini-powered chat where you can ask, follow up, and refine, and get synthesised, cited answers rather than a page of links.

It's worth distinguishing from its sibling, the [AI Overview](/glossary/ai-overviews). An Overview is a summary block that appears *above* normal search results; AI Mode is a dedicated, back-and-forth chat surface. Both pull from Google's index and lean on [query fan-out](/glossary/query-fan-out). Decomposing your question into many sub-searches, but AI Mode goes deeper into multi-turn research.

For brands, AI Mode raises the stakes of the same fundamentals: because Google grounds these answers in its existing search index, the structured, authoritative content that wins rankings and Overviews also feeds AI Mode. It's another high-traffic surface where being *cited in the answer*, not just ranked below it. Is the goal.

## The great decoupling
Source: https://heybuffy.com/glossary/great-decoupling

The great decoupling is the widening gap between how often a site's pages are *shown* in search (impressions) and how often they are *clicked* (clicks and click-through rate). Impressions stay flat or climb while clicks fall, so the two lines that used to move together pull apart.

The cause is answers moving onto the results page. When an [AI Overview](/glossary/ai-overviews) or a [featured snippet](/glossary/featured-snippet) resolves the query in place, the searcher is satisfied without a visit, the [zero-click](/glossary/zero-click-search) pattern. Your page still earns the impression for being displayed inside or beside the answer, but the click becomes optional. Ahrefs measured the effect on informational queries at an isolated top-result click-through-rate drop of roughly 34.5% (March 2025 data) rising to up to 58% in its 2026 update, single-vendor and Google-AI-Overviews-specific, so directional.

The decoupling reframes what to measure: falling clicks against steady impressions is not necessarily lost visibility. It often means you are being shown and read inside answers. It is distinct from rank-decoupling (a page no longer needing a top-10 rank to be cited). The durable scorecard becomes whether you are [cited](/glossary/citation) inside the answer, not clicks alone.

## Grounding
Source: https://heybuffy.com/glossary/grounding

Grounding is the practice of tying an AI's output to real, verifiable sources. A grounded answer is built from documents the engine fetched and can point to; an ungrounded one comes from the model's parametric memory, which may be outdated or wrong.

It's the main defence against [hallucination](/glossary/ai-hallucination), and it's foundational to AI search surfaces like Google's AI Overviews and Perplexity. They retrieve, then answer from what they retrieved, then cite. For users it means more trustworthy, current answers with sources to check.

For brands, grounding is the opportunity: if the engines prefer to answer from sources they can verify, then being a clear, authoritative, reachable source about your own brand and category is how you get pulled into, and credited in. Those answers. Make your facts easy to ground, and you're more likely to be the evidence.

## Hero Products
Source: https://heybuffy.com/glossary/hero-products

Brand-level visibility can hide product-level problems. Hero Products are the flagship items you most care about, and each gets its own dedicated deep-dive prompt, scored individually for how favourably AI describes it when asked specifically.

This matters because a brand can have strong overall visibility while its newest or highest-margin product is described thinly, inaccurately, or not at all. A 0-100 read per hero product shows where the engines talk about your stars positively and substantively versus where they're vague or missing the details that drive a purchase.

It's the difference between "AI knows my brand" and "AI can actually sell my best product", and it points precisely at which product pages and facts need to be clearer and more reachable for the engines to pick up.

## Holdout test
Source: https://heybuffy.com/glossary/holdout-test

A holdout test is a way to measure whether something *caused* a result by keeping a comparable group unchanged for comparison. The changed group is the treatment; the untouched group is the holdout, or control. Because both groups drift together over time, any extra movement in the treated group, measured against the holdout, is attributable to the change rather than to background noise.

In AI visibility the holdout is the fix for a stubborn problem: [citations](/glossary/citation) rise and fall on their own, so a bare before-and-after cannot tell you whether your edit or the tide moved them. Hold out a comparable set of pages when you add schema, refresh copy, or build links, then read the treated set's [citation coverage](/glossary/citation-coverage) against the holdout, not against zero. The strongest version randomizes assignment: the 2026 Agarwal and Sen field experiment hid Google's AI Overview at random for some searches and compared clicks against a control, which is what let it claim a causal effect rather than a [correlation](/glossary/correlation-vs-causation).

Holdout tests have limits. The groups must be genuinely comparable, the window must outlast the crawl-to-cite lag, and on third-party surfaces you often cannot randomize at all, only approximate a control with matched pages or queries. Used honestly, though, a holdout is the difference between "cited pages have X" and "adding X made pages cited," and it is the discipline behind reading any AI-visibility claim, or measuring your own [share of voice](/glossary/share-of-voice), without fooling yourself.

## Information Gain
Source: https://heybuffy.com/glossary/information-gain

Information gain is how much *new* information a page adds relative to what is already available for the same query. A page that restates the consensus everyone else already published has low information gain; a page with a proprietary statistic, a first-hand test, or a detail no competitor covers has high information gain.

The term comes from a Google patent, ["Contextual estimation of link information gain"](/blog/information-gain-and-ai-citations) (publication US11354342B2, filed 2018), which describes scoring a document by "the additional information" it contains beyond documents a user has already seen, then reranking follow-up results accordingly. Google has never confirmed it runs this exact mechanism in production, so treat information gain as a well-evidenced *concept*, not a named ranking factor.

It matters for AI visibility because engines retrieve and cite at the passage level. When a model assembles an answer, a page holding a specific, [corroborated](/glossary/corroboration) datapoint that no higher-ranked page provides can be pulled in even when it ranks outside the top results — while [commodity content](/glossary/commodity-content) that duplicates the field gets skipped. Original evidence is the durable lever; restated summaries decay first.

## Knowledge Cutoff
Source: https://heybuffy.com/glossary/knowledge-cutoff

A knowledge cutoff is the date a model's training data ends. Everything the [model](/glossary/large-language-model) learned during training reflects the world up to that point; on its own, it has no awareness of anything that happened after.

This explains a lot of brand-visibility behavior. If you rebranded, launched a product, or changed your positioning *after* a model's cutoff, the model's trained knowledge of you is simply stale. It may describe an old version of your brand with total confidence.

The fix is **live retrieval**: when an engine searches the web at answer time and [grounds](/glossary/grounding) its response in what it finds (see [RAG](/glossary/retrieval-augmented-generation)), it can pick up current facts regardless of cutoff, *if* your current information is crawlable and citable. So two things keep AI descriptions of you accurate: being well-represented in training over time, and ensuring fresh, retrievable pages exist for the engine to find right now.

## Knowledge Graph
Source: https://heybuffy.com/glossary/knowledge-graph

A knowledge graph is a structured map of entities. Brands, products, people, places, and the relationships connecting them ("this brand makes this product," "this product is a type of moisturizer"). Google's Knowledge Graph is the best-known example, and similar entity understanding underpins how AI engines represent the world.

It matters because being a *recognized entity* in these graphs is what lets an engine confidently name and describe you. A brand the graph understands. Clearly defined, consistently referenced, linked to the right products and categories. Gets surfaced with confidence; an ambiguous or absent one gets skipped or confused with something else.

You strengthen your place in the graph the same way you build [entity authority](/glossary/entity-authority): consistent naming everywhere, clear "what we are" descriptions, [structured data](/glossary/structured-data) (Organization, Product) that spells out the facts and relationships, and corroboration across reputable sources. It's a slow, compounding asset, and a major input to whether AI [grounds](/glossary/grounding) an answer in *you*.

## Large Language Model (LLM)
Source: https://heybuffy.com/glossary/large-language-model

A large language model (LLM) is a neural network trained on enormous amounts of text to predict the next word, and, from that simple objective, to generate fluent language, answer questions, and summarize. It's the engine inside ChatGPT, Gemini, Claude, and the AI features now built into search.

For brands, the important part is *how* an LLM "knows" things. Some knowledge comes from **training**: text the model learned, frozen at a [knowledge cutoff](/glossary/knowledge-cutoff). The rest comes from **live retrieval** at answer time, where the model searches the web and grounds its answer in what it finds (see [RAG](/glossary/retrieval-augmented-generation) and [grounding](/glossary/grounding)).

An LLM doesn't store facts like a database; it represents patterns. That's why it can sound confident yet be wrong. An [AI hallucination](/glossary/ai-hallucination). Influencing what an LLM says about your brand means being well-represented in the text it learns from **and** being retrievable and citable when it searches live.

## llms.txt
Source: https://heybuffy.com/glossary/llms-txt

`llms.txt` is a proposed convention: a Markdown file at the root of your site (`yourdomain.com/llms.txt`) that hands AI systems a short, curated map of what matters. Your key pages, products, and a one-line description of each. In a format that's trivial for a model to parse.

Think of it as a counterpart to `robots.txt`, but inverted: `robots.txt` says what crawlers *may* access; `llms.txt` says what they should *pay attention to*. Instead of making an engine infer your site's structure from messy HTML, you tell it plainly.

It's still an emerging standard. Adoption is growing but not universally honoured yet, so treat it as a low-cost, high-signal addition rather than a guarantee. For brands it's a cheap way to point AI at your best, most accurate content. (There's also `llms-full.txt`, a fuller single-file dump of site content for the same purpose.)

## Mixed-use crawler
Source: https://heybuffy.com/glossary/mixed-use-crawler

A mixed-use crawler is an [AI crawler](/glossary/ai-crawler) that blends several jobs — search indexing, AI-agent fetching, and model training — behind a single [user-agent](/glossary/robots-txt). Because one token does more than one thing, a site owner cannot cleanly permit the use they want (say, live retrieval for citations) without also permitting the ones they may not want (training). It is the practical reason "just block the AI bots" is rarely simple.

The term moved from concept to consequence in mid-2026. From 15 September 2026, Cloudflare's new defaults block AI training and agent crawlers on ad-bearing pages while leaving pure search crawlers allowed — and a crawler that mixes those functions gets blocked on ad pages unless its operator lets site owners separate the jobs. Purpose, not just identity, now decides access. Attributed to Cloudflare's July 2026 policy; single-operator and dated, since defaults are still moving.

Mixed use is why [verified identity](/glossary/verified-bot) and clear per-purpose signalling matter: when a bot's job is ambiguous, the safe default drifts toward *deny*. For a brand that wants AI visibility, the takeaway is to decide access per crawler purpose, and to confirm that the crawlers feeding live answers can still reach the pages you want cited, rather than being caught in a mixed-use block meant for training bots.

## Multimodal Search
Source: https://heybuffy.com/glossary/multimodal-search

Multimodal search means asking with more than text. Snapping a photo of a product, or speaking a question aloud, and having the AI interpret it and answer. It's no longer a niche: Google reported that more than one in six AI Mode searches now arrive as voice or image, with image-based queries growing fast.

For brands, this raises the bar on what a machine can understand about you. A voice query is usually longer and more [conversational](/glossary/conversational-search); an image query depends on the engine recognizing your product, which leans on clear product imagery, alt text, and [structured data](/glossary/structured-data).

The practical implication: facts about your products need to exist in formats different query types can reach. Descriptive text *and* labelled images *and* structured attributes. A page that only "looks right" to a human, with its real information locked in pictures a crawler can't read, loses the multimodal branches of the [fan-out](/glossary/query-fan-out).

## Parametric Memory
Source: https://heybuffy.com/glossary/parametric-memory

Parametric memory is the knowledge a [large language model](/glossary/large-language-model) absorbed during training and stored inside its parameters (its weights). When a model answers from parametric memory, it is drawing on what it learned, not on any document it fetched for that specific question. It is the model's built-in, from-memory knowledge.

This is the counterpart to retrieval. In [retrieval-augmented generation](/glossary/retrieval-augmented-generation), an engine fetches live documents and [grounds](/glossary/grounding) its answer in them; without retrieval, the model falls back on parametric memory alone. The two behave very differently for a brand. Parametric memory is frozen at the [knowledge cutoff](/glossary/knowledge-cutoff) and changes only when the model is retrained, so it can describe an outdated version of you with complete confidence. Retrieved knowledge is as current as the page just read.

For AI visibility, the distinction sets your priorities. You influence parametric memory only slowly and indirectly, by being consistently and correctly described across the web so the next training cycle learns the accurate version. You influence retrieval directly and now, by being reachable and citable. An answer with no sources is usually parametric memory talking; an answer that cites pages retrieved them.

## Position-Adjusted Word Count
Source: https://heybuffy.com/glossary/position-adjusted-word-count

Position-Adjusted Word Count is a visibility metric introduced in the 2024 Princeton [GEO study](/blog/what-content-changes-lift-ai-citations) to measure how prominently a source appears inside an AI-generated answer. Rather than counting whether a page was cited, it counts *how much of the page's wording the answer actually used*, then weights that by where and how prominently the citation appears, so being quoted at length and early scores higher than a passing link near the end.

It exists because a raw [citation](/glossary/citation) count is too blunt: two sources can both be "cited" while one supplies a single clause and the other supplies half the answer. Position-Adjusted Word Count separates them, which is why the study used it to rank content edits, adding statistics lifted it by about 41%, keyword stuffing lowered it.

Read it as a research measure, not a live dashboard number. It was computed on a simulated engine over a fixed benchmark, so it is directional evidence about *what makes a source prominent*, not a KPI any engine reports today. The practical equivalent you can track is your own [citation coverage](/glossary/citation-coverage) and [share of voice](/glossary/share-of-voice) per engine over time.

## Product Feed
Source: https://heybuffy.com/glossary/product-feed

A product feed is a structured file, or API, that lists your products one row at a time, each with a defined set of attributes: title, description, price, availability, image, brand, GTIN, and category. Platforms like Google Merchant Center ingest it, and it is increasingly the same clean source that AI shopping surfaces read from.

For AI visibility the feed matters because it hands machines your product facts already labelled, no parsing or guessing. When Google's Merchant Center AI performance report scores "product attribute completeness," it is judging your feed: a shopper asks an AI for a waterproof jacket in size medium, and a feed missing the `material` or `size` attribute simply can't be surfaced for that query, even if the same fact sits in an image on your page.

A product feed is the commerce-specific counterpart to [structured data](/glossary/structured-data): schema markup labels facts on a page, a feed delivers them in bulk. Both make your catalogue legible to [shopper agents](/glossary/shopper-agent) and [agentic commerce](/glossary/agentic-commerce) systems. Keeping the high-demand attributes complete and current is the baseline for being found in AI shopping.

## Prompt Injection
Source: https://heybuffy.com/glossary/prompt-injection

Prompt injection is the attempt to manipulate an AI's behavior or output by feeding it crafted instructions or content. Getting a model to ignore its rules, or to repeat planted claims as if they were fact.

In an AI-visibility context, the tempting version is seeding the web with self-serving "best at X" statements in the hope an engine echoes them. Informal experiments have shown some engines will repeat absurd, never-corroborated rankings when prompted, while others decline, asking for specificity or finding no consensus. The lesson isn't a manipulation playbook; it's the opposite.

What survives is **corroboration**, not trickery. Anything an engine can be tricked into saying once, it can be corrected on the moment a real, [corroborated](/glossary/corroboration) source contradicts it, and manipulation risks your brand being described as untrustworthy. Durable AI visibility comes from being a genuinely well-established [entity](/glossary/entity-authority) that reputable sources agree on, not from gaming a prompt. Manipulated claims are also a route to [hallucinated](/glossary/ai-hallucination) answers. The last thing a brand wants attached to its name.

## Prompt-to-visit rate
Source: https://heybuffy.com/glossary/prompt-to-visit-rate

The **prompt-to-visit rate** is the share of AI prompts in a category that lead the same person to visit a relevant site within a set time window. It is measured by linking a prompt to a later visit by the same user — a visit that actually happened, and happened after the prompt — then dividing linked visits by prompts over the same period. It is a demand-side, user-behaviour metric, distinct from the [crawl-to-refer ratio](/glossary/crawl-to-refer-ratio), which counts a crawler's page fetches per referral and describes bot behaviour.

The defining feature of the rate is that it **rises sharply the longer the window**. In Gener8's July 2026 AI Landscape report (mobile, US & UK), it climbed roughly 9x to 10x between the 1-hour mark and 72 hours after a prompt, across every vertical measured — evidence that most of a prompt's eventual visits take days, not minutes, to materialise. The rate also varies widely by category (Gener8 put B2B SaaS near 14% and apparel near 3.5% at 24 hours) and by platform (Google AI Mode led ChatGPT and Gemini). Figures are single-vendor and self-reported, so treat them as directional and dated.

The rate matters because it reframes measurement: an AI answer's impact is a curve that builds over days, and the resulting visit usually arrives through branded search or as [dark traffic](/glossary/dark-traffic) rather than a labelled AI referral. A same-session attribution window will read most of that demand as zero.

## Prompt
Source: https://heybuffy.com/glossary/prompt

A prompt is the input a person gives an AI. The question, request, or instruction it responds to. In AI search it plays the role the keyword query played in traditional search, but it's typically longer, more specific, and phrased as a full natural-language question.

That difference matters for visibility. Where old search tracked a handful of high-volume keywords, the [prompts](/glossary/conversational-search) buyers type are long-tail and varied, "which moisturizer is best for sensitive skin in a dry climate?" rather than "best moisturizer." The [model](/glossary/large-language-model) often expands a single prompt into several sub-questions before answering. See [query fan-out](/glossary/query-fan-out).

For brands, the takeaway is to think in *real questions*, not keywords. The content that wins is the content that answers the actual prompts your customers ask. Including the comparisons, conditions, and "is this right for me?" follow-ups that a keyword list never captured.

## Query Fan-Out
Source: https://heybuffy.com/glossary/query-fan-out

When you ask an AI a question, it often doesn't run one search. It **fans the query out** into several sub-queries, runs them in parallel, and synthesises the combined results into one answer. Ask "best fragrance-free moisturizer for eczema under $30," and behind the scenes the engine might search for "fragrance-free moisturizer eczema," "best moisturizer sensitive skin," "affordable eczema moisturizer," and more.

This changes the visibility game in two ways. First, you don't have to match the user's exact phrasing. You have to be retrievable for the *underlying* sub-questions, which broadens the surface you're competing on. Second, a single answer can pull from many sources at once, so breadth of relevant, well-structured content matters more than a single perfectly-optimised page.

It's why "the questions that matter" for a brand number in the hundreds, and why measuring AI visibility means sampling across many prompts, not checking one.

## Query Freshness Window
Source: https://heybuffy.com/glossary/query-freshness-window

A query freshness window is the recency limit an AI search tool attaches to a single background search: how recently a page must have been updated to be preferred as a source for that specific sub-query. It is chosen by the *topic*, not by the site — the same page can be fresh enough for one query and stale for another.

The clearest example is ChatGPT's 2026 [pipe-delimited search format](/blog/chatgpt-new-search-query-language), where each search line carries a freshness value in days as its third field. Observed values scale with how fast the facts change: search consultant Suganthan Mohanadasan reported roughly 2 days for stock prices, 7 for sports results, 30 for commercial products, 90 for earnings data, and 365–3,650 days for evergreen forum content (a directional, single-account observation from August 2026 — treat the exact numbers as a snapshot).

Freshness windows matter because they turn "keep content fresh" from a vague instruction into a per-query threshold. A page outside its window can still be fetched — sometimes as a [silent source](/glossary/silent-source) that shapes the answer without a link — but it is not preferred for the citation. It is the retrieval-time cousin of [content decay](/glossary/content-decay): the window is the engine's recency rule at search time, and decay is what you observe downstream if you never refresh. The practical response is to match your refresh cadence to each page's window — monthly for commercial pages, rarely for definitions.

## Reddit product page
Source: https://heybuffy.com/glossary/reddit-product-page

A Reddit product page is a "deep dive" page Reddit generates about a specific product, assembled from what redditors have already said about it across the platform. When a product name is highlighted inside a thread, tapping it opens an AI-written summary of the relevant Reddit conversations plus direct quotes from those threads. When the brand has supplied a Dynamic Product Ads catalog entry, the page also shows a commerce card — product image, price, and a where-to-buy link.

The defining trait is who authors what. The editorial part — the summary and quotes — is generated from community conversations, not brand copy, so a brand cannot edit the verdict; it can only change what redditors say and supply the catalog card. That makes a Reddit product page a form of [earned media](/glossary/earned-media) turned into a shopping surface: closer to a live, aggregated review than to a controllable landing page.

These pages surface inside Reddit Answers, Reddit's AI search, when someone asks a shopping question, often alongside a "Related Products" carousel. Reddit began testing them for US users in early 2026 and expanded the shopping push at Cannes Lions in June 2026, starting with electronics, video games, and health and beauty. As of mid-2026 the feature is a gradual US-only test; the categories, geography, and rollout dates are dated and will move, but the mechanic — community conversations become a per-product page — is the durable part.

## Retrievability
Source: https://heybuffy.com/glossary/retrievability

Retrievability is the probability that an AI engine selects your page into the shortlist of sources it retrieves for a given query, the gate you must pass before anything else can happen. In a [retrieval-augmented](/glossary/retrieval-augmented-generation) answer, an engine first fetches a set of candidate documents, then reranks them, then synthesises and [cites](/glossary/citation) from what survives. Retrievability is only that first stage: were you pulled in at all?

It matters because it is the stage most GEO advice skips. Metrics like [Position-Adjusted Word Count](/glossary/position-adjusted-word-count) measure *prominence*, how much of your wording an answer uses once you are already in the context, which is a different thing entirely. A July 2026 critical survey of 45 GEO studies (Olivier Martinez, arXiv 2607.14035) found that citation-oriented rewrites can *raise* prominence while *lowering* retrievability, in one test cutting a page's top-10 presence after reranking by about 16%. Optimizing to be quotable can make you harder to fetch.

Read retrievability as the bottleneck, not the finish line. Topical relevance and clean, crawlable structure are its most reproducible levers; clever formatting tuned for the prominence stage is not. Because no engine reports retrievability directly, the practical proxy is your measured [cited-pages](/glossary/cited-pages) mix and citation coverage per engine over time, watched for whether a change helped you get selected, not just quoted.

## Retrieval-Augmented Generation (RAG)
Source: https://heybuffy.com/glossary/retrieval-augmented-generation

Retrieval-Augmented Generation is the architecture behind most AI *search*. Instead of answering purely from what a model memorised in training, a RAG system first **retrieves** relevant documents from a live index, then feeds them to the model to **generate** an answer grounded in what it just read, and usually cites those sources.

This is why your content can show up in an AI answer within days of publishing: it doesn't need to wait for the next training cycle, it just needs to be retrievable and clearly relevant. It's also why structure matters so much. Retrieval works on **passages**, so a clean, self-contained chunk that directly answers the question is far more likely to be pulled than the same point buried across a page.

For brands, RAG is the most influenceable layer of AI visibility: get reachable, get parseable, and you become eligible to be retrieved and cited.

## robots.txt
Source: https://heybuffy.com/glossary/robots-txt

`robots.txt` is a plain text file at the root of your domain (`yourdomain.com/robots.txt`) that tells automated crawlers which parts of your site they're allowed to fetch. It's the first thing a well-behaved bot checks.

For AI visibility, it's a one-line decision with real consequences: each [AI crawler](/glossary/ai-crawler) has its own user-agent token (`GPTBot`, `OAI-SearchBot`, `ClaudeBot`, `Google-Extended`, `PerplexityBot`), and you can allow or block each one, per path. Block a training bot and future models learn less about you; block a live-answer fetcher and you forfeit [citations](/glossary/citation) in AI answers.

A common, costly mistake is blocking AI crawlers by accident. Inherited from an old rule or a security plugin's default, then wondering why the brand never appears. It's worth reading your own `robots.txt` the way a bot would. Note that `robots.txt` differs from an [llms.txt](/glossary/llms-txt), which *guides* rather than *gates*.

## Same-Origin Policy
Source: https://heybuffy.com/glossary/same-origin-policy

The same-origin policy is a foundational browser security rule, introduced in 1995, that stops a website from reading data that belongs to another site — even when one site is embedded inside the other. It is what keeps an advertisement frame from reaching into your open email tab, and it is one of the protections most of the modern web quietly depends on.

The concept matters again in AI search because an [agentic browser](/glossary/agentic-browser) reads and acts on the live page for a user, which changes what the rule has to hold against. A 2026 University of Washington study of seven agentic browsers found that four of them let a malicious page bypass the same-origin policy, with a demonstrated data-theft attack against one (ChatGPT Atlas). The researchers' framing: in these browsers the protection effectively reduces to the strength of the agent's defenses against [prompt injection](/glossary/prompt-injection) — if a page can trick the agent with hidden instructions, it can push the agent across a boundary that used to be absolute (attributed and hedged as single-study, mid-2026 data; affected browsers will change as vendors patch).

For brands, the same-origin policy is distinct from [answer poisoning](/glossary/answer-poisoning), which seeds false content into the sources engines retrieve about you. This is on your own page, aimed at a visitor's agent during a live session. The practical implication is page hygiene: user-generated content, third-party embeds, and hidden text are where injected instructions live, so keeping them inert is now part of being safe for the agents that visit you.

## Search Generative AI Control
Source: https://heybuffy.com/glossary/search-generative-ai-control

The Search generative AI control is a site-level setting in Google Search Console, introduced in mid-2026, that lets a site owner opt out of Google's generative AI Search surfaces — [AI Overviews](/glossary/ai-overviews), [AI Mode](/glossary/google-ai-mode), and Discover's AI features — without affecting how the site appears in regular Google Search. Google has stated the control is not used as a ranking or inclusion signal elsewhere in Search, so an opted-out site keeps its normal ranking, indexing, and [featured snippets](/glossary/featured-snippet).

Its significance is the decoupling. Before it existed, Google's guidance was that the only way to keep a page out of AI Overviews was the `nosnippet` directive — which also stripped featured snippets and preview text, penalising the page in classic Search. The new control separates "stay out of the AI answer" from "keep my normal Search visibility," making the opt-out a real, reversible choice rather than a costly one.

It is narrow by design. It is a display-and-grounding setting inside Google Search — not a crawl rule ([robots.txt](/glossary/robots-txt)), not a training control (Google-Extended), and not effective outside Google. It does nothing about how ChatGPT, Perplexity, or Claude retrieve and cite pages. Reported effective from 17 June 2026 and rolled out first to a subset of UK site owners before widening, its availability was still uneven as of August 2026, so treat any specific status as dated. For most visibility-seeking brands the standing advice is to leave the control on and work on being cited well, not to opt out of a growing answer surface.

## Self-Preferencing
Source: https://heybuffy.com/glossary/self-preferencing

Self-preferencing is when an AI answer surface disproportionately cites its owner's own properties as the source for its answers, rather than independent third-party pages. In AI search it describes an engine routing its [citations](/glossary/citation) back into surfaces the platform controls — a search-engine's own results pages, its business listings, its video platform — so a large share of the "sources" in an answer belong to the same company that generated it.

The clearest measured example as of mid-2026 is [Google AI Mode](/glossary/google-ai-mode): SE Ranking's 2026 study of about 1.3 million citations found Google.com was the single most-cited domain at roughly 17.42%, tripling from about 5.7% a year earlier, with Google-controlled properties near 20% of all sources (attributed and hedged as single-vendor, directional data).

Self-preferencing is distinct from a [walled garden](/glossary/walled-garden), which is about *blocking outside agents*, and from a [first-party citation](/glossary/first-party-citation), which is a brand citing its *own* domain. Here it is the *platform* preferring itself. For brands it raises effective [visibility concentration](/glossary/visibility-concentration): where an engine cites itself heavily, the external-citation pool is smaller, so the surfaces the platform hands back to itself — like a claimed business profile — become the practical place to compete.

## Semantic Search
Source: https://heybuffy.com/glossary/semantic-search

Semantic search retrieves content by *meaning* instead of exact-keyword overlap. Where old keyword search rewarded pages that repeated the searched phrase, semantic search uses [embeddings](/glossary/embeddings) to match the *intent* behind a question to passages that genuinely answer it. Even if they use different words.

This is how AI engines find candidate sources before composing an answer. A question about "shoes that won't hurt my knees on pavement" can surface a page about cushioning and impact protection that never uses the word "knees," because the meanings align.

For brands, it ends keyword-stuffing as a strategy and rewards genuine topical depth. Cover the concept thoroughly. Its synonyms, sub-topics, and the adjacent questions buyers ask, so your content matches a wider range of [fanned-out sub-queries](/glossary/query-fan-out). Writing clearly for *meaning*, not for one exact phrase, is the core of [generative engine optimization](/glossary/generative-engine-optimization).

## Sentiment Analysis
Source: https://heybuffy.com/glossary/sentiment-analysis

Sentiment analysis measures the *tone* of how a brand is described, not just whether it appears. In AI visibility, two brands can both show up in an answer while one is framed as "premium and well-reviewed" and the other as "a cheaper, lower-quality option". Same presence, very different outcomes.

It's the layer that turns raw [mentions](/glossary/total-mentions) and [share of voice](/glossary/share-of-voice) into *positioning*. Tracking it reveals the gap between how a brand sees itself and how the models actually summarize it. Often the most uncomfortable and useful finding in an AI-visibility review.

Because AI answers vary by phrasing and by engine, a reliable sentiment read comes from sampling many prompts across every engine over time, not a single check. On the Buffy Intel side, this is captured as [Brand Perception](/glossary/brand-perception). The structured view of how engines characterize your brand, and where to push to improve it.

## Share of Voice (SoV)
Source: https://heybuffy.com/glossary/share-of-voice

Share of Voice answers the most basic question in AI visibility: **do you even show up?** Across a set of category-level prompts. The kinds of questions buyers actually ask an AI. It's the percentage of answers that mention your brand at all.

A high SoV means the engines surface you across more of the category's AI conversation. A low SoV means you're absent from most of it, no matter how strong your product is.

It's a *presence* metric, not a *position* one. Being mentioned ninth still counts toward SoV. That's why it's read alongside [Top-Ranked %](/glossary/top-ranked-percent) and [Average Rank](/glossary/average-rank), which capture how *prominently* you appear when you do. Together they answer "how often, and how high."

Because AI answers shift by phrasing and differ across engines, a reliable SoV reading comes from many prompts, sampled repeatedly, across every engine, not a single spot check.

## Shopper Agent
Source: https://heybuffy.com/glossary/shopper-agent

A shopper agent is an AI agent a brand deploys to carry a customer through the shopping journey. Answering product questions, comparing options, completing checkout, and handling service. Conversationally and in the brand's own voice. Unlike a generic assistant, it represents one brand, and it is increasingly surfaced inside third-party AI platforms rather than only on the brand's own site.

The concept went mainstream in mid-2026: Salesforce's Agentforce Commerce reached general availability with a "Shopper Agent" (consumers), "Buyer Agent" (B2B procurement), and "Merchant Agent" (catalog operations), and Google launched a brand-voice "Business Agent" inside Search, with distribution into ChatGPT, Gemini, and Google AI Mode as the headline.

One caveat for brands: a shopper agent is a channel, not a visibility lever. It speaks and sells for you *once you're in the consideration set*, but whether an engine surfaces your product still depends on [agentic commerce](/glossary/agentic-commerce) readiness. Catalog richness, [structured data](/glossary/structured-data), entity strength, and corroboration. Being chosen is still answer-engine optimisation.

## Silent Source
Source: https://heybuffy.com/glossary/silent-source

A silent source is a page an AI engine retrieves and uses while composing an answer, but does not link or name in the visible response. It shapes what the model says without ever surfacing as a [citation](/glossary/citation). You supplied part of the answer and left no trace.

It is distinct from a [ghost citation](/glossary/ghost-citation), where the engine *does* link your page but omits your brand name. A silent source is a step further into the dark: no link at all, only influence during [retrieval](/glossary/retrieval-augmented-generation). A mid-2026 Peec AI analysis illustrated this with arXiv, which it reported was pulled in during retrieval for unrelated queries (even a shopping question) and referenced several times without appearing in the answer. Treat that as a single-vendor, directional observation.

Silent sources matter because they break output-only measurement. If you only watch the citations an answer displays, you miss pages doing real work behind the scenes, and you miss when an engine quietly reorders which domains it trusts. It is the retrieval-side cousin of the visible-but-unclicked [dark library effect](/glossary/dark-library-effect). The fix is to measure retrieved sources, not just named ones.

## site: operator
Source: https://heybuffy.com/glossary/site-operator

The `site:` operator is a long-standing search command — written as `site:example.com` — that restricts results to a single domain. Originally a manual Google Search shortcut, it has become a notable signal in AI search because engines now issue it inside their [query fan-out](/glossary/query-fan-out): rather than searching the open web, the model restricts a background sub-query to one named domain.

Its use inside AI fan-outs rose sharply in 2026. A July 2026 Peec AI analysis reported the `site:` operator appeared in about 43% of ChatGPT 5.6 query fan-outs, versus roughly 0.004% in ChatGPT 5.5 (single-vendor, directional, one model version). In that data, about 84% of the targeted domains were branded — the first-party site of the product or company in question — and the operator pointed at the bare root domain in roughly 86% of cases, narrowing to a specific path only when a precise product or pricing fact was needed.

For AI visibility, the `site:` operator matters because it marks a source-targeted [retrieval](/glossary/retrieval-augmented-generation) step: the model has decided which domain it trusts for an answer and is pulling facts directly from it. That rewards first-party pages whose specs, pricing, and official details are exposed as clean, server-rendered text over [structured data](/glossary/structured-data). A `site:` probe against your domain that finds nothing machine-readable is a missed citation.

## Site Reputation Abuse
Source: https://heybuffy.com/glossary/site-reputation-abuse

Site reputation abuse. Often called *parasite SEO*. Is publishing third-party content on an established, trusted website primarily to borrow that site's ranking signals, rather than because the content belongs there. A classic example is a promotional "best X" roundup placed on a major publication's domain purely to inherit its authority. Google names it as a spam category in its Search spam policies.

It matters for AI visibility because engines lean heavily on trusted domains, and [best-of lists](/glossary/best-of-list) are among the most-cited page types in AI answers. That makes renting a reputable site's authority tempting, and, since Google's 2026 clarification that its spam policy covers [manipulating AI answers](/blog/google-spam-policy-ai-answers), squarely a spam tactic when done to game those answers.

The clean alternative is *earned* placement: get included in independent lists on the merits, and build [entity authority](/glossary/entity-authority) through genuine [corroboration](/glossary/corroboration). Earned inclusion looks similar on the surface but is durable, because it reflects real trust rather than borrowed signals.

## Spam Update
Source: https://heybuffy.com/glossary/spam-update

A **spam update** is a periodic Google algorithm change that enforces Google's published spam policies, demoting sites found to violate them. It differs from a *core update*, which is a broad re-assessment of overall relevance and quality: a spam update targets policy violations specifically — such as scaled content abuse or expired-domain abuse — rather than reweighting quality across the board. Google issues several a year; the August 2026 spam update, for example, rolled out globally over about two days, 18–21 August 2026, and introduced no new policy types.

Spam updates matter for AI visibility because [AI Overviews](/glossary/ai-overviews) and [AI Mode](/glossary/google-ai-mode) are not a separate index — they are [grounded](/glossary/grounding) in Google's ranked web results. When a spam update demotes a site in classic ranking, it shrinks that site's presence in the same pool the AI answer draws from, so lost rankings tend to drag AI-answer citations down with them on Google's own surfaces. The effect is partial and lagged, and it is Google-only: ChatGPT, Perplexity, and Claude operate their own retrieval and are not directly moved by a Google spam update.

Recovery follows the ranking timeline, which Google says can take months. In a May 2026 clarification Google noted its spam policies also cover attempts to manipulate generative AI responses, so seeding or gaming AI answers now sits under the same enforcement — a further reason the durable route to citations is genuine credibility, not manipulation.

## Stablecoin
Source: https://heybuffy.com/glossary/stablecoin

A stablecoin is a cryptocurrency token engineered to hold a steady value, typically by being pegged one-to-one to the US dollar and backed by reserves. Unlike volatile crypto assets, it's built to be *spent*, not speculated on, which is why it's emerging as a settlement rail for payments.

Stablecoins matter for [agentic commerce](/glossary/agentic-commerce) because AI agents make many small, high-frequency payments. To other agents, APIs, and merchants, that the ~$0.30 per-transaction floor of card networks makes uneconomic. A stablecoin can settle a sub-cent payment in seconds, programmatically, for a fraction of a cent. Reported agent activity is still tiny (a Keyrock report via CoinDesk estimated ~$73M settled May 2025-April 2026) but growing, and June 2026's broadly-backed *Open USD* added dollar-stablecoin infrastructure agent payments could later ride on.

One caveat for brands: a stablecoin is a payment rail, not a visibility lever. It moves money *after* an agent has chosen a product; being the product an agent picks is still [answer-engine optimisation](/glossary/answer-engine-optimization). Catalog richness, entity strength, and corroboration.

## Structured Data (Schema markup)
Source: https://heybuffy.com/glossary/structured-data

Structured data is markup. Usually JSON-LD following the Schema.org vocabulary, that explicitly labels what things on your page *are*: this is a `Product` with this `price` and `availability`; this is an `Organization`; this is an `FAQPage` with these questions and answers.

Humans infer all this from layout and context. Machines shouldn't have to guess, and structured data means they don't. It turns a wall of text into labelled, extractable facts an engine can lift cleanly into an answer, which is why it consistently helps both classic rich results and AI citations.

For AI visibility the high-value types are `Product`/`Offer` (for commerce), `FAQPage` (direct Q&A engines love to quote), `Organization` and `DefinedTerm` (entity clarity), and `BreadcrumbList`. It pairs with [llms.txt](/glossary/llms-txt): structured data makes individual pages legible; llms.txt points crawlers at the right ones. Both make your facts easy to [ground](/glossary/grounding) and [cite](/glossary/citation).

## Top-Ranked %
Source: https://heybuffy.com/glossary/top-ranked-percent

Being mentioned and being *recommended first* are different things. Top-Ranked % captures the second: of the AI answers that mention your brand, the share that put you at #1. The single top pick, not just somewhere in the list.

It's the sharpest read of preference. Two brands can have identical [Share of Voice](/glossary/share-of-voice) while one is consistently the lead recommendation and the other is perennially "also available." For high-intent buyer questions, the top slot is where the trust, and the click. Goes.

It pairs with [Average Rank](/glossary/average-rank): Top-Ranked % is the headline "how often am I first," while average rank shows where you land the rest of the time. A brand can have a modest Top-Ranked % but a strong average rank (usually 2nd-3rd), or the reverse. The two together describe your real competitive position.

## Total Mentions
Source: https://heybuffy.com/glossary/total-mentions

Total Mentions is the raw count: how many times your brand surfaced across every tracked prompt in the latest analysis. Where [Share of Voice](/glossary/share-of-voice) is a *percentage* (the share of answers that mention you), Total Mentions is the underlying *volume*.

The two read together. A rising Share of Voice on flat mentions can simply mean competitors faded; rising mentions *and* share is genuine momentum. And volume gives the other metrics their weight. A 90% [Top-Ranked %](/glossary/top-ranked-percent) means far more across hundreds of mentions than across a handful.

Treat it as the denominator-with-context: the absolute footprint your brand has in AI answers, which makes every rate-based metric meaningful rather than a small-sample artifact.

## UCP (Universal Commerce Protocol)
Source: https://heybuffy.com/glossary/ucp

UCP, the Universal Commerce Protocol, is an open-source standard from Google that gives AI agents one shared way to shop across merchants — discovering products, building a cart, checking out, and handling fulfilment and order updates. Instead of an agent integrating separately with every store's checkout, UCP defines common primitives a merchant exposes once and any compliant agent can use, the way HTTP standardised the web.

As of its January 2026 specification, UCP standardises six functional primitives: **product discovery, checkout, discount handling, fulfilment, order management, and identity linking**. It is compatible with [AP2](/glossary/ap2) for the payment-authorisation step, and merchants can implement it via ordinary APIs, the Agent2Agent (A2A) protocol, or the Model Context Protocol. That makes UCP the commerce-orchestration counterpart to the [Agentic Commerce Protocol (ACP)](/glossary/agentic-commerce-protocol) from OpenAI and Stripe — the two are parallel bets at the same layer, sitting above the payment protocols beneath them.

Google announced UCP on 11 January 2026, co-developed with retailers including Shopify, Etsy, Wayfair, Target, and Walmart and endorsed by more than 20 partners such as Visa, Mastercard, Stripe, and American Express. Its first product is the **Universal Cart**, a single cart shoppers fill across Google surfaces — Search and the Gemini app first, with YouTube and Gmail to follow — where the brand stays the merchant of record. So UCP is genuinely an open standard, while its largest early deployment is Google's own surfaces; both are true. Partners, surfaces, and rollout geography are dated to mid-2026 and will move.

## Verified bot
Source: https://heybuffy.com/glossary/verified-bot

A verified bot is an [AI crawler](/glossary/ai-crawler) whose identity has been confirmed by evidence outside its own user-agent header, most commonly a reverse-DNS lookup that resolves the requesting IP to the operator's published address ranges, or an emerging cryptographic scheme that signs the request. It is the answer to a simple problem: a user-agent string is self-declared and trivially spoofed, so the name in a request tells you what a bot *claims* to be, not what it is.

Verification matters because AI-crawler controls that trust the header, including [robots.txt](/glossary/robots-txt), are only as reliable as the honesty of the bot. Non-compliant scrapers routinely rotate IPs, fake browser identities, and impersonate well-known bots, so any real enforcement or measurement has to key off verified identity rather than the label. Blocking, rate-limiting, and allowlisting all depend on knowing the traffic is genuinely from the operator it names.

In practice, verification takes three forms: reverse-DNS and published-IP-range checks (the long-standing method operators like OpenAI, Anthropic, and Google document); managed "verified bot" lists at CDN level (Cloudflare and others maintain them); and signed-agent standards such as HTTP Message Signatures / web-bot-auth, still early but designed to make a bot's identity cryptographically provable. Verify before you act, because trusting the header alone lets an impostor through and blames the wrong operator for traffic that was never theirs.

## Video AEO
Source: https://heybuffy.com/glossary/video-aeo

Video AEO is [answer-engine optimization](/glossary/answer-engine-optimization) applied to video: structuring a video, and the page that hosts it, so AI answer engines can retrieve, understand, and cite what it says. Because an engine lifts text, not footage, video AEO is mostly about the video's transcript, captions, title, description, chapters, and [structured data](/glossary/structured-data) rather than its production values.

The practice matters because video became a top AI-[citation](/glossary/citation) source in 2026. Ahrefs' mid-2026 data put YouTube as the single most-cited domain in Google AI Overviews at roughly 20.9% mention share, ahead of every publisher and brand site, helped by Google owning YouTube and being able to read its transcripts. A separate Ahrefs study of 75,000 brands found YouTube mentions correlated with AI brand visibility more strongly than any other metric. These are single-vendor, directional figures, but the direction is consistent.

In practice, video AEO means answering one question per video, answer-first; publishing an accurate transcript rather than relying on auto-captions; adding chapters and a fact-rich description; and marking up the hosting page with `VideoObject` schema. It is the video-shaped case of [multimodal search](/glossary/multimodal-search): expose the facts as retrievable text, or the engine can't cite them.

## Visibility concentration
Source: https://heybuffy.com/glossary/visibility-concentration

Visibility concentration measures how much of a category's AI-answer visibility is held by a few dominant brands. It is usually expressed as the **share of total category visibility owned by the top three brands**: a high share means answers in that vertical are dominated by a handful of names, and a low share means the field is contestable.

Concentration is a property of the *category*, not of AI search overall. Semrush's 2026 AI Visibility Index found the top three brands held roughly 82.9% of News & Media visibility and 76.9% of Consumer Electronics, but only about 41.4% of Finance and 42.2% of Industrial (126M US prompts, January–April 2026, single-vendor and directional). So the same engines behave close to winner-take-all in one vertical and leave real room to climb in another.

It is distinct from [Share of Voice](/glossary/share-of-voice), which measures *your* brand's presence, whereas visibility concentration measures the *market structure* around you. It also differs from a [citation fingerprint](/glossary/citation-fingerprint) (which page *types* get cited) and from domain concentration (which domains engines lean on generally). Reading your category's concentration first tells you whether to compete for the crowded head directly or to go around it with long-tail depth and [earned placement](/glossary/earned-media).

## Walled garden
Source: https://heybuffy.com/glossary/walled-garden

A walled garden is a platform that deliberately restricts outside AI agents and crawlers from reading its content or acting inside its accounts, so that discovery, data, and transactions stay within its own ecosystem. In AI commerce, the term describes large marketplaces that block third-party [shopper agents](/glossary/shopper-agent) while building their own in-house assistants, keeping ad revenue, first-party data, and checkout under their control.

The walls go up at three levels: disallowing an [AI crawler](/glossary/ai-crawler)'s user-agent in [`robots.txt`](/glossary/robots-txt), challenging or blocking agent traffic at the CDN or WAF, and legal enforcement against unauthorized access to logged-in accounts, the layer at issue in Amazon's 2026 preliminary injunction against Perplexity's Comet browser (attributed and hedged, as it is a preliminary order in ongoing litigation).

A walled garden is distinct from *protocol* choice: a platform can back an open checkout standard for authorized partners and still gate crawlers it hasn't sanctioned. For brands, the practical response is to keep your own storefront open and legible and to be present on more than one surface, so a single platform's closed posture doesn't erase you from [agentic commerce](/glossary/agentic-commerce).

## Web Discovery Project
Source: https://heybuffy.com/glossary/web-discovery-project

The Web Discovery Project (WDP) is Brave's open-source, opt-in mechanism for building an independent search index from anonymous signals contributed by users' Brave browsers, rather than from submitted URLs. It matters for AI visibility because Claude's live web search appears to draw on Brave's index, so what WDP discovers shapes what Claude can cite.

There is no submission path: no search console, no sitemap intake, no IndexNow. Per Merj's mid-2026 reading of the WDP source code, a page enters Brave's index through one of two channels. The **page channel** requires roughly 20 different opted-in users on different networks to visit a URL. Enforced by [STAR](https://brave.com/privacy-updates/19-star/) secret sharing, which keeps the URL undecryptable until the threshold is met. The **query channel** needs just one opted-in user to view a Google, Bing, Yahoo, or DuckDuckGo results page where the URL ranks; the browser anonymously re-fetches that page and reports the listed URLs. So classic search visibility seeds Brave discovery.

Because Brave's own crawler sends no distinctive user agent, a "block all unknown bots" rule can silently exclude it. Making WDP a quiet dependency for anyone who wants to be found by [Claude](/blog/how-to-get-cited-in-claude). Being discoverable here is upstream of being cited: it is [answer-engine optimisation](/glossary/answer-engine-optimization) applied to an index most brands never think about.

## x402
Source: https://heybuffy.com/glossary/x402

x402 is an open standard for paying over HTTP. It reuses the long-dormant `402 Payment Required` status code so a server can quote a price and a client can pay for a gated resource inside a normal web request — no checkout page, no stored card, no human login. It was designed for machine-to-machine payments: an AI agent, app, or crawler requests a page, dataset, API, or product, receives a `402` stating the price and where to pay, pays, and retries with proof attached.

The handshake is the whole idea: request → `402` with price and accepted asset → pay → retry with proof → resource returned. Because it lives inside ordinary HTTP, any compatible server can charge and any x402-speaking client can pay, without a bespoke billing integration. That suits the sub-cent, high-frequency payments AI agents generate — territory where the ~$0.30 card-fee floor makes traditional rails uneconomic.

[Coinbase](/blog/stablecoins-agentic-payments) originated x402 as a stablecoin-native scheme (USDC on Base). On 14 July 2026 the **Linux Foundation** launched the x402 Foundation to steward it under vendor-neutral governance, with 40 members including Google, Stripe, Visa, Mastercard, Cloudflare, and Coinbase. The standard is written to be payment-type-agnostic — spanning [cards to stablecoins](/blog/cards-vs-stablecoins-agent-payments) — though most live settlement today runs in stablecoins.

x402 is a payment-request layer, not a checkout experience or a settlement rail. It sits below the [Agentic Commerce Protocol](/glossary/agentic-commerce-protocol) (which orchestrates an order inside an assistant) and above the card and stablecoin rails (which move the money). One notable use beyond commerce: it makes charging an [AI crawler](/glossary/ai-crawler) for access — [pay-per-crawl](/blog/can-you-charge-ai-agents-to-crawl) — a real option between allowing and blocking. Figures and membership are dated to mid-2026 and will move.

## Zero-Click Search
Source: https://heybuffy.com/glossary/zero-click-search

A zero-click search is one the user never leaves: the answer is delivered right there. In a featured snippet, a knowledge panel, or now an AI Overview, so there's no click to a website. With AI answers, zero-click has gone from common to dominant for informational queries.

This is the strategic shift behind GEO. If users increasingly *don't* click, then the goal can't only be "rank a link to earn a visit." It has to also be **being the source named and cited inside the answer**: because that's where the brand impression (and the trust) now forms, click or no click.

It reframes how you measure success, too: alongside clicks and traffic, you track presence and [citations](/glossary/citation) in the answers themselves. Being the cited authority in a zero-click answer can shape a buyer's shortlist even when no visit shows up in your analytics. Part of why AI visibility needs its own measurement, not just web traffic.

# Articles (209)

## Accessibility and AI: why your accessibility score predicts AI-parseability
Source: https://heybuffy.com/blog/accessibility-and-ai-parseability

Accessibility and AI-parseability are the same discipline. The semantic HTML that lets a screen reader navigate your page. Real headings, labelled forms, alt text, table headers. Is exactly what lets an [AI crawler](/glossary/ai-crawler) segment, extract, and cite your content. So your Lighthouse **accessibility score** doubles as a rough proxy for how cleanly AI engines can read you.

## Why does accessibility predict AI-parseability?

Because both a screen reader and an AI parser consume a page through its **structure, not its pixels**. Neither sees your layout; both rely on the underlying markup to know what's a heading, what's a control, what an image depicts, and where one idea ends and the next begins. Markup that communicates that to assistive tech communicates the same thing to a crawler.

The practical upshot: the fixes that raise an accessibility score. Semantic landmarks, accessible names, alt text, labelled tables. Are the same fixes that turn a wall of `<div>` soup into [extractable, chunk-level content](/blog/how-to-get-cited-by-ai) an engine can lift a clean passage from.

## What does the Lighthouse accessibility score actually measure?

Per Chrome's documentation, the Lighthouse accessibility score is a **weighted average of 70+ automated audits**, with weighting based on axe user-impact assessments. Two details matter for how you read it:

- **Each audit is binary. Pass or fail, no partial credit.** If some buttons have accessible names and others don't, the page scores **zero** on that audit. One overlooked control can sink a check.
- **Audit weights range from 3 to 10.** The heaviest (weight 10) are image alt text, button names, form labels, and ARIA validity. Lighter ones (weight 3) include heading order and skip-link focusability. Manual and best-practice checks don't affect the number.

So the score is impact-weighted toward exactly the structural facts AI parsers depend on, which is why it works as a proxy.

## Which accessibility checks map to AI extraction?

The overlap is close to one-to-one. Each accessibility requirement enforces a structural signal an AI engine also relies on:

| Accessibility check | What it enforces | Why AI parsers need it |
|---|---|---|
| **Image alt text** | A text alternative for every meaningful image | Exposes visual facts as text for multimodal [fan-out](/blog/how-query-fan-out-works) |
| **Accessible names** (buttons, links) | Every control is labelled | Lets agents identify and act on the right element |
| **Heading order & landmarks** | A logical H1→H2→H3 outline | Defines clean chunk boundaries for passage retrieval |
| **Table headers & captions** | Real `<th>`/`<caption>`, not styled divs | Makes specs and comparisons extractable as [structured data](/glossary/structured-data) |
| **Form labels** | Inputs tied to labels | Machine-readable forms. The basis of agent actions |
| **HTML lang & title** | Document language and title set | Language and topic signals for indexing |

The pattern: every point you earn for a human using assistive tech, you also earn for a machine trying to parse you.

## How to use your accessibility score for AI visibility

Treat it as a cheap, repeatable parseability check, not a one-off:

1. **Score a representative template, not just the homepage.** In Chrome DevTools → Lighthouse → Accessibility, audit a product page, an article, and a category page. The templates that actually carry your facts.
2. **Fix the weight-10 failures first**: alt text, button and link names, form labels, ARIA validity. These are the gaps most likely to hide content from AI too.
3. **Repair the heading outline.** A clean H1→H2→H3 structure is what passage-level retrieval segments on; skipped or decorative headings blur the boundaries.
4. **Move facts into real tables.** Specs and comparisons belong in `<table>` with headers, not a CSS grid of divs an engine reads as prose.
5. **Re-score after each change and track the trend.** Parseability erodes as templates change; a periodic snapshot catches regressions early.
6. **Pair it with reachability checks.** Accessibility assumes the crawler got the page at all. Confirm your [CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers) and the page isn't [too slow or JS-dependent to render](/blog/does-page-speed-affect-ai-visibility).

> Accessibility and AI-parseability are the same discipline: a page a screen reader can navigate is a page an AI crawler can chunk and cite.

## What the score won't tell you

A high accessibility score is necessary, not sufficient. It confirms your markup is *legible*. It says nothing about whether the page is *reachable*, *rendered*, or *worth citing*. A flawlessly accessible page whose content only appears after JavaScript runs can still be invisible to an engine that doesn't execute it. And clean structure around thin, unsourced content just makes emptiness easy to read.

So use the score as one signal in a stack: reachable (crawlable, not CDN-blocked), rendered (server-side, fast), parseable (accessible, semantic), and citable (specific, sourced, fresh). Catching when a template change quietly drops your parseability, and watching whether engines still cite you afterward. Is part of what ongoing monitoring with **Buffy Intel** surfaces.

## How to add the elements that lift AI citations: statistics, quotes, and sources
Source: https://heybuffy.com/blog/add-citation-lifting-elements

**To make AI answers pull from your page more often, edit each key claim to carry a specific statistic, a named quotation, and a citation to a credible source, then tighten the passage and cut keyword padding.** That is the practical distillation of the [Princeton GEO experiment](/blog/what-content-changes-lift-ai-citations), which tested nine content edits and found evidence-adding changes lifted a source's visibility by up to about 40%, while keyword stuffing made it roughly 10% worse.

This is the action companion to that study explainer. The steps are ordered by the return the experiment measured, highest first. Apply them to your highest-value pages, and treat your own measured [citation coverage](/glossary/citation-coverage) as the scoreboard, not the benchmark's percentages.

## Step 1: Add a specific, attributed statistic to each key claim

This was the single strongest edit in the study (about +41% on the paper's [position-adjusted word count](/glossary/position-adjusted-word-count) metric). Go through each section and replace one vague claim with a verifiable number.

- "Fast setup" becomes "live in under five minutes, no developer."
- "Widely used" becomes "used by 4,200 teams as of mid-2026."
- Attribute and date anything you did not measure yourself ("Google reported…, June 2026"), and cut any figure you cannot source. An unattributed statistic is a liability, not a lift.

The point is not decoration; a specific number is a clean, liftable unit an engine can quote with confidence.

## Step 2: Cite authoritative external sources inline

In the experiment, adding citations to credible sources was the biggest **equalizer**: a source sitting 5th in the results gained roughly 115% relative visibility. Linking out to authoritative references adds [corroboration](/glossary/corroboration), the signal engines use to decide a passage is safe to repeat.

- Link the primary source for each claim (the study, the standard, the official doc), with descriptive anchor text naming the source, not "click here."
- Citing your own sources models the behaviour engines reward and makes your page safer to quote. It is the same discipline as earning a [citation](/glossary/citation) yourself.

## Step 3: Quote a credible source

Adding quotations lifted the study's perceived-authority score by about 28%. A short, attributed quotation from a recognised source raises the authority of the surrounding passage and gives the engine a crisp, liftable line.

- Use a real, verifiable quotation with clear attribution; never invent one.
- One well-placed quote per major section beats a wall of them.

## Step 4: Tighten each passage so it is answer-first and self-contained

The study found that combining clearer writing (fluency optimization) with added statistics beat every single method on its own. Clarity is a multiplier, not an afterthought.

- Open each section with the direct answer in about 40–60 words, then explain.
- Keep each chunk self-contained (roughly 100–300 words) so it can be lifted without the rest of the page.
- Put specs, steps, and comparisons in tables or lists, the formats engines extract most cleanly. This is the same structural work behind [how to get cited by AI](/blog/how-to-get-cited-by-ai) and the [six factors behind AI recommendations](/blog/factors-ai-recommends-products).

## Step 5: Cut keyword padding

The one edit that went backwards. Keyword stuffing performed about 10% worse than the unedited baseline, because repetition adds no evidence and reads as low quality.

- Remove sentences that repeat the target phrase without adding a fact.
- Cover the topic's natural related vocabulary instead, so the page spans the full concept rather than one phrase. This is the difference between semantic depth and spam, and it is why you can [grow AI visibility without spam](/blog/grow-ai-visibility-without-spam).

## Step 6: Re-measure per engine and refresh on a cadence

The Princeton figures are controlled-environment relatives, not promises for your niche, so the only number that counts is your own. After editing, track your citation share on each engine separately, and revisit high-value pages before they go stale, since [citations decay after roughly a quarter](/blog/content-freshness-citation-cliff).

> Add a statistic, a source, and a quote to every claim that matters, tighten the passage, and delete the padding. That single edit pattern is most of what the first GEO experiment found actually works.

One caution: these edits raise how often you are *cited*, which is not the same as being *named*. If engines lift your facts but drop your brand, that is a separate job, covered in [how to get named in AI answers](/blog/how-to-get-named-in-ai-answers). Add [entity](/glossary/entity-authority) signals alongside the evidence so your name travels with your facts.

Applying this across a site is repetitive work, and its payoff is only visible if you can see citation share move. That is where **Buffy Intel** fits: it snapshots whether AI engines cite and recommend your brand over time, so you can edit a page, then watch whether the statistics, sources, and quotes you added actually lifted your citations, engine by engine, rather than assuming a benchmark percentage carried over.

## AEO for education and learning content: a playbook for the 'Learn' intent
Source: https://heybuffy.com/blog/aeo-for-education-and-learning-content

Education and Knowledge is one of the top topics people bring to AI search, and "Learn" is one of the five core intents Google names for AI Mode. For course providers, edtech products, universities, and knowledge brands, that makes [answer engine optimisation](/glossary/answer-engine-optimization) a direct channel: when someone asks an AI engine how to learn a skill, you want your explanation cited and your programme recommended. This playbook turns the "Learn" intent into a concrete content plan.

It draws on Google's documented usage data and applies the same method behind the rest of the corpus. It builds on [what GEO and AEO are](/blog/what-is-geo-aeo); here the focus is the learning vertical specifically.

## Why is the "Learn" intent worth optimising for?

Because learning questions are a large and well-suited slice of AI search. In Google's 2026 report *"How people are using AI Mode in the U.S."*, **Education/Knowledge ranked among the top topics** people search in AI Mode, and Google groups usage into five intents. Explore, Decide, **Learn**, Create, Do (see the [AI Mode usage reference](/blog/google-ai-mode-usage-data-2026)). Two behaviours make learning content a natural fit:

- **Queries are longer and conversational.** Google reports the average AI Mode query is about triple the length of a traditional search, and follow-up queries grew more than 40% per month. The shape of someone working through a subject step by step.
- **People ask question-words.** Google's top first words in AI Mode were *What, How, I, Is, Can*. The grammar of learning.

All figures are Google's own platform data, dated to mid-2026 and not independently audited, so read the direction (learning is a major, conversational use of AI search) as firmer than any single number.

> A learner rarely asks one question. They ask what it is, how to start, how long it takes, and whether it's worth it, so the content that wins the "Learn" intent answers the whole journey, not just the headline.

## What does the learning question tree look like?

AI engines fan a single learning goal into many sub-questions and assemble the answer from different sources. Cover the whole branch set, each as a self-contained chunk:

| Branch | Example question | What to publish |
|---|---|---|
| Definition | "What is data analytics?" | A clear, answer-first definition |
| How to start | "How do I learn data analytics?" | A step-by-step path |
| Prerequisites | "What do I need before starting?" | A prerequisites list |
| Time | "How long does it take to learn?" | An honest, ranged estimate |
| Comparison | "Bootcamp vs degree vs self-study?" | A neutral criteria table |
| Cost | "How much does it cost?" | Transparent pricing/options |
| Outcome | "What job or credential does it lead to?" | Career/credential mapping |

Covering several branches well can get you cited multiple times in one answer. This is the [query fan-out](/glossary/query-fan-out) multiplier at work. The how-to side of this is in [how query fan-out works](/blog/how-query-fan-out-works).

## How should you structure a learning page?

Apply the extraction rules that get any chunk selected, tuned for instruction:

- **Answer-first, then teach.** Open each section with the direct answer in 40-60 words, then expand. A learner (and a model) should get the gist before the detail.
- **Real steps as a numbered list.** Instructional sequences belong in ordered steps, not prose, and they map cleanly to learning-oriented structured data.
- **Prerequisites and specs in tables.** Time, cost, level, and prerequisites are facts; put them in tables a model can lift.
- **Define jargon inline** on first use. Learning content is full of terms a newcomer won't know.
- **One concept per chunk** so a section answers its question without the rest of the page.

This is the same discipline as [getting cited by AI](/blog/how-to-get-cited-by-ai) and [optimising for AI Overviews](/blog/how-to-optimize-for-ai-overviews); learning content simply has more steps and prerequisites to expose.

## Why does teaching credibility matter so much here?

Because learning is a high-stakes, [experience-and-expertise](/glossary/e-e-a-t) topic. Engines and learners both want to know *who is teaching this*. Make your authority explicit and verifiable:

- **Name the instructors** and their relevant qualifications, not "our expert team."
- **State accreditation or recognition** where it exists, with the issuing body named.
- **Show outcomes honestly**: completion data or credential value, attributed and dated, never invented.
- **Be consistent across the web** so your institution reads as a strong [entity](/blog/entity-strength-ai) the [knowledge graph](/glossary/knowledge-graph) recognises.

Unverifiable claims hurt more than they help here: over-claiming on outcomes is the fastest way to be described as untrustworthy.

## How do you keep learning content cited over time?

Curricula and tooling change, and live AI retrieval favours recently-reviewed pages. Put your core learning pages on a refresh cadence and make updates substantive. Corrected tool versions, new prerequisites, updated cost. Rather than a bumped date. Definitional explainers ("what is X") decay slowly; "how to learn X in 2026" pages decay faster and need attention. The mechanics of this are in the [content-freshness citation cliff](/blog/content-freshness-citation-cliff).

## Where should education brands start?

A focused first pass:

1. Pick one flagship subject you genuinely teach well.
2. Map its learning question tree (the table above) and write a self-contained chunk for each branch.
3. Make teaching credibility visible on the page.
4. Add learning-appropriate structured data and clean internal links between the branches.
5. Track whether AI engines cite and recommend you for the subject. Across engines, over time.

That last step is the loop that closes it: knowing whether AI answers actually surface, cite, and recommend *your* programme for the questions learners ask is exactly what **Buffy Intel** measures. Presence, citations, and share of voice across every major engine, tracked over time rather than spot-checked.

## ACP vs AP2 vs x402: how the agent-payment standards compare
Source: https://heybuffy.com/blog/agent-payment-protocols-compared

**Three standards are being built for the moment an AI agent buys something, and they mostly sit at different layers rather than competing.** The [Agentic Commerce Protocol (ACP)](/blog/agentic-commerce-protocol-acp) orchestrates a checkout inside chat; Google's [AP2](/blog/what-is-ap2) proves a human authorised the payment; [x402](/blog/what-is-x402) carries the payment request over HTTP. This is a neutral, criteria-based comparison of what each does, who backs it, and how they fit together — because for most brands the answer is not "pick one" but "understand which layer each owns."

All three are early and moving, so figures and adoption below are dated to mid-2026 and directional. The durable point is the layering, which is stable even as the details shift.

## What are ACP, AP2, and x402, in one line each?

- **ACP (Agentic Commerce Protocol)** — an OpenAI-and-Stripe standard that lets an agent complete a delegated checkout inside a chat surface like ChatGPT.
- **AP2 (Agent Payments Protocol)** — a Google standard that attaches cryptographic proof of human authorisation to an agent-initiated payment.
- **x402** — a Linux Foundation standard that revives the HTTP `402 Payment Required` status so a client can pay for a resource inside an ordinary web request.

Each solves a different piece of the same problem: how does a machine buy from you, provably and without a person clicking through a hosted checkout?

## How do the three standards compare, criterion by criterion?

The criteria that actually distinguish them, compared even-handedly:

| Criterion | ACP | AP2 | x402 |
|---|---|---|---|
| **From** | OpenAI & Stripe | Google | Coinbase → Linux Foundation |
| **Layer** | Checkout orchestration | Payment authorisation | Payment request (transport) |
| **Core job** | Complete an order inside chat | Prove a human authorised the payment | Ask for, and confirm, payment over HTTP |
| **Key artefact** | Delegated in-chat checkout | Signed Mandates (Intent, Cart, Payment) | The `402` challenge + proof-of-payment retry |
| **Settlement rail** | Via Stripe (cards) | Rail-agnostic (cards, bank, stablecoins via x402) | Rail-agnostic; mostly stablecoins today |
| **Announced / stewarded** | 2025, OpenAI + Stripe | September 2025, 60+ partners | x402 Foundation, Linux Foundation (14 Jul 2026) |
| **Best-fit scenario** | Consumer buys inside an assistant | Any agent payment needing provable authorisation | Machine-to-machine, sub-cent, high-frequency payments |

Sources: OpenAI/Stripe ACP materials; Google Cloud AP2 announcement (September 2025); x402 Foundation / Linux Foundation launch materials (July 2026). The pattern the table shows: the three answer different questions — *complete*, *authorise*, *request* — which is why they can stack rather than clash.

## Are they competitors or complements?

Mostly complements, because they occupy different layers of one stack. Placed in order, an agent purchase can move through all of them:

| Layer | Standard | What it decides |
|---|---|---|
| Discovery / being chosen | [Answer-engine optimisation](/glossary/answer-engine-optimization) | Whether an agent surfaces and picks your product |
| Checkout orchestration | [ACP](/blog/agentic-commerce-protocol-acp) | How the order is assembled and completed in chat |
| Payment authorisation | [AP2](/blog/what-is-ap2) | Whether the payment is provably human-authorised |
| Payment request | [x402](/blog/what-is-x402) | How the payment is asked for and confirmed |
| Settlement rail | [Cards or stablecoins](/blog/cards-vs-stablecoins-agent-payments) | How the money actually moves |

> The agent-payment standards are not three roads to the same place. They are three layers of one road — orchestration, authorisation, and request — and the real contest sits above all of them, at whether an agent chooses you at all.

There is genuine overlap at the edges — AP2 explicitly uses the x402 extension for the stablecoin path, and both AP2 and ACP can front a card rail — but that overlap is interoperability, not rivalry. As of mid-2026 no standard has absorbed the others, and the field is still forming.

## So which should a brand adopt?

For most brands, none of them is the thing to optimise for — and that is the point. These standards are settlement and authorisation plumbing; they move and validate money *after* an agent has decided to buy. Which product an agent surfaces and picks still turns on catalog richness, [entity strength](/blog/entity-strength-ai), reviews, and corroboration — the [answer-engine optimisation](/glossary/answer-engine-optimization) that decides whether you are in the answer at all.

The practical stance: make your [checkout ready](/blog/agentic-commerce-readiness) to accept however agents want to pay as these standards mature, keep an eye on which gain real adoption, and spend your actual effort a layer up — on being the product agents choose. Whether AI agents and answer engines surface and recommend your products is exactly what **Buffy Intel** measures, snapshot over snapshot. Questions: support@flash.tech.

## Agentic commerce for services: getting bookings, not just products, chosen by AI agents
Source: https://heybuffy.com/blog/agentic-commerce-for-services

**Agentic commerce is expanding from products to services — hotel stays, food orders, reservations and appointments an AI agent can complete for a shopper — and service businesses need to expose bookable availability, not just a catalog, to be chosen.** The clearest signal is Google's 2026 move to extend the [Universal Commerce Protocol (UCP)](/blog/what-is-ucp) beyond retail into hotel booking and food delivery. The readiness principle is the same as for products, but the object an [agent](/glossary/shopper-agent) transacts is a booking, and that changes what you need to publish.

**Last reviewed: 18 August 2026.** Platform specifics below — surfaces, partners, rollout — are dated to mid-2026 and will shift; the durable idea is that agent-driven transactions are moving from products to services, and the readiness work generalises.

## What does 'agentic commerce for services' mean?

It means an AI agent completing a *service* transaction — a reservation, an order, an appointment — on a shopper's behalf, the same way it now builds a product cart and checks out. In the product world, [agentic commerce](/glossary/agentic-commerce) means an agent discovers an item, adds it to a cart, and pays. For a service, the "add to cart" step becomes "hold this slot": a hotel night for specific dates, a table for a party size, a delivery order from a live menu, a booking for a named time.

The mechanics that made product checkout work — a shared way for an agent to discover, transact, and confirm across many merchants — are being pointed at services next. That is a bigger surface than retail: most local and hospitality businesses sell time and availability, not boxed goods, and until recently none of that was reachable by an agent.

## What changed — why services, and why now?

Because the agentic-commerce standards that launched around products started reaching into service verticals in 2026. At **Google Marketing Live 2026 (May 2026)**, Google said it was expanding UCP — its open standard for the agentic shopping journey — beyond retail into **hotel booking and food delivery**, describing a near-future where a shopper can *book a hotel directly from AI Mode* or *order food from a conversation inside Google Maps*. The same announcements extended UCP checkout into new surfaces (Shopping ads on YouTube, Direct Offers) and added buy-now-pay-later options inside Google Pay.

| Announced (Google Marketing Live 2026, May 2026) | What it signals for services |
|---|---|
| UCP expanding into **hotel booking** and **food delivery** | Bookings and orders join products as agent-completable transactions |
| Book a hotel from **AI Mode**; order food from **Google Maps** conversations | The transaction moves into the answer/assistant surface, not a separate site |
| UCP checkout into **YouTube Shopping ads, Direct Offers** | The buy step spreads across more surfaces a service can appear in |
| Rollout **U.S. first**, then Canada, Australia, U.K. | Geographic and vertical coverage is still filling in — dated, and moving |

Source: Google Marketing Live 2026 announcements, as reported mid-2026. These are volatile specifics from one platform — read the direction (agents transacting services, inside the answer) rather than any single partner or date. Other payment networks and platforms are building comparable agent-transaction support, so this is a category shift, not one company's feature.

## How is a bookable service different from a product for an agent?

The catalog groundwork rhymes, but the object an agent acts on is different — and that changes what you must expose. A product is largely static; a booking is a live, conditional claim on availability.

| Dimension | Product | Bookable service |
|---|---|---|
| Core unit | SKU with price | Slot: date, time, party size, or location |
| Availability | In stock / out of stock | Changes continuously by date and demand |
| Key facts an agent needs | Price, specs, shipping | Live availability, price *for those conditions*, lead time |
| Conditions | Returns policy | Cancellation, deposit, minimum stay, cut-off times |
| "Add to cart" equivalent | Reserve the item | Hold the slot before someone else takes it |

The through-line: an agent completing a booking needs **live, structured availability and the rules attached to it**, not just a headline price. A product feed answers "what is it and what does it cost." A service needs to answer "is it available for *these* conditions, at what price, and what happens if plans change" — in a form a machine can read and act on.

## What does a service business need to expose to be chosen?

The same readiness discipline as a [product catalog](/blog/prepare-product-catalog-for-ai-agents), pointed at availability. Whether or not a formal agentic-checkout integration has reached your vertical yet, the groundwork is stable:

1. **Clear, structured offer data.** What you offer, in specific terms — room types, menu items, appointment types — with [structured data](/glossary/structured-data) so a machine reads it without guessing.
2. **Prices tied to conditions.** Not one headline number, but the price for a date, a party size, a duration — the way the service is actually sold.
3. **Live or near-live availability.** The single hardest and most valuable input: an agent cannot book a slot it cannot see is open.
4. **The rules, stated plainly.** Cancellation, deposit, lead time, minimum stay, cut-off — the conditions a booking depends on, in crawlable text, not a PDF or an image.
5. **Crawlable, server-rendered pages.** If an AI agent cannot fetch your availability and terms, it cannot recommend or book you — the same reachability bar as every other agentic surface.

> Getting your store into a product cart was about a clean catalog; getting your service booked is about exposing live availability and the rules around it — the reservation, not just the price.

## How is this different from just ranking in AI Mode?

Ranking gets you *recommended*; booking-readiness gets you *transacted*. Winning AI-answer visibility for, say, travel queries — covered in [how to win Google AI Mode travel queries](/blog/optimize-for-ai-mode-travel) — is the discovery half: being named when someone asks an AI where to stay or eat. Agentic commerce for services is the transaction half: the agent then completing the booking without the shopper leaving the answer.

The two are a funnel, and both halves reward the same underlying work. This mirrors the product-side split we drew in [discover in AI, buy on your site](/blog/discover-in-ai-buy-on-your-site): you can be discovered inside an AI answer and still control where and how the transaction completes. For services, the discovery signal is your specific, structured content; the transaction signal is your live, machine-readable availability. Do the readiness work once and it pays into both — you are easier to recommend *and* easier to book.

---

Buffy Intel tracks whether AI engines surface and recommend your business when shoppers ask — for services and bookings, not just products — so you can see where you are being chosen and where an agent passes you by. To find out how visible your bookable offers are across AI answers, [start with Buffy Intel](https://heybuffy.com) or reach us at support@flash.tech.

## The payment rails behind agentic checkout: Visa, Mastercard, and tokenised agents
Source: https://heybuffy.com/blog/agentic-commerce-payment-rails

If [agentic commerce](/blog/what-is-agentic-commerce) is AI agents buying on a shopper's behalf, someone still has to move the money. Securely, and without handing a bot your card number. As of mid-2026, the card networks are answering that with **tokenised, scope-limited credentials**: a payment token bound to a specific agent, purpose, and spending limit, so an agent can pay without ever holding your real card details.

## Who actually moves the money in agentic checkout?

The payment networks do. The same Visa and Mastercard rails behind ordinary card payments, extended so an AI agent can be the one initiating the charge. According to reporting in June 2026 (AP and others), Visa embedded its payment network into ChatGPT, giving the assistant access to Visa's tokenisation and fraud infrastructure for agent-initiated purchases. The agent researches, compares, and triggers payment; the network clears it.

This is a distinct layer from the checkout *protocols*. Standards like the [Agentic Commerce Protocol (ACP)](/blog/agentic-commerce-protocol-acp) define the shared language for an agent and merchant to transact; the card networks provide the money movement underneath. A complete agentic purchase needs both.

## How do tokenised agent credentials work?

Tokenisation replaces your sensitive card data with a network token, but for agents, the token is also **scoped**. Per June 2026 reporting on Visa's approach, a token is bound to a specific agent and use case, with limits enforced at the network:

- A token issued for a **grocery** shopping agent cannot be used to book **travel**.
- A token carrying a **$200** limit cannot authorise a **$500** transaction.
- The agent transacts with the token; your real card number is never exposed to it.

The effect is least-privilege payments: the agent gets exactly enough authority to do the one job, and no more. That containment is what makes delegating a purchase to software tolerable in the first place.

## What did Visa and OpenAI announce?

Reporting in June 2026 described Visa embedding its payment network directly into ChatGPT, framed by Visa as part of "agentic commerce". AI systems that don't just suggest products but research items, compare prices, and help complete payment. Notably, the same reporting indicated that **at launch, Visa requires human approval for most transactions**: ChatGPT sends the shopper a notification to confirm each purchase before it completes. Treat the specifics as point-in-time; the launch posture and limits are early and will evolve.

> Tokenised agent credentials make the money safe to move. They don't make your product the one the agent decides to buy, that's still earned upstream.

## How is Mastercard's approach different?

Mastercard is building a parallel capability rather than ceding the lane. Its framework, reported as **Mastercard Agent Pay**, lets verified AI agents transact on a consumer's behalf using **Agentic Tokens**: described as an extension of the Mastercard Digital Enablement Service (MDES), the same tokenisation backbone behind its existing digital payments. Reporting in June 2026 placed more of Mastercard's early emphasis on business procurement use cases. The shared idea across both networks: a verified agent, a scoped token, and controls at the network layer.

| Network | Mechanism (as reported, mid-2026) | Early emphasis |
|---|---|---|
| **Visa** | Payment network embedded in ChatGPT; tokenised, scope-limited credentials; human approval for most transactions at launch | Consumer shopping inside the assistant |
| **Mastercard** | Agent Pay framework; Agentic Tokens extending MDES | Verified-agent transactions, incl. business procurement |

Names, scopes, and availability are moving quickly. The durable takeaway is the *pattern*, not any one product detail.

## Where payments sit vs. being chosen

Here's the distinction brands keep missing in the launch noise: the payment rail is **distribution and settlement, not selection**. It moves the money once an agent has already decided to buy your product. It does nothing to make your product the one the agent chooses.

That choice still turns on the layer above the rails. Catalog richness, [entity strength](/blog/entity-strength-ai), reviews, and how consistently other sources corroborate your claims. It's the same [answer-engine optimisation](/glossary/answer-engine-optimization) that decides whether you're surfaced at all. Wiring up a flawless agentic payment path for a product no agent recommends is a fast checkout to nowhere.

So treat the payments news as confirmation the transaction layer is real, and then spend your effort where selection is won. Knowing whether agents and answer engines actually surface and pick your products, as these rails mature, is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## The Agentic Commerce Protocol (ACP), explained
Source: https://heybuffy.com/blog/agentic-commerce-protocol-acp

If [agentic commerce](/blog/what-is-agentic-commerce) is the shift to agents buying on a shopper's behalf, the **Agentic Commerce Protocol (ACP)** is one of the first concrete pieces of plumbing making the "buying" part real.

## What ACP is

ACP is an open standard introduced by **OpenAI and Stripe** that lets an AI agent complete a **secure, delegated checkout inside a chat surface** like ChatGPT. In plain terms: a shopper can discover your product in the conversation and *buy it there*. Without being bounced to your site to start a fresh checkout.

It standardises the hand-off between the agent and the merchant. How product details, the cart, and payment are passed and authorised, so the agent can transact on the shopper's behalf within guardrails the shopper sets. Stripe handles the payment rails; the protocol defines the shared language.

## Why it matters for merchants

Checkout has always been where intent turns into revenue, and where friction kills it. ACP collapses the gap between "the AI recommended you" and "the shopper paid you" into one uninterrupted moment. The brands wired into it can capture a purchase at the point of recommendation; the ones that aren't watch the agent transact with a competitor who is.

> Being recommended by an AI is worth a lot less if the shopper then has to leave the chat, find your site, and re-start checkout. ACP is about closing that gap.

## It's not the only protocol

ACP is the most visible, but the standards layer is still forming, and it's worth knowing the neighbours:

| Protocol | From | What it does |
|---|---|---|
| **ACP** (Agentic Commerce Protocol) | OpenAI & Stripe | Lets an agent complete a delegated checkout inside a chat surface |
| **AP2** (Agent Payments Protocol) | Google | A standard for agent-initiated payments |
| **MCP** (Model Context Protocol) | Anthropic | Connects agents to tools and data; broader than commerce, but part of the same "let agents act" movement |

Specifics will keep shifting as these mature, so treat the names as a moving target. The durable takeaway is the *direction*: the industry is standardising how agents **transact**, not just how they answer.

## What it asks of you

You can't bolt ACP onto a thin catalog. Participating means your product data is **complete and structured** (clean attributes, specs, availability, price), your offers and policies are **machine-readable**, and your store meets the **checkout-readiness** bar the agent needs to transact confidently. That's the same groundwork that improves AI visibility generally, and it's the subject of the [next article](/blog/agentic-commerce-readiness).

## Is your catalog ready for agentic commerce?
Source: https://heybuffy.com/blog/agentic-commerce-readiness

An AI agent can only sell what it can **find, understand, and buy**. That's the whole readiness test, and it breaks cleanly into three questions. Fail any one and the chain snaps.

## 1. Discovery: can an agent find your products?

If the agent can't reach your product pages, nothing else matters.

- AI crawlers are **allowed** (in robots.txt *and* at your CDN. A CDN can silently block them, [as we've covered](/blog/is-your-cdn-blocking-ai-crawlers)).
- Products are in **server-rendered HTML and structured feeds**, not locked behind JavaScript an agent won't run.
- Your catalog is exposed where agents look. Clean URLs, a sitemap, and product feeds.

## 2. Completeness: is the data rich enough to show?

Agents don't see your hero imagery; they read **structured product data**. Thin data means your product can be *found* but not confidently *recommended*.

- **Product [schema](/glossary/structured-data)** (Product / Offer / availability / price) on every PDP.
- **Full attributes**: specs, materials, sizes, categories, identifiers, not just a marketing paragraph.
- **Accurate taxonomy** so the agent can place your product in the right category for a query.
- An **[llms.txt](/glossary/llms-txt)** and clean structure so the important facts are easy to extract.

This is where most catalogs fall down: a human shopper fills the gaps from the photos; an agent can't.

## 3. Checkout: can an agent actually transact?

The last mile: once recommended, can the purchase complete?

- Clear, machine-readable **offers and pricing**.
- Published **shipping, returns, and policy** information an agent can surface.
- A checkout the agent can use. Including support for emerging standards like the [Agentic Commerce Protocol](/blog/agentic-commerce-protocol-acp) where you want in on in-chat purchase.

## The order matters

Work the three in sequence. Protocol/checkout support is the headline, but it's the *last* step. Brands lose far more to invisible products and thin data than to missing checkout integration. The encouraging part: discovery and completeness are exactly the same investments that lift your ordinary [AI visibility](/glossary/ai-visibility-score) and [citations](/glossary/citation-coverage). You're not doing separate work for "AI search" and "agentic commerce". You're making your catalog legible to machines, which pays off on both.

Knowing which of the three is actually holding you back, and tracking it as the engines evolve. Is what an AI-readiness audit, and ongoing monitoring with **Buffy Intel**, are for.

## Why your product catalog needs a context-capture loop for agentic commerce
Source: https://heybuffy.com/blog/agentic-context-capture-loop

Static product catalogs are starting to lose to catalogs that learn. The durable idea behind agentic commerce readiness is shifting from "publish a complete, structured catalog once" to "treat the catalog as a system that continuously captures how shoppers and agents actually ask about your products, then feeds that back in." A 2026 framework calls this a context-capture loop, and even stripped of its more speculative claims, the core move is sound.

This builds on [getting your product catalog ready for AI agents](/blog/prepare-product-catalog-for-ai-agents), that piece is about the data layers; this one is about keeping them current through a feedback loop. The framework here comes from Retailgentic's 2026 [Agentic Commerce Optimization](/glossary/agentic-commerce) series (a single-author, single-vendor source), so the specifics are one practitioner's view. Attributed and hedged throughout.

## What is a context-capture loop?

It's a way of treating your catalog as a self-improving system instead of a static file. Rather than enriching product data once and moving on, you continuously capture the *context* in which shoppers and AI agents discover and compare your products, then loop that context back into the listings and republish. Retailgentic names this a "Recursive Compounding Context Capture Loop". The claimed payoff is that each cycle compounds, so the catalog gets steadily more complete and better-matched to real demand.

The five steps, as the source lays them out:

| Step | What happens |
|---|---|
| 1. Publish & measure | Ship the optimised catalog and measure how it performs |
| 2. Capture online context | Continuously gather context from answer engines, your site, and social |
| 3. Capture offline context | Less frequently, gather it from stores and manufacturers |
| 4. Evaluate & prepare | Assess what improved and prepare an updated catalog version |
| 5. Republish & repeat | Republish and repeat the cycle, at increasing velocity |

The analogy the source draws is to how AI systems improve through feedback. It borrows the term **RLAIF (Reinforcement Learning with AI Feedback)**, where AI-generated signals, rather than slow human review, drive each iteration. Read that as a metaphor for tightening your update cadence, not a literal claim that your catalog trains a model.

## Where should you capture product context from?

From the places shoppers and agents actually form opinions about your products. Retailgentic's framework lists six sources and advises ranking them for your business, then starting with the top two:

| Source | What it reveals |
|---|---|
| Answer engines (Google, ChatGPT, Claude) | The queries and comparisons buyers bring to AI |
| Retail agents (e.g. Amazon's Rufus, Walmart's Sparky) | Shopper prompts and the features agents surface |
| Physical stores | Sales-floor knowledge and the questions associates field |
| Brands / manufacturers | Complete technical specs and design detail |
| Social media | Creator and community mentions of the product |
| Website behaviour | On-site search, reviews, and agent interactions |

For most online sellers the top two are answer engines and retail agents, because that's where AI-mediated discovery now happens. The practical version of "capturing context" from them is the work this corpus already covers: mine the [query fan-out](/glossary/query-fan-out) to see the sub-questions buyers ask, and watch which product attributes agents demand. The point is not to instrument all six at once. It's to pick the two that move your category and feed what you learn back into the catalog.

## Why does a loop beat a one-time catalog optimisation?

Because agentic discovery shifts faster than an annual catalog refresh can keep up with. New real-world events create new agent queries overnight, and an attribute that wasn't worth stating last quarter can become the deciding filter this one. The same dynamic behind [products going invisible when demand spikes](/blog/event-driven-product-visibility). A catalog updated once a year is structurally behind; a catalog on a tight feedback loop catches the drift.

> A static catalog answers the questions you anticipated. A looping catalog answers the questions shoppers are actually asking this week, and closes the gap a little more each cycle.

This is the agentic-commerce sibling of a measurement idea already in the corpus: [turning query fan-out data into citations](/blog/query-fan-out-content-loop) is the same publish → measure → refine rhythm, applied to content rather than product data. The signals that decide whether an agent picks you are the [six factors that make AI recommend a product](/blog/factors-ai-recommends-products). The loop is how you keep improving against them. And it rhymes with the [freshness citation cliff](/blog/content-freshness-citation-cliff): live retrieval favours recently-updated sources, so a catalog that visibly keeps current is more likely to be chosen than one that looks frozen.

## How should you read the framework's predictions?

As a directional bet, not a deadline. Retailgentic predicts forward-leaning retailers experimenting with these loops through the 2026 holiday season, the practice becoming standard for senior commerce leaders by the end of 2027, and "significant digital retail disruption" over the following 18 months as faster loops compound into advantage. That's a plausible trajectory from a single source. Credible as a direction, unproven as a timeline.

The honest, low-risk takeaway doesn't depend on the predictions being right. You don't need a fully automated loop to capture most of the value:

- **Read real queries.** Look at how answer engines and retail agents actually describe and compare your products.
- **Fix the gaps.** Where the catalog is silent or guessed-at, state the attribute explicitly. The controlled-vs-inferred distinction from [Shopify's agentic storefronts](/blog/shopify-agentic-storefronts).
- **Refresh on a cadence.** Make updates substantive and visible, not date-bumps.
- **Start with two sources, not six.** Pick the inputs that move your category and instrument those first.

Treat the loop as a discipline, not a product you have to buy. Knowing whether AI agents and answer engines actually surface and pick your products after each refresh. The "measure" step that makes the loop a loop. Is exactly what **Buffy Intel** tracks. Questions: support@flash.tech.

## Do a few domains dominate AI citations? Reconciling the studies
Source: https://heybuffy.com/blog/ai-citation-domain-concentration

**AI citations concentrate on a relatively small set of domains, and the exact percentages you'll read are all over the map.** Both statements are true, and reconciling them is the point of this piece. The concentration is well corroborated: a handful of community and reference sites recur near the top of most engines. The wildly different headline numbers you see quoted are mostly an artefact of studies measuring different things. Different engines, denominators, dates, and methods. Trust the pattern; distrust any single percentage until you know how it was cut.

This is a reconciliation, not a new dataset. It sits alongside our [AI search statistics reference](/blog/ai-search-statistics-2026) and exists to stop a real hazard: pasting one study's number next to another's when the two aren't measuring the same thing. Every figure below is attributed, dated, and hedged.

## Do AI citations really concentrate on a few domains?

Yes. The concentration is one of the more robust findings in AI-search research. The clearest quantified cut comes from Profound's "AI Platform Citation Patterns" analysis (Nick Lafferty, published June 2025), covering roughly **680 million citations** across ChatGPT, Google AI Overviews, and Perplexity from **August 2024 to June 2025**:

| Finding | Figure | Source (period) |
|---|---|---|
| Share of all citations from `.com` domains | ~80.41% | Profound (Aug 2024-Jun 2025) |
| Share of all citations from `.org` domains | ~11.29% | Profound (Aug 2024-Jun 2025) |
| Wikipedia's share of ChatGPT's **top-10** sources | ~47.9% | Profound (Aug 2024-Jun 2025) |
| Reddit's share of Perplexity's **top-10** sources | ~46.7% | Profound (Aug 2024-Jun 2025) |
| Reddit reported as the **#1 source** across major engines | widely reported | multiple 2026 analyses |

Two TLDs account for over 90% of citations, and within each engine a single source often owns nearly half of the top-10 slots. Profound's own framing is that the concentration is "more extreme than Google PageRank ever produced." Read as a single word, the finding is: **concentrated.** All figures are vendor-reported and directional.

## Why do the studies report such different numbers?

Because the denominator, engine, date, and method are rarely the same, and each changes the number more than the underlying reality does. The cleanest example is Wikipedia inside ChatGPT, where you can find "13%" and "48%" quoted for what sounds like the same thing:

| What's being measured | Wikipedia figure | Source (date) |
|---|---|---|
| Wikipedia's share of **all** US ChatGPT citations | ~13.15% | 5W Research (June 2026) |
| Wikipedia's share of ChatGPT's **top-10** sources | ~47.9% | Profound (Aug 2024-Jun 2025) |
| Wikipedia's share of **all** ChatGPT citations | ~7.8% | Profound (Aug 2024-Jun 2025) |

These do not contradict each other. The ~48% is a share of a **top-10 subset**; the ~13% and ~7.8% are shares of **all** citations, measured by different vendors over different windows. A "share of the top 10" will always dwarf a "share of everything," and a figure from mid-2025 will differ from one a year later. Put a percentage next to another only when the **denominator, engine, and date match**: otherwise you are comparing a fraction of a shortlist with a fraction of the whole web. This is exactly the kind of [answer volatility](/glossary/answer-volatility) that makes single snapshots misleading.

## How much do the engines overlap with each other?

Barely, and this is the finding that stays stable even as the percentages move. Being cited on one engine tells you little about another. The figures already in our stats reference, from Profound's "State of AI Search" (Zero Click conference, June 2026):

- **Claude ↔ ChatGPT** domain overlap: ~8%
- **Claude ↔ Google** domain overlap: ~64%
- Widely reported alongside these: **ChatGPT ↔ Perplexity** overlap in the low tens of percent. Most domains cited by one are not cited by the other.

Even *within* one company the surfaces diverge. Google AI Mode and AI Overviews share about **59% of their top-100 sources** (BrightEdge, April 2026), yet measured as *exact matching URLs* rather than shared domains in a top-100 set, reported overlap falls to the low double digits. Same two surfaces, very different numbers, because one counts shared domains and the other counts identical pages. We unpack that pair in [do AI Mode and AI Overviews cite the same sources](/blog/ai-mode-vs-ai-overviews-citations). The lesson generalises: **the metric definition drives the number.**

## Do the engines even cite brands at the same rate?

No, and this is a *different* metric again, easy to confuse with domain concentration. "How often does an engine cite any brand at all?" is not "which domains does it cite." One 2026 analysis of **34,234 AI responses** (Leapd, April 2026) reported brand-citation rates roughly **46× apart** between engines:

| Engine | Reported brand-citation rate | Source (date) |
|---|---|---|
| ChatGPT | ~0.59% | Leapd (Apr 2026) |
| Perplexity | ~13.05% | Leapd (Apr 2026) |
| Grok | ~27% | Leapd (Apr 2026) |

A separate analysis (Ranketai, April 2026) put ChatGPT at ~0.7% and Perplexity at ~13.8%. Different absolute numbers, same enormous gap. The corroborated read across both: ChatGPT mentions brands in prose but **cites** them sparingly, while Perplexity cites densely against a short, high-authority shortlist. This is brand-citation *frequency*, not source concentration. Keep the two metrics apart when you quote them.

> The robust finding across every study is the same shape: citations concentrate on few sources, community content ranks high, engines barely overlap, and the numbers swing by method and month. The specific percentage is the least durable thing in the dataset.

## What should you actually do with these numbers?

Use them as directional context, and measure your own reality. Concretely:

- **Always check the cut before you quote.** Ask which engine, what denominator (all citations vs a top-N subset), and which date. A number without those three is not comparable to anything.
- **Design for the durable pattern, not the point estimate.** Concentration and low cross-engine overlap are stable; the exact shares are not. Build [entity strength](/blog/entity-strength-ai) that travels across engines and earn presence on the community sources that recur near the top. The case for taking [Reddit visibility](/blog/how-to-use-reddit-for-ai-search-visibility) seriously rests on this.
- **Don't let one engine's number stand in for all.** With overlap as low as ~8%, a strong showing in ChatGPT says almost nothing about Perplexity. Measure each separately.
- **Refresh, because the numbers decay.** Citation shares move month to month, so any figure. Including these. Ages fast. That's the same [freshness discipline](/blog/content-freshness-citation-cliff) any competitive reference needs.
- **Treat your own [citation coverage](/glossary/citation-coverage) as the only number that matters.** Whether *your* brand is cited, on *which* engine, trending *which* way, beats every industry average.

The published studies agree on the shape and disagree on the digits, which is exactly why the metric worth watching is your own, tracked per engine over time. That per-engine [citation](/glossary/citation) measurement, and how it moves, is what **Buffy Intel** is built to provide. Questions: support@flash.tech.

## Does every industry get cited differently by AI? The citation-fingerprint data
Source: https://heybuffy.com/blog/ai-citation-fingerprint-by-industry

Each industry gets cited differently by AI engines, and the winning page type is not the same across verticals. In a study published 13 July 2026 by Brandon Kidd of DeltaV Digital, covering **25,337 citations** across ChatGPT, Perplexity, Gemini, Google AI Overviews, and Google AI Mode, listicles captured about **61% of citations in B2B technology services**, homepages about **55% for a local medical-aesthetics brand**, and program pages about **53% in higher education**. The same engines, over the same 90 days, cited a completely different mix of page types depending on the category being asked about.

That pattern has a name in the report: a **[citation fingerprint](/glossary/citation-fingerprint)** — the specific blend of page types an engine relies on when answering questions in a given vertical. This piece lays out the data, attributed and hedged, then explains why a generic "publish listicles and FAQs" checklist under-serves most brands. The companion [how-to on matching your industry's fingerprint](/blog/match-your-industry-citation-fingerprint) turns it into a workflow.

## What is a citation fingerprint?

A citation fingerprint is the distinctive mix of page types AI engines cite when they answer questions in one industry. It is a per-vertical pattern, not a per-engine one: it describes *what kind of page* wins the citation (a listicle, a homepage, a product page, a program page), rather than which engine does the citing.

The DeltaV study measured it two ways: **citation share** (what percentage of an industry's total citations each page type earned) and **citation rate** (citations per retrieval, i.e. how often a fetched page was actually kept). The headline finding is that these blends diverge sharply between industries — so the "right" content format is a property of your category, not a universal rule.

## Which page types get cited most overall?

Across all eight brands combined, three formats carried more than half of citations. The portfolio baseline, per the DeltaV data:

| Page type | Citation share (all industries) | Citation rate (cites per retrieval) |
|---|---|---|
| Articles | 23.7% | 1.43 |
| Listicles | 19.6% | 1.45 |
| Product pages | 16.3% | 1.22 |
| Comparison pages | 4.1% | **1.87** (highest) |

Source: Brandon Kidd, DeltaV Digital, "AI search citations study" (25,337 citations, 21,075 AI responses, 14 Apr–13 Jul 2026). Comparison pages were a small share of citations but the most *efficient* format — when one was retrieved, it was the most likely to be kept and cited. This corroborates the corpus view that [neutral comparison content earns trust](/blog/get-into-ai-cited-best-lists) and that [listicles are a heavily-cited format](/blog/why-ai-loves-listicles) — but, as the next section shows, the averages hide most of the story.

## How much does the cited page type change by industry?

A lot. This is the core finding. The dominant page type flips from vertical to vertical:

| Industry | Dominant cited page type(s) | Share |
|---|---|---|
| B2B technology services | Listicles | 61% |
| Consumer automotive | Articles + listicles | 64% combined |
| Medical aesthetics (local) | Homepages | 55% |
| Healthcare | Articles | 54% |
| Specialty food CPG | Listicles + homepages | 54% combined |
| Higher education | Program pages | 53% |
| B2B cybersecurity | Articles + how-to guides | 51% combined |

Source: DeltaV Digital, July 2026. The reading: a B2B software brand lives or dies by earning placement in third-party listicles, while a local medical-aesthetics practice is cited mostly through its own homepage, and a university through its program pages. Publishing a pile of listicles would do little for the local practice or the university. **The same engines, the same 90 days, and three different answers to "what should we publish?"**

## Can your own website win the citation, or must it be earned?

This is the second under-discussed cut, and it is the one that decides your content budget. The DeltaV study reported each industry's **own-domain citation share** — how much of its cited content came from the brand's own site versus third-party sources:

| Industry | Own-domain citation share |
|---|---|
| Higher education | 74.7% |
| Specialty food CPG | 18.9% |
| Government scholarship | 11.5% |
| Healthcare nonprofit | 8.3% |
| B2B cybersecurity | 8.2% |
| Consumer automotive | 7.4% |
| Medical aesthetics | 3.0% |
| B2B technology services | **0.0%** |

Source: DeltaV Digital, July 2026. In higher education, the brand *was* the citation — three-quarters of the answers pulled from its own domain. In B2B technology services, none of it did: every cited source was a third-party listicle, review site, or directory. That maps cleanly onto the [owned-versus-earned distinction](/blog/get-into-ai-cited-best-lists): some verticals reward publishing your own authoritative pages, and others force you to [earn placement in independent lists](/blog/how-to-get-cited-by-ai) because engines will not cite your site directly for those queries.

One consistent thread across all eight brands: **Reddit appeared among the top-cited domains for seven of them**, and LinkedIn was the single most-cited domain for the B2B technology-services brand (736 citations). That matches the corpus finding that [Reddit's AI citations are real but concentrated on specific surfaces](/blog/does-reddit-get-you-cited-by-ai), and reinforces that user-generated and professional-network content sits in most industries' fingerprints whether or not a brand cultivates it.

## How does this square with "listicles get cited" and other corpus findings?

It sharpens those findings rather than reversing them. Three reconciliations:

- **Listicles still matter — but not universally.** [Why AI loves listicles](/blog/why-ai-loves-listicles) holds on the average and in list-heavy verticals like B2B tech. The fingerprint data adds the caveat: in local services, healthcare, and higher education, other formats win, so "publish listicles" is category-dependent advice.
- **This is a different axis from content edits.** The [Princeton GEO experiments](/blog/what-content-changes-lift-ai-citations) tested *what changes to a page* lift citations (adding statistics, quotes, sources). The fingerprint data tests *which page type* gets cited in a vertical. You need both: the right format, then the evidence density inside it.
- **This is page-type concentration, not domain concentration.** It is distinct from [how few domains AI engines concentrate citations on](/blog/ai-citation-domain-concentration) and from per-vertical *brand* concentration. Fingerprints describe formats; those describe which sites and brands recur. Keep the two separate when you plan.

## What are the caveats on this data?

Several, and they are load-bearing:

- **Eight brands, one per vertical.** Each "industry fingerprint" is essentially a single brand's citation profile. Read the per-industry percentages as illustrations of *how much variance exists between categories*, not as audited benchmarks for the whole industry.
- **Single-vendor, single-window.** The data comes from one measurement pipeline over one 90-day window (Apr–Jul 2026). Engines change their retrieval behaviour, so treat the numbers as a dated snapshot and cite "DeltaV Digital, July 2026" with the date when you reuse a figure.
- **Citation share is not causation.** A format winning citations in a vertical does not prove that publishing more of it will earn you citations — the engines may be citing incumbents. Use the fingerprint to prioritise where to look, then measure your own results.

None of these undo the durable, corroborated point: **the page types AI engines cite differ enough between industries that a one-size-fits-all content checklist is the wrong starting point.**

> Every industry has a distinct AI citation fingerprint. Copy the fingerprint of your category, not a generic best-practices checklist — the format that wins B2B software citations is not the one that wins for a local clinic or a university.

## What should you actually do about it?

Work from your category's fingerprint outward:

1. **Find which page types get cited for your category's questions.** Look at the actual AI answers for your buyers' queries and note the format of each cited source, per the [companion how-to](/blog/match-your-industry-citation-fingerprint).
2. **Check your own-domain share.** If engines rarely cite sites like yours for your queries, prioritise [earned placement in independent lists](/blog/get-into-ai-cited-best-lists); if they cite owned pages (as in higher ed), invest in your own [extractable, well-structured pages](/blog/prioritize-your-structured-data).
3. **Match the format, then raise the evidence density inside it.** Once you know the winning page type, apply the [content edits that lift citations](/blog/what-content-changes-lift-ai-citations) within it.
4. **Track it as a trend, per engine.** Fingerprints shift as engines change, so watch your [citation coverage](/glossary/citation-coverage) and [share of voice](/glossary/share-of-voice) over time rather than acting on one snapshot.

The through-line is measurement: knowing which page types and sources AI engines cite for *your* category — and whether that includes your own domain — is exactly what **Buffy Intel** is built to show, engine by engine and snapshot over snapshot, so you can spend on the format your vertical actually rewards instead of a generic checklist.

## Where does AI crawl, and where does it actually send visitors?
Source: https://heybuffy.com/blog/ai-crawl-vs-referral-traffic

**AI crawls almost everything on your site, but sends visitors to almost none of it.** A mid-2026 analysis of more than 560,000 AI crawl requests across 74 websites found homepages get roughly 15 times the crawl attention of other pages, articles get read heavily but rarely clicked, and 47% of all pages earned zero referral visits at all. The headline for marketers: crawl volume tells you AI can *reach* your pages; it says almost nothing about which pages AI will *send people to*. Those are two different maps, and they barely overlap.

This is a data explainer, not a new dataset. It sits alongside our [AI search statistics reference](/blog/ai-search-statistics-2026). The figures come from Orbit Media's study by Andy Crestodina, published early July 2026, built on **Cloudflare AI Crawl Control** exports (the "Most Crawled Paths" and "AI Referral Traffic" reports) covering **560,695 crawl requests** and **446,267 referrals** across **74 sites** (27 of them on paid tiers with referral tracking) and **21,212 URL paths**. Every figure below is attributed, dated, and hedged: it is one vendor's dataset, skewed toward B2B and services sites, so read the patterns as directional.

## Which pages does AI crawl the most?

Homepages, overwhelmingly. Adjusted for site size. A homepage is one page competing with dozens or hundreds of others. Homepages drew about **15x** the AI crawl attention of any other page type. Nothing else came close; every other category clustered below its proportional share.

| Page type | Relative AI crawl attention (1.0 = proportional) |
|---|---|
| Homepage | ~15x |
| Service / product | 0.85x |
| Articles / resources | 0.82x |
| About | 0.80x |
| Contact | 0.77x |
| Pricing | 0.68x |
| Case studies | 0.56x |
| Docs (PDFs) | 0.56x |

Source: Orbit Media / Cloudflare AI Crawl Control, 74 sites, mid-2026 (median crawl intensity, normalised for site size; single-vendor, directional). The clear read: if you want AI to learn one thing about your brand, the homepage is where it looks first, which is why the homepage now does [a discovery job it didn't a year ago](/blog/optimize-your-homepage-for-ai-referrals).

Site size mattered too. Page count alone predicted total crawl volume almost perfectly. A **0.86 correlation, explaining about 73%** of the variation in total AI requests. More pages meant more surface area to match against more prompts. But it wasn't destiny: some small sites drew far more attention than their size predicted, likely from stronger brands and better-optimised pages.

## Why do crawled pages not turn into visits?

Because reading a page and recommending a click are separate decisions. This is the study's most important finding, and Orbit Media gave it a name: the **Dark Library Effect**: pages AI reads heavily and summarises, but rarely sends a visitor to. Articles are the clearest case. They get crawled and cited, then the answer satisfies the user in place, and no click follows. It's the same [zero-click](/glossary/zero-click-search) dynamic that reshaped classic search, now applied to AI.

Comparing each page type's share of referrals against its share of crawls exposes the gap directly:

| Page type | Referral share minus crawl share (points) |
|---|---|
| Homepage | +10.4 |
| Service / product | +2.2 |
| About | −0.1 |
| Contact | −0.8 |
| Docs (PDFs) | −2.6 |
| Articles / resources | −8.7 |

Source: Orbit Media / Cloudflare, 27 sites with referral tracking, mid-2026 (directional). A positive number means a page type sends *more* traffic than its crawl volume predicts; a negative number means it's read more than it's clicked. Homepages and service pages over-deliver on traffic; articles under-deliver by the widest margin. Service and product pages earned roughly **three times more AI-referral traffic per page** than a typical article. Even though the typical site in the study had more articles than service pages.

> The Dark Library Effect: AI reads your articles far more than it sends anyone to them. In this dataset, 47% of all pages earned zero referral visits. Crawled, summarised, and never clicked.

This is not an argument to stop publishing. It's the same lesson our [freshness and citation](/glossary/content-decay) work keeps surfacing: content that gets crawled and cited builds the model's knowledge of your brand even when it drives no click. Crestodina's own conclusion is that content marketing stays valuable without referral traffic. It trains AI, earns citations, and supports the sale in ways a click counter never sees. The mistake is applying click-through goals to pages that were never going to win the click. That's also why heavy crawling with few citations is [a leading indicator, not a failure](/blog/chatgpt-citation-lag): the crawl comes first.

## Does page depth change how much traffic AI sends?

Sharply. AI crawlers will find pages buried deep in a folder structure. Crawl budget stretches far, but they rarely *recommend* them. Orbit Media called this an "architecture tax," and the drop-off with depth is steep.

| Folder depth | AI-referral intensity (1.0 = proportional) |
|---|---|
| One level deep (`/services/`) | 0.91 |
| Two levels (`/services/seo/`) | 0.68 |
| Three levels (`/services/seo/local/`) | 0.25 |
| Four or more levels | 0.05 |

Source: Orbit Media / Cloudflare, mid-2026 (median referral intensity by depth; directional). A page three folders deep earned about a quarter of the traffic its footprint predicted; at four levels, close to zero. The study is careful, and so are we, that this is **correlation, not causation**: moving a page shallower won't automatically win it traffic, and you shouldn't reshuffle your whole site over one dataset. But if you're planning a new structure, keeping your most important pages within a click or two of the homepage is a defensible default.

## What should marketers actually do with this?

Treat crawl and referral as two separate measurements, and match the page to the job. AI visits a site for two different reasons. To fill in background knowledge (training crawlers) and to answer a live question (search-agent crawlers), and neither guarantees a click. Practical moves from the data:

- **Make the homepage a real briefing.** It gets the most crawl attention and over-delivers on traffic, so state plainly who you are, what you do, and your differentiators in [extractable text](/blog/make-your-website-agent-readable), not a slogan over a hero image.
- **Invest in service and product pages** if you want AI referrals that may convert; they earn far more traffic per page than articles.
- **Keep publishing articles, but judge them right.** Expect citations and brand-training value, not direct clicks. Measure [citations, not just referral clicks](/blog/from-clicks-to-citations).
- **Don't bury your best pages.** Deep pages get crawled but rarely recommended.
- **Remember AI traffic hides.** Much of it lands in analytics as [direct traffic](/glossary/dark-traffic), so the referral counts you see understate the real total, and [AI visitors often convert better](/blog/is-ai-traffic-more-valuable) than the raw numbers suggest.

The deeper point is that "we get crawled a lot" and "AI recommends us" are different claims that need different evidence. Watching where AI actually crawls, cites, and sends visitors across engines, and separating the [Dark Library Effect](/glossary/dark-library-effect) from real recommendation. Is exactly what **Buffy Intel** is built to measure. Questions: support@flash.tech.

## Is AI crawling about to be blocked by default? Cloudflare's September 2026 change
Source: https://heybuffy.com/blog/ai-crawler-default-block-2026

**AI crawling is not being switched off across the web, but its default is changing.** From **15 September 2026**, Cloudflare will start blocking **AI training and AI-agent crawlers by default on any page that carries advertising**, while leaving classic **search crawlers allowed**. The change applies to new customers, new sites from existing customers, and free-tier users who have not set their own rules. Alongside it, Cloudflare is shifting how it charges AI companies, from **pay-per-crawl** to **pay-per-answer**.

This piece explains what actually changes on that date, who it reaches, and what a brand that wants to be [cited](/glossary/citation) in AI answers should watch for. The facts are attributed to Cloudflare's July 2026 announcements and corroborating reporting, and dated to mid-2026, because default policies and billing models are still moving.

## What is Cloudflare changing on 15 September 2026?

Cloudflare is flipping the default posture for AI crawlers on ad-supported pages. Under the new defaults, a search crawler that indexes your pages is still welcome, while a crawler fetching content to train a model or to power an AI agent is blocked unless the site owner opts in.

| Crawler class | Default on ad pages (from 15 Sep 2026) | Example jobs |
|---|---|---|
| Search indexing | **Allowed** | Classic search results; feeds AI Overviews / AI Mode |
| AI training | **Blocked** | Gathering content to train future models |
| AI agent | **Blocked** | Fetching pages to complete a user's task live |
| Mixed-use (blends the three) | **Blocked** unless the owner opts in and the bot lets users separate the functions | One user-agent doing several jobs |

Who it applies to, in Cloudflare's own framing: **new customers, new sites added by existing customers, and every free user who has not changed their settings**. Existing paid sites with their own bot rules are not converted automatically. Source: Cloudflare's 1 July 2026 announcement and reporting by TechCrunch and PPC Land (single-operator policy; details may change before the date).

## What is a "mixed-use" crawler, and why does it matter?

A [mixed-use crawler](/glossary/mixed-use-crawler) is one that blends several jobs — search indexing, model training, and AI-agent fetching — behind a single [user-agent](/blog/ai-crawler-user-agent-directory). It matters because Cloudflare's new default keys off *purpose*: search is allowed, training and agent use are not. A bot that does all three at once cannot be cleanly allowed for one job without allowing the others, so under the September defaults it is blocked on ad pages unless the operator lets site owners separate the functions.

This is the same knot the corpus has flagged before: a single token like `Googlebot` can span indexing, training-adjacent, and AI-answer use, which is why "just block the AI bots" is rarely clean. The September change turns that ambiguity into a default: when a crawler's purpose is unclear or mixed, the safe default becomes *deny* on the pages a publisher monetises.

## What is "pay per use," and how is it different from pay per crawl?

Pay-per-use charges an AI company when its content is **actually used to answer a question**, not each time a crawler fetches a page. Cloudflare described this shift on 1 July 2026, evolving its earlier [pay-per-crawl](/blog/can-you-charge-ai-agents-to-crawl) model, which billed per fetch using the HTTP `402 Payment Required` status.

The rationale is a waste statistic: Cloudflare says **more than half of the crawl traffic from bots it classifies as legitimate re-fetches pages that have not changed** since the last visit. Charging per crawl therefore prices re-fetching, not value. Pay-per-use ties payment to the answer the content helped produce. Early partners named for this model include Ceramic.ai (publishers paid when their content appears in its search results) and You.com (agents buy premium content on demand).

| Model | What triggers payment | Status (mid-2026) |
|---|---|---|
| Pay Per Crawl (2025) | Each crawler fetch (HTTP `402`) | Live, being superseded |
| Pay Per Use / pay-per-answer | Content used to answer a query | Announced Jul 2026; early partners |

Source: Cloudflare, July 2026, corroborated across TechCrunch and PPC Land. This sits on top of the same settlement plumbing — the [x402](/blog/what-is-x402) payment standard and Cloudflare's Monetization Gateway — covered in our [pay-per-crawl explainer](/blog/can-you-charge-ai-agents-to-crawl); pay-per-use is the pricing evolution, not a different pipe.

## Why single out ad pages?

Because an ad is treated as a signal that the page was built for a human to land on. Cloudflare's reasoning is that content earning ad revenue is where the [crawl-to-refer imbalance](/glossary/crawl-to-refer-ratio) bites hardest: the same crawl often feeds a model that then answers the user directly, so the visit — and the ad revenue — never arrives. Making ad pages opt-in for training and agent bots is meant to protect that revenue while keeping search discovery intact.

That imbalance is well documented. Pure-AI crawlers fetch [thousands of pages for every visitor they refer](/blog/how-many-pages-ai-crawlers-take-per-visitor), and a [robots.txt disallow is only a request](/blog/how-often-do-ai-crawlers-ignore-robots-txt) that a rising share of bots ignore. A CDN-level default enforced at the edge is a harder wall than a text file — which is exactly why the default flipping matters more than a robots.txt line.

## Does this block you out of AI answers?

Mostly not — but it can, quietly, on your monetised pages. The default only touches ad-bearing pages, only under the new-defaults subset, and it **leaves search crawlers allowed**, so the pipeline into Google's AI Overviews and AI Mode is unaffected. The risk is narrower and easier to miss: if your ad-supported pages are silently closed to live-retrieval and agent bots, you can forfeit citations and agent visibility on precisely those pages, the same failure mode as an [accidental CDN block](/blog/is-your-cdn-blocking-ai-crawlers), now arriving as a default rather than a mistake.

> The default is flipping from "let AI read everything" to "let search in, make AI training and agents ask." For a brand that wants citations, the danger isn't the block itself — it's inheriting a default you never chose.

The decision is still yours to make per crawler class, exactly as our guide to [allowing vs. blocking AI crawlers](/blog/should-you-let-ai-crawlers-index-your-site) lays out. What has changed is that doing nothing no longer means "open by default" everywhere.

## What should brands do about it?

Two moves. First, find out whether you are in the affected subset and what your CDN is actually allowing after the date — see our step-by-step on [keeping AI crawlers reaching your site](/blog/keep-ai-crawlers-reaching-your-site). Second, decide deliberately: keep live-retrieval and agent bots welcome on the pages whose job is to be discovered and cited, and reserve blocking or metering for content that is genuinely a product.

Whether AI engines and agents can still reach, cite, and recommend your pages after a default like this changes underneath you is exactly what **Buffy Intel** measures, snapshot over snapshot. Questions: support@flash.tech.

## The AI crawler lifecycle: train, index, and answer
Source: https://heybuffy.com/blog/ai-crawler-lifecycle

When people picture an "AI crawler," they imagine one bot hoovering up the web. The reality is more useful to know: a single lab usually runs **several** bots, each doing a different job. Sort them by job and a lot of confusing `robots.txt` decisions become obvious.

There are three jobs.

## 1. Train: baking content into the model

Training crawlers gather content that may be used to train future models. Once something is in the training corpus it's effectively permanent and uncompensated, which is why publishers who monetize content most want to block these.

- **Who:** `GPTBot` (OpenAI), `ClaudeBot` (Anthropic), `Google-Extended` (Gemini training), `Applebot-Extended`.
- **Behaviour:** broad and periodic. They crawl widely, not in response to any single user.
- **What blocking does:** the next generation of models learns *less* about you.

## 2. Index: building the live search index

Search/indexing crawlers build a searchable index the AI queries *at conversation time* ([retrieval-augmented generation](/glossary/retrieval-augmented-generation)). Your content gets retrieved and **cited live**, but isn't used to train the model.

- **Who:** `OAI-SearchBot` (OpenAI), `Claude-SearchBot` (Anthropic), `PerplexityBot`.
- **What blocking does:** you disappear from AI **search** answers. Usually the last thing a brand wants.

## 3. Answer: fetching a page on demand

Inference (or user-triggered) fetchers grab one specific page in real time because a user asked, for example, when someone pastes your URL into a chat and says "summarise this."

- **Who:** `ChatGPT-User` (OpenAI), `Claude-User` (Anthropic).
- **What blocking does:** breaks the "summarise this link" experience for your own visitors.

Anthropic's three bots map cleanly onto this. `ClaudeBot` = train, `Claude-SearchBot` = index, `Claude-User` = answer, and OpenAI mirrors it with `GPTBot` / `OAI-SearchBot` / `ChatGPT-User`.

## The odd one out: Common Crawl

`CCBot` doesn't fit any of the three boxes. Common Crawl is a non-profit that crawls the web into a giant **public archive**: it trains no models itself. The catch: that archive is one of the most widely used *inputs* for training models across many labs.

> Blocking GPTBot and ClaudeBot does **not** stop your content reaching those same labs through the Common Crawl dataset. To close that back-door you have to block `CCBot` separately.

## So what should you allow?

It depends on your goal, and the decision is per-bot, not a single "AI: on/off" switch:

- **Want maximum AI visibility?** Allow the **index** and **answer** bots without question. They're what get you cited and make link-sharing work. Most brands allow **training** bots too, because being learned by the models means they recognise your brand later.
- **Protecting proprietary or monetised content?** Block the **training** bots (and `CCBot`), but think hard before blocking index/answer bots, that's where live citations come from.

Two caveats worth remembering. First, this is all enforced by **user-agent**, so a site can be visible to one lab and invisible to another purely as a `robots.txt` artifact (see [Should you let AI crawlers index your site?](/blog/should-you-let-ai-crawlers-index-your-site)). Second, allowing a bot in `robots.txt` isn't enough if your CDN blocks it at the edge first ([your CDN might be doing exactly that](/blog/is-your-cdn-blocking-ai-crawlers)).

Knowing which bot does what is the difference between a deliberate AI strategy and accidentally locking the door on the engines you most want to reach, which is exactly the kind of gap **Buffy Intel** is built to surface.

## Which AI crawlers hit your site most? (mid-2026 share data)
Source: https://heybuffy.com/blog/ai-crawler-market-share-2026

**As of mid-2026, AI crawlers make up about 22% of all bot traffic. Googlebot still leads the crawler leaderboard; Anthropic's ClaudeBot holds the #2 spot among purpose-built AI crawlers after its June surge cooled, and Anthropic's combined footprint (ClaudeBot + Claude-SearchBot, ~19.8%) now trails only Googlebot.** This is a dated, fully-attributed reference to which bots are hitting sites, what each one is for, and what the shift means for your access decisions.

**Last reviewed: 15 August 2026.** Share figures are for the full month of July 2026 from Cloudflare Radar's AI Insights (per-crawler share of AI-bot requests, pulled 1 August 2026), plus Cloudflare's own network analysis. Cloudflare sees a large share of web traffic but not all of it, so treat these as a single-network snapshot. Directional, and shifting month to month.

## Which AI crawlers have the most traffic right now?

Here is the July 2026 share of AI-bot traffic, with the month-over-month change from June:

| Crawler | Operator | July 2026 share | Change vs June | Primary job |
|---|---|---|---|---|
| **Googlebot** | Google | ~24.5% | −0.4 pp | Index (Search + AI Overviews / AI Mode) |
| **ClaudeBot** | Anthropic | ~16.3% | **−3.7 pp** | Train |
| **Meta-ExternalAgent** | Meta | ~12.7% | +2.5 pp | Train |
| **GPTBot** | OpenAI | ~9.7% | +0.1 pp | Train |
| **Bingbot** | Microsoft | ~8.9% | +0.8 pp | Index (Bing + Copilot grounding) |
| **Applebot** | Apple | ~6.5% | +0.7 pp | Index / train |
| **Amazonbot** | Amazon | ~6.0% | +0.5 pp | Index / train |
| **Bytespider** | ByteDance | ~5.1% | −2.2 pp | Train |
| **Claude-SearchBot** | Anthropic | ~3.5% | +0.2 pp | Index (Claude citations) |

Source: Cloudflare Radar AI Insights, July 2026 (full-month share of AI-bot requests). The one-line read: **Googlebot still leads because it feeds both classic Search and Google's AI features, but among purpose-built AI crawlers, ClaudeBot is still the front-runner — and Anthropic's two bots together (~19.8%) are now the clear #2 crawl presence on the web.**

## What just changed, and why does Anthropic's footprint matter?

The story is still Anthropic, now told in two bots instead of one. **ClaudeBot's June spike partly normalised** — it eased from about 20.0% to 16.3% of AI-bot traffic in July — but that does not undo the shift. Add **Claude-SearchBot (~3.5%)** and Anthropic's **combined crawl footprint is about 19.8%**, second only to Googlebot and comfortably ahead of OpenAI's GPTBot. Meta-ExternalAgent climbed to roughly 12.7% to take clear third, while Bytespider kept fading.

That footprint lines up with Anthropic's rising [business AI adoption](/blog/anthropic-overtakes-openai-business-adoption) over the same period. More usage tends to mean more aggressive crawling to keep models and retrieval fresh. For your site, the practical signal is that Anthropic is now fetching your pages heavily across two bots, so whether Claude can learn from and cite you increasingly depends on your letting both `ClaudeBot` (train) and `Claude-SearchBot` (index) through.

> Googlebot still tops the list, but the durable story is Anthropic's two-bot footprint (~19.8%) settling in as the clear #2 crawl presence — even after ClaudeBot's one-month spike cooled. Crawl attention is following adoption.

## How big has AI crawling become overall?

Large, and increasingly training-driven. Cloudflare reports that AI crawlers reached **about 22% of all bot traffic in Q1 2026**, up from a negligible share two years earlier. Now bigger than every bot category except traditional search-engine crawlers. And the mix has tilted toward training: **roughly 80% of AI bot activity is training-purpose crawling**, up from about 72% a year earlier.

The longer trend, year over year (Cloudflare, July 2024 to July 2025):

- **GPTBot** grew from ~4.7% to ~11.7% of overall crawl share.
- **Meta-ExternalAgent** jumped from ~0.9% to ~7.5%.
- **Bytespider** collapsed from ~14.1% to ~2.4% as ByteDance pulled back.

The takeaway: the set of bots visiting your site turns over fast, and a crawler that dominated last year can fade while a new one takes over. This is why a static [robots.txt](/glossary/robots-txt) written once and forgotten drifts out of date.

## Does heavy crawling mean heavy traffic back?

No, but the gap is narrowing fast. Cloudflare's crawl-to-referral data shows AI operators still crawl far more than they send visitors — yet the ratios improved sharply between June and July 2026 as AI search began sending more referrals:

| Operator | Crawl-to-refer, June 2026 | Crawl-to-refer, July 2026 |
|---|---|---|
| **Anthropic** | ~3,386 : 1 | ~1,917 : 1 |
| **OpenAI** | ~647 : 1 | ~251 : 1 |

Source: Cloudflare Radar crawl-to-refer summary, pulled 1 August 2026. Both operators roughly halved their pages-crawled-per-referral in a single month, so the "crawl a lot, refer almost nothing" pattern is easing — though Anthropic still crawls on the order of thousands of pages per referral. High crawl volume remains a leading indicator of being learned and indexed, not a promise of clicks, as we cover in [where AI crawls versus where it sends visitors](/blog/ai-crawl-vs-referral-traffic). Judge a bot's crawling by whether it helps you get cited, not by referral traffic alone.

## How should you use this data?

Treat it as a dated snapshot that informs access decisions, not a target:

- **Decide per bot, not with one switch.** Each crawler has a job. Train, index, or answer. Allow at least the index and answer bots that drive citations; the [AI crawler user-agent directory](/blog/ai-crawler-user-agent-directory) and the [train/index/answer lifecycle](/blog/ai-crawler-lifecycle) explain what each costs you if blocked.
- **Don't let a CDN silently block the surging bots.** A default "block all unknown bots" rule can cut off exactly the fast-growing crawlers like ClaudeBot and Claude-SearchBot. See [is your CDN blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers).
- **Watch your own logs, not just the industry chart.** Which bots hit *your* site, and how often, is the signal that matters. The method in [how to see which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site).
- **Revisit quarterly.** Because shares move this fast, a crawl policy set once decays; review it as the leaderboard shifts.

The industry share chart tells you where crawler attention is heading in aggregate. What decides your AI visibility is which bots reach your pages and whether that access turns into citations for your brand. Measured on your own site and across engines over time. That is exactly what **Buffy Intel** is built to track.

## The complete AI crawler user-agent directory
Source: https://heybuffy.com/blog/ai-crawler-user-agent-directory

AI crawlers multiply fast, the documentation is scattered, and the names are easy to confuse. This is a single, current directory of the major ones. What each does, what you lose by blocking it, and how to set your `robots.txt` deliberately.

## How to read this: the three jobs

Every bot here is doing one of three jobs (covered in depth in [The AI crawler lifecycle](/blog/ai-crawler-lifecycle)):

- **Train**: gathers content that may be baked into a future model.
- **Index**: builds the live search index the model retrieves from and **cites** at answer time.
- **Answer**: fetches one specific page in real time because a user asked (e.g. "summarise this link").

A single operator usually runs a separate bot for each, so you can allow or block them independently.

## The directory

| Operator | User-agent | Job | If you block it |
|---|---|---|---|
| OpenAI | `GPTBot` | Train | Less of your content learned by future GPT models |
| OpenAI | `OAI-SearchBot` | Index | You drop out of ChatGPT search citations |
| OpenAI | `ChatGPT-User` | Answer | "Summarise this link" breaks for your pages |
| Anthropic | `ClaudeBot` | Train | Less of your content learned by Claude |
| Anthropic | `Claude-SearchBot` | Index | Absent from Claude's cited search results |
| Anthropic | `Claude-User` | Answer | User-pasted-link summaries break |
| Google | `Googlebot` | Index | You lose Google Search **and** AI Overviews / AI Mode |
| Google | `Google-Extended` | Train | Excluded from Gemini training & grounding |
| Google | `GoogleOther` | Misc / research | Minor. Research and product crawls |
| Microsoft | `Bingbot` | Index | Lose Bing **and** Copilot grounding |
| Perplexity | `PerplexityBot` | Index | Absent from Perplexity's answers |
| Perplexity | `Perplexity-User` | Answer | User-triggered fetches break |
| Apple | `Applebot` | Index | Lose Siri / Spotlight surfaces |
| Apple | `Applebot-Extended` | Train | Excluded from Apple Intelligence training |
| Amazon | `Amazonbot` | Index | Lose Amazon's assistant surfaces |
| Meta | `meta-externalagent` | Train / Index | Less presence in Meta AI |
| Meta | `FacebookBot` | Index / previews | Social link previews degrade |
| ByteDance | `Bytespider` | Train | Content kept out of ByteDance / TikTok AI |
| DuckDuckGo | `DuckAssistBot` | Answer | Absent from DuckAssist answers |
| Cohere | `cohere-ai` | Train / retrieval | Content kept out of Cohere systems |
| Mistral | `MistralAI-User` | Answer | User-triggered fetches break |
| DeepSeek | `DeepSeekBot` | Train | Content kept out of DeepSeek models |
| Common Crawl | `CCBot` | Aggregator | See below. Closes a back-door into many models |

*(Older OpenAI/Anthropic tokens like `anthropic-ai` and `claude-web` still appear in some logs; the bots above are the current set. The landscape shifts every few months. Treat this as a living list.)*

## The special case: Common Crawl (`CCBot`)

`CCBot` doesn't fit the three jobs. Common Crawl is a non-profit that crawls the web into a giant **public archive** and trains no models itself, but that archive is one of the most widely used *inputs* for training models across many labs.

> Blocking `GPTBot` and `ClaudeBot` does **not** stop your content reaching those same labs through the Common Crawl dataset. To close that back-door, block `CCBot` specifically.

## robots.txt recipes

**Welcome everyone** (the right default for most brands that want AI visibility):

```
User-agent: *
Allow: /
```

**Allow search + answer, block training** (for publishers protecting content from model training while staying visible in AI search):

```
# Block training crawlers
User-agent: GPTBot
User-agent: Google-Extended
User-agent: ClaudeBot
User-agent: Applebot-Extended
User-agent: Bytespider
User-agent: CCBot
Disallow: /

# Everything else (search + answer bots) is welcome
User-agent: *
Allow: /
```

Grouping several `User-agent` lines above one `Disallow` applies that rule to all of them.

## Two things robots.txt can't do

1. **Stop spoofing.** A user-agent is self-reported. Well-behaved bots honour `robots.txt`; to actually enforce access (or verify a bot is who it claims), use IP-range / reverse-DNS checks at your server or CDN.
2. **Override your CDN.** If your CDN or WAF returns a 403 to a crawler before the request reaches your site, your `robots.txt` never gets read. A silent, common failure ([here's how to catch it](/blog/is-your-cdn-blocking-ai-crawlers)).

## Verify your own site in 30 seconds

Pretend to be a crawler and check the status code:

```
curl -sI -A "GPTBot/1.2 (+https://openai.com/gptbot)" https://yourdomain.com | head -1
```

A `200` means you're reachable; a `403` means something is blocking you regardless of `robots.txt`. Run it for the bots you care about most.

Deciding *which* of these to welcome is a strategy call. See [Should you let AI crawlers index your site?](/blog/should-you-let-ai-crawlers-index-your-site). Keeping the door open to the right ones, and catching it when it silently closes, is part of what **Buffy Intel** monitors.

## Is Google Search Console showing your AI Mode conversations?
Source: https://heybuffy.com/blog/ai-mode-conversations-in-search-console

Yes, and the surprise is *where*. As of **early August 2026**, Google confirmed that AI Mode query data lands in your **main Search Console performance report** — the same table as your classic Search queries — not in the separate Generative AI performance report. Because AI Mode counts every follow-up turn as a new query, conversational fragments like "yes, pricing" or "yes go on" are AI Mode turns hiding in plain sight in your keyword data.

This is part of the [measuring AI visibility](/blog/from-clicks-to-citations) series, and a direct follow-on to [what the Generative AI performance report shows and can't](/blog/google-search-console-ai-performance-report). That report answers "did I appear in an AI feature?"; this note is about a *different* data home — where the AI Mode **question text** actually surfaces, and how to read it honestly.

## Where does AI Mode query data actually show up in Search Console?

In the **main Performance report's query table**, alongside classic Search queries — not in the Generative AI report. Google confirmed in early August 2026 that the Generative AI performance report has **no query dimension** (it exposes impressions, pages, countries, devices, and dates only), so AI Mode's query strings flow into the general performance data instead. There are now two AI-relevant data homes in Search Console, and they hold different things:

| Search Console surface | What it isolates | Query text? | Clicks? |
|---|---|---|---|
| Generative AI performance report (launched 3 Jun 2026) | Impressions inside [AI Overviews and AI Mode](/blog/how-google-ai-mode-works) | No | No |
| Main Performance report (Search) | All Search queries, AI Mode turns included but unlabeled | Yes | Yes |

The practical consequence: the report that tells you *how often you appeared* in AI features (the Generative AI report) is silent on *which questions* surfaced you, while the report that holds the AI Mode question text (the main report) doesn't tell you which rows are AI Mode at all. The data is split across two views, and neither joins them for you.

## Why does each follow-up turn count as a new query?

Because AI Mode treats a conversation as a sequence of independent queries, not one session. Google's own documentation states that if a user asks a follow-up question within AI Mode, they are essentially performing a new query — and the impression, position, and click data in that new response are counted as coming from this new user query. So a single AI Mode conversation of five turns can generate five separate query rows in your data, each attributed to the words of that turn.

That design is why the query text looks so strange. A person mid-conversation doesn't re-type the full context; they reply in shorthand. Those replies become the "query."

> Each follow-up turn in an AI Mode conversation is logged as its own query — so a five-turn conversation shows up as five separate, conversational-looking rows in your Search Console data, not one.

## How do you recognise an AI Mode conversation turn in your data?

Look for queries that only make sense as **replies**, not as things someone would type into a search box cold. They are short, dependent, and conversational. Common shapes practitioners have reported spotting in mid-2026:

- One-word confirmations — "yes", "sure", "ok"
- Continuation prompts — "yes go on", "tell me more", "and then"
- Refinements that assume prior context — "yes, pricing", "the cheaper one", "for a small team"
- Pronoun-heavy fragments with no named subject — "does it integrate with that"

None of these carry a label saying "AI Mode." You are **inferring** from the conversational shape, so treat the pattern as directional evidence, not a confirmed segment. The tell is dependency: if a query is meaningless without a preceding turn, it almost certainly *is* a following turn.

## What can't you do with this data? (the honest limits)

The limits matter as much as the discovery, and naming them keeps you from over-reading the data:

- **You can't break AI Mode out.** There is no filter, dimension, or flag that isolates AI Mode queries from classic ones. You can pattern-match the fragments, but you can't measure AI Mode as a clean segment.
- **You can't reconstruct the conversation.** Turns aren't threaded or grouped by session, so you see scattered fragments, not the journey they belonged to.
- **Position is unreliable here.** As with AI Overviews, AI-feature placement doesn't map cleanly onto the classic "average position" metric, so read presence and query text, not rank.
- **Volume is understated and noisy.** Only turns that produced an impression for your site appear, and only when they clear Google's query-sampling thresholds — so this is a keyhole view, not a census.

This is the same honesty the Generative AI report demands: a real first-party signal and a narrow slice at the same time. It does **not** contradict the standing caveat that Search Console isn't a clean AI-prompt log — the [regex query-mining method](/blog/mine-search-console-for-ai-questions) still treats GSC as a *proxy* for AI intent. What's new is narrower and specific: AI Mode's own follow-up turns do land in the main report, as conversational fragments you can spot but not cleanly segment.

## What should brands do about it?

Read the conversational fragments as **conversion-journey breadcrumbs**, then structure content to be citable at every turn — not just the opening question. A practical loop:

1. **Pattern-match the fragments.** Scan your query table for conversational, dependent strings and group them by likely intent (confirm, continue, refine, compare, price).
2. **Map them to journey stage.** A "yes, pricing" turn is a late-funnel signal; "tell me more" is mid-funnel. The mix tells you where AI Mode conversations about you are heading.
3. **Answer every branch extractably.** [Query fan-out](/blog/how-query-fan-out-works) already means one question spawns many sub-queries; AI Mode conversations add *sequential* turns on top. Cover the predictable follow-ups — pricing, integrations, comparisons, who-it's-for — as self-contained, answer-first chunks so you can be cited at each turn, not only the first.
4. **Corroborate in the engines.** Because you can't segment AI Mode in GSC, verify with answer-level checks whether you're actually named and cited across engines, the way the [five-metric reporting stack](/blog/ai-visibility-reporting-stack) prescribes.

The strategic read is the one worth keeping: [AI Mode](/glossary/google-ai-mode) behaves less like a search box and more like a multi-turn [conversation](/glossary/conversational-search), and each [follow-up turn](/glossary/conversational-query) is a measurable query. If your brand isn't structured to be cited accurately at each turn, you simply won't appear in those rows — and you won't know the conversation happened.

Turning scattered, unlabeled query fragments into an answer-level view of whether you're cited across every AI surface, conversation turn by conversation turn, is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Do Google AI Mode and AI Overviews cite the same sources?
Source: https://heybuffy.com/blog/ai-mode-vs-ai-overviews-citations

**Google AI Mode and AI Overviews do not cite the same sources. Even though both are Google.** Two 2026 studies put numbers on the gap: the two surfaces share only about **59% of their top-100 cited sources** (BrightEdge, April 2026), and AI Mode pulls far less from classic search rankings than AI Overviews do. Roughly **19% of AI Mode citations came from the organic top-20** versus about **56% for AI Overviews** (seoClarity). Yet the *brands* recommended stay remarkably steady across surfaces. If you assume a citation in one Google AI surface means a citation in the other, the data says you're wrong.

This piece lays out what the two studies actually measured, why the surfaces diverge, and what it changes about how you earn and track AI citations. Both are single-vendor analyses using different methods and dates, so we read the numbers as directional, not precise. The *direction* is well corroborated across them.

## How different are the two Google surfaces, in numbers?

Here are the load-bearing figures, each with its source and date:

| Finding | Figure | Source (date) |
|---|---|---|
| AI Mode ↔ AI Overviews top-100 source overlap | ~59% (highest of any engine pair measured) | BrightEdge, AI Catalyst, 10 industries (24 Apr 2026) |
| Gemini ↔ AI Mode / Gemini ↔ AI Overviews overlap | 27% / 34% | BrightEdge (24 Apr 2026) |
| Range of source overlap across all engine pairs | 16-59% (a 43-point spread) | BrightEdge (24 Apr 2026) |
| Range of **brand-recommendation** overlap across engines | 36-55% (a 19-point spread) | BrightEdge (24 Apr 2026) |
| Share of AI Mode citations from the organic **top-20** | ~19% | seoClarity, 1,000 transactional US queries, 12,011 citations (Sep 2025) |
| Queries where AI Mode cited ≥1 organic top-20 page | 81% (only 28% for top-10) | seoClarity (Sep 2025) |
| Share of AI Overview citations from the organic **top-20** | ~56% | seoClarity, 5.1M citations across 362,000 AI Overviews (Oct 2025) |

The pattern is consistent across both vendors: the two Google surfaces are **more alike than any other engine pair, yet still meaningfully different**: and AI Mode is markedly less tethered to classic rankings than AI Overviews are.

## Why do two Google products cite different pages?

Because they are different systems solving the question differently, even sharing an index. **AI Overviews** generate a summary block on the standard results page and still lean substantially on the pages that rank well for the query, which is why more than half of their citations trace to the organic top-20. **[AI Mode](/blog/how-google-ai-mode-works)** is a Gemini-powered conversational experience that decomposes a question into many sub-queries. [Query fan-out](/blog/how-query-fan-out-works), and retrieves sources for each branch. That fan-out reaches well beyond the top-10 blue links, so most of what it cites sits *outside* the classic rankings.

In seoClarity's data the individual-position pull is also weaker than for AI Overviews: the organic **#1 result was cited about 25% of the time** in AI Mode, #2 about 21%, #3 about 16%. A real but modest advantage, far from a guarantee. Ranking first buys you a strong chance, not a slot.

## If sources differ, why are the same brands recommended?

This is the most important finding, and it resolves an apparent paradox. BrightEdge measured both layers and found they behave differently: **source overlap between engines swung widely (16-59%), but brand-recommendation overlap stayed tight (36-55%).** In its words, *"source agreement between engines varies widely and inconsistently; brand agreement is consistently steady."*

The engines disagree on *which page to quote* but agree on *which brand to name*, because a well-established [entity](/glossary/entity-authority) is recognised across all of them, even when each surface reaches for a different URL as its citation. This maps exactly onto the two-lens split we describe in the [brand-mention gap vs source gap](/blog/brand-mention-gap-vs-source-gap) audit: your *mention* strength travels across surfaces, your *cited pages* are decided per surface. It also underlines why [entity strength](/blog/entity-strength-ai) is the durable lever. It is the thing that stays constant when the citation plumbing does not.

> The exact page an engine cites is volatile and surface-specific. The brand it recommends is stable and entity-driven. Build for the second and you become resilient to the first.

## What does this change about your strategy?

The fundamentals don't change. Reachable, extractable, corroborated, fresh pages win everywhere. What changes is **how you measure and where you place your bets**:

- **Don't treat one Google citation as two.** A page cited in AI Overviews may be absent from AI Mode's answer to the same question, and vice versa. Verify each surface.
- **Classic SEO still carries into AI Overviews** (56% of citations from the top-20), so ranking work is not wasted there. It carries **less** into AI Mode (19%). You can be cited by AI Mode without ranking on page one, and ranked without being cited.
- **Win AI Mode by answering the fan-out**, not just the head query. Self-contained, answer-first passages for the predictable sub-questions. That's the subject of our companion guide, [how to get cited in Google AI Mode](/blog/how-to-get-cited-in-google-ai-mode).
- **Invest in the entity layer.** It's what keeps you *recommended* even as the *cited* URLs shift between surfaces and over time.
- **Measure each surface separately, over time.** A single check on one surface is noise; the signal is the trend on each, tracked across repeated snapshots.

Tracking whether you're cited in AI Overviews, AI Mode, and every other engine, as separate lines that each move on their own. Is exactly what **Buffy Intel** is built to measure, so you can see which surface you're winning and which one is quietly leaving you out.

## Google AI Overviews: the complete guide
Source: https://heybuffy.com/blog/ai-overviews-complete-guide

Google [AI Overviews](/glossary/ai-overviews) are the AI-generated answer block at the top of Google's search results: a synthesised response, assembled from multiple sources and citing them, that often sits *above* the familiar list of links. For a huge and growing share of searches, it's the first thing a user reads, and sometimes all they read.

## How AI Overviews work

Three things matter about the mechanics:

- **Grounded in Google's index.** Unlike a chat engine running its own crawler, Overviews draw on Google's existing search index and ranking signals, so a lot of classic SEO authority carries over here more than on other AI surfaces.
- **Built via [query fan-out](/glossary/query-fan-out).** Google decomposes your question into many sub-queries, retrieves sources for each, and synthesises one answer, so you're competing across many sub-searches, not one keyword.
- **It cites.** Overviews link the sources they used, which is the [citation](/glossary/citation) you're competing to earn, and the path to any click that still happens.

## Why they matter

AI Overviews sit on the **highest-traffic surface in search**. They compress the old "ten blue links" into one answer that names a few sources and brands. If you're not in that answer, the user may never scroll to where you rank. The classic [zero-click](/glossary/zero-click-search) dynamic, now dominant for informational queries. The goal shifts from *ranking a link* to *being cited inside the Overview*.

## What gets pulled into an Overview

In practice, Overviews favour the same things AI citation favours generally:

- **Answer-first, extractable passages**: content that states the answer cleanly in one self-contained chunk (the same structure that earns featured snippets).
- **[Structured data](/glossary/structured-data)**: `FAQPage`, `Article`, `Product` markup that labels what your content is.
- **Authority and corroboration**: pages from recognised entities, with claims echoed by other trusted sources.
- **Freshness**: recently-updated, accurate pages, especially for anything time-sensitive.

> Because AI Overviews ride on Google's index, the structured, authoritative content that already wins rankings and featured snippets is what wins Overview citations. It's the most SEO-continuous of the AI surfaces.

## How it differs from AI Mode

An Overview is a **summary block** on the results page. [Google AI Mode](/glossary/google-ai-mode) is a **full conversational experience**: a back-and-forth chat. Both are Gemini-powered and index-grounded, but AI Mode is where deeper, multi-turn research happens.

## Measuring your presence

Because Overviews vary by query, location, and time, eyeballing a few searches won't tell you much. What's decision-useful is **presence over time** across the many questions your customers ask. Are you named, are you cited, and who's recommended instead. The companion piece, [how to optimize for AI Overviews](/blog/how-to-optimize-for-ai-overviews), turns this into a plan; tracking it is what **Buffy Intel** automates.

## AI Overviews vs AI Mode: which costs publishers more clicks?
Source: https://heybuffy.com/blog/ai-overviews-vs-ai-mode-click-loss

**Both surfaces cut clicks to the open web, and the evidence suggests AI Mode cuts more.** In a 2026 randomized experiment, [AI Overviews](/glossary/ai-overviews) reduced outbound organic clicks by about **39.8%** yet left user satisfaction unchanged. The same study's exploratory [AI Mode](/glossary/google-ai-mode) arm left roughly **0.36 external clicks per search** against **0.53** for control users, and **lowered satisfaction by 1.14 points**. The difference is structural: an AI Overview sits atop a normal results page, so links survive below it, while AI Mode replaces the page with a conversation.

This compares the two Google surfaces on **click and traffic impact**. For the separate question of *which sources each one cites*, see [do AI Mode and AI Overviews cite the same sources](/blog/ai-mode-vs-ai-overviews-citations). The click figures come from Agarwal and Sen's 2026 SSRN working paper (not yet peer-reviewed, US desktop Chrome), covered in full in [do AI Overviews actually cause click loss](/blog/do-ai-overviews-cause-click-loss); the AI Mode arm there was exploratory, so read its numbers as directional.

## What is the difference between AI Overviews and AI Mode?

They are two different answer surfaces from the same company. Naming them precisely matters, because they behave differently for publishers.

- **AI Overview** is a generative summary that appears *above* the classic list of blue links on a normal Google results page. The organic links still exist below it, so a searcher can scroll past the answer to them.
- **AI Mode** is a separate, fully conversational interface. It answers in a chat-style thread, surfaces fewer outbound links, and supports follow-up questions rather than a fixed list of results.

The practical consequence is that an AI Overview leaves more of the old results page intact, while AI Mode is closer to a self-contained answer that a searcher rarely leaves.

## Which surface takes more clicks?

On the available causal evidence, AI Mode leaves fewer clicks to the open web, though the comparison is not like-for-like. The table below sets the measured figures side by side, each with its own baseline.

| Measure | AI Overviews | AI Mode |
|---|---|---|
| Outbound clicks (shown vs counterfactual) | 0.37 per search shown vs 0.62 hidden (~39.8% cut) | ~0.36 external clicks per search vs 0.53 for control |
| Effect on user satisfaction | No meaningful change | Fell by 1.14 points |
| Surface layout | Summary above surviving organic links | Full conversational takeover, fewer links |
| Evidence strength | Primary randomized arm | Exploratory arm (forced redirect) |

Source: Agarwal and Sen, 2026 (SSRN working paper). The two click figures use different metrics and subsamples, so the honest read is directional: AI Mode both removed more outbound clicks *and* lowered satisfaction, whereas AI Overviews removed clicks without changing how satisfied users felt. Do not subtract one number from the other as if they were the same measurement.

## How do they compare on citations, not just clicks?

Differently again, which is why you track both. Click impact tells you how much traffic a surface removes; citation sourcing tells you which pages it names as sources. On sourcing, two 2026 studies found the two surfaces share only about **59% of their top cited sources**, and AI Mode drew far less from the classic organic top rankings (roughly 19% of AI Mode citations from the organic top-20 versus about 56% for AI Overviews). The full breakdown is in [do AI Mode and AI Overviews cite the same sources](/blog/ai-mode-vs-ai-overviews-citations).

> AI Overviews and AI Mode are two zero-click surfaces with different physics: the overview thins the clicks on a page you still recognise, while AI Mode replaces the page and cites a different set of sources. Winning one does not mean winning the other.

## What does this mean for your visibility strategy?

Plan for both as [zero-click](/glossary/zero-click-search) surfaces, and shift the goal from the click to the [citation](/glossary/citation). Concretely:

- **Expect a structural click drop on both.** Neither surface lets you opt out of appearing, and both remove outbound clicks on informational queries, so budget for it rather than treating it as a temporary dip.
- **Compete to be the cited source on each surface separately.** Because they cite different pages, verify your presence on AI Overviews and AI Mode independently, not as one score.
- **Measure citations alongside traffic.** If sessions are your only metric, both surfaces read as pure loss even while your brand is shown and recommended, the shift laid out in [from clicks to citations](/blog/from-clicks-to-citations).

The two surfaces differ in how they take the click and in which sources they cite, so a single traffic number can hide whether you are still winning the answer. Watching where you are cited, where you are merely shown, and where AI still sends visitors, across both surfaces and over time, is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Are AI-scraping lawsuits changing what crawlers can take? The 2026 cases
Source: https://heybuffy.com/blog/ai-scraping-lawsuits-2026

**The 2026 AI-scraping lawsuits are a fight over how crawlers obtain content, not whether AI can cite you — and the early rulings favour publishers.** In July 2026 two cases raised the stakes: News Corp sued Brave (filed 22 July) for allegedly disguising crawlers to evade blocks, and a federal judge on 31 July largely refused to dismiss Reddit's "industrial-scale" scraping suit against Perplexity. Both turn on *bypassing access controls*, which is the same behaviour our crawler guidance has long said a self-declared [user-agent](/blog/ai-crawler-user-agent-directory) can't be trusted to reveal.

**Last reviewed: 13 August 2026.** Every legal fact below is attributed and dated; complaints and interim rulings are not verdicts, so read them as the state of play in mid-2026, not settled law. This piece explains what each case alleges, how licensing deals run in parallel, and what the access fight means for your AI visibility.

## What did News Corp accuse Brave of?

News Corp filed suit against Brave on **22 July 2026**, alleging that Brave **disguised its web crawlers to evade publisher blocks** and then scraped and sold copyrighted News Corp content to AI companies before March 2025. The complaint frames the disguise as the wrongdoing, not just the copying.

> "They have shamelessly stolen and then perfidiously profited from that pilfering by illicitly fencing our journalists' work." — News Corp CEO Robert Thomson, on the Brave complaint (as reported, July 2026)

The disguise allegation is the durable part. A block only works if the blocked party identifies itself honestly, and the corpus has documented repeatedly that a crawler's name is self-reported and [trivially spoofed](/glossary/verified-bot). What is new is a large publisher asking a court to treat *evading the block by hiding identity* as unlawful. If that theory holds, covert access becomes a legal liability, not a grey-area growth tactic. The claims are unproven; Brave has not conceded them.

## What happened in Reddit v Perplexity?

On **31 July 2026**, a federal judge **largely rejected Perplexity and SerpApi's motion to dismiss** Reddit's lawsuit, letting the core claims proceed. The court found Reddit had "plausibly pleaded that Perplexity conspired with at least one of the three data scrapers to bypass access controls."

The specifics that make it citable:

- **What Reddit alleges:** "industrial-scale" bypassing of its technical protections to obtain Reddit content for an AI answer engine.
- **Who is named:** Perplexity, plus data-scraping suppliers **SerpApi, Oxylabs and AWMProxy** as co-defendants.
- **The stage:** surviving a motion to dismiss means the case continues; it is **not** a finding of liability.

The one-line read: **a court has now let a "bypassing access controls" theory proceed against both an AI engine and its scraping suppliers.** That extends legal exposure down the supply chain, to the vendors who actually do the fetching, which is exactly the ["scraping vendor wearing a costume"](/blog/check-if-ai-bots-ignore-your-robots-txt) pattern the corpus has flagged.

## How do licensing deals fit alongside the lawsuits?

They are the other half of the same market: publishers are simultaneously **suing** some operators and **licensing** to others. The reported deals give the fight a price tag. All figures are as reported mid-2026; most deals publish no terms.

| Deal | Reported terms | Note |
|---|---|---|
| News Corp — OpenAI | **$250M+ over 5 years** | Largest single reported figure |
| News Corp — Meta | Up to **$50M/year** (≥3 years) | Same publisher, multiple buyers |
| Amazon — The New York Times | **$20–25M/year** | Ongoing content licence |
| Google — Reddit | Undisclosed | Reddit content for Gemini training |
| Nine — Microsoft | Undisclosed (2026) | Terms not published |

Source: Press Gazette and AI Business reporting, mid-2026; figures where a publisher or filing disclosed them. The pattern is a **multi-buyer licensing market forming next to active litigation** — the same publisher (News Corp) both licenses to OpenAI and Meta and sues Brave. Read it as leverage: content owners are being paid where access is negotiated, and going to court where they say it was taken.

## What does the access fight mean for your AI visibility?

Mostly it reinforces a strategy the corpus already recommends: **be reachable to identifiable, well-behaved crawlers, and enforce access by verified identity, not by trusting a name.** The lawsuits do not threaten citation of content a crawler was permitted to read; they target covert access. Three practical implications:

1. **Blocking is a real trade-off, now with legal weather around it.** If you [block AI crawlers](/blog/should-you-let-ai-crawlers-index-your-site), the operators that respect the block lose the ability to cite you, while litigation pressure pushes the rest toward licensed access over evasion. Decide per crawler class rather than blanket-blocking.
2. **Enforce by verified identity.** Because a self-declared name is spoofable, confirm crawlers against published IP ranges with a [verified-bot](/glossary/verified-bot) check, per [seeing which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site). That is the same signal these cases turn on.
3. **Licensing is becoming a lever, not just a defence.** Large publishers are monetising access directly; the emerging [pay-per-answer and charge-the-crawler models](/blog/can-you-charge-ai-agents-to-crawl) are the infrastructure version of the same shift for everyone else.

The through-line: the 2026 cases are narrowing the space for covert scraping, which makes *legitimate, identifiable* crawling the norm engines are being pushed toward. For a brand that wants to be cited, that is the access posture to optimise for.

Buffy Intel tracks whether your content is actually being reached and cited across AI engines — the citation side of the same access story these lawsuits are about. See where you show up, and where a block or a missed crawl is quietly costing you answers. Questions: support@flash.tech.

## AI search statistics 2026: a fully-sourced reference
Source: https://heybuffy.com/blog/ai-search-statistics-2026

This is a living, fully-sourced reference of AI search statistics for 2026. Every figure below is tied to its **named source and date**, hedged where the number is volatile; anything we couldn't attribute to a primary source has been left out. AI-search data is early and fast-moving, so treat these as directional reference points, and check the original before you quote them.

**Last reviewed: 15 June 2026.** Figures are vendor- or platform-reported unless noted; citation shares in particular swing month to month.

## How big is AI search in 2026?

Adoption is climbing fast across the major engines. The platform-reported figures, hedged:

| Statistic | Source | As of |
|---|---|---|
| Google AI Mode passed **1 billion monthly active users** | Google (I/O 2026) | May 2026 |
| Google AI Overviews reach **well over a billion users** monthly | Google (reported) | 2026 |
| OpenAI reported **~800 million weekly active users** of ChatGPT | OpenAI (reported) | late 2025 |
| Traditional search engine volume forecast to **fall ~25% by 2026** as users shift to AI | Gartner (forecast) | 2024 |

The direction is unambiguous even where the exact numbers move: the major engines now serve AI answers at the scale of the open web. (For how those answers are assembled, see [how Google AI Mode works](/blog/how-google-ai-mode-works) and the [AI Overviews guide](/blog/ai-overviews-complete-guide).)

## How much discovery is now zero-click?

A growing share of searches end inside the answer, with no click to a website. The [zero-click](/glossary/zero-click-search) reality that reshapes how brands get found.

- **~68% of Google searches ended without a click** in early 2026, per a Datos/SparkToro analysis reported by Search Engine Land. The rise of AI summaries is a major driver.
- Engines increasingly answer the question on the results page, so visibility shifts from *earning the click* to [being cited in the answer](/blog/from-clicks-to-citations).

The practical read: if your only metric is sessions, AI search will look like a loss even as your brand is being shown. Measure citations and recommendations alongside traffic.

## Which sources do AI engines cite most?

Community-edited and experience-rich sources dominate AI citations. Often over established news and brand pages. Numbers vary by engine and category, so these are directional:

| Statistic | Source | As of |
|---|---|---|
| Wikipedia ~**13.15%** + Reddit ~**11.97%** of US ChatGPT citations (together >25%); WSJ, NYT, Bloomberg absent from top 20 | 5W Research | June 2026 |
| Reddit **leads AI citation share**; LinkedIn cited in ~14.3% of ChatGPT Search, ~13.5% of Google AI Mode, ~5.3% of Perplexity responses | Semrush (325K-prompt study) | 2026 |
| "Best X" blog lists were **43.8% of all cited page types** in a ChatGPT analysis of ~750 prompts / ~26,283 URLs | Glen Allsopp (practitioner study) | 2026 |
| Claude-ChatGPT citation **domain overlap just 8%**; Claude-Google overlap ~64% | Profound, "The State of AI Search" (Zero Click conf) | June 2026 |

Two takeaways: citation sources skew toward [corroborated](/glossary/corroboration) community content (a reason to take [Reddit visibility](/blog/how-to-use-reddit-for-ai-search-visibility) seriously), and the engines barely agree with each other, so being cited on one is no guarantee on another. The dominance of independent roundups also confirms the [listicle effect](/blog/why-ai-loves-listicles) and the case for [earned placement](/blog/get-into-ai-cited-best-lists).

## How fast is AI referral traffic growing?

When citations are clickable, AI engines are starting to send real referral traffic, though it's still a small share of the total.

- **Adobe Analytics** reported a roughly **693% year-over-year surge in AI-source traffic to US retail sites** over the 2025 holiday season. A large jump off a small base.
- **Profound** reported ChatGPT referral traffic **jumped ~60% in May 2026** when its citations became clickable, with about a **quarter of those clicks landing on homepages** (up from ~3.6%).

These are directional and vendor-reported, but the pattern is consistent: AI referral volume is growing quickly off a small base, and it behaves differently from search clicks, which is why it often [shows up as direct traffic](/blog/why-ai-traffic-shows-up-as-direct) in analytics.

> The numbers move every month, but the direction doesn't: discovery is shifting into AI answers, the sources engines cite skew toward community and independent content, and the engines disagree with each other. Optimise for citations, corroborate across engines, and measure the trend, not the headline.

## How should you use these statistics?

Treat this page as a reference, not gospel. Cite the **named primary source** when you reuse a figure, note its **date**, and prefer a measured trend over a single snapshot. Because live retrieval favours recently-updated pages, we keep this reference on a refresh cadence and update figures substantively as new studies land. The same [freshness discipline](/blog/content-freshness-citation-cliff) that keeps any competitive page citable.

The one stat that matters most is your own: whether AI engines actually surface, cite, and recommend *your* brand, tracked over time across every engine. That measurement is exactly what **Buffy Intel** is built to provide.

## Why your AI 'share of voice' score swings week to week
Source: https://heybuffy.com/blog/ai-share-of-voice-volatility

AI answers are probabilistic, not fixed. Ask an AI engine the same category question repeatedly and the set of brands it names changes; reword the question slightly and the list scrambles further. So a single snapshot of your "share of voice" or citation rate is **volatile by design**: it moves week to week even when nothing about your brand changed. The fix is not to abandon measurement but to change the method: sample many prompts, repeatedly, across every engine, and anchor on downstream outcomes.

This piece collects the evidence. Every figure attributed and dated, and explains what to measure instead. It pairs with the deep-dive on [how ChatGPT picks the sources it cites](/blog/how-chatgpt-picks-sources) and defines the underlying concept in the glossary entry for [answer volatility](/glossary/answer-volatility).

## How unstable is an AI "share of voice" number, really?

Very. A 2026 study by Zaprev (an India- and US-based AI-visibility vendor), summarised in a widely shared LinkedIn post by founder Mayank Shrivastava, asked roughly **12,000 commercial queries** across OpenAI and Anthropic models and measured how much the list of recommended brands overlapped between two answers. It scored overlap with **Jaccard similarity**: the count of shared brands divided by the combined pool, where 1.0 is identical and 0 is no overlap.

The findings, as reported, are stark. Treat the exact numbers as one vendor's self-reported study (single methodology, shared via social post, not peer-reviewed). Directional rather than precise.

| What changed between the two answers | Brand-list overlap | 
|---|---|
| **Nothing**: identical question asked 30 times in one day | same set only **50-61%** of the time |
| **Synonym swap**: "best CRM" → "top CRM" | **~28%** overlap |
| **Added constraint**: "CRM" → "CRM for a SaaS startup under 50 people" | **~13.5%** (Jaccard) |
| **Region / language**: English → French, UK → German | **~13.8%** overlap |
| **Different provider**: same question to OpenAI vs Anthropic | **~33%** consensus |

Source: Zaprev / ZapRank study (2026), as reported by the author on LinkedIn. The headline reading: even the best case. The identical question, asked twice, same day. Agrees only about half the time, and any cosmetic rewording scrambles the brand list *more* than switching to an entirely different model provider does. Wording moves the answer more than the model does.

## Why do AI answers change when nothing about your brand did?

Because four independent sources of variation stack on top of each other, and none of them is under your control:

- **Sampling.** Language models generate by sampling tokens probabilistically, so the same prompt yields a slightly different answer each time. Different phrasing, and often a different shortlist.
- **Live retrieval.** When the engine searches the web, it pulls a fresh mix of pages each time; what is indexed and judged relevant shifts day to day. (How that selection happens is the subject of [how ChatGPT picks sources](/blog/how-chatgpt-picks-sources).)
- **Query fan-out.** A single question is silently expanded into many sub-queries, and small wording changes route to different sub-queries and different sources. See [how query fan-out works](/blog/how-query-fan-out-works).
- **Phrasing sensitivity.** As the table shows, adding a constraint or translating the prompt produces a substantially different answer, because it changes which slice of the corpus the model retrieves against.

The phenomenon is corroborated beyond the single study. An academic preprint, *"Don't Measure Once: Measuring Visibility in AI Search"* (arXiv, 2026), tracked AI answers over ~45 days and found day-to-day overlap of cited sources averaging only about **0.34-0.42** (Jaccard). Roughly 60-65% of cited sources changing between consecutive days. Vendors acknowledge it too: HubSpot shipped a free "AEO Sensor" specifically to track answer-engine volatility, and Profound publishes an ongoing AI-search-volatility tracker. The instability is a property of the medium, not a flaw in any one tool.

## Does a smarter model or "more reasoning" fix it?

No. The same study reported that changing the model's reasoning effort from high to low moved the overlap numbers by **at most about 5%**: a rounding error next to the 40-50-point swings caused by rewording. You cannot buy your way out of volatility with a bigger model, because the variation lives in sampling and retrieval, not in reasoning depth. This is why a "we asked the smartest model once" snapshot is no more trustworthy than any other single observation.

## Does this mean AI-visibility tracking is pointless?

No. It means a **single snapshot of a tiny fixed prompt set** is unreliable, which is a sampling problem with a sampling answer. The same statistics that make one observation noisy make a large, repeated sample stable. The honest method:

- **Sample many prompts, not a handful.** Ten hand-picked prompts will whipsaw; a few hundred representative ones average out. This is why [choosing the right prompts to track](/blog/how-to-choose-prompts-to-track) matters more than any single result.
- **Repeat the sampling on a schedule** and read the **distribution**, not one figure. A [share of voice](/glossary/share-of-voice) of "42% ± 6 over 300 prompts this week" is a real signal; "43% on Tuesday" is noise.
- **Measure across every engine.** Cross-provider consensus was only ~33%, so a number from one engine says little about another. [Citation coverage](/glossary/citation-coverage) and presence have to be read per engine.
- **Watch the trend, not the wobble.** A four-week moving line tells you whether you are gaining ground; a day-to-day delta mostly tells you the model sampled differently. This is exactly the discipline behind [reading an AI-visibility case study](/blog/how-to-read-an-ai-visibility-case-study) honestly.

Done this way, presence metrics are useful leading indicators. Done as a single spot check, they are theatre.

## What should you actually measure?

Anchor on **downstream outcomes**, because they aggregate over many answers and tie to real behaviour rather than to one volatile generation. The scoreboard has already moved [from clicks to citations](/blog/from-clicks-to-citations), but the most stable layer sits one step further down the funnel:

- **AI-referred sessions and conversions**: build an [AI-referral view in GA4](/blog/ga4-ai-referral-dashboard), remembering that much AI traffic arrives unlabelled as [Direct](/glossary/dark-traffic).
- **Pipeline from AI-discovered buyers**: the method for tying revenue to AI answers is in [how to prove AI traffic converts](/blog/prove-ai-traffic-converts).
- **Smoothed presence trends** as the leading indicator that feeds the above, never a single citation-rate reading.

> Treat one AI answer like one coin flip: a single result tells you almost nothing, but ten thousand results tell you the odds. Measure the distribution and the downstream outcome, not the snapshot.

The durable takeaway survives whatever the exact 2026 numbers turn out to be: AI answers are noisy by construction, so a stable reading comes from volume, repetition, and outcomes, not from a prettier single number. Confusing a noisy snapshot for a trend is the most common mistake in AI-visibility reporting.

Reading presence as a smoothed distribution across hundreds of prompts and every major engine, and tying it to AI-referred traffic and conversions. Is exactly what **Buffy Intel** is built to do: it samples repeatedly over time so you track the signal, not the noise.

## AI shopping in India: what's different, and what brands should do
Source: https://heybuffy.com/blog/ai-shopping-in-india

Most AI-visibility advice is written for a US buyer with a credit card and a Best Buy nearby. Indian shopping questions behave differently inside AI engines. Different sources get cited, different objections get raised, and price operates as a hard constraint, not a preference. We track how engines answer Indian buyer prompts every day; this is what consistently differs, and what to do about it.

## How do engines handle Indian shopping intent?

The deciding factor is whether the query carries **India signals**: "₹", "in India", a city, an Indian marketplace name, or India-specific vocabulary. With them, engines switch into an Indian source pool; without them, they frequently default to global answers: US brands, dollar prices, retailers that don't ship to Pune.

That has a sharp implication: your customers' real prompts are full of India signals, so **the answers that matter to you are built from the India source pool**: and your visibility in that pool, not in generic global answers, is what to measure and optimize. A brand that looks great on "best vitamin C serum" may be absent from "best vitamin C serum under ₹700 in India", and only the second one sells.

## What gets cited for Indian queries?

The citation mix we observe skews away from brand sites and toward three surfaces:

- **Marketplaces**: Amazon.in, Flipkart, Nykaa, Myntra and category peers. Their listings are deep, structured, review-rich, and engines treat them as ground truth for *price, availability, and ratings in India*. Your marketplace listing is an AI-visibility surface whether you manage it or not.
- **India-focused reviewers and roundups**: tech and beauty publishers, YouTube reviewers, and "best under ₹X" listicles. As everywhere, [independent roundups dominate commercial-intent citations](/blog/why-ai-loves-listicles), but in India they're organized by **price band**, which is its own playbook (below).
- **Communities**: buyer threads on quality, durability, and service experiences feed the reliability branch, in a market where post-purchase trust is the deciding objection.

## Why are price bands the unit of competition?

Indian shopping queries are price-anchored to a degree global playbooks underestimate: "best phone under ₹20,000", "sunscreen under ₹500". The band is in the prompt itself. Engines respect it, fan out within it, and cite the roundups built around it. Practical consequences:

1. **Know your bands.** Your products compete inside specific ₹ thresholds; the fan-out happens *within* the band, not across the category.
2. **State the price in crawlable text and structured data**, in rupees. An engine that can't place you in the band can't shortlist you for it.
3. **Pursue earned placement in band-specific roundups**: "best under ₹X" lists are the listicle ecosystem that decides these answers.

## What's the India-specific trust branch?

Beyond specs and price, Indian buyer questions reliably fan out into a distinct objection set: **cash on delivery, return pickup, warranty honored in India, genuine-vs-grey-market, and delivery timelines.** These are answerable questions, and most D2C brands answer them nowhere a crawler can read. Put them in product-level FAQs in plain text: "COD available across India", "7-day return with free pickup", "1-year India warranty, serviced in 40 cities." Each one is a sub-query you either win or forfeit to a marketplace page.

> In India, the engine's last question before recommending you isn't "is it good?". It's "will it arrive, can I pay on delivery, and is it genuine?" Answer those in crawlable text or lose the answer to whoever does.

## The playbook for Indian D2C brands

1. **Make your India-ness machine-legible**: ₹ pricing, "ships across India", serviceability, and regional model equivalences (electronics brands: [the model-number hygiene rules](/blog/ai-visibility-for-electronics-brands) apply doubly when an India SKU differs from global).
2. **Treat marketplace listings as citation surfaces**: same specs, same claims, same names as your own site; engines cross-check, and contradictions cost trust.
3. **Answer the trust branch** in product FAQs, as text.
4. **Win your price bands**: on-page clarity plus earned placement in band roundups.
5. **Mind the language gap**: engines process Hinglish and vernacular prompts, but cited sources skew English; clear, simple English content that mirrors how Indian shoppers actually phrase things (occasions, festivals, "for Indian skin/weather/voltage") matches more of the real fan-out.
6. **Measure with India prompts**: track [share of voice](/glossary/share-of-voice) and citations on the queries your buyers actually ask, ₹ signs included, per engine, over time. The engines disagree, and [the answer-level metrics](/blog/from-clicks-to-citations) are where the truth lives.

## What to do next

Write down ten real buying questions for your category *as an Indian shopper would type them*. Bands, COD, "in India" and all. Ask each engine. Note who's recommended, who's cited, and whether your India answers exist anywhere crawlable. That gap list is the playbook above in priority order, and monitoring it daily, across every engine, is what **Buffy Intel** is built for, from India, for exactly this market.

## AI visibility for D2C beauty brands: a playbook
Source: https://heybuffy.com/blog/ai-visibility-for-d2c-beauty-brands

Beauty is one of the most AI-researched categories there is, and one of the hardest to win, because the answers lean so heavily on sources you don't own. A D2C skincare or beauty brand that isn't found, described accurately, and recommended by AI is being cut from shortlists it never sees. Here's the playbook.

## Why beauty is a high-stakes AI category

- **Relentless research intent.** Shoppers ask AI in concern-and-ingredient language: "best vitamin C serum for sensitive skin," "niacinamide vs retinol for acne," "fragrance-free moisturizer for eczema." Every query [fans out](/blog/how-query-fan-out-works) across concern × ingredient × skin type × budget. Hundreds of branches per product.
- **Third-party sources dominate.** AI answers about beauty lean on Reddit communities, review sites, expert/derm roundups, and "best of" [listicles](/blog/why-ai-loves-listicles). Exactly the sources beauty shoppers already trust. Your own PDP is one input among many.
- **Claims and ingredients are scrutinised.** AI will describe your actives, concentrations, and whether you're "good for" a concern, so accuracy and [perception](/glossary/brand-perception) carry real risk.

## The playbook

### 1. Map your category's fan-out
List the real questions: by concern (acne, dullness, ageing, sensitivity), by ingredient (vitamin C, retinol, niacinamide, SPF), by skin type, and the comparisons ("X vs Y," "alternatives to X"). Build [intent-complete](/blog/how-query-fan-out-works) hubs that answer them, not a single product page per query.

### 2. Make your PDPs machine-legible
Beauty buyers, and AI. Want specifics, not vibes. On every product:
- Key actives and **concentrations**, full ingredient list, and what each does.
- **Concerns addressed**, **skin types**, and honest claims ("fragrance-free," "non-comedogenic").
- [Structured data](/glossary/structured-data). `Product`, `Offer`, `FAQPage`, so the facts are extractable.

This is what lets AI describe your [hero products](/glossary/hero-products) accurately instead of guessing.

### 3. Win the sources beauty AI trusts
Because third-party content dominates, the highest-leverage move is **earned placement**: get included in the independent "best [category]" roundups and reviews AI cites, and be genuinely discussed in the communities (skincare forums, reviews) that feed beauty answers. Trying to out-rank those roundups with your own self-listing page loses.

### 4. Manage perception and correct claims
Watch how each engine describes your hero products' efficacy and ingredients. AI working from stale or thin info can misstate a concentration, attribute a competitor's claim to you, or frame you as "basic." [Fix wrong descriptions](/blog/fix-wrong-ai-description) by making the correct facts reachable and corroborated.

### 5. Measure across engines, for *your* category
Beauty answers vary sharply by engine and phrasing. Track [presence, share of voice, citations, and sentiment](/blog/how-to-measure-ai-visibility) across ChatGPT, Gemini, Claude, and Google's AI surfaces, for your specific concern-and-ingredient queries. Over time.

> In beauty, the buying decision increasingly happens inside an AI answer built from Reddit, reviews, and roundups. You win by being accurately legible to AI *and* present in the sources it trusts, not by shouting louder on your own PDP.

This is the category Buffy Intel was built around, and the work is concrete: legible product data, earned presence, accurate perception, measured across every engine.

## AI visibility for electronics brands: a playbook
Source: https://heybuffy.com/blog/ai-visibility-for-electronics-brands

Electronics buyers ask AI the hardest questions in commerce: exact specs, model-vs-model comparisons, compatibility, and "is it worth it over the cheaper one?" Engines love this category. It's factual and tabular, but they're merciless about data quality. The brands that win are the ones whose product facts are **unambiguous, complete, and current** everywhere the engine looks.

This is part 2 of the category playbooks. The [beauty playbook](/blog/ai-visibility-for-d2c-beauty-brands) covers a category ruled by sentiment and routines; electronics is ruled by **specs and comparisons**.

## What does the fan-out look like for electronics?

A single question. "Should I buy the X90 Pro?". [Fans out](/blog/how-query-fan-out-works) into branches with very different winning formats:

| Branch | Example sub-query | What wins it |
|---|---|---|
| Specs | "X90 Pro battery capacity / ports / weight" | Your PDP's spec table, if it's crawlable |
| Comparison | "X90 Pro vs Y50" | Comparison pages + expert reviews |
| Compatibility | "does it work with my MacBook / which charger?" | Product FAQs, support docs |
| Value tier | "best in this price range" | Independent roundups and reviewers |
| Reliability | "X90 Pro problems / after 1 year" | Communities, long-term reviews |

You can't win every branch with one page. You win with a *system*: structured PDPs for specs, honest comparison content, FAQs for compatibility, and earned coverage for the tier and reliability branches (where [third-party listicles dominate citations](/blog/why-ai-loves-listicles)).

## Why do model numbers matter so much?

Electronics has an entity problem no other category has: **one product, many names.** The marketing name, the model number, regional variants, retailer SKUs, and last year's near-identical predecessor all coexist. An engine that can't resolve them confidently will mix specs across variants, attribute reviews to the wrong generation, or leave you out of an answer rather than risk being wrong.

The fix is [entity hygiene](/blog/entity-strength-ai), stated explicitly on your own pages:

- **Declare equivalences**: "X90 Pro (model XR-90P; sold as XR-90P-IN in India)". In text, on the PDP.
- **One canonical page per product**, with variants as structured options, not five competing URLs.
- **Name the generation**: "the 2026 model, replacing the X80", so reviews and specs attach to the right device.
- **Keep identifiers in your structured data**: GTIN/MPN in Product schema lets engines match your page to retailer and review data with certainty.

## What should the PDP actually contain?

Everything a careful salesperson would say, in machine-readable form. The [catalog-enrichment layers](/blog/prepare-product-catalog-for-ai-agents) applied to devices:

1. **A complete spec table** in semantic HTML, not an image, not a JS-only tab, not a PDF. This is the single highest-leverage asset in the category.
2. **Product structured data**: name, brand, model, GTIN/MPN, price, availability, ratings, so the facts are labelled, not guessed.
3. **Compatibility FAQs**: the "does it work with…" questions from your support tickets, answered as text.
4. **An honest comparison**: against your own lineup at minimum ("X90 Pro vs X90: what you get for the extra ₹4,000"). Engines treat criteria-based comparison content as high-trust; it also wins the branch your competitors' marketing pages can't.
5. **Dated firmware/availability notes**: electronics facts go stale fast, and [stale pages fall out of live citations](/blog/content-freshness-citation-cliff). When the new generation launches, update or clearly supersede the old PDP rather than leaving two "current" models competing.

> In electronics, the engine isn't persuaded. It's *resolved*. The brand whose facts are unambiguous, liftable, and current gets recommended; everything else is noise the model routes around.

## Where do reviews fit?

Reliability and value branches are decided off your site. Expert reviewers, communities, marketplace reviews. Two moves matter: **consistency** (specs and claims identical across your site, marketplaces, and retail listings. Engines cross-check, and contradictions read as untrustworthy) and **earned presence** (the reviewers and roundups engines actually cite for your category and price tier. Pitch them; that's [where commercial-intent citations live](/blog/why-ai-loves-listicles)).

## What to do next

Take your three best-selling devices and ask an AI engine the five branch questions above for each. Score yourself: were your specs quoted from *your* page? Did the comparison include you, accurately? Did compatibility answers exist at all? The gaps are your roadmap, and tracking those answers daily, across every engine, with fixes ranked by impact, is what **Buffy Intel** is for. Electronics brands entering AI answers early get a compounding head start: the [agentic-commerce wave](/blog/agentic-commerce-readiness) consumes exactly the same structured catalog.

## AI visibility for fashion and apparel brands: a playbook
Source: https://heybuffy.com/blog/ai-visibility-for-fashion-brands

Fashion is the hardest category for AI to recommend, and the biggest opportunity. There is no objective "best" dress the way there's a best-spec laptop, so engines recommend apparel by **context**: occasion, fit, aesthetic, weather, budget. The brands that win state those attributes in plain, crawlable text; the brands selling vague "elevated essentials" can't be matched to any real query. This is part 3 of the category playbooks, where the [beauty playbook](/blog/ai-visibility-for-d2c-beauty-brands) is ruled by sentiment and the [electronics playbook](/blog/ai-visibility-for-electronics-brands) by specs, fashion is ruled by **taste and occasion**.

## What does the fan-out look like for fashion?

A single question. "What should I wear to an autumn outdoor wedding?". [Fans out](/blog/how-query-fan-out-works) into branches that each reward different content:

| Branch | Example sub-query | What wins it |
|---|---|---|
| Occasion | "guest outfit for an outdoor wedding" | Styling guides, lookbooks, editorial |
| Fit | "midi dress for petite / curvy / tall" | PDPs that state fit and body-type cues |
| Aesthetic | "quiet-luxury / cottagecore autumn looks" | Pages using the same style vocabulary |
| Material & care | "is it warm enough / machine washable?" | Fabric details and care FAQs |
| Trend & season | "autumn 2026 wedding-guest trends" | Freshly updated seasonal content |

You can't win this with a bare product grid. You win with a *system*: attribute-rich PDPs, editorial styling content for the occasion and aesthetic branches, and earned coverage in the roundups engines cite for "best [item] for [occasion]."

## Why does attribute language decide everything here?

Because taste questions are answered by matching qualifiers, not by ranking a winner. An engine resolving "smart-casual linen shirt for hot weather" is looking for pages that literally say *smart-casual*, *linen*, *breathable*, *hot weather*. Translate every subjective claim into a concrete, liftable attribute:

- **Occasion tags**: "office, smart-casual, beach wedding," not "versatile."
- **Fit and cut**: "high-waisted, relaxed, true to size; model is 5'9" wearing S," not "flattering."
- **Fabric and care**: composition, weight/season, washability. The [catalog-enrichment layers](/blog/prepare-product-catalog-for-ai-agents) applied to apparel.
- **Aesthetic vocabulary**: name the styles your pieces actually fit ("minimalist, quiet-luxury") so they match how shoppers now describe taste to an engine.

> In fashion, AI doesn't pick the best garment. There isn't one. It picks the garment whose page proves it fits *this* occasion, *this* body, *this* aesthetic. Specific attributes are how taste becomes machine-readable.

## How should fashion brands handle variants and sizing?

Apparel has an entity problem as acute as electronics': one style, many colourways, sizes, and regional SKUs. Without [entity hygiene](/blog/entity-strength-ai), engines mix reviews across variants or drop the item. Keep **one canonical page per style** with variants as structured options; state sizing in references an engine can use ("runs small. Size up; UK 12 = EU 40"); and keep identifiers in [structured data](/glossary/structured-data) so your page matches retailer and review data with confidence.

## Where do reviews and earned coverage fit?

Fit and quality are judged off your site. Reviews ("true to size?"), editorial roundups, and communities. Two moves matter most: surface **fit-specific review text** as crawlable content (the single most-asked apparel sub-query), and pursue **earned placement** in the styling guides and "best [item]" lists engines actually cite for your segment, that's [where commercial-intent citations live](/blog/why-ai-loves-listicles), and where owned pages alone can't reach.

## What to do next

Take your three best-selling styles and ask an AI engine the five branch questions above for each. Were you matched to the right occasion and fit? Were your own attribute words quoted, or did the engine recommend a competitor who stated theirs more clearly? The gaps are your roadmap, and tracking those answers daily, across every engine and every season, with fixes ranked by impact, is what **Buffy Intel** is for. The same attribute-rich catalog also feeds the [agentic-commerce wave](/blog/agentic-commerce-readiness), where an agent shops your apparel on a customer's behalf.

## AI visibility for multi-location & local-service brands
Source: https://heybuffy.com/blog/ai-visibility-for-local-service-brands

For a multi-location or local-service brand, AI visibility is won or lost **one city at a time**. When someone asks for the "best fertility clinic near me," the engine builds a city-specific answer from local listings, reviews, and directories for *that* location, so a brand that's strong nationally can still be invisible where its local footprint is thin. This is the per-location playbook, modeled on the [category playbook approach](/blog/ai-visibility-for-d2c-beauty-brands) but pointed at place-based brands.

The core truth: **the answer is assembled per location, so your footprint has to be complete per location.**

## Why is this harder for multi-location brands?

Because every location is its own contest. AI localizes through the retrieval layer. It [infers the user's city and searches locally](/blog/do-ai-engines-know-where-you-are), so a query in Phoenix and the same query in Denver pull different local sources and can name different businesses. A flagship with a pristine profile doesn't carry a satellite location with a thin one. The brand-level reputation helps, but the *local* footprint in each market is what gets retrieved and cited there.

## What does the per-location playbook look like?

The same levers as single-location local AEO, executed at every location and kept consistent across all of them:

| Lever | Multi-location specifics |
|---|---|
| Google Business Profile | One verified profile per location, accurate categories and hours |
| NAP consistency | Identical data per location, consistent across every directory |
| Per-location pages | One real, substantive page per location. Never templated stubs |
| Reviews | Review velocity at *each* location, not just the flagship |
| Local schema | `LocalBusiness` (or category type) per location, with address + geo |
| Service-area logic | For mobile/home services, define service areas honestly |

The failure mode is the templated doorway page: fifty near-identical city pages that only swap the place name. Engines discount thin duplicates, and they can hurt. One honest page per place you actually operate beats fifty stubs.

## How does this play out by vertical?

Different local-service categories stress different parts of the playbook:

- **Healthcare (clinics, fertility, dental).** YMYL. The highest trust bar. Accurate credentials, `MedicalClinic` schema, consistent professional listings, and trustworthy reviews carry extra weight (more below).
- **Home services (plumbing, HVAC, electrical).** Service-area logic and review velocity dominate; directories like Thumbtack and HomeGuide are heavily cited, so earned presence there matters.
- **Multi-location retail.** Per-store profiles, accurate hours and inventory signals, and local pages that reflect each store, not the chain.
- **Legal.** YMYL again; practice-area and location specificity, `LegalService` schema, verifiable credentials, and reputation across legal directories.
- **Real estate.** Hyper-local content and agent/office-level profiles; market-specific authority per area served.

## Why is healthcare the hardest case?

Because it's [YMYL](/glossary/e-e-a-t). Your Money or Your Life, where engines apply a higher trust bar. For a fertility clinic, the engine is effectively vetting a medical provider, so it leans on credibility signals: verifiable credentials, `MedicalClinic` schema, consistent listings across medical directories, and [corroboration](/glossary/corroboration) from trustworthy third parties. Thin, inconsistent, or unverifiable data is more costly here than in any low-stakes category, and reviews carry both reputational and trust weight.

> For place-based brands, there is no national AI answer. Only a stack of city answers, each built from that city's local web. You win them one location at a time, and in healthcare and legal you win them with credibility, not volume.

## What to do this quarter

1. **Inventory every location** and audit its profile, NAP, and reviews independently.
2. **Fix the weakest locations first**: they're your invisible cities.
3. **Publish one real page per location**, with local specifics and the right schema.
4. **Drive review velocity at each location**, not just the flagship.
5. **For YMYL categories**, prioritize credentials, category schema, and corroboration.
6. **Measure presence per city, per engine**: a national average hides the gaps.

A brand-level dashboard will lie to a multi-location business; the truth is in the per-city, per-engine breakdown. Tracking AI presence and citations location by location, across every engine, is exactly what **Buffy Intel** is built to do, and it's where this Local AI Visibility series has been heading all along.

## The AI-visibility reporting stack: 5 metrics that matter
Source: https://heybuffy.com/blog/ai-visibility-reporting-stack

The fastest way to lose a budget for AI visibility is to report a number nobody trusts. "We're mentioned more!" invites the obvious question, *so what?*, and a single presence metric can't answer it. To survive a planning review, AI-visibility reporting needs to connect *what the engines say* to *what it drives.*

Here's the stack we'd defend: five metrics, two layers. The first three are **answer-level**: measured inside the AI answers themselves. The last two are **outcome-level**: measured in your own analytics.

## Layer one: what the engines say

These can't be pulled from a rank tracker or GA4. You have to *ask the engines* the questions your customers ask, across many prompts and every engine, and log what comes back, because answers vary run-to-run, and they disagree with each other.

### 1. Share of voice

How often you appear, relative to competitors, across a representative set of buyer prompts. This is the headline presence number, but read it as *share*, not raw count: appearing in 40% of answers means little until you know a competitor is in 80%. Track it [per engine](/blog/from-clicks-to-citations), because ChatGPT, Gemini, Claude, and Google's AI surfaces each draw a different shortlist.

### 2. Citation rate

When you *are* mentioned, is your **own site** the cited source, or is the engine learning about you through a retailer, a review site, or a competitor's comparison page? High presence with low citation rate means the narrative about you is being written by others. This is the most actionable metric in the stack, because it points straight at content you can fix.

### 3. Sentiment

*How* you're described, not just whether you appear. "Premium and well-reviewed" and "a cheaper alternative" are both mentions; only one helps you. Sentiment turns presence into positioning, and it's where a brand most often discovers the gap between how it sees itself and how the models summarise it.

| Answer-level metric | Question it answers | The trap if you ignore it |
|---|---|---|
| Share of voice | Do we appear, vs competitors? | Counting raw mentions with no benchmark |
| Citation rate | Is *our site* the source? | High presence, but others control the story |
| Sentiment | How are we framed? | Winning mentions that quietly hurt you |

## Layer two: what it drives

Presence is the leading indicator; this is the lagging one that earns the budget.

### 4. AI-referral revenue

Tie the AI traffic you *can* see to outcomes, not just sessions, but conversions and revenue. AI-referred visitors tend to arrive high-intent (they already got a recommendation), so this channel often punches above its session count. Reported as revenue, it's the line that turns "we're more visible" into "it's worth funding."

### 5. Dark-traffic index

The honest asterisk on metric 4. A large share of AI-driven visits arrive with no referrer and get filed as "Direct," so revenue measured on *visible* AI referrals understates the truth. A dark-traffic index. Estimated from deep-landing, new-user "Direct" sessions. Sizes the gap so you're not crediting AI with only the fraction you can see. (The full method is in [why your AI traffic shows up as "Direct."](/blog/why-ai-traffic-shows-up-as-direct))

> Layer one tells you *why* the revenue is moving; layer two tells you *whether* it is. Report either alone and someone can wave it away. Report both and the channel defends itself.

## How to read the stack together

The metrics are most useful as a diagnosis, not five separate gauges:

- **High SoV, low citation rate** → you're known, but third parties own the narrative. Fix your own citable content.
- **High presence, poor sentiment** → you appear in the wrong frame. This is a positioning and corroboration problem, not a coverage one.
- **Strong answer-level metrics, flat AI-referral revenue** → either attribution is leaking into "Direct" (check your dark-traffic index) or the answers cite you without sending traffic, which is still brand impact in a [zero-click](/glossary/zero-click-search) world.

Keep your existing SEO and analytics. They still feed AI Overviews and still count real visits. But add this layer on top, sampled across engines and tracked as a trend. Standing up the answer-level three by hand is slow and non-reproducible; doing it continuously, across every engine, is exactly what **Buffy Intel** is built to report.

## Anthropic passed OpenAI in business AI adoption: what it means for AEO
Source: https://heybuffy.com/blog/anthropic-overtakes-openai-business-adoption

Anthropic passed OpenAI in US business AI adoption for the first time in April 2026, according to **Ramp's AI Index**. Ramp reported Anthropic at **34.4%** of businesses (up 3.8 points month over month) against OpenAI's **32.3%** (down 2.9). A lead built on spending data across tens of thousands of US companies, reported on 13 May 2026. For anyone doing [answer engine optimisation](/glossary/answer-engine-optimization), the signal is simple: buyer attention is shifting toward Claude, which raises the stakes for being citable inside it.

**What this data is, and isn't.** The Ramp AI Index measures **paid business adoption**, inferred from real corporate-card and expense spending on Ramp's platform, not consumer usage, market share, or citation share. It is one company's transaction data, so it is directional and US-business-skewed. It is corroborated by independent coverage (Axios, VentureBeat, The Decoder, WinBuzzer, all mid-May 2026), which is why it is worth reading, but hedge it as a spending signal, dated to April 2026.

## What exactly did Ramp report?

The month-over-month shift, as Ramp reported it for April 2026:

| Provider | Share of businesses (Apr 2026) | Month-over-month change |
|---|---|---|
| **Anthropic** | **34.4%** | **+3.8 points** |
| **OpenAI** | **32.3%** | **−2.9 points** |

Source: Ramp AI Index, April 2026 data, reported 13 May 2026. The reversal is stark against a year earlier: per Ramp's underlying data, in April 2025 OpenAI held roughly **32%** of business adoption while Anthropic was **under 8%**. So Anthropic did not inch ahead. It closed a gap of more than 20 points in about a year.

## Why did Anthropic pull ahead?

Ramp and the coverage around it attribute the swing largely to one product: **Claude Code**, Anthropic's agentic coding tool, described as the fastest-growing product in the company's history. A separate analysis cited alongside the index estimated that around **4% of all public GitHub commits** were being authored by Claude Code. Roughly double the share of a month earlier (a third-party estimate, so treat it as illustrative, not audited).

The mechanism matters for AEO. Coding tools put a specific assistant. Claude. In front of technical buyers and their teams every day. Daily working use is exactly what builds the habit of asking that same assistant non-coding questions too, including "which tool should we use for X." That is how a developer tool becomes a discovery surface.

> Ramp's data measures where businesses spend, not where consumers chat. It says buyer attention at work is moving toward Claude, which is a reason to make sure Claude can find, cite, and recommend you.

## What does this mean for being cited in Claude?

It raises the commercial value of Claude visibility. If more of your buyers work inside Claude, then whether Claude can retrieve, cite, and recommend you stops being a niche concern. Two things follow:

- **Claude's discovery plumbing becomes business-critical.** Claude's web results lean heavily on Brave Search, so a site Brave cannot discover is one Claude struggles to cite. The mechanics are in [how Brave Search discovers your pages](/blog/how-brave-search-discovers-pages) and the practical checklist in [how to get cited in Claude](/blog/how-to-get-cited-in-claude).
- **Recommendation, not just mention, is the goal.** Being named in a Claude answer is not the same as being the recommended option. The distinction in [cited versus recommended in AI search](/blog/cited-vs-recommended-in-ai-search).

Crucially, this does **not** mean shift effort away from ChatGPT. Adoption share and citation share are different things: OpenAI still holds enormous consumer reach, and the engines cite different sources from different pools (see [how many sources each engine cites](/blog/how-many-sources-ai-engines-cite)). The honest read is *add* Claude to what you measure and optimise for, weighted by how much your own buyers use it, not swap one engine for another.

## Will Anthropic's lead hold?

Unclear, and worth hedging. VentureBeat's coverage flagged that several threats could erase the lead, and a single month of spending data is a fragile basis for a trend. Adoption among businesses is volatile, procurement decisions lag, and a strong product release from any provider can move the numbers again.

The durable takeaway is not "Claude won." It is that **business AI adoption is now genuinely multi-engine and moving fast**, so betting your visibility on one assistant is riskier than it was. That is the same lesson the corpus keeps reaching: measure presence and [citations](/glossary/citation) across every engine your buyers use, and track the trend rather than a single headline month. The discipline in [how to measure AI visibility](/blog/how-to-measure-ai-visibility).

## How should you act on this?

A short, honest response beats a scramble:

1. **Find out which assistants your buyers actually use**: don't assume; ask, and check your own AI-referral data.
2. **Confirm Claude can reach you**: that you aren't [blocking its crawler path at the CDN](/blog/is-your-cdn-blocking-ai-crawlers) and that Brave can discover your pages.
3. **Measure your citation and recommendation share in Claude and ChatGPT side by side**, weighted to your buyer mix, over time.

That last step is the loop that closes it. Knowing whether Claude, ChatGPT, and the rest actually surface, cite, and recommend *your* brand. Tracked daily across every engine rather than spot-checked. Is exactly what **Buffy Intel** is built to measure.

## Are agentic browsers safe for your site? What the same-origin-policy finding means for brands
Source: https://heybuffy.com/blog/are-agentic-browsers-safe-for-your-site

Agentic browsers are not yet safe to trust with sensitive tasks on your site, and a 2026 study puts a sharp finding on why. Researchers at the University of Washington tested seven agentic browsers and found **four of them let a malicious web page bypass the same-origin policy** — the roughly 30-year-old browser rule that stops one site from reading another's data. They demonstrated a working data-theft attack against ChatGPT Atlas. For brands this is not just a browser-security story: agents now **read and act on your pages**, so content on the page — an ad, an embed, a user review — can be turned against the person the agent is working for.

**Last reviewed: 27 August 2026.** The core findings below are from a University of Washington (Paul G. Allen School) study presented at the Agents in the Wild workshop in April 2026 and reported by UW News on 30 June 2026. It is a **single-study, directional** analysis of a fast-moving surface, so read the *pattern* as firmer than any one detail and cite "University of Washington, 2026" with the date when you reuse it. Which browsers are affected will change as vendors patch; treat the named list as a mid-2026 snapshot.

## What did the University of Washington study actually find?

That the browser boundary most of the web relies on weakens when an AI agent drives the browser. The [same-origin policy](/glossary/same-origin-policy) has kept sites isolated since 1995; the study found agents can be talked into stepping across it.

| Finding | Detail |
|---|---|
| Agentic browsers tested | **7** |
| Browsers that allowed a same-origin-policy bypass | **4** |
| Browser with a demonstrated data-theft attack | **ChatGPT Atlas** (proof-of-concept) |
| Others where the conditions were found | Chrome with Gemini, Claude for Chrome, Perplexity Comet |
| Same-origin policy in use since | **1995** (~30 years) |

Source: University of Washington, 2026. In the demonstrated attack, one website embedded inside another was able to steal information from it — the researchers' analogy is an ad on an email page reaching in and reading the email. The same-origin policy is exactly the rule that is supposed to make that impossible, which is why the researchers framed the result as a meaningful step back for browser security after decades of hardening.

## Why does this matter if agents read my pages?

Because the protection now depends on the agent resisting [prompt injection](/glossary/prompt-injection), and pages are where injected instructions live. Prompt injection is when an attacker hides instructions inside content a model reads, and the model treats them as if they came from the user. An [agentic browser](/glossary/agentic-browser) reads the live page as part of doing its job, so any text on that page — visible or hidden — is a potential instruction.

The University of Washington finding is that, in the affected browsers, the same-origin policy effectively reduces to the strength of the agent's prompt-injection defenses. If a page can trick the agent, it can make the agent cross a boundary that used to be absolute. That reframes the risk for a brand: the security of an agent acting on your site is partly a function of **what your own pages carry**.

> When an agent obeys the page it is reading, your website is not just where you get discovered — it is a surface where a visitor's agent can be given instructions you never wrote.

Three parts of a typical brand page are the realistic vectors: **user-generated content** (reviews, comments, Q&A), **third-party embeds and ads** you do not fully control, and **hidden or injected text** placed by an attacker who found a way onto the page. None of these are exotic; they are on most commercial sites today.

## Is this a browser problem or my problem too?

Both, and the brand half is the part you can act on. You cannot patch the browser — that is the vendors' job, and they are working on it. Anthropic, for example, reported cutting prompt-injection attack success from about **23.6% to 11.2%** by stacking two independent defenses (scanning content before the model reads it and blocking risky actions at execution); it reduces the risk without eliminating it. And this is not only a lab result: Palo Alto Networks' Unit 42 has reported observing web-based indirect prompt injection against AI agents **in the wild** in 2026, not just in controlled tests. Treat both as attributed, directional signals, not settled numbers.

What you *can* control is whether your own pages are a clean surface for the agents that visit them. That is a new item on the brand's list, adjacent to two threats we already cover: [answer poisoning](/blog/protect-your-brand-from-ai-answer-poisoning), where false content is seeded into the sources engines retrieve *about* you, and the broader question of [whether AI search can be manipulated](/blog/can-ai-search-be-manipulated) at the corpus level. This one is different — it is on *your* page, aimed at *your* visitor's agent, during a live session — but the defensive instinct is the same: control your first-party surface.

## What should brands do about it now?

Keep optimizing for the surface, and add page hygiene as a second job. The security finding does not argue for blocking agents — it argues for keeping your own pages clean enough that they cannot be weaponised.

- **Do not stop being visible to agents.** Agentic browsers are a growing discovery-and-checkout surface; the fundamentals of [showing up in one](/blog/what-is-an-agentic-browser) and [being selectable by an agent](/blog/optimize-for-agentic-browsers) — extractable facts, completable flows, [structured data](/glossary/structured-data) — are unchanged.
- **Treat your own UGC and embeds as an attack surface.** Reviews, comments, and third-party widgets are where injected instructions hide. Sanitising them protects your visitors, not just your rankings — the [page-hygiene playbook](/blog/protect-your-site-from-agent-hijacking) has the specifics.
- **Be realistic about the agent-checkout timeline.** Cautious users and enterprises will limit what they let an agent do on any site until the security matures, so weight your near-term expectations for agent-completed purchases accordingly, without abandoning the [readiness work](/blog/discover-in-ai-buy-on-your-site).
- **Watch the finding, not the panic.** Which browsers are affected will change as vendors patch. Track the state of the surface over time rather than reacting to a single headline.

The honest read for late 2026: agentic browsers are a real and rising surface for your brand, and the same surface carries a security weakness that makes your own page hygiene part of the job. Being visible to agents and being safe for the people those agents work for are now the same project — and knowing how your brand is surfaced across these AI surfaces, over time, is exactly what **Buffy Intel** is built to measure. Questions: support@flash.tech.

## How to audit your content for information gain
Source: https://heybuffy.com/blog/audit-your-content-for-information-gain

**An information-gain audit finds the pages that only restate what already ranks — the ones AI engines read and skip — and shows you where to add the original data, first-hand detail, or unique synthesis that earns a citation.** The method below is a repeatable, five-step review you can run without a special tool: score each page for what it *adds*, flag the commodity content, and fix the highest-value gaps first.

**Last reviewed: 28 August 2026.** This is a method built on how AI engines select passages (chunk-level retrieval that filters redundant content) and on the [information gain](/glossary/information-gain) concept from Google's patent literature. It reconciles our existing guidance on [what content changes lift AI citations](/blog/what-content-changes-lift-ai-citations) into an audit you can run on your own corpus.

## How do you audit a page for information gain?

Compare the page against the pages already answering the query, and measure the gap. Work one target query per page, in five steps:

1. **Run the query and read the field.** Search the query your page targets and open the pages currently ranking or being cited in AI answers. These are what an engine already has.
2. **List the shared consensus.** Write down every fact, claim, and number that appears across those pages. This is the information an engine can already assemble without you.
3. **Mark what your page adds.** Read your page and highlight only what is *not* on the shared list — an original datapoint, a first-hand result, a worked example, a detail no competitor covers.
4. **Score the gap.** If step 3 is empty, the page has low information gain (commodity content). If it holds one or more unique, verifiable facts, it has real gain. Rank your pages by that gap.
5. **Fix highest-value first.** Prioritise pages where you have original evidence to add and that already get crawled but not cited — the fastest commodity-to-citable moves.

The output is a list of pages sorted by how much they add, not by traffic or length. That sort is the audit.

## Which pages have low information gain?

The commodity pages share a fingerprint. Use this table to flag them fast during the audit:

| Signal | What it looks like | Why it fails |
|---|---|---|
| **Restated consensus** | Every claim also appears on the top competitors | Adds nothing to the answer shortlist |
| **No original evidence** | No first-hand data, tests, or examples | Nothing unique for a model to lift |
| **Padded length** | Long, but high word-to-fact ratio | Low signal-to-noise; length is not gain |
| **Rewritten source** | A paraphrase of one or two ranking pages | Duplicate of what the engine already has |
| **Crawled, not cited** | AI bots hit it; citations stay flat | Read and passed over as redundant |

A page matching two or more rows is commodity content — it duplicates the field and will keep being skipped. The last row is the leading indicator: heavy [crawler activity](/blog/how-to-see-which-ai-bots-crawl-your-site) with no citations often means the content is being evaluated and rejected for redundancy, not for reachability.

> The fastest way to find your low-gain pages is to ask, for each one: if this page vanished, would the answer to its query be any worse? If not, an engine already agrees — that is why it is not citing you.

## How do you add information gain to a thin page?

Give the page something the field does not have, then make it liftable. In priority order:

- **Add original data.** A number from your own logs, a test result, or a small study is the highest-value gain because no competitor can copy it.
- **Add first-hand detail.** A worked example, a screenshot-backed walkthrough, or an expert observation from real use — [experience](/glossary/e-e-a-t) the ranking pages lack.
- **Resolve a contradiction.** Where sources disagree, do the reconciliation on the page; a synthesis that settles a real conflict is new information in itself.
- **Cut the restated middle.** Remove boilerplate that repeats the consensus so the unique material stands out and signal-to-noise rises.
- **Make the unique fact extractable.** State it specifically, numerically, and dated in a sentence or table a model can lift whole — the [extractable-chunk](/blog/structure-content-into-extractable-chunks) discipline — and [corroborate](/glossary/corroboration) it so it is safe to quote.

Re-score the page after editing: read the field again, and confirm your page now holds at least one fact the ranking pages do not. If it does, you have moved it from commodity to citable.

## How often should you re-run the audit?

Put competitive pages on a refresh cadence, because information gain erodes as the rest of the field catches up. A datapoint that was unique when you published it becomes consensus once competitors copy it, and a page that once stood out slides back to commodity. That is the same [content-decay](/glossary/content-decay) cliff that pulls stale pages out of AI answers — from the content side rather than the freshness side.

- **Competitive, fast-moving pages:** re-audit each quarter; the field moves and your gain shrinks.
- **Evergreen or definitional pages:** re-audit rarely — do not churn stable content just to restate it.
- **After any ranking or citation drop:** audit the affected pages for gain before assuming a technical cause, and fix the content the durable way rather than [spam-proofing a healthy page](/blog/grow-ai-visibility-without-spam).

An information-gain audit turns "write better content" into a concrete, repeatable pass: find the pages that add nothing, add something real, and make it liftable. Tracking whether those edits actually earn citations — across ChatGPT, Google AI Overviews, Perplexity, and Claude, over time — is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Beyond RAG: AI search is going agentic
Source: https://heybuffy.com/blog/beyond-rag-agentic-ai-search

The first wave of AI search was [RAG](/glossary/retrieval-augmented-generation): retrieve relevant passages, synthesise one cited answer. The next wave is **agentic**: the engine doesn't just fetch and summarise, it **plans, browses, compares, uses tools, and acts** to complete a task. That shift changes what content has to do.

## From answering questions to completing tasks

A RAG system answers "what's the best fragrance-free moisturizer for eczema?" An agentic system handles "find one under $30, check it's in stock, and add it to my cart." It plans the steps, runs its own [fan-out](/blog/how-query-fan-out-works) of searches, browses pages, compares options against your stated criteria, and increasingly **takes the action**.

So the unit of success moves from "did I get a good answer?" to "did the agent complete the task. Using my brand?"

## What it means for your content

- **Completeness over a single page.** An agent traverses multiple pages to finish a task. Thin or partial coverage drops you out mid-task. Build [intent-complete](/blog/how-query-fan-out-works) coverage.
- **Machine-readable facts.** Agents act on [structured data](/glossary/structured-data). Specs, price, availability, attributes, not your hero imagery. If the fact an agent needs isn't extractable, you're skipped.
- **Be actionable, not just visible.** Being *mentioned* isn't enough if the agent can't *do* anything with you. For commerce, that means being [transactable](/blog/what-is-agentic-commerce). Discoverable, complete, and buyable.
- **Agent Experience (AX).** The emerging discipline of designing your site for AI agents the way UX designs for humans: clear structure, stable identifiers, machine-readable everything.

> RAG asked "is your content findable and citable?" Agentic search adds a harder question: "can an agent *act* on it?" Visibility is the entry ticket; actionability is the new bar.

## The throughline

Agentic search is why the same fundamentals keep compounding. Reachable, structured, complete, authoritative content, and why [agentic commerce](/blog/what-is-agentic-commerce) is the sharpest version of the trend: there, the agent doesn't just recommend you, it buys from you. Either way, the brands that get chosen are the ones a machine can fully read and reliably act on.

Watching how you're surfaced as engines turn agentic. Recommended, cited, and (soon) transacted. Is the frontier **Buffy Intel** tracks.

## What Bing Webmaster Tools' new AI data tells you (and what it can't)
Source: https://heybuffy.com/blog/bing-webmaster-tools-ai-visibility

Bing Webmaster Tools quietly became one of the few **free, first-party** windows into how an AI engine uses your content. As of June 2026 it reports which AI "grounding queries" cited your site, what share of citations you captured, the intent behind those queries, and the topics Microsoft's systems associate with you. That's real evidence most teams aren't looking at, but it answers a narrower question than it first appears.

This is part of the [measuring AI visibility](/blog/from-clicks-to-citations) series; it assumes you already know *why* citations replaced rankings and focuses on one concrete data source.

## What does Bing Webmaster Tools now report about AI?

Microsoft launched an **AI Performance report** in public preview in **February 2026**, surfacing the grounding queries (the searches an AI surface runs to ground its answer) where your site was cited. In **June 2026** it added four capabilities, rolling out in preview globally:

| Feature | What it shows |
|---|---|
| Intents | Grounding queries classified by intent. Informational, Commercial, Navigational, Research, Local, "Learn and Solve," Creation, and more |
| Topics | A thematic view that groups grounding queries into subject areas where you're gaining (or missing) AI visibility |
| Citation Share | The percentage of AI citations your site captured for a grounding query, out of all citations shown across all sites for it |
| Compare | An overlay of a previous period (e.g. the prior 30 days, or a custom range) to see how citation activity changed |

All figures are attributed to Microsoft's Bing Webmaster blog and corroborating coverage (Search Engine Land, Search Engine Journal) from June 2026. The headline addition is **Citation Share**: your share of citations on a query, not just a raw count, which is the closest a free tool gets to an answer-level [share of voice](/glossary/share-of-voice).

## Why does this data matter when it's "only" Bing?

Because Bing is bigger than its consumer search share suggests, and its index feeds AI you care about. Microsoft's web index powers **Copilot** across Windows and Microsoft 365, and, as reported through 2026. Is among the web-results providers **ChatGPT Search** can draw on. So a grounding query that cited you in Bing's data is direct evidence your content is retrievable and quotable in the kind of pipeline several assistants share. It's a proxy, not a guarantee. Hedge it, but a free proxy backed by first-party data beats inference.

The most useful, least-obvious move is to read **Intents and Topics as prompt research.** Most teams build a tracking list by brainstorming questions; AI answers are instead assembled from retrieval paths and [query fan-out](/glossary/query-fan-out). When Bing groups your citations by intent and topic, it's handing you first-party evidence of the *clusters* AI already associates with your content. A better starting point than a guess. That feeds directly into [how to choose which prompts to track](/blog/how-to-choose-prompts-to-track) and the wider question of [how to measure your AI visibility](/blog/how-to-measure-ai-visibility).

## What can't it tell you?

This is where most read it wrong. Citation Share tells you how you did on queries where you *already appeared*; it is silent on the more valuable question, where you should appear but don't.

> Bing Webmaster Tools answers "how did we do?", not "where should we appear but don't?" It's a free first-party signal, not a cross-engine scoreboard, and the gap is the whole game.

Concretely, the report does **not** show:

- **The exact prompts** users typed. You see grounding queries and intents, not the raw conversation.
- **The full AI answer** your content appeared in, or whether you were *recommended* versus merely cited (a distinction that matters. See [cited isn't recommended](/blog/cited-vs-recommended-in-ai-search)).
- **Visibility across other engines**: Google AI Overviews, Gemini, Perplexity, and Claude are all outside it.
- **The "should" list**: the topics and queries where you're absent entirely, which by definition can't show up in a report of where you were cited.

So treat it as one strong input, not the system of record. It's the AI-era counterpart to reading your server logs to see [which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site): authoritative for what it covers, blind beyond it.

## How to use it in a real workflow

Fold the Bing data into the reporting stack rather than treating it as the whole picture:

1. **Verify your site** in Bing Webmaster Tools (free) and open the AI Performance report.
2. **Read Topics for authority and gaps**: note where you're gaining citation share and which adjacent topics are thin.
3. **Turn Intents into prompts**: use the commercial and "learn and solve" clusters to seed realistic prompts, then validate them against actual customer language.
4. **Use Compare for trend, not snapshots**: citation activity is noisy; a 30-versus-30 overlay shows direction.
5. **Cross-check across engines**: Bing covers Microsoft's surfaces; pair it with the broader [five-metric reporting stack](/blog/ai-visibility-reporting-stack) so a single engine doesn't define your view.

Bing Webmaster Tools is the rare free, first-party AI signal. Worth wiring in today. But "how did we do on Bing?" is one engine's slice of a question that spans all of them: where are we recommended, across every AI surface, over time? Closing that gap. Turning per-engine signals into one cross-engine scoreboard. Is exactly what **Buffy Intel** does. Questions: support@flash.tech.

## Brand-mention gap vs source gap: the two-lens AI-visibility audit
Source: https://heybuffy.com/blog/brand-mention-gap-vs-source-gap

There are two distinct ways to be invisible in AI search, and they have opposite fixes. Either the engine **never names your brand** in answers to your customers' questions (a brand-mention gap), or it covers your topic but **never cites your pages** as the source (a source gap). Measuring only one hides half the problem. This two-lens audit. Part 7 of the measuring series. Separates the demand side from the supply side so your fixes land where the gap actually is.

## What are the two lenses?

Each lens answers a different question about the same set of AI answers:

| Lens | The question it answers | What a low score means |
|---|---|---|
| Brand-mention gap | Across my customers' prompts, how often am I **named or recommended**? | Demand-side: weak presence, reputation, or entity strength |
| Source gap | When the answer covers my topic, how often are **my pages cited** as the source? | Supply-side: weak extractability, reachability, or freshness |

The first lens is about [share of voice](/glossary/share-of-voice) and [total mentions](/glossary/total-mentions). Am I in the conversation at all? The second is about [citation coverage](/glossary/citation-coverage). When the conversation happens, is my content the supply that feeds it? They move independently, which is the whole point.

## Why measure both separately?

Because the same overall "we're invisible" symptom has two unrelated causes, and treating the wrong one wastes a quarter. The four combinations:

- **Named and cited**: healthy; defend it with freshness.
- **Cited but not named**: your page feeds the answer, but a competitor is recommended. This is the [cited-isn't-recommended](/blog/cited-vs-recommended-in-ai-search) pattern: an entity or corroboration problem, not a content one.
- **Named but not cited**: the model "knows" you from training, but live retrieval pulls others' pages. A content extractability and freshness problem.
- **Neither**: the hardest case; start with reachability and entity basics.

> Knowing your overall AI visibility is "low" tells you nothing actionable. Knowing whether the gap is *demand* (you're not named) or *supply* (you're not cited) tells you exactly which team owns the fix.

## How do you perform the audit?

Snapshot the same prompt set across engines on a schedule and score each lens. A workable method:

1. **Build the prompt set.** 30-50 real customer questions across the [fan-out](/blog/how-query-fan-out-works) branches. Brand, category "best X," comparison, and how-to intents. [Choosing the right prompts](/blog/how-to-choose-prompts-to-track) is most of the value here.
2. **Snapshot across engines.** Capture answers for each prompt on ChatGPT, Google AI Mode, Perplexity, and others. Repeated captures, not one, since answers are non-deterministic.
3. **Score lens 1 (mentions).** For each prompt, was your brand named? Recommended? Compute a mention rate and a recommendation rate per engine.
4. **Score lens 2 (sources).** For prompts about your topic, what share of cited sources are your pages versus third parties versus competitors?
5. **Map each gap to its fix.** Mention gaps → entity clarity, [corroboration](/glossary/corroboration), earned coverage. Source gaps → extractable answer-first pages, [reachability](/blog/is-your-cdn-blocking-ai-crawlers), and a [freshness cadence](/blog/content-freshness-citation-cliff).

## What do you do with the result?

Rank fixes by which lens is weakest and which prompts are highest-intent. A brand strong on sources but weak on mentions should invest in [entity strength and earned placement](/blog/get-into-ai-cited-best-lists), not more content. A brand named everywhere but rarely cited should fix [extractability and freshness](/blog/how-to-get-cited-by-ai) on existing pages. Re-snapshot quarterly and watch both scores trend. A source score that slips is the early warning that pages are decaying out of answers. Tracking both lenses continuously, across every engine, with fixes prioritised by impact, is exactly what **Buffy Intel** measures.

## How to calculate your own crawl-to-refer ratio (per AI bot)
Source: https://heybuffy.com/blog/calculate-your-crawl-to-refer-ratio

The public [crawl-to-refer ratios](/glossary/crawl-to-refer-ratio) are network-wide averages, and your site can sit far from them. Computing your own takes two data sources you already have, server or CDN logs for the crawl side and analytics for the referral side, divided over the same window. This is the hands-on companion to [how many pages each AI bot crawls per visitor](/blog/how-many-pages-ai-crawlers-take-per-visitor); read that for the benchmark figures. Below is the method, in five steps.

## Step 1: Count crawler hits per operator from your logs

Pull every request from verified AI crawler user-agents over a fixed window (use 28 days to match the public data). Your server access logs or CDN bot analytics record each one. Group the hits by operator, not just by bot name, since one operator often has several tokens:

| Operator | User-agent tokens to sum |
|---|---|
| OpenAI | `GPTBot`, `OAI-SearchBot`, `ChatGPT-User` |
| Anthropic | `ClaudeBot`, `Claude-SearchBot`, `Claude-User` |
| Perplexity | `PerplexityBot`, `Perplexity-User` |
| Google (AI) | `Google-Extended` (training) + AI-Mode/AIO fetches |
| Microsoft | `BingBot` (shared with Copilot) |

Count only HTTP 200 responses, so a block doesn't inflate the picture, and confirm the requests really come from the operator's published IP ranges rather than a spoofed string. Our guide to [seeing which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site) covers the filtering and IP-verification mechanics in detail.

## Step 2: Count AI referrals per operator from analytics

For the same dates, count the sessions each operator's assistant sent you. Web-based engines usually arrive with a referrer (`perplexity.ai`, `chatgpt.com`, Google AI surfaces), so a referrer filter or a dedicated AI channel captures them. A large share of AI visits carry no referrer and fall into "Direct," so add an estimate for that dark slice rather than ignoring it. The fastest way to stand this up is the [GA4 AI-referral dashboard](/blog/ga4-ai-referral-dashboard), which builds both the visible channel and a dark-traffic estimate.

Keep the operators separate. You want ClaudeBot's crawls matched to Anthropic's referrals, not one blended total, because the ratios differ by an order of magnitude between operators.

## Step 3: Divide, per operator

For each operator, divide total crawler hits by total referral sessions over the window:

**crawl-to-refer ratio = crawler HTTP-200 hits ÷ AI referral sessions**

A result of 900:1 means the operator fetched about 900 of your pages for each visitor it sent. Do this per operator and you get your own version of the public table, tuned to your site. If an operator sent zero referrals but crawled heavily, note the ratio as "crawl-only" rather than dividing by zero; that is common and expected for training-first bots.

> Match the crawl side and the referral side to the exact same 28-day window, and always split by operator: a blended ratio hides the ten-fold gap between a training-first bot like ClaudeBot and a search-backed one like Google.

## Step 4: Benchmark against the public figures

Compare your per-operator ratios to the mid-2026 public numbers (Cloudflare Radar, window ending 21 July 2026): roughly **2,237:1** for Anthropic, **217:1** for OpenAI's GPTBot, **225:1** for Perplexity, **35:1** for Microsoft, and **4.6:1** for Google. What the comparison tells you:

- **Much higher than the benchmark** usually means strong crawling but weak referral capture, often a [dark-traffic](/glossary/dark-traffic) measurement gap, not a visibility problem. Fix the measurement before drawing conclusions.
- **Much lower than the benchmark** can mean the crawler isn't reaching you at all (check for [robots.txt](/glossary/robots-txt) or CDN blocks), so your denominator is small because you're barely crawled.
- **In line with the benchmark** is the common, healthy case: you're being learned at the normal rate.

## Step 5: Track the trend, not the snapshot

Recompute monthly against the same 28-day window and watch the direction. The public ratios fell sharply across 2026 as AI assistants matured into click-sending search products; your own ratio should drift down too as engines send you more referrals. A steadily falling ratio is good news. A ratio that spikes is usually a training pass, harmless, while a crawl side that suddenly drops to near zero is worth investigating as a possible block.

Do not treat any single month as a verdict. The number is context for two separate questions, can AI reach me, and does AI cite me, and only the second is the real goal. Heavy crawling with no citations is [a leading indicator, not a failure](/blog/chatgpt-citation-lag); the point of tracking the ratio is to confirm the crawl is happening while you [measure the citations](/blog/from-clicks-to-citations) that actually matter.

Computing the ratio once is a useful audit; watching it, your citations, and your AI referrals move together across engines is the ongoing job that **Buffy Intel** is built for. Questions: support@flash.tech.

## Can AI search be manipulated? What the 'gullibility' tests reveal for brands
Source: https://heybuffy.com/blog/can-ai-search-be-manipulated

Can you trick an AI engine into repeating something untrue about a market, or a brand? An informal 2026 experiment says: sometimes, for a while. The more useful lesson is *why it doesn't last*, and what that tells brands about earning durable visibility.

## What the experiment found

SEO practitioner **Lily Ray** ran an informal test in 2026: she invented absurd, never-before-searched questions. Like which SEO is "best at eating spaghetti". Published satirical rankings, and watched which engines repeated them. The reported pattern:

- **Google's AI Overviews, Gemini, and AI Mode** stated the made-up answers, but flagged the source as "informal," "playful," or "lighthearted."
- **Claude and Perplexity** were **less likely** to use the brand-new article, apparently because the questions were highly specific and lacked any consensus across sources.

It's a single, informal experiment on questions engineered to have no real answer, and engine behaviour shifts constantly, so treat it as directional. But the mechanism it exposes is the durable part.

## Why the manipulation doesn't hold

The made-up rankings worked, where they worked, only because **nobody else had answered the question**. In a vacuum, an engine has one source to draw on, so it draws on that one. The moment a question has real coverage, that fragile advantage disappears.

> A claim with no corroboration can fill an empty space, but it can't survive contact with other sources. The engines that refused the bait were the ones waiting for *consensus*, not a single confident voice.

This is the same retrieval filter behind [why AI cites one brand and ignores a near-identical competitor](/blog/why-ai-cites-one-brand): models weight **corroboration across credible sources** heavily, precisely because a lone assertion is easy to fake and hard to trust. Manipulation exploits the gaps; corroboration closes them.

## What this means for your brand

The takeaway isn't "go seed claims about yourself", that's the fragile move the experiment exposes. It's that **the thing protecting you from manipulation is the same thing that earns you citations**: being corroborated.

| If your goal is… | The losing move | The durable move |
|---|---|---|
| Get recommended | Publish self-serving claims and hope | Earn agreement from independent sources |
| Defend your reputation | React to each bad mention | Build [entity strength](/blog/entity-strength-ai) so one voice can't overwrite consensus |
| Fix a wrong description | Restate it on your own site only | Get credible third parties to state it too |

If an engine is repeating something wrong about you, the fix isn't to shout louder on your own pages. It's corroboration. (We cover the mechanics in [what to do when AI gets your brand wrong](/blog/fix-wrong-ai-description).) And if a competitor is being described too generously on the strength of thin claims, that advantage is the unstable kind; the brand with broad, consistent third-party agreement wins over time.

## The practical defense

- **Be consistent everywhere.** State the same facts about yourself across your site, profiles, and listings. Engines lock onto consistent [entities](/glossary/entity-authority).
- **Earn corroboration.** Reviews, independent roundups, and credible mentions that agree with your own claims are what survive scrutiny. [How to get cited](/blog/how-to-get-cited-by-ai) is mostly this.
- **Monitor across engines.** Manipulation and errors both show up as *something wrong in an answer*. You can only correct what you can see.

The honest conclusion: AI search can be nudged in the gaps, but it can't be durably gamed where corroboration exists, so the winning strategy is to *be* the corroborated answer. Seeing what every engine currently says about your brand, and catching it when it drifts, is exactly what **Buffy Intel** monitors.

## Can you charge AI agents to crawl your site? The x402 pay-per-crawl model
Source: https://heybuffy.com/blog/can-you-charge-ai-agents-to-crawl

**A third option is emerging between letting AI crawlers in free and blocking them: charging them.** As of mid-2026, Cloudflare's **Monetization Gateway** (in waitlist) lets a site quote a price for a page, dataset, API, or MCP tool and settle it in [stablecoins](/glossary/stablecoin) over the open [x402](/glossary/x402) protocol, which revives the HTTP `402 Payment Required` status. A crawler requests a resource, receives a `402` with the price, pays, and retries with proof attached. It is metered, per-request access — a middle posture that classic [robots.txt](/glossary/robots-txt) blocking never offered.

This piece explains how pay-per-crawl works, who is building it, and how to weigh charging for access against wanting to be cited. The products named are early and gated, so read this as the shape of an emerging option, dated to mid-2026, not a settled control.

## What is pay-per-crawl?

Pay-per-crawl charges an [AI crawler](/glossary/ai-crawler) for each fetch, instead of allowing or denying it for free. Today most sites face a binary: robots.txt or a CDN rule either lets a bot in (you earn nothing) or shuts it out (you get nothing and forfeit citations). Pay-per-crawl inserts a third state — the bot can reach the content, but only after paying a price you set, settled automatically inside the request.

The mechanism is [x402](/blog/what-is-x402), the HTTP-native payment standard the Linux Foundation began stewarding in July 2026. When a paid resource is requested, the server answers `402 Payment Required` with a small payload naming the price, the accepted asset, and where to pay. The client pays — typically a stablecoin such as USDC, clearing sub-second — and retries with proof. No login, no checkout page, no invoice.

## Who is building pay-per-crawl?

Cloudflare is furthest along, and it is not alone. Cloudflare first shipped **Pay Per Crawl** in 2025 as a way to charge AI bots for content, alongside a July-2025 shift to [blocking AI crawlers by default](/blog/is-your-cdn-blocking-ai-crawlers) for new domains. In mid-2026 it generalised that into the **Monetization Gateway**: in its own words, "instead of only charging crawlers for content, you will be able to charge any caller for any resource" — pages, datasets, APIs, or MCP tools — settled in stablecoins over x402.

| What | Detail (mid-2026) |
|---|---|
| Product | Cloudflare Monetization Gateway |
| Status | Waitlist; no general-availability date disclosed |
| Charges for | Web pages, datasets, APIs, MCP tools behind Cloudflare |
| Protocol | x402 (HTTP `402`; open standard under the Linux Foundation) |
| Settlement | Stablecoins (USDC), sub-second |
| Predecessor | Cloudflare Pay Per Crawl (2025) |

Source: Cloudflare's Monetization Gateway announcement and x402 documentation, mid-2026 (waitlist-stage; details subject to change). Cloudflare and AWS both moved to embed x402 micropayments at the network edge within roughly two weeks of each other, per InfoQ reporting in July 2026, which is why edge-level metering — not a per-site plugin — is the likely shape of this.

**Update (Aug 2026): from pay-per-crawl toward pay-per-answer.** On 1 July 2026 Cloudflare signalled a further shift — charging AI companies not for each fetch but for when content is **actually used to answer a question**, a "pay-per-use" model. Its stated reason: more than half of legitimate crawl traffic re-fetches pages that have not changed, so per-fetch pricing charges for the wrong thing. The same announcement set a **15 September 2026 default** that blocks AI training and agent crawlers on ad-bearing pages for new and free sites while leaving search crawlers allowed. Both moves are covered in [Cloudflare's September 2026 default-block](/blog/ai-crawler-default-block-2026); they evolve, rather than replace, the metered-access idea below (attributed to Cloudflare, dated, single-operator).

## Why would a site charge crawlers at all?

Because AI crawlers take far more than they give back. Cloudflare notes that AI crawlers "already request content anywhere from a hundred to tens of thousands of times for every visitor they send back" — the extraction-heavy pattern our [crawl-to-refer ratio](/blog/how-many-pages-ai-crawlers-take-per-visitor) data quantifies, with pure-AI bots crawling thousands of pages per referral. When reading rarely turns into a visit, some publishers would rather be paid for the reading.

Metering also gives leverage that robots.txt lacks. A [disallow rule is only a request](/blog/how-often-do-ai-crawlers-ignore-robots-txt), which a rising share of crawlers ignore; a price enforced at the edge is a wall with a turnstile. For owners of genuinely valuable data — archives, proprietary datasets, paid APIs — charging is a way to turn heavy crawling into revenue instead of cost.

## Should you charge AI agents, or stay open for citations?

It depends on whether a given page's value is as *data* or as *visibility* — and for most marketing content, it's visibility. A price gate that a crawler won't pay removes you from the free AI answer entirely, and being [cited and recommended](/blog/should-you-let-ai-crawlers-index-your-site) in that answer is usually worth more than a micropayment. Charge the wrong pages and you buy pennies while losing the discovery that drives the business.

> Pay-per-crawl is powerful for content that is a product, and self-defeating for content that is a billboard. The skill is knowing which of your pages is which.

A workable split for most sites:

- **Keep open** — educational, marketing, and product pages whose job is to be discovered, cited, and recommended by AI. Citations live in the free tier.
- **Consider metering** — proprietary datasets, research archives, and APIs that are genuinely a product, and that AI operators crawl heavily without referring traffic back.
- **Measure either way** — track whether metered resources still get requested (demand at your price) and whether open pages still get cited (visibility preserved).

The deeper point is that charging for access and earning citations are two different games, and most brands are still playing only for citations. Whether AI agents and answer engines actually surface, cite, and recommend the pages you keep open is exactly what **Buffy Intel** measures, snapshot over snapshot. Questions: support@flash.tech.

## Cards vs stablecoins: how will AI agents pay?
Source: https://heybuffy.com/blog/cards-vs-stablecoins-agent-payments

Two settlement rails are being built for [agentic checkout](/blog/what-is-agentic-commerce) at the same time: tokenised **card credentials** and **stablecoins**. As of mid-2026, the likely outcome isn't one winner but a split by use case. Cards lead consumer-facing agent shopping, stablecoins lead machine-to-machine micropayments. This is a neutral comparison of where each fits, and why neither settles the question that matters most to a brand.

## What are the two rails, in one line each?

- **Tokenised cards**: the existing Visa/Mastercard networks, extended so an agent transacts with a scoped, single-purpose token instead of your real card number. Covered in depth in [the card-rail explainer](/blog/agentic-commerce-payment-rails).
- **Stablecoins**: dollar-pegged crypto tokens settled on a blockchain, letting an agent pay instantly and programmatically, below the card-fee floor. Covered in [the stablecoin explainer](/blog/stablecoins-agentic-payments).

Both are real and shipping in early forms. The question is which fits which job.

## How do cards and stablecoins compare for agent payments?

The criteria that actually matter to a merchant or brand, compared even-handedly. Figures are reported and directional as of mid-2026:

| Criterion | Tokenised cards | Stablecoins |
|---|---|---|
| **Per-transaction cost** | Fixed floor ~$0.30; fine for normal orders, uneconomic for sub-cent payments | Fraction of a cent on some chains; suited to micropayments |
| **Settlement speed** | Fast authorisation; funds settle on network timelines | Near-instant, on-chain, programmatic |
| **Reversibility** | Mature chargeback / dispute machinery | Generally final once settled; disputes not built in |
| **Consumer protection** | Established (fraud rules, liability shifts) | Emerging; depends on the wallet/guardrail layer |
| **Human-approval model** | Reported human confirmation for most consumer purchases at launch | Approval mandates and scoped limits still emerging |
| **Maturity / adoption** | Large, embedded in assistants (e.g. reported Visa-ChatGPT integration) | Tiny but growing; ~$73M agent volume May 2025-Apr 2026 (Keyrock via CoinDesk) |
| **Best-fit use case** | Consumer purchases inside an assistant | Machine-to-machine, agent-to-API, high-frequency payments |

The pattern is complementary, not competitive: cards bring reach and consumer-protection machinery; stablecoins bring machine-speed, machine-cost settlement. Expect a shopper's grocery order to clear on a card and an agent's per-call API payment to clear in a stablecoin.

## Which standards sit on top of each rail?

Both rails are being wrapped in agent-payment standards, and they overlap:

- **Card-leaning:** Mastercard's **Agent Pay** (and its June 2026 *Agent Pay for Machines*) extends tokenisation to verified agents.
- **Stablecoin-leaning:** **x402** (HTTP-402 micropayments) is stablecoin-native.
- **Rail-agnostic:** Google's **AP2** (Agent Payments Protocol) is reported to support both cards and stablecoins.

None has converged into a single standard as of mid-2026. A brand doesn't need to bet on one. The transaction layer is being built to be plural.

> Cards and stablecoins are two rails to the same destination: moving money once an agent has decided to buy. Winning that decision happens a layer up, and neither rail touches it.

## So which should a brand optimise for?

Neither, because this is the wrong layer to optimise for visibility. The rail is settlement infrastructure; it moves money after the choice is made. Which product an agent surfaces and picks still turns on catalog richness, [entity strength](/blog/entity-strength-ai), reviews, and corroboration. The [answer-engine optimisation](/glossary/answer-engine-optimization) that decides whether you're in the answer at all.

Make sure your checkout can accept however agents want to pay as these rails mature, and then spend your real effort on being the product they choose. Whether AI agents and answer engines actually surface and recommend your products is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## ChatGPT sends 92% of standalone AI referral traffic, so is it the only engine that matters?
Source: https://heybuffy.com/blog/chatgpt-ai-referral-traffic-share

ChatGPT drives about **92.4%** of standalone-LLM referral traffic, according to **Previsible's 2026 State of AI Discovery report**, published 6 July 2026, but that figure does not mean it is the only engine worth optimising for. Previsible's own report notes that AI discovery happening inside Google, including [AI Overviews](/glossary/ai-overviews), almost certainly sends more traffic than all standalone LLM platforms combined. So 92% is ChatGPT's share of one large slice, not of all AI discovery.

**What this data is, and isn't.** Previsible analysed **6.77 million** LLM-driven sessions across **166 GA4 properties** in nine industries, from November 2024 to May 2026. It measures referral *clicks* that arrive tagged from a standalone chat product, not citations, not crawler hits, not business spend, and not the huge volume of zero-click AI answers that never send anyone anywhere. It is one analytics dataset, directional and skewed to sites that tag AI referrals well.

## What did Previsible actually measure?

Standalone-LLM referral sessions. Visits where a chat assistant sent a click to a website. Aggregated across GA4:

| Metric (Previsible 2026 State of AI Discovery) | Figure |
|---|---|
| Sessions analysed | 6.77 million |
| GA4 properties / industries | 166 / 9 |
| Date range | Nov 2024 - May 2026 |
| Monthly session growth | ~9.9x, to 644,478 (May 2026 peak) |
| ChatGPT share of standalone-LLM referrals | ~92.4% |
| Claude growth | ~64x, to 8,528/mo; overtook Perplexity Mar 2026 |
| Nov 2025 dip | ChatGPT referrals fell 448,412 → 213,345 in one month |

Source: Previsible 2026 State of AI Discovery report, reported 6 July 2026. One scope caveat worth keeping: analytics tools misattribute a lot of AI referrals as "direct," so even this fast-growing number is an undercount. The mechanics are in [why AI traffic shows up as direct](/blog/why-ai-traffic-shows-up-as-direct).

## Does 92% mean I can ignore other engines?

No, and the same report gives three reasons.

**First, Google is the bigger discovery layer.** Previsible states plainly that AI discovery inside Google's results likely exceeds all standalone LLMs combined. This standalone figure simply doesn't include it, which is why the corpus treats Google's AI surfaces as a first-class target (see [Google AI Mode usage data](/blog/google-ai-mode-usage-data-2026) and [AI Mode vs AI Overviews citations](/blog/ai-mode-vs-ai-overviews-citations)).

**Second, referral share is one metric among several, and each has a different leader.** "Which AI is winning" depends entirely on what you count:

| Metric | What it counts | Source (mid-2026) | Who leads |
|---|---|---|---|
| Standalone-LLM referral traffic | Clicks sent to sites | Previsible, Jul 2026 | ChatGPT ~92.4% |
| AI crawler traffic | Bot requests hitting sites | Cloudflare, mid-2026 | Googlebot ~24.9%, ClaudeBot ~20% |
| Business AI adoption | Paid business spend | Ramp, Apr 2026 | Anthropic 34.4% > OpenAI 32.3% |
| Sources cited per answer | Citation behaviour | Semrush, 2026 | Varies (ChatGPT ~15, Gemini ~3) |

These do not contradict each other. They measure different things. ChatGPT can lead referral clicks while ClaudeBot leads purpose-built crawling (see [AI crawler market share](/blog/ai-crawler-market-share-2026)) and Anthropic leads business spend (see [Anthropic overtakes OpenAI in business adoption](/blog/anthropic-overtakes-openai-business-adoption)). Reading one as "the" AI leaderboard is the misread to avoid.

**Third, referral volume is volatile.** Previsible recorded a roughly 50% single-month drop in November 2025, driven almost entirely by ChatGPT. A number that can halve in a month is a shaky foundation for a single-engine strategy.

> ChatGPT wins the referral click today. But referral clicks, crawler hits, business spend, and citations each crown a different engine, so "optimise for the leader" is a question, not an answer. Measure all four for the engines your buyers use.

## Why is Claude overtaking Perplexity in referrals?

Because its rise in referrals tracks its rise in adoption. Previsible reported Claude grew about **64x** over the period, reaching 8,528 monthly sessions and passing Perplexity in March 2026. Flat through 2025, then accelerating as agentic and enterprise tools landed. That is the same direction as Ramp's spending data without restating it: attention is broadening beyond a single assistant. Claude is still a small referral share, so treat it as a fast-rising signal to *add* to measurement, not a new leader to chase.

## How much AI referral traffic am I probably missing?

More than your dashboard shows. Because assistants often send visits that land as "direct," the true figure is higher than tagged referrals suggest. A form of [dark traffic](/glossary/dark-traffic) and, for pages read-but-not-clicked, the [dark library effect](/glossary/dark-library-effect). The fix is measurement built for it: a referral view that separates AI sources ([GA4 AI-referral dashboard](/blog/ga4-ai-referral-dashboard)) and, more importantly, presence and [citation](/glossary/citation) tracking across every engine, since a [zero-click](/glossary/zero-click-search) answer can build your brand without ever sending a session.

The honest read of Previsible's data is that AI referral traffic is real, growing fast, ChatGPT-led, and only part of the picture. Knowing your share of citations and recommendations across ChatGPT, Google's AI surfaces, Claude, and Perplexity, not just the clicks one of them sends. Is what **Buffy Intel** tracks daily, so you optimise for the whole board rather than one square. Questions: support@flash.tech.

## ChatGPT started linking brands in May 2026: what the branded-link shift means for referral traffic
Source: https://heybuffy.com/blog/chatgpt-branded-links-referral-shift

On 7 May 2026, ChatGPT changed how it points readers to brands: it moved from footnote-style citation chips to **inline, clickable brand links inside the answer**, and it started including a brand URL far more often. The measurable result was immediate. Referral traffic to brand websites, and to homepages in particular, jumped sharply the same day and stayed elevated. As of mid-2026, two independent datasets agree on the shape of the shift.

This piece collects the evidence. Every figure attributed and dated, and explains what the change does and does not mean. It is the data companion to the practical playbook on [optimising your homepage for AI referrals](/blog/optimize-your-homepage-for-ai-referrals).

## What changed on 7 May 2026?

ChatGPT switched from showing sources as footnote-style chips to embedding **inline hyperlinks on brand names and terms** within the answer text, and it began surfacing a clickable brand URL in a far larger share of answers. Practitioners have called it the "branded-link update."

The clearest single measure comes from **Profound** (an AI-visibility analytics vendor), which reported that the share of ChatGPT answers containing a brand URL rose from about **4.5% to roughly 20-24% on 7 May 2026**: about a **5× increase in one day**. The effect was structural, not a blip: the elevated rate held in the weeks after. Because this is one vendor's tracking of the sites it monitors, treat it as directional and dated rather than an audited industry constant.

## How much did referral traffic change?

A lot, and two datasets measured with different methods point the same way. The table below keeps each figure tied to its source.

| Metric | Figure | Source |
|---|---|---|
| Answers containing a brand URL | **~4.5% → ~20-24%** on 7 May (~5×) | Profound (2026) |
| OpenAI referrals to monitored brand sites | **~60-65% lift overnight**, held | Profound (2026) |
| Total ChatGPT referrals, week-on-week | **+157.7%** (30 Apr-6 May vs 7-13 May) | Similarweb desktop panel (2026) |
| Homepage referrals, week-on-week | **+354.7%** (same window) | Similarweb desktop panel (2026) |
| Page views per ChatGPT visit | **3.8 → 4.7** (+24%) | Similarweb desktop panel (2026) |
| Time on site per ChatGPT visit | **3.5 → 3.9 min** (+11%) | Similarweb desktop panel (2026) |

Source: Profound (server-side referral tracking across a basket of monitored brand sites) and Similarweb (desktop clickstream panel, 30 Apr-20 May 2026). Both are single-source datasets with undisclosed or panel-limited samples, so the **direction** (a large, sustained jump in ChatGPT referrals, concentrated on homepages) is firmer than any single percentage. The fact that two independent methodologies agree on that direction is what makes the finding credible.

## Why did homepage traffic surge specifically?

Because the inline link ChatGPT now adds most often is a **brand's homepage**, not a deep product or article page. When an answer names a company and makes that name clickable, the natural target is the brand's root URL.

The homepage share of ChatGPT referrals shifted dramatically:

- **Similarweb:** homepages went from roughly **26-32% to about 60%** of ChatGPT referrals immediately after 7 May.
- **Profound:** on its own site, homepage share of OpenAI referrals moved from about **28% to 62%**; industry-wide across its monitored basket, homepages went from about **4% to 24%** of OpenAI referral traffic.

The two homepage figures from Profound measure different scopes (one site vs a broad basket), which is why they differ. Both show the same direction. The practical read: the **homepage has become the page AI most often sends a clicker to**, so it now carries a discovery job it did not have a year ago.

> The branded-link shift turned ChatGPT into a referral channel that lands on your front door. Your homepage is now the page an AI answer hands a curious buyer.

## Did every industry benefit equally?

No. Profound's breakdown showed the lift concentrated in some sectors and absent in others:

| Sector | Daily OpenAI referral change vs pre-7-May baseline |
|---|---|
| B2B Software / SaaS | **Up more than 200%** |
| Financial Services / Fintech | **~60% lift** |
| E-commerce / Retail | **Essentially flat** |

Source: Profound (2026), single-vendor. The pattern is consistent with how people use ChatGPT differently by category: research- and consideration-heavy sectors (SaaS, fintech) generate answers that name and link a brand, while transactional retail queries more often route through product surfaces and shopping features than through an inline brand link. Do not assume the SaaS-scale lift transfers to a retail catalogue.

## Does more referral traffic mean more recommendations?

No, and conflating the two is the trap. The branded-link change affects **how often a clickable link appears and where it lands**, not whether your brand is the one named as the answer. This is the difference between being [cited versus recommended in AI search](/blog/cited-vs-recommended-in-ai-search): you can pick up more referral clicks while a competitor is still the brand the engine actually recommends.

It also does not mean ChatGPT is the whole picture. Each engine is its own [citation](/glossary/citation) ecosystem. Being linked more by ChatGPT says nothing about Gemini, Claude, or Perplexity, which is [why one brand gets cited and another doesn't](/blog/why-ai-cites-one-brand) varies by engine. And a sizeable share of AI-driven visits still arrive with no referrer, landing in analytics as [Direct](/glossary/dark-traffic), so even this surge is undercounted unless you [unmask AI traffic in GA4](/blog/why-ai-traffic-shows-up-as-direct).

## What should you do about it?

Three durable moves, none of which depend on the exact 7 May numbers holding:

- **Treat your homepage as an AI landing page.** It is now the page ChatGPT most often links, so it must state who you are and what you do in plain, extractable text, and route visitors onward. The step-by-step is in [how to optimise your homepage for AI referrals](/blog/optimize-your-homepage-for-ai-referrals).
- **Measure the channel honestly.** Build an [AI-referral view in GA4](/blog/ga4-ai-referral-dashboard) and track the share that lands on the homepage. Remember the scoreboard has moved [from clicks to citations](/blog/from-clicks-to-citations). Referral clicks are one signal, answer-level presence is the other.
- **Earn the recommendation, not just the link.** Strengthen the [entity signals](/blog/entity-strength-ai) and corroboration that make an engine name you, and follow the playbook on [how to get recommended in ChatGPT](/blog/how-to-get-recommended-in-chatgpt). A link you didn't earn the recommendation behind converts poorly.

The honest caveat: these are mid-2026 figures from two vendors, and AI answer formats change fast. OpenAI could adjust link behaviour again. Anchor on the durable shift (the homepage is now an AI referral destination) and date the volatile specifics.

Knowing whether this change is sending *you* traffic, and whether those answers actually name your brand. Is exactly what **Buffy Intel** tracks: your presence, citations, and AI-referred traffic across every major engine, measured over time rather than spot-checked.

## The ChatGPT citation lag: why content gets crawled for weeks before it gets cited
Source: https://heybuffy.com/blog/chatgpt-citation-lag

You publish a page, AI bots crawl it hard for weeks, and it still doesn't show up in a single answer. That gap is normal. It's the **citation lag**, and understanding it changes how you read your own data.

## What the citation lag is

The citation lag is the **delay between an AI bot crawling your page and the engine actually citing it** in answers. A page moves through three stages. It gets crawled (trained on or fetched), it gets indexed (added to the engine's retrieval layer), and only then does it get cited at answer time. The lag sits between the first stage and the last, and it commonly runs to weeks.

This maps directly to the [AI crawler lifecycle](/blog/ai-crawler-lifecycle): train, index, answer. Crawling is the entry point, not the finish line.

## What practitioners are reporting

Field data shared by the CEO of Promptwatch on LinkedIn in June 2026. Single-vendor, self-reported, so directionally credible rather than definitive. Described the pattern in concrete terms:

- **Crawl precedes citation by weeks.** [GPTBot](/blog/how-to-see-which-ai-bots-crawl-your-site) crawl volume on a page spiked *before* OpenAI's search index picked the page up and citations began.
- **Explainers overtook comparisons.** Broad comparison guides were cited fast but plateaued; focused single-topic explainer pages with deep context broke through later. Reportedly climbing from roughly 250 to about 1,700 daily citations.
- **Google rank didn't predict ChatGPT citation.** A page's position in Google search did not correlate with how often ChatGPT cited it.

Treat the numbers as one practitioner's data, not a law. The shape of the finding. Crawl first, citation later, explainers durable. Lines up with how retrieval systems are known to work.

## Why heavy crawling with zero citations is a good sign

Brands often panic when AI bots hammer a new page that earns no citations. That reaction reads the signal backwards.

> Heavy bot crawling with no citations yet is a leading indicator, not a failure. The crawl spike is what happens *before* the engine starts citing you. Judging a page dead in week two is judging it before the pipeline has run.

The implication for measurement: track **crawl activity and citations as two separate signals on a timeline**, not one. Rising crawl with flat citations early on is the expected mid-pipeline state. Flat crawl *and* flat citations weeks in is the real warning sign, that's a [discoverability](/blog/ai-crawler-lifecycle) or relevance problem, not a patience problem.

## What it means for what you publish

If citation follows crawl by weeks, the strategy writes itself:

- **Publish explainers as the backbone.** Deep, single-topic pages start slower but climb higher and hold. They're built for durable citation, not a quick spike. (This is also why [AI loves a focused, comprehensive page](/blog/why-ai-loves-listicles) over a thin one.)
- **Use comparisons for quick wins.** They get cited fast; just don't expect them to keep climbing.
- **Don't chase Google rank as a proxy.** Ranking #1 in classic search doesn't guarantee the AI citation. They're scored differently.
- **Give pages a quarter before you judge them.** Pair the lag with the [3-month citation cliff](/blog/content-freshness-citation-cliff): you wait weeks to start getting cited, then citations decay after roughly a quarter without a refresh. The window is real but finite.

The practical takeaway: measure the crawl-to-cite pipeline as a timeline, be patient through the lag, and weight your calendar toward explainers. Watching crawl activity turn into citations over the weeks that follow. Across every engine. Is exactly what **Buffy Intel** tracks.

## ChatGPT is starting to search for brands by name: what fan-out patterns reveal
Source: https://heybuffy.com/blog/chatgpt-fanout-searches-for-brands

A 2026 study of ChatGPT 5.5 by Seer Interactive found something worth watching: the model's hidden [fan-out](/glossary/query-fan-out) sub-queries are increasingly **brand-specific**. Instead of only searching generic phrases like "top GEO agencies," ChatGPT 5.5 also issues searches shaped like "*[brand]* GEO research." When a model's own sub-query *is* your brand name, your brand has stopped competing inside a generic list and started being part of the question. This piece lays out the data, attributed and hedged, and explains why it raises the stakes on [entity strength](/blog/entity-strength-ai).

It pairs with the mechanics in [how query fan-out works](/blog/how-query-fan-out-works) and the week-to-week instability documented in [why your AI share-of-voice score swings](/blog/ai-share-of-voice-volatility).

## What did the ChatGPT 5.5 fan-out study find?

Seer Interactive (Wil Reynolds and Nick Haigler, 2026) examined the sub-queries ChatGPT 5.5 generates *before* it composes an answer. The fan-out step where a single prompt is silently expanded into many background searches. The headline finding is a shift in the *shape* of those sub-queries.

| Study detail | As reported |
|---|---|
| Source | Seer Interactive (2026), a digital-marketing agency |
| Prompt set | **617 prompts** typical of growth VPs, CMOs, and marketing directors |
| Repeat test | One prompt asked **30 times** ("As a VP of growth looking to future-proof our search strategy…") |
| Key shift | Fan-out moved from **generic** ("top GEO agencies") to **brand-specific** ("*[brand]* GEO research") sub-queries |
| Brand presence | Specific brand names appeared in **roughly half** of the 30 answers |

Source: Seer Interactive, 2026. This is a **single-vendor, self-reported** analysis of one model, shared as practitioner research, so read the *direction* as the signal and treat the specific proportions as directional, not precise. Seer's own framing is that human-validated work, not scalable content, is what gets a brand "hardwired" into the model.

## Why does a brand-name sub-query matter so much?

Because it changes what game you are playing. In a generic fan-out. The model searches "best CRM for startups". Your brand is one candidate the model has to *discover and select* from a retrieved list. In a brand-specific fan-out. The model searches "*your brand* pricing" or "*your brand* review". The model has **already decided your brand is relevant** and is now gathering detail on it.

> When the AI's own sub-query is your brand name, you are no longer an option inside the answer. You have become part of the question. That only happens when the model has strongly associated your brand with the topic.

This is the difference between being *found* and being *assumed*. A brand-specific fan-out is downstream evidence of a strong entity association. The model reaches for your name unprompted because, across the corpus it learned from, your brand and the topic co-occur again and again. It is the same mechanism behind [why AI keeps citing one brand](/blog/why-ai-cites-one-brand) and [how AI engines choose which brands to name](/blog/how-ai-engines-choose-brands).

## Is this consistent with what other engines do?

Directionally, yes. The trend line across independent work points the same way, even though methods differ. Newer, more capable models tend to fan out into **more, longer-tail, and more specific** sub-queries rather than a single broad search. That aligns with:

- **The reasoning-model pattern** documented elsewhere. A "thinking" model can spawn dozens of sub-queries per prompt, some of which name specific entities, as covered in [how ChatGPT picks the sources it cites](/blog/how-chatgpt-picks-sources).
- **The primacy of brand-level signals**: correlation studies repeatedly rank branded mentions and branded search among the strongest predictors of AI citation, above raw backlinks (see [the three citation levers](/blog/freshness-structure-authority-levers)).

The caution: this is one study of one model version, and model behaviour changes between releases. The *durable* claim. Capable models increasingly resolve topics down to named entities. Is firmer than any single number, and it survives whichever exact fan-out ChatGPT does next quarter.

## What should you actually do about it?

You cannot make a model fan out to your brand directly. There is no setting for it. You earn it indirectly, by building the association the model reads:

- **Publish work worth naming.** Original research, specific data, and genuine thought leadership get discussed and repeated across independent sources. The [corroboration](/glossary/corroboration) that teaches a model to link your brand to the topic. Scalable, me-too content does not.
- **Be a recognised entity, consistently.** Use one consistent brand name, keep your [Organization identity](/blog/make-your-website-agent-readable) clean and machine-legible, and build presence where your buyers and the models both look. Including communities, per [using Reddit for AI-search visibility](/blog/how-to-use-reddit-for-ai-search-visibility).
- **Go deep on a focused topic.** Singular-topic depth builds a stronger association than broad, shallow coverage. The same principle behind [earning a place in AI-cited best-lists](/blog/get-into-ai-cited-best-lists) through earned authority rather than self-promotion.
- **Measure the right thing.** Being *fanned out to* is upstream of being cited, which is upstream of being [recommended](/blog/cited-vs-recommended-in-ai-search). Track [share of voice](/glossary/share-of-voice) as a smoothed trend across many prompts and every engine, not a single reading.

The practical read for 2026: as models get better at resolving a question down to named brands, the payoff shifts from *ranking a page* to *being a known entity*. Entity strength compounds slowly and is hard to fake, which is exactly why it is worth building. Tracking whether the engines have started reaching for your brand by name. Across ChatGPT, Gemini, Claude, and Perplexity, over time. Is exactly what **Buffy Intel** is built to measure.

## How fresh does your page need to be for ChatGPT?
Source: https://heybuffy.com/blog/chatgpt-freshness-windows

ChatGPT now tells its search tool how recent a page must be to count. In its 2026 [pipe-delimited query format](/blog/chatgpt-new-search-query-language), the third field of every background search is a **freshness window in days** — roughly **2 days** for stock prices, **30 days** for commercial products, and **365 to 3,650 days** for evergreen forum content. A page updated outside the window for its query type can still be fetched, but it is not preferred. This is a step-by-step guide to which windows apply and how to keep your pages inside them.

**Last reviewed: 23 August 2026.** The window values below were observed by search consultant **Suganthan Mohanadasan** (suganthan.com) across a small set of questions on a single account in August 2026. Treat the *existence* of a per-query recency field as the durable finding and the *exact day counts* as a directional, single-observer snapshot — attribute "Suganthan, August 2026" and date any figure you reuse. This assumes you already accept that [freshness affects citations](/blog/content-freshness-citation-cliff); the question here is *how recent, for which pages*.

## What is a freshness window in ChatGPT search?

It is the recency ceiling ChatGPT hands to each sub-search. When the model [fans a question out](/blog/how-query-fan-out-works) into many searches, each line carries a number of days in its third field — a [query freshness window](/glossary/query-freshness-window). A window of `30` means "prefer pages touched in the last 30 days for this sub-query." Short windows enforce recency hard; long windows effectively switch the recency filter off. The window is chosen by the *topic*, not by you, which is why the same site can be perfectly fresh for one query and stale for another.

## What freshness windows does ChatGPT use by query type?

They scale with how fast the underlying facts change. The observed values, from most to least time-sensitive:

| Query type | Observed freshness window | What it implies |
|---|---|---|
| Stock prices | ~**2 days** | Only near-live data qualifies |
| Sports results | ~**7 days** | This week's outcomes only |
| Commercial products / pricing | ~**30 days** | Refresh monthly to stay eligible |
| Earnings / financial guidance | ~**90 days** | Quarterly cadence is enough |
| Reddit / evergreen forum content | ~**365–3,650 days** | Recency barely filters; age is fine |

Source: Suganthan, August 2026 (small single-account sample; directional). The pattern is intuitive: the faster a topic's facts move, the tighter the window. The actionable row is **commercial products at ~30 days** — most brand-relevant pages (pricing, plans, comparisons, "best for X") sit in that bucket, which means a page that has not been genuinely updated in a quarter risks falling outside the window exactly where buying decisions happen.

## How often should you refresh each page type?

Map your pages to their window and set the cadence to match — no more, no less:

1. **Pricing, plans, and comparison pages → monthly.** These hit the ~30-day commercial window. A substantive monthly review (verify prices, update the comparison, note what changed) keeps them eligible.
2. **News, launches, and time-sensitive pages → as events happen.** Short windows mean stale is worse than absent; update on the news, not on a calendar.
3. **Financial or quarterly-data pages → quarterly.** The ~90-day earnings window means a quarterly refresh is sufficient; monthly churn adds no benefit.
4. **Evergreen explainers and glossary/definition pages → rarely.** Long windows plus slow real-world change mean these decay slowly. Refresh when the facts actually change, not on a timer — over-churning stable content wastes your budget and can erase accrued authority.

The rule of thumb: **spend your refresh budget where the window is short and the query is commercial.** A page in a 30-day window fighting for a buying query earns far more from a real monthly update than a definition page in a 10-year window ever will.

## Does this contradict the three-month citation cliff?

No — they are two different stages of the same story, and it is worth being precise so the corpus does not appear to disagree with itself. The **freshness window** is a *retrieval filter* applied by one engine (ChatGPT) at the moment it searches, expressed in days per query type. The [three-month citation cliff](/blog/content-freshness-citation-cliff) is an *observed decay pattern* — across engines, a page's citations tend to fade after roughly a quarter without updates.

> The freshness window is the engine's recency rule at search time; the citation cliff is the decay you observe downstream if you never refresh. They are cause and effect, not a contradiction.

Both point to the same discipline: keep competitive, time-sensitive pages genuinely current. The window explains *why* a specific ChatGPT search skips your stale page today; the cliff explains *what* the cumulative neglect costs over a quarter. Neither implies you should churn evergreen [content that decays slowly](/glossary/content-decay).

## How to check your pages against ChatGPT's windows

A quick audit you can do without special tools:

- **Classify each key page by query type.** Is it commercial (30-day), time-sensitive (days), quarterly (90-day), or evergreen (long)? That sets its target cadence.
- **Check the visible "updated" date and the real content behind it.** A date bump with no substantive change does not count; ChatGPT rewards updated *content*, not updated *timestamps*.
- **Prioritise the short-window commercial pages.** These are where falling outside the window costs citations on buying queries — fix these first.
- **Measure citations before and after a refresh.** Because of the known [crawl-to-index-to-cite lag](/blog/chatgpt-citation-lag), watch the trend over several weeks, not overnight.

The honest takeaway: ChatGPT's search tool now encodes recency as a hard, per-topic parameter, so "publish and forget" fails fastest exactly on your commercial pages. Knowing which of your pages sit in short windows — and whether your refreshes actually move citations — is the loop **Buffy Intel** is built to close. Questions: support@flash.tech.

## ChatGPT's new search query language: how web.run works now (2026)
Source: https://heybuffy.com/blog/chatgpt-new-search-query-language

In mid-August 2026, ChatGPT rebuilt how its search tool talks to the web. Between **16 and 20 August 2026**, the model stopped issuing searches as JSON objects and switched to a compact, **pipe-delimited query language** — each background search is now one line: a call type, the query, a freshness window in days, and an optional target domain. This reference lays out the syntax field by field and what each part changes for getting cited.

**Last reviewed: 23 August 2026.** The format below was documented by search consultant **Suganthan Mohanadasan** (suganthan.com), who captured ChatGPT's browser traffic across a small set of questions on a single Plus account between those dates. It is a **single-observer, directional** teardown of a tool OpenAI changes without announcement — the *structure* is directly observed, but the exact values (freshness windows especially) come from a small sample. The direction is corroborated by [Search Engine Land's](https://searchengineland.com/) reporting on `web.run` and by Promptwatch's fan-out tracking. Attribute "Suganthan, August 2026" and date any figure you reuse. For the underlying concept of one prompt becoming many searches, see [how query fan-out works](/blog/how-query-fan-out-works).

## What does ChatGPT's new search syntax look like?

One line per search, fields separated by pipes. The change is easiest to see side by side — the same intent, before and after the switch:

```
Old (JSON, ~16 Aug 2026):
{"system1_search_query":[{"q":"site:intercom.com Fin AI Agent pricing 2026"}]}

New (pipe-delimited, ~20 Aug 2026):
fast|Intercom Fin AI agent pricing 2026 live chat support|30|intercom.com
```

Each line reads as an ordered set of fields, and a search sequence often closes with a separate `length|long` (or `medium`/`short`) directive that sets how much the model wants back:

| Field (position) | What it holds | Example |
|---|---|---|
| 1 — call type | Which search vertical to use | `fast` |
| 2 — query | The rewritten sub-query text | `Intercom Fin AI agent pricing 2026` |
| 3 — freshness window | Recency limit, in days | `30` |
| 4 — domain (optional) | A single domain to target | `intercom.com` |
| closing directive | Desired answer length | `length\|long` |

The takeaway: a fan-out sub-query is no longer just a keyword string. It is a structured retrieval instruction that already encodes *what kind* of search, *how recent*, and *which domain* — before it ever touches the open web. This is a return to form, not a brand-new idea: analysts note ChatGPT used a similar pipe format before GPT-5.3, moved to JSON, and has now moved back to a compact language.

## What are the search verticals (call types)?

Five, each routed to a different index. The first field decides which one, and that decision determines whether a citation is even possible:

| Call type | What it searches | Citation opportunity |
|---|---|---|
| `fast` | General web search | Yes — standard web pages |
| `product` | Catalogue lookups for physical goods | Product cards / merchant offers |
| `business` | Places and local lookups (with location) | Local listings / business data |
| `image` | Image search | Image sources |
| `genui_run` | Generated UI widgets (charts, schedules) | **None** — OpenAI-hosted, no web page cited |

Source: Suganthan, August 2026. The practical read is that different query types are won on different surfaces. A commercial "best X" question flows through `fast` and rewards clean web pages; a "show me trail shoes under $120" flows through `product` and rewards a correct [product feed](/glossary/product-feed) with merchant offers; a "coffee near me" flows through `business` and rewards your places data, not your blog. Knowing which vertical your target queries hit tells you which asset to fix.

## What is the domain slot, and how is it different from site:?

The domain slot is the fourth field, and it is the structured successor to the [`site:` operator](/glossary/site-operator). Earlier in 2026, analysts measured ChatGPT increasingly appending `site:` to its fan-out sub-queries to pin a search to one domain — a behaviour we documented in [what ChatGPT's query fan-out targets](/blog/chatgpt-site-operator-fan-out-data). The new format promotes that targeting from text-inside-the-query to its own dedicated field.

Why it matters: the tool now routinely **pre-selects a domain** before searching, and that domain reflects the competitive set already in the model's memory. If it targets your domain and your page hides the answer behind JavaScript, images, or vague marketing prose, the sub-search returns nothing citable and the model moves on. If it targets a competitor's domain and skips yours, you were never in the consideration set for that query. The domain the model writes is a free read on how it perceives your category.

## What does the freshness field do?

It caps how old a page can be and still be preferred for that search. The third field is a number of days, and the observed values scale with how time-sensitive the topic is — roughly 2 days for stock prices, 30 days for commercial products, up to thousands of days for evergreen forum content. Because the values vary so much by query type, we cover them in their own piece: see [how fresh your page needs to be for ChatGPT](/blog/chatgpt-freshness-windows) and the [query freshness window](/glossary/query-freshness-window) definition. The short version: for commercial and comparison pages, the observed window is about a month, so a pricing page that has not been genuinely updated in a quarter can fall outside it.

## Why do genui_run widget answers matter for citations?

Because they close the citation door entirely. A `genui_run` line returns a rendered interface component — a stock chart, a sports schedule, a weather card — built from OpenAI-hosted data, not assembled from web pages.

> When a query resolves to a `genui_run` widget, there is no web page in the answer and no link to earn — the citation slot you were optimising for does not exist for that question.

For visibility measurement, this is a real trap. If you track a basket of target queries and some of them now return widgets, those slots are unwinnable and will drag your apparent citation rate down for no fixable reason. The fix is to identify the widget-returning queries and stop counting them as citation opportunities — measure the queries where a citation is actually possible.

## What should brands do about the new search language?

Treat each field as a diagnostic, and fix the asset that matches the vertical:

- **Read the domains ChatGPT writes.** Ask your target questions, watch which domain slots the model fills, and confirm they include yours. A wrong or missing domain — common after rebrands, migrations, and country-domain splits — means wasted probes and a fixable visibility gap.
- **Match the asset to the call type.** `fast` rewards clean, server-rendered web pages; `product` rewards a complete product feed; `business` rewards accurate places data. Fix the one your queries actually hit.
- **Respect the freshness field.** Keep commercial and comparison pages genuinely current, because the observed commercial window is about 30 days — see the [freshness-window playbook](/blog/chatgpt-freshness-windows).
- **Discount the widgets.** Flag `genui_run` queries and remove them from your winnable-citation count so your measurement stays honest.
- **Measure the retrieval, not just the answer.** The format proves how much happens before a citation appears; watching only the final links misses where you are being dropped.

The durable point behind the volatile syntax: ChatGPT's search tool is a precise, structured retrieval system, and each field tells you something about how it sees your brand. Reading those signals across hundreds of real questions — which verticals your category triggers, which domains get pre-selected, how fresh your pages need to be — is exactly what **Buffy Intel** is built to measure over time. Questions: support@flash.tech.

## What ChatGPT's query fan-out targets: the site: operator dataset (2026)
Source: https://heybuffy.com/blog/chatgpt-site-operator-fan-out-data

ChatGPT's query fan-out increasingly narrows its background searches to a single named domain using the `site:` operator, and the domains it points at are overwhelmingly first-party. According to a July 2026 analysis by AI-visibility platform Peec AI, the `site:` operator appeared in about **43% of ChatGPT 5.6 (codename Luna) query fan-outs**, up from roughly **0.004% in ChatGPT 5.5**, and **84% of those `site:` domains were branded** — the site of the product or company the question was about. This reference lays out what the fan-out actually targets, with every figure attributed and dated.

**Last reviewed: 24 July 2026.** All figures below are from Peec AI's analysis of ChatGPT 5.6 query fan-outs, published by researcher David Konitzny (22 July 2026), unless noted. It is a **single-vendor, directional** dataset from one analytics vendor's prompt sample, so treat the exact percentages as a snapshot of one model version and cite "Peec AI, July 2026" with the date when you reuse a figure. For the underlying mechanics of the fan-out step itself, see [how query fan-out works](/blog/how-query-fan-out-works).

## How much more does ChatGPT 5.6 use the site: operator?

Dramatically more than the prior version. The [`site:` operator](/glossary/site-operator) restricts a search to one domain, and its use inside ChatGPT's fan-out jumped by orders of magnitude between versions. Peec AI's term-frequency comparison of the sub-queries each model generates:

| Term in fan-out sub-queries | ChatGPT 5.6 (Luna) | ChatGPT 5.5 |
|---|---|---|
| `site:` prefix | **43.2%** | 0.004% |
| Year mention (2025 / 2026) | 26.5% | 6.2% |
| "official" | 21.9% | 1.4% |
| "best" / "top" | 5.4% | 8.5% |
| "pricing" / "cost" | 3.0% | 0.51% |
| "review" | 1.1% | 1.02% |
| "vs" / "versus" | 0.03% | 1.30% |

The pattern: Luna leans heavily on domain-restricted, "official," and recency-dated sub-queries, and away from open "best/top" and "vs" comparisons. The fan-out is behaving less like a broad keyword sweep and more like targeted verification against specific, current, first-party sources.

## Which domains does the site: operator target?

Mostly one domain at a time, and mostly the brand's own. Peec AI reports that in **88.66%** of fan-outs using the operator, only a single `site:` domain appears; two or three domains show up in roughly 9% of cases combined. And the domains split sharply between first-party and secondary sources:

| Domain type | Share of `site:` domains | What it means |
|---|---|---|
| **Branded** (first-party) | **83.63%** | The model targets the product/company's own site |
| **Non-branded** (secondary) | **16.37%** | Community, review, and institutional sources |

That 84%-branded finding is the mechanistic companion to [ChatGPT's shift toward brand-name fan-out sub-queries](/blog/chatgpt-fanout-searches-for-brands): the model has often already decided which brand the question is about and points a `site:` probe straight at that brand's domain. The consequence for AI visibility is direct — if your first-party pages hide their facts behind JavaScript or images, the fan-out narrows to your domain and finds nothing citable.

## What terms appear alongside the site: operator?

Product attributes lead. When Peec AI clustered the terms that appear with a `site:` domain, the most common were product specifications, followed by "official" and reviews:

| Term cluster alongside `site:` | Share of `site:` occurrences |
|---|---|
| Product specs (size, model, colour) | 11.72% |
| Official | 9.29% |
| Reviews | 4.71% |
| Support | 3.17% |
| Pricing | 3.14% |
| Recommendations | 0.88% |

The read: the operator is used to pull *highly specific* facts from a trusted domain — the exact spec, the official detail, the price — not to browse. This is why [structured, extractable product facts](/blog/prioritize-your-structured-data) on your own pages matter so much for the branded majority of these searches.

## Which non-branded domains does the fan-out reach for?

Reddit, by a wide margin. Within the 16% of `site:` domains that are non-branded secondary sources, one platform dominates:

| Non-branded domain | Share of non-branded `site:` targets |
|---|---|
| reddit.com | **71.5%** |
| trustpilot.com | 5.92% |
| linkedin.com | 2.34% |
| g2.com | 2.27% |
| capterra.com | 1.75% |

Reddit alone is about **12.28% of all `site:` operator domains** — roughly one in eight. Grouped by category, the non-branded targets break down as **Social & forums 76.6%**, **Review & comparison 10.9%**, and **Public institutions 4.1%**. Within Social & forums, Reddit is **93.4%** of the category; within Review & comparison, Trustpilot leads at **54.5%** (then G2 20.9%, Capterra 16.1%). Note the important nuance from the [cross-engine citation data](/blog/does-reddit-get-you-cited-by-ai): being the top *retrieval* target is not the same as being cited — ChatGPT rejects the vast majority of Reddit pages it pulls in.

Public institutions are more spread out (bbb.org 34.6%, fda.gov 22.8%, mayoclinic.org 17.7%, pubmed 8.6%), with **arXiv appearing at about 7.1%** of that category — echoing the [silent-source](/glossary/silent-source) pattern where research repositories are retrieved for context without always being cited.

## Does the operator target whole domains or specific pages?

Whole domains, mostly. Peec AI found the `site:` operator points at the **bare root domain in 86.19%** of cases and at a specific path or URL in only **13.81%**. But the intent differs by depth:

| Term cluster | Root-domain `site:` | Domain + path `site:` |
|---|---|---|
| Product / specs | 12.37% | **32.52%** |
| Pricing | 5.41% | 12.31% |
| Official / verification | 10.17% | 8.58% |
| Reviews / ratings | 7.27% | 0.55% |
| Customer service | 4.41% | 0.63% |
| Comparison | 1.84% | 0.05% |

> Root-domain searches are used to identify a trusted source; path-level searches appear when the model already has a precise need, such as a specific product detail or price.

In plain terms: broad informational intents (reviews, official, service, comparison) skew to the whole domain, while product- and price-specific queries reach for a specific page. The fan-out is a structured retrieval strategy — first identify the trusted domain, then narrow to the exact fact.

## How should you use this dataset?

As a directional reference, not a target to game:

- **Cite the source and date.** Attribute figures to "Peec AI, July 2026 (ChatGPT 5.6 analysis)" and hedge them as single-vendor and version-specific — Luna's behaviour can change with the next model release.
- **Serve your first-party facts cleanly.** With 84% of `site:` targets being branded, your own pages must expose specs, pricing, and official details as server-rendered text the model can lift.
- **Know your non-branded destinations.** For your category, the external validation the fan-out reaches for likely lives on Reddit, Trustpilot, G2, or Capterra — but weight that against whether each engine actually *cites* those sources.
- **Measure retrieval and citation separately.** Being targeted by a `site:` probe is upstream of being cited, which is upstream of being recommended.

Tracking what the fan-out points at for *your* buyers' questions — and whether those retrievals turn into citations across ChatGPT, Gemini, Claude, and Google — is exactly what **Buffy Intel** is built to measure, engine by engine, over time.

## ChatGPT vs Google AI search vs Perplexity for product discovery
Source: https://heybuffy.com/blog/chatgpt-vs-google-vs-perplexity-product-discovery

ChatGPT, Google's AI search, and Perplexity all recommend products now, but they **find, cite, and transact differently**, so "optimise for AI shopping" isn't one job. As of mid-2026, ChatGPT is strongest at conversational discovery, Google's AI surfaces at shopping-data depth and checkout breadth, and Perplexity at cited, research-style comparisons. This is a neutral, criteria-based look at how they differ and what that means for a brand.

A note on scope: agentic-commerce features are moving fast and several have changed more than once across 2025-2026. The durable differences are in *how each engine retrieves and cites*; treat the specific shopping features as dated to mid-2026 and verify them against each platform's current announcements.

## How do ChatGPT, Google AI search, and Perplexity differ for product discovery?

At a glance, by criteria rather than by verdict:

| Criterion | ChatGPT | Google AI search (AI Overviews / AI Mode) | Perplexity |
|---|---|---|---|
| Primary strength | Conversational discovery & recommendation | Shopping-data depth, checkout breadth | Cited, research-style comparisons |
| How it finds products | Live web retrieval + model knowledge | Google web index + [Shopping Graph](/glossary/google-ai-mode) | Live web retrieval, source-first |
| Sourcing tendency | Established / authoritative sources | Google ranking signals + product feeds | Forums/community (e.g. Reddit) + cited web |
| Citation style | Selective, fewer links | Inline links + shopping modules | Citation-heavy, sources listed |
| Checkout rails (mid-2026) | Agentic Commerce Protocol (with Stripe) | Universal Commerce Protocol; checkout in AI Mode | In-assistant purchase for subscribers |

The table is a starting map, not a scoreboard. The sections below explain each row and where the figures come from.

## How does each engine find products?

They retrieve from different places:

- **ChatGPT** blends its trained knowledge with live web retrieval, surfacing products conversationally as a shopper narrows intent ("a waterproof jacket for commuting under £150"). It reads the open web rather than a dedicated product feed.
- **Google's AI surfaces** sit on top of Google's web index *and* its **Shopping Graph**: which Google reported holds more than 50 billion product listings, with over two billion refreshed hourly (Google's own figures, attributed to its 2025-2026 announcements). That feed depth is Google's structural advantage for shopping specifically.
- **Perplexity** is retrieval- and source-first: it runs a live search and assembles a cited answer, which makes it well-suited to "compare X vs Y" style product research.

The practical takeaway: a clean, server-rendered [product page](/blog/write-conversational-product-pages) with [structured data](/glossary/structured-data) helps all three, but Google additionally rewards a complete, accurate product feed.

## How does each one source and cite?

Sourcing tendencies differ enough to change who gets named. As of mid-2026, studies reported that ChatGPT skews toward established, encyclopedic and authoritative sources; Perplexity leans heavily on community and forum content (Reddit prominent among them) alongside cited web pages; and Google's AI surfaces reflect Google's own web index and ranking signals plus its product data. Treat the exact percentages floating around as study-dependent and directional. The *direction* (ChatGPT authoritative-leaning, Perplexity community-leaning, Google index-leaning) is the stable, useful signal.

Why it matters: the same product page can be [cited](/glossary/citation) by one engine and missed by another, purely on sourcing policy and crawler access, not on quality. That's the core reason to measure presence per engine rather than assume it transfers. The mechanism is unpacked in [why AI cites one brand and ignores a near-identical competitor](/blog/why-ai-cites-one-brand).

## What are the shopping and checkout features?

This is the fastest-moving layer, so read it as a mid-2026 snapshot:

- **ChatGPT** surfaces products in-conversation and uses the **[Agentic Commerce Protocol](/glossary/agentic-commerce-protocol)** it co-developed with Stripe to handle checkout sessions and payment; the in-chat purchase experience has shifted across 2025-2026, so confirm the current flow.
- **Google** and Shopify back the **Universal Commerce Protocol**, and Google has brought checkout into AI Mode with select merchants, alongside visual and shoppable features. The two protocols are compared in [WebMCP vs UCP](/blog/webmcp-vs-ucp).
- **Perplexity** offers in-assistant purchasing (notably for its subscribers), keeping discovery and buying in one cited flow.

The bigger shift behind all three is [agentic commerce](/glossary/agentic-commerce). Software agents completing the purchase. Getting ready for it is its own checklist: [agentic commerce readiness](/blog/agentic-commerce-readiness) and [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents).

> The engines don't share one mechanism, so they don't share one answer. The same product can win in ChatGPT, lose in Perplexity, and never appear in Google's AI Mode, not because of quality, but because each finds, cites, and transacts differently.

## Which should a brand optimise for?

All three, because shoppers use all three, and presence in one doesn't guarantee the others. The even-handed playbook:

1. **Build the foundation once.** A reachable, parseable, structured product page serves every engine.
2. **Feed Google specifically.** Its shopping advantage runs on complete, accurate product data.
3. **Earn community and authoritative mentions.** That's what Perplexity and ChatGPT respectively lean on.
4. **Measure each engine separately.** Track who cites and recommends you per engine, over time. Don't infer one from another.

There's no single engine to "win"; there's a [share of voice](/glossary/share-of-voice) to hold across all of them. Sampling the same product questions across ChatGPT, Google's AI surfaces, and Perplexity. Repeatedly, and logging exactly who gets recommended where. Is precisely what **Buffy Intel** is built to do.

## How to check whether AI bots are ignoring your robots.txt
Source: https://heybuffy.com/blog/check-if-ai-bots-ignore-your-robots-txt

Network data suggests about **30% of AI-bot scrapes ignore robots.txt**, but that is a web-wide average, not your number. The only way to know whether AI bots respect *your* [robots.txt](/glossary/robots-txt) is to compare their requests against your own disallow rules in your logs. This is the hands-on companion to [how often AI crawlers ignore robots.txt](/blog/how-often-do-ai-crawlers-ignore-robots-txt); read that for the benchmark figures. Below is the method, in five steps.

## Step 1: Write down exactly what your robots.txt disallows

You can't detect a violation without a rule to check against. Open your live `robots.txt` and list, per user-agent, every path you disallow. Robots directives are user-agent-specific, so a path blocked for `*` may be allowed for a named bot (or vice versa), and that distinction decides whether a fetch is a violation.

Pay attention to the AI-relevant agents you actually name, common ones include `GPTBot`, `OAI-SearchBot`, `ChatGPT-User`, `ClaudeBot`, `Claude-SearchBot`, `PerplexityBot`, and `Google-Extended`. If your file only has a global `Disallow`, every one of those bots is measured against the same rule. Keep this list; it is the ruler for Step 3.

## Step 2: Pull AI-bot requests from your logs

Get every AI-crawler request over a fixed window (28 days is a good default) from your server access logs or CDN bot analytics. For each request you need three fields: the **user-agent**, the **path** requested, and the **HTTP status** returned. Group the requests by operator so one bot's behaviour doesn't hide in the total, the same user-agent grouping we detail in [seeing which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site).

Keep the raw paths, not just counts. You need to know *which* URLs each bot hit to compare them against your disallow list, so a summary of "GPTBot: 4,000 hits" isn't enough on its own.

## Step 3: Match each request against your disallow rules

Now cross-reference. For each AI-bot request, ask: was this path disallowed for this user-agent, and did it return content? A non-compliance event is the overlap:

**non-compliant hit = HTTP 200 response to a path your robots.txt disallowed for that bot**

Tally those hits per operator and divide by that operator's total requests to get its non-compliance rate for your site. A bot that fetched only allowed paths complied, however heavily it crawled. A bot that pulled disallowed paths and got a 200 ignored your file. Compare your per-bot rates to the ~30% network aggregate: far lower means your rules are largely respected; near or above it means real leakage worth acting on.

> The signal is narrow and unambiguous: a 200 status on a path you disallowed for that agent. Everything else, heavy crawling of allowed pages, blocked paths that returned 403, is not a violation.

## Step 4: Verify identity before you count it

Don't trust the user-agent string. Because a self-declared name is [trivially spoofed](/glossary/verified-bot) and non-compliant scrapers rotate IPs and fake headers, confirm each "bot" against the operator's published IP ranges with a reverse-DNS check before you attribute a violation to it. Sort the results into two buckets:

- **Verified bot, hit a disallowed path** — genuine non-compliance by a named operator. This is what the network data measures.
- **Unverifiable IP claiming a bot name** — likely impersonation or a scraping vendor wearing a costume, a different threat you handle with edge blocking, not robots.txt tuning.

Separating the two keeps you from blaming an operator for traffic that wasn't theirs, and tells you whether your problem is real bots bending the rules or imposters ignoring them entirely.

## Step 5: Decide, enforce, and re-measure

A non-compliance number is only useful if it drives a decision, path by path. For content you genuinely need closed (proprietary data, paywalled pages), move enforcement to where it works: a CDN or WAF rule keyed to verified identity that returns a 403, since [robots.txt can't enforce anything](/blog/how-often-do-ai-crawlers-ignore-robots-txt) and a bot ignoring it won't stop on request. For everything else, remember that the crawlers reading you are usually the ones that ground and [cite live answers](/blog/from-clicks-to-citations), so an over-eager block quietly costs you citations, and check you aren't already [blocking crawlers by accident](/blog/is-your-cdn-blocking-ai-crawlers).

Then recompute each month against the same window. Non-compliance is a moving target that rose ten-fold across 2025, so a single snapshot is a starting point, not a verdict. Watching who crawls you, whether they respect your rules, and whether that reading turns into citations, across engines and over time, is the ongoing job that **Buffy Intel** is built for. Questions: support@flash.tech.

## Cited isn't recommended: why AI quotes your page but names a competitor
Source: https://heybuffy.com/blog/cited-vs-recommended-in-ai-search

An AI engine can lift a fact straight from your page and, in the same answer, recommend a competitor instead. **Being cited and being recommended are two different outcomes, and in 2026 they are visibly decoupling.** Two practitioner analyses this year put numbers on the gap and, between them, explain why the popular tactic of publishing your own "we're the best" list now tends to backfire.

## What's the difference between cited and recommended?

A [citation](/glossary/citation) is when the engine pulls a passage or fact from your page and attributes it as a source. A *recommendation* is when the engine names your brand as the answer. The first is about being a useful document; the second is about being the trusted choice, and the same answer can do one without the other.

The marketing strategist behind the "GEO is a CMO problem, not an SEO problem" analysis (mid-2026) framed it bluntly: high web rankings and citations do not guarantee the brand gets recommended. In a "best AI SDR agents" query, the brand Coldreach reportedly ranked first and was cited, yet was not the brand the answer recommended. In a "best insider-threat management" query, several brands that had published self-listing roundups were cited but not recommended, while competitors that *hadn't* gamed the format were the ones named. It's one analyst's reading of specific queries. Directional, not a controlled study, but it isolates the gap cleanly.

> An AI answer can quote your page and recommend your competitor in the same breath. Winning the citation is not winning the customer. The recommendation goes to the brand the wider web already trusts.

## How big is the gap, and why does self-promotion widen it?

Large enough to invert the tactic that created it. SEO analyst Lily Ray's mid-2026 analysis tracked **100 B2B "best [category]" queries** between April and June 2026. Her headline finding: when a brand's own self-promoting listicle (one that ranks itself #1) was cited in the AI answer, **the self-promoting brand was left out of the actual recommendation roughly 69% of the time**: often while competitors named lower on its own page got recommended instead.

A few specifics from that analysis, all attributed to Ray and dated mid-2026 (single-author, treat as directional):

- She identified **184 self-promoting listicle pages across 146 brands**, with a sharp spike from 2025 as the "GEO boom" accelerated.
- Examples: **Oasis LMS** was cited extensively for "best LMS" yet excluded from the recommendation, with Kajabi and Thinkific named instead; **Pylon** had two self-promo listicles cited while Zendesk and Freshdesk were recommended.
- A **January 2026 Google update** algorithmically demoted sites leaning heavily on the tactic, with some losses extending domain-wide, not just the listicle pages.
- Google added disclaimers warning users about **"self-proclaimed experts"** for some queries, and Reddit and Forbes increasingly dominate "best" citations. A tilt toward user-generated and editorial sources.

The mechanism is the one we covered in [why AI loves listicles](/blog/why-ai-loves-listicles): engines treat a page that ranks only its own author as promotional and discount the *recommendation* it makes, even while they'll still cite a useful fact from it. So a self-listing page can simultaneously earn a citation and hand the recommendation to the rivals it lists.

## What actually earns the recommendation?

Corroboration. What others say about you, not self-assertion. The recommendation tracks the brand the wider web already agrees on, which is why both analyses point to the same levers:

1. **Be consistent across your own surfaces.** Homepage, product pages, and docs should state the same positioning and the same specifics, so an engine builds one coherent picture of you.
2. **Earn third-party coverage.** Reviews, independent roundups, and editorial mentions are the [corroboration](/glossary/corroboration) engines weigh above your own claims. Pursue *earned* placement in lists, per [getting into the best-of lists AI cites](/blog/get-into-ai-cited-best-lists).
3. **Build entity strength.** The durable signal is how well-established you are as an [entity](/glossary/entity-authority) across the web. The slow lever in [entity strength](/blog/entity-strength-ai), and the one that lets bigger brands still get recommended where smaller ones can't.
4. **Don't neglect the web ranking.** The CMO-problem piece cites research by Kevin Indig finding that web search position has the biggest single impact on LLM citation rate. Classic SEO still feeds the system, even as it stops being the whole story.

This is the same conclusion the corpus keeps reaching from different angles, that you can't fake your way past [corroboration](/blog/can-ai-search-be-manipulated), and that the content and platform signals behind a pick are separable from the ones behind a citation, which is the heart of [why AI cites one brand](/blog/why-ai-cites-one-brand) over a near-identical competitor. For the broader inputs an engine balances, see [how AI engines decide which brands to recommend](/blog/how-ai-engines-choose-brands).

## What should a brand do differently?

Stop optimising for the citation and start measuring the recommendation. Practically:

- **Audit bottom-funnel prompts.** For your real "best [category]" and "alternatives to [competitor]" questions, check whether you're *recommended*, not just whether you're linked somewhere in the sources.
- **Retire the self-listing play.** If you publish a "best tools" page with yourself at #1, recognise it may be voting for the competitors you list; redirect that effort to [earned placement](/blog/get-into-ai-cited-best-lists) and genuine [educational content](/blog/how-to-get-cited-by-ai).
- **Own your narrative where you legitimately win.** Brand- and feature-specific questions ("how does X work," "X pricing") are where your own pages should be the recommendation, because the engine wants the canonical first-party source.
- **Track the gap over time.** Citation without recommendation is a measurable, fixable state, but only if you watch both, across every engine.

The uncomfortable takeaway: you can do everything that earns a citation and still not be the brand AI names. Measuring whether you're recommended, not merely cited. Across engines and over time is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## How to compete for AI visibility in a concentrated category
Source: https://heybuffy.com/blog/compete-in-concentrated-ai-categories

**To compete for AI visibility in a concentrated category, measure how crowded the head really is, then invest where the dominant brands are weak: long-tail sub-topics, specific comparisons, and earned placement in the sources AI cites for your vertical.** Competing head-on for the most-asked prompts against entrenched entities is the slow, expensive path; calibrating your strategy to your category's measured concentration is the efficient one.

This is the action companion to the data piece on [whether AI visibility is winner-take-all](/blog/is-ai-visibility-winner-take-all), which shows that the top three brands hold ~82.9% of News & Media visibility but ~41.4% of Finance (Semrush, 2026 AI Visibility Index). The steps below assume you have read your own category's number, or are about to measure it in step 1.

## Step 1: Measure your category's concentration

Before any content decision, quantify how crowded the head is. A vertical average from a published index is a starting point, not your answer.

- Assemble **20–40 real buyer prompts** spanning your category's intent branches (definitions, comparisons, buying decisions, troubleshooting), the same input a [citation-fingerprint audit](/blog/match-your-industry-citation-fingerprint) uses.
- Put each through the engines your buyers actually use and record which brands each answer **mentions** and **cites**.
- Calculate the **share held by the top three brands.** Above roughly two-thirds signals a concentrated head; under about half signals an open field. This is the same discipline as [measuring AI visibility](/blog/how-to-measure-ai-visibility) generally, focused on category structure rather than your own rank.

## Step 2: Separate the crowded head from the open tail

Concentration lives at the head of the category, not evenly across it. Split your prompt set into two buckets:

| Bucket | Example | Typical concentration |
|---|---|---|
| **Head prompts** | "best CRM", "best marathon shoes" | High — dominated by a few entities |
| **Tail prompts** | "CRM for solo real-estate agents", "marathon shoes for flat feet and overpronation" | Low — contestable |

The tail is where new brands realistically break in, because the dominant names answer specific sub-questions thinly or not at all. Map which of your prompts sit in each bucket; that map, not a generic checklist, decides where to spend.

## Step 3: In a concentrated category, go around the head

If your top-3 share is high, competing for the main prompts directly is the least efficient move you can make. Redirect that effort:

- **Own the long tail.** Publish deep, specific pages for the sub-topics and buyer segments the incumbents treat as an afterthought. Focused single-topic depth is what breaks the citation ceiling, not another broad overview of the head term.
- **Publish genuinely neutral comparisons.** Criteria-based, multi-option comparisons earn trust and are the commercial layer AI leans on; they let you appear in "which is best for X" answers without out-ranking a giant on the bare category term. Never a self-serving "and we're #1" list.
- **Answer the branches the leaders skip.** One category answer is assembled from many sub-queries, so covering a neglected branch can win you a citation inside an answer the head brands also appear in.

## Step 4: Earn placement where owned pages can't win

In a crowded head, your own domain often cannot be the cited source, so the citation has to come from somewhere the engine already trusts. That means [earned media](/glossary/earned-media): independent listicles, reviews, expert roundups, and the community and reference sites AI cites for your vertical.

- Identify which third-party domains the engines cite for your category (from your step-1 capture) and pursue honest presence there, as in [how to get into AI-cited best-of lists](/blog/get-into-ai-cited-best-lists).
- Where community sources dominate your vertical, take [Reddit and forum visibility](/blog/reddit-aeo-for-startups) seriously, without astroturfing, which backfires.
- Treat earned placement as the primary lever in concentrated categories and owned content as the support, the reverse of the open-category order.

> In a winner-take-all head, the fastest route in is not to out-shout the incumbents on the main question. It is to own the questions they answer badly and to be present in the third-party sources the engine already cites.

## Step 5: In an open category, climb the main prompts directly

Where the top three hold under half, the core prompts are contestable and worth attacking directly. Here owned content leads:

- Build [entity strength](/blog/entity-strength-ai): consistent, corroborated presence across the web so engines associate your brand with the category's head terms.
- Publish the clean, citable, server-rendered pages that win the main question outright, and pair them with the same neutral comparisons and long-tail depth, now as expansion rather than the only way in.
- Move faster, because an open field can concentrate over time; early entity-building compounds.

## Step 6: Re-measure and rebalance on a cadence

Concentration is not fixed. Categories tighten as leaders entrench and loosen as engines diversify their sources, so a strategy set once goes stale.

- Repeat your step-1 measurement **quarterly** and after any major engine change, re-using the same prompt set so you are comparing like with like.
- Watch whether your top-3 share is rising or falling, and shift budget between owned and earned accordingly, the same [freshness discipline](/blog/content-freshness-citation-cliff) any competitive program needs.
- Judge progress by whether *your* brand's mentions and citations are climbing in the buckets you chose, not by a single snapshot.

Competing in a concentrated category is less about out-spending the leaders than about spending where they are weak, calibrated to a number you can actually measure. Tracking that category structure, and whether your own visibility is climbing within it, across every engine over time, is exactly what **Buffy Intel** is built to provide. Questions: support@flash.tech.

## Conductor's 2026 AEO/GEO benchmarks: a fully-sourced reference
Source: https://heybuffy.com/blog/conductor-aeo-geo-benchmarks-2026

This is a fully-sourced reference to **Conductor's 2026 AEO/GEO Benchmarks Report**, described as the first large-scale industry analysis of how AI-powered discovery reshapes brand visibility. The headline figures: AI referral traffic is about **1.08%** of all website traffic, **ChatGPT drives ~87.4%** of that referred traffic, and Google **AI Overviews appear in ~25%** of searches. This page collects the report's numbers, each tied to its source.

**Last reviewed: 27 June 2026.** All figures below are from Conductor's 2026 AEO/GEO Benchmarks Report, first published **13 November 2025** and last updated by Conductor in **April 2026**. The figures were verified against Conductor's own report page and corroborated across independent coverage (Business Wire, The AI Journal, and multiple secondary analyses). It is a single-vendor dataset, so treat the **direction** as firmer than any single number, and attribute anything you quote to "Conductor, 2026."

## What did Conductor analyse?

The report's scale is what makes it useful as a benchmark. Conductor's stated methodology:

| Metric | Figure | Source |
|---|---|---|
| Total sessions analysed | **3.3 billion** | Conductor, 2026 |
| AI-traffic sessions specifically | **35.7 million** | Conductor, 2026 |
| Domains studied | **13,770** | Conductor, 2026 |
| Industries / sub-industries | **10 / 22** (mapped to GICS) | Conductor, 2026 |
| AI-generated responses examined | **17 million** | Conductor, 2026 |
| Citations tracked | **over 100 million** | Conductor, 2026 |
| Google searches analysed for AI Overviews | **21.9 million** | Conductor, 2026 |

The takeaway: this is one of the largest public datasets on AI visibility to date, which is what makes its benchmarks worth referencing, while remembering they reflect Conductor's enterprise-domain sample, not the whole web.

## How much traffic does AI actually refer?

Conductor's most-cited finding is that AI referral traffic is still a small slice of the whole, but growing and very uneven by sector:

| Metric | Figure | Source |
|---|---|---|
| AI referral traffic (all industries) | **1.08% of total** | Conductor, 2026 |
| Month-over-month growth | **~1%** | Conductor, 2026 |
| ChatGPT's share of AI referral traffic | **87.4%** | Conductor, 2026 |
| Highest sector. IT | **2.80%** | Conductor, 2026 |
| Second. Consumer Staples | **1.91%** | Conductor, 2026 |
| Lowest. Communication Services | **0.25%** | Conductor, 2026 |
| Lowest. Utilities | **0.35%** | Conductor, 2026 |

The 1.08% figure is easy to dismiss as trivial, but two things make it matter: it is compounding monthly, and, because AI answers are often [zero-click](/glossary/zero-click-search). Referred visits undercount AI's real influence on a buying decision. Much of AI's impact shows up as brand awareness and shortlisting that never registers as a click, which is why Conductor's own advice is to measure citations and mentions, not just referrals. We make the same case in [from clicks to citations](/blog/from-clicks-to-citations).

## How prevalent are Google AI Overviews?

Across the 21.9 million Google searches Conductor analysed, about one in four returned an AI Overview:

| Sector | AI Overview prevalence | Source |
|---|---|---|
| All searches (average) | **25.11%** | Conductor, 2026 |
| Healthcare (highest) | **48.75%** | Conductor, 2026 |
| Financials | **25.8%** | Conductor, 2026 |
| Consumer Staples | **6.82%** | Conductor, 2026 |
| Real Estate (lowest) | **4.48%** | Conductor, 2026 |

The ~25% average sits in the same range as other mid-2026 estimates (Google's own and third-party trackers have put [AI Overview](/glossary/ai-overviews) prevalence between roughly 16% and 25%, depending on query mix and date). The sector spread is the more actionable point: in Healthcare nearly half of searches surface an AI summary, so the [AI Overview optimisation](/blog/ai-overviews-complete-guide) stakes are far higher there than in Real Estate.

## Who wins the citations?

Conductor reports that within several industries, **third-party publishers and marketplaces, not the brands themselves. Capture the largest citation shares**:

| Domain | Citation share | Industry | Source |
|---|---|---|---|
| Amazon | **17.99%** | Consumer Staples | Conductor, 2026 |
| Zillow | **7.36%** | Real Estate | Conductor, 2026 |
| NerdWallet | **6.73%** | Financials | Conductor, 2026 |
| Google | **5.34%** | IT | Conductor, 2026 |

In Financials, in other words, a publisher like NerdWallet is winning more AI [citations](/glossary/citation) than many traditional banks. This is the same dynamic behind [why AI loves listicles](/blog/why-ai-loves-listicles): for category questions, engines lean on neutral-looking marketplaces and review publishers over brand-owned pages. The strategic implication is earned placement in those sources, not just optimising your own site.

> "AI isn't just adding another search surface. It's deciding which brands the world sees first.". Conductor, 2026 AEO/GEO Benchmarks Report

## How should you use these benchmarks?

Treat this as a dated benchmark, not a target. Every number here is **Conductor's own**, drawn from an enterprise-domain sample over a defined window, so cite Conductor and the date when you reuse one, and hedge as "as of the 2026 report." Because live retrieval favours recently-updated pages, we keep references like this on a refresh cadence and update figures substantively as new editions land. Conductor's report is also published in per-industry cuts, so the sector benchmark that matters most is the one for *your* industry, not the cross-industry average.

The one figure that ultimately matters is your own: whether the engines surface, cite, and recommend *your* brand for the questions your customers ask. Measured over time, across engines, against your category benchmark. That is precisely what **Buffy Intel** is built to measure, turning industry benchmarks like Conductor's into a read on your actual [share of voice](/glossary/share-of-voice).

## Content freshness and the 3-month citation cliff
Source: https://heybuffy.com/blog/content-freshness-citation-cliff

In live AI search, age is a ranking signal. Engines that retrieve and cite pages at answer time lean toward content that's **recently updated**: and the corollary is harsher than most teams expect: citations **decay** as content goes stale.

## The citation cliff

Analyses of AI [citations](/glossary/citation) keep surfacing the same pattern: a meaningful share of citations come from pages updated within roughly the **last three months**, and eligibility drops off after that. A page that earned citations on publish, then sat untouched, quietly loses them to fresher competitors covering the same ground.

The "publish a great post and move on" model. Fine for some evergreen SEO. Leaks citations in AI search.

> The "publish a great post and move on" model. Fine for some evergreen SEO. Leaks citations in AI search.

## Why engines favour fresh content

Live retrieval exists precisely to get *current* answers beyond a model's training cutoff. So when an engine assembles an answer, recency is a proxy for accuracy: a page updated last month is more likely to reflect today's reality than one from two years ago. For anything that changes. Prices, product lineups, "best X for Y," comparisons. Fresh wins.

## How to refresh deliberately

Freshness isn't about churning everything constantly. It's about a cadence on the pages that matter:

- **Identify your high-value, competitive pages**: the ones tied to buyer queries, and put them on a refresh schedule.
- **Make updates substantive.** Correct facts, add new data or examples, revise stale claims. A bumped date with no real change is hollow (and engines increasingly look at actual content change, not just a timestamp).
- **Signal the update** with an honest "last updated" date and genuinely revised content.
- **Leave stable content alone.** Definitional and reference pages (a [glossary term](/glossary/generative-engine-optimization), say) don't need the same cadence. Don't spend refresh budget where recency barely helps.

## Measure the decay

Because the cliff is gradual and invisible, you only catch it by watching citations over time. A page slipping out of answers months after publishing is the signal to refresh, and watching whether the refresh wins the citations back is how you know it worked. That ongoing read across engines is part of what [measuring AI visibility](/blog/how-to-measure-ai-visibility) (and **Buffy Intel**) is for.

## Crawled but not indexed: why Google's indexing bar is now your AI-visibility bar
Source: https://heybuffy.com/blog/crawled-not-indexed-ai-visibility

A page stuck in Google's **"Crawled – currently not indexed"** status cannot appear in AI Overviews or AI Mode either. Google's AI surfaces draw only from its Search index, and its own documentation says a page must be indexed to be shown there. So a page Google reads and declines to index is invisible to Google's AI answers, not just its blue links. This piece explains what Google said is behind the status, why the usual cause is "commodity content," and what it means for [AI visibility](/blog/why-youre-invisible-in-ai-search).

It pairs with a companion how-to, [how to diagnose and fix pages Google crawls but won't index](/blog/fix-crawled-not-indexed), and it extends the argument in [is GEO just SEO?](/blog/is-geo-just-seo): the indexing quality bar and the AI-citation bar are converging into one bar.

> A page Google won't index can't be an AI Overviews source. The quality threshold for the classic index and the quality threshold for an AI citation are turning into the same threshold.

## What does "Crawled – currently not indexed" mean?

It means Googlebot fetched (downloaded) your page but chose not to add it to the Search index. The page was reachable and crawlable; Google simply decided not to keep it. This is different from **"Discovered – currently not indexed,"** where Google is aware of the URL but has not crawled it yet.

| Status | What Google has done | Typical cause |
|---|---|---|
| **Discovered – currently not indexed** | Knows the URL exists; has not crawled it | Crawl-budget or scheduling; Google hasn't fetched it yet |
| **Crawled – currently not indexed** | Fetched the page; declined to index it | A technical issue hiding content, or a quality judgment that the page isn't useful enough |

Both appear in the Search Console page-indexing report under Indexing → Pages. Some pages *should* sit in the crawled-not-indexed bucket: non-canonical duplicates, pagination, feed URLs, and parameter variants are normal there and need no fixing. The concern is when pages you want indexed are stuck.

## Why does an unindexed page also vanish from AI Overviews?

Because Google's AI surfaces are built on the same index. Google's Search Central documentation states that "to be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet." Being crawled is not enough; the page has to clear indexing.

That single requirement turns a classic SEO status into an AI-visibility problem. If your content sits in crawled-not-indexed, it is not a candidate for [AI Overviews](/glossary/ai-overviews) or [Google AI Mode](/glossary/google-ai-mode) at all, no matter how well it would answer the query. The index is the gate, and the gate is upstream of every Google AI answer. This is why [optimising for AI Overviews](/blog/how-to-optimize-for-ai-overviews) has to start with confirming the page is actually indexed.

## What did Google say is behind it?

At an April 2026 Google Search Central event in Toronto, a Google presenter discussed why Google crawls a page and then declines to index it, as reported afterwards by SEO analyst Marie Haynes. (The event organisers asked attendees not to attribute quotes to specific Googlers but permitted sharing what was said, so the quotes below are relayed second-hand and should be read as directional paraphrase.) The presenter framed crawling as downloading a page, then: "If we think it's useful we might put it in a database," meaning the index.

Two causes were described:

| Cause | What it looks like | How common |
|---|---|---|
| **Technical issue** | Google fetches the page but sees little content. Example reported: a `robots.txt` rule like `Disallow: /*?*`, meant to block tracking parameters, also blocked the parameterised CSS and JavaScript the theme relied on, so crawlers saw only a heading and boilerplate | Rarer; worth ruling out first |
| **Quality** | Google looked at the page and, per the paraphrase, "found it not to be good," often because many pages already cover the same topic and yours adds nothing more useful | The common case |

The presenter said Google now wants to index content that offers two things: **first-hand personal experience**, and **knowledge no one else has**. The reasoning given was that generative AI has lowered the threshold for producing content, so when anyone can generate a page on any topic, the bar for what earns a place in the index rises. One relayed line went further, describing an experiment "with seeing which one produces happier users," implying Google sometimes indexes a page temporarily to test user response. Treat that as one analyst's account of a single event, not official policy; the durable takeaway is the direction, corroborated by trade coverage in mid-2026: generic, easily-replaceable content is increasingly left uncrawled-into-index.

## Isn't heavy crawling a good sign for AI visibility?

Sometimes, but do not confuse two different signals. Being crawled repeatedly by AI training and retrieval bots such as GPTBot or ClaudeBot, with no citations yet, is usually normal lag, not failure. Crawl volume tends to spike weeks before an engine's index picks a page up, as covered in [the crawl-to-cite lag](/blog/chatgpt-citation-lag) and the [dark library effect](/glossary/dark-library-effect). You should not panic-edit a page just because bots read it and citations haven't started.

Google's "Crawled – currently not indexed" is a different animal. It is not an AI crawler building a corpus; it is Googlebot's index-quality gate returning a verdict of "not this one." Two distinctions keep this straight:

- **Different crawler, different decision.** GPTBot reading your page says nothing about Google's index status, and vice versa. They are separate systems.
- **Lag resolves itself; a gate does not.** Crawl-to-cite lag ends when the engine indexes you. A crawled-not-indexed verdict is a standing exclusion from Google's AI surfaces until you change what caused it.

So the response differs: ride out crawl-to-cite lag; act on a crawled-not-indexed verdict.

## What does this mean for GEO?

It collapses two to-do lists into one. The signals that get a page indexed by Google are increasingly the signals that get it cited by any AI engine: it must be [reachable and parseable](/blog/is-your-cdn-blocking-ai-crawlers), and it must clear a rising quality bar built on first-hand experience and unique knowledge rather than restated common knowledge. That is the same standard behind [entity strength](/blog/entity-strength-ai) and [earning AI citations](/blog/how-to-get-cited-by-ai).

The practical move is to treat your crawled-not-indexed report as an AI-visibility report. Pages sitting there are pages your Google AI answers can never use, and they are a strong hint at what other engines will skip too. The companion piece, [how to diagnose and fix pages Google crawls but won't index](/blog/fix-crawled-not-indexed), walks the checks step by step.

Watching whether your pages are indexed, reachable, and actually cited across ChatGPT, Gemini, Claude, Perplexity, and Google's AI surfaces, over time, is exactly what **Buffy Intel** is built to measure.

## How to tell if an AI-visibility drop is you or the model
Source: https://heybuffy.com/blog/diagnose-ai-visibility-drops

When ChatGPT names or cites your brand less, the instinct is to start editing pages. Before you do, find out whether the cause is on your side at all. Mid-2026 research by [Peec AI](/blog/why-ai-visibility-changes-without-you) documented AI engines silently changing how they expand a prompt into sub-queries and which sources they prefer, which means a drop can happen with no change to your content. This is a five-step diagnostic to tell a real, your-side regression from a model shift you should simply ride out.

It is the practical companion to [why your AI visibility changes even when your content hasn't](/blog/why-ai-visibility-changes-without-you). That piece is the evidence; this is the procedure.

> A drop that hits your whole category is the model changing its mind. A drop that hits only you is a problem on your side. Diagnose which before you touch a single page.

## Step 1: Establish a baseline before you diagnose

You cannot diagnose a drop you can't measure. AI answers are probabilistic and shift between observations, so a single reading tells you nothing. Before anything else, make sure you have a baseline built from **many prompts, sampled repeatedly, across every engine**, read as a trend line rather than one number.

If you do not already have this, you cannot yet tell a drop from ordinary [answer volatility](/glossary/answer-volatility). Start sampling now and treat the first sustained pattern, not the first dip, as your signal. Everything below assumes you are reading a trend, not a snapshot.

## Step 2: Split the drop into three signals

"Visibility went down" is too coarse to act on. Separate it into three measurable signals, because each points at a different cause:

| Signal | What it measures | A drop here suggests |
|---|---|---|
| **Mentions** | How often your brand is named in the answer text | A naming/entity problem, or a [ghost citation](/glossary/ghost-citation) pattern (cited but not named) |
| **Retrieved sources** | How often your domain is pulled in during retrieval, including [silent](/glossary/silent-source), uncited uses | A retrieval/reachability problem, or the engine reordering which domains it trusts |
| **Fan-out terms** | The sub-queries the prompt actually triggers | The model changed how it decomposes the question |

Watching all three at once is the whole point: a mention drop with steady retrievals is a very different problem from retrievals falling off a cliff. A single citation-rate figure blurs them together.

## Step 3: Check breadth. Did it hit only you, or everyone?

This is the fastest way to assign blame. Compare your movement against your competitors and the broader category over the same window.

- **Category-wide shift** (rivals and comparable sites moved too): almost certainly the **model**. When an engine changes its [query fan-out](/glossary/query-fan-out) or source preferences, it reorders the whole field, not just you. Peec AI's Reddit and arXiv examples moved entire source categories at once.
- **You-specific shift** (the category held steady, you fell): look for a **your-side cause**. Something changed what the engine can fetch, parse, or trust about your pages specifically.

Without a competitive baseline you will misread a category-wide model change as a personal failure, and burn a sprint fixing pages that were never the problem.

## Step 4: Line the drop up against model releases

Timing is evidence. Note when the drop began and check it against known model updates. ChatGPT 5.6 (the Sol/Terra/Luna tier family) shipped on 9 July 2026, and Peec AI reports its Luna tier fans out very differently from 5.5, leaning heavily on the `site:` operator, the word "official", and year modifiers, with more multi-step retrieval.

If your drop clusters around a release date and coincides with a category-wide move, you have your answer: the retrieval behaviour changed, not your content. If the timing is unrelated and the drop is yours alone, keep looking on your side.

## Step 5: Decide. Fix a regression, or ride out a shift

Now act on the diagnosis, not the panic.

**If it is a your-side regression**, work the reachability-to-quotability chain in order:

1. **Reachability:** confirm AI crawlers still get a 200, not a block. A CDN or robots change is the most common silent killer. See [how to see which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site).
2. **Render:** confirm your facts are in server-rendered HTML, not injected by JavaScript a crawler skips.
3. **Structure:** confirm exact facts (specs, pricing, attributes) are in clean lists and tables a precise, targeted search can match, not buried in prose. This is where [structured data](/glossary/structured-data) earns its keep.
4. **Freshness:** confirm the page isn't stale past the [citation cliff](/blog/content-freshness-citation-cliff); refresh with substantive updates, not a bumped date.
5. **Entity:** confirm your naming and [entity strength](/blog/entity-strength-ai) are intact and corroborated across the web.

**If it is a model shift**, do not thrash. You cannot control an engine's fan-out or source weighting. Ride it out, keep sampling, and lean into the durable levers above, which pay off across whichever retrieval behaviour ships next. As Luna's precision turn shows, exact structured facts and reachable first-party pages are the safe bet regardless of the update.

The discipline in one line: measure a trend, split it into mentions, retrievals, and fan-outs, check whether the whole category moved, and only spend effort where the cause is actually yours. Doing that continuously across ChatGPT, Gemini, Claude, and Perplexity, so you can tell a model shift from your own regression, is exactly what **Buffy Intel** is built to do.

## Discover in AI, buy on your site: what OpenAI scaling back Instant Checkout means
Source: https://heybuffy.com/blog/discover-in-ai-buy-on-your-site

OpenAI is pulling native **Instant Checkout** out of ChatGPT and moving it to its **Apps** platform, after only a few dozen merchants went live on the feature it launched in September 2025. The durable lesson for brands is not that AI shopping failed. It is that **product discovery inside AI keeps growing while the checkout rail consolidates**. The practical response: optimise to be *discovered and recommended* inside AI answers, and *convert* that intent on your own site. This is part 13 of the agentic-commerce series.

## What actually changed with ChatGPT's Instant Checkout?

OpenAI launched Instant Checkout. A native, in-chat purchase flow built on the [Agentic Commerce Protocol](/blog/agentic-commerce-protocol-acp). In **September 2025**. By **early 2026** it had reversed course. The Information reported the scale-back in March 2026, and CNBC reported on **24 March 2026** that OpenAI was revamping the ChatGPT shopping experience after struggling with the offering.

An OpenAI spokesperson framed the shift plainly, per Search Engine Land and Modern Retail:

- **"Instant Checkout is moving to Apps, where purchases can happen more seamlessly."**
- In practice, checkout moves from a single native in-chat flow to **individual retailer apps**: names like Instacart, Target, Expedia, and Booking.com, that plug into ChatGPT.

So the change is architectural, not a retreat from commerce: OpenAI is stepping back from *being the checkout* and toward *routing to where checkout already works*. Discovery and recommendation inside ChatGPT continue; the native payment surface is what consolidated.

## Why did in-chat checkout stall?

Two reasons, both company-reported and best read as directional early-to-mid-2026 figures.

| Signal | What was reported | Source |
|---|---|---|
| Merchant adoption | ~30 Shopify merchants live by Feb 2026 (Rye counted ~12) | Forrester (Emily Pfeiffer); Rye |
| Conversion | In-chat checkout converted ~3× worse than click-through to walmart.com | Walmart |
| New-customer rate | ChatGPT drove ~2× the new-customer rate Walmart sees from search | Walmart |

The pattern reconciles cleanly: **AI drove valuable demand, but the native in-chat checkout under-converted it.** Shopify president Harley Finkelstein, speaking at an investor conference, located the bottleneck on the AI-firm side rather than with merchants. The plumbing to complete a purchase in-chat, not merchant willingness. Attribute the specifics to those sources and hedge accordingly; the robust finding is the *shape* of the problem, not the exact multiples.

> The demand AI created was real; the in-chat checkout that was supposed to capture it was not ready. Discovery outran conversion, so the smart move is to win the discovery and take the conversion home.

## Does this mean AI shopping is fading?

No, and conflating the two surfaces is the mistake to avoid. As covered in [what agentic commerce is](/blog/what-is-agentic-commerce), there are two separate things happening: **discovery** (an AI engine surfacing and recommending your product) and **checkout** (the payment rail that completes the sale). Only the second one stalled.

- **Discovery is still growing.** Buyers increasingly start product research inside ChatGPT, Gemini, and Perplexity. That is exactly why [where ChatGPT product recommendations come from](/blog/where-chatgpt-product-recommendations-come-from) is a strategic question.
- **Checkout is consolidating** toward big integrated retailers' apps and first-party sites, where conversion is higher and the experience is controlled.

This is consistent with the rest of the series: a [shopper agent](/blog/shopper-agents-and-product-visibility) is a channel, not a visibility lever, and payment rails are [settlement, not selection](/blog/agentic-commerce-payment-rails). Whether an engine recommends you is decided upstream of any checkout button.

## What does "discover in AI, buy on your site" mean for brands?

It means splitting your effort to match where each stage actually happens:

1. **Win discovery inside AI.** Be the product an engine surfaces and recommends. That depends on [the factors AI uses to recommend products](/blog/factors-ai-recommends-products). Accurate, complete catalog data, [structured data](/glossary/structured-data), [entity strength](/blog/entity-strength-ai), and third-party corroboration, not on any checkout integration.
2. **Prepare your catalog for agents.** Machine-readable product data ([prepare your catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents)) keeps you eligible as engines route more buyers to more surfaces.
3. **Convert on ground you control.** Send that AI-created intent to your own site or first-party app, where conversion is stronger and you own the relationship. Don't stake your revenue on any single engine's native checkout being ready.
4. **Stay rail-agnostic.** Support the emerging [agentic checkout standards](/blog/agentic-commerce-readiness) as they mature, but treat them as distribution plumbing, not the thing that decides whether you are recommended.

The through-line: [answer-engine optimisation](/glossary/answer-engine-optimization) determines whether you are discovered; your own storefront determines whether you convert. OpenAI's pullback just made the division of labour explicit.

Discovery inside AI is now a measurable surface of its own. One that keeps growing even as the checkout layer reshuffles. Tracking whether AI engines actually surface and recommend your products, across ChatGPT, Gemini, Claude, and Perplexity, sampled over time, is exactly what **Buffy Intel** does.

## Do AI assistants render your JavaScript? What a 12-engine test found
Source: https://heybuffy.com/blog/do-ai-assistants-render-javascript

A June-2026 test by Search Engine World fed 12 AI assistants a page whose real answer was hidden behind JavaScript, and **every major Western assistant read only the raw HTML and missed it.** ChatGPT, Claude, Gemini, Perplexity, and Meta AI all reported the decoy value sitting in the unrendered markup. The practical takeaway is old advice with fresh proof: if a fact matters for [getting cited by AI](/blog/how-to-get-cited-by-ai), put it in the HTML the server sends, not in script the browser has to run.

This is part of the [crawlers and technical](/blog/should-you-let-ai-crawlers-index-your-site) series. It assumes you already know that an AI engine has to *reach* a page before it can cite it; here the question is narrower. Once it fetches the page, does it actually execute your JavaScript?

## What did the JavaScript-rendering test actually do?

It used a decoy. The researchers built one page with a fake "internal reference number" written directly into the raw HTML, then used an external script to fetch the *real* number from a second endpoint and swap it in. The genuine value existed only after the code ran. Each of 12 assistants got a unique secret URL and one instruction: summarise the page and report the internal reference number. Server logs recorded three things. The page fetch, the script request, and any follow-up call for the real value, and a unique "canary" string proved a genuine fetch versus a hallucination.

That design separates three behaviours cleanly: did the assistant fetch the HTML, did it download the script, and did it execute the script. Reporting the decoy means it read raw HTML only; reporting the real number means it rendered.

## Which assistants rendered JavaScript and which didn't?

A sharp geographic split emerged. The major US assistants returned the raw-HTML decoy; the Chinese systems tested and France's Mistral returned the JavaScript-injected real value.

| Assistant | Rendered JavaScript? | Value reported |
|---|---|---|
| ChatGPT | No | Decoy (raw HTML) |
| Claude | No | Decoy (raw HTML) |
| Gemini | No | Decoy (raw HTML) |
| Perplexity | No | Decoy (raw HTML) |
| Meta AI | No | Decoy (raw HTML) |
| Microsoft Copilot | Downloaded script, didn't execute | Decoy (raw HTML) |
| Grok (xAI) | Executed, ignored the result | Decoy (raw HTML) |
| DeepSeek, ERNIE, Qwen, Kimi, Mistral | Yes | Real (JS-injected) |

Two details are worth holding onto. **Copilot** uniquely fetched the script (through Diffbot) but never parsed it, so the rendered value never reached the answer. **Grok** executed the code yet still reported the decoy. Its pipeline and its answer disagreed. All figures here are attributed to Search Engine World's June-2026 test; it is a single experiment with one page design, so read it as directional, not a benchmark, and expect behaviour to change as assistants add rendering.

## Why does client-side rendering hide content from AI?

Because fetching a page and rendering a page are different jobs, and the second is expensive. Executing JavaScript at scale means running a full browser engine for every URL. Far more compute than reading the HTML a server returns. So most retrieval pipelines do the cheap thing: fetch the HTML, parse the text, move on. Anything your page assembles *after* that. Content loaded by a framework, injected by a tag manager, or fetched from an API on the client. Simply isn't in the text they parsed.

> For ChatGPT, Gemini, Claude, Perplexity, and Copilot, content injected by JavaScript effectively does not exist. If the fact isn't in the HTML the server sends, assume the engine never read it.

This is the same root cause behind the warning against building [a separate, JavaScript-driven "AI version" of your site](/blog/separate-ai-version-of-your-website): if the real content only exists after rendering, the engine sees a shell. It's also why [accessibility scores predict AI-parseability](/blog/accessibility-and-ai-parseability). A screen reader and a retrieval bot both want the meaning to be in the markup, not painted on by script.

## How do I make sure AI can read my key content?

Get the facts into the server-rendered HTML, then verify it. Concretely:

- **Server-side render (SSR) or statically generate** the pages you want cited, so the core content is in the initial HTML response.
- **Put citable facts in the markup**: prices, specs, definitions, product attributes, and key claims belong in real text and [structured data](/glossary/structured-data), not in a client-side fetch.
- **Reserve JavaScript for enhancement**: interactivity, personalisation, lazy-loaded media, not for delivering the answer itself.
- **Check what a non-rendering reader sees.** Disable JavaScript in your browser, or view the raw response (`curl` the URL, or "View Source" rather than the inspector), and confirm your headline facts are present.
- **Don't trust the assistant's self-report.** In the test, one assistant claimed it "couldn't access" a page that the server logs showed it had fetched successfully. Behaviour is what logs show, not what the chatbot says. The same logic behind reading [which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site) from your own server data.

Reachability isn't only about whether the bot is [blocked at your CDN](/blog/is-your-cdn-blocking-ai-crawlers) or [allowed in your robots file](/blog/should-you-let-ai-crawlers-index-your-site). It's also about whether the content survives the trip from fetch to parse. A page can be fully crawlable and still hand the engine an empty shell. Confirming that your most-citable facts are in the raw HTML, across the engines that decide [which brand gets cited](/blog/why-ai-cites-one-brand), is exactly the kind of check **Buffy Intel** is built to keep watch on. Questions: support@flash.tech.

## Do AI assistants respect robots.txt? A 12-engine test
Source: https://heybuffy.com/blog/do-ai-assistants-respect-robots-txt

When a user pastes a URL into a chatbot, does the assistant check your robots.txt before fetching it? A June-2026 test by Search Engine World put 12 assistants to the test, and **only three. ChatGPT, Claude, and Perplexity. Honoured a robots.txt block; the other nine fetched the page anyway.** The lesson for site owners is blunt: robots.txt is a request that compliant bots choose to honour, not a wall, so it shapes who *politely* stays out, not who *can*.

This is part of the [crawlers and technical](/blog/should-you-let-ai-crawlers-index-your-site) series, and a companion to the test on whether [AI assistants render your JavaScript](/blog/do-ai-assistants-render-javascript). Here the question is compliance: does the assistant respect the file that's supposed to govern access?

## What did the robots.txt test measure?

On-demand fetches, verified by logs. For each assistant the researchers built two isolated test URLs. One allowed, one disallowed in [robots.txt](/glossary/robots-txt). Each carrying a unique "canary" reference string. They pasted the blocked URL into each assistant's chat and asked it to read the page, then checked their own **server logs** (not the chatbot's self-report) to see whether the fetch happened and whether the page returned its secret string. Every page that was fetched returned its exact canary, which proves a genuine retrieval rather than a hallucinated answer.

One scope note to read the result honestly: this tests **user-initiated fetches**: a person explicitly asking the assistant to open a specific URL. That's the `ChatGPT-User` / `Claude-User` category of activity, which several vendors classify as a user action rather than autonomous crawling, and the [Robots Exclusion Protocol](/glossary/robots-txt) is genuinely ambiguous about whether it should apply. The test doesn't settle that debate; it shows what the assistants *do*.

## Which assistants respected robots.txt, and which ignored it?

Only a quarter complied. The three that did also declared honest, identifiable user-agents; the nine that didn't used a range of disguises.

| Behaviour | Assistants | User-agent |
|---|---|---|
| **Respected the block** | ChatGPT, Claude, Perplexity | Honest, declared (`ChatGPT-User`, `Claude-User`, `Perplexity-User`) |
| **Ignored the block** | Gemini, Meta AI, Microsoft Copilot, Grok, DeepSeek, Qwen, ERNIE, Kimi | Disguised or undeclared |

Among the nine non-compliant systems, the disguises escalated: Gemini fetched as a generic `Google` client, Meta AI used undeclared crawler variants, Copilot outsourced the fetch to Diffbot, and several (DeepSeek, Qwen, Kimi) presented faked browser identities. Including "proxy swarms" across multiple countries with impossible user-agent strings like `Windows NT 11.0`. All findings are attributed to Search Engine World's June-2026 test; it is a single experiment focused on user-initiated fetches, so treat the specific pass/fail list as a point-in-time snapshot that will shift as vendors change behaviour.

## Why doesn't robots.txt reliably stop AI fetchers?

Because it was never an enforcement mechanism. The Robots Exclusion Protocol is a published *request*: a well-behaved [AI crawler](/glossary/ai-crawler) reads your robots.txt and voluntarily stays out of disallowed paths. Nothing in the protocol forces compliance. A fetcher that decides to ignore it, or that classifies a user-pasted URL as a user action outside the protocol's scope. Simply requests the page, and your server returns it.

> robots.txt tells polite bots where not to go. It does nothing to a bot that doesn't ask politely. If a page must stay private, enforce that at the server, not in a text file the fetcher is free to ignore.

That reframes two common mistakes. First, using robots.txt as a *security* control: it is the wrong tool, because the bots you most want to keep out are the least likely to honour it. Second, assuming a `Disallow` line guarantees you won't appear in an answer. It doesn't, if the assistant fetches anyway. To genuinely block traffic you need a CDN or WAF rule that returns a 403 by user-agent, IP, or behaviour. The same layer that, configured wrong, ends up [blocking AI crawlers by accident](/blog/is-your-cdn-blocking-ai-crawlers).

## What should I actually do about it?

Decide your stance deliberately, then enforce it where enforcement lives, and verify with logs:

- **If you want AI visibility (most brands): allow them.** Don't rely on robots.txt to block, and don't block by accident. Confirm the major user-agents in the [AI crawler user-agent directory](/blog/ai-crawler-user-agent-directory) aren't disallowed. The cost of being unreadable is being uncited.
- **If you must protect content: enforce at the CDN/WAF.** A robots.txt `Disallow` is a courtesy, not a lock. Put paywalled or proprietary content behind real access control and return a 403 to fetchers you've decided to exclude.
- **Identify traffic by behaviour, not just the declared name.** Because non-compliant fetchers disguise their user-agent, read your raw server logs to see [which AI bots actually crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site). Disguised fetches hide behind ordinary browser strings and won't show up in a name-only filter.
- **Don't trust the chatbot's word.** Compliance is what your logs show, not what the assistant claims when asked.

robots.txt remains worth getting right. It's how you signal intent to the bots that honour it, and how you avoid the far more common own-goal of blocking the crawlers that would have cited you. But treat it as a signal, not a guarantee. Knowing which engines reach your pages, under which user-agents, and whether that turns into citations is exactly what **Buffy Intel** keeps watch on. Questions: support@flash.tech.

## Do AI crawlers follow JavaScript links? A 41-day, 27-bot experiment
Source: https://heybuffy.com/blog/do-ai-crawlers-follow-javascript-links

**AI crawlers do not follow links that only exist after JavaScript executes.** In a mid-2026 field experiment, SEO engineer Vinicius Stanula split a roughly 1,000-page site so half its navigation links sat in the raw HTML and half were injected by JavaScript, then logged what 27 bots did over 41 days. Only Google's two crawlers followed the JavaScript links. Every AI crawler tested. GPTBot, ClaudeBot, PerplexityBot, and the rest. Reached zero pages that were reachable only through a script-generated link. The practical lesson is blunt: a link a bot can't see in the HTML source is, for that bot, a link that doesn't exist.

This is part of the [crawlers and technical](/blog/should-you-let-ai-crawlers-index-your-site) series and the field-data companion to our piece on whether [AI assistants render your JavaScript](/blog/do-ai-assistants-render-javascript). That piece asked whether an engine *reads* script-injected content; this one asks something upstream. Whether a crawler can even *discover* a page when the only route to it is built by JavaScript.

## What did the JavaScript-link experiment actually test?

It isolated link discovery from everything else. Stanula took a site with 21 top-level categories and about 1,000 pages beneath them, then split the categories in two: 11 kept normal HTML links in the page source, and 10 had their links injected by JavaScript so they were invisible in the raw markup. Same design, same content, same templates. Each subcategory inherited its parent's condition. The only variable was whether the path to a page existed before or after scripts executed.

The experiment lasted 41 days: 28 days with the split live, then 13 more after every link was converted back to plain HTML, to watch recovery. Edge middleware logged **30,180 bot requests** across **27 distinct crawlers** that reached the surface pages. Because the surface (linked-from-homepage) pages were reachable by everyone, the test cleanly measured one thing: which bots could get *past* a JavaScript link to the pages behind it.

## Which crawlers followed the JavaScript links?

Almost none. Of the 27 bots that reached the site, only **Googlebot and GoogleOther**: 2 of 27. Followed the JavaScript-injected links to the pages behind them. Every other crawler, including all the AI crawlers, found nothing there.

| Crawler | Followed JavaScript links? | Pages found behind JS |
|---|---|---|
| Googlebot / GoogleOther | Yes | Followed (with depth loss, below) |
| GPTBot (OpenAI) | No | Zero |
| ClaudeBot (Anthropic) | No | Zero |
| PerplexityBot | No | Zero |
| Bingbot (Microsoft) | No | Zero |
| Meta, Amazonbot, DuckDuckBot, Yandex, others | No | Zero |

GPTBot was an especially clear case: it made **3,809 requests** to the site and crawled **zero** pages that lived behind a JavaScript link. All figures are attributed to Stanula's experiment; it is a single test on one site, so read the specific counts as directional, not a benchmark.

## Even Google lost pages as the links went deeper

Google could follow the JavaScript links, but coverage decayed sharply with depth. On the HTML side of the site, Google crawled **100% of pages at every level. All 759 of them.** On the JavaScript side, it reached **67%** of pages one level down, **56%** two levels down, and **42%** at the deepest level.

Speed and coverage turned out to be different problems. Google found its first JavaScript page in about **7.5 hours**, close to the **6.1 hours** it took on the HTML side, so the JavaScript links weren't slow to process, they were incompletely followed. Fast discovery of *some* pages masked the fact that many never got crawled at all. For engines that don't execute scripts, there is no partial credit: the coverage is simply zero.

> A link a crawler can't see in the HTML source is a link that doesn't exist. For 26 of the 27 bots in this experiment. Every AI crawler among them. A JavaScript-injected link led nowhere.

## What happened when the links were switched back to HTML?

Recovery was fast for the crawlers that had been shut out. In the 13 days after every link was converted to plain HTML, **GPTBot picked up 250 new pages**: the first 250 within 48 hours, and **Bingbot found 89**. Google, the one crawler that could already render the pages, added **zero**: it had nothing new to discover.

That asymmetry is the whole story in miniature. The AI crawlers had been blind to those pages the entire time, not slow. The moment a plain-HTML path appeared, they rushed in. The pages hadn't changed; only their discoverability had.

## Does this hold up beyond one experiment?

The pattern is well corroborated, even if one field test isn't proof on its own. Independent analyses through mid-2026 reach the same conclusion: AI crawlers fetch raw HTML and do not execute JavaScript. One analysis of more than 500 million GPTBot fetches reported no evidence of script execution. GPTBot downloads JavaScript files a fraction of the time but doesn't execute them (figures reported by Lantern, mid-2026, single-vendor and directional). Our own coverage of a [12-engine rendering test](/blog/do-ai-assistants-render-javascript) found the major Western assistants read only the raw HTML. The consistent exception is Google, whose crawlers share the rendering infrastructure behind Googlebot, which is exactly what this experiment shows.

The takeaway is durable even as individual numbers move:

- **Put real links in server-rendered HTML.** Navigation, pagination, related-content, and "load more" links should be standard `<a href>` anchors present before any script executes.
- **Give every important page a plain-HTML path** from a page that is itself crawlable. Don't strand pages behind client-side routing.
- **Verify from the source, not the inspector.** View Source or `curl` the page; if a link only appears after the browser executes code, the AI crawlers won't see it.
- **Don't confuse rank with reach.** A site can [rank well on Google](/blog/is-geo-just-seo), which renders, while remaining invisible to the AI crawlers that [decide which brand gets cited](/blog/why-ai-cites-one-brand).

Reachability isn't only about whether a bot is [blocked at your CDN](/blog/is-your-cdn-blocking-ai-crawlers) or [allowed in your robots file](/blog/should-you-let-ai-crawlers-index-your-site). It's about whether your links survive the trip from fetch to parse. Confirming that every citable page has a plain-HTML path the [AI crawlers](/glossary/ai-crawler) can actually follow is exactly the kind of check **Buffy Intel** keeps watch on. Questions: support@flash.tech.

## Do AI engines filter out spam and misinformation like Google does?
Source: https://heybuffy.com/blog/do-ai-engines-filter-out-spam

**No — AI answer engines do not filter spam and misinformation the way Google Search does, and the gap matters more than it sounds.** Google spent two decades building adversarial anti-spam systems; AI engines mostly [retrieve](/glossary/retrieval-augmented-generation) candidate passages and synthesise them, leaning on corroboration rather than a mature per-claim truthfulness filter. Worse, the web they pull from is tilting: a peer-reviewed 2026 study found **60% of reputable sites block at least one AI crawler, versus just 9.1% of misinformation sites** — so the trustworthy web is opting out of the corpus while the untrustworthy web stays open.

**Last reviewed: 19 August 2026.** The robots.txt figures below come from "Is Misinformation More Open? A Study of robots.txt Gatekeeping on the Web," presented at the ACM Web Conference 2026 by researchers at Saarland University. It is one peer-reviewed study of one signal (declared crawler access), so read it as strong directional evidence of a *trend*, not a precise measure of what any given engine actually retrieves.

## Do AI engines have spam detection like Google's?

Not at the same maturity. The two systems do fundamentally different jobs. Google's ranking stack is the product of roughly twenty years of adversarial pressure — an arms race against link farms, doorway pages, cloaking and scaled content abuse — with named [spam policies](/blog/google-spam-policy-ai-answers) and both automated and manual enforcement demoting pages that try to game it.

An AI answer engine works differently. It gathers candidate passages relevant to a query, then a language model synthesises them into an answer. The quality controls it applies are real but shallower than Google's: it weights **corroboration** (do multiple credible sources agree?), **source authority**, and **freshness** when selecting chunks. What it largely does *not* do is adjudicate whether an individual claim is true. As the framing of a 2026 analysis of AI's "spam blind spot" put it, a model tends to average whatever specific, repeated, independent-looking text it finds, without an independent test of truthfulness.

That is not the same as saying engines are defenceless — they discount lone, uncorroborated assertions, and the safeguards are improving month to month. But the practical difference is large:

| | Google Search (mature) | AI answer engines (emerging) |
|---|---|---|
| Core job | Rank and demote pages | Retrieve passages and synthesise |
| Primary spam defence | Named spam policies + automated and manual demotion, hardened over ~20 years | Corroboration, authority and freshness weighting at selection time |
| Per-claim truth check | Indirect, but heavily engineered | Minimal — relies on agreement across sources |
| Easiest thing to exploit | Links, thin pages (well-defended now) | Low-consensus topics with no corroborating source |

Source: characterisation of publicly documented Google spam policy and of how retrieval-augmented answer engines work, as of mid-2026. The direction is the durable point: **engines lean on agreement, not verification.**

## What did the robots.txt gatekeeping study find?

That the crawlable web is quietly sorting itself the wrong way for answer quality. The Saarland University study compared how reputable news sites and known misinformation sites declare AI-crawler access in their robots.txt files. The asymmetry is stark and it is widening.

| Metric | Reputable sites | Misinformation sites |
|---|---|---|
| Block at least one AI crawler | **60.0%** | **9.1%** |
| Distinct AI agents referenced (avg) | **15.5** | **0.77** |
| Sites disallowing GPTBot | Over 50% | — |
| Do not disallow any AI agent | — | Over 80% |
| Trend, Sep 2023 → May 2025 | Block rate rose **23% → 60%** | Roughly flat |

Source: "Is Misinformation More Open?", Saarland University, ACM Web Conference 2026. The one-line read: **the sites most worth citing are the ones most likely to be closed to the crawler, and the sites least worth citing are almost all open.** The study measures declared access, not what each engine ultimately ingests — but robots.txt is the front door, and the front door is being shut selectively.

## Why does the trustworthy web opting out matter for AI answers?

Because a synthesised answer can only be built from what the engine can reach. If high-quality publishers increasingly block AI crawlers — for their own reasons, usually protecting content value and lost referral traffic, the [license-litigate-or-block decision](/blog/license-litigate-or-block-ai-crawlers) many news organisations are now making — while low-quality sites stay wide open, the retrievable corpus skews toward the open, lower-quality end. The engine is not *choosing* bad sources; the good ones are removing themselves from the choice set.

This is not a reason to panic, and it is emphatically **not** advice to block your own crawlers — for a brand doing GEO, our whole [should-you-let-AI-crawlers-in](/blog/should-you-let-ai-crawlers-index-your-site) and [CDN-blocking](/blog/is-your-cdn-blocking-ai-crawlers) guidance points the other way. There is no contradiction: the news publishers in the study are protecting paid journalism from uncompensated ingestion, a different calculus from a brand that *wants* to be found and recommended. In fact the corpus tilt sharpens the opportunity — if much of the quality web is leaving the retrievable set, then well-structured, corroborated, openly-crawlable content stands out more, not less.

> The trustworthy web is locking its front door and the untrustworthy web is propping it open — so being a reachable, corroborated, high-quality source is a bigger advantage now than when the whole web was open.

## Does the spam-detection gap mean you can seed your way to visibility?

Only fragilely, and at real risk. Because engines lean on corroboration rather than verification, a confident claim *can* fill a vacuum where no other source has answered — which is exactly what the ["can AI search be manipulated" tests](/blog/can-ai-search-be-manipulated) showed: seeded rankings got repeated in low-consensus spaces and refused where real coverage existed. Some 2026 experiments go further, reporting that a small cluster of self-promotional pages could dominate the answers for an *unknown* brand (one widely-cited test seeded roughly three dozen pages across a handful of domains and saw them cited in a large majority of answers). Treat those figures as single-source and directional.

The catch is that this is a bet with a short shelf life and a growing downside:

1. **It only works in a vacuum.** The moment a topic has genuine coverage, corroboration overwrites the lone seeded claim — the same mechanism that protects you from bad actors works against you as a manipulator.
2. **It is now named spam.** Google's spam policy explicitly covers [attempting to manipulate its AI answers](/blog/google-spam-policy-ai-answers), so the tactic carries the same enforcement risk as any other manipulation, with cleanup costs later.
3. **It doesn't scale to established brands** (next section). The whole point of GEO is durable visibility, and seeded content is the opposite of durable.

The honest version of this — earning visibility without crossing into spam — is a solved problem: see [how to grow AI visibility without violating spam policies](/blog/grow-ai-visibility-without-spam). Everything that works there survives the engines getting smarter; seeding does not.

## What is the real risk for an established brand?

Two things, and neither is "seed more." First, an asymmetry: once you are an established entity, you largely *cannot* move your own answer by publishing on your own site. Reported 2026 comparisons of established brands found the large majority of their new AI mentions traced to **third-party content — reviews, comparisons, community discussion — not the brand's own promotional pages** (single-source figures, directional). That is the same lesson as the [brand-mention gap vs source gap audit](/blog/brand-mention-gap-vs-source-gap): your answer is built mostly from what *others* say about you.

Second, and more serious: the same corroboration-not-verification gap that a marketer might exploit is a gap an *adversary* can exploit against you. If false or manipulated content about your brand gets seeded into sources an engine retrieves — a form of [answer poisoning](/glossary/answer-poisoning) — the model can repeat it, and a denial on your own FAQ page may not be enough to correct it, because your single page is outweighed by the corroborating (false) chorus. That is why the defence is structural, not a one-page fix. We cover it step by step in [how to protect your brand from AI answer poisoning](/blog/protect-your-brand-from-ai-answer-poisoning).

## What should a brand actually do about the spam-detection gap?

Play the durable side of the gap, on both offence and defence. The moves are the same whether you are trying to be found or trying not to be misrepresented:

1. **Stay reachable and well-structured.** Keep AI crawlers allowed, your key pages server-rendered and in the [sitemap](/glossary/robots-txt), and your facts in clean, extractable chunks. The corpus is tilting toward openness-at-the-bottom; be the quality source that is still open.
2. **Build corroboration, not claims.** Earn consistent, independent third-party mentions that agree on who you are and what you do. Corroboration is the one signal manipulation can't fake and the one thing that both wins citations and immunises you against a false narrative — the [durable entity lever](/blog/most-cited-domains-ai-overviews).
3. **Be specific and dated.** Named, numeric, dated facts are both more citable and harder to overwrite with vague counter-claims.
4. **Monitor across engines.** You cannot defend an answer you never see. Track how you are described and cited across engines over time, so a seeded falsehood or a slipping citation surfaces while it is still fixable.

The takeaway is not that AI search is broken — it is that it currently trusts agreement more than it verifies truth, and the web it reads is tilting toward the open and the untrustworthy. Both facts reward exactly one strategy: be the reachable, specific, corroborated source that the smarter engines of next year will still want to cite.

---

Buffy Intel tracks how AI engines describe and cite your brand across ChatGPT, Gemini, Claude, Perplexity and Google's AI answers — so you can see a seeded falsehood, a corroboration gap, or a slipping citation while there is still time to act. To watch your AI answers the way you'd watch your search rankings, [start with Buffy Intel](https://heybuffy.com) or reach us at support@flash.tech.

## Do AI engines know where you are? How location shapes AI answers
Source: https://heybuffy.com/blog/do-ai-engines-know-where-you-are

Ask ChatGPT or Google's AI for the "best fertility clinic" without naming a city, and you'll often get an answer tailored to *your* city anyway. The engine inferred where you are and quietly localized the recommendation. The way Google Search has always done. But *how* it knows, *how precisely*, and *which engines do it* are widely misunderstood. Getting this right is the foundation of local AI visibility.

The short version: **most AI engines localize, but only through their web-search layer, only coarsely (your city/region from your IP), and not in the model itself.**

## How can an AI "know" my location at all?

Every AI engine has two layers, and only one of them can know where you are:

- **The trained model.** Frozen at a [knowledge cutoff](/glossary/knowledge-cutoff), a [large language model](/glossary/large-language-model) has no awareness of the person asking. No location, full stop. With web search off, the answer is location-blind.
- **The live search layer.** When the engine runs a web search to ground its answer, it behaves like a search engine, and *this* is where your location enters. It reads your approximate location (usually from your IP) and rewrites your question: "best clinic near me" becomes "best clinic in [your city]" before it searches.

So the right question isn't "does the AI know my city?" It's **"does this engine run a location-aware web search, and does that change the answer?"** That reframing is the whole game.

> Location enters through the search layer, never the model. Which means local AI visibility is won exactly where local search is won. In the listings, reviews, and citations an engine retrieves.

## Which engines localize, and how much?

All of the consumer engines localize coarsely through search; the APIs do not unless you tell them to. As of mid-2026:

| Engine | Localizes implicitly? | How |
|---|---|---|
| Google [AI Overviews](/glossary/ai-overviews) / [AI Mode](/glossary/google-ai-mode) | Yes | Inherits Google Search's location signals |
| ChatGPT (search mode) | Yes | IP → coarse city/region; rewrites "near me" into your city |
| Perplexity | Yes | IP-based by default, even logged-out |
| Gemini | Yes / partial | Google account + IP; saved Home/Work & device location with permission |
| Claude (web search) | Yes, coarse | IP city/region; opt-out available; no GPS collected |
| Any of the above via **API** | No, unless passed | OpenAI & Perplexity accept an approximate `user_location`; none by default |

Two caveats worth stating plainly. **AI Mode is a separate ranking system from Google's local 3-pack**: one 2026 study found 28.5% of businesses in the local pack were absent from AI Mode for the same query, so winning the map pack does not guarantee inclusion in the AI answer. And these figures come from studies run in the US, UK, Canada, and Australia; **localization behavior in other markets, including India, is unverified and should be tested directly** rather than assumed.

## Why is it only "coarse"?

Because the default signal is your **IP address**, which resolves to a city or region, not a precise spot. Engines round further, and IP geolocation is imperfect (testers have been placed in a city 45 minutes from where they actually were). Precise, GPS-level location is opt-in, not default: ChatGPT added an explicit precise-location toggle in March 2026, and Anthropic states Claude collects no precise or GPS location at all. Signed-in and paid accounts tend to produce sharper local answers than logged-out sessions, because the account adds context beyond the raw IP, but the baseline everywhere is coarse.

## Does this happen if I never mention a city?

Yes, that's the key point for benchmarking. **Implicit** localization (the engine infers your city from IP and localizes silently) is different from **explicit** localization (you type "in City X"). They don't always return the same answer, and the implicit path is the one most real users trigger without realizing it.

This is also why testing local AI visibility by hand is unreliable: you can't easily fake a *city-level* IP inside a consumer app, engines round your location, and the same prompt in the same place can return [different answers](/glossary/citation) run to run because these systems are non-deterministic. The dependable approach is to benchmark **both**: explicit-city prompts across a matrix of cities, sampled repeatedly, and, where possible, use the APIs' location parameter to set the city deterministically. (That methodology gets its own part in this series.)

## What this means for your brand

If location lives in the retrieval layer, then local AI visibility is won in the **local content ecosystem** an engine retrieves from, not by "training the model." Studies of local AI answers find the majority of citations go to third-party directories and review sites, with the rest to the businesses themselves. So the levers are familiar: a complete, consistent presence across local listings and review platforms, [structured data](/glossary/structured-data) that states who and where you are, and earned placement in the "best [X] in [city]" lists engines lean on. For regulated, high-trust categories like healthcare, the bar on credibility and [corroboration](/glossary/corroboration) is higher still.

The takeaway: AI is not inventing a new local game. It's reading the existing one through a new surface. The brands that show up are the ones whose local footprint is clear, consistent, and trusted enough for an engine to repeat. Measuring that footprint city by city, across every engine, is exactly what **Buffy Intel** is built to do.

## Do Google AI Mode ads get you cited? What a 50,032-keyword study found
Source: https://heybuffy.com/blog/do-ai-mode-ads-get-you-cited

**No. Buying a Google AI Mode text ad does not make a site more likely to be cited in the answer.** A study of **50,032 commercial keywords** by the SEO platform SE Ranking (US AI Mode, data collected 30 June 2026, reported mid-July 2026) found that for the keywords a brand advertised on, its domain appeared among the cited sources only about **11.5% of the time**, and the exact advertised URL just **1.95%** of the time. After controlling for domain strength, backlinks, referring domains, and organic standing, advertisers were cited **no more often than comparable non-advertisers**. The ad slot and the citation are decided by different systems.

This is a single-vendor study reflecting one snapshot in time, so we read the figures as directional, not precise. But the direction matters for anyone budgeting for AI visibility: paid placement in [Google AI Mode](/glossary/google-ai-mode) and being cited as a source are separate outcomes, and spending on one does not move the other.

## What did the SE Ranking study measure?

SE Ranking analysed **50,032 commercial keywords across 20 niches** (about 2,500 per niche), looking at US AI Mode results captured on 30 June 2026. The keywords were selected to surface text ads rather than product carousels, so the ad-frequency figures describe high-intent commercial searches specifically, not all queries. Here are the load-bearing numbers:

| Finding | Figure | Notes |
|---|---|---|
| Commercial queries returning a text ad | 29.45% (14,733 of 50,032) | ~1 in 3 commercial keywords sampled |
| Ad placements with two competing ads side by side | 71.1% | Advertisers rarely appear alone |
| Advertiser **domain** cited among the answer's sources | 11.53% | For keywords they advertised on |
| Advertiser's **exact URL** cited | 1.95% | The advertised page itself |
| Advertiser ranking organically for the same keyword (domain) | 15.35% | ~85% had no organic presence for it |
| Advertiser's exact URL ranking organically | 2.32% | — |
| Ad presence by cost: under \$2 / \$2–\$10 / over \$10 | 24.33% / 32.45% / 53.56% | Ad frequency rises with CPC |

All figures are SE Ranking's, from a single mid-2026 US snapshot; treat them as directional.

The headline: in **about 88% of the keywords a brand bid on, its domain was not among the sources AI Mode cited**, and in about 85% the brand did not rank organically for that keyword either. Paid, organic, and cited barely overlapped.

## Why doesn't paying for an ad earn a citation?

Because the ad auction and the citation engine are answering different questions. A text ad is placed by a **paid-media auction**: you bid, and the slot is allocated by bid and ad quality. A [citation](/glossary/citation) is chosen by a **retrieval-and-synthesis** step: AI Mode splits your question into many sub-queries through [query fan-out](/glossary/query-fan-out) and pulls the pages that best answer each branch, judged on relevance, extractability, corroboration, and entity strength. Money is an input to the first process and not to the second.

SE Ranking framed it directly, and the line is worth keeping:

> The ad slot is a paid-media decision; being cited is an authority-and-content decision, and neither one moves the other.

This is why the controlled comparison is the most important part of the study. It is not merely that few advertisers were cited; it is that once you match advertisers and non-advertisers on domain strength and organic standing, the ad buys **no citation lift at all**. Whatever citation advantage a big advertiser has, it comes from being a strong [entity](/glossary/entity-authority) with good content, not from the ad.

## How does this fit what we already know about AI Mode citations?

Cleanly, and it sharpens the picture. Earlier data already showed AI Mode citing largely from **outside** the classic rankings: only about 19% of its citations traced to the organic top-20, far less than AI Overviews, because fan-out reaches well beyond the top-10 (see [do AI Mode and AI Overviews cite the same sources?](/blog/ai-mode-vs-ai-overviews-citations)). If ranking first is only a modest citation advantage, it is unsurprising that a paid slot, which the model's retrieval step never consults, is none.

It also reinforces the broader decoupling of rank and citation covered in [does Google rank get you cited by AI?](/blog/does-google-rank-get-you-cited-by-ai). Three visibility channels now sit side by side in a single AI Mode result, each won differently:

- **Paid** — text ads, allocated by auction. Buys placement, not citation.
- **Organic** — classic rankings. A modest, not decisive, citation input in AI Mode.
- **Cited** — the sources synthesised into the answer, chosen by relevance, extractability, corroboration, and entity strength.

Optimising for one does not deliver the others. We walk through the full three-way split, and where each surface is worth investing, in the companion comparison [paid, organic, and cited: the three systems behind AI Mode visibility](/blog/paid-organic-cited-ai-mode).

## What should brands do about it?

Treat ads and citations as separate line items with separate playbooks, and don't let a paid win read as an AI-visibility win.

- **Keep ad budgets for what ads do** — capturing high-intent commercial clicks, especially on expensive keywords where ad presence is highest. Just don't expect the spend to place you inside the synthesised answer.
- **Earn the citation the earned way.** Answer-first passages for the predictable sub-questions, facts in text and [structured data](/glossary/structured-data) rather than images, third-party [corroboration](/glossary/corroboration), and consistent entity signals. The method is in [how to get cited in Google AI Mode](/blog/how-to-get-cited-in-google-ai-mode) and [how to get cited by AI](/blog/how-to-get-cited-by-ai).
- **Measure the channels separately.** A brand can be advertising, ranking, and cited on the same keyword, or present in only one. Track your citation share as its own line, distinct from ad impressions and organic rank, and watch it across engines over time.

That last point is the discipline **Buffy Intel** is built for: it tracks whether AI engines actually cite and recommend your brand, snapshot over snapshot, so you can see your earned AI visibility as its own signal, not something a media budget can quietly paper over. If you want to know whether you're being cited, and not just whether your ad showed up, that's the line to watch.

## Do Google AI Overviews actually cause click loss? The first randomized experiment
Source: https://heybuffy.com/blog/do-ai-overviews-cause-click-loss

**Yes. The first randomized experiment shows AI Overviews cause the click loss, not just accompany it.** In a 2026 field experiment by Saharsh Agarwal (Indian School of Business) and Ananya Sen (Carnegie Mellon Heinz), an [AI Overview](/glossary/ai-overviews) was hidden at random for some searches. Showing it **cut outbound organic clicks by about 39.8%** (0.62 per search without the overview, 0.37 with it) and pushed the **share of no-click searches from 0.54 to 0.73**. Crucially, the lost clicks were not lower quality, and satisfaction did not improve.

This is a dated reference, not a new dataset. **Last reviewed: 7 August 2026.** The figures come from Agarwal and Sen's working paper, first posted to the Social Science Research Network on 3 April 2026 and last revised 17 June 2026; it is not yet peer-reviewed. It matters because almost every earlier click-loss number is *associational*. Our own [AI Overview click-loss reference](/blog/how-much-do-ai-overviews-reduce-clicks) reports Ahrefs figures of roughly 34.5% to 58% and hedges them as associations, not proof of cause. This experiment supplies the causal complement, and its ~40% lands inside that same band, so it sharpens the existing read rather than contradicting it.

## What did the experiment actually measure?

The causal question, using random assignment. Instead of counting clicks on pages that happen to sit under an AI Overview, the researchers built a browser extension and randomly decided, per user, whether the overview appeared. That random switch is what turns a [correlation into causation](/glossary/correlation-vs-causation): the groups are alike except for the one thing being tested.

| Attribute | Detail |
|---|---|
| Design | Randomized field experiment (browser extension) |
| Participants | **1,065** US desktop Chrome users (analytical sample) |
| Searches observed | **68,089** unique searches |
| Groups | Control (standard results), hide-overview (AI Overview removed), plus an exploratory arm redirected to [Google AI Mode](/glossary/google-ai-mode) |
| Data collection | Roughly **January–February 2026** |
| Venue | SSRN working paper (posted 3 Apr 2026, revised 17 Jun 2026); not peer-reviewed |

Source: Agarwal and Sen, 2026 (SSRN working paper). The design isolates the *effect of the overview appearing* from everything else about a query, which a raw "clicks are lower where overviews show" count cannot do.

## How much did AI Overviews cut clicks?

By about 39.8%, concentrated on informational queries. Removing the overview lifted outbound organic clicks and lowered the no-click rate; both moves reversed when it reappeared.

| Metric | AI Overview shown | AI Overview removed | Effect |
|---|---|---|---|
| Outbound organic clicks per search | **0.37** | **0.62** | ~**39.8%** fewer clicks when shown |
| Share of no-click searches | **0.73** | **0.54** | Roughly a third more zero-click sessions |
| Navigational / transactional queries | — | — | **No measurable change** |

Source: Agarwal and Sen, 2026 (SSRN working paper). The overview triggered on roughly 41% of all queries and 53% of informational ones, and the losses concentrated there, so the effect on any one site scales with how informational its query mix is. This is the [zero-click](/glossary/zero-click-search) pattern the [featured snippet](/glossary/featured-snippet) began and generative answers deepened, and it is the mechanism behind the [great decoupling](/glossary/great-decoupling) of impressions from clicks.

## Were the lost clicks just low-value traffic?

No, and this is the finding that changes the argument. A common industry reassurance is that AI Overviews only skim off low-intent visits nobody wanted. The experiment tested that directly and found no support for it.

- **Engagement was unchanged.** Bounce rate, time on site, and how often people bounced back to the results page did not differ meaningfully between groups.
- **Satisfaction did not improve.** An endline survey found no difference in overall satisfaction, perceived information quality, or ease of finding information when overviews were present.
- **Ads were untouched.** Sponsored clicks did not move, and neither did clicks within Google's own properties; the displacement fell specifically on outbound organic clicks to the open web.

> The clicks an AI Overview removes look like ordinary clicks, not junk. Publishers lose real visits, users are no more satisfied, and only sponsored and Google-owned destinations are spared.

## Why does a randomized experiment matter more than the usual data?

Because it breaks the tie that association studies cannot. Most AI-visibility claims rest on comparing pages or queries that differ in many ways at once, so any single trait gets unfair credit. Random assignment holds everything else roughly constant, which is the same logic behind reading GEO research critically in [does GEO actually work](/blog/does-geo-actually-work) and behind testing changes with a [holdout](/glossary/holdout-test) rather than a bare before-and-after, the method in [how to test whether a change moved your citations](/blog/test-if-a-change-moved-your-ai-citations). It is a single study on US desktop Chrome, so it is not the last word, but it is the first *causal* word on a question that association could only circle.

## What are the study's limits?

Real ones, which is why the honest claim is "strong causal signal," not "settled law." Read the numbers with these in view.

| Caveat | Why it matters |
|---|---|
| Working paper | Posted to SSRN and revised, but not yet peer-reviewed |
| Narrow population | 1,065 US desktop Chrome users; mobile, other markets, and logged-out behaviour may differ |
| Short window | Roughly five weeks of data, less than a full seasonal cycle |
| Exploratory AI Mode arm | The redirect to AI Mode was suggestive, not a clean like-for-like comparison |
| One team, one design | Direction is firm; the precise 39.8% will vary by query mix and setting |

Source: Agarwal and Sen, 2026 (SSRN working paper), with limitations as described by the authors and coverage. None of these rescue the "it's only junk traffic" reading; they bound the figure, not the finding.

## What should you do with this?

Treat AI Overview click loss as real and causal, then change the scoreboard rather than mourn the clicks. Concretely:

- **Stop waiting for proof of cause.** You now have it; plan for a structural drop in outbound clicks on informational queries, and size it to your own query mix using [our estimation method](/blog/estimate-ai-overview-click-loss).
- **Measure citations, not just sessions.** If traffic is your only metric, AI search reads as pure loss even while your brand is shown and cited; track presence and [citation](/glossary/citation) coverage too, per [from clicks to citations](/blog/from-clicks-to-citations).
- **Compete to be the cited source.** You cannot opt out of the overview appearing, but being named inside it is the winnable game, and it is not the same surface as [AI Mode](/blog/ai-overviews-vs-ai-mode-click-loss), which behaves differently again.

The click loss is now causally established; the number that governs your strategy is whether your brand is still being shown, cited, and recommended inside those answers, measured across engines and over time. That answer-level, cross-engine visibility measurement is exactly what **Buffy Intel** is built to provide. Questions: support@flash.tech.

## Do Google's spam updates affect your AI Overviews and AI Mode visibility?
Source: https://heybuffy.com/blog/do-google-spam-updates-affect-ai-visibility

Mostly yes. Because [AI Overviews](/glossary/ai-overviews) and [AI Mode](/glossary/google-ai-mode) are grounded in Google's ranked web results, a site demoted by a spam update tends to lose AI-answer citations along with its blue-link rankings. The effect is partial, lagged, and confined to Google's own surfaces — it does not directly touch ChatGPT, Perplexity, or Claude. This explainer covers what Google's August 2026 spam update actually did, how a ranking demotion propagates into AI answers, and what to do if your AI visibility dropped.

**Last reviewed: 25 August 2026.** The rollout facts below are from Google's Search Status Dashboard and contemporaneous trade coverage (Search Engine Land, Search Engine Journal), attributed and dated. The propagation mechanism is a reconciliation of how Google says its AI surfaces work, not a new dataset — treat the *direction* as firm and any single magnitude as directional.

## What did Google's August 2026 spam update do?

It was a routine algorithmic enforcement of Google's existing [spam policies](/blog/google-spam-policy-ai-answers), not a new rule. Google announced no new spam policy types with the rollout and pointed site owners back to the policies already published.

| Fact | Detail | Source |
|---|---|---|
| Rollout start | 18 August 2026, ~9:27 a.m. Pacific | Google Search Status Dashboard |
| Rollout complete | 21 August 2026, ~1:49 a.m. Pacific | Google Search Status Dashboard |
| Duration | ~2 days, 16 hours | Search Engine Land (2026) |
| Scope | Global, all languages | Search Engine Land (2026) |
| New policy types | None announced | Search Engine Journal (2026) |
| Position in 2026 | Third spam update of the year (after March and June) | Search Engine Roundtable (2026) |

Google's documentation says recovery can take **months**, because its automated systems need time to see that a site now follows the rules. As of the rollout, Google had **not** said whether this particular update targeted the "manipulating generative AI responses" behaviour it added to its spam policy in a May 2026 clarification. So treat the AI-specific intent as unconfirmed and reason from the mechanism instead.

## Do spam updates reach into AI Overviews and AI Mode?

Yes, indirectly, because those surfaces are not a separate index. AI Overviews and AI Mode are generated by a Google model that is [grounded](/glossary/grounding) in Google Search results — it retrieves from the same ranked web index that a spam update reranks. When a spam update demotes a site in classic ranking, it shrinks that site's presence in the exact pool the AI answer draws from.

- **One index, several surfaces.** A spam update changes Google's ranking of the web. Google Search, AI Overviews, and AI Mode all read from that ranking, so a demotion propagates outward from blue links into the AI answers built on top of them.
- **Citations lean on ranking on Google's surfaces.** Studies consistently find that [Google rank still helps you get cited](/blog/does-google-rank-get-you-cited-by-ai) on AI Overviews and AI Mode (far more than on ChatGPT). A spam update moves that ranking input against you.
- **It compounds a corpus that already tilts.** Separately, the trustworthy web is [opting out of AI crawlers faster than spam is](/blog/do-ai-engines-filter-out-spam) — so a Google-side demotion of a legitimate site is one more way good sources thin out of AI answers.

## How much AI visibility does a spam-update demotion actually cost?

Expect a directional drop, not a fixed one — the size depends on the engine and the query. The rank-to-citation link is real but loose: ranking is one input among several, and its weight varies by query type and surface, so a demotion rarely maps one-to-one onto lost citations.

| Surface | Sensitivity to a Google spam demotion | Why |
|---|---|---|
| Google AI Overviews | High | Grounded in ranked Google results; ranking is a meaningful citation input |
| Google AI Mode | High | Same grounding; pulls heavily from ranked results |
| Google Search (blue links) | High | Direct target of the update |
| ChatGPT | Low / indirect | Own retrieval; least tied to Google rank of any engine |
| Perplexity, Claude | Low / indirect | Own retrieval and crawls; not Google's ranking |

The honest read: a spam-update hit is most likely to cost you citations on Google's own AI surfaces, on a lag, and to a degree that tracks how much your category's AI answers depend on ranking in the first place.

> A Google spam update does not have a separate AI penalty — it reranks one index, and every Google surface built on that index, blue links and AI answers alike, moves together.

## Does it affect ChatGPT, Perplexity, or Claude?

Not directly. A Google spam update reranks Google's index. ChatGPT, Perplexity, and Claude generate answers from their own retrieval pipelines and, where they lean on a search backend, more often use Bing or their own crawls than Google's ranking. So a site demoted by a Google spam update can hold its ChatGPT citations while losing its Google AI Overviews citations in the same week.

That divergence is the practical point: because a Google-only event moves your Google AI surfaces but not the others, a single blended "AI visibility" number will hide what happened. Watching each engine on its own is the only way to see a Google spam update as the Google-shaped event it is — the same reason [AI visibility shifts on its own](/blog/why-ai-visibility-changes-without-you) for reasons that have nothing to do with your content.

## How do you tell a spam-update hit from ordinary AI-answer volatility?

Line up the timing and the surfaces. AI answers churn constantly on their own, so a drop is only a spam-update signal if it fits the update's fingerprint.

1. **Match the dates.** Did the drop begin inside the rollout window (18–21 August 2026 for this one)? A change that predates or postdates the window is probably something else.
2. **Check that blue links moved too.** A spam update hits classic ranking first. If your organic rankings fell alongside the AI citations, that points to a ranking-level cause; if only the AI answer changed, it is more likely engine-side volatility.
3. **Check whether it is Google-only.** If Google AI Overviews and AI Mode citations dropped but ChatGPT and Perplexity held, that is the signature of a Google-index event rather than a web-wide one.
4. **Read it against a policy, not a vibe.** A spam update enforces named policies. If a page cleanly matches one, that is the lever to fix; if nothing matches, resist "spam-proofing" a healthy page.

## What should you do if a spam update hit your AI visibility?

Fix the ranking cause, because on Google's surfaces that is the AI cause. There is no separate route back into AI Overviews.

- **Diagnose it as a ranking event.** Confirm the classic-ranking drop first, then treat the lost AI citations as a downstream symptom — the workflow in [diagnosing an AI visibility drop](/blog/diagnose-ai-visibility-drops).
- **Repair against the specific policy.** Identify which spam policy the affected pages breach and fix that, rather than editing pages that were never the problem.
- **Grow visibility the durable way.** The route back is the same one that earns citations in the first place: genuinely useful, well-[corroborated](/glossary/corroboration) content, not manipulation — see [growing AI visibility without spam](/blog/grow-ai-visibility-without-spam).
- **Wait on Google's timeline, and measure it.** Recovery takes months; track your Google AI Overviews and AI Mode citations as a per-engine line so you can see the return when it comes, and separate it from the day-to-day churn on other engines.

The takeaway for late 2026: Google's spam updates are a ranking event that now casts a shadow into AI Overviews and AI Mode, because those surfaces read from the same index — but the shadow is Google-shaped, partial, and lagged, and it says nothing about your standing on ChatGPT or Perplexity. Seeing that clearly means watching each engine separately over time, which is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Does mass-produced AI content hurt your AI search visibility?
Source: https://heybuffy.com/blog/does-ai-generated-content-hurt-ai-visibility

Mass-produced, templated AI content increasingly *hurts* visibility, but using AI to help write genuinely useful pages does not. That distinction is the heart of new Google research, reported by Search Engine Journal in June 2026, describing a **Scalable Cluster Termination System (S-CTS)** that detects AI-generated spam by spotting coordinated *networks* of similar content rather than judging each page in isolation. Here's what it means for brands that produce content with AI.

## What did Google's research actually describe?

Per the June 2026 reporting, Google researchers outlined a shift in how spam is caught:

- **Network-level, not page-level.** S-CTS identifies *clusters* of accounts and pages using similar AI-generated templates, instead of scoring isolated content. The stated rationale, quoted in the reporting: *"Traditional content-centric moderation fails against this coordinated, adversarial generation strategy."*
- **Similarity by embeddings.** It reportedly uses sentence-embedding similarity (Sentence-BERT) to find mathematically alike patterns across many pieces. The signature of templated generation at scale.
- **Fast adaptation.** Techniques like Low-Rank Adaptation (LoRA) and automatic prompt optimisation let the system adapt quickly as spam tactics change.

Two honest caveats. First, the paper primarily addresses *video* spam, with text-based methods the reporting notes are applicable to web content, so read it as a direction of travel, not a confirmed web-ranking change. Second, this is research and reporting, not an announced ranking update. Attribute it as "Google research, reported by Search Engine Journal, June 2026" and treat the specifics as directional.

## Does this mean AI-written content is penalised?

No, and that's the key misread to avoid. There is no evidence of a blanket penalty for AI assistance, and Google's standing position is that it rewards helpful, quality content regardless of production method. What the research targets is **coordinated manipulation**: thousands of near-identical, templated pages spun up to game rankings. The difference is intent and originality, not the tool.

| Activity | Detection risk | Why |
|---|---|---|
| AI as a drafting aid for specific, accurate, original pages | Low | Reads as genuine content; no coordinated template signature |
| Lightly-edited mass output across many near-identical pages | Rising | Cluster-level similarity is exactly what S-CTS is built to flag |
| Automated networks producing templated spam to manipulate rank | High | Coordinated, adversarial generation. The explicit target |

The lesson aligns with what the corpus has argued from first principles: [AI search can be manipulated only briefly](/blog/can-ai-search-be-manipulated), and scaled, low-substance content is a fragile strategy.

> Detection is moving from "is this page spam?" to "is this part of a coordinated spam network?", which makes templated content at scale a liability, and specific, original, corroborated content the durable play.

## What should brands do about it?

The defensive move and the [GEO](/glossary/generative-engine-optimization) move are the same one. Write content that is too specific and too corroborated to look like template output:

- **Lead with specifics.** Named, numeric, dated facts are hard to mass-produce and easy for engines to lift. The opposite of templated filler.
- **Build entity strength.** Be [consistently named and corroborated across the web](/blog/entity-strength-ai); coordinated spam has no real entity behind it, and engines increasingly lean on [corroboration](/glossary/corroboration) to decide what to trust.
- **Earn the citation on merit.** The reason [AI cites one brand over a near-identical competitor](/blog/why-ai-cites-one-brand) is substance and structure, not volume.
- **Keep it fresh and accurate.** Substantive updates beat churning out more pages; stale or thin content [decays out of answers](/blog/content-freshness-citation-cliff) anyway.

In short: use AI to help you produce *fewer, better, more specific* pages, not more of the same.

## How does this connect to getting cited?

It closes a loop the corpus keeps returning to. The fastest way to be **citable** is also the surest way to look nothing like spam: answer real questions with verifiable, well-structured, on-brand content. That's the whole of [how to get cited by AI](/blog/how-to-get-cited-by-ai), and it's why scaling thin content has always been the wrong bet for AI visibility.

Knowing whether your content is actually being cited and recommended, or quietly losing ground. Takes measurement across every engine, over time. That's exactly what **Buffy Intel** is built to provide.

## Does content length affect AI citations? What the conflicting studies show
Source: https://heybuffy.com/blog/does-content-length-affect-ai-citations

**Content length is not a meaningful AI-citation factor on its own.** The largest study to date found word count barely correlates with getting cited, and over half of cited pages come in under 1,000 words. What looks like a "longer wins" effect is really about coverage: a comprehensive page answers more of the sub-questions an engine breaks a query into, so it gets pulled into more answers. The lever is how completely and how extractably you answer, not how many words you write.

**Last reviewed: 12 August 2026.** Every figure below is attributed, dated, and hedged. This piece reconciles two single-study datasets that appear to disagree; treat each number as directional and check its denominator, engine, and date before you quote it.

## Do longer pages get cited more by AI?

Not for the reason most people assume. Two 2026 datasets look like they contradict each other, and the disagreement is where the useful answer hides.

The largest analysis, from Ahrefs (published December 2025), studied **174,048 pages** drawn from 1.67 million cited URLs across 560,346 [AI Overviews](/blog/ai-overviews-complete-guide). It found the correlation between a page's word count and whether it got cited was about **0.04 on a Spearman scale, effectively zero.** A smaller study of 1,000 AI Overviews (April 2026) found the opposite-sounding result: pages over 2,500 words were cited about **1.6x more often** than pages under 800.

Both are right. They measure different questions. Ahrefs asked "does word count predict whether a given page is cited?" (no). The smaller study asked "do longer pages accrue more citations overall?" (often yes) without isolating *why*. The most plausible why is coverage, not length, and the rest of this piece separates the two.

## What did the largest study find about length and citations?

Ahrefs' 174,048-page analysis found length distributed almost evenly across cited pages, with a slight lean toward shorter content. The near-zero correlation means a page's word count told you almost nothing about its odds of being cited.

| Cited-page length | Share of AI Overview citations |
|---|---|
| Under 1,000 words | 53.4% |
| 1,000–2,000 words | 30.6% |
| Over 2,000 words | 16.0% |

*Source: Ahrefs, December 2025, 174,048 pages across 560,346 AI Overviews. Mean length of cited content was ~1,282 words; word-count-to-citation correlation ~0.04. The dataset skews toward blog and audio content, which can pull the median down.*

The takeaway Ahrefs drew is blunt: **content length is not a major factor in whether you get cited.** More than half of the citations went to pages under 1,000 words, which directly contradicts the folklore that only 5,000-word pillar pages earn AI citations.

## Then why do comprehensive pages seem to get cited more?

Because AI answers are assembled through [query fan-out](/glossary/query-fan-out). The engine breaks one question into many sub-queries and retrieves a source for each, then synthesises. Citation happens at the passage level, not the page level: the engine lifts the [chunk](/glossary/content-chunk) that best answers each sub-query, wherever it lives.

That mechanism explains the smaller study cleanly. A comprehensive page covers more of the sub-questions a query fans into, so it has more chances to win a branch and be cited. Its extra citations come from **breadth of coverage, not density of words.** The same study noted the lift was "step-shaped, not linear," starting around 1,800 words and plateauing near 3,500, exactly what you'd expect if the gain comes from covering more distinct sub-topics rather than from length itself.

So a 3,000-word guide that answers eight real sub-questions can out-cite a 600-word page. But a 3,000-word page that says one thing eight times will not. The confound is that thorough writers tend to write longer, so length and coverage travel together, and it is coverage doing the work.

## Does the answer differ by AI engine?

Directionally, yes, though this is mechanism-level reasoning more than a clean measured number, so treat it as a working model, not a promise.

- **Google AI Overviews** retrieve a best-matching fragment per sub-query, which is why length barely matters there (the 0.04 correlation). A short page that nails one sub-query competes evenly with a pillar page.
- **ChatGPT** does [fewer, longer-tail fan-outs](/blog/how-chatgpt-picks-sources) and tends to favour a source that covers a topic in depth, so comprehensive pages can carry more weight there.

The safe planning rule across engines: cover the real sub-questions completely, and make each answer independently liftable. That satisfies both a fragment-retrieving engine and a depth-favouring one, without betting on either.

## So how long should your content be?

As long as it takes to fully answer the question, and no longer. Length is an output of coverage, not an input you target. Three rules follow from the data:

1. **Answer completely.** Cover the core question and its predictable branches (uses, comparisons, specs, troubleshooting, who-it's-for). Each branch is a chance to be cited.
2. **Chunk tightly.** Give each sub-question its own self-contained, answer-first section of roughly 100–300 words, so an engine can lift it without the rest of the page. This is the work in [structuring a page into extractable chunks](/blog/structure-content-into-extractable-chunks).
3. **Never pad.** The Princeton GEO experiment found [keyword-stuffing a page](/blog/what-content-changes-lift-ai-citations) made it about 10% *less* visible. Extra words with no new answer are dead weight at best and a quality signal against you at worst.

The thing to add is not length but evidence: [specific statistics, named quotes, and cited sources](/blog/add-citation-lifting-elements) on each claim. That is what the controlled experiments actually rewarded.

> AI cites the passage that answers the question, not the page with the most words. Write to cover more real questions, not to hit a word count.

## How the two studies line up

| Question | Finding | Source |
|---|---|---|
| Does word count predict if a page is cited? | No; correlation ~0.04, 53% of cited pages under 1,000 words | Ahrefs, Dec 2025 (174,048 pages) |
| Do comprehensive pages accrue more total citations? | Yes; pages >2,500 words cited ~1.6x more, step-shaped, plateaus ~3,500 | 1,000-AI-Overview study, Apr 2026 |
| Does padding a page longer help? | No; keyword-stuffing ~10% worse | Princeton GEO experiment (in-corpus) |

The three reconcile into one rule: **breadth of coverage and extractable structure earn citations; raw length does not.** A short, complete, well-structured answer beats a long, padded one at every engine measured.

Knowing whether a length or structure change actually moved your citations takes measurement, not a benchmark percentage. That is where **Buffy Intel** fits: it snapshots whether AI engines cite and recommend your brand over time, so after you rework a page for coverage and extractable chunks, you can watch whether your citation share moved, engine by engine, instead of assuming a study's numbers carry over to your niche.

## Does domain authority affect AI citations?
Source: https://heybuffy.com/blog/does-domain-authority-affect-ai-citations

**Barely.** Traditional Domain Authority — the third-party, backlink-based score from tools like Moz or Ahrefs — is a weak predictor of whether AI engines cite you. In Featured's 2026 analysis of **22,881** AI citations across ChatGPT, Claude, Perplexity, and Gemini, **34.5%** came from sites with a Domain Authority under 40. AI engines retrieve and cite at the passage level, not the domain level, so a small site with the cleanest, best-matched answer can be lifted ahead of a household-name domain.

**Last reviewed: 26 August 2026.** The headline figure is from Featured's AI Citation Report (405 [GEO](/glossary/generative-engine-optimization) audits conducted 2 June–21 August 2026). It is **single-vendor, preview-period** data — attribute "Featured, 2026" and treat the exact percentage as directional. The corroborating correlations below are dated and attributed in place.

## Does a high Domain Authority score get you cited by AI?

Not reliably. Domain Authority (DA) is a third-party score — most familiar as Moz's 0–100 metric, with Ahrefs' Domain Rating a close cousin — that estimates how likely a domain is to rank in classic Google search, built mostly from the quantity and quality of its backlinks. It was never a measure of AI citation, and the 2026 data shows it does not stand in for one.

Featured's AI Citation Report is the freshest cut. Across the audits it carried out during its preview period, it recorded the Domain Authority of every cited source:

| Featured AI Citation Report (2026) | Figure |
|---|---|
| AI citations analysed | **22,881** |
| GEO audits (2 Jun–21 Aug 2026) | **405** |
| Engines covered | ChatGPT, Claude, Perplexity, Gemini |
| Citations from sites with **DA under 40** | **34.5%** |

Source: Featured, 2026 (single-vendor; directional). More than a third of the cited sources were domains a classic SEO audit would treat as low-authority. That is the opposite of what you would expect if AI engines simply cited the biggest domains — and it lines up with the wider pattern that AI citations [do not track Google rank](/blog/does-google-rank-get-you-cited-by-ai) either.

## Why doesn't Domain Authority predict AI citations?

Because AI retrieval operates on different inputs from the ones Domain Authority summarises. DA is a proxy for link-based ranking power. An answer engine, by contrast, fans one question into many sub-queries and then selects passages that score on relevance to the sub-query, extractable structure, freshness, and [corroboration](/glossary/corroboration) — not on how many sites link to the domain.

The practical consequence: the unit that gets cited is a self-contained chunk, not a whole domain. A niche site that answers one specific question cleanly, in a table or an answer-first paragraph, presents a better candidate passage than a high-DA page that buries the same fact three scrolls down. This is why one 2026 correlation analysis reported Domain Authority explaining only about 3% of the variation in AI citations (single-source, directional) — the metric is measuring the wrong thing for this job.

## What actually drives AI citations, if not Domain Authority?

The signals that do correlate are about your standing as a recognised source and the quality of the passage, not your backlink count. Here is how the better-evidenced levers compare, each attributed:

| Lever | What it is | Evidence (attributed, dated) |
|---|---|---|
| [Entity authority](/glossary/entity-authority) | How strongly AI associates your brand with a topic | Repeatedly found to predict citations more than backlinks (2026) |
| Brand mentions across the web | Being named, with or without a link | Ahrefs: correlated with AI Overview presence **0.664** vs **0.218** for backlinks (75,000 brands, 2026) |
| Topical depth | Comprehensive, single-topic coverage | Focused explainers overtake broad guides on citations (Promptwatch, 2026; directional) |
| Extractable structure | Answer-first passages, tables, clean HTML | Zyppy rated "answer near the top" 8.8/10, "AI-ready structure" 8.6/10 (2026) |
| Freshness | Recently reviewed/updated | AI-cited pages average ~25.7% fresher than organic top-10 (2026) |

Source detail and the ranking of these levers are laid out in our [three AI-citation levers](/blog/freshness-structure-authority-levers) reference. Read every figure as directional and correlational — but note the through-line: none of them is Domain Authority, and the one that looks closest ("authority") is *entity* authority, a different thing.

> Domain Authority tells you how a page might rank in Google. It does not tell you whether an AI will cite it — a third of AI citations come from sites a classic audit would call low-authority.

## Does this contradict "authority matters for AI citations"?

No — the two claims are about different kinds of authority, and conflating them is the whole trap. When the research says authority is a strong AI-citation signal, it means [entity authority](/glossary/entity-authority): how well-established and credible your brand is as a recognised entity for a topic, read from brand search volume, knowledge-graph presence, and how often your brand co-occurs with its category. That is *earned by being talked about*, not by accumulating links.

Traditional Domain Authority is the backlink-based SEO score. The same Ahrefs data that props up "authority matters" is the data that separates the two: branded web mentions correlated with AI presence about three times more strongly than raw backlink count. So the honest reconciliation is that *being a recognised source* matters a great deal, and *your Moz or Ahrefs authority number* barely moves the needle on its own. High entity authority usually comes with a high DA, which is why the two get muddled — but it is the mentions and the topic association doing the work, not the link score.

## What should you do about your Domain Authority for AI visibility?

Stop treating the DA number as your AI-visibility scoreboard, and spend the effort where the citations actually come from.

- **Do not chase the DA score for its own sake.** Link-building to lift a third-party authority number is one of the slowest and least direct ways to earn an AI citation. It is not useless for classic SEO — it is just the wrong target here.
- **Build entity authority instead.** Earn brand mentions across independent coverage, keep your entity consistent across the web, and become the recognised source for a specific topic — the durable lever in [entity strength](/blog/entity-strength-ai).
- **Win at the passage level.** Answer-first chunks, facts in tables, clean server-rendered HTML — make each page a better candidate passage than a bigger domain's. Start with [how to get cited by AI](/blog/how-to-get-cited-by-ai) and [prioritising your structured data](/blog/prioritize-your-structured-data).
- **Check for the cited-but-not-named gap.** Featured also flagged cases where an engine cites a brand's own site without naming the brand in the answer — the [brand-mention vs source gap](/blog/brand-mention-gap-vs-source-gap) worth auditing.
- **Measure citations, not authority.** Track your own [citation](/glossary/citation) share per engine over time; a domain-authority tool cannot tell you whether ChatGPT or Perplexity actually cited you.

The honest read for late 2026: a low or mid Domain Authority is not the barrier to AI citation it is for classic ranking — a third of AI citations come from sites under DA 40 — so the winning move is to be the clearest, best-corroborated source on your topic, not the biggest domain. Watching which of your pages actually get cited, per engine and over time, is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## Does ecommerce SEO still matter for AI search?
Source: https://heybuffy.com/blog/does-ecommerce-seo-matter-for-ai-search

Yes. Ecommerce SEO still matters for AI search, because AI search is built on top of SEO, not instead of it. The crawlable, server-rendered, structured foundation that classic ecommerce SEO creates is exactly what an AI engine needs to fetch, parse, and cite your products. What changes is the *objective*: you're now optimising to be **named and recommended inside an answer**, not just to rank a link a shopper clicks.

## Does traditional ecommerce SEO still matter for AI?

It does. [Generative engine optimisation](/glossary/generative-engine-optimization) builds on SEO fundamentals; it doesn't replace them. An AI engine can only cite a product page it can reach, render, and read, and reachability, rendering, and clean markup are precisely what technical SEO delivers. A store that neglected SEO is usually invisible to AI for the same reasons it was invisible in search: pages the crawler can't get to, facts locked in images or JavaScript, thin duplicate copy.

The shift is in measurement. Organic search still drives a large share of ecommerce traffic, but a growing slice of discovery now happens inside an AI answer the shopper never clicks through. So the foundations stay; the scoreboard moves from rankings and clicks to [citations](/glossary/citation) and recommendations.

## Which ecommerce SEO foundations transfer to AI visibility?

Most of the core technical work pays off twice. Each SEO foundation maps directly to something an AI engine needs:

| Ecommerce SEO foundation | Why AI search needs it |
|---|---|
| Crawlable architecture, clean URLs, XML sitemap | An engine can't cite a page it can't discover or fetch |
| Server-rendered HTML (not JS-only) | Facts that only appear after JavaScript runs are often invisible to crawlers |
| Product/Offer [structured data](/glossary/structured-data) | Labels exactly what you sell. Price, availability, attributes, so the model doesn't guess |
| Unique, specific product & category copy | Manufacturer-default descriptions get skipped; specific, numeric copy gets lifted |
| Fast, mobile-friendly pages | Slow or render-blocked pages get crawled less and parsed worse |
| Descriptive internal linking | Builds the topical cluster that signals entity relationships |

The takeaway: if you've done ecommerce SEO well, you've already paid most of the *reachability and parseability* bill AI search charges. (For the catalog specifics, see [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents) and whether [page speed affects AI visibility](/blog/does-page-speed-affect-ai-visibility).)

## What does AI search add that SEO never covered?

Reachability gets you considered; it doesn't get you chosen. The new layer is about being the **extractable, corroborated, recommendable** option:

- **Extractability over ranking.** Retrieval happens at the passage level. Write product and category copy answer-first, in self-contained chunks, with specs in real tables, so a model can lift a clean, accurate line about your product.
- **Entity strength.** Engines lean on how well-established you are as a brand entity. Consistent naming, descriptions, and facts across your site, profiles, and the wider web compound into citations. See [entity strength for AI](/blog/entity-strength-ai).
- **Corroboration, not just self-claims.** AI engines trust community-edited and third-party sources heavily. Reviews, and authentic presence in [communities like Reddit](/blog/how-to-use-reddit-for-ai-search-visibility), corroborate what your PDP claims.
- **Earned placement in best-of lists.** For "best X" buyer questions, independent roundups get cited far more than brand pages, so pursue [earned placement in the lists AI engines cite](/blog/get-into-ai-cited-best-lists) rather than a self-listing page, as the [listicle effect](/blog/why-ai-loves-listicles) predicts.

> Classic SEO decides whether an AI engine *can* read your store. The new layer decides whether it *chooses* you. You need both. One is the floor, the other is the win.

## How should a lean store prioritise?

Don't boil the ocean. Sequence the work so the foundation comes first:

1. **Fix reachability.** Confirm your [CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers), pages are server-rendered, and the sitemap is clean. Nothing else matters if engines can't fetch you.
2. **Complete your structured data.** Product/Offer markup with accurate price, availability, and attributes on every PDP.
3. **Rewrite thin and duplicate copy.** Replace manufacturer defaults with specific, numeric, answer-first descriptions on your top products and categories.
4. **Build entity and corroboration signals.** Consistent brand facts everywhere; encourage genuine reviews; participate authentically where buyers discuss your category.
5. **Pursue earned placement** for your commercial-intent "best X" terms.
6. **Measure citations, not just rank.** Track whether AI engines surface and recommend you over time.

The honest summary: ecommerce SEO is the price of entry to AI search, not a relic of the old one. Keep the fundamentals, add the citation-and-recommendation layer on top, and measure the new scoreboard, which is what **Buffy Intel** is built to watch.

## Does GEO actually work? What a critical survey of 45 studies found
Source: https://heybuffy.com/blog/does-geo-actually-work

**The evidence that specific GEO content tweaks reliably increase whether AI engines retrieve or send traffic to your page is weak; the effects that replicate are narrower than the marketing suggests.** That is the conclusion of a July 2026 critical survey of 45 studies (2023-2026) by Olivier Martinez, ["Optimizing Visibility in Generative Engines"](https://arxiv.org/abs/2607.14035) (arXiv 2607.14035, dated 15 July 2026). Its finding, in the authors' words: *"already-retrieved content can causally alter its citation or use, but no reviewed technique shows a stable, longitudinal, cross-platform causal effect on organic discoverability or downstream behavior."* It is a single-author pre-print, so read it as a rigorous synthesis to pressure-test, not settled law. But its core distinction is one every [generative engine optimization](/glossary/generative-engine-optimization) claim should be held to.

## What did the survey actually find?

That GEO is not one ranking task but a **pipeline of stages**, and evidence for a technique at one stage rarely carries to the others. The survey models the path as: search activation, crawling and indexing, retrieval, reranking and context allocation, citation, prominence, factual absorption, and finally user behavior. A content edit can help late stages (how much you are quoted once selected) while doing nothing, or worse, at the early stage that decides whether you are selected at all.

Within that frame, three results are worth pinning down, all attributed to the survey and its reviewed corpus:

| Claim | What the evidence shows | How to read it |
|---|---|---|
| Content edits lift visibility | Real, but only *after* retrieval, in controlled testbeds | Prominence effect, not a retrieval or traffic effect |
| A single technique reliably wins across engines | Not found in 45 studies | Generic heuristics transfer poorly between engines |
| More citation-optimized = more cited overall | Sometimes the reverse | Rewrites can cut retrieval, negating downstream gains |

The one-line summary: **the most reproducible levers were topical relevance and context position, not clever formatting; and competition erodes individual gains** as everyone applies the same edits.

## Where does the "40% uplift" number come from?

From a single metric in one controlled experiment, not from live traffic. The survey traces the widely-quoted 40% to the foundational Princeton GEO study, covered in our own explainer on [which content changes lift AI citations](/blog/what-content-changes-lift-ai-citations). There, the [Position-Adjusted Word Count](/glossary/position-adjusted-word-count) metric rose from **19.3 to 27.2** (about a 41% relative gain) under a "Quotation Addition" strategy.

The catch the survey stresses: that gain occurred *"conditional on a source already being present in a fixed context"*, a testbed where five documents had already been supplied to the generator. In the survey's words, the foundational gains *"are valid within its experimental setting"* but *"establish neither organic discoverability nor durable traffic effects."* So the number describes how much more of your wording an answer reuses once you are in the candidate set. It says nothing about your odds of getting into that set, and nothing about clicks.

## Can GEO edits make a page harder to find?

Yes, and this is the survey's most useful correction. It reports an end-to-end test (the SAGEO Arena setup) in which optimizing **only a page's body text** for citability:

- **cut top-10 presence after reranking by about 16%**
- reduced average top-20 presence by roughly **9%**
- lowered final citation by about **6%**

> A rewrite that makes your passage more quotable once retrieved can make the whole page a worse match at retrieval, so it is pulled into the answer less often. Optimizing the prominence stage can quietly sabotage the [retrievability](/glossary/retrievability) stage.

This is why "we added statistics and quotations, so we will be cited more" does not always hold on a live engine. The [retrieval](/glossary/retrieval-augmented-generation) step and the prominence step reward partly different things, and a change tuned for one can cost you the other. The step-by-step way to check a claim like this before you act on it is in the companion how-to, [how to tell if a GEO study or stat is trustworthy](/blog/how-to-vet-a-geo-study).

## Does this contradict the Princeton GEO study, or Buffy's own advice?

No, and holding both without contradiction is the point. The [Princeton experiments](/blog/what-content-changes-lift-ai-citations) measured a *prominence* metric in a simulated engine and were careful to call the numbers controlled-environment relatives; our write-up already flagged the zero-sum, five-source arena as the reason the percentages inflate. The Martinez survey does not overturn that, it **formalizes the caveat and quantifies the missing stages**: prominence is not retrieval, and retrieval is not traffic.

It also lines up with Google's own position that, on its surfaces, [GEO is "still SEO"](/blog/is-geo-just-seo), no special files or tricks, just genuinely useful, crawlable, corroborated content. Two independent sources, an academic survey and a search engine, arriving at the same unglamorous answer is [corroboration](/glossary/corroboration), the signal worth trusting. The takeaway is not "GEO is fake." It is that **durable levers beat technique-chasing, and the only figure that counts for you is your own measured [citation coverage](/glossary/citation-coverage) per engine**, which is exactly what a [content edit's effect should be validated against](/blog/how-to-measure-ai-visibility) rather than a benchmark percentage.

## What should you actually do about it?

Stop buying single techniques as guarantees, and start treating visibility as a measured, multi-stage outcome:

1. **Compete on relevance and evidence, not formatting hacks.** The reproducible levers were topical relevance and clear, corroborated substance, the same things that survive [freshness decay](/blog/content-freshness-citation-cliff).
2. **Test edits against retrieval, not just prominence.** Before rolling a rewrite site-wide, confirm it did not make the page harder to retrieve, the survey shows that failure mode is real.
3. **Measure per engine, over time.** Citation behavior differs by engine and shifts weekly; a one-off benchmark cannot tell you if you are winning.
4. **Distrust any "+X% visibility" claim that will not say which stage it measured** (retrieval, prominence, citation, or traffic) and on which live engines.

That measurement loop, snapshotting whether AI engines cite and recommend your brand across engines and over time, is what **Buffy Intel** is built to close. The survey's lesson is Buffy's thesis stated academically: you cannot optimize what you refuse to measure, and the techniques worth keeping are the ones your own citation data confirms, not the ones a lab percentage promised.

## Does Google AI Mode cite itself? The self-preferencing data
Source: https://heybuffy.com/blog/does-google-ai-mode-cite-itself

Yes, Google AI Mode cites its own properties more than any other source. According to a 2026 study by SEO platform SE Ranking, Google.com is the single most-cited domain in AI Mode answers, appearing in about **17.42%** of all citations — more than the next six domains combined. Most of that points back to Google's own surfaces: roughly **59%** to its search results pages and **36.1%** to Google Business Profiles, with YouTube pushing Google-controlled properties to close to **20%** of all cited sources. This reference lays out the data, attributed and dated, and what a self-preferencing answer surface changes for your AI visibility.

**Last reviewed: 22 August 2026.** All figures below are from SE Ranking's AI Mode study (published February 2026) unless noted, based on **68,313 keywords across 20 niches and 1,321,398 citations** measured with its AI Mode tracker. It is a **single-vendor, directional** analysis, and SE Ranking notes other readings of the data are valid — so treat the exact percentages as a snapshot and cite "SE Ranking, 2026" with the date when you reuse them. AI Mode is a fast-moving surface; treat every share here as a mid-2026 state, not a fixed constant.

## How much does Google AI Mode cite itself?

More than any external site, by a wide margin. Google.com is the top-cited domain in AI Mode, and the share going to Google's own properties has climbed steeply:

| Finding | Figure | Source (date) |
|---|---|---|
| Google.com share of all AI Mode citations | ~**17.42%** (most-cited domain; more than the next six combined) | SE Ranking, 68,313 keywords / 1.3M citations (Feb 2026) |
| Google.com share, June 2025 | ~**5.7%** | SE Ranking (Feb 2026) |
| Google + YouTube combined share of all sources | ~**20%** | SE Ranking (Feb 2026) |
| Niches where Google was the single top source | **19 of 20** | SE Ranking (Feb 2026) |

The headline is the trajectory: Google's self-citation rate roughly **tripled in under a year**, from about 5.7% to 17.42%. This is a distinct measurement from the widely-cited finding that [AI Mode and AI Overviews cite different pages](/blog/ai-mode-vs-ai-overviews-citations) — that study is about how little the two Google surfaces overlap with each other; this one is about how much AI Mode points at Google itself.

## What does Google actually cite when it cites itself?

Its own search results pages, mostly — a recent shift. In June 2025, almost all of Google's self-citations were Business Profiles; by early 2026 the majority pointed to Google's own search results. Here is the current split of where Google's self-citations go:

| Google surface cited | Share of Google's self-citations |
|---|---|
| Google search results pages | **59%** |
| Google Business Profiles | **36.1%** |
| Other Google properties | **3.1%** |
| Google Support | **1.7%** |
| Google Flights | **0.1%** |

Source: SE Ranking, 2026. The two categories behave very differently for a brand. A citation to a **Google search results page** is a pointer back into Google — the page it links to is itself assembled from whoever ranks, so your visibility there still flows through classic rankings. A citation to a **Google Business Profile** is a Google-owned surface you can directly claim, verify, and optimise. The tripling since June 2025 is driven mostly by the search-results category, which barely existed a year earlier.

> When the most-cited "source" in an answer engine is the engine's own search page, being cited is no longer the same as being visited — the citation can resolve to another Google surface instead of your site.

## Which industries does Google self-cite the most?

Very unevenly — self-citation is concentrated in a few consumer verticals and nearly absent in specialised ones. This is the most actionable cut of the data, because it tells you how much room is left for an external citation in *your* category:

| Niche | Google self-citation rate |
|---|---|
| Travel | **53.18%** (highest) |
| Entertainment & hobbies | **48.74%** |
| Real estate | **30.54%** |
| Insurance | ~**6.48%** |
| Finance | ~**5.13%** |
| Careers & jobs | Google second; **Indeed cited 3.1× more** |

Source: SE Ranking, 2026. The pattern: in local-and-listings-heavy consumer categories — travel, real estate, local services — Google routes people to its own Business Profiles and results pages, so external citations are scarce. In expertise-heavy categories like finance and insurance, self-citation is low and third-party sources still win most of the answer. Careers is the one niche where a specialist (Indeed) outcites Google — echoing how [the most-cited domains in AI answers](/blog/most-cited-domains-ai-overviews) skew toward category specialists. Read your own vertical's number before deciding how much of your AI Mode strategy to bet on an external citation.

## Is this "self-preferencing," and does it break anything?

It fits the plain-language definition of [self-preferencing](/glossary/self-preferencing) — an answer surface disproportionately citing its owner's properties — but SE Ranking frames its numbers descriptively, and no regulator has made a formal finding about AI Mode citations as of mid-2026, so we do the same: report the concentration, and hedge the interpretation. Two things are worth separating:

- **The measurement is well-sourced.** 1.3 million citations across 20 niches is a large sample, and the direction is corroborated by other 2026 analyses of AI Mode's link behaviour.
- **The intent is not.** A search-results citation may reflect genuine utility (Google's own results *are* a comprehensive source for "show me options") as much as preference. Report the "what," hedge the "why."

For brands, the durable takeaway is structural, not legal: a growing slice of AI Mode's citations is a closed loop back into Google. That makes the surface behave more like a [walled garden](/glossary/walled-garden) and raises the [visibility concentration](/glossary/visibility-concentration) you are competing against — the same dynamic we cover in [is AI visibility winner-take-all](/blog/is-ai-visibility-winner-take-all) and [how to compete in concentrated AI categories](/blog/compete-in-concentrated-ai-categories).

## What should brands do when Google cites itself?

Play the surfaces Google hands back to itself, and measure the gap honestly. The self-citation shrinks the external-citation pool but does not close it:

- **Own the Google surfaces you can.** Since 36.1% of Google's self-citations are Business Profiles, a complete, verified, well-structured profile is now an AI Mode citation surface, not just a local-pack one — the [local AI-visibility fundamentals](/blog/local-aeo-win-your-city) apply directly.
- **Keep ranking, because the search-results citation depends on rankings.** When AI Mode cites its own results page, the pages *inside* it are still chosen by classic ranking, so being on page one still feeds the answer indirectly.
- **Weight your bet to your vertical.** In a ~5% self-citation category (finance, insurance) an external citation is very much in reach; in a ~50% category (travel, entertainment) plan for a smaller external slice and compete harder for it. Winning the [external citation in AI Mode](/blog/how-to-get-cited-in-google-ai-mode) matters most exactly where self-citation is lower.
- **Measure AI Mode as its own line, over time.** Self-citation tripled in a year; a static assumption goes stale fast. Track how much of your category's answer is Google-owned versus open, and watch the trend.

The honest read for late 2026: Google's AI Mode increasingly answers with Google, and the external citation is getting scarcer and more valuable in the categories where it still exists. Knowing how much of *your* category's AI answers point back to Google — and how that share is moving — is exactly what **Buffy Intel** is built to measure over time. Questions: support@flash.tech.

## Does ranking on Google get you cited by AI? It depends on the engine
Source: https://heybuffy.com/blog/does-google-rank-get-you-cited-by-ai

**A strong Google ranking still helps you get cited by AI, but how much depends entirely on which engine you mean, and the published studies disagree sharply on the magnitude.** For Google's own AI surfaces and Perplexity, ranking is a meaningful input; for ChatGPT it is the weakest signal of all. The one finding that holds across every dataset: ChatGPT is the least tied to Google rank. This piece lays out what each study actually measured, why the numbers conflict, and how to act on the durable part.

**Last reviewed: 13 July 2026.** Every figure below is attributed, dated, and hedged. This is a reconciliation of several single-vendor studies, not a new dataset. Treat each number as directional and check its denominator, engine, market, and date before you quote it.

## Does a top Google ranking still earn AI citations?

Partly, and unevenly. Classic search ranking clearly feeds Google's own AI features and Perplexity, both of which retrieve from a web index that ranking helps populate. But even there, ranking is neither necessary nor sufficient. Plenty of cited pages never ranked, and plenty of #1 results are never cited. And on ChatGPT, the link to ranking is faint.

The reason is mechanical. AI answers are assembled through [query fan-out](/glossary/query-fan-out). The engine breaks your question into many sub-queries and retrieves sources for each. A page that ranks well for the head term can still lose every sub-query, while a page outside the top-10 can win the specific branch an engine needed. So "ranks first" and "gets cited" are related but distinct outcomes, and the strength of that relationship varies by engine.

## How much does Google rank matter, engine by engine?

Here are the load-bearing figures, each with its source, and the caveat that they come from different studies measuring different things:

| Engine | How tied to Google rank? | Representative figure | Source (period) |
|---|---|---|---|
| **Google AI Overviews** | High | ~54% of AIO citations came from organic rankings; top-10 share of citations fell from ~76% to ~38% over 16 months | BrightEdge / ALM analyses (2026) |
| **Google AI Mode** | Moderate, disputed | ~20% of AI Mode citations from organic top-20; rank #1 cited ~27% of the time (US) | seoClarity (2026, 10,853 citations) |
| **Perplexity** | High (web-index driven) | ~89% of citations from Google's top-10; correlation ~0.87 with Google rank | CiteLens (June 2026, single market) |
| **Claude** | Moderate | ~53% of citations from Google's top-10; ~58% went to sites with a Wikipedia presence | CiteLens (June 2026, single market) |
| **ChatGPT** | Low | ~30% from top-10; ~70% of recommended sources ranked outside the top-10; near-zero correlation with rank | CiteLens (June 2026, single market) |

The summary the table supports: **Google's own surfaces and Perplexity reward classic ranking the most; Claude sits in the middle; ChatGPT rewards it the least.** That ordering is consistent across the studies even where the exact percentages are not.

## Why do the studies disagree so much?

Because they are not measuring the same thing, and one figure in particular shows how far the numbers can swing. On Google AI Mode, seoClarity's US analysis found only about **20% of citations came from the organic top-20**, while CiteLens's June 2026 benchmark reported **93% of AI Mode citations coming from Google's top-10**. Those are not small differences; they point in opposite directions.

They can both be defensible, because the studies differ on nearly every axis:

- **Market.** seoClarity's cut is US; CiteLens's is the Turkish market. Ranking pools and content ecosystems differ by country.
- **Query type.** CiteLens used 320 *templated buyer queries* across three consumer sectors. Buyer queries with clear commercial intent tend to surface established, well-ranked retailers. A different mix than a broad query set.
- **Denominator and date.** seoClarity measured share of top-20; CiteLens measured top-10; and the studies span different months of a fast-moving year.
- **Vendor interest.** CiteLens is a vendor benchmark published in a press release (Solustiq, 8 July 2026); seoClarity, BrightEdge, and ALM are separate vendors. Each has its own method and incentives.

This is the same hazard we flagged in [reconciling conflicting AI-citation studies](/blog/ai-citation-domain-concentration): pasting one study's number next to another's when they aren't the same measurement. For the AI-Mode-specific number, our standing reference remains [AI Mode versus AI Overviews citations](/blog/ai-mode-vs-ai-overviews-citations), which anchors on the larger US datasets. The CiteLens AI Mode figure is best read as a single-market outlier that illustrates how much market and query type move the result, not as a correction to it.

> The studies fight over how much Google rank matters for Perplexity and Google's AI. Anywhere from a fifth to nearly all of citations. They agree on ChatGPT: it is the engine least tied to your ranking.

## What holds across every study?

Strip out the disputed magnitudes and three findings survive:

1. **ChatGPT is the least rank-dependent engine.** CiteLens found near-zero correlation between ChatGPT citations and Google rank, with ~70% of its sources ranking outside the top-10. That matches [Seer Interactive's fan-out research](/blog/chatgpt-fanout-searches-for-brands), where ChatGPT 5.5 increasingly issues brand-name sub-queries rather than generic, ranking-driven ones, and our standing position that Google rank does not predict a ChatGPT citation.
2. **Google's own surfaces reward classic SEO the most.** This is consistent with Google's own guidance that optimizing for its AI features is [still SEO](/blog/is-geo-just-seo). The same index ranks results and feeds AI Overviews and AI Mode.
3. **Entity strength is the lever that travels.** Where ranking fades as a signal (ChatGPT, Claude), [entity strength](/blog/entity-strength-ai). A recognised, corroborated brand presence across the web. Rises. CiteLens's note that ~58% of Claude citations went to sites with a Wikipedia presence points the same way.

## What should you do about it?

Treat ranking as necessary-but-partial, and split your effort by where your buyers actually search:

- **Keep the SEO fundamentals.** Crawlable, semantic, well-structured pages still earn Google's AI surfaces and Perplexity, which lean on the web index. There is no version of this where ranking hurts.
- **Invest in entity strength for the rank-agnostic engines.** For ChatGPT and Claude, being a corroborated, consistently-named entity for your topic matters more than any single ranking. See [how to get cited by AI](/blog/how-to-get-cited-by-ai) and the [freshness, structure, and authority levers](/blog/freshness-structure-authority-levers).
- **Measure each engine separately.** Because the rank-to-citation link varies so much by engine, a win on Perplexity tells you little about ChatGPT. Track [citation](/glossary/citation) on each surface as its own line. The discipline in [how to measure AI visibility](/blog/how-to-measure-ai-visibility).
- **Distrust any single headline number.** The one figure that matters is your own measured citation share per engine, tracked over time, not a vendor's cross-market average.

The takeaway is not "SEO is dead" or "SEO is everything." It is that classic ranking buys you very different amounts of AI visibility depending on the engine, and the only way to know your position is to measure it where your customers ask. That per-engine, over-time measurement is exactly what **Buffy Intel** is built to provide. A daily snapshot of who gets cited for the questions that matter to your brand.

## Does page speed affect your AI visibility?
Source: https://heybuffy.com/blog/does-page-speed-affect-ai-visibility

Page speed isn't a direct AI-ranking dial, but the chain from "fast, light page" to "cited in AI answers" is real. Crawlers have to **fetch, render, and parse** your pages before anything you wrote can be retrieved, and slow or bloated pages leak at every step.

## The mechanism: fetch → render → parse

- **Fetch (crawl efficiency).** Crawlers work within budgets. Slow responses mean fewer of your pages get crawled, and less often, so new or updated content takes longer to become eligible.
- **Render (the JS trap).** Many AI crawlers don't reliably execute JavaScript. If your key content and [structured data](/glossary/structured-data) only appear after JS runs, they may simply not exist for the crawler. Server-rendered HTML is the safe default.
- **Parse (the byte budget).** Crawlers process a finite amount of a page. Google's crawler, for instance, works within a roughly **2MB** window, if bloated inline CSS/JS pushes your real content and JSON-LD past that, the important facts can be missed even though they're "on the page."

## Why this maps to citations

AI citation happens at the [passage level](/blog/how-query-fan-out-works): a model lifts a clean chunk from content it could fetch and read. A page that's slow to fetch, renders late, or buries its facts below a wall of inline code is harder to extract from, so it loses to a leaner competitor that says the same thing more accessibly. Performance isn't a vanity metric here; it's an extractability prerequisite.

## What to fix

- **Server-render key content and structured data** so they're in the initial HTML, not JS-injected.
- **Keep the important stuff early and light**: get your core answer, headings, and JSON-LD well within the byte budget; don't bury them under heavy inline code.
- **Hit Core Web Vitals**: fast loads help crawlers and users alike.
- **Trim render-blocking bloat**: minimise inline CSS/JS that pushes content down.

> "We have great content" doesn't help if the crawler times out, can't render it, or never reaches the facts before its budget runs out. Speed and clean delivery are what turn good content into *retrievable* content.

This pairs with making sure you're reachable at all ([is your CDN blocking AI crawlers?](/blog/is-your-cdn-blocking-ai-crawlers)) and [structured for extraction](/blog/how-to-get-cited-by-ai). Catching when a slow or JS-heavy template is quietly costing you AI presence is part of what a readiness audit, and ongoing monitoring with **Buffy Intel**: surfaces.

## Does posting on Reddit get you cited by AI? What the citation data shows
Source: https://heybuffy.com/blog/does-reddit-get-you-cited-by-ai

Posting on Reddit rarely gets you cited by ChatGPT, effectively never by Claude, and meaningfully only by Google. In a citation-mining dataset covering March–July 2026, published by SEO researcher Dan Petrovic (DEJAN), ChatGPT retrieved Reddit pages **491,024 times but cited only 3,012** of them, a **99.4% rejection rate** that Petrovic reports was the highest of any domain in the data. Claude cited Reddit **zero times**, and Google cited it heavily. Reddit's AI presence, in other words, tracks its ordinary Google ranking, not an AI preference for the platform.

That reframes a year of "put your brand on Reddit to get cited by AI" advice. This piece lays out the engine-by-engine data, attributed and hedged, then reconciles it with what the [decision framework for investing in Reddit](/blog/is-reddit-worth-it-for-ai-visibility) already says. That piece helps you decide *whether* to invest; this one shows *where the citations actually land* across engines.

## How often do AI engines actually cite Reddit?

Very differently by engine. Petrovic's method was [citation mining](/blog/how-chatgpt-picks-sources): tracking how often each engine *retrieves* a domain as a candidate versus how often it *cites* the domain in the final answer, across OpenAI, Google, and Anthropic over roughly six months. The Reddit numbers he reports:

| Engine | Reddit retrieved | Reddit cited | Selection rate | Reading |
|---|---|---|---|---|
| **ChatGPT (OpenAI)** | 491,024 | 3,012 | **0.61%** (99.39% rejected) | Retrieved constantly, cited almost never |
| **Claude (Anthropic)** | Not supplied as a candidate | **0** across 139,601 grounding sources | ~0% | Reddit never even enters the pool |
| **Google** | Sampled in ~26.6% of searches | 14,127 (of 697,768 sources) | ~14× ChatGPT's rate | Cited heavily |

Source: Dan Petrovic / DEJAN, "No, AI doesn't prefer Reddit. Search does." (dejan.ai), citation-mining data March–July 2026; the Anthropic slice covers May–July 2026. Reported secondhand via Search Engine Journal (July 2026). This is **single-vendor, self-reported** research, so read the exact counts as a directional snapshot of one measurement pipeline, not a fixed constant.

For comparison inside the same OpenAI dataset, Petrovic reports Wikipedia at a **5.64%** selection rate and arXiv at **0.77%** — so Wikipedia is genuinely favoured on selection, while Reddit and arXiv are retrieved far more than they are kept.

## Why does ChatGPT retrieve Reddit so much but cite it so rarely?

Because retrieval and citation are two separate steps, and the gap between them is enormous for Reddit. An engine pulls many candidate pages into context to *inform* an answer, then footnotes only the few it can read cleanly and that directly answer the question. Being fetched is not being [cited](/glossary/citation); the retrieval-to-citation funnel is documented in detail in [how ChatGPT picks the sources it cites](/blog/how-chatgpt-picks-sources), which recorded Reddit fetched roughly 278 times and cited only 11 in a smaller teardown.

Petrovic's data is the same pattern at scale, and it clears up a common confusion: ChatGPT still cites Reddit **3,012 times in absolute terms**, which is why other datasets describe ChatGPT as "drawing heavily on Reddit and Wikipedia" (see [how many sources each engine cites](/blog/how-many-sources-ai-engines-cite)). Both are true. Reddit's absolute citation count is meaningful, *and* its selection rate is the worst of any domain measured. The high absolute number comes from sheer retrieval volume, not from the engine trusting each Reddit page. Independent corroboration: Ahrefs' analysis of 1.4 million prompts found Reddit cited in about **1.93%** of answers while accounting for a large share of pages ChatGPT pulls in and never names.

## Why does Reddit still show up in AI answers, then?

Because a large share of the Reddit citations people actually see come from **Google's AI surfaces**, and Reddit's presence there is inherited from ordinary Google search ranking. Reddit ranks well in classic Google results, and [AI Overviews and AI Mode reuse much of that ranking](/blog/does-google-rank-get-you-cited-by-ai). Google reported paid data-licensing access to Reddit content, and separately, [Reddit is one of the most-cited domains in Google's AI Overviews](/blog/most-cited-domains-ai-overviews), second only to YouTube. So the visible Reddit-in-AI phenomenon is real, but it is concentrated on the one engine whose AI layer is fed by web ranking.

Petrovic's one-line thesis captures it:

> AI doesn't prefer Reddit. Search does. Reddit's presence in AI answers tracks its organic Google performance, so "post on Reddit to get cited by AI" was always "rank in Google, which happens to feed Google's AI."

## Does this mean Reddit "isn't worth it" for AI visibility?

No, and this is where the data must not be over-read. The [Reddit decision framework](/blog/is-reddit-worth-it-for-ai-visibility) calls Reddit "one of the most-cited sources in AI answers," and that is still accurate on Google's surfaces and in absolute terms. What the new data adds is that the citation is **engine-specific**: valuable where Google's AI is the destination, weak where ChatGPT or Claude is. That sharpens the framework's "current retrieval share" criterion rather than reversing it.

- **If your buyers' answers come from Google AI Mode / AI Overviews**, Reddit remains a live channel, because Google cites it heavily. The play is the ordinary one: earn genuine, [helpful mentions that rank](/blog/how-to-use-reddit-for-ai-search-visibility) in Google search.
- **If your priority is ChatGPT or Claude**, Reddit is a weak lever on this data. Effort is better spent on owned, extractable content and [earned placement in independent sources](/blog/get-into-ai-cited-best-lists) those engines actually keep.
- **Never fake it.** Seeding threads or [buying aged Reddit accounts backfires](/blog/why-buying-aged-reddit-accounts-backfires) at both Reddit's moderation layer and the engine's, on every engine.

## What are the caveats on this data?

Several, and they matter for how confidently you should act:

- **Single-vendor and self-reported.** The counts come from one researcher's measurement pipeline; the specific numbers are a snapshot, not an audited constant. Cite "Petrovic / DEJAN, 2026" with the date when you reuse a figure.
- **Absolute vs rate.** Reddit is *heavily retrieved and non-trivially cited in absolute terms* on ChatGPT; the striking finding is the low *selection rate*, not a zero.
- **Models change.** OpenAI and Anthropic can alter retrieval and grounding at any time; the Anthropic "zero Reddit" finding especially could shift if Claude adds a Reddit source.
- **Inference on Google.** Petrovic's Google selection rate is estimated from sampled presence, not a clean retrieved-vs-cited count like OpenAI's, so treat the Google figure as the softest of the three.

None of these undermine the durable, corroborated claim: **Reddit is retrieved far more than it is cited, and the citations it does earn are concentrated on Google's search-fed AI.**

## What should you actually do about Reddit?

Decide per engine, and measure before you commit:

1. **Check your own Reddit citation share by engine.** Before assuming Reddit is (or isn't) your channel, look at how often each engine actually cites Reddit *for your category's questions*. Reddit that ranks in Google for your topic is worth more than Reddit in general.
2. **Match the channel to the destination engine.** Google-surface priority favours earned, ranking Reddit presence; ChatGPT/Claude priority favours owned extractable pages and independent third-party placement.
3. **Own your facts; earn your mentions.** Publish your specifications, pricing, and definitions as clean, server-rendered text so you are the citable source, and pursue genuine third-party presence for the recommendation, per [how to get cited by AI](/blog/how-to-get-cited-by-ai).
4. **Build the durable lever.** A [corroborated, strong entity](/blog/entity-strength-ai) across the trusted sources your buyers use outlasts any single-platform tactic.

The through-line is measurement: knowing which engines cite which sources for *your* buyers' questions, tracked as a trend rather than a one-off snapshot, is exactly what **Buffy Intel** is built to show — engine by engine, over time.

## Does schema markup increase your AI citations? The controlled-study evidence
Source: https://heybuffy.com/blog/does-schema-markup-improve-ai-citations

**Adding schema markup did not increase AI citations in the best controlled test available.** In a 2026 Ahrefs study, 1,885 pages that added JSON-LD [structured data](/glossary/structured-data) were matched against 4,000 comparable pages that didn't; citations to the schema pages moved **-4.6% on Google AI Overviews** (statistically significant), **+2.4% on AI Mode** and **+2.2% on ChatGPT** (neither significant). Yet across ~6 million URLs, AI-cited pages were about **3× more likely to carry schema**. Both are true, and the gap between them is the whole story.

This is a dated reference, not a new dataset. **Last reviewed: 6 August 2026.** All figures come from Ahrefs' controlled schema experiment, published May 2026, which measured citation change over roughly a 30-day window per page across Google AI Overviews, Google AI Mode and ChatGPT. It is single-vendor and carries the caveats set out below, so read the *direction* as firmer than any one percentage and cite "Ahrefs, 2026 schema study" with the date when you reuse a figure. It confirms and sharpens, rather than contradicts, our earlier read that structured data is machine-legibility hygiene, not a citation lever, in [prioritise your structured data](/blog/prioritize-your-structured-data) and [the three AI-citation levers ranked by evidence](/blog/freshness-structure-authority-levers).

## What did the schema study actually measure?

The causal question, not the usual correlation. Most "schema helps AI" claims rest on the observation that cited pages tend to have markup. Ahrefs instead used a before-and-after design: take pages that *added* JSON-LD in a known window, compare their citation change against matched pages that didn't, and see whether the markup itself moved anything.

| Attribute | Detail |
|---|---|
| Treated pages | **1,885** that added JSON-LD schema |
| Control pages | **4,000** matched pages that did not |
| Schema-add window | **August 2025 – March 2026** |
| Engines measured | Google AI Overviews, Google AI Mode, ChatGPT |
| Observation window | ~**30 days** per page |
| Correlation sample | ~**6 million** URLs |
| Published | **May 2026** (Ahrefs) |

Source: Ahrefs, 2026 schema study. The design matters because it isolates the *effect of adding schema* from everything else that makes a page citable, which a raw "cited pages have more schema" count cannot do.

## Did adding schema move citations on any engine?

No engine showed a meaningful uplift, and one showed a small decline. Measured against the matched controls, the change in citations for pages that added schema was:

| AI engine | Citation change after adding schema | Statistically significant? |
|---|---|---|
| **Google AI Overviews** | **-4.6%** | Yes |
| **Google AI Mode** | +2.4% | No |
| **ChatGPT** | +2.2% | No |

Source: Ahrefs, 2026 schema study; changes are relative to 4,000 matched control pages. The two small positive moves sit inside the noise band, so the honest reading is "no detectable effect." The AI Overviews decline is real in the data but small, and most plausibly reflects other shifts over the window (Google reduced some rich-result surfaces in this period) rather than schema actively hurting you. The safe conclusion is the null one: **adding markup did not buy citations.**

## So why are cited pages more likely to have schema?

Because schema travels with quality, not because it creates citations. This is the reconciliation the whole topic turns on, so state it plainly:

- **The correlation is real.** Across ~6M URLs, AI-cited pages were ~3× likelier to contain JSON-LD. A [2026 correlational read](/blog/freshness-structure-authority-levers) of on-page signals points the same way.
- **The cause points the other way round.** The sites that add schema are disproportionately well-resourced, well-structured, strongly-corroborated sites, exactly the ones that earn [citations](/glossary/citation) for reasons that have nothing to do with the markup.
- **The controlled test breaks the tie.** When you hold quality roughly constant by matching pages and change only the schema, the citations don't follow. That is the difference between "cited pages have schema" and "adding schema makes pages cited."

> Schema is a marker of a well-built page, not a mechanism that earns the citation. Cited pages carry markup for the same reason they carry good content, the underlying quality, so adding markup to a page without that quality changes little.

Confusing the two is the single most common error in reading AI-visibility studies, and it is worth its own method: see [how to tell whether an on-page change actually moved your AI citations](/blog/test-if-a-change-moved-your-ai-citations) and the plain-English definition of [correlation vs causation](/glossary/correlation-vs-causation).

## What are the study's limits?

Real ones, which is why the claim is "not a lever," not "never matters." Read the numbers with these in view:

| Caveat | Why it matters |
|---|---|
| Only already-cited pages | Every treated page had 100+ AI Overview citations in Feb 2025, so the test asks "does schema add citations to pages that already win?", not "can it help a page break in?" |
| Schema types pooled | `Product`, `FAQPage`, `Article` and the rest were grouped, so a type that helps could be masked by types that don't |
| Equal-weighted citations | A citation on a high-value query counts the same as a trivial one |
| ~30-day window | A short observation period given the real [crawl-to-cite lag](/blog/chatgpt-citation-lag) |
| Single vendor, three engines | Ahrefs' measurement, US-weighted, not the whole AI-answer ecosystem |

Source: Ahrefs, 2026 schema study, with limitations noted by Ahrefs and industry commentary. None of these rescue schema as a growth lever; they bound the claim to "adding markup to a decent page is not a reliable citation gain," which is exactly the useful conclusion.

## How does this square with Google, and with our own guidance?

Cleanly, and that is the point of writing it down. Three sources now say the same thing from different angles:

- **Google's official guide** states you *don't* need special files or markup to appear in its AI features, that it's [still SEO](/blog/is-geo-just-seo). This controlled test is the empirical version of that statement for schema specifically.
- **Our levers piece** ranked structure and authority as the signals that move citations and flagged that the schema link was correlational, in [freshness, structure, authority](/blog/freshness-structure-authority-levers). The study confirms schema is not itself the structural lever.
- **Our structured-data playbook** already told you to add the right types and then *measure whether it moved anything*, in [prioritise your structured data](/blog/prioritize-your-structured-data). The study is the large-sample answer to that measurement: mostly, it won't move citations on its own.

There is no contradiction to resolve, only a sharpening: schema is table-stakes machine-legibility that helps engines parse and reuse your facts, and it is worth keeping accurate, but it is not the thing that earns the citation.

## What should you do with structured data now?

Keep it, right-size it, and stop treating it as a growth lever. Concretely:

- **Keep accurate schema that matches your visible content.** It labels your facts for machines, still drives non-AI rich results, and is cheap hygiene, the case in [answer-engine optimization](/glossary/answer-engine-optimization) is unchanged.
- **Don't expect uplift from adding more.** On this evidence, bolting extra markup onto an already-decent page is not a reliable way to gain AI citations; budget accordingly.
- **Spend the freed effort on the real levers.** Non-commodity content, [entity strength](/blog/entity-strength-ai), and third-party corroboration are what move citations; schema just makes the facts on those pages legible.
- **If you do add markup, test it honestly.** Baseline, add, and read a smoothed trend against a control, the method in [testing whether a change moved your citations](/blog/test-if-a-change-moved-your-ai-citations), rather than trusting a single before-and-after.

The published averages tell you schema is not the lever; the number that governs your strategy is whether the changes you *do* make actually move how the engines cite you, measured across engines and over time. That per-change, per-engine citation measurement is exactly what **Buffy Intel** is built to provide. Questions: support@flash.tech.

## Entity strength: why AI already 'knows' some brands
Source: https://heybuffy.com/blog/entity-strength-ai

Ask why one brand is the AI's default recommendation and a near-identical competitor is invisible, and the answer is usually **entity strength**: not a better blog post.

## What "entity" means here

An entity is a thing the web (and AI) recognises and has facts about: a brand, a person, a product. Your **entity strength** is how strongly and credibly engines associate you with your topic, and analyses suggest it often correlates with AI citations *more than* backlink volume or classic technical SEO.

It's built from signals like:

- **Brand search volume**: do people search for you by name?
- **Knowledge-graph presence**: Wikipedia, Wikidata, Google's Knowledge Graph.
- **Topic co-occurrence**: how often your brand appears *alongside* your category across the open web.
- **Consistency**: the same facts about you, repeated everywhere.

A recognised entity inherits authority: when an AI answers a category question, it reaches for the brands it already "knows," even with identical wording on the page.

## Why it's the slow lever, and why that's good

Unlike [retrieval](/glossary/retrieval-augmented-generation) (which can win citations within days) or freshness (a refresh cadence), entity strength **compounds over months**. You can't fabricate it overnight, and that's exactly why it's defensible. Once you're an established entity for "AI visibility tools" or "fragrance-free skincare," competitors can't quickly out-publish you for it.

## How to build it

- **Have an entity home**: one canonical, authoritative page that defines who you are (a strong About page), with `Organization` [structured data](/glossary/structured-data).
- **Earn knowledge-graph presence** where warranted. Wikidata, and Wikipedia if you genuinely meet notability.
- **Be corroborated**: consistent, accurate descriptions of your brand across retailers, reviews, press, and the third-party sources engines trust ([why earned coverage matters](/blog/why-ai-loves-listicles)).
- **Co-occur with your category**: publish and get mentioned in your topic space so the association strengthens.
- **Keep your facts consistent** everywhere they appear, so the web tells one coherent story.

> Retrieval and freshness get you cited this quarter. Entity strength is why you're the default answer next year. Work both, but start the slow one today.

Tracking whether your entity is strengthening. Are you increasingly the named, default recommendation across engines?. Is the long-arc signal **Buffy Intel** watches alongside the faster ones.

## How to estimate what AI Overviews cost you in clicks
Source: https://heybuffy.com/blog/estimate-ai-overview-click-loss

The public AI Overview click-loss figures, an isolated drop of roughly [34.5% to 58% for the top result](/blog/how-much-do-ai-overviews-reduce-clicks), are network-wide averages, and your site can sit far from them. Estimating your own number takes three inputs you can mostly assemble for free: your click and CTR trend from Google Search Console, a signal for which of your queries trigger an [AI Overview](/glossary/ai-overviews), and the public benchmark to sanity-check the result. Below is an honest method, in five steps, that names what it can and cannot prove.

## Step 1: Segment your informational queries in Search Console

Start where the click loss concentrates. Ahrefs found about 99.2% of AI-Overview keywords are informational, so open the Search Console Search performance report and isolate your informational, question-style queries (how, what, why, best way to, and topic-explainer terms) from your branded and transactional ones. Export clicks, impressions, and average CTR for that informational segment over at least the last 12 months. This segment is where an AI Overview is most likely to sit above you and skim the click.

## Step 2: Identify which of those queries trigger an AI Overview

Search Console will not tell you this directly, so bring an outside signal. Three practical options, roughly in order of rigour:

| Method | How it works | Limitation |
|---|---|---|
| Rank tracker with an AI-Overview flag | Many trackers mark which tracked keywords show an AI Overview | Costs money; covers only tracked terms |
| Generative AI performance report | Confirms which of your pages appear in AI features | Impressions-only; no query, no CTR |
| Manual SERP checks | Spot-check your top informational queries by hand | Slow; a point-in-time snapshot |

Combine what you have: a tracker flag tells you an AI Overview appears, and the [Generative AI performance report](/blog/google-search-console-ai-performance-report) confirms whether *your* page is being surfaced in AI features at all. Neither gives clicks, which is why Step 3 leans on your own CTR trend.

## Step 3: Compare CTR where AI Overviews appear against where they do not

With the queries split, compare average CTR at a similar position for two groups: informational queries that trigger an AI Overview versus informational queries that do not. This mirrors the method Ahrefs used, holding intent and position roughly constant so the AI Overview is the main difference. If you lack a clean AI-Overview flag, use time instead: track CTR-at-position for your informational segment across the period AI Overviews expanded on your terms, and watch for a sustained decline that is not explained by a ranking change.

> Search Console cannot hand you an AI Overview click-loss number, because its AI report has no clicks and its click report has no AI-Overview flag. The estimate lives in the gap between them, so label it an estimate and show your working.

## Step 4: Apply the public benchmark as a sanity check

Convert the CTR difference into a rough click-loss estimate, then check it against the public range. If your position-one informational CTR is materially lower where AI Overviews appear, an isolated drop in the region of **one-third to one-half** is consistent with Ahrefs' 34.5%–58% findings. A far larger apparent drop usually means something else moved too (a ranking slip, a seasonal dip, a redesign), so investigate before attributing it all to AI Overviews. An estimate that lands inside the benchmark band is the credible, defensible case.

## Step 5: Reframe the goal from clicks kept to citations earned

Finish by turning the estimate into a plan, because you cannot switch AI Overviews off. Seer Interactive found organic CTR was about **0.70% when a brand was cited inside the AI Overview versus 0.52% when it was not**, so the winnable gap is being named as the source, not avoiding the overview. Use your estimate to prioritise the informational pages losing the most clicks, then work to be [cited rather than merely shown](/blog/cited-vs-recommended-in-ai-search) on exactly those queries. The click you can still earn increasingly comes from being inside the answer.

Estimating the loss once is a useful audit; watching your click loss, your AI-Overview citations, and your recovered [zero-click](/glossary/zero-click-search) visibility move together across engines is the ongoing job that **Buffy Intel** is built for. Questions: support@flash.tech.

## Why your products go invisible when demand spikes overnight
Source: https://heybuffy.com/blog/event-driven-product-visibility

When a real-world event creates new shopping queries overnight, an AI agent matches those queries against your catalog **exactly as it reads right now**: and a product can go invisible to a search it should obviously win. The product hasn't changed. The language shoppers use to find it has, and your catalog still says what it said yesterday.

This is the timing layer of [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents): that piece covers *what* context to add, this one covers *when* it has to be there.

## Why does a product vanish from AI search after an event?

Because demand shifts faster than catalogs do. Imagine a team wins a championship tonight. By morning, shoppers are asking AI assistants for "the sneaker their star wore in the finals," "championship-edition kicks," "that limited-edition colourway from the title run." The exact shoe exists in a brand's catalog, but it's tagged with a model name and a colour, not with the event that just made it famous.

An AI agent fielding those queries does what it always does: it matches the request against the catalog as written. None of the new phrases appear there, so the agent returns no match and recommends whatever *is* tagged for the moment. The shoe is invisible to the search it should win, because the catalog was written before the query existed.

> The agent matches today's queries against today's catalog. When an event invents new queries overnight, an un-updated catalog goes silent on exactly the demand the event created.

Large, dominant brands survive this. They're cited anyway because their [entity strength](/blog/why-ai-cites-one-brand) is too big to miss. For everyone else, an untagged product is simply absent.

## What kinds of events trigger new queries?

The pattern isn't limited to sports. Any moment that reframes how people describe a product creates a fresh batch of [fan-out queries](/glossary/query-fan-out):

| Trigger | Example new query | What the catalog usually lacks |
|---|---|---|
| Cultural / sports moment | "championship-edition jacket," "the bag from that awards show" | Event, "worn-by," moment tags |
| Seasonal / weather shift | "rain boots for sudden flooding," "first cold-snap layers" | Use-case and seasonal-occasion attributes |
| News / regulation | "BPA-free swap for the recalled bottle," "compliant replacement" | Compliance and substitute-for context |
| Viral content | "the gadget from that video," "dupe for the trending serum" | Trend, comparison, and "alternative-to" framing |
| Release tie-in | "outfit like the new show's lead," "console-launch accessories" | Cross-reference to the thing driving demand |

Each row is the same failure: the product is eligible, but the words that would surface it aren't in the text the agent reads.

## How short is the window?

Short enough that slow updates miss it entirely. Event-driven demand tends to peak and fade inside roughly **48 to 72 hours**: the parade window, not the season. Because AI engines read your catalog at answer time and weight [freshness](/blog/content-freshness-citation-cliff) heavily, an attribute added on day four arrives after the spike it was meant to capture.

That collides with how catalog data actually refreshes. On commerce platforms, price and inventory move in near real time, but descriptive fields. Tags, categories, metafields, highlights. Change only when a human (or a workflow) writes them. So demand moves at the speed of the event, while context moves at the speed of whoever updates the catalog. If nobody's writing, the product stays silent.

## How do you tag for a moment before it passes?

Treat it as two problems. The predictable and the unpredictable.

1. **Pre-tag the predictable.** Seasons, recurring sales moments, scheduled releases, and annual events are all on the calendar. Add the occasion, use-case, and event attributes *before* demand arrives, so the catalog is already speaking the query's language when it spikes.
2. **Build a fast path for the unpredictable.** Decide in advance who can add an attribute, where, and how fast. On Shopify, for instance, that means category metafields and product tags an operator can edit in minutes. `Event`, `worn-during`, `championship-year`, `alternative-to`. Rather than a quarterly feed rebuild.
3. **Expose the new attributes as crawlable text,** not just internal fields. The agent has to *read* the tag, so it must reach the product page as server-rendered [structured data](/glossary/structured-data) and visible copy, the same reachability bar every AI crawler applies.
4. **Write the attribute in the shopper's words,** not your taxonomy's. "Championship-edition" beats an internal SKU suffix; "first-cold-snap layer" beats "AW base layer." Match the query, don't translate it.
5. **Retire stale event tags** once the moment passes, so last season's framing doesn't muddy this season's matching.

This is where the platforms are heading anyway. Shopify reported that its Agentic Storefronts make millions of stores discoverable inside AI assistants by pulling structured attributes out of titles, descriptions, and metafields, which means the catalog field *is* the storefront an agent sees. The brands that win event-driven queries are the ones whose catalogs can speak a new language within hours.

## What to do next

Pick the three events most likely to move your category in the next quarter and write the attributes for them today, before demand shows up. Then decide your fast path: who can tag a product mid-spike, and how quickly the change reaches a crawlable page. The brands that capture overnight demand aren't faster shippers. They're faster *writers*. Watching which event queries you appear in, and which competitors quietly own, is exactly the visibility loop **Buffy Intel** is built to report.

## What makes AI recommend your product? The six factors
Source: https://heybuffy.com/blog/factors-ai-recommends-products

AI engines don't rank products the way a search engine ranks links. When an assistant decides which product to recommend, it behaves less like a ranking algorithm and more like a careful editor choosing a source to quote: it narrows to products it can reach and read, then weighs which one best, most credibly, and most freshly answers the question. No engine publishes that logic, but six factors consistently shape the outcome.

This framework is our synthesis of how AI recommendation behaves across engines, not a published ranking formula. Use it as a checklist, not a guarantee, and read it alongside [how AI engines choose brands](/blog/how-ai-engines-choose-brands).

## The six factors at a glance

| Factor | The question the engine is really asking | How you win it |
|---|---|---|
| 1. Reachability | "Can I fetch and read this page at all?" | Crawlable, server-rendered HTML; AI bots not blocked |
| 2. Coverage | "Does this text answer the actual question and its branches?" | Conversational attributes, use-cases, fit, FAQs |
| 3. Specificity | "Are there concrete, quotable facts here?" | Named, numeric, dated attributes, not adjectives |
| 4. Corroboration | "Do other credible sources agree?" | Reviews, third-party mentions, earned best-lists |
| 5. Freshness | "Is this current, priced, and in stock?" | Live price/availability; substantively updated pages |
| 6. Clarity | "Can I lift a clean, unambiguous passage?" | Extractable chunks, no contradictions, structured data |

The order is roughly a funnel: each factor only matters if the ones above it pass. The rest of this piece takes them one at a time.

## Factor 1: Reachability: can the engine read you?

Reachability is the gate. An AI engine can only recommend a product whose page it can fetch and parse. If your [CDN is blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers), your specs live only in JavaScript the bot won't execute, or critical text is locked in images, the product is invisible before any other factor applies.

This is the most common silent failure because the page looks fine to a human in a browser. Test it the way an [AI crawler](/glossary/ai-crawler) sees it: fetch the raw HTML and confirm the price, attributes, and description are present in the server-rendered source.

## Factor 2: Coverage: does your text answer the real question?

Reachable isn't enough; the text has to *cover the question*. AI shopping queries are long and specific, "which of these works for a heavy runner with flat feet who mostly uses a treadmill?", and the engine fans that into [sub-queries](/glossary/query-fan-out) about fit, use-case, durability, and trade-offs. A catalog carrying only a title, price, and six attributes can't answer those branches, so the engine sources the answer from whoever can.

Coverage means exposing conversational context: what it pairs with, who it's for, what occasion it suits, how to care for it. That enrichment work is the subject of [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents).

## Factor 3: Specificity: are your facts quotable?

Engines lift specifics and skip vagueness. "Streamlines your routine" gets dropped; "weighs 240g, fits wrists 14-19cm, 18-hour battery" gets quoted. Verifiable, named, numeric, dated claims are what a model can safely repeat in an answer, and a recommendation is just a quoted claim with a buy intent attached.

The discipline is to convert every adjective into an attribute. If a fact can't be stated specifically and truthfully, cut it rather than inflate it. Over-claiming gets a brand described as unreliable, the opposite of the goal.

## Factor 4: Corroboration: do others agree?

AI engines favour products that the wider web corroborates. A claim that appears only on your own page is weaker than the same claim echoed in reviews, third-party write-ups, and independent [best-of lists](/glossary/best-of-list). This is why [independent listicles get cited far more](/blog/why-ai-loves-listicles) than brand-owned "best tools" pages for commercial queries, and why earned placement matters more than self-promotion.

Corroboration is the slow, durable lever: consistent facts about your product across the web, real reviews exposed as text, and genuine third-party mentions. You build it; you can't fake it without risking the trust you're trying to earn.

## Factor 5: Freshness: is this current?

Live retrieval favours recent, accurate data. For products specifically, freshness has two faces: an honest "updated" date on the page, and *live* price and availability the engine can trust. A recommendation that sends a shopper to an out-of-stock or wrongly priced product is a bad answer, so engines lean toward sources that look current.

Freshness is also where [event-driven demand](/blog/event-driven-product-visibility) lives. When a moment creates new queries overnight, the catalog that's been updated to speak their language wins, and the stale one goes silent. Citations also decay after roughly a quarter, so competitive pages need a real refresh cadence, not a date bump.

## Factor 6: Clarity: can the engine lift a clean passage?

Finally, the engine has to be able to *extract* you. Recommendation happens at the passage level: the model lifts a clean, self-contained chunk. Walls of prose, contradictory specs (one price here, another there), and ambiguous pronouns all lower your odds. Clear structure. Real headings, lists, tables, [structured data](/glossary/structured-data) labelling what each thing is. Makes you the easy, safe source to quote.

Clarity is also where contradictions cost you: if your spec table and your description disagree, the engine may distrust both. Say each fact once, clearly, and consistently.

## How the six factors work together

> Reachability gets you considered; coverage and specificity get you matched; corroboration and freshness get you trusted; clarity gets you quoted. A product needs all six. A single missing factor can keep it out of the answer.

No single factor is a silver bullet, and the weighting shifts by engine and query. The practical move is to audit a product against all six, fix the weakest link first (usually reachability or coverage), then measure which answers you actually appear in. Tracking that. Across engines, over time, by product. Is exactly what **Buffy Intel** is built to do.

## How to find AI Mode conversation turns in your Search Console data
Source: https://heybuffy.com/blog/find-ai-mode-queries-in-search-console

To find AI Mode conversation turns in Google Search Console, open the **main Performance report** and filter the query table for short, conversational, dependent fragments — the follow-up replies that [AI Mode counts as new queries](/blog/ai-mode-conversations-in-search-console). There's no AI Mode label, so you pattern-match by shape, then read the fragments as conversion-journey signals rather than exact metrics.

This is the practical companion to the finding that [AI Mode conversation turns land in your main Search Console report](/blog/ai-mode-conversations-in-search-console). It's a distinct task from the broader [regex method for mining Search Console for AI-search questions](/blog/mine-search-console-for-ai-questions): that one treats your *classic* query data as a proxy for AI intent; this one isolates the AI Mode **follow-up turns** specifically.

## Before you start: what this method can and can't do

State the scope up front so you don't over-read the output. As of mid-2026, Search Console has **no filter, dimension, or label** that isolates AI Mode queries. Every follow-up turn a user asks in AI Mode is logged as a separate query in the main report, but nothing marks it as AI Mode. So this method **infers** AI Mode turns from their conversational shape. It's directional evidence — good for spotting journeys and content gaps, not for reporting a clean "AI Mode traffic" number.

## Step 1: Open the main Performance report, not the Generative AI report

The query text lives in the general report. Open **Google Search Console → Performance → Search results**. Do *not* use the Generative AI performance report for this — it isolates AI-feature impressions but carries no query data at all. If you want AI-feature impression totals, that report is the place; for the conversational **question text**, you need the main Performance report.

## Step 2: Filter the query table for conversational fragments

Add a query filter set to **Custom (regex)** and apply the patterns below one at a time. Each isolates a different kind of follow-up turn. Treat them as starting points and adapt to your vocabulary:

| Turn type | What it surfaces | Regex (Query → Custom regex) |
|---|---|---|
| Confirmations | "yes", "yeah", "sure", "ok" as standalone replies | `^(yes|yeah|yep|sure|ok|okay|no)\b` |
| Continuations | "go on", "tell me more", "and then" | `\b(go on\|tell me more\|and then\|what about\|explain more\|keep going)\b` |
| Short fragments | 1–3-word dependent replies | `^(\w+\s?){1,3}$` |
| Context-carrying refinements | replies starting with a pronoun/article | `^(the\|that\|this\|it\|those\|these\|they)\b` |

The tell across all four is **dependency**: a query that is meaningless without a preceding turn is almost certainly a follow-up turn. Export each filter's matches so you can group them in the next step.

> The signature of an AI Mode turn is dependency — a query that can't stand on its own, like "yes, pricing" or "the cheaper one." A person types a full question into a search box; they reply in fragments inside a conversation.

## Step 3: Group the fragments by journey stage

Sort the exported fragments into conversation-journey stages, because the *mix* tells you where AI Mode conversations about your brand are heading:

- **Confirm / continue** ("yes", "go on") — early-to-mid funnel; the user is still exploring.
- **Refine** ("for a small team", "the cheaper one") — mid funnel; they're narrowing.
- **Compare** ("vs the other one", "any alternative") — mid-to-late; a decision is forming.
- **Price / commit** ("yes, pricing", "how much") — late funnel; buying intent.

A cluster of late-funnel fragments on a page means AI Mode conversations are reaching a decision *while citing you* — the pages worth protecting and refreshing first.

## Step 4: Corroborate before you act

Because you can't cleanly segment AI Mode, treat the fragments as a lead, not a verdict. For each high-value pattern:

1. **Check the landing pages** the fragments map to, and confirm each answers the predictable next turn (pricing, integrations, comparisons) as a self-contained, answer-first chunk.
2. **Pose the likely full questions in the engines** — ask AI Mode, ChatGPT, and Perplexity the underlying question and its follow-ups, and note whether you're named and cited at each turn.
3. **Fold it into your baseline** so a single noisy report never drives a decision, the way the [five-metric reporting stack](/blog/ai-visibility-reporting-stack) prescribes.

## What are the limits of this method?

Read the output directionally, for three reasons. First, it's a **keyhole view**: only turns that produced an impression for your site appear, and Google samples and thresholds query data, so counts understate reality. Second, **regex filters inflate metrics** — Search Console sums matching rows across pages, so trust the patterns and proportions, not exact totals. Third, the patterns catch **false positives**: some genuinely short classic queries ("yes bank", "ok google") match too, so eyeball the list before trusting it. The honest frame: this surfaces *candidate* AI Mode turns to investigate, and the investigation happens in the engines, not in Search Console.

Taking these candidate turns, posing the real questions across AI Mode, ChatGPT, Perplexity, and Claude, and tracking whether your brand is named and your pages [cited versus merely surfaced](/blog/cited-vs-recommended-in-ai-search) over time — turn by turn — is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## How to find your AI citation hero pages (and reinforce them)
Source: https://heybuffy.com/blog/find-your-ai-citation-hero-pages

**To find your AI citation hero pages, capture which of your own URLs get cited across engines for your buyers' recurring questions, rank your pages by how often they're cited, then pour maintenance into the small set that wins — and treat questions with no owned winner as earned-media targets.** This turns the [hero-page pattern](/blog/your-ai-citation-hero-pages) into a workflow you can carry out.

The reason to bother: AI citations pile onto a few of your pages rather than spreading evenly, because engines cite a tight per-query shortlist and your buyers ask a bounded, repeating set of questions. Spreading content effort uniformly across your site therefore spends most of it where citations never happen. The steps below find the pages that already work, so you can defend and compound them.

## Step 1: List your buyers' recurring questions

Write down 20–40 real questions your buyers ask AI engines about your category, spanning the intent branches an answer fans out into: definitions, comparisons, how-tos, buying decisions, and troubleshooting.

- Pull them from sales calls, support tickets, your site search, and the follow-up questions engines surface.
- Cover the [whole question tree](/blog/how-to-get-cited-by-ai), not just your head term — hero pages are defined by the recurring questions they win, so a thin query set hides them.

## Step 2: Capture which of your URLs get cited, per engine

Put each question through the engines your buyers actually use — ChatGPT, Perplexity, Gemini, Google AI Overviews, Google AI Mode — and record every source each answer cites, then keep only the citations that point to your own domain.

- Log the exact URL, the engine, and the question it was cited for.
- Keep engines separate. Citation behaviour differs sharply by engine, so a blended list hides which page wins where — the same per-engine discipline behind [auditing your site for AI visibility](/blog/how-to-audit-your-site-for-ai-visibility).
- This is the raw material for [which of your pages are cited](/glossary/cited-pages); most of your URLs will appear zero times, and that is the expected, lopsided shape.

## Step 3: Rank your pages by citation share

Tally how often each of your URLs was cited across the whole query set, and sort. The top of that list — usually a small handful — is your set of hero pages.

- Note *which questions* each hero page wins, not just the count. A page that wins one high-value buying question can matter more than one that wins several trivial ones.
- Watch for the drop-off. If a few pages carry most of the citations and a long tail carries none, that gap is your allocation map: it tells you where maintenance pays off and where it doesn't.
- Compare the winners against your assumptions. The pages that get cited are frequently not your homepage or your newest post — let the [measured citations](/blog/how-to-measure-ai-visibility) decide, not intuition.

## Step 4: Reinforce the winners

Concentrate maintenance on the hero pages, because they are both your biggest asset and your most exposed one.

- **Refresh them on a cadence.** Citations decay after roughly a quarter, so a hero page left untouched can slip off the [freshness cliff](/blog/content-freshness-citation-cliff) without any other change.
- **Raise evidence density inside them.** Add a specific attributed statistic per claim, a credible quote, and inline sources — the [edits that lift citations](/blog/what-content-changes-lift-ai-citations) — and make sure the answer-first passage is still clean and [structured for extraction](/blog/prioritize-your-structured-data).
- **Build internal links into them** from related pages, so the hero page is easy to reach and clearly the canonical answer to its question.

## Step 5: Flag the gaps for earned coverage

List the recurring, high-value questions where *no* page of yours is cited — engines only reach for third parties.

- These are not signals to publish more owned pages; they are signals that engines won't cite your site for that question. Pursue genuine [earned placement](/blog/get-into-ai-cited-best-lists) in the independent lists and reviews they do cite.
- Repeat the whole capture quarterly and after major engine changes. Hero pages rise and fall, so a list captured once goes stale — re-sample the same questions so you are comparing like with like.

> Don't polish evenly. Find the few pages engines already cite, make those undeniable and never let them go stale, and send the questions you can't win owned to earned coverage instead. Uniform effort on a lopsided distribution is mostly wasted effort.

Doing this once is useful; doing it continuously is where it compounds, because the hero-page set moves as engines and competitors change. That is where **Buffy Intel** fits: it snapshots which of your pages get cited across engines over time, so your hero pages surface, you catch one slipping before your traffic does, and you can see which questions still need earned coverage. Questions: support@flash.tech.

## How to diagnose and fix pages Google crawls but won't index
Source: https://heybuffy.com/blog/fix-crawled-not-indexed

Pages stuck in Google's **"Crawled – currently not indexed"** status are pages Google downloaded and chose not to keep. They cannot appear in Google Search, and because AI Overviews and AI Mode draw only from the index, they cannot be cited there either. This is a five-step diagnostic to find the cause and fix it, working from the quick technical checks to the harder quality question.

It is the practical companion to [crawled but not indexed: why Google's indexing bar is now your AI-visibility bar](/blog/crawled-not-indexed-ai-visibility). That piece is the why; this is the procedure.

> Rule out the technical causes first because they are fast to check. But be honest: for most stuck pages, the real answer is that the content is a commodity, and no technical fix will change that.

## Step 1: Confirm which status you actually have

Open Search Console → Indexing → Pages and check the exact label. "Crawled – currently not indexed" and "Discovered – currently not indexed" are different problems:

- **Discovered – currently not indexed:** Google knows the URL but hasn't crawled it yet. This points to crawl-budget, internal-linking, or scheduling issues, not a quality verdict.
- **Crawled – currently not indexed:** Google fetched the page and declined to index it. This is either a technical fault hiding your content or a quality judgment.

The rest of this guide is about the crawled case. Getting the label right stops you chasing the wrong fix.

## Step 2: Rule out the technical causes that hide your content

These are rarer than quality problems but faster to check, so do them first. Use URL inspection in Search Console: click the magnifying glass next to a stuck URL, then **Test Live URL**, and look at the rendered HTML and screenshot.

- **Does Google see real content?** If the live test shows only a heading and a few boilerplate words, something is stopping Google from rendering the page. If it shows the full content, the cause is almost certainly quality, not technical (skip to Step 4).
- **Is robots.txt blocking your assets?** A rule meant to block tracking parameters, such as `Disallow: /*?*`, can also block parameterised CSS and JavaScript files a theme depends on. Google then sees an unstyled, contentless shell. Check that your `robots.txt` isn't blocking resources the page needs to render.
- **Is the content locked in JavaScript?** Confirm your facts are in server-rendered HTML, not injected client-side. See [do AI assistants render JavaScript?](/blog/do-ai-assistants-render-javascript) — the same rendering gaps that hurt AI engines also cost you in Google's index.
- **Are you accidentally blocked?** Rule out a `noindex` tag, a canonical pointing elsewhere, or a [CDN blocking crawlers](/blog/is-your-cdn-blocking-ai-crawlers).

If Google can see a full page and nothing is blocking it, stop looking for a technical cause.

## Step 3: Recognise the pages that belong in this bucket

Not every crawled-not-indexed URL is a problem. Some pages *should* be there, and trying to force them in wastes effort:

- Non-canonical duplicates (Google is correctly consolidating to the canonical).
- Pagination pages (`/page/2/` and beyond).
- Feed URLs (`/feed/`) and archive variants.
- URLs with tracking or filter parameters.

Filter these out before you count your problem. If the stuck pages are all parameter variants and feeds, you may have no issue at all. Focus only on canonical, content-bearing pages you genuinely want indexed.

## Step 4: Judge honestly whether the content is a commodity

When the page is technically fine and canonical, the cause is almost always quality. The pattern reported from Google's mid-2026 guidance is [commodity content](/glossary/commodity-content): pages that restate what many others already cover without adding anything more useful. Google described wanting to index content that offers two things it can't get elsewhere: **first-hand experience** and **knowledge no one else has**.

Audit each stuck page against that bar, plainly:

| Ask | If the answer is "no" |
|---|---|
| Does it contain first-hand experience, testing, or original data? | It reads as generic and easily replaced |
| Does it say something the top existing pages don't? | It is a rehash competing with better-established pages |
| Would a reader who saw the other results still find this useful? | It adds no reason to be indexed |

This is the same standard AI engines apply when they decide what to [cite](/glossary/citation). A page too generic for Google's index is usually too generic for an AI answer.

## Step 5: Fix the cause, then validate

Match the fix to the cause you found:

1. **Technical fault:** remove the block (fix robots.txt, the render, the canonical), then use **Validate Fix** so Google re-crawls. Recovery is gradual, over weeks.
2. **Commodity content:** consolidate several thin pages into one strong, comprehensive page; add first-hand experience, original data, and specifics; or retire pages that duplicate stronger ones. A substantive rewrite beats a [date bump past the freshness cliff](/blog/content-freshness-citation-cliff).
3. **Site-wide pattern:** if a large share of your pages are stuck, treat it as a content-quality problem across the site, not a page-by-page cleanup, and prioritise your highest-value URLs first.

A fair warning from the same guidance: sites with many pages stuck in this bucket often find recovery difficult, because the cause is systemic. There is no shortcut around producing content worth indexing.

The whole loop in one line: confirm the status, rule out the fast technical causes, ignore the pages that belong there, and spend your effort making the rest worth indexing, because the pages Google will index are increasingly the pages AI engines will cite. Watching which of your pages are indexed, reachable, and actually cited across every AI surface, over time, is exactly what **Buffy Intel** is built to do.

## What to do when AI gets your brand wrong
Source: https://heybuffy.com/blog/fix-wrong-ai-description

When an AI states something wrong about your brand, you don't fix it by arguing in the chat. You fix it by changing what the engine pulls from: your own pages and the broader web it trusts. Sooner or later it will get something wrong. Last year's pricing, a product you discontinued, a feature that's actually a competitor's, or a flatly negative framing, and because the answer reads confidently, the buyer believes it. Here's the playbook for correcting it across the engines.

## 1. Diagnose where the error lives

The fix depends on the source, so check across engines first ([how to measure](/blog/how-to-measure-ai-visibility)):

- **Wrong on every engine** → it's likely baked into **training data** or your **[entity](/glossary/entity-authority)**: the web's general "knowledge" of you is outdated. Slow to fix, but fixable.
- **Wrong on one engine, right on others** → it's a **retrieval / source** problem on that engine. It's reading a bad or stale source. Faster to fix.

## 2. Fix your own source of truth

Make the *correct* facts reachable and unambiguous on pages you control. Accurate pricing, current product lineup, clear positioning. In clean, structured HTML so engines can [ground](/glossary/grounding) answers in them. If the right answer isn't easy to retrieve from you, the engine fills the gap by guessing or by trusting someone else.

## 3. Correct the corroborating web

Engines lean heavily on third-party sources. If retailers, review sites, directories, or your Wikipedia/Wikidata entry carry stale facts, the model will trust the consensus over your lone correction. Update the places that describe you, so the web tells one consistent, current story.

## 4. Refresh, and re-publish

Stale pages lose out to fresh ones in live retrieval (the [citation cliff](/blog/content-freshness-citation-cliff)). A meaningful update. Corrected facts, a new "last updated". Signals currency and helps the corrected version win.

## 5. For training-baked errors, play the long game

You can't edit a model's weights. What you *can* do is make the correct information so consistent and well-corroborated across the web that the next training cycle learns the right version, while live retrieval carries the correction in the meantime.

## 6. Watch it propagate

A correction isn't done when you publish it. It's done when the engines repeat it. Track the specific wrong claim across ChatGPT, Gemini, Claude, and Google's AI surfaces until it flips.

> Most "AI is wrong about us" problems are really "the correct answer isn't reachable or corroborated enough for the engine to prefer it." Fix that, and the answer fixes itself.

That diagnose-fix-verify loop. Across every engine, tracked over time. Is exactly what **Buffy Intel** is built to run.

## Freshness, structure, authority: the three AI-citation levers, ranked by evidence
Source: https://heybuffy.com/blog/freshness-structure-authority-levers

The 2026 studies on what gets content cited by AI largely agree on the *ingredients*. Freshness, structure, and authority, but teams often rank them wrong, over-investing in one and ignoring the cheapest win. This page scores the three levers against the year's best public datasets, every figure attributed, so you can spend effort where the evidence points.

It complements our deeper pieces on each: the [3-month citation cliff](/blog/content-freshness-citation-cliff) on freshness, [entity strength](/blog/entity-strength-ai) on authority, and [how to get cited by AI](/blog/how-to-get-cited-by-ai) on structure. Here they're side by side, ranked.

**Sources, dated.** The evidence below draws on a 2026 synthesis (digitalapplied) built around **Cyrus Shepard's Zyppy study** (7 May 2026-54 experiments, patents, and case studies, scoring 23 factors 0-10), plus **Ahrefs'** 75,000-brand correlation study and ~17 million cited-URL freshness analysis, **Seer Interactive** (5.47M queries / 53 brands), and **BuzzStream** (4M citations / 3,600 prompts / 10 industries). Several are single-vendor and correlational. Treat them as directional, not causal.

## Lever 1: Structure: the fastest win you fully control

Structure scores highest among on-page factors you can change today. In the Zyppy 0-10 evidence scoring (May 2026):

| Structural factor | Zyppy evidence score | Source |
|---|---|---|
| Answer near the top of the page | **8.8 / 10** | Zyppy, 2026 |
| AI-ready structure (headings, lists, tables) | **8.6 / 10** | Zyppy, 2026 |
| Self-contained passages | **8.0 / 10** | Zyppy, 2026 |

The reason is mechanical: engines retrieve and cite at the **passage level**, so a clean, answer-first chunk with clear boundaries is easier to lift than the same fact buried in prose. One further claim, that pages combining text, images, and structured elements see "156% higher selection rates than text-only pages" (attributed to Wellows). Is **unverified single-vendor data**, so we flag it rather than lean on it. The durable point stands without it: [structured, accessible markup](/blog/accessibility-and-ai-parseability) is the same discipline as AI-parseability. This is the lever to pull first, because you own every input.

## Lever 2: Authority: the most powerful lever, built slowly

Authority shows the strongest correlations with AI visibility, but it's earned over months, not edited in an afternoon. Ahrefs' 2026 study of 75,000 brands measured how different signals correlate (Spearman) with appearing in Google AI Overviews:

| Signal | Correlation | Strength vs backlinks |
|---|---|---|
| Branded web mentions | **0.664** | ~3.0× stronger |
| Branded anchor texts | **0.527** | ~2.4× stronger |
| Branded search volume | **0.392** | ~1.8× stronger |
| Domain Rating | **0.326** | ~1.5× stronger |
| Number of backlinks | **0.218** | baseline |

Source: Ahrefs, 2026 (Spearman correlations. Association, not proven causation). The pattern is consistent: **being mentioned by name across the web outweighs the raw link count.** Ahrefs also reported that brands in the top quartile by mentions saw about **169 AI Overview mentions versus 14** for the next tier. This is the data behind [why AI cites one brand over another](/blog/why-ai-cites-one-brand) and the [entity-strength](/glossary/entity-authority) thesis: corroborated presence compounds. It's slower than fixing structure, but it raises the ceiling structure alone can't.

> Structure is the lever you pull this week; authority is the one you build all year. Brand mentions correlate with AI visibility about three times more strongly than backlinks, but you can't ship them overnight.

## Lever 3: Freshness: real, moderate, and easy to over-rate

Freshness is genuinely a factor, but a moderate one, and the most over-hyped. Across roughly **17 million cited URLs** (Ahrefs, 2026):

| Freshness metric | Figure | Source |
|---|---|---|
| Avg age of AI-cited content | **~1,064 days** | Ahrefs, 2026 |
| Avg age of organic top-10 results | **~1,432 days** | Ahrefs, 2026 |
| AI-cited content is fresher by | **~25.7%** | Ahrefs, 2026 |
| ChatGPT (most recency-biased) | **~958 days** | Ahrefs, 2026 |
| Zyppy freshness evidence score | **7.0 / 10** | Zyppy, 2026 |

So AI-cited pages skew fresher, and ChatGPT most of all, but "fresher" here still means *years* old on average, not weeks. A widely-repeated "4.3× fresher" claim is **unsourced and should not be repeated** (digitalapplied flagged it directly). The honest read: freshness matters most for time-sensitive and competitive pages, which is exactly the [citation-cliff refresh cadence](/blog/content-freshness-citation-cliff) we recommend, not a reason to churn evergreen content.

## How do the three levers rank together?

Two cross-cutting findings reframe all three. First, **only about 38% of AI Overview citations now come from pages ranking in the top 10** (Ahrefs, 2026), down from roughly 76% in mid-2025, so classic rank is a weakening proxy, and these on-page/brand levers matter more, not less. Second, by content type, **editorial blog content drew 53.46% of citations versus 0.04% for press releases** (BuzzStream, 2026). Format and substance beat distribution channel.

A practical ranking for most teams:

1. **Structure first**: fastest, fully controlled, highest on-page evidence scores.
2. **Authority always**: strongest correlation, but a months-long build; start now.
3. **Freshness as maintenance**: keep competitive pages current so the first two keep paying off.

And the payoff is measurable downstream: Seer Interactive (2026) found being cited was associated with about **120% more organic clicks per impression** than not being cited, so the levers that win [citations](/glossary/citation) feed the funnel even in a [zero-click](/blog/from-clicks-to-citations) world.

The catch is that you can't manage what you don't measure. Which levers are actually moving *your* citations, and whether a structure fix or a freshness pass won the answer back. Only shows up by watching your visibility across engines over time. That ongoing read is what **Buffy Intel** is built to give you: which pages get cited, for which questions, on which engines, and what changed when you pulled each lever.

## From clicks to citations: the metrics that replace rankings
Source: https://heybuffy.com/blog/from-clicks-to-citations

For two decades the scoreboard was simple: rankings and clicks. In AI search, both are going quiet. Answers are increasingly [zero-click](/glossary/zero-click-search), and the buyer forms an impression *inside the answer*, often without ever visiting your site. If you only measure traffic, you're blind to where the decision now happens.

The metrics have to move with the behaviour: **from clicks to citations.**

## What stops working

- **Rank alone.** Being #3 in the blue links matters less when the AI answer above them names two brands and you're not one.
- **Clicks/CTR as the whole story.** A zero-click answer can win or lose you a customer with no click to count.
- **Single-engine checks.** ChatGPT, Gemini, Claude, and Google's AI surfaces disagree; one of them is a third of the picture.

## The new scoreboard

Track these *inside the answers*, across engines, over time:

| Metric | What it tells you |
|---|---|
| [Share of Voice](/glossary/share-of-voice) | Do you appear, and how often vs competitors? |
| [Citation Coverage](/glossary/citation-coverage) | Is your *own site* the cited source, or someone else's? |
| [Brand Perception](/glossary/brand-perception) | *How* are you described. Premium, budget, dated? |
| Sub-query recall | Across the [fan-out](/blog/how-query-fan-out-works), how many branches contain you? |
| Consistency | How reproducible is all of the above (AI is non-deterministic)? |

## Why this isn't just "SEO with new words"

These aren't rankings relabelled. Citation and presence behave differently: they vary run-to-run, differ by engine, and are driven by [entity strength](/glossary/entity-authority) and corroboration as much as on-page work. You can't infer them from a rank tracker. You have to *ask the engines* the questions your customers ask and log who gets named and cited.

> The brand cited in a zero-click answer can win the sale without ever appearing in your traffic report. If your dashboard only counts visits, you're measuring the old game.

## The practical shift

Keep your SEO metrics. They still feed AI Overviews. But add an **answer-level layer**: presence, citations, share of voice, and sentiment, sampled across many prompts and every engine, tracked as a trend. That's the gap [measuring AI visibility](/blog/how-to-measure-ai-visibility) closes, and exactly what **Buffy Intel** is built to report.

## How to set up an AI-referral dashboard in GA4 (in one afternoon)
Source: https://heybuffy.com/blog/ga4-ai-referral-dashboard

You can stand up a working AI-referral view in GA4 in an afternoon, with no tagging changes. The build has four parts: a **channel** that captures visible AI referrals, an **exploration** that ties them to outcomes, an **estimate** for the dark portion, and a **maintenance habit** so it doesn't rot. This is the hands-on companion to [why AI traffic shows up as "Direct"](/blog/why-ai-traffic-shows-up-as-direct). Read that first if you want the mechanics.

## Step 1: Create the "AI / LLM referral" channel

In GA4 (as of mid-2026): **Admin → Data display → Channel groups**. Don't edit the default group. **Create a copy**, then add a new channel at the **top** of the rule order so it claims AI hits before Organic or Referral can.

Define it as *Source matches regex*:

```
chatgpt\.com|chat\.openai\.com|openai\.com|perplexity\.ai|gemini\.google\.com|
copilot\.microsoft\.com|bing\.com/chat|claude\.ai|you\.com|poe\.com|phind\.com|
duckduckgo\.com/aichat|meta\.ai
```

Two notes. First, **rule order is the whole trick**: if Organic Search sits above your AI channel, Google-property AI sources can get claimed there. Second, channel groups apply from creation onward (they don't rewrite history), so the sooner this exists, the sooner you have a trend.

## Step 2: Tie the channel to outcomes

Reports answer "how much"; you want "is it worth anything." Build a **Free-form exploration**: dimension = your new channel (from the custom channel group), metrics = sessions, engaged sessions, key events (conversions), and revenue. Add **landing page** as a second dimension and you'll see *which pages AI answers send people to*. Usually deep content and PDPs, not the homepage.

This is the table that makes the case internally: AI-referred visitors arrive pre-recommended, so their conversion rate typically reads meaningfully above generic organic. Report it as revenue, not sessions. Sessions undersell it.

## Step 3: Estimate the dark portion

The visits that lost their referrer are sitting in "Direct." You can't reclaim them, but you can bound them. Build a second exploration on **Direct** sessions with three filters:

1. **Landing page is not the homepage** (bookmark/typed traffic overwhelmingly lands on `/`).
2. **New users** (AI answers skew toward first-time visitors).
3. Landing pages that match your **citable content**: the blog posts, guides, and PDPs that appear in AI answers.

Trend that segment next to your Step-1 channel. When they rise and fall together, you're looking at the same demand split across two buckets; the ratio between them is your house **dark-traffic multiplier**. It's an estimate. Defensible, directional, honest, and far better than reporting only the visible floor. (The reasoning behind each signal is in [the companion piece](/blog/why-ai-traffic-shows-up-as-direct).)

> The channel you built in Step 1 is the floor. The Step-3 segment is the shadow. Report both, labelled as such. A floor plus an estimate beats a precise-looking number that's silently wrong.

## Step 4: Keep it honest

- **Update the regex** when a new engine ships or a domain changes. Put a quarterly reminder on it. New AI sources appearing as plain "Referral" are your tell.
- **Annotate launches** (site changes, AI-visibility pushes) so movements in the trend have context.
- **Don't over-read small numbers.** Pre-scale, week-to-week noise is large; judge the monthly trend.
- **Remember what GA4 can't see:** answers that mention you but send no click. A [zero-click](/glossary/zero-click-search) recommendation still shapes the shortlist, which is why this dashboard pairs with [answer-level metrics](/blog/ai-visibility-reporting-stack), not replaces them.

## What you'll have by evening

One channel showing visible AI referrals and their revenue, one view estimating the hidden remainder, and a trend you can defend in a planning meeting. What it still can't tell you: *which prompts, which engines, and which of your pages* earn the answers upstream of the click. That's the answer-level layer. [Share of voice, citation rate, sentiment](/blog/ai-visibility-reporting-stack), and tracking it daily across every engine is what **Buffy Intel** does.

## How to get cited by AI when you don't have a high-authority domain
Source: https://heybuffy.com/blog/get-cited-without-high-domain-authority

**You do not need a big domain to be cited by AI — you need to be the clearest, best-corroborated source on a specific question.** Because AI engines retrieve at the passage level and weigh [corroboration](/glossary/corroboration) and extractability over backlinks, a small site can be lifted ahead of a household name. In Featured's 2026 analysis, [34.5% of AI citations came from sites with a Domain Authority under 40](/blog/does-domain-authority-affect-ai-citations). This is the playbook for competing from a low-authority position.

**Last reviewed: 26 August 2026.** This assumes you have a real site AI crawlers can reach and you are willing to go deep on a narrow topic. It complements the general [how to get cited by AI](/blog/how-to-get-cited-by-ai) playbook — that covers the structural basics for any site; this covers the *strategy* when you cannot win on domain authority.

## Why a low-authority site can win AI citations at all

Because the unit of citation is a passage, not a domain. An AI engine fans a question into sub-queries and selects the passages that best answer each one, judged on relevance, extractable structure, freshness, and corroboration — not on how many sites link to you. That is why Domain Authority, the backlink-based score, [barely predicts AI citations](/blog/does-domain-authority-affect-ai-citations), and why AI citations [do not track Google rank](/blog/does-google-rank-get-you-cited-by-ai) either.

The strategic reading: you cannot beat an incumbent on authority, but you can beat them on *this exact question* by being more specific, better structured, and better corroborated for it. Do that across a cluster of related questions and you become the recognised source for a lane — which is [entity authority](/glossary/entity-authority), the signal that actually correlates with citations.

## Step 1: Pick a lane narrow enough to own completely

Choose a topic specific enough that you can be the most comprehensive source on it, not the tenth-best source on a broad one. Broad guides get cited fast but plateau; focused single-topic explainers overtake them (Promptwatch, 2026; directional). A big domain covers your category shallowly across a thousand pages — your advantage is covering one slice of it deeper than anyone.

- Target questions with weak existing answers, not the highest-volume head terms.
- Prefer a cluster of tightly related questions over one isolated page — interlinked depth signals topical authority.
- Say no to breadth early; a small site that tries to cover everything is a strong source for nothing.

## Step 2: Become the primary source, not a summary of others

Publish something an engine can only get from you: original data, a first-hand method, a specific worked example, named and dated facts. A page that restates what larger sites already say gives an engine no reason to cite the small version. A page that *is* the source of a specific claim is a citation magnet regardless of authority.

- Put your most specific, [numeric and dated](/glossary/citation) claims where they are easy to lift — in a table or an answer-first sentence.
- Cite your own sources for any data claim; it models the behaviour engines reward and makes you safer to quote.
- If you cannot yet be the primary source, be the clearest *synthesis* — the page that reconciles the topic best — but original evidence beats synthesis every time.

## Step 3: Earn mentions, don't chase links

Being named across the web matters more than the link. Ahrefs' 2026 study of 75,000 brands found branded web mentions correlated with AI Overview presence about three times more strongly than raw backlink count (0.664 versus 0.218, Spearman — correlational, directional). For a low-authority site that is good news: you can earn mentions faster than you can build a link profile big enough to move a Domain Authority score.

- Get named in independent coverage, reviews, and expert roundups for your lane — the [earned-media](/glossary/earned-media) route.
- Show up where communities discuss your topic; a relevant forum mention can carry more AI-citation weight than a low-authority backlink. See [using Reddit for AI-search visibility](/blog/how-to-use-reddit-for-ai-search-visibility) and [Reddit AEO for startups](/blog/reddit-aeo-for-startups).
- Keep your brand entity consistent everywhere — same name, same descriptor — so scattered mentions reinforce one entity.

## Step 4: Make sure AI can actually reach and parse you

None of the above matters if the crawler cannot fetch the page. This is where small sites quietly lose citations they had already earned.

- Confirm AI crawlers are not blocked in robots.txt or at your CDN, and that your facts live in server-rendered HTML, not JavaScript-only rendering.
- Get indexed where the engines read — for ChatGPT that means Bing indexation in particular; confirm your key pages are in Bing, not only Google.
- Add the [structured data](/glossary/structured-data) that labels what your facts are, and keep pages in the sitemap and internally linked.

## Step 5: Keep the pages fresh

Live retrieval favours recently reviewed pages, and citations decay after roughly a quarter, so a small site that maintains its handful of pages can hold citations a neglected bigger site loses.

- Put your citation-earning pages on a refresh cadence and make updates substantive — corrected facts and new data, not a bumped date — as covered in the [3-month citation cliff](/blog/content-freshness-citation-cliff).
- Show an honest "Updated" date so the freshness is legible to both readers and engines.

> A small site cannot out-authority the incumbents, but it can out-answer them on one question — and at the passage level, that is what gets cited.

## What to measure

Track whether the strategy is working by watching citations, not authority scores. A Domain Authority tool cannot tell you whether ChatGPT, Perplexity, Claude, or Gemini actually cited you — only per-engine [citation](/glossary/citation) tracking can. Watch which of your pages get cited, on which engines, and over time; when a page slips out of answers, that is the cue to refresh it, not to build more links. This per-engine, over-time citation view is exactly what **Buffy Intel** measures — so a low-authority site can see the lane it is winning and double down. Questions: support@flash.tech.

## How to get into the "best of" lists AI engines actually cite
Source: https://heybuffy.com/blog/get-into-ai-cited-best-lists

For "best X for Y" buyer questions, AI engines lean hardest on one page type: the independent "best of" list. New research puts a number on just how dominant it is, and points to a clear, if uncomfortable, playbook.

## How much do best-of lists dominate AI answers?

In a 2026 study, Glen Allsopp analysed around **750 top-of-funnel prompts** across ChatGPT (software, products, and agencies) and roughly **26,283 source URLs**. The headline finding:

- **"Best X" blog lists were 43.8% of all cited page types**: the single most-cited format.
- Of 1,100 best-of lists examined, **79.1% had been updated in 2025**, and **26% within the prior two months**: strong evidence that engines favour recently refreshed comparison content.
- Brands in the **top third** of a list were more likely to surface in ChatGPT answers than those further down.
- About **35% of cited best lists came from low-authority domains**: many built mainly for link-building rather than genuine usefulness.

It's a single practitioner study on one engine, so read it as directional. But it echoes a pattern other 2026 analyses report and that we've covered in [why AI loves listicles](/blog/why-ai-loves-listicles): for commercial-intent questions, third-party roundups beat brand-owned pages by a wide margin.

## Why engines reach for roundups over your own page

When a shopper asks "what's the best X," the model wants a **neutral-looking, multi-option** answer. A page that already weighs several brands against criteria matches that shape; a page listing only your own products reads as a sales pitch and gets discounted.

> You can't out-neutral an independent comparison by writing your own "best tools (and we're #1)" page. The model is trained to treat single-brand roundups as biased, so the work isn't more self-promotion, it's getting *into* the lists that already get cited.

Roundups also carry higher [entity density](/blog/entity-strength-ai). Many named brands co-occurring with the category, and more verifiable specifics, both of which retrieval favours.

## The earned-placement playbook

If the lists win and you can't credibly publish your own, the strategy is to earn your way into the ones that already get cited:

1. **Find the lists AI is actually pulling.** For your top buyer questions, see which roundups the engines cite, and treat that set as your target list, not a random outreach spread.
2. **Earn placement, fairly.** Pitch reviewers and publishers with verifiable specifics. Pricing, features, real differentiators. The things a list editor needs to slot you in accurately.
3. **Aim for the top third.** Position inside the list matters; a mention buried at the bottom does less than a spot near the top. Give editors the evidence to rank you well.
4. **Prioritise freshness.** Lists updated in the last quarter get cited most. Favour publishers who keep their roundups current, and revisit your own placements so your listed facts stay accurate.
5. **Mind authority. Both ways.** Plenty of cited lists sit on low-authority domains, but durable visibility comes from credible ones. Chase placements that are both *cited* and *trustworthy*.

## Where your owned content still wins

This isn't an argument against publishing. It's about giving owned content the right job. Your own pages win **brand- and feature-specific** questions: "how does X work," "X pricing," "does X integrate with Y." There the model wants the canonical first-party source, and that's you. Reserve owned content for those queries plus genuine [educational explainers](/blog/how-to-get-cited-by-ai) that build entity strength; pursue earned placement for the "best X" questions.

The net: for "which is best" buyer questions, the independent roundup wins, so the move is getting into the comparison content that already gets cited, and then tracking whether it's working across every engine. That tracking is what **Buffy Intel** is for.

## How to get your store into Google's Universal Cart (UCP)
Source: https://heybuffy.com/blog/get-your-store-into-universal-cart

**To get your store into Google's Universal Cart, you meet Google's Merchant Center baseline, enrich and structure your catalog so an agent can describe and buy your products, choose a checkout path, and then measure whether agents actually surface you.** The Universal Cart runs on the [Universal Commerce Protocol (UCP)](/blog/what-is-ucp), Google's open standard for the agentic shopping journey; being *in* it means an agent can discover, buy, and track an order from your store inside Search or the Gemini app without the shopper ever loading your site.

This is the practical path, in order. It assumes you sell online and want to be transactable by AI agents on Google's surfaces; the catalog steps apply to any agentic surface, and the surface-specific steps are called out as such. Specifics are dated to mid-2026 and will move — the durable work is the catalog groundwork.

## Step 1 — Meet the Merchant Center baseline

Google's stated gate for the Universal Cart is an **active Merchant Center account with checkout-eligible products.** In practice that means each product carries accurate price and availability, valid identifiers, and the shipping and returns data a real purchase needs — the same data quality Google Shopping has always required, now as the entry ticket for agent checkout.

Start by auditing feed health: resolve disapprovals, fix missing GTINs or attributes, and confirm price and stock match your site. An agent cannot complete a purchase against a product it is not allowed to sell.

## Step 2 — Enrich the catalog so an agent can describe you

Eligibility gets you in the door; richness gets you chosen. AI agents field long, conversational queries and can only recommend what your [product data](/glossary/product-feed) actually says. This is the same enrichment covered in depth in [preparing your catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents) — do that work here rather than repeating it:

- **Conversational context** — what a product pairs with, who it suits, how to use and care for it.
- **Social proof as data** — review themes exposed as crawlable text, not a star widget.
- **Objection handling** — product-level FAQs answering the questions that decide a sale.

Generate this from your own reviews, search logs, and support tickets — never from a general-purpose model's guesses, which invent confident, wrong detail you then spend a year correcting.

## Step 3 — Expose it as structured, parseable data

UCP standardises primitives — product discovery, checkout, discounts, fulfilment, order management, identity linking — but it can only act on data it can read. Make sure every product fact lives in server-rendered HTML with [structured data](/glossary/structured-data) labelling what it is, not locked in images, click-to-reveal tabs, or JavaScript an agent will not execute.

This is where being agent-buyable and being [AI-visible](/glossary/answer-engine-optimization) converge: the clean, structured catalog that lets UCP transact is the same asset that lets answer engines cite and recommend you.

## Step 4 — Choose your checkout path

The Universal Cart offers two ways to complete a purchase, and the merchant stays the merchant of record in both:

1. **Native checkout** — the shopper pays with Google Pay in a few taps, inside the Google surface.
2. **Transfer to your site** — the cart moves to your own checkout to complete.

Native checkout removes friction but keeps the shopper in Google's surface; transferring keeps them in your funnel but adds a step. Pick per your margins, your data needs, and how much of the experience you want to own — this is a genuine strategic choice, not a default.

## Step 5 — Layer payment authorisation with AP2

For agent-initiated payments — where the agent, not the person, pushes the button — UCP is designed to work with [AP2](/blog/what-is-ap2), Google's Agent Payments Protocol, which attaches a cryptographically signed proof that the human authorised the purchase. Google said it would bring AP2-backed payments to these surfaces starting with Gemini. You largely *accept* this rather than build it, but knowing UCP hands payment off to AP2 tells you where the trust boundary sits: UCP runs the journey, AP2 vouches for the money.

## Step 6 — Measure whether agents actually surface you

Being transactable is not the same as being chosen. Once your catalog is UCP-ready, the open question is whether agents and answer engines actually discover, describe, and recommend your products — and whether they do it accurately. Track which queries surface you, how you are described, and whether your own pages become the cited source, across every engine and over time.

That feedback loop — did being buyable translate into being bought? — is exactly what **Buffy Intel** is built to report. For a fuller side-by-side of the standards underneath all this, see [ACP vs AP2 vs x402](/blog/agent-payment-protocols-compared). Questions: support@flash.tech.

## Ghost citations: when AI cites your page but never names your brand
Source: https://heybuffy.com/blog/ghost-citations-cited-not-named

**A "ghost citation" is when an AI engine pulls a fact from your page and links it as a source, but never names your brand in the answer.** The reader sees the claim and maybe a link icon, never who said it. A study Semrush published in June 2026, with Kevin Indig of Growth Memo, put a number on it: across four engines, roughly **61.7% of brand appearances were ghost citations**: cited, not named. Citation and mention, it turns out, are two different outcomes that rarely travel together.

This is a reading of one multi-engine dataset, not a universal law. Every figure below is attributed, dated, and hedged. It sits alongside our [two-lens visibility audit](/blog/brand-mention-gap-vs-source-gap) and the [cited-isn't-recommended](/blog/cited-vs-recommended-in-ai-search) piece; together they map the ways a link can fail to become brand value. If you want the playbook rather than the diagnosis, skip to [how to get named, not just cited](/blog/how-to-get-named-in-ai-answers).

## What is a ghost citation, exactly?

A ghost citation is a source link with no brand mention attached. The engine used your page. It may even show a citation marker, but the answer text never says your name, so the reader learns the fact without learning who it came from. The Semrush study (with Kevin Indig / Growth Memo, published June 2026) logged **3,981 domain appearances across 115 prompts in 14 countries** on ChatGPT, Google AI Overviews, Gemini, and Google AI Mode, using the Semrush AI Visibility Toolkit, and split every appearance three ways:

| How a brand appeared | Share of appearances | What the reader sees |
|---|---|---|
| Ghost citation. Cited, not named | ~61.7% | A fact and a link; no brand name |
| Cited **and** named | ~13.2% | The fact, the source, and who said it |
| Named, not cited | ~25.1% | The brand named in prose; no source link |

The single most common outcome. Nearly two in three appearances. Is the one that builds the least brand value: your page does the work, and someone else's answer takes the credit. All figures are vendor-reported and directional; treat the shape, not the third decimal, as the finding.

## Do citations and mentions actually decouple?

Yes, and by more than most brands assume. Aggregate the table above and the two rates pull apart cleanly: the **citation rate was about 74.9%** (ghost + named-and-cited) while the **mention rate was only about 38.3%** (named-and-cited + named-only). A link is roughly twice as likely as a name. The [citation](/glossary/citation) and the [total mentions](/glossary/total-mentions) are measuring different events, and the study shows they don't move in lockstep.

The starkest evidence is how differently the engines behave, which is the part worth internalising:

| Engine | Named in the answer | Cited as a source |
|---|---|---|
| Gemini | ~83.7% | ~21.4% |
| ChatGPT | ~20.7% | ~87% |

These are near-mirror images. Gemini tends to **name brands in prose but rarely link them**; ChatGPT tends to **link sources heavily but rarely name the brand behind them**. Measuring only one number on only one engine would give you a wildly wrong picture of your visibility. A pattern consistent with the low cross-engine overlap documented in [do a few domains dominate AI citations](/blog/ai-citation-domain-concentration). Per-engine, per-metric, or you're guessing.

## Why does a model cite without naming?

Because retrieval and phrasing are separate steps. An engine can retrieve your page into its context, lift the fact, and then generate a sentence that states the fact plainly. Without the naming being a deliberate act of attribution. Three mechanics drive the gap:

- **Paraphrase strips provenance.** The model restates the claim in its own words; unless your brand name is part of the claim, there's nothing tying the sentence to you.
- **The link is a footnote, not a sentence.** Citation markers are attached after generation. The prose can carry a fact whose source sits only in a link the reader never opens.
- **Naming is an entity decision.** The model names an entity when it's confident the entity *is* the answer. A function of [entity strength](/blog/entity-strength-ai), not of whether your page was retrieved. Weak entity association means your facts get used anonymously.

The through-line: earning the citation is a content-and-reachability job; earning the mention is an entity job. They have different fixes, which is exactly why they decouple.

## Does it vary by market?

Sharply. The same study found the mention rate swings by country: brands were named in about **50% of answers in India and Sweden**, but only **18-22% in Italy, Brazil, and the Netherlands** (Semrush/Indig, June 2026). The gap is large enough that a global brand can look well-recognised in one market and near-invisible in another off the same content. If you operate across markets, a single blended mention number hides more than it shows. Measure per market as well as per engine.

> A citation is a link; a mention is your name. In a zero-click answer, the link is a footnote most readers never open, so being the uncredited source of a fact is closer to invisibility than to visibility. The work is making your name travel with your facts.

## Why does this matter for AI visibility?

Because a ghost citation delivers almost none of the brand value a citation is assumed to. In the old model, a link earned a click and a visit; in a [zero-click](/glossary/zero-click-search) AI answer, most readers never click, so an unnamed link leaves no memory of you at all. You supplied the answer and stayed anonymous.

It also reframes what "we're cited a lot" means. A healthy citation rate with a weak mention rate is precisely the *cited-but-not-named* quadrant of our [two-lens audit](/blog/brand-mention-gap-vs-source-gap). A signal to stop optimising for more citations and start working the entity side. This doesn't contradict the case for earning citations; it refines it. Citations remain the supply that feeds answers. The point is that supply alone, without your name attached, doesn't build the brand, so both metrics belong on the dashboard, tracked apart. How to close the gap is its own playbook: [how to get named, not just cited](/blog/how-to-get-named-in-ai-answers).

The durable read is simple. Measure your [citation](/glossary/citation) rate and your mention rate as two separate lines, on each engine and each market, and watch the gap between them. That per-engine, per-market split, and how it moves over time. Is what **Buffy Intel** is built to track. Questions: support@flash.tech.

## Google AI controls compared: robots.txt, Google-Extended, nosnippet, the AI opt-out, and noindex
Source: https://heybuffy.com/blog/google-ai-control-levers-compared

**Five different Google controls decide how your content is crawled, ranked, shown in AI answers, and used for training — and they do genuinely different jobs that are easy to mix up.** Reaching for `noindex` when you meant the AI opt-out, or assuming Google-Extended keeps you out of [AI Overviews](/glossary/ai-overviews), is a common and costly mistake. This is a neutral, criteria-based reference: what each lever does, what it leaves alone, and when it is the right one.

**Last reviewed: 20 August 2026.** Behaviour and availability — especially of the newest control — are moving; the descriptions below reflect Google's stated guidance and reputable reporting as of mid-2026. Verify against current Search Console and Search Central documentation before acting.

## The five controls at a glance

Each row is one lever; each column is a thing you might want to protect or remove. Read across to see exactly what a control touches.

| Control | Normal Search ranking/indexing | AI Overviews & AI Mode | Featured / text snippets | Gemini model training | Scope |
|---|---|---|---|---|---|
| **Search generative AI control** (Search Console setting) | Unaffected | Removes you | Unaffected | Unaffected | Google AI surfaces only |
| **nosnippet / data-nosnippet / max-snippet:0** | Page still ranks | Removes you | Also removed | Unaffected | The specific page/element |
| **Google-Extended** (robots.txt token) | Unaffected | Not removed on its own | Unaffected | Limits training + Gemini-app grounding | Gemini training/grounding |
| **Block Googlebot** (robots.txt) | Not crawled → drops out | Removed (not crawled) | Removed | Removed | Everything Google |
| **noindex** (meta/header) | Removed from index | Removed | Removed | Removed | Everything Google |

Source: Google's stated guidance and reputable SEO reporting, mid-2026. The pattern to notice: only the **Search generative AI control** removes you from the AI answer while leaving normal ranking *and* snippets intact. Every other "remove me" lever takes something else down with it.

> Only one of Google's five controls removes you from the AI answer without also costing you ranking or snippets — reach for the wrong lever and you take down far more than you meant to.

## Which control should you use for each goal?

Match the lever to the outcome, not to the fear. The precise goal decides the tool.

- **"Stay in Search but out of AI Overviews/AI Mode."** Use the [Search generative AI control](/blog/google-ai-features-opt-out). It is the only surgical option, and it is reversible with a toggle.
- **"Stop my content training Gemini, but keep appearing normally."** Use Google-Extended in robots.txt. Note it governs training and Gemini-app grounding — not whether you show in AI Overviews.
- **"Keep this specific preview text out of results."** Use nosnippet or `data-nosnippet` on the element — accepting that it also removes featured-snippet eligibility for that page.
- **"Remove this page from Google entirely."** Use noindex. Expect to lose ranking, snippets, and AI features together.
- **"Stop Google crawling a section at all."** Block the path for Googlebot in robots.txt — the bluntest option, with the widest collateral effect.

## Why do people pick the wrong lever?

Because the controls sit at different layers — crawl, index, display, and training — and the labels do not make that obvious. Three recurring mistakes:

1. **Assuming Google-Extended blocks AI Overviews.** It does not on its own; AI Overviews are built from Google's Search index, so a page Googlebot can still crawl and index can still surface in the AI answer even with Google-Extended set. The [training-versus-retrieval distinction](/glossary/retrieval-augmented-generation) is the crux — Google-Extended is a training/grounding control, not a retrieval-display control.
2. **Using nosnippet to leave AI Overviews and then losing featured snippets.** This was the only pre-2026 route and it quietly cost classic-Search visibility; the Search generative AI control now removes that trade-off.
3. **Reaching for robots.txt or noindex to make one AI change.** Both are sledgehammers that also demolish your normal Search presence. For an AI-only decision they are almost never the right tool.

## Do these controls affect other AI engines?

No — and this is the biggest scope error of all. Every lever in the table is a *Google* control. None of them changes how ChatGPT, Perplexity, Claude, or other engines crawl, retrieve, or cite your pages. Those engines are governed by their own [AI crawler](/glossary/ai-crawler) directives in your robots.txt and their own retrieval systems. Deciding whether to be open or closed to *those* engines is a separate, cross-engine strategy question — see [whether to let AI crawlers index your site](/blog/should-you-let-ai-crawlers-index-your-site) and, at the more adversarial end, [blocking or licensing AI crawlers](/blog/license-litigate-or-block-ai-crawlers). The standing default for a visibility-seeking brand is to [keep AI crawlers reaching your site](/blog/keep-ai-crawlers-reaching-your-site) and win the citation, not to wall it off.

Picking the right control is only useful if you can see the result. Buffy Intel tracks your brand's presence across Google's AI Overviews and AI Mode alongside ChatGPT, Perplexity, and Claude — daily — so you know whether a lever did what you intended. [Check your AI visibility with Buffy Intel](https://heybuffy.com), or reach us at support@flash.tech.

## What is Google's AI Overviews opt-out control, and should you use it?
Source: https://heybuffy.com/blog/google-ai-features-opt-out

**Google now lets you remove your site from AI Overviews, AI Mode, and Discover's AI features through a Search Console setting — without harming your normal Search ranking.** The control, commonly called the *Search generative AI* setting, was reported to take effect from **17 June 2026**, starting with a subset of UK site owners and widening from there. Its significance is the decoupling: for the first time, opting out of Google's AI answers no longer forces you to also give up your [featured snippets](/glossary/featured-snippet). For most brands the right move is still to stay in — but the choice is finally a real one.

**Last reviewed: 20 August 2026.** Rollout status, availability, and exact behaviour are moving; specific dates and coverage below come from Google's stated guidance and reputable secondary reporting as of mid-2026, and should be read as dated. Verify against what actually appears in your own Search Console.

## What is the Search generative AI control?

It is a site-level toggle in Google Search Console that governs whether your content can appear in — and help ground — Google's generative AI Search features. It lives under Search Console **Settings**, and when a site opts out it stops receiving traffic and impressions from three surfaces at once:

- **AI Overviews** — the AI answer box at the top of many Google results.
- **[AI Mode](/glossary/google-ai-mode)** — Google's fully generative, conversational search interface.
- **AI Overviews in Google Discover** — the generative features inside the Discover feed.

Crucially, an opted-out site *still appears* in regular Google Search results and in the standard Discover feed. Google has stated the control is not used as a ranking or inclusion signal anywhere else in Search. In plain terms: you disappear from the AI answer, not from the blue links.

> For the first time, a brand can leave Google's AI answers without leaving Google Search — the opt-out and your ranking are finally separate decisions.

## How is this different from the old nosnippet method?

Until this control existed, Google's guidance was that the only way to keep a page out of AI Overviews was the `nosnippet` family of directives — and that came with a steep, coupled cost. The new setting breaks that coupling.

| Method | Removes you from AI Overviews? | Effect on featured snippets & text snippets | Effect on normal ranking |
|---|---|---|---|
| **nosnippet / data-nosnippet / max-snippet:0** | Yes | Also removed — you lose featured snippets and preview text | Page still ranks, but with no snippet |
| **Search generative AI control** (new) | Yes | Unaffected — snippets and previews stay | Unaffected; not a ranking signal |

Source: Google's stated guidance and reputable SEO reporting, mid-2026. The takeaway is that the older `nosnippet` route punished you in classic Search for opting out of AI; the new control does not. If you tried the coupled approach before and reverted because you lost snippet visibility, the calculus has changed.

## What does the control NOT do?

Plenty — and the gaps are where brands get this wrong. The control is narrow by design.

- **It does not block AI crawlers.** It is a display-and-grounding setting inside Google Search, not a crawl rule. To govern crawling you still use [robots.txt](/glossary/robots-txt) and tokens like Google-Extended.
- **It does not stop Gemini model training.** Google-Extended, a separate robots.txt token, governs training of Gemini models and grounding in the Gemini apps. The Search generative AI control does not.
- **It does nothing outside Google.** ChatGPT, Perplexity, Claude, and other engines have their own [AI crawlers](/glossary/ai-crawler) and their own retrieval; this Google setting is invisible to them.
- **It does not override Merchant Center or Ads.** Shopping and paid choices are configured separately and are unaffected.

So the four "keep AI away" levers do genuinely different jobs, and they are routinely confused. If you want the full side-by-side, see our [comparison of Google's AI-control levers](/blog/google-ai-control-levers-compared).

## Why does this control exist now?

Reporting ties the rollout to regulatory pressure, particularly in the UK, where publishers and regulators pushed for a way to leave AI answers without being penalised in ordinary Search. That framing matters for reading its scope: it was built to resolve a publisher grievance about the coupled `nosnippet` trap, not as a general-purpose "block AI" tool. Google's decision to start with a subset of UK site owners before widening is consistent with a regulator-driven pilot. Attribute this to secondary reporting and treat it as context, not a Google statement of intent.

## Should your brand actually opt out?

For most brands the answer is no — but here is the honest trade-off table, because a minority of sites have a real case.

| Situation | Leaning | Why |
|---|---|---|
| You want AI-visibility (most brands) | **Stay in** | Opting out removes you from a fast-growing answer surface; being cited in AI answers is the goal, not the risk |
| Ad- or subscription-funded publisher losing referral clicks to AI answers | **Consider opting out** | If AI Overviews are cannibalising the clicks that fund you, and you can measure it, leaving may protect revenue |
| You opted out via nosnippet before and lost snippets | **Switch, don't stay out** | The new control lets you rejoin AI features or leave them without the snippet penalty — re-evaluate cleanly |
| News/trending content | **Be careful** | Reporting indicates Top Stories increasingly render *inside* AI Overviews for trending queries, so opting out could drop you from both placements at once |

The measurement problem is the catch. As of mid-2026 there is no mature, Google-provided click or conversion breakdown for AI features, so "is AI Overviews costing me net traffic?" is still largely an estimate. Opting out to protect revenue you cannot yet measure is a bet, not a decision — which is why the default for a brand chasing visibility is to stay in and instead work on [being cited well in AI Overviews](/blog/how-to-optimize-for-ai-overviews).

This also should not be confused with the broader, strategic question of whether to [block AI crawlers or license your content](/blog/license-litigate-or-block-ai-crawlers). That debate is about your whole footprint across every engine; this control is one vendor, one surface, and reversible with a toggle. Blocking crawlers to protect IP and keeping open to AI answers for visibility are separate levers — this setting sits squarely in the second column, and for most brands the standing advice to [stay reachable to AI crawlers](/blog/keep-ai-crawlers-reaching-your-site) is unchanged.

## How do you find and use the setting?

Open Google Search Console, select the property, and look under **Settings** for the Search generative AI control. If it is present, the default is to remain included (appearing as links and helping ground AI responses); opting out is an explicit choice. Google has indicated changes can take a few days to process. If the setting is not there, your account has not received it yet — availability is still uneven, so its absence is not an error.

Whatever you choose, treat it as a monitored decision rather than a one-time switch: watch your AI-answer presence and referral patterns across engines before and after, so you are acting on evidence instead of instinct.

Buffy Intel tracks whether your brand is being cited across AI Overviews, AI Mode, ChatGPT, Perplexity, and more — daily — so a decision like opting in or out is grounded in your real visibility, not guesswork. [See where your brand stands in AI answers](https://heybuffy.com). Questions? Reach us at support@flash.tech.

## What Google's AI Mode usage data reveals (2026)
Source: https://heybuffy.com/blog/google-ai-mode-usage-data-2026

This is a fully-sourced reference on how people use [Google AI Mode](/glossary/google-ai-mode), drawn from Google's official report *"How people are using AI Mode in the U.S."*, published at the surface's one-year mark in mid-2026. The headline: Google says AI Mode has passed **1 billion monthly active users** globally, queries have **more than doubled every quarter** since launch, and the average AI Mode query is **triple the length** of a traditional search. This page collects the report's figures, each tied to its source.

**Last reviewed: 22 June 2026.** All figures below are from Google's *AI Mode U.S. Insights* report. Google states the data is from internal Google Search and Google Trends, covering the period from AI Mode's US launch in **May 2025 to April 2026**, and that AI Mode Trends data is *not* publicly available on trends.google.com. It is platform-reported and not independently audited, so read the *direction* as firmer than any single number, and hedge anything you quote as "as of mid-2026, per Google."

## How big is AI Mode, and how fast is it growing?

Google frames AI Mode as the most significant change to Search in its history. The scale figures it reported:

| Metric | Figure | Source |
|---|---|---|
| Monthly active users (global) | **Surpassed 1 billion** | Google, AI Mode U.S. Insights (2026) |
| Query growth | **More than doubled every quarter** since launch | Google, AI Mode U.S. Insights (2026) |
| US launch | **May 2025** | Google, AI Mode U.S. Insights (2026) |

The same 1-billion figure echoes what Google reported at I/O 2026 (see the [AI search statistics reference](/blog/ai-search-statistics-2026)). The direction is unambiguous: AI Mode now operates at the scale of the open web.

## How is search behaviour changing in AI Mode?

People search *differently*, not just more. Google's behavioural findings:

- **Queries are ~3× longer** than a traditional search query. People express full intent in natural language instead of keywords.
- **Follow-up queries grew more than 40% per month** on average in the US, as people refine and dive deeper across turns. A live example of [query fan-out](/glossary/query-fan-out) playing out conversationally.
- **More than 1 in 6 searches are multimodal** (non-text); image-input searches grew more than 40% month-over-month since launch, making them one of the fastest-growing query types.

The lead-in words confirm the shift to question-shaped search. Google's top first words in AI Mode queries were **What, How, I, Is, Can**, and the top keywords were **Find, Information, Identify, Explain, Summarize**. People ask questions; they no longer translate them into keywords.

> AI Mode rewards content that answers a full question and its follow-ups, because the average query is triple the length of a keyword search and people refine conversationally, turn after turn.

## What are people doing in AI Mode?

Google groups usage into five intents. **Explore, Decide, Learn, Create, Do**: and reports which categories grew fastest against AI Mode queries overall:

| Behaviour | Growth (vs AI Mode queries overall) | Signal |
|---|---|---|
| Planning ("Do") | **+80% faster** | Logistics, schedules, to-do and exercise plans |
| "Which" decision queries | **+40% faster** | "Which of", "which one" grew most. Comparison intent |
| Brainstorming ("Explore") | **+30% faster** | Open-ended, inspiration-led discovery |
| Image creation ("Create") | **More than tripled** since the start of the year | Creative generation inside Search |

The top 10 topics people search in AI Mode, per Google: Creative/Content Generation, Media/Entertainment, Education/Knowledge, Personal/Professional Development, Fashion/Beauty, Productivity/Practical Tasks, Food/Drinks, Technology/Coding, Health/Wellness, and Travel. The takeaway for brands: AI Mode is used for decision-making and planning, not just lookups, so content that helps a user *decide* and *act* is in the path of the fastest-growing query types.

## What does the data say about shopping?

Google reports that when shopping, people **often begin on traditional Search and click into AI Mode to dive deeper** with follow-up questions. The top shopping topics where those follow-ups happen:

| Rank | Top shopping topics (follow-ups) | Top retail attributes asked about |
|---|---|---|
| 1 | Electronics | Price |
| 2 | Books / Movies / Music | Location |
| 3 | Apparel | Colour |
| 4 | Health / Beauty | Brand |
| 5 | Automotive | Availability |
| 6 | Home / Garden | Size |
| 7 | Grocery | Material |
| 8 | Home Improvement | Style |
| 9 | Toys / Games | Type |
| 10 | Sports / Outdoors | Quality |

For apparel specifically, the top follow-up subjects were Clothing, Shoes, Jewelry, Handbags, and Wedding/Bridal. The practical read: AI Mode shoppers ask for **concrete, structured attributes**: price, availability, size, material, so brands that expose those facts cleanly win the follow-up. We turn this into an action plan in [how to optimise your products for AI Mode shopping](/blog/optimize-for-ai-mode-shopping).

## How should you use these figures?

Treat this as a dated reference, not a guarantee. Every number here is **Google's own**, drawn from internal Search and Trends data that Google notes is sampled and not publicly verifiable on trends.google.com, so cite Google and the date when you reuse one, and hedge as "as of mid-2026." Because live retrieval favours recently-updated pages, we keep references like this on a [refresh cadence](/blog/content-freshness-citation-cliff) and update figures substantively as new data lands.

The figure that ultimately matters is your own: whether AI Mode and the other engines surface, cite, and recommend *your* brand for the questions your customers actually ask. Tracked over time, not spot-checked. That measurement is exactly what **Buffy Intel** is built to provide.

## Search Console vs Merchant Center: which Google AI report shows what?
Source: https://heybuffy.com/blog/google-first-party-ai-reports-compared

Google now gives you **two** first-party reports for AI visibility, and they do not overlap the way their names suggest. [Search Console](/blog/google-search-console-ai-performance-report)'s Generative AI performance report is **impressions-only across all your content**. [Merchant Center](/blog/google-merchant-center-ai-performance)'s AI performance insights adds **query-level share of voice and a shopping funnel**, but only for products and only in a limited US pilot. This is a neutral, criteria-based comparison of what each shows, so you use the right one for the job, plus the blind spot they both share.

## What does each Google AI report actually cover?

The two reports answer different questions. Search Console answers "did my content appear in AI answers at all?" Merchant Center answers "how do my products rank in AI shopping, and for which terms?"

| Criterion | Search Console: Generative AI performance | Merchant Center: AI performance insights |
|---|---|---|
| Launched / status | 3 June 2026; beta rollout to a subset of sites | Announced 2026; limited **US pilot** as of mid-2026 |
| Scope | All content (any page type) | Product / shopping visibility only |
| Google surfaces | AI Overviews, AI Mode (Discover shown separately) | AI Overviews, AI Mode, Gemini app |
| Core metric | Impressions | Share of voice (impressions ÷ total, benchmarked) |
| Query data | No queries | Yes, popular shopping terms with your share |
| Funnel / stages | None | Discovery, Evaluation, Purchase |
| Attribute signals | None | Product attribute completeness (size, colour, material) |
| Paid vs organic | Organic AI features | Organic "free listing" only, excludes ads |
| Who it's for | Any verified site owner | Merchants with a product feed |

The headline difference: **only Merchant Center exposes the queries.** For shopping brands that is a genuine first, native [share of voice](/glossary/share-of-voice) and the exact terms surfacing your products. For everyone else, Search Console remains the only first-party AI signal Google offers, and it stays impressions-only.

## Which report should you use?

Match the report to what you sell and what you need to know.

1. **You're a retailer or D2C brand with a product feed.** Use **both**. Search Console for whole-site AI presence, Merchant Center for the shopping-specific share of voice, term list, and funnel. Merchant Center's Product Term Insights is where you find the shopping questions you're absent from; act on those.
2. **You're a publisher, SaaS, or service business.** Use **Search Console**. Merchant Center's report needs a [product catalogue](/blog/prepare-product-catalog-for-ai-agents) to populate, so it will stay empty for you. Search Console's impressions confirm which pages reach AI Overviews and AI Mode.
3. **You're outside the US pilot.** You only have Search Console today. Google has said Merchant Center's report expands to Australia, Canada, India, and New Zealand in the coming months; until then, treat the shopping-term data as unavailable rather than absent.

> Search Console tells you *whether* you appeared, for any content. Merchant Center tells you *which shopping terms* surfaced you and how you rank, for products. Different questions, and retailers need both answers.

## What do both reports leave out?

The shared blind spot is bigger than either report's feature list, and naming it is how you read them honestly. As of mid-2026, **neither** Google report shows:

- **Any non-Google engine.** Both cover only AI Overviews, AI Mode, and Gemini. Neither says a word about ChatGPT, Perplexity, or Claude, which is where a large share of AI discovery now happens.
- **Cited versus merely shown.** An impression or an appearance does not tell you whether the answer [leaned on you as a trusted source or just listed you](/blog/cited-vs-recommended-in-ai-search).
- **Clicks or value.** Neither ties AI visibility to traffic or conversion, so you can't price an AI impression.
- **Non-shopping queries.** Merchant Center's query data is shopping-only; there is still no first-party Google report of the *questions* that surface your editorial or brand pages in AI answers.

This is why first-party reports are a **baseline, not a scoreboard**. They are corroborated, free, and worth wiring in, exactly because Google itself confirms the data, but each is one platform's partial view. The strategic questions, across which engines, cited or not, are answered at the [answer level, across every engine](/blog/ai-visibility-reporting-stack), not inside one vendor's dashboard.

## How do you combine them into one view?

Layer them, don't pick one. A practical stack:

1. **Confirm presence** with Search Console AI impressions, whole-site.
2. **Diagnose shopping** with Merchant Center's funnel and Product Term Insights, if you have products and access.
3. **Add the other engines** with cross-engine, answer-level tracking, since Google's tools are silent on ChatGPT, Perplexity, and Claude.
4. **Verify citation, not just appearance,** by checking the real answers for whether you're quoted or [recommended](/blog/cited-vs-recommended-in-ai-search), the thing no impression count can tell you.

Turning per-platform feeds like these into a single answer-level scoreboard, presence, citations, and sentiment across every AI surface, tracked daily rather than spot-checked, is what **Buffy Intel** does. It's the layer that sits above Google's first-party reports and reconciles them with the engines those reports can't see. Questions: support@flash.tech.

## Is Google legally responsible for what its AI Overview says? A German court just ruled yes
Source: https://heybuffy.com/blog/google-liable-for-ai-overview-errors

In May 2026 a German court ruled that a Google AI Overview is **Google's own statement**: not a neutral list of links, and made Google legally liable for a false claim its AI invented about a publisher. The Regional Court of Munich I (Landgericht München I) granted an injunction and set fines of up to **€250,000 per violation**. The ruling matters far beyond one lawsuit: it is one of the first courts anywhere to treat an AI-generated summary as the platform's own speech, and it reframes what is at stake when an AI engine describes your brand.

The case is **26 O 869/26**, decided **28 May 2026**. This piece reads it for the durable lesson it carries, for Google, for every AI search engine, and for any brand that an AI answer can get wrong. It is a first-instance regional decision under German law and is appealable, so we treat its holding as a strong directional signal rather than settled global doctrine.

## What did the AI Overview get wrong?

Google's AI Overview falsely associated a Munich-based publishing company (Verlagshaus24, the plaintiff) with **scams, subscription traps and "dubious business practices,"** and connected it to other companies said to be involved in fraudulent schemes. According to the court's account and the coverage of the decision, the AI stated claims of the form *"Yes, [company] is known for dubious business practices"*. Connections that **appeared nowhere in the underlying source articles** the results were drawn from.

That last detail is the crux. This was not a case of the AI faithfully surfacing a bad source. The [AI hallucination](/glossary/ai-hallucination) manufactured a defamatory accusation that did not exist in the material it summarised. The publisher sued, and the court had to decide a question that sits under every AI answer: **when the machine invents something, whose statement is it?**

## Why did the court say the statement is Google's own?

Because, in the court's reasoning, the AI Overview does something a traditional search result does not. It **generates new, independent, substantive statements** rather than pointing to third-party pages. The court drew a clean line between the two:

| | Traditional search results | AI Overview |
|---|---|---|
| What it does | Makes third-party content **findable**; lists and links to sources | **Compiles, summarises and evaluates** content "in its own words" |
| Whose words | The third party's, quoted or linked | The platform's own synthesised statement |
| Liability posture | Intermediary; safe-harbour protections generally apply | **Direct infringer**; the platform is responsible for the output |

In the court's own framing, *"this 'overview with AI' represents [Google's] own statement made by its own AI offered to users,"* and because *"the AI used by the defendant independently compiles the information in the overview and summarises it into a summary text, this constitutes an independent presentation for which [Google] is responsible."* Google alone controls the model and the algorithms, the court noted, so Google, not the sources. Owns what the model asserts. It also rejected the argument that the feature deserves search-engine intermediary protection, observing that an AI overview "is by no means absolutely necessary for using the internet."

## What is the remedy, and does it stick?

The court **enjoined Google from disseminating the specific false statements** and attached fines of **up to €250,000 per violation**, with provisional enforceability and most of the proceeding's costs falling on Google. But the judges also noted a hard technical reality: nothing inherently stops a generative model from **producing the same statement again** on a future query. An injunction can forbid a claim; it cannot easily guarantee a probabilistic system never regenerates it. That tension. A legal duty not to repeat something the system may re-invent. Is exactly why this ruling is being read as a preview of a much larger fight.

> The court's move was subtle but far-reaching: it reclassified the AI answer from *a list of what others said* to *a thing the platform itself said*. Once an AI summary is your own speech, you own its mistakes.

## Why does a German defamation case matter for AI visibility?

Because it puts a legal frame around a problem GEO practitioners already track daily: **AI engines confidently state things about brands, and sometimes those things are wrong.** The ruling changes the stakes in three durable ways, none of which depend on German law surviving appeal.

- **Accuracy about your brand is now a liability surface, not just a marketing one.** If a platform can be held responsible for a false AI claim, platforms have a growing incentive to ground answers in sources they can defend, which rewards brands whose correct facts are reachable and [corroborated](/glossary/corroboration) across the web.
- **The defense and the growth lever are the same mechanism.** The way an engine avoids asserting a falsehood is the way it decides what to cite: check a claim against multiple independent, authoritative sources and discount what it can't verify. Being the well-[corroborated entity](/blog/entity-strength-ai) protects you *and* gets you cited. This is the same trust logic behind the [phantom-citation research](/blog/phantom-citations-hallucinated-references). Unverifiable claims get discounted, whether they are fake references or fake accusations.
- **"The AI got us wrong" now has both a technical and, sometimes, a legal path.** The everyday fix is still to [correct the sources the engine draws from](/blog/fix-wrong-ai-description); this ruling adds that, where a false AI statement is defamatory and harmful, accountability may not stop at "the algorithm did it."

Note the honest boundary: this does **not** mean brands can litigate their way to better AI visibility, and it does not make engines liable for merely unflattering-but-true answers. It addresses **false, defamatory** statements the AI itself generated. It also sits alongside, not against. The reality that AI answers can be [nudged by manipulated sources](/blog/can-ai-search-be-manipulated); the takeaway from both is the same discipline: control your own facts, and be the corroborated source the web agrees on.

## What should you actually do about it?

Treat it as one more reason to keep the diagnose-and-correct loop going as a matter of course, plus an awareness that egregious cases now have a legal dimension.

1. **Snapshot what AI says about you.** Check your brand across ChatGPT, Google AI Mode, AI Overviews, Gemini, Claude and Perplexity on a schedule. Repeated captures, since answers drift. You cannot fix a false claim you haven't seen.
2. **Fix your own source of truth.** Put accurate, current, unambiguous facts. Pricing, product lineup, positioning. In clean, [structured](/glossary/structured-data) HTML the engines can ground in.
3. **Correct the corroborating web.** Update the reviews, directories and knowledge-graph entries the model trusts, so the consensus tells one accurate story.
4. **Document harmful, false claims.** If an AI states something defamatory and damaging about you, preserve the evidence. The Munich ruling shows why that record can matter.

Knowing. Quickly and continuously. When an AI engine starts saying something false or damaging about your brand, across every engine and over time, is exactly what **Buffy Intel** is built to surface, so you can correct it before a buyer (or a court) ever sees it.

## Google Merchant Center now shows your AI Overviews and AI Mode share of voice
Source: https://heybuffy.com/blog/google-merchant-center-ai-performance

Google Merchant Center now has an **AI performance insights** report, and it is the first Google product to expose **query-level data** for AI shopping. It shows how your products surface across [AI Overviews](/glossary/ai-overviews), [AI Mode](/glossary/google-ai-mode), and the Gemini app, broken into four modules: your **share of voice**, a **Discovery-Evaluation-Purchase funnel**, the **shopping terms** buyers use, and the **product attributes** they ask for. As of mid-2026 it is a limited US pilot. It covers organic "free listing" visibility only, not ads.

That "query-level" part is the news. Google's [Search Console Generative AI performance report](/blog/google-search-console-ai-performance-report), launched 3 June 2026, is impressions-only: no queries, no [share of voice](/glossary/share-of-voice). Merchant Center's report is the first native Google surface to tell shopping brands *which terms* they show up for inside AI answers, and how they stack up against similar merchants.

## What is in the AI performance insights report?

Per Google's 2026 announcement and its Merchant Center Help documentation, the report has four modules. Each answers a different question about how your products appear in AI shopping.

| Module | What it shows | The question it answers |
|---|---|---|
| Share of voice | Your AI impressions divided by total impressions, benchmarked against similar merchants | "How visible am I versus my category?" |
| Shopping funnel performance | Visibility split across Discovery, Evaluation, and Purchase stages | "Where in the journey do I show up, and where do I drop out?" |
| Product term insights | Popular conversational shopping terms, with your share of voice for each | "Which shopping questions surface me, and which don't?" |
| Product attribute insights | The specifications buyers ask for (size, colour, material), with feed-completeness signals | "Which attributes should my feed cover?" |

The report scope is narrow and worth stating up front: Google describes it as covering **conversational shopping and brand queries** with **organic** AI visibility, the equivalent of free listings, excluding paid ads. It is product-and-shopping data, not a report on your whole site.

## How does the Discovery-Evaluation-Purchase funnel work?

Google splits your AI shopping impressions into three stages, so you can see where in the buying journey a product enters the conversation and where it falls away.

| Stage | What buyers are doing | Example query types Google groups here |
|---|---|---|
| Discovery | Broad, early exploration | Category, features, or style ("waterproof hiking jackets") |
| Evaluation | Comparing and checking specs | Product specifications, user reviews, comparisons |
| Purchase | Ready-to-buy signals | Pricing, availability, local stock |

The funnel is diagnostic. A product with healthy Discovery share but near-zero Evaluation share is being *found* but not *shortlisted*, usually because the specs, reviews, or comparison facts an AI needs at the Evaluation stage are missing or not [extractable](/blog/write-conversational-product-pages). That maps directly to the attributes buyers ask AI Mode about most, which Google published separately: [price, availability, colour, size, and material](/blog/optimize-for-ai-mode-shopping).

## Why does a native share-of-voice number matter?

Because until now, [share of voice](/glossary/share-of-voice) in AI answers was something you inferred from third-party trackers, never a figure Google handed you. A first-party, benchmarked number, "your impressions as a percentage of total, versus similar merchants", is a different kind of signal: it is corroborated by the platform doing the surfacing.

> Merchant Center's AI report is the first time Google tells a shopping brand which terms surface it inside AI answers and how it ranks against its category, not just that it appeared.

Two cautions keep the read honest. First, it is **shopping-scoped**: it measures product visibility across Google's AI surfaces, not citations of your editorial or brand content, and not any non-Google engine. Second, like the Search Console rollout, practitioners with early access report it is **light on direct actionability** so far, useful for spotting where you are absent, less so for telling you the exact fix. Treat it as a diagnostic layer, not a to-do list.

## How do I access it, and who has it?

The path, per Google's documentation: log into **Google Merchant Center**, open the **Analytics** tab, select **Products**, then select the **AI performance** tab.

- **Availability (as of mid-2026):** a limited **US pilot** with a subset of Merchant Center accounts. Google has said it will expand to **Australia, Canada, India, and New Zealand** in the coming months.
- **Why it may be empty for you:** most accounts are not in the pilot yet, and the data is shopping-and-product only, so a site with no product feed will not populate it.
- **What to do now if you have it:** benchmark your share of voice by funnel stage, note the Product Term Insights where your share is lowest, and check whether the Product Attribute Insights flag gaps in your [product catalogue](/blog/prepare-product-catalog-for-ai-agents).

For the broader context on how these shopping answers are assembled, see [how Google AI Mode works](/blog/how-google-ai-mode-works) and Google's own [AI Mode usage data](/blog/google-ai-mode-usage-data-2026). If you sell into India, note it is on the announced expansion list, which pairs with the [AI shopping in India](/blog/ai-shopping-in-india) picture.

## How should this fit your measurement stack?

As one first-party signal among several, not the whole picture. Merchant Center tells you about Google's AI shopping surfaces; it says nothing about ChatGPT, Perplexity, or Claude, and nothing about whether you were [cited as a source or merely recommended](/blog/cited-vs-recommended-in-ai-search). Fold it into the [five-metric reporting stack](/blog/ai-visibility-reporting-stack) alongside Search Console's AI impressions, Bing's citation data, and cross-engine tracking so no single vendor defines your view.

That cross-engine, answer-level scoreboard, presence, citations, and sentiment tracked daily across every AI surface rather than one platform's shopping tab, is exactly what **Buffy Intel** is built to give you. Questions: support@flash.tech.

## What Google Search Console's Generative AI performance report shows (and what it can't)
Source: https://heybuffy.com/blog/google-search-console-ai-performance-report

Google Search Console now has a **Generative AI performance report**: launched **3 June 2026**: that shows how often your pages appeared inside AI Overviews and AI Mode. It is the first time Google has officially confirmed, in your own first-party data, that it surfaces your content in AI answers. But it reports **impressions only**: no clicks, no queries, no position, and no way to tell whether you were *cited* or merely *shown*. It answers "did I appear?" and almost nothing else.

This is part of the [measuring AI visibility](/blog/from-clicks-to-citations) series. It is the Google-side counterpart to [what Bing Webmaster Tools' AI data tells you](/blog/bing-webmaster-tools-ai-visibility). A free first-party signal that is real evidence and a narrow slice at the same time.

## What does the Generative AI performance report include?

A single metric. Impressions. Sliced by four dimensions. According to Google's June 2026 announcement and the Search Console Help documentation, the report covers generative AI features in Search (AI Overviews and AI Mode), with a separate view for generative AI features in Discover; Search Labs experiments are excluded.

| Dimension | What it shows |
|---|---|
| Impressions | How often links to your site were shown inside a generative AI feature |
| Pages | Which URLs appeared, grouped to the canonical URL |
| Countries | Where the search originated |
| Devices | Desktop, tablet, or mobile (Search results only) |
| Dates | Performance over time. Hourly, daily, weekly, or monthly granularity |

The data is not a separate silo: Google notes these AI impressions are part of your overall Search performance totals, now broken out into their own view. Treat the newest days, shown as a dotted line, as preliminary. They can change within hours.

## What does the report deliberately leave out?

The omissions are bigger than the inclusions, and naming them is how you read the report honestly. As of its June 2026 launch, the report does **not** show:

- **Clicks or CTR**: so you cannot calculate the value of an AI impression or compare it to your traditional-search click-through rate.
- **The queries** that triggered the impression. You see that a page appeared, not the question that surfaced it.
- **Position or a visibility trend**: there is no "average position" equivalent for AI features.
- **Cited versus surfaced**: an impression does not tell you whether the answer leaned on your page as a source or merely displayed it among links.

> The report confirms you showed up. It can't tell you which question surfaced you, whether anyone clicked, or whether you were the source the answer trusted, and those are the questions that decide strategy.

This is the same critique practitioners raised within days of launch: impressions confirm presence but not *context*. A page with 100,000 AI impressions and no query, click, or citation breakdown tells you something is working without telling you what to do more of.

## How should you use it today?

Use it for what it is good at. Confirming reach and spotting movement, and pair it with the data it lacks. A practical workflow:

1. **Confirm coverage.** Check which pages earn AI-feature impressions at all. A page you expected to surface that shows zero impressions is a [reachability or extractability problem](/blog/why-youre-invisible-in-ai-search) to chase down.
2. **Watch trend, not snapshots.** AI impressions are noisy day to day; use the date view to read direction over weeks, the way you would [read any visibility case study](/blog/how-to-read-an-ai-visibility-case-study). Looking for sustained change, not a single spike.
3. **Cross-reference pages with your own AI-answer checks.** Because the report can't say whether you were cited, take the pages that earn impressions and verify in the actual engines whether you are quoted, linked, or [recommended versus merely cited](/blog/cited-vs-recommended-in-ai-search).
4. **Layer it into the stack.** This is one engine's impression feed. Fold it into the broader [five-metric reporting stack](/blog/ai-visibility-reporting-stack) alongside Bing's citation data and cross-engine [share of voice](/glossary/share-of-voice) so no single source defines your view.

## Why is an impressions-only report still worth wiring in?

Because a free, official, first-party signal beats inference. Even a narrow one. Before this report, "are we in AI Overviews?" was answered by third-party trackers and spot checks. Now Google itself confirms it, which is the kind of corroborated, first-party evidence worth anchoring a baseline on. The limits are the point, not a reason to ignore it: it tells you the door is open, and you still have to walk through the rest of the measurement yourself.

The honest read is that Google's report answers "did we appear in AI search?" and is silent on "which questions, how often clicked, and were we the trusted source?". The cross-engine, answer-level questions that decide where to invest. Closing that gap, by turning per-engine impression feeds into one answer-level scoreboard across every AI surface, is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Does Google's spam policy apply to AI Overviews and AI Mode?
Source: https://heybuffy.com/blog/google-spam-policy-ai-answers

Yes. As of a **2026 update**, Google's spam policy explicitly names "attempting to manipulate generative AI responses in Google Search" as spam. A definition that now covers [AI Overviews](/glossary/ai-overviews) and [AI Mode](/glossary/google-ai-mode), not just the ten blue links. The practical meaning: the tactics Google already treats as spam apply when the target is an AI answer, and can trigger the same enforcement. This piece lays out precisely what changed, what it does *not* mean, and where the line sits.

It pairs with the broader question of [whether AI search can be manipulated at all](/blog/can-ai-search-be-manipulated), which looks at the mechanism across engines; this piece is narrower. It is about Google's own stated *policy*.

## What did Google actually change?

Google updated the top-level definition in its Search spam policies so that "spam" now explicitly includes manipulating its AI answers. The current wording reads: *"Spam refers to techniques used to deceive users or manipulate our Search systems into featuring content prominently, such as attempting to manipulate Search systems into ranking content highly or attempting to manipulate generative AI responses in Google Search."* The final clause. **Attempting to manipulate generative AI responses**: is the addition. Search Engine Land reported the change in **May 2026**; it appears in Google's live spam-policy documentation. The effect is clarifying rather than a brand-new rulebook: Google is stating that the existing named spam categories. The ones that have long governed ranking. Also apply when the goal is to game an AI-generated answer.

| What | Detail |
|---|---|
| Change | Spam definition now covers "attempting to manipulate generative AI responses in Google Search" |
| Reported | May 2026 (per Search Engine Land); present in Google's spam-policy docs |
| Surfaces covered | AI Overviews, AI Mode, and other AI-generated responses in Google Search |
| Not covered | Non-Google engines (ChatGPT, Perplexity, and the like set their own rules) |
| Nature | A clarification that existing spam categories apply to AI answers, not a new penalty type |

Source: Google Search spam-policy documentation; reporting by Search Engine Land, May 2026. Treat the exact wording as current as of mid-2026. Policy text is updated periodically, so re-check the source before quoting it.

## Is the June 2026 spam update the same thing?

No, and it is worth keeping the two apart. Google released a separate **June 2026 spam update**, an algorithmic update that began rolling out on **24 June 2026** and finished on **26 June 2026**, applied globally across all languages. Search Engine Land described it as feeling "a bit bigger than the March 2026 spam update."

That update is Google's periodic refresh of its anti-spam systems. Google did **not** publish any statement tying the June update specifically to AI Overviews or AI citations, so it would be an overreach to call it an "AI-spam crackdown." The durable, verifiable fact is the *policy wording* (above); the June update is context. Evidence that Google actively enforces these policies, not proof of an AI-specific action.

## Which tactics count as manipulating AI answers?

Because the policy points back to Google's existing spam categories, the tactics most relevant to AI visibility are the ones already named there. Mapped to how they show up in an AI-answer context:

| Named spam category | Google's definition (paraphrased) | How it targets AI answers |
|---|---|---|
| **Scaled content abuse** | Generating many pages mainly to manipulate rankings, not to help users | Mass-produced, thin AI-written pages made only to appear in answers |
| **Site reputation abuse** | Publishing third-party content on an established site to exploit its ranking signals | Renting a trusted domain's authority to get a promotional list or page cited |
| **Link spam** | Creating links mainly to manipulate rankings | Building links to force entity or page prominence in AI results |
| **Cloaking** | Showing users and search engines different content | Serving crawlers content the human visitor never sees |
| **Keyword stuffing** | Filling a page with keywords to manipulate rankings | Stuffing AI-target phrases and fake Q&A to bait extraction |
| **Machine-generated traffic** | Automated queries to Google, including rank-checking scrapes | Automated querying purely to game or measure AI placement |

Source: category names and definitions from Google's Search spam-policy documentation, mid-2026. The common thread is **intent to deceive or manipulate**: not the fact that a page happens to appear in an AI answer.

## Where is the line between optimising and manipulating?

The line is honesty and user value, not the act of optimising. Making content clear, well-structured, [structured-data](/glossary/structured-data)-labelled, accurate, and easy to cite is exactly what Google's own guidance asks for, that is legitimate [answer-engine optimisation](/glossary/answer-engine-optimization). Manipulation is the opposite: deceiving users or tricking Search systems into featuring content it would not feature on merit.

> Optimising means earning a place in the answer by being the clearest, most trustworthy source. Manipulating means faking that trust. Google's spam policy now says the second one is spam whether the target is a blue link or an AI answer.

Two honest caveats. First, this governs **Google's surfaces only**: AI Overviews and AI Mode, and says nothing about ChatGPT, Perplexity, or Gemini's standalone app, which each set their own rules. Second, the *principle* still travels: every major engine discounts manipulative, low-[corroboration](/glossary/corroboration) content, so a tactic banned on Google is rarely a safe bet elsewhere. The strategy that survives is the same one that survives manipulation generally. [Being the corroborated answer](/blog/can-ai-search-be-manipulated).

## What should you actually do about it?

- **Audit the aggressive tactics, not the honest ones.** If any part of your AI-visibility programme relies on scaled thin pages, rented-domain placements, or link schemes, it now sits squarely inside Google's spam definition. Retire it.
- **Keep doing the legitimate work.** Clear structure, accurate facts, real schema, and genuine expertise are safe and effective; see [how to get cited by AI](/blog/how-to-get-cited-by-ai) and [how to optimise for AI Overviews](/blog/how-to-optimize-for-ai-overviews).
- **Pursue earned placement the clean way.** Getting into the independent [best-of lists](/glossary/best-of-list) engines trust is powerful, but do it by earning inclusion, not by [site reputation abuse](/glossary/site-reputation-abuse). We cover the honest version in [getting into AI-cited best-lists](/blog/get-into-ai-cited-best-lists).
- **Build the durable lever.** [Entity strength](/blog/entity-strength-ai) and corroboration are what Google's policy *rewards* rather than punishes. The slow, compounding work no update penalises.

The reassuring read for 2026: this changes almost nothing for brands doing honest work, and closes a door on those who were not. Watching what Google's AI surfaces, and every other engine. Actually say about your brand, so you can tell legitimate visibility from a fragile, manipulated result, is exactly what **Buffy Intel** is built to measure.

## How to grow AI visibility without violating Google's spam policies
Source: https://heybuffy.com/blog/grow-ai-visibility-without-spam

Google's spam policy now explicitly covers [attempting to manipulate its AI answers](/blog/google-spam-policy-ai-answers). That does not mean optimising for AI Overviews and AI Mode is risky. It means the *manipulative* tactics were always spam and are now named as such. This is a practical, white-hat method for growing AI visibility that stays clearly on the right side of the line, with a category-by-category test you can apply to any tactic.

The whole method rests on one distinction: **optimisation earns a place in the answer by being the best source; manipulation fakes it.** Everything below is a way to stay on the earning side.

## Step 1: Apply the two-question spam test to every tactic

Before adopting any AI-visibility tactic, ask two questions. If it fails either, it is spam:

1. **Would it help a real person who landed on this page?**
2. **Would you be comfortable explaining it to Google in plain terms?**

Honest optimisation passes both easily. Manipulation fails at least one. Usually the first, because the tactic exists only to trick the engine. This mirrors Google's own framing: spam is about deceiving users or manipulating Search systems, AI answers included. Use the test as a gate on everything that follows.

## Step 2: Map your tactics against the named spam categories

Google names specific spam categories, and a handful map directly onto how people chase AI visibility. Check your programme against them:

| If you are tempted to… | It matches this spam category | Do this instead |
|---|---|---|
| Mass-produce thin pages to blanket a topic | **Scaled content abuse** | Publish fewer, deeper, genuinely useful pages |
| Publish a promotional list on a rented high-authority domain | **Site reputation abuse** | Earn inclusion in independent lists on merit |
| Stuff AI-target phrases and fake Q&A into a page | **Keyword stuffing** | Answer real questions clearly; use honest FAQs |
| Build links purely to force prominence | **Link spam** | Earn mentions by being worth citing |
| Show crawlers content users never see | **Cloaking** | Serve one honest version to everyone |
| Add fake reviews or unearned schema | **Scaled/thin content abuse** | Mark up only content you genuinely have |

Source: category names from Google's Search spam-policy documentation, mid-2026. The pattern is consistent. Every "do this instead" is simply the honest version of the same goal.

## Step 3: Handle AI-written content by purpose, not by tool

The most common worry in 2026 is whether AI-assisted content is itself a risk. It is not, on its own. Google's category is **scaled content abuse**: generating many pages *primarily to manipulate rankings*, and it applies regardless of who or what wrote them.

> Google does not penalise content for being AI-assisted. It penalises content made at scale to game the system rather than help a reader. The tool is irrelevant; the purpose and quality are everything.

So AI-drafted content that is accurate, specific, reviewed by a human, and genuinely useful is fine. What crosses the line is publishing volume for volume's sake. We go deeper on this in [does AI-generated content hurt AI visibility](/blog/does-ai-generated-content-hurt-ai-visibility). The short version is that quality and intent decide it, not the drafting method.

## Step 4: Get into best-lists the earned way

Independent [best-of lists](/glossary/best-of-list) are among the most-cited page types in AI answers, so the temptation to game them is real, and it is exactly where **site reputation abuse** lives (renting a trusted domain to place a promotional roundup). The clean alternative is earned placement: make your product genuinely list-worthy, then get reviewers and publishers to include you on the merits.

- Build a real case. Specific capabilities, evidence, differentiation, that a fair reviewer would rank.
- Reach out to legitimate independent publishers rather than paying for a slot on someone else's authority.
- Keep the coverage fresh, because recently-updated lists are cited far more (see [the freshness cliff](/blog/content-freshness-citation-cliff)).

The full playbook is in [getting into AI-cited best-lists](/blog/get-into-ai-cited-best-lists), and it is deliberately all earned-placement. No rented authority.

## Step 5: Invest in the lever no update can penalise

The safest and strongest lever is [entity strength](/blog/entity-strength-ai) built through [corroboration](/glossary/corroboration): publish genuinely useful, specific work, and earn independent sources that agree with it. Because it works by *earning* trust rather than faking it, no spam update touches it. It is precisely what the policies reward.

- **Be corroborated, not just loud.** One self-serving claim is fragile; the same fact echoed across reviews, press, and communities is durable. Including in places like [Reddit](/blog/how-to-use-reddit-for-ai-search-visibility).
- **Be consistent across the web.** Matching names, facts, and positioning strengthen your entity; contradictions read as untrustworthy.
- **Structure honestly.** Clean semantic HTML, real [structured data](/glossary/structured-data) for content you actually have, and answer-first writing help engines lift your facts. Legitimately.

## Step 6: Measure so you can prove it is working honestly

White-hat visibility compounds slowly, so measure it as a trend rather than expecting an overnight jump. Track your AI citations and AI-referred traffic across engines over several weeks, and watch for the durable signal. Being [cited and recommended](/blog/cited-vs-recommended-in-ai-search) more often as your corroboration grows.

This also gives you an early warning: if a tactic ever produced a sudden, fragile spike, a smoothed trend line will show it collapsing. The signature of something the engines discounted. Watching what every AI engine says about your brand over time, so you can grow visibility on the durable, policy-safe side of the line, is exactly what **Buffy Intel** is built to measure.

## The Hinglish language trap: why Indian shoppers ask in Hinglish but AI cites English
Source: https://heybuffy.com/blog/hinglish-language-trap-indian-d2c

Indian shoppers ask AI engines questions in **Hinglish**: Hindi-English code-mixing, usually typed in the Latin alphabet, and in romanised vernacular. The engines understand them fine. The catch is what happens next: the answer gets assembled from **English-language sources**, because that is where the authoritative, crawlable, structured commerce content sits. The shopper's language and the cited sources' language diverge, and that gap quietly decides which Indian D2C brands get recommended.

This extends [AI shopping in India](/blog/ai-shopping-in-india), which covers the source mix and price-band logic; here we go deep on the single point that trips brands up most. The language mismatch between question and citation.

## What exactly is the Hinglish trap?

It is a mismatch between the language of the **prompt** and the language of the **sources**. Two things are simultaneously true as of mid-2026:

- **Comprehension is not the problem.** Multilingual models read Hinglish and romanised vernacular and infer intent well. "Best sunscreen for oily skin under 500 rupees, koi acha brand bata do" is understood.
- **Citation is the problem.** When the engine fans the question out and retrieves sources, the crawlable, structured, review-rich commerce content it pulls from skews heavily English. Marketplace listings, English reviewers, "best under ₹X" roundups written in English.

So the engine understands the buyer in Hinglish and answers them from English. Your visibility depends on being in that English source pool, phrased to match the *intent* the Hinglish carried, not on having translated your page.

## Why do engines cite English even when asked in Hinglish?

Because retrieval favours the language with the deepest, best-structured, most-corroborated web content, and for Indian commerce, that is still English. A few reasons compound:

1. **The crawlable commerce web in India skews English.** Product pages, specs, structured data, and the big marketplaces present their citable, machine-legible detail predominantly in English.
2. **Authority and corroboration cluster in English.** The reviewer sites, tech press, and roundups engines lean on for commercial queries are largely English, so the [corroboration](/glossary/corroboration) signal is strongest there.
3. **Code-mixed and transliterated content is sparse and messy.** Genuine Hinglish is inconsistent to spell and rarely carries clean [structured data](/glossary/structured-data), so even when it exists it is harder to retrieve and trust.

The practical upshot: the [query fan-out](/glossary/query-fan-out) starts in Hinglish and resolves into English sub-queries against an English source pool. You compete in English regardless of the language the shopper typed.

> The engine understands your customer's Hinglish perfectly. It just answers them out of English sources. If your English content doesn't mirror how the Hinglish question was actually asked, you're absent from an answer the shopper got in their own language.

## How do you write for both sides of the gap?

Build the **citable layer in clear English**, but shape it around the **real intent** the Hinglish carries. The occasion, the band, the use-case, the objection. Translation is not the move; mirroring intent is.

| What the shopper does | What loses the citation | What wins it |
|---|---|---|
| Asks in Hinglish ("acha laptop under 50k") | A generic English spec sheet | English content built around the ₹ band and the real use-case |
| Anchors to an occasion ("Diwali gift for mom") | No occasion language anywhere on-page | Plain-English occasion and use-case framing in crawlable text |
| Raises a trust objection ("genuine hai na?") | Trust answers buried or absent | "Genuine, 1-year India warranty" stated as text |
| Uses Indian framing ("for Indian skin/voltage") | Global copy with no India context | Explicit India context in the English copy |

The pattern: keep the machine-legible facts in simple English so they get retrieved and [cited](/glossary/citation), but make that English reflect how Indian shoppers actually phrase the need. That is also why earned placement in India-focused, English-language roundups matters. [AI engines lean on independent roundups](/blog/why-ai-loves-listicles), and in India those are organised by price band and occasion.

## Should you publish in Hindi and vernacular at all?

Yes, for reach, brand familiarity, and the queries that genuinely resolve in-language, but don't expect a translated page alone to earn the citation if the English evidence isn't there too. As of mid-2026, the dependable [citable](/blog/how-to-get-cited-by-ai) layer for Indian shopping answers is English, so lead there. Treat vernacular content as a complement that builds presence and serves in-language reading, not as a substitute for the English facts engines retrieve. For categories where an India SKU differs from the global one, the [model-number and entity hygiene rules](/blog/ai-visibility-for-electronics-brands) apply in both languages.

## What to do next

List ten real buying questions for your category the way an Indian shopper would actually type them. Hinglish, romanised, band and occasion included. Ask each engine, in that exact phrasing. Note the language of the answer and the language of the sources it cited, and whether your brand appears. You will almost always find the question came in Hinglish and the citations came back English, and the gap between them is your work list: English content, mirroring Hinglish intent, in crawlable text. Watching that gap close across engines, [answer by answer](/blog/from-clicks-to-citations) and over time, is what **Buffy Intel** is built for. Tracking AI visibility from India, for the way India actually shops. Questions: support@flash.tech.

## How AI engines decide which brands to recommend
Source: https://heybuffy.com/blog/how-ai-engines-choose-brands

In the [first article](/blog/what-is-geo-aeo) we covered *what* GEO and AEO are. This one answers the question every brand asks next: **how does an AI actually decide who to mention, and can I influence it?**

The short answer: yes, because AI answers are assembled from three inputs, and two of them are squarely in your control.

## The three inputs behind every AI answer

### 1. Training data: what the model already "knows"

When a model is trained, it absorbs a vast snapshot of the web: articles, forums, reviews, retailer pages, your own site. This becomes the model's background knowledge about your category and brand. It's powerful but **slow and lagging**: it reflects how the web described you months or years ago, and you can't edit it directly. What you *can* do is shape the web it learns from next: the more consistently and clearly your brand is described across the open web, the stronger and more accurate that background knowledge becomes.

### 2. Live retrieval: what the engine fetches right now

This is the big shift. ChatGPT search, Gemini, Perplexity, and Google's AI surfaces increasingly **fetch live pages at the moment you ask**, then write an answer [grounded](/glossary/grounding) in what they just read, and cite their sources. This is the fastest lever you have: a well-structured, authoritative page can be retrieved and cited *today*, without waiting for the next training cycle. Most "how do I get cited by AI" wins live here.

### 3. Your site's structure: what the engine can actually parse

Retrieval only helps if the engine can *read* your page. Engines (and the crawlers that feed them) parse the underlying HTML, not the pretty pixels. If your key facts live in clean, semantic markup and accurate [structured data](/glossary/structured-data), they're easy to extract and quote. If they're trapped in JavaScript widgets, images, or non-semantic `<div>` soup, they may as well not exist.

## What engines reward

Across all three inputs, the same qualities keep winning:

- **Clarity**: direct, factual answers to real questions, not marketing fog.
- **Structure**: semantic HTML, headings, lists, and schema.org data that label what things *are* (a product, a price, an FAQ, an organization).
- **Authority & consistency**: the same facts about your brand, repeated consistently across your site, retailers, reviews, and the broader web.
- **Freshness**: recently updated, accurate pages beat stale ones for live retrieval.
- **Extractability**: content an engine can lift a clean sentence or fact from without guessing.

## Why the engines disagree about you

Because each engine weighs these inputs differently. One leans harder on live retrieval; another leans on training knowledge; another grounds heavily in a specific index. So the same brand can be the top recommendation in one engine and unmentioned in another. **This is why single-engine spot checks mislead**: you have to look across ChatGPT, Gemini, Claude, and Google's AI surfaces together to see the real picture.

> The same brand can be the top recommendation in one engine and unmentioned in another, which is why single-engine spot checks mislead.

## Turning this into action

Put the three inputs together and a clear order of operations emerges:

1. **Fix what engines can parse**: semantic structure and accurate schema, so your facts are extractable. (This is also exactly what a site-readiness audit measures.)
2. **Earn live retrieval**: authoritative, well-structured pages that directly answer the questions customers actually ask.
3. **Shape the broader web**: consistent, accurate descriptions of your brand everywhere it appears, so the next training cycle gets you right.
4. **Measure across engines, over time**: so you know whether any of it is moving the needle.

That last step is the one teams skip, and it's where Buffy Intel lives: tracking how every major engine describes and recommends your brand, every day, and turning the gaps into a prioritized [action plan](/glossary/action-plan).

## How Brave Search discovers your pages, and why it decides whether Claude can cite you
Source: https://heybuffy.com/blog/how-brave-search-discovers-pages

Brave Search builds its index from anonymous signals contributed by opted-in Brave browsers, **not from anything you submit**. There is no search console, no sitemap intake, and no IndexNow. A page enters Brave's index either when **about 20 opted-in users visit it**, or when **one opted-in user sees it rank** on Google, Bing, Yahoo, or DuckDuckGo. Because Claude's live web search appears to lean on Brave's independent index, whether Brave has discovered your page increasingly decides whether Claude can cite you at all. This is part of the crawlers-and-technical series.

The mechanics below come from **Merj's mid-2026 deep dive**, which read the open-source [Web Discovery Project](/glossary/web-discovery-project) (WDP) client line by line, corroborated against Brave's own published documentation. Treat the exact thresholds as one consultancy's careful reading of open-source code. Directionally reliable, not a Brave spec sheet.

## Why does Brave's index matter for AI visibility?

Because it is the discovery layer underneath Claude. As covered in [how to get cited in Claude](/blog/how-to-get-cited-in-claude), independent evidence points to Claude's live search being powered by Brave's index. Anthropic listed Brave Search as a subprocessor in March 2025, and Google Cloud's documentation describes Brave Search as the third-party service behind Claude's web search tool.

The citation overlap is the striking part:

- [Profound](/blog/ai-search-statistics-2026) reported in **June 2026** that **79.2% of Claude's citations sat in Brave's top-ten results** for the same query, versus **34% for Google's own top ten**: across roughly 35,000 citations over about 400 queries.
- That makes Brave discovery a precondition for Claude citation: a page Brave has never indexed is one Claude's search is unlikely to reach, no matter how well it ranks on Google.

Why care now? Because Claude is where business buyers are heading. **Ramp's AI Index** (April 2026 data, published 13 May 2026, tracking spending across 50,000+ U.S. businesses) showed **Anthropic overtaking OpenAI in business adoption for the first time. 34.4% of businesses versus 32.3%**, up from under 8% a year earlier. Ramp's figures measure paid business usage, not consumer share, and single-source spending data is directional, but the direction is clear enough that Claude's plumbing now matters commercially.

> Whether Brave has discovered your page increasingly decides whether Claude can cite you at all. And unlike Google, you cannot submit your way in. You have to be found.

## How does a page get into Brave's index?

Through two channels with very different bars, per Merj's reading of the WDP client. Neither involves submitting a URL.

| Channel | What triggers it | The bar | Best read as |
|---|---|---|---|
| **Page channel** (the hard door) | Opted-in users visit your URL directly | ~20 different users on different networks before Brave can decrypt the URL | A strong quality signal |
| **Query channel** (the easy door) | One opted-in user views a results page where you rank | A single search on Google, Bing, Yahoo, or DuckDuckGo | The lowest-friction path in |

The important takeaway: **classic search visibility seeds Brave visibility**, which seeds Claude's. If you already rank on a mainstream engine, an opted-in Brave user searching that term is enough to hand your URL to Brave. Being reachable on the open web is upstream of everything else.

## What is the page channel (the hard door)?

The page channel discovers URLs that enough real people visit. Its privacy design is why the bar is high. Per Merj. Corroborated by Brave's own [STAR](https://brave.com/privacy-updates/19-star/) writeup. Each visited URL is encrypted with **STAR secret sharing** (a scheme based on Shamir's Secret Sharing) before it leaves the browser. Brave's servers **cannot recover the URL until roughly 20 distinct users have reported the same page**; below that threshold, decryption is mathematically impossible.

Two anti-gaming details matter:

- **Network deduplication.** Reports are deduplicated by the last octet of the user's IP address, so an office full of people on one network counts as roughly one voice. You cannot manufacture a quorum from a single location.
- **Exemptions.** Bare homepages and pages a user reached by clicking a Brave Search result are exempt from the full quorum. The system already has reason to trust those.

For most brands, the page channel is not the practical lever: gathering 20 independent Brave users on distinct networks is not something you can engineer. The query channel is.

## What is the query channel (the easy door)?

The query channel is where a single search puts your URL in front of Brave. Opted-in Brave browsers ship recognisers for **Google, Bing, Yahoo, and DuckDuckGo** results pages. Per Merj's analysis, when an opted-in user searches on one of those engines, their browser waits a **random 1-20 minute delay**, anonymously re-fetches the same results page with no cookies or identity, and reports the listed URLs. Provided **at least four clean results survive sanitisation**. There is no quorum: one user, one search, and a URL that ranks can reach Brave.

A server-side pattern file (cryptographically signed, polled hourly) controls which engines are harvested. Brave can switch a source on or off without shipping new code. The practical implication is durable regardless of that file's exact state:

- If you **rank on any mainstream engine**, you are already discoverable by Brave through the query channel.
- If you rank **nowhere**, the page channel's ~20-user bar is your only remaining route. A much harder path.

This is why classic [answer-engine and search fundamentals](/glossary/answer-engine-optimization) still underpin AI visibility: they are what feed Brave, and Brave is what feeds Claude.

## What can silently keep your page out of Brave?

Even a visited page must survive a verification fetch with strict, testable edges before it qualifies. Per Merj, these are the filters that quietly disqualify pages:

| Filter | Rule (per Merj's WDP reading) | Why it bites |
|---|---|---|
| **JavaScript** | The verification fetch reads raw HTML off the wire and does not execute JavaScript | Client-side-rendered content is invisible to discovery |
| **noindex / canonical** | Honoured only inside the HTML `<head>`; the `X-Robots-Tag` and `Link` HTTP headers are ignored | Header-only directives are neither obeyed nor read |
| **Redirects** | Any redirect makes the URL ineligible. It must return 200 at the exact URL | A "helpful" redirect can drop you from discovery |
| **Size and time** | Responses over ~2 MB or slower than ~10 seconds are refused | Heavy, slow pages fail the fetch |
| **URL cleanliness** | Long query strings, many parameters, and risky path words (`login`, `checkout`, `admin`) are rejected | Parameterised URLs may never qualify |

Then there is the crawler that fills gaps. Brave's own crawler, per its documentation, is **gated on Googlebot-crawlability**: "if a domain or page is not crawlable by Googlebot, then Brave Search's bot will not crawl it either", and it deliberately **sends no distinctive user agent**, to avoid being treated differently from Google. The unintended consequence, which Merj highlights: a **"block all unknown bots" rule silently cuts Brave off**, because Brave does not announce itself the way [named AI crawlers](/blog/ai-crawler-user-agent-directory) do. This connects directly to whether your [CDN is blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers). A default-deny bot rule can quietly remove you from Claude's reachable web without any error you would notice.

## What should you do about it?

The levers are unglamorous and mostly things good technical [GEO](/glossary/generative-engine-optimization) already covers. Sharpened by how Brave behaves:

1. **Rank somewhere mainstream.** Google, Bing, Yahoo, or DuckDuckGo visibility is the query channel's fuel. This is the single highest-leverage move.
2. **Serve server-rendered HTML.** Because the fetch [does not execute JavaScript](/blog/do-ai-assistants-render-javascript), critical content and facts must be in the raw HTML.
3. **Put directives in the `<head>`.** If a page should be indexable, keep `noindex` out of the HTML and canonical tags accurate in the markup. Header-only signals are ignored.
4. **Don't default-block unknown bots.** Confirm your [CDN and robots rules](/blog/should-you-let-ai-crawlers-index-your-site) don't silently exclude a crawler that sends no special user agent.
5. **Keep URLs clean.** Short paths, few parameters, no redirects on the pages you want discovered.

None of this is submission. Brave has no front door. It is being reachable and rank-worthy so the network of opted-in browsers finds you on your behalf.

Brave discovery is one link in a longer chain. Reachable, then discovered, then retrieved, then quoted, and Claude is one engine among several, each with its own plumbing. The work is to be discoverable and extractable across all of them, then measure where you actually appear. Tracking your citation share across Claude, ChatGPT, Perplexity, and Google's AI surfaces, sampled over time, is exactly what **Buffy Intel** does.

## How does ChatGPT pick which sources to cite?
Source: https://heybuffy.com/blog/how-chatgpt-picks-sources

ChatGPT picks sources in three stages. First it sorts your question into a **use-case bucket** that decides whether it searches the web at all. If it does search, it pulls pages through one of **four retrieval pipelines**. Then it cites only the pages it can **read cleanly and that directly answer the question**: not simply the highest-authority domain. The practical upshot: plain, server-rendered HTML that answers the question wins the citation.

The clearest recent window into this came in June 2026, when SEO consultant **Suganthan Mohanadasan** inspected the raw network traffic of his own ChatGPT Pro account and published the internal labels he found. This piece summarises what that teardown revealed and what to do about it. It is a companion to the data piece on [why AI share-of-voice scores are volatile](/blog/ai-share-of-voice-volatility), and a different lens than [where ChatGPT's product recommendations come from](/blog/where-chatgpt-product-recommendations-come-from), which looks at ranking rather than the retrieval plumbing.

**A note on confidence.** This is one practitioner's reading of about 1,240 source records from a single Pro account over several days. A small, tech-skewed sample. The author himself separates **high-confidence structural facts** (the internal field names and pipeline labels exist) from **directional frequencies** (the exact percentages). Internal labels can change without notice. Treat the structure as informative and the numbers as indicative.

## How does ChatGPT decide whether to search the web at all?

Before anything else, ChatGPT classifies the question into a use-case bucket. Exposed internally as a `turn_use_case` field. The teardown identified six: **instant search, shopping, text, local, thinking, and image generation**. The decisive one for visibility is **text**: those questions are answered from the model's training data with **no live web search**, so no page can be cited no matter how well optimised it is.

In the author's small test, **3 of 10 deliberately current queries received no web search**: the model judged it could answer from memory. The lesson is upstream of everything else: you can only be cited on questions that actually trigger retrieval, which tends to mean specific, current, or comparative phrasing rather than general-knowledge questions.

## Where does ChatGPT pull its sources from?

When a question does trigger a search, the teardown found results arriving through one of four pipelines, labelled in a `result_source` field. Each leans toward a different kind of content:

| Pipeline | What it provides | Tends to dominate |
|---|---|---|
| **SERP** | Open-web baseline | News and general results |
| **Labrador** | Allowlisted premium publishers (e.g. Reuters, WSJ, Guardian, Wikipedia) | High-trust reference and news |
| **Bright** | A commercial scraper (Bright Data) | Shopping and finance queries |
| **Oxylabs** | A commercial scraper (Oxylabs) | Regional and local content |

Source: Suganthan Mohanadasan's network-traffic analysis (2026), single account. A weather query, for example, split across pipelines. Global sites (Met Office, AccuWeather) via one scraper and regional Gulf press (Khaleej Times, Gulf News) via another. The existence of a `result_source` field independently echoes an earlier point-in-time observation noted in our [product-recommendations teardown](/blog/where-chatgpt-product-recommendations-come-from), so two observers have now seen similar internal plumbing, though neither is officially confirmed by OpenAI.

## What is the difference between fetched, cited, and mentioned?

They are three separate outcomes, and conflating them is the most common mistake. A page can be:

- **Fetched**: pulled into the model's context to inform the answer, invisible to the user.
- **Cited**: shown as a footnoted source the user can click.
- **Mentioned**: your brand name appears in the answer, but a *different* page is the cited source.

The gap between fetched and cited is large. The teardown counted **Reddit fetched ~278 times but cited only 11**, and **YouTube fetched ~201 times and cited zero**. The model read them for context, then footnoted something more cleanly extractable. This matches independent data: Ahrefs' analysis of 1.4 million prompts found Reddit cited in about **1.93%** of answers versus YouTube's **0.51%**, and the [Reddit-for-AI-visibility](/blog/how-to-use-reddit-for-ai-search-visibility) play works precisely because Reddit is fetched constantly. The takeaway: being read is not being [cited](/glossary/citation), and being mentioned is not being the source. Aim to be the clean page the model can footnote.

## How does ChatGPT expand one question into many?

For complex, comparative questions, the **thinking** bucket spawns many sub-queries from a single prompt. The teardown saw **15-40** for hard comparison tasks, including literal `site:` domain probes and price-verification searches with guessed values. This is [query fan-out](/glossary/query-fan-out) in action: the single question you see becomes a tree of retrievals behind the scenes, each pulling its own sources. (The mechanics across engines are covered in [how query fan-out works](/blog/how-query-fan-out-works).) Practically, it means one answer can cite several different pages, so covering the *branches* of a question, not just the headline, gives you more chances to be the source for one of them.

## What stops a page from being cited?

Content the model cannot cleanly read. The most concrete finding: ChatGPT **abandoned parsing a pricing table that loaded via JavaScript** and cited a third-party site (like G2) for the numbers instead. The chain-of-thought reasoning showed it giving up on the JS-rendered page and routing to whatever exposed the fact in plain text.

That single behaviour explains a category of invisibility. Facts locked in JavaScript, PDFs, or images are effectively absent at citation time. The engine cites whoever published them as readable text. This is the same lesson as [whether AI assistants render JavaScript](/blog/do-ai-assistants-render-javascript) and why [accessibility and AI-parseability are the same discipline](/blog/accessibility-and-ai-parseability): if a human screen reader or a scraper can't get the fact as text, neither can the model.

> The page that gets cited isn't the most authoritative one. It's the one that states the fact in clean, server-rendered text the model can lift without a fight.

## How do you become the page ChatGPT picks?

The teardown points to a short, durable checklist. None of it dependent on the exact internal labels holding:

- **Be cleanly scrapable.** Put every citable fact. Prices, specs, definitions, comparisons. In server-rendered plain HTML text, never only in JavaScript, PDFs, or images. Check that your [CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers) before anything else.
- **One strong page per claim.** A single, complete page on a topic outperforms several thin ones competing for the same fact.
- **Own your own facts; earn the recommendations.** Vendor pages get cited for their own pricing and specs; *recommendations* are sourced from third parties, so publish your facts cleanly and pursue third-party presence (reviews, Reddit, listicles) for the recommendation, as in [how to get cited by AI](/blog/how-to-get-cited-by-ai).
- **Answer specific, current, comparative questions.** Those are the queries that trigger retrieval in the first place; general-knowledge phrasing may never leave the model's training data.

The honest frame: this is one well-documented snapshot of an opaque system that OpenAI can change at any time, so anchor on the durable mechanic. **Clean, extractable, server-rendered facts get cited**: and don't over-fit to the internal field names.

Knowing whether ChatGPT is actually fetching, citing, *and* recommending your pages. Across the prompts your buyers use. Is exactly what **Buffy Intel** measures, engine by engine, over time.

## How Claude web search works (and what it means for getting cited)
Source: https://heybuffy.com/blog/how-claude-web-search-works

Yes. Claude can search the live web. Anthropic introduced a **web search tool on the Claude API in September 2025**, letting Claude pull current information from beyond its training cutoff, then answer with **citations to the sources it used**. For brands, the mechanics matter: Claude's citations are always on and quote a short slice of your page, so being the source it lifts is a concrete, winnable target.

## What is Claude web search?

Claude web search is a tool that gives Anthropic's AI assistant direct access to real-time web content. Before it existed, Claude could only answer from its training data, bounded by a [knowledge cutoff](/glossary/knowledge-cutoff). With the tool enabled, Claude can fetch current information and [ground](/glossary/grounding) its response in live sources, and, per Anthropic's documentation, **every web search response includes citations** to the pages it drew from.

It pairs with Anthropic's Citations feature (launched June 2025), which lets Claude reference the exact sentences and passages behind an answer. The combined effect: answers that are verifiable and linked back to their sources, rather than unattributed synthesis.

## How does Claude decide when to search?

Claude doesn't search on every turn. According to Anthropic's docs, it reasons about whether a question needs fresh information first.

| Claude tends to search | Claude tends to answer directly |
|---|---|
| Recent events, news, announcements | Established facts, math, science fundamentals |
| Current prices, rates, scores, statistics | Coding concepts and stable how-tos |
| Specific organisations, people, or products that may have changed | Content already provided in the conversation |
| Explicit "search for…" or "look up…" requests | Greetings and creative writing |

So the queries that put your pages in play are the **current, changing, entity-specific** ones. Exactly the questions buyers ask before choosing a product. If your category, pricing, or availability information is stale or unreachable, you're absent from the moment Claude reaches for the live web.

## How do Claude's citations actually work?

This is the part brands should optimise around. When Claude searches, the response carries structured citation data for each source it uses:

- **`url` and `title`**: the page Claude is crediting.
- **`cited_text`**: up to about **150 characters** of the exact text Claude pulled from your page.
- **`page_age`**: a freshness signal indicating when the source was last updated.

Two implications follow directly. First, **freshness is a ranked input**: the system tracks how old a page is, which echoes the broader [content-freshness citation cliff](/blog/content-freshness-citation-cliff). Second, because the quoted snippet is short, a **clean, self-contained, factual sentence is far more liftable** than the same fact diffused across a paragraph. The 150-character window rewards [extractable](/blog/how-to-get-cited-by-ai) writing.

> Claude's citations quote roughly 150 characters of your page, verbatim. Write the sentence you want quoted: specific, numeric where possible, and able to stand on its own.

## What controls do developers have over the search?

The tool is configurable, which shapes what gets retrieved:

- **`max_uses`** caps how many searches Claude performs per request. Simple questions use a few, research-style tasks can use ten or more.
- **`allowed_domains` / `blocked_domains`** restrict or exclude sources, so an application can confine Claude to trusted domains.
- **`user_location`** localises results, the same way [conversational-search](/glossary/conversational-search) engines tailor answers by place. Relevant if you compete in specific markets.
- Newer tool versions add **dynamic filtering**, where Claude writes code to discard irrelevant results before they reach its context, improving accuracy and cutting tokens.

Web search is priced at **$10 per 1,000 searches** on the Claude API, plus standard token costs. A reminder that engines spend real money to fetch, so easy-to-parse pages are cheaper to use and likelier to be kept.

## How do you get cited by Claude?

The levers are the same GEO fundamentals, sharpened by how this tool behaves:

1. **Be reachable.** Claude can only cite a page its search can fetch and render. Serve crawlable, server-rendered HTML and confirm your [CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers).
2. **Be fresh.** Because `page_age` is exposed, keep competitive pages substantively updated, not date-bumped.
3. **Be extractable.** Write answer-first, self-contained chunks; put the quotable fact in one clean sentence that fits the ~150-character citation window.
4. **Be corroborated.** Like other engines, Claude leans on sources that agree with the wider web. Consistent entity facts and third-party mentions make you safer to quote.

Claude is one engine among several, and each cites differently, so the work is to be the reachable, fresh, extractable, corroborated source across all of them, then measure where you actually appear. Tracking your citation share across Claude, ChatGPT, Perplexity, and Google's AI surfaces, sampled over time, is exactly what **Buffy Intel** does.

## How Google AI Mode works
Source: https://heybuffy.com/blog/how-google-ai-mode-works

[Google AI Mode](/glossary/google-ai-mode) is Google's full conversational search experience: a Gemini-powered chat where you ask, follow up, and refine, and get a synthesised, cited answer, not a page of links. Where an [AI Overview](/blog/ai-overviews-complete-guide) is a *summary block* on the results page, AI Mode is a *destination chat* for deeper research.

## How it works

- **Gemini-powered, index-grounded.** AI Mode generates answers with Gemini but grounds them in Google's existing search index, so, like Overviews, classic search authority carries over.
- **Heavy [query fan-out](/blog/how-query-fan-out-works).** It decomposes a question into many sub-queries, runs them in parallel, and synthesises, and because it's conversational, it does this repeatedly across follow-ups, going deeper each turn.
- **Multi-turn intent.** A single session can move from "best vitamin C serum for sensitive skin" to "will it cause purging?" to "how do I pair it with retinol?". Each turn fanning out again.
- **It cites.** Like other AI surfaces, it links sources, which is the [citation](/glossary/citation) you're competing for.

## What it means for brands

The fundamentals are the same as for Overviews. Be indexable, structured, authoritative, fresh, but AI Mode raises the premium on **intent depth**. Because users go several turns deep, the brands that win are the ones whose content covers not just the headline question but the **follow-ups**: the comparisons, the how-tos, the objections.

> AI Mode rewards coverage over a single page. If your content answers the first question but none of the natural follow-ups, you're cited in turn one and absent by turn three.

That's the [intent-hub](/blog/how-query-fan-out-works) model in action: interlinked content that answers a topic's whole conversation, not one query. The same structured, authoritative, well-linked content that wins Search and Overviews compounds here.

## How to think about measuring it

AI Mode answers shift by conversation context, user, and over time. Even more than Overviews. So a one-off check tells you little; what matters is presence and citation across the **questions and follow-ups** that make up your category's AI conversation, tracked over time. That cross-engine, multi-prompt read is what **Buffy Intel** is built for.

## How long do AI citations last? The six-week turnover data
Source: https://heybuffy.com/blog/how-long-do-ai-citations-last

**AI citations turn over fast: in a 2026 study of 1,127 cited URLs, only about 10.6% were still being cited six weeks later.** Digital Authority Partners tracked those URLs across ChatGPT, Perplexity, Gemini, Microsoft Copilot and Google [AI Overviews](/glossary/ai-overviews) in three waves, 28 days apart, and just 119 of them appeared in all three. The other ~89% rotated out at least once. A [citation](/glossary/citation) is a position you defend over weeks, not a win you bank once.

**Last reviewed: 15 August 2026.** All figures below come from Digital Authority Partners' *2026 AI Visibility Study* (published 1 July 2026), a single-vendor, single-period read. It is directional, not definitive, so cite "Digital Authority Partners, 2026" with the date when you reuse a number, and treat the *direction* as firmer than any one percentage.

## How long does an AI citation actually last?

On this data, a matter of weeks. Across the full six-week window, the study found only **10.6% of cited URLs (119 of 1,127) persisted across all three sampling waves**. The commentary around the study coined a useful frame for it: AI citations have a short **half-life** — the pool of sources an engine leans on is mostly replaced within about a month, whether or not the underlying pages change.

This is a different failure mode from a page slowly aging out. It is the whole *population* of cited sources reshuffling. The study reports that **roughly 40-60% of cited sources rotate every month**, and that between the first and last wave the two waves shared only about **20% of their URLs** (Wave 1 surfaced 530 unique URLs, Wave 3 surfaced 546). Nearly a quarter of the query-and-engine pairs tested saw *complete* turnover — zero overlap between the first and last wave.

## What exactly did the six-week study measure?

A longitudinal panel of AI citations, not a one-time snapshot. The design is what makes it useful: instead of asking "who gets cited" once, it asked the same questions three times over six weeks and watched which cited URLs survived.

| Attribute | Detail |
|---|---|
| Unique URLs tracked | **1,127** |
| Engines | ChatGPT, Perplexity, Gemini, Microsoft Copilot, Google AI Overviews |
| Sampling | **3 waves**, ~28 days apart, over **6 weeks** |
| Persisted across all 3 waves | **119 URLs (~10.6%)** |
| Monthly source rotation | **~40-60%** |
| Wave 1 ↔ Wave 3 URL overlap | **~20%** |
| Publisher / date | Digital Authority Partners, 1 July 2026 |

Source: Digital Authority Partners, *2026 AI Visibility Study*. The one-line read: **the set of pages an AI engine cites is mostly not the same set a month later.** Because it is one vendor measuring one window, read the magnitudes as directional; the pattern of heavy churn is what carries.

## Which engines hold their citations longest?

Retention varied widely by engine — from about 11% to 44% over four weeks. The more an engine leans on live retrieval and recency, the faster its cited set churned.

| Engine | 4-week citation retention |
|---|---|
| **Perplexity** | ~44% (most stable) |
| **Microsoft Copilot** | ~34% |
| **ChatGPT** | ~31% |
| **Google AI Overviews** | ~27% |
| **Gemini** | ~11% (most volatile) |

Source: Digital Authority Partners, 2026. Even the most stable engine, Perplexity, dropped well over half its cited URLs in four weeks. The takeaway is not "optimize for Perplexity because it is stable" — it is that **no engine treats a citation as durable**, so any single-engine, single-snapshot reading of your visibility is unreliable. This mirrors the low cross-engine overlap the same study found (78-85% of cited domains were unique to a single platform), which is consistent with our read that [engines cite largely different pages](/blog/ai-citation-fingerprint-by-industry).

## Why do AI citations churn so fast?

Three mechanisms stack, and together they explain a ~90% monthly turnover. None of them require your page to get worse.

- **Answers are probabilistic.** Ask an engine the same question twice and it samples a slightly different response, so the cited set moves on its own. This is [answer volatility](/glossary/answer-volatility), quantified separately: an identical question asked repeatedly in a single day returned the same brand set only 50-61% of the time. See [why your AI share of voice swings week to week](/blog/ai-share-of-voice-volatility).
- **Retrieval favours fresh pages.** Live [retrieval](/blog/how-chatgpt-picks-sources) pulls recently-updated content, so a page cited today can be displaced by a fresher competitor tomorrow — the [3-month citation cliff](/blog/content-freshness-citation-cliff) acting on the whole field, not just your one page.
- **The web underneath keeps changing.** New pages get published, others get updated, and the index the engine draws from shifts continuously, so the candidate pool itself turns over.

Within-day volatility, freshness decay and an ever-changing index compound. A citation you earned in one wave has to survive all three pressures to still be there a month later — and on this evidence, most do not.

> An AI citation is not a trophy you win and keep. It is a position you hold for a few weeks against a cited pool that is ~90% replaced within a month. Presence in AI answers is defended, not banked.

## Does this contradict our freshness and volatility pieces?

No — it is the third leg of the same stool, and it sharpens the other two rather than fighting them. It is worth stating plainly so the corpus stays consistent.

- **Answer volatility** describes *one moment*: the same prompt returns a different answer each time it is asked. That is the within-request noise.
- **The freshness cliff** describes *one page*: your content loses citations as it ages relative to fresher rivals. That is the decay of a single asset.
- **Citation turnover** — this piece — describes *the whole cited pool over time*: aggregate across many prompts and weeks, and about 90% of the sources rotate monthly. It is what you get when within-moment volatility and per-page decay compound across the field.

All three point to the same operating conclusion: read your AI visibility as a smoothed trend across many prompts and engines, and keep re-earning the citations you care about. None asserts a fixed number the others deny.

## What should you do about citation turnover?

Treat citation as a maintained position, and measure it as a distribution — not a one-off win. Concretely:

- **Know which pages are cited now.** You cannot defend a position you cannot see. Track [citation coverage](/glossary/citation-coverage) per engine so you know what to protect before it rotates out.
- **Put your highest-value cited pages on a refresh cadence.** Because freshness is one of the churn drivers, substantively updating (not date-bumping) the pages tied to buyer queries is how you re-win the citation, per the [freshness playbook](/blog/content-freshness-citation-cliff).
- **Don't rely on one cited URL.** With 40-60% monthly rotation, breadth is insurance: earn citations across several strong pages so losing one wave does not zero out your presence.
- **Sample many prompts, repeatedly, across every engine.** A single snapshot of a handful of prompts will read the noise, not the signal. Average across a large prompt set and watch the trend, the method behind [measuring AI visibility](/blog/how-to-measure-ai-visibility) and the reason [share of voice](/glossary/share-of-voice) is read as a distribution.

The number that matters is not whether you were cited in one snapshot — it is whether your [share of voice](/glossary/share-of-voice) holds up as the cited pool churns beneath it, measured across engines and over time. Continuously tracking which of your pages are cited, on which engines, and when they slip is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## How many pages does each AI bot crawl per visitor it sends? (crawl-to-refer ratios, mid-2026)
Source: https://heybuffy.com/blog/how-many-pages-ai-crawlers-take-per-visitor

**AI crawlers take far more than they give back, and the exact gap is now measurable per operator.** Over the 28-day window ending 21 July 2026, Cloudflare Radar data shows Anthropic's ClaudeBot crawled roughly **2,237 pages for every visitor it referred**, OpenAI's GPTBot about **217**, and Google about **4.6**. That number, the crawl-to-refer ratio, is the cleanest single measure of how differently AI operators and classic search engines treat your site.

This is a dated reference, not a new dataset. **Last reviewed: 28 July 2026.** The headline figures come from **Cloudflare Radar**'s bot-and-crawler analytics for the 28-day window ending 21 July 2026, as compiled by SEOmator, and are cross-checked against SEOmator's own panel of 500+ B2B sites (January–July 2026). Every figure is a verified-bot, network-wide average that varies by site type, so read the *direction* as firmer than any single decimal, and cite "Cloudflare Radar, window ending 21 July 2026" when you reuse one. It sits alongside our [AI crawler share leaderboard](/blog/ai-crawler-market-share-2026) and our [where-AI-crawls-vs-where-it-sends-visitors](/blog/ai-crawl-vs-referral-traffic) explainer.

## What is the crawl-to-refer ratio?

The crawl-to-refer ratio is the number of pages an operator's [AI crawler](/glossary/ai-crawler) fetches for every visitor its assistant refers back to a site. Divide total crawl requests by total referral sessions over the same window and you have it. A ratio of 217:1 means the bot fetched about 217 pages for each click it sent. It is a single number that captures a structural fact: AI operators crawl to *learn*, and only some of that learning ever turns into a visit.

The metric matters because crawl volume and referral traffic are separate outcomes that people routinely conflate. A crawler reaching your pages tells you that you are eligible to be learned, indexed, and eventually cited. It says nothing about whether the assistant will send anyone your way. The ratio makes that split legible in one figure.

## How many pages does each AI bot crawl per referral?

Wildly different amounts, split cleanly between pure-AI operators and search-backed ones. The table below is the mid-2026 snapshot.

| AI operator (crawler) | Pages crawled per referral | Category |
|---|---|---|
| Mistral | ~3,389 : 1 | Pure-AI |
| Anthropic (ClaudeBot) | ~2,237 : 1 | Pure-AI |
| Perplexity | ~225 : 1 | AI search |
| OpenAI (GPTBot) | ~217 : 1 | Pure-AI / AI search |
| Microsoft (Copilot) | ~35 : 1 | Search-backed |
| Google (Gemini / AI Overviews) | ~4.6 : 1 | Search-backed |
| DuckDuckGo | ~2.5 : 1 | Search-backed |

Source: Cloudflare Radar bot analytics, 28-day window ending 21 July 2026, compiled by SEOmator (verified-bot, network-wide averages; single-source, directional). The pattern is the story: operators without a mature search engine attached (Mistral, Anthropic) crawl thousands of pages per click, while Google, which has always paired crawling with a click-sending search product, sits near parity. SEOmator's independent panel of 500+ B2B sites (January–July 2026) landed on nearly identical numbers, Anthropic **2,363:1**, Microsoft **35:1**, Google **4.0:1**, which is why the ordering, if not the exact decimal, is trustworthy.

## Is the crawl-to-refer gap narrowing?

Yes, and quickly for the biggest AI crawlers. The same Cloudflare-derived series shows the pure-AI ratios falling hard across 2026 as the assistants matured into search products that actually send clicks:

| Operator | Earlier 2026 ratio | Window ending 21 Jul 2026 |
|---|---|---|
| Anthropic (ClaudeBot) | ~23,951 : 1 (Q1 2026) | ~2,237 : 1 |
| OpenAI (GPTBot) | ~1,276 : 1 (Jan–Mar 2026) | ~217 : 1 |
| Google | ~4.9 : 1 (Mar 2026) | ~4.6 : 1 |

Source: Cloudflare Radar via SEOmator, Q1 2026 vs the window ending 21 July 2026 (directional; the ratio is volatile month to month). ClaudeBot's roughly ten-fold drop is the sharpest move: it crawled on the order of tens of thousands of pages per referral in early 2026 and mid-2025, and now crawls thousands. This lines up with the older, coarser reading we cited last year, Anthropic on the order of tens of thousands to one and OpenAI around a thousand to one in mid-2025, so the multi-quarter trend is a steady climb *toward* parity. Google, already near parity, barely moved. The gap is closing from the top down as AI search sends more traffic, not because the bots crawl less.

## Why is the ratio so high in the first place?

Because AI operators crawl for two jobs that mostly happen before any click. The first is **training**: bots fetch huge swaths of the web to build the datasets a [large language model](/glossary/large-language-model) learns from, and that pass touches far more pages than any user will ever visit. The second is **retrieval**: search-backed assistants maintain a fresh index to ground live answers, the [retrieval-augmented generation](/glossary/retrieval-augmented-generation) layer, which also means fetching broadly and repeatedly.

Neither job is tied to sending you a visitor. A page can be crawled, learned, and summarised in an answer while the user never leaves the assistant, the [Dark Library Effect](/glossary/dark-library-effect) we documented in the page-type data. So a high ratio is the normal physics of AI discovery, not a malfunction. It is also why heavy crawling with zero citations is [a leading indicator, not a failure](/blog/chatgpt-citation-lag): the crawl reliably comes weeks before the citation.

> The crawl-to-refer ratio is the price of being learned: an AI operator may fetch thousands of your pages before it sends a single visitor, and that is the expected shape of AI discovery, not a sign anything is broken.

## What should you actually do with this number?

Treat it as context for two separate decisions, not a target to chase. Concretely:

- **Don't judge an AI bot by referral clicks.** A crawler sending few visitors is normal; the payoff shows up as citations and brand knowledge, so [measure citations, not just clicks](/blog/from-clicks-to-citations).
- **Confirm the crawlers can actually reach you.** A ratio only exists if the bots get HTTP 200s; check your logs so a silent [robots.txt](/glossary/robots-txt) or CDN block isn't hiding you, using our guide to [seeing which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site).
- **Watch bandwidth if the ratio is extreme.** For a large site, a 2,000:1 crawler is real load; rate-limit or serve it efficiently rather than block it outright, or you lose the citations too.
- **Remember referral counts understate reality.** Much AI-referred traffic lands in analytics as [direct traffic](/glossary/dark-traffic), so the true referral side of the ratio is higher than your dashboard shows; a [GA4 AI-referral view](/blog/ga4-ai-referral-dashboard) narrows the gap.
- **Compute your own** rather than assuming the network average applies; site type moves the number a lot (see the [companion how-to](/blog/calculate-your-crawl-to-refer-ratio)).

The deeper point is that "we get crawled constantly" and "AI recommends us" are different claims needing different evidence. Watching where AI crawls, what it cites, and where it sends visitors, across engines and over time, and separating crawl volume from real recommendation, is exactly what [measuring AI visibility](/blog/how-to-measure-ai-visibility) with **Buffy Intel** is built to do. Questions: support@flash.tech.

## How many sources does each AI engine cite per answer? (2026 data)
Source: https://heybuffy.com/blog/how-many-sources-ai-engines-cite

AI engines differ sharply in how many sources they pull into a single answer. According to Semrush's **2026 AI Visibility Index**: an analysis of **126 million US AI search prompts** collected between January and April 2026 and released on 26 June 2026. **ChatGPT cites about 15 sources per response** while **Gemini cites about 3**. That gap changes your realistic odds of being one of the sources cited on each engine. This is a dated, fully-sourced reference to the numbers and what they mean for [answer engine optimisation](/glossary/answer-engine-optimization).

**Last reviewed: 12 July 2026.** All figures here are from Semrush's 2026 AI Visibility Index (Semrush is an Adobe company) unless noted. It is a single-vendor dataset. Large and useful, but vendor-reported and a snapshot of a fast-moving landscape, so read the *direction* as firmer than any single number, and cite "Semrush 2026 AI Visibility Index" with the date when you reuse a figure.

## How many sources does each AI engine cite per answer?

The headline figures from the index, with the two engines Semrush reported source-count averages for:

| Engine | Avg. sources cited per response | Where it leans | Source |
|---|---|---|---|
| **ChatGPT** | **~15** | Community + reference (Reddit, Wikipedia) | Semrush 2026 AI Visibility Index |
| **Gemini** | **~3** | A narrower pool (Wikipedia, YouTube) | Semrush 2026 AI Visibility Index |
| Google AI Mode | Analysed in the index; per-response source count not reported here |. | Semrush 2026 AI Visibility Index |
| Google AI Overviews | Analysed in the index; per-response source count not reported here |. | Semrush 2026 AI Visibility Index |

The index covered **ChatGPT, Gemini, Google AI Mode, and Google AI Overviews** across more than **1,200 brands** in **22 industries**. **Perplexity was not part of this index**: a common misreading, so don't attribute a Perplexity source-count to it. The one-line summary: ChatGPT casts a wide net per answer; Gemini pulls from a short list.

## Why does the source count matter for getting cited?

Because it sets how many [citation](/glossary/citation) slots exist in a typical answer. An engine that assembles ~15 sources per response has far more openings than one that pulls ~3, so on ChatGPT, broad and well-[corroborated](/glossary/corroboration) coverage of a topic has more chances to land, while on Gemini the few slots are contested and being in the narrow trusted pool matters more.

- **More slots ≠ easier, exactly.** A wider pool also means more competing sources per answer, so a ChatGPT citation is one of many rather than one of a few.
- **Fewer slots raise the bar.** Gemini's ~3-source answers reward being an established, corroborated source on the topic. See [how to get cited in Gemini](/blog/how-to-get-cited-in-gemini).
- **The selection filter is the same everywhere.** Regardless of count, engines keep passages that are extractable, evidence-dense, scoped, authoritative, corroborated, and fresh. The mechanics in [how to get cited by AI](/blog/how-to-get-cited-by-ai).

The practical read: the source count tells you the *shape* of the opportunity per engine, but not a shortcut. This complements our source-*share* reference (which sources get cited most often) in the [AI search statistics reference](/blog/ai-search-statistics-2026). Count is per-answer breadth; share is how often a given domain appears.

> ChatGPT pulls about 15 sources into an answer and Gemini about 3, so the same topic is a wide-net contest on one engine and a short-list contest on the other. Being cited on one is no promise on the other.

## Are brands visible on every engine, or just one?

Mostly just one. Semrush reported that across the whole study period **only 36 brands maintained visibility on every platform** it analysed. A group it called the "Universal 36," made up largely of very large platforms (Semrush's list includes the likes of YouTube, Reddit, and Amazon). Everyone else showed up on some engines and vanished on others.

That single finding is the strongest argument for measuring each engine separately. Because the engines pull different numbers of sources from different pools, a brand can be well-cited on ChatGPT and absent on Gemini. The [brand-mention gap versus source gap](/blog/brand-mention-gap-vs-source-gap) problem, seen across engines. Semrush also noted that on Gemini specifically, the overlap between *mentioned* brands and *cited* domains can be as low as 30%. The [ghost-citation](/glossary/ghost-citation) pattern where you are named without your page being the source ([more here](/blog/ghost-citations-cited-not-named)).

## Does an integrated SEO + AI-visibility workflow help?

Semrush's companion survey suggests it does. Organisations that ran **SEO and AI-visibility as one integrated workflow** reported far better outcomes than those keeping them siloed:

| Approach | Reported increased traffic or leads from AI platforms |
|---|---|
| **Fully integrated** SEO + AI-visibility | **81%** |
| **Siloed** (managed separately) | **36%** |

Source: Semrush 2026 AI Visibility Index companion survey. Self-reported, so directional. The result lines up with our standing position that [GEO is not a separate discipline from SEO](/blog/is-geo-just-seo): the crawlability, structure, and entity work that earns rankings is the same work that earns citations. Treat the 81%-versus-36% gap as a reason to unify the two functions, not as a guaranteed multiplier.

## How should you use these numbers?

Treat this as a dated reference, not a target. The figures are Semrush's own and a January-April 2026 snapshot; citation behaviour shifts month to month as models and retrieval pipelines change. So:

- **Cite the source and date** ("Semrush 2026 AI Visibility Index") whenever you reuse a figure, and hedge it as vendor-reported.
- **Don't chase the count.** Aim to be a clean, corroborated source on your topic; the per-engine count then tells you how contested each answer is.
- **Measure per engine.** Because visibility rarely carries across engines, track ChatGPT, Gemini, AI Mode, and AI Overviews separately. The discipline in [how to measure AI visibility](/blog/how-to-measure-ai-visibility).

The number that ultimately matters is not how many sources an engine cites in general, but whether *your* brand is one of them for the questions your buyers actually ask. Tracked across every engine, over time rather than spot-checked. That measurement is exactly what **Buffy Intel** is built to provide.

## How much do Google AI Overviews reduce clicks? (2026 CTR data)
Source: https://heybuffy.com/blog/how-much-do-ai-overviews-reduce-clicks

**Google AI Overviews are associated with a large drop in clicks to the top result, and the gap is now measured.** In Ahrefs' 2026 update using December 2025 data across 300,000 keywords, the presence of an AI Overview lined up with up to a **58% lower click-through rate for the No. 1 organic result**. An earlier Ahrefs study using March 2025 data put the isolated effect at about **34.5%**. Both point the same way: when Google answers on the page, fewer people click through.

This is a dated reference, not a new dataset. **Last reviewed: 30 July 2026.** The headline figures come from **Ahrefs**, which analysed 300,000 keywords (150,000 with an AI Overview present, 150,000 informational keywords without) and compared click-through rates before and after the U.S. rollout of [AI Overviews](/glossary/ai-overviews). The cited-versus-not-cited numbers come from a separate **Seer Interactive** analysis. Both are single-vendor, specific to Google's AI Overviews rather than every AI engine, and focused on informational intent, so read the *direction* as firmer than any single decimal, and cite the source and date when you reuse a figure.

## How much do AI Overviews cut clicks to the top result?

By roughly a third to a half of the click-through rate, depending on the study window. Ahrefs measured the effect twice, and the gap widened as AI Overviews spread. The table below is the like-for-like comparison Ahrefs reported for keywords that trigger an AI Overview.

| Metric | Ahrefs, March 2025 study | Ahrefs, 2026 update (Dec 2025 data) |
|---|---|---|
| Keywords analysed | 300,000 | 300,000 |
| Isolated CTR drop, position 1 | ~34.5% | up to ~58% |
| Position-1 CTR on AI-Overview keywords | ~7.3% → ~2.6% | ~7.3% → ~1.6% |
| Intent studied | Informational (99.2% of AI-Overview keywords) | Informational |

Source: Ahrefs, March 2025 study and its 2026 update using December 2025 data (single-vendor, Google-AI-Overviews-specific, informational intent; associations, not proven causation). The 34.5% figure isolates the AI Overview effect against a forecast of what CTR would have been without one; the 58% figure reflects the larger, later December 2025 sample. The consistent read is that a top ranking earns far fewer clicks once an AI Overview sits above it, and the effect has deepened over 2026, not eased.

## Does being cited inside the AI Overview help?

Yes, relatively, but it does not restore the old click level. Seer Interactive compared organic click-through rates across three states on the same results page, and being named inside the answer beat being left out of it.

| State of the result page | Organic CTR | Reading |
|---|---|---|
| No AI Overview present | ~1.45% | The pre-AI-Overview baseline |
| AI Overview present, brand cited in it | ~0.70% | Best of the reduced outcomes |
| AI Overview present, brand not cited | ~0.52% | The worst case |

Source: Seer Interactive (single-vendor, point-in-time). Being cited inside the AI Overview was associated with about **35% more organic clicks** than not being cited (0.70% versus 0.52%), yet both sat roughly half of the no-AI-Overview level. The practical lesson: you cannot opt out of AI Overviews appearing, but you can compete to be the source cited *inside* one, which is the difference between the middle row and the bottom row.

## Why do AI Overviews reduce clicks at all?

Because the answer is delivered on the results page, so the click becomes optional. An AI Overview summarises the answer above the classic links, satisfying many searchers without a visit, the [zero-click](/glossary/zero-click-search) pattern that a [featured snippet](/glossary/featured-snippet) started and generative answers accelerated. As of early 2026, a Datos/SparkToro analysis reported by Search Engine Land put roughly **68% of Google searches** ending without a click, with AI summaries a major driver.

This is also why impressions and clicks are drifting apart, the [great decoupling](/glossary/great-decoupling): your pages can be shown as often as ever while earning fewer visits, because being displayed inside an answer is not the same as being clicked. It is a different phenomenon from rank-decoupling, where a page no longer has to rank in the top 10 to be cited, which we cover in [does ranking on Google get you cited by AI](/blog/does-google-rank-get-you-cited-by-ai) and [which domains AI Overviews cite most](/blog/most-cited-domains-ai-overviews).

> An AI Overview can cut clicks to the No. 1 result by up to 58%, yet being cited *inside* that overview earns about 35% more clicks than being left out. The click you used to win by ranking is now split between appearing in the answer and being named as its source.

## What should you actually do with these numbers?

Treat the click loss as a reason to change the scoreboard, not evidence AI search is worthless. Concretely:

- **Measure citations, not just clicks.** If sessions are your only metric, AI search reads as pure loss even while your brand is shown and trusted; track presence and [citation](/glossary/citation) coverage alongside traffic, per [from clicks to citations](/blog/from-clicks-to-citations).
- **Compete to be the cited source.** The gap between the cited and not-cited rows above is the winnable one; earn the citation inside the answer rather than mourning the vanished click.
- **Segment by intent before you panic.** The click loss concentrates on informational queries; your transactional and branded pages are far less exposed, so weight the impact to your own query mix.
- **Estimate your own exposure** rather than assuming the network figure applies; site and query mix move the number a lot (see the [companion how-to](/blog/estimate-ai-overview-click-loss)).
- **Remember the referral you keep is often undercounted.** Much AI-influenced traffic returns later as branded or [direct traffic](/glossary/dark-traffic), so a raw click count understates AI's real contribution.

The deeper point is that "we lost clicks" and "we lost visibility" are different claims that need different evidence. A page can shed clicks to an AI Overview while its brand is being shown, cited, and recommended more than ever, and only cross-engine, answer-level measurement tells them apart. Watching where you are cited, where you are merely shown, and where AI still sends visitors, over time and across engines, is exactly what [measuring AI visibility](/blog/how-to-measure-ai-visibility) with **Buffy Intel** is built to do. Questions: support@flash.tech.

## How often do AI crawlers ignore robots.txt? The 2026 network-scale data
Source: https://heybuffy.com/blog/how-often-do-ai-crawlers-ignore-robots-txt

**At network scale, a large and growing share of AI crawlers ignore robots.txt: about 30% of AI-bot scrapes did not comply with the file's permissions in Q4 2025, up from roughly 3.3% a year earlier**, according to TollBit's *State of the Bots* data aggregated across the publisher sites it monitors. The blunt lesson for site owners: [robots.txt](/glossary/robots-txt) is a request compliant bots choose to honour, not a wall, and at web scale a meaningful slice of AI traffic no longer honours it.

This is a dated reference, not a new dataset. **Last reviewed: 1 August 2026.** The headline figures come from **TollBit**'s *State of the Bots* reports (Q2 2025 and Q3 & Q4 2025), a bot-traffic analytics vendor whose numbers are network-wide aggregates across the publisher sites on its platform, reported via FIPP and Media Copilot. They are single-source and directional, so read the *trend* as firmer than any single decimal, and cite "TollBit, State of the Bots (Q4 2025)" when you reuse one. It sits alongside our controlled test of whether [AI assistants respect robots.txt on a user fetch](/blog/do-ai-assistants-respect-robots-txt) and our [AI crawler share leaderboard](/blog/ai-crawler-market-share-2026).

## How often do AI crawlers ignore robots.txt?

Increasingly often, and the trend line is steep. TollBit's network aggregate shows the share of AI-bot scrapes that bypassed robots.txt permissions climbing roughly ten-fold in a year:

| Quarter | AI-bot scrapes ignoring robots.txt |
|---|---|
| Q4 2024 | ~3.3% |
| Q1 2025 | ~13% |
| Q4 2025 | ~30% |

Source: TollBit, *State of the Bots* (Q2 2025 and Q3 & Q4 2025 editions), network-wide aggregates via FIPP and Media Copilot (single-source, directional). The direction is the story: in late 2024 non-compliance was a rounding error; a year later roughly one scrape in three ignored an explicit disallow. TollBit also reported over **26 million disallowed scrapes in March 2025 alone**, on sites whose robots.txt asked bots not to extract content. Treat the exact percentages as a moving aggregate, not a fixed rate, and never as a per-bot verdict.

## How much AI-crawler traffic is there now?

Enough that non-compliance is no longer a fringe problem. TollBit's data shows AI-bot activity growing sharply relative to human visits and shifting toward live retrieval:

- **Bot density rose fast.** By Q4 2025 the ratio had tightened to about **1 AI-bot visit for every 31 human visits**, roughly a 60% increase in bot density over the period.
- **Retrieval overtook training.** Real-time [retrieval-augmented generation](/glossary/retrieval-augmented-generation) scrapes, the fetches that ground live answers, grew faster than training crawls and, TollBit reported, now outnumber them.
- **Little of it returns a visitor.** TollBit put referral traffic from AI applications at about **0.12%** of visits on average, a fraction of what classic search sends, the extraction-heavy shape we cover in the [crawl-to-refer ratio](/glossary/crawl-to-refer-ratio) data.

The combined picture: more AI crawling, a rising share of it ignoring robots.txt, and very little of that reading turning into a click. Figures are TollBit network aggregates for 2025 (single-source, directional).

## Why can't robots.txt stop AI crawlers?

Because robots.txt was never an enforcement mechanism, it is an honour system. The Robots Exclusion Protocol is a plain-text file that *asks* well-behaved bots not to fetch certain paths; it has no technical power to refuse a request. A bot that chooses to ignore it faces no barrier, and the record shows some do. TollBit also documented that a market of nearly **40 web-scraping vendors** now sells access to the web, and that non-compliant scraping leans on evasion, **IP rotation, user-agent spoofing, and cloud-based headless browsers**, precisely the techniques that defeat a file which trusts the bot to identify itself honestly.

> robots.txt is an honour system, not a lock: it tells honest bots where not to go and does nothing to the ones that ignore it, which is why a controlled test and a network aggregate can both be true at once.

That is why a self-declared user-agent string can't be trusted either. If a bot will ignore your disallow rules, it will also relabel itself, so the only reliable signal of who is really fetching you is a [verified bot](/glossary/verified-bot) identity, confirmed by reverse DNS to published IP ranges, not the name in the request header.

## Does this mean ChatGPT and Claude ignore robots.txt?

Not as simply as the aggregate suggests, and this is where two credible findings have to be reconciled rather than pitted against each other. Our own reference on the [June-2026 user-fetch test](/blog/do-ai-assistants-respect-robots-txt) found that when a user pasted a robots.txt-blocked URL into a chatbot, **ChatGPT, Claude, and Perplexity honoured the block** and declared honest user-agents; nine other assistants fetched the page anyway. TollBit's aggregate, by contrast, flags OpenAI's `ChatGPT-User` agent at about **42%** of its requests reaching disallowed content across the sites it monitors.

These measure different things, so the 42% is not a clean "ChatGPT ignores robots.txt" headline:

- **Request type differs.** The controlled test is a single, explicit *user-initiated* fetch of one URL. The aggregate pools every request from an agent across many sites and windows, a mix of user fetches and autonomous retrieval, where the grey area of whether a user-triggered fetch should obey a crawl directive is unresolved.
- **Scope and window differ.** One is a point-in-time lab test on isolated canary URLs; the other is a rolling network average whose composition shifts by site configuration and quarter.
- **Compliance is not a fixed property.** A bot can decline one blocked URL in a test and still show a high non-compliant share in aggregate, because the two samples capture different behaviour.

The reconciled reading: **the aggregate scale finding (~30% of AI scrapes non-compliant, rising) and the structural point (robots.txt can't enforce anything) are the durable takeaways.** The per-agent percentages, on either side, are narrower snapshots that shouldn't be read as a bot's fixed character. Both studies point the same way, robots.txt shapes who *politely* stays out, not who *can*.

## What should you do about AI-crawler non-compliance?

Decide deliberately, then enforce where enforcement actually lives. The rising non-compliance rate doesn't mean "block everything", for most brands that want AI visibility, the bigger risk is being unreadable. A short decision guide:

- **Audit before you act.** Check your own logs for AI-bot hits to disallowed paths before assuming you have a problem, using our [companion how-to](/blog/check-if-ai-bots-ignore-your-robots-txt); network averages don't tell you your rate.
- **Enforce at the edge for what must stay closed.** For genuinely proprietary or paywalled content, use a CDN or WAF rule keyed to [verified-bot](/glossary/verified-bot) identity that returns a 403, not a robots.txt line, and confirm you aren't [blocking crawlers by accident](/blog/is-your-cdn-blocking-ai-crawlers).
- **Open what you want cited.** The crawlers that ground and cite live answers are the ones you usually want reading you; [deciding whether to let AI crawlers index your site](/blog/should-you-let-ai-crawlers-index-your-site) is a business call, not a default block.
- **Verify identity, not headers.** Group and confirm bots by published IP ranges, not the user-agent string, per our guide to [seeing which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site).

The deeper point is that "can I keep AI bots out?" and "am I being cited?" are different questions with different tools. robots.txt answers neither cleanly: it can't reliably keep non-compliant crawlers out, and blocking the compliant ones costs you citations. Watching who actually crawls you, whether they obey your rules, and whether that reading turns into citations, across engines and over time, is exactly what [measuring AI visibility](/blog/how-to-measure-ai-visibility) with **Buffy Intel** is built to do. Questions: support@flash.tech.

## How often do AI engines actually name a brand?
Source: https://heybuffy.com/blog/how-often-do-ai-engines-name-brands

AI engines name a specific brand far less often than most marketers assume, and how often depends heavily on which engine you ask. In a 2026 analysis of 34,234 AI answers by AI-visibility platform Leapd.ai, ChatGPT named a brand in about **0.59%** of responses, Perplexity in about **13.05%**, and Grok in about **27%** — roughly a **46-times** gap between the least and most brand-naming engines. This reference lays out the figures, attributed and dated, explains why the engines diverge so sharply, and separates "naming a brand" from the related-but-different questions of being [cited](/glossary/citation) as a source and being recommended.

**Last reviewed: 24 August 2026.** The brand-naming rates below are from Leapd.ai's 2026 analysis of 34,234 AI responses. It is a **single-vendor, directional** study whose full per-engine methodology is not published, and brand-naming rates are highly sensitive to the mix of commercial versus informational prompts in the sample — so read the **ordering and order-of-magnitude** as the finding, not the second decimal place, and cite "Leapd.ai, 2026" with the date when you reuse the numbers.

## How often does each AI engine name a brand?

Rarely on ChatGPT, occasionally on Perplexity, and most often on Grok, on the reported sample. The headline is the spread, not any single figure:

| Engine | Share of answers that named a brand | Notes |
|---|---|---|
| ChatGPT | **~0.59%** | Answers many prompts from training data; retrieves selectively |
| Perplexity | **~13.05%** | Performs a live web search on essentially every query |
| Grok | **~27%** | Highest brand-naming rate in the sample |

Source: Leapd.ai, 2026 (analysis of 34,234 AI responses). The gap between the lowest and highest is about **46 times** — a far wider divergence than the same brands would see across classic search engines. The practical takeaway: **there is no single "AI brand-mention rate."** A brand that appears often in Perplexity answers can be nearly absent from ChatGPT's prose for the same questions, and a one-engine spot check will badly misread total visibility.

## Why do the engines differ so much?

Because they retrieve differently. The brand-naming rate is downstream of when and how each engine goes to the live web:

- **ChatGPT** answers many prompts from its trained parameters and performs a live search only for a subset. Leapd.ai reports it retrieves for roughly **53.5%** of commercial queries versus about **18.7%** of informational ones. When it does not retrieve, it tends to describe a category rather than name a vendor — so a brand name surfaces only when retrieval fires *and* a specific brand is the answer.
- **Perplexity** performs a live web search on essentially every query and foregrounds named sources, which mechanically surfaces more brand names in the visible answer.
- **Grok** named brands most often in the sample; treat its high rate cautiously given the single-vendor source and the smaller likely sub-sample per engine.

The pattern is that **an engine that searches the live web more often, and shows its sources more prominently, names more brands.** This is the same architecture split the corpus has documented from the other direction: engines cite [largely different sets of pages](/blog/ai-mode-vs-ai-overviews-citations), because they retrieve from different places at different times.

> There is no single number for how often AI names your brand. The rate swings roughly 46-fold across engines, so "our AI mention rate" is only meaningful once you say which engine, for which kind of question.

## Is naming a brand the same as citing a source?

No — and conflating the two is the most common measurement error here. Three distinct things happen in an AI answer, and each is measured separately:

| Metric | What it measures | Example |
|---|---|---|
| Brand-naming rate | Whether a brand name appears in the visible answer text | "Tools like Acme and Globex do this" |
| Source citation | Whether a domain is cited as the source of a claim | A footnote linking `acme.com` |
| Recommendation | Whether the answer actually endorses the brand | "The best option is Acme" |

These come apart constantly. An engine can [cite your page as a source and still recommend a competitor](/blog/cited-vs-recommended-in-ai-search); it can name a brand it never cited; and it can lift a fact from your domain without ever printing your name — a [ghost citation](/glossary/ghost-citation). So a low brand-naming rate is not the same as being invisible. It is one lens among several, and it pairs naturally with the [brand-mention gap versus source gap audit](/blog/brand-mention-gap-vs-source-gap), which separates "the engine never names us" from "the engine never cites our pages" because they need opposite fixes.

This is also why brand-naming rate does not contradict the source-count data. ChatGPT [cites on the order of 15 source domains per answer](/blog/how-many-sources-ai-engines-cite) on Semrush's 2026 figures, yet names a brand in under 1% of answers here — because citing many domains as background sources is a different act from printing a vendor's name in the sentence a reader reads.

## Does this square with ChatGPT's shift toward first-party sources?

Yes, cleanly. We reported separately that ChatGPT is [resolving more of its citations to first-party domains](/blog/is-chatgpt-citing-fewer-listicles) after GPT-5.6 — using the [`site:` operator](/glossary/site-operator) to fetch named domains directly. That is about *which domains it cites as sources*, and it can rise at the same time as the *brand-naming rate in prose* stays low. The model can quietly fetch and quote a brand's own page while still writing an answer that describes the category without naming vendors. Both are true: ChatGPT increasingly grounds on [first-party pages](/glossary/first-party-citation) as sources, and it rarely names brands in the visible text. They are two different surfaces of the same answer, and a brand should measure both rather than assume one implies the other.

## What should a brand do about it?

Stop chasing a single "AI mention rate," and work the engine that matches where your buyers actually ask:

- **Measure per engine, per question type.** A 46-fold spread means one blended number hides everything. Track ChatGPT, Perplexity, Gemini, Grok, and Google separately, split by commercial versus informational prompts, the way an [AI visibility audit](/blog/how-to-audit-your-site-for-ai-visibility) should.
- **Win the naming engines with corroboration, not self-declaration.** On Perplexity and Grok, which surface live sources, brand names ride in on third-party pages and clean first-party facts — the same levers behind [why AI cites one brand](/blog/why-ai-cites-one-brand) and how to [get recommended in ChatGPT](/blog/how-to-get-recommended-in-chatgpt).
- **On ChatGPT, be the first-party source it fetches.** Because it names few brands but reaches for named domains, make your specs, pricing, and official facts clean, [server-rendered, extractable text](/blog/prioritize-your-structured-data) so that when it does retrieve, your page is what it lifts.
- **Track the trend, not the snapshot.** Brand-naming rates move with each model release. A quarter-over-quarter line per engine tells you far more than any one reading.

The honest read for late 2026: how often AI names your brand is real, worth tracking, and almost meaningless as a single blended figure — it only becomes decision-grade once you split it by engine and question type and watch it over time. That per-engine, over-time view is exactly what **Buffy Intel** is built to measure. Questions: support@flash.tech.

## Query fan-out: why one question becomes a dozen searches
Source: https://heybuffy.com/blog/how-query-fan-out-works

Ask an AI "what's the best vitamin C serum for sensitive skin?" and it feels like one question. Behind the scenes it's a dozen.

Generative search engines don't search with the string you typed. They treat it as a **starting clue**, then **fan it out** into many related sub-queries, retrieve sources for each, select the best passages, and synthesise everything into one answer. Understanding that machinery is the difference between optimising for a keyword and optimising for how AI actually assembles answers.

## How the fan-out works

Four steps, roughly:

1. **Expand**: the system generates many sub-queries from your prompt.
2. **Route**: it sends each sub-query to the sources and formats best suited to it.
3. **Select**: it pulls candidate passages ("chunks") and keeps the most extractable, credible ones.
4. **Synthesise**: it stitches the surviving chunks into a single cited answer.

For our serum question, the expansion might include: *vitamin C serum for sensitive/reactive skin*, *best vitamin C serum under $40*, *vitamin C vs niacinamide for sensitive skin*, *how to introduce vitamin C without irritation*, *vitamin C concentrations for beginners*, *ingredients to avoid alongside vitamin C*, and more. One typed question, fifteen-plus actual searches.

## The kinds of sub-queries

The expansions aren't random. They tend to fall into patterns:

- **Rewrites & narrowing**: more specific versions ("…for sensitive skin, under $40, fragrance-free").
- **Related / latent intent**: neighbouring topics the system infers you'll care about (application tips, what to pair it with), surfaced via embeddings and knowledge-graph links.
- **Anticipated follow-ups**: the questions people usually ask next ("will it cause purging?").
- **Slot-filling**: variables the system needs to resolve: concentration, skin type, budget, format.
- **Comparisons**: "X vs Y," "alternatives to X."

Each branch is a separate chance to be present, or absent.

## Routing: different sub-queries want different sources

Fan-out is **modality-aware**. A "how to apply" sub-query may favour video (with transcripts); a "best X" sub-query leans on comparison content and reviews; a "what is" sub-query pulls concise reference text; a "price/specs" sub-query wants tables and structured data. If your information only exists as a pretty paragraph, or is trapped in a format a crawler can't parse. You're invisible to the branches that prefer another format.

## What it means for brands

This is the shift from keyword competition to **intent coverage**, and it changes the playbook:

- **Compete for the whole tree, not one phrase.** If you only have a page targeting the exact query, you're eligible for one branch of the fan-out. The brands that win cover the *sub-questions* too.
- **Build intent-complete hubs.** Around a core topic, create interlinked modules for the predictable expansions. Uses, comparisons, ingredients, troubleshooting, who-it's-for. Each becomes eligible for its own branch.
- **Optimise at the chunk level.** Selection happens on passages, not whole pages. A clean, self-contained, well-cited chunk. Scoped clearly, dense with verifiable facts, [structured](/glossary/structured-data). Beats the same point diffused across prose. ([How to get cited](/blog/how-to-get-cited-by-ai) goes deeper on this.)
- **Keep multimodal parity.** Tables, lists, transcripts, and structured data let you be retrieved across formats, not just one.
- **The multiplier:** because a single answer is assembled from many branches, a brand that covers several of them can appear *multiple times in the same answer*. Named in the recommendation, cited in the "how to use," and again in the comparison.

## The moving target: fewer, deeper fan-outs

Fan-out behaviour shifts with each model generation. Some newer models run **fewer, longer-tail** sub-queries and expect a single comprehensive source to satisfy more of the intent, which raises the bar on depth and specificity. Either way the direction holds: shallow, single-keyword content loses; comprehensive, well-structured, intent-complete content wins.

## How you'd measure it

Classic SEO metrics (one keyword's ranking, CTR) miss this entirely. What matters is **sub-query recall**: across the many branches a question fans into, how often does your content show up? That's exactly why measuring AI visibility means sampling [many prompts](/glossary/query-fan-out), repeatedly, across every engine. A single check can't see the tree. Tracking your coverage across that fan-out is part of what **Buffy Intel** does.

## How to audit your site for AI visibility
Source: https://heybuffy.com/blog/how-to-audit-your-site-for-ai-visibility

An AI-visibility audit checks whether AI engines can **reach, read, and quote** your pages, not whether you rank a link. It has five parts: crawler access, extractability, product data, off-site corroboration, and quotability. Do them in that order, because a page an engine can't fetch can't be cited no matter how good it is, and a brand no third-party source mentions won't be recommended no matter how clean its schema.

## What does an AI-visibility audit check?

Classic SEO audits grade a page's ability to rank a blue link. An AI-visibility audit grades a different chain: can an [answer engine](/glossary/answer-engine-optimization) discover your content, extract a clean passage, understand your products, verify your brand against other sources, and lift a sentence into its answer. Each link can fail independently, so audit them separately.

| # | Check | The question it answers | Fails when |
|---|---|---|---|
| 1 | Crawler access | Can AI engines fetch your pages at all? | CDN/robots return 403 to AI bots |
| 2 | Extractability | Can an engine parse and cite a clean chunk? | JS-only content, no schema, no `<h1>` |
| 3 | Product data | Can shopping agents read your catalog? | No Product/Offer schema |
| 4 | Corroboration | Do off-site sources confirm your brand? | Thin/absent on Wikipedia, Reddit, reviews |
| 5 | Quotability | Would an AI lift an answer from your prose? | Buried answer, vague marketing fluff |

> A page an AI can't fetch can't be cited; a brand no other source mentions won't be recommended. Structure and prose only matter once those two gates are open.

### Step 1: Can AI crawlers reach your pages?

Fetch your key pages while identifying as the major AI crawlers and confirm you get **HTTP 200, not 403**. Check `GPTBot` (feeds ChatGPT), `ClaudeBot` (feeds Claude), `OAI-SearchBot` (ChatGPT Search), and `PerplexityBot` (Perplexity) against your homepage plus one example of each page type. A [silent CDN block](/blog/is-your-cdn-blocking-ai-crawlers) is the single most common reason a brand is never cited, and it never shows in normal analytics. While you're here, confirm `robots.txt` welcomes those user-agents and your `sitemap.xml` exists and is current. The [crawler directory](/blog/ai-crawler-user-agent-directory) lists the exact tokens.

### Step 2: Can an engine extract and cite your pages?

Most AI crawlers never execute JavaScript. They read the raw HTML. So measure how much real content exists *before* any script: [if your content depends on JavaScript](/blog/do-ai-assistants-render-javascript), an engine may see an empty shell. Then grade three structural signals per page: valid [structured data](/glossary/structured-data) (a real `Organization` block with `sameAs` links to your profiles, plus `BlogPosting`/`FAQPage` where relevant), one `<h1>` per page with labelled sections and image alt text so an engine can [segment the page](/blog/prioritize-your-structured-data), and reasonable HTML weight so your schema isn't buried past a crawl budget. Pages that are [readable to agents](/blog/make-your-website-agent-readable) as clean, semantic HTML are the ones that get quoted.

### Step 3: Can shopping agents read your products?

If you sell, check every product template for `Product` and `Offer` schema exposing name, price, and availability. The exact fields [AI shopping agents read](/blog/prepare-product-catalog-for-ai-agents). A product page that looks perfect to a human but carries no machine-readable price or stock status is invisible to an agent composing a "best [category] under ₹X" answer. This check is skippable for a pure publisher, but decisive for D2C and ecommerce.

### Step 4: Do off-site sources corroborate you?

AI engines lean on how well-established you are as an *entity*, often more than on your own pages. Audit where engines can verify you beyond your site: is there a Wikipedia or Wikidata entry, and does it list your official website; are you present and active on the platforms your customers cite (Reddit, LinkedIn, YouTube, Instagram); do independent reviews and roundups mention you. Gaps here are [corroboration](/glossary/corroboration) gaps. The slow, durable lever behind [entity strength](/blog/entity-strength-ai). "Not found" on a source your competitors dominate is an opportunity, not a verdict.

### Step 5: Would an AI actually quote your writing?

Grade your best content pages. Products, articles, guides. Against three lenses an engine implicitly applies. **Gets to the point:** does the page state its core answer in the first visible text, before navigation and marketing preamble? **Makes sense on its own:** could a single paragraph be quoted alone and still parse. Named subject, no dangling "it" or "we"? **Facts, not fluff:** concrete numbers, specs, and comparisons versus adjectives and slogans. A page can pass every technical check and still never get lifted because the answer is buried under a promotional banner.

## How often should you audit?

The structural checks (1-3) change only when you ship a release or a CDN rule, so re-audit **monthly or quarterly**. Corroboration (4) moves slowly. Review it quarterly. But whether you're actually *named and cited* shifts constantly, so pair the deep audit with the lighter [one-hour weekly routine](/blog/weekly-ai-visibility-routine) and read both as trends. An audit tells you whether the doors are open; the weekly snapshot tells you who's walking through. If you find a gap, the [two-lens split](/blog/brand-mention-gap-vs-source-gap), not named versus not cited. Tells you which fix to queue first.

## Do the audit, then keep it fresh

Start with Step 1 today: it's ten minutes and the most common silent failure. Then work down the list once, fixing the highest-leverage gap each pass. Doing all five checks by hand across a whole site. Probing every AI crawler, grading schema and structure on each template, searching every off-site source, and scoring quotability page by page. Is exactly what **Buffy Intel's Site Audit** does automatically: it reads your pages the way AI crawlers do, scores each pillar 0-100, shows the specific fixes, and refreshes on a monthly cadence so you catch regressions early. Point it at your domain to see where the doors are already open and where they're quietly shut.

## How to benchmark local AEO across cities
Source: https://heybuffy.com/blog/how-to-benchmark-local-aeo

You cannot benchmark local AI visibility by asking an engine a question from your desk. To know whether AI recommends you city by city, you need a method: an **explicit-city prompt matrix, sampled repeatedly, reported as rates**: plus the API location parameter where you can use it. This how-to lays out the method and the traps.

The reason hand-testing fails is built into how [location works in AI engines](/blog/do-ai-engines-know-where-you-are): you can't fake a city-level IP in a consumer app, engines round your location, and the same prompt returns different answers run to run.

## Step 1: Build the prompt matrix

Define three axes and take their product:

- **Cities**: the locations you serve or want to win (start with 5-20).
- **Engines**: ChatGPT, Perplexity, Gemini, Claude, Google AI Overviews/AI Mode.
- **Prompts**: the real questions buyers ask, in two flavors (see Step 2).

Each cell is one *city × engine × prompt*. That grid is your benchmark surface. Keep the prompts fixed and natural ("best fertility clinic in [city]," "affordable plumber in [city] open now") so results are comparable across the matrix.

## Step 2: Measure implicit *and* explicit localization, and label which

There are two different behaviors, and they don't return the same answer:

- **Explicit**: you name the city in the prompt ("best dentist in Denver"). Reproducible anywhere; this is your backbone.
- **Implicit**: the engine infers the city from location and localizes silently ("best dentist near me"). This is what most real users trigger.

Measure both, and **label every result with which method produced it**. Reporting an implicit result as if it were explicit (or vice versa) is the most common way these benchmarks mislead.

## Step 3: Set the city deterministically with the API where you can

For explicit, deterministic city-setting, use the web-search APIs that accept a location parameter. As of mid-2026:

| Engine | User-location parameter? | How to benchmark it |
|---|---|---|
| OpenAI web-search API | Yes. Approximate location | Set city via the API, sample repeatedly |
| Perplexity API | Yes. Approximate location | Set city via the API, sample repeatedly |
| Gemini | No exposed parameter | Explicit-city prompts only |
| Claude (web search) | No exposed parameter | Explicit-city prompts only |
| Google AI Overviews / AI Mode | No exposed parameter | Explicit-city prompts only |

Where the API carries no location, **the API has no user city at all unless you pass it**: so explicit-city prompting is the honest substitute. Don't pretend an API result is "localized" when nothing set the location.

## Step 4: Sample repeatedly and report rates, not snapshots

Because answers are non-deterministic, a single pull is noise. Sample each cell several times and report **presence** (did you appear?) and [share of voice](/glossary/share-of-voice) (what fraction of the named businesses were you?) as percentages across samples. "Cited in 4 of 10 samples in Phoenix on Perplexity" is a real number; "I asked once and didn't see us" is not.

> A local AI benchmark is a rate, not a screenshot. One prompt, one city, one pull tells you nothing durable. The signal lives in repeated sampling across a city-and-engine matrix.

## Step 5: Read the gaps

With the matrix sampled, two patterns matter most:

- **City gaps**: cities where you're present elsewhere but absent here. Usually a local-footprint problem (listings, reviews, local pages) in that market.
- **[Citation gaps](/glossary/citation-gap)**: the engine recommends your category but never names you, or cites a directory that omits you. That points at the third-party sources you're missing from.

Trend these over time, not once. Local standing shifts as listings, reviews, and the cited sources change.

## The pitfalls, in one place

- **You can't fake a city-level IP** in a consumer app. Use the API parameter or explicit prompts.
- **Engines round** location to a coarse city/region, so precision is limited by design.
- **Non-determinism** means single pulls mislead. Always sample and report rates.
- **Implicit ≠ explicit**: measure both and label which produced each result.

This is measurement infrastructure, not a one-afternoon task. A city-and-engine matrix, sampled on a schedule, trended over time. It fits inside a broader [AI-visibility reporting stack](/blog/ai-visibility-reporting-stack), and running it continuously across every engine and city is exactly what **Buffy Intel** is built to do.

## How to choose which prompts to track for AI visibility
Source: https://heybuffy.com/blog/how-to-choose-prompts-to-track

The prompts you track decide what your AI-visibility data is even about, so choosing them from real customer language beats guessing from a keyword list. A workable method: group prompts into roughly **80% organic, 10% branded, 10% competitor**, source the wording from real customer signals (PPC queries, support transcripts, live observation), and crucially, track the **follow-up** prompts where decisions actually happen, not just the opening question.

This is a how-to for building that prompt set. It assumes you already know *why* to measure AI visibility, if not, start with [how to measure your AI visibility](/blog/how-to-measure-ai-visibility), and focuses on the one input that most tracking setups get wrong.

## Why does prompt selection make or break AI tracking?

Because a tracker only reports on the prompts you give it. Feed it marketer-invented phrasing and you get a confident answer to a question no customer asks. Seer Interactive argued in June 2026 that most teams pick prompts from intuition rather than observed behaviour, and that this is now a real gap: analysing 387 real prompts across seven studies (July 2025-June 2026), they reported an **83% drop in keyword-search-style prompts**, a **270% rise in task-delegation requests** ("do this for me"), and a **300% rise in personal information shared inside prompts**. Treat those as one practitioner's dataset. Directional, not definitive, but the implication is clear: people no longer talk to AI the way they typed into Google, so prompts written like search keywords miss how customers actually ask.

The fix is to anchor every tracked prompt in something a real person said.

## What's a good split of organic, branded, and competitor prompts?

A practitioner framework shared by Promptwatch's co-founder (June 2026, single-vendor and self-reported) groups prompts into three monitors, weighted toward the category rather than the brand:

| Prompt type | Share | What it captures | Example |
|---|---|---|---|
| Organic | ~80% | Category questions, problems, use cases. **No brand named** | "What should I look for in a waterproof commuter jacket?" |
| Branded | ~10% | Sentiment and accuracy about *your* brand | "Is [your brand] good for cycling commutes?" |
| Competitor | ~10% | Where competitors are winning the answer | "Best alternatives to [competitor]?" |

The logic behind the heavy organic weighting: most AI buying journeys start with an unbranded problem, so that's where the [share of voice](/glossary/share-of-voice) is won or lost. Branded and competitor [prompts](/glossary/prompt) act as a thermometer. They tell you how you're described and where rivals get named, but they're a small slice because customers rarely open with a brand name. Keep the *exact wording* realistic; that's what the next section is about.

## Where should the prompt wording come from?

From real customer signals, in ascending order of effort and quality. Seer's "humanity stack" frames three tiers. Use as many as you can:

1. **PPC and search-query data (start here).** Your paid-search query reports are real human phrasings, available cheaply today. They're the fastest way to replace invented prompts with actual language.
2. **Sales and support transcripts (higher signal).** Call notes, chat logs, and tickets reveal the vocabulary, objections, and constraints customers use. The questions they ask a human are the ones they'll ask an AI.
3. **Live customer observation (highest signal).** Watch real customers use AI tools to make a decision. Seer's blunt version: spend 30 minutes observing one real customer in an AI tool *before* you build a tracking strategy. It surfaces behavioural patterns, and follow-up phrasing. Competitors typically never see.

Mining the [query fan-out](/blog/how-query-fan-out-works). The sub-questions an engine spawns from one prompt. Is a fourth source once you're tracking, and a powerful one for [turning that data into content](/blog/query-fan-out-content-loop). But the three tiers above are how you seed a realistic set in the first place.

## Why track follow-up prompts, not just the opening one?

Because the opening prompt is exploration and the follow-up is the decision, and most tools only measure the opener. Seer reported that **25-50% of prompts in a session are follow-ups**, and framed it sharply:

> The opening prompt is where people figure out what to ask. The follow-up prompts are where they decide.

In practice this means tracking the *second and third turns* of a realistic conversation: "okay, of those, which is best for under £150?" or "which of those ships to India?" Those refinements carry the personal context. Budget, location, constraints, that decides who gets recommended. A prompt set that stops at the opening question measures discovery while missing the purchase, and it's a common reason a brand looks present yet still loses the sale. (For the related diagnosis of *why* you might be absent, see [why you're invisible in AI search](/blog/why-youre-invisible-in-ai-search).)

## A practical checklist for building your prompt set

Pulling it together. Audit and rebuild against these:

- **Audit the current list.** When were the prompts last updated, and did any customer input shape them? If the answer is "we made them up," start over.
- **Seed from real language.** Pull from PPC queries first, then support and sales transcripts, then live observation.
- **Apply the 80/10/10 split.** Mostly organic category questions; a thin slice each of branded and competitor.
- **Add follow-ups.** For every opening prompt, write the realistic second and third turns where a buyer narrows down.
- **Include personal context.** Test how answers shift with constraints real customers give. Budget, location, square footage, use case.
- **Sample repeatedly across engines.** AI answers are non-deterministic and differ by engine, so each prompt needs multiple samples over time, not a single check.

Do this by hand for a few prompts to learn the texture; do it at scale. Hundreds of realistic prompts, with follow-ups, sampled repeatedly across every engine and turned into a trend, and you've described exactly the job **Buffy Intel** automates.

## How to earn Google AI Overview citations from YouTube video
Source: https://heybuffy.com/blog/how-to-earn-ai-citations-from-youtube

**YouTube is the single most-cited domain in Google AI Overviews (Ahrefs, mid-2026), and Google owns it, so well-structured video is one of the highest-leverage, least-crowded ways to earn AI citations.** This is a five-step method to make a video extractable enough that an AI answer can lift a claim or step from it, rather than scrolling past.

It's the practical companion to [which domains Google AI Overviews cites most](/blog/most-cited-domains-ai-overviews). That piece is the evidence that video wins; this is how to earn the citation. The concept it builds is [video AEO](/glossary/video-aeo).

> A video gets cited for the same reason a page does: a clean, answer-first, well-labelled chunk a model can lift. On YouTube that chunk is the transcript, not the footage.

## Step 1: Answer one question per video, answer-first

Pick a single question the video answers and make it obvious. Use a question-shaped title that matches how people ask ("How do you clean a cast-iron pan?"), and state the direct answer in the first 20–30 seconds of speech, before the intro and backstory. AI Overviews assemble answers from a [query fan-out](/glossary/query-fan-out) of sub-questions, so a video that resolves one sub-question cleanly is a candidate; a rambling ten-minute video that buries the answer at 6:40 is not. One video, one question, answer first.

## Step 2: Give engines a clean, accurate transcript

The text is what gets retrieved, so the transcript is the asset. Auto-generated captions are a starting point, but they drop punctuation and mis-hear names and numbers, which is exactly the detail an AI answer needs to lift a claim. Upload a corrected transcript (or a caption file) so the spoken answer is machine-readable and quotable. Say specific, [citable](/glossary/citation) things out loud, named entities, dated facts, and figures, because a model can only pull a specific claim if the words are actually there in the text.

## Step 3: Structure the video with chapters and a fact-rich description

Break the video into chapters with timestamps so a specific moment can be located and lifted, and write a description that states the key facts in text rather than teasing them. Treat the description like a short answer-first summary: the main takeaway first, then the supporting points as a short list. This gives engines a text version of the video's structure to retrieve from, and it mirrors the [answer-first, extractable-chunk](/blog/how-to-get-cited-by-ai) discipline that wins citations for written pages.

## Step 4: Add VideoObject structured data on the page that embeds it

Wherever you embed the video on your own site, add `VideoObject` [structured data](/glossary/structured-data) describing the title, description, thumbnail, upload date, and, where supported, the transcript and key moments. This labels what the video is so engines don't have to infer it, and it exposes the facts even when the player itself isn't parsed. Put the transcript in on-page text too, so the embedding page is a self-contained, extractable source in its own right. Our guide to [prioritising your structured data](/blog/prioritize-your-structured-data) covers how to decide which schema is worth the effort.

## Step 5: Build the entity signals that make video pay off

Video works best when it reinforces a consistent brand entity. A separate Ahrefs study of 75,000 brands (released May 2026) reported that YouTube mentions correlated with AI brand visibility more strongly than any other metric, while link volume and total page count correlated only weakly. Name your brand and products consistently across the channel, video, transcript, and description, so the co-occurrence is unmistakable. That consistency is what compounds into [entity strength for AI search](/glossary/entity-authority), the durable signal engines lean on when deciding whom to name.

## What this method won't do

Be honest about scope. This is weighted toward Google's AI Overviews, where YouTube leads because Google owns it. Other engines weight sources differently, ChatGPT and Perplexity lean harder on text, community, and reference sites, so video is an addition to your text pages, not a replacement for them. Video also inherits the usual [crawl-to-cite lag](/blog/content-freshness-citation-cliff): heavy views before any citation is normal, not failure. Publish extractable video as one more retrievable format, then measure whether it actually earns you mentions.

Video is the most-cited surface in Google's AI answers and one of the least contested, but a citation still goes to the clearest, most extractable source, on whichever engine is answering. Knowing whether your video, and everything else you publish, is actually being cited across engines over time is what **Buffy Intel** measures. Structure the video for the answer; verify it earned one.

## How to get your brand cited by AI engines
Source: https://heybuffy.com/blog/how-to-get-cited-by-ai

In the [previous article](/blog/how-ai-engines-choose-brands) we covered *how* AI engines decide who to recommend. This one turns that into a playbook. The moves have a natural order. Earlier ones unlock the later ones.

## 1. Get reachable (the prerequisite)

None of the rest matters if the engine can't fetch your page.

- Confirm AI crawlers are **allowed**: both in `robots.txt` and at your CDN. (A CDN can silently 403 them even when robots.txt says yes. See [is your CDN blocking AI crawlers?](/blog/is-your-cdn-blocking-ai-crawlers).)
- Decide which bots you want across the [train / index / answer lifecycle](/blog/ai-crawler-lifecycle). At minimum allow the index and answer bots.
- Make key content **server-rendered**, not locked behind JavaScript a crawler won't execute.

## 2. Get parseable (structure for retrieval)

Retrieval works on passages, so write so an engine can lift a clean answer:

- **Answer-first.** Lead a section with the direct answer, then explain. Don't bury it.
- **Question-style headings** that match how people ask ("How much does X cost?").
- **[Schema markup](/glossary/structured-data)**: Product, FAQPage, Organization, Article, so machines know what each thing *is*.
- **Self-contained chunks.** One section should answer one question without needing the rest of the page.

## 3. Get specific (give them something quotable)

Engines favour verifiable, numeric, named claims. Replace vague marketing lines with concrete ones:

- ✗ "trusted by leading brands" → ✓ "used by 40 D2C beauty brands across 6 markets"
- ✗ "fast setup" → ✓ "live in under 5 minutes, no developer required"

Specific claims get pulled into answers; vague ones get skipped.

## 4. Get corroborated (the lever brands underuse)

This is the big one most teams miss. AI engines lean heavily on **third-party** authoritative sources, not just your own site. A claim echoed on Reddit, G2, review sites, and press reads as *corroborated*; the same claim only on your own page reads as a lone assertion.

- Pursue earned mentions and reviews.
- Get **into independent "best [category]" roundups**: for buyer queries these get cited far more than your own pages ([here's why](/blog/why-ai-loves-listicles)).
- Keep your brand facts **consistent** everywhere they appear, so the web tells one coherent story about you.

## 5. Build entity strength (the slow compounding one)

The engines reward brands that are well-established *[entities](/glossary/entity-authority)*: a Wikipedia/Wikidata presence, steady brand search volume, consistent co-occurrence with your category. This is slow, but it's what makes a model "know" you well enough to recommend you unprompted.

## 6. Stay fresh

There's roughly a **three-month citation cliff**: content decays if you publish and forget. Refresh your most important pages on a cadence; updated, accurate pages win live retrieval over stale ones.

> Order matters: reachable → parseable → specific → corroborated → entity → fresh. Skipping to "write more content" before you're reachable and parseable is the most common wasted effort in GEO.

Work the list top to bottom and you move from invisible to citable. The part teams can't do by eye. Knowing *which* of these is actually holding you back, on *which* engine. Is what [measuring your AI visibility](/blog/how-to-measure-ai-visibility) (and **Buffy Intel**) is for.

## How to get cited in Claude (and why it leans on Brave Search)
Source: https://heybuffy.com/blog/how-to-get-cited-in-claude

[Claude](/blog/how-claude-web-search-works) answers current questions by searching the live web, synthesising what it finds, and showing [citations](/glossary/citation) to the pages it used. The twist that sets it apart from the other engines: as of mid-2026, that search appears to be powered by **Brave Search's independent index**: not Google's, not Bing's. This is part 7 of the engine guides, and getting cited in Claude means understanding both how Claude retrieves and how Brave indexes.

## Does Claude really use Brave Search?

The evidence is strong but unofficial. Three independent signals point the same way:

- **The subprocessor list.** Anthropic added "Brave Search" to its public subprocessor list in **March 2025**: the partners that process Claude data. Programmer Simon Willison and TechCrunch reported the addition at the time, alongside identical citations appearing in Claude and Brave for the same query.
- **The internal parameter.** Testers found a setting named `BraveSearchParams` inside Claude's own web-search tool. A strong hint about what supplies the results.
- **The citation overlap.** [Profound](/blog/ai-search-statistics-2026) (Josh Blyskal, mid-2026) reported that **79.2% of Claude's citations came directly from Brave's top-ten results** for the equivalent search, with a measured **86.7% overlap** (13 of 15 results) and "no meaningful reranking." No other major model tracks its search provider this closely.

Treat this as well-corroborated but **not officially confirmed by Anthropic**, and expect the arrangement to evolve. The Profound figures are single-vendor and self-reported. Directionally credible, not gospel. The durable takeaway survives the caveats: Claude's live answers lean on an index that is *not Google's*.

## How does Claude's web search work?

Claude blends two sources, much like ChatGPT:

1. **Trained knowledge.** Anthropic's training crawler, `ClaudeBot`, reads the open web; what it learns becomes Claude's baked-in picture of your brand. This has no citations and updates slowly, on model releases.
2. **Live web search.** For current or comparative questions, Claude searches the web. Apparently via Brave, and grounds the answer in retrieved pages. These answers carry citations through Anthropic's Citations API, which returns a short `cited_text` span (about 150 characters in practice) tied to each source URL.

A single question is decomposed through [query fan-out](/blog/how-query-fan-out-works) into several sub-queries, each retrieving its own sources, then synthesised into one [grounded](/glossary/grounding) answer. So one buying question becomes several retrievals, and several chances to be cited.

> Claude's web search appears to read from Brave's index, not Google's. If your Google rank is strong but Brave barely knows you, Claude may never see the page Google loves.

## What gets cited in Claude?

Claude narrows many candidate passages to the handful it quotes. The selectors are the familiar five quality bars, but filtered through Brave's retrieval first:

| Selector | What it means for your page |
|---|---|
| Present in Brave | Reachable and indexed by Brave's independent crawl, not just Google |
| Extractable | Answer-first passages a 150-char citation can lift cleanly |
| Specific | Numeric, named, dated claims; vague marketing copy gets skipped |
| Structured | Schema, tables, and clean markup Brave extracts well (see below) |
| Corroborated | Agreed by [multiple credible sources](/glossary/corroboration), not a lone claim |

For "best X" and comparison questions, Claude. Like every engine. Leans on independent roundups and community threads, so [earned placement in the lists it cites](/blog/why-ai-loves-listicles) matters alongside your own pages.

## How do you rank in Brave's index?

Brave publishes no ranking guidelines, so nobody optimises Brave directly. But Brave is unusually open about *how it reads pages*, which tells you what to give it. Per Brave's own Search API documentation (mid-2026):

- **It is a genuinely independent index**: Brave reports **over 30 billion pages**, refreshed by "100 million page updates a day," built from its own crawl plus anonymised data contributed by Brave browser users. Being in Google's index does not put you in Brave's.
- **It sells an "LLM context" / AI-grounding endpoint** designed to feed models clean, factual, real-time content and cut hallucinations. The exact surface a tool like Claude would consume.
- **It prioritises structured extraction.** Brave's docs emphasise schema-enriched results. JSON-LD [structured data](/glossary/structured-data), tables (down to row-level granularity), forum discussions, and clean query-optimised text snippets. Pages that expose facts in structured, extractable form are easier for Brave to represent well.

The practical reading: the same GEO fundamentals win here, with extra weight on **being reachable to crawlers generally** (don't assume Google access equals Brave access) and on **clean structured data** that Brave parses cleanly.

## The playbook to get cited in Claude

1. **Open the gates wide, for everyone.** Allow `ClaudeBot` and confirm your CDN isn't [silently 403-ing AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers); the [crawler directory](/blog/ai-crawler-user-agent-directory) has the tokens. Because Claude leans on Brave, also make sure you aren't blocking general web crawlers. A narrow allowlist that only admits Google can leave you invisible in Brave's index.
2. **Don't assume Google coverage equals Brave coverage.** Search your key terms on Brave Search directly and see whether your pages appear. If they don't, the cause is upstream of anything Claude does.
3. **Write answer-first.** Lead each section with the direct answer in 40-60 words so the ~150-character `cited_text` span has a clean sentence to lift.
4. **Mark up your facts.** Add JSON-LD schema, put specs and comparisons in real tables, and keep forum-style Q&A crawlable. The formats Brave's docs say it extracts best.
5. **Date and corroborate claims.** Specific, dated, source-attributed statements survive retrieval; unattributable numbers get cut.
6. **Pursue earned coverage** in the reviews and roundups Claude cites for your category. [Third-party sources win the "best" questions](/blog/get-into-ai-cited-best-lists).
7. **Keep competitive pages fresh** so live retrieval keeps finding current, dated content before they [fall off the citation cliff](/blog/content-freshness-citation-cliff).

For a contrast, [Perplexity](/blog/how-to-get-cited-in-perplexity) cites from its own blended retrieval and [Google AI Mode](/blog/how-google-ai-mode-works) grounds in Google's index, so the same page can win in one engine and lose in another. That divergence is exactly why single-engine checks mislead.

## How do you measure your Claude visibility?

Ask Claude your highest-intent customer questions, repeatedly, and track two things over time: whether your **brand is named** and whether **your pages are cited** as sources, then compare that against the same prompts in ChatGPT, Perplexity, and Google's surfaces, since Claude's Brave-grounded answers will diverge from the Google-grounded ones. That cross-engine, multi-prompt read. Presence, citations, and sentiment tracked daily rather than spot-checked. Is exactly what **Buffy Intel** is built for.

## How to get cited in Google Gemini
Source: https://heybuffy.com/blog/how-to-get-cited-in-gemini

[Google Gemini](/glossary/google-ai-mode) is Google's standalone AI assistant. The app you open directly on the web, on mobile, or built into Chrome and Workspace. It grounds its answers in live Google Search and shows [citations](/glossary/citation) to the pages it used. This is part 6 of the engine guides, and the key thing to get straight first is that Gemini is *not* the same surface as the AI features inside Search.

## How is Gemini different from AI Mode and AI Overviews?

All three are Gemini-powered and grounded in Google's index, but they are distinct surfaces:

| Surface | Where it lives | What it is |
|---|---|---|
| Gemini app | Standalone assistant (web, mobile, Chrome, Workspace) | A full conversational assistant for any task, not only search |
| [AI Mode](/blog/how-google-ai-mode-works) | A tab inside Google Search | Conversational search. Multi-turn research over the index |
| [AI Overviews](/blog/ai-overviews-complete-guide) | A summary block above normal results | A short synthesised answer on the results page |

The optimisation work is largely shared because all three ground in Google Search, but they are different entry points, and a brand can be present in one and absent in another. Gemini also reaches beyond search: it summarises documents, drafts in Workspace, and (via "Summarize with Gemini") reads the page a user is on in Chrome.

## How does grounding in Gemini work?

When a question benefits from live information, Gemini uses **Grounding with Google Search**. Per Google's developer documentation (as of mid-2026), the flow is automatic:

- **The model decides if it needs to search.** For current, comparative, or factual questions it generates one or more search queries itself. A form of [query fan-out](/glossary/query-fan-out).
- **It retrieves and synthesises** results from Google's index, then writes a grounded answer.
- **It returns inline citations.** The response carries *grounding chunks* (each a web source with a URL and title) and *grounding supports* that tie a passage of the answer back to specific sources.

Stable, general questions ("what is GEO?") may be answered from Gemini's trained knowledge instead, which has a [knowledge cutoff](/glossary/knowledge-cutoff) and no citations. So you need to be both *learned* by the model and *retrievable* at answer time.

> Because Gemini grounds in Google Search, your Google authority carries over, but the prize is the cited passage on a specific sub-question, not your overall rank.

## What gets cited in Gemini?

The selectors mirror the rest of Google's AI surfaces, because the index is shared:

- **Indexable and reachable.** If Googlebot and Google's AI crawlers can't reach a page, it can't be grounded. Confirm you aren't [blocking them at the CDN](/blog/is-your-cdn-blocking-ai-crawlers).
- **Answer-first and extractable.** Sections that open with a direct answer, with facts in lists and tables, get lifted; buried answers don't.
- **Strong as an entity.** Brands that are [consistently named and corroborated across the web](/blog/entity-strength-ai) get named confidently; inconsistently-described ones get garbled or skipped.
- **Fresh.** Live grounding favours recently updated pages; stale content [decays out of answers](/blog/content-freshness-citation-cliff) within months.
- **Deep on the follow-ups.** Because Gemini is conversational, it fans out again on each turn, so cover the comparisons, objections, and how-tos, not just the headline question.

## The playbook to get cited in Gemini

1. **Stay indexable.** Keep Google's crawlers unblocked and your key pages in Google's index. Grounding can only cite what Search can retrieve.
2. **Win your owned questions on your pages.** Brand, product, and feature questions should be answered answer-first on your own site, with [structured data](/glossary/structured-data) and the fan-out branches covered.
3. **Cover the conversation, not one query.** Build interlinked content that answers a topic's follow-ups, so you stay cited from turn one to turn three.
4. **Fix your entity.** One consistent brand name and a clear "what we are" description across your site and profiles, so Gemini can pin down who you are.
5. **Pursue earned coverage** in the independent roundups and communities Google's surfaces cite for category questions. Your own pages win brand and feature queries; [third-party sources win the "best" ones](/blog/why-ai-loves-listicles).
6. **Keep competitive pages fresh** with substantive updates, not date bumps.

For the other chat engines, see the [ChatGPT](/blog/how-to-get-recommended-in-chatgpt), [Perplexity](/blog/how-to-get-cited-in-perplexity), and [Claude](/blog/how-to-get-cited-in-claude) guides. Each grounds differently, so the same page can win in one and lose in another.

## How do you measure your Gemini visibility?

Gemini answers shift by phrasing, by user context, and over time, so a single check tells you little. Take your highest-intent customer questions, ask them across the Gemini app *and* AI Mode (they can diverge), and track over time whether your **brand is named** and whether **your pages are cited**. That cross-engine, multi-prompt read. Presence, citations, and sentiment tracked daily rather than spot-checked. Is exactly what **Buffy Intel** is built for.

## How to get cited in Google AI Mode
Source: https://heybuffy.com/blog/how-to-get-cited-in-google-ai-mode

To get cited in Google AI Mode, make your pages the **clean, extractable answer to the specific sub-questions your customers ask**: because AI Mode reaches well beyond the top-10 blue links to build its answers. Only about **19% of AI Mode citations come from the organic top-20** (seoClarity, Sep 2025), so classic ranking is not the path it once was. This is part 8 of our engine guides, and AI Mode is the surface where the gap between "ranks well" and "gets cited" is widest.

If you want the mechanics of the surface first, start with [how Google AI Mode works](/blog/how-google-ai-mode-works); for the data on how differently it cites from AI Overviews, see [do AI Mode and AI Overviews cite the same sources](/blog/ai-mode-vs-ai-overviews-citations). This guide is the playbook.

## How does AI Mode decide what to cite?

AI Mode is Google's **Gemini-powered conversational search**: a chat that researches, synthesises and cites across many sub-queries, rather than returning a page of links. Three traits shape what it quotes:

- **Heavy [query fan-out](/blog/how-query-fan-out-works).** One question is decomposed into many sub-queries, each retrieving its own sources, which are synthesised into a single answer with a combined citation set. It cites the best passage per branch, not the best-ranking page overall.
- **Loose coupling to classic rank.** Because it fans out, it routinely cites pages outside the top-10. In seoClarity's data the organic #1 was cited only about **25%** of the time, #2 ~21%, #3 ~16%. An edge, not a lock.
- **Grounding in Google's index with Gemini's judgment.** It carries some of Google's ranking signals across, but the final selection favours the passage that most cleanly answers the sub-question.

The practical read: you don't win AI Mode by ranking #1 for the head term. You win it by being the extractable answer to the **branch questions** the fan-out generates.

## What gets a page cited in AI Mode?

The same five quality bars that govern AI citation generally, weighted toward retrieval and sub-question coverage:

| Selector | What it means for your page |
|---|---|
| Reachable | Not blocked to Google's crawlers; server-rendered HTML, not JS-only |
| Extractable | Answer-first passages (40-60 words), real headings, facts in lists and tables |
| Sub-question complete | Covers the predictable branches. Uses, comparisons, cost, how-to, who-it's-for |
| Corroborated | Agreed by [multiple credible sources](/glossary/corroboration), so the model trusts it |
| Fresh | Recently updated; live retrieval [decays stale pages](/blog/content-freshness-citation-cliff) |

## The playbook to get cited in Google AI Mode

1. **Open the gates.** Confirm Google's crawlers reach your pages and your CDN isn't [silently blocking them](/blog/is-your-cdn-blocking-ai-crawlers). A page that can't be fetched can't be cited on any surface.
2. **Answer the fan-out, not just the head query.** For each core topic, cover the branch questions. Comparisons, cost, prerequisites, how-to, who-it's-for. Each as its own self-contained, answer-first chunk. AI Mode retrieves per sub-query, so breadth of clean answers wins more citations than one long page.
3. **Lead every section with the direct answer** in 40-60 words, then explain. AI Mode lifts the clean passage, not the buried one.
4. **Put facts in tables and lists.** Specs, steps and criteria are quoted far more readily than the same facts narrated in prose.
5. **Build [entity strength](/blog/entity-strength-ai).** It's the layer that keeps you *recommended* across surfaces even when the exact cited URL shifts. The one lever that travels from AI Overviews to AI Mode and beyond.
6. **Don't assume an AI Overview win covers you here.** The two surfaces share only about 59% of sources; verify AI Mode separately and fill the gaps.
7. **Keep competitive pages fresh** so live retrieval keeps finding current, dated content on your branch questions.

## How is AI Mode different from AI Overviews and the chat engines?

[AI Overviews](/blog/how-to-optimize-for-ai-overviews) still track organic rankings closely (about 56% of their citations come from the top-20), so classic SEO carries over there more directly. [ChatGPT](/blog/how-to-get-recommended-in-chatgpt) blends trained knowledge with live search and doesn't always cite; [Perplexity](/blog/how-to-get-cited-in-perplexity) grounds and shows sources on nearly every answer. AI Mode sits between them: **fully conversational and citation-showing like Perplexity, but grounded in Google's index and carrying some of Google's signals**: with a fan-out that reaches far past the top-10. Optimise the shared fundamentals once; then win AI Mode specifically by covering the sub-question tree.

## How do you measure your AI Mode visibility?

Snapshot your highest-intent customer questions in AI Mode on a schedule and track two things per prompt: whether your **brand is named** and whether **your pages are cited**: repeated captures, since answers drift by phrasing, time and follow-up. Google Search Console's [generative-AI performance view](/blog/google-search-console-ai-performance-report) reports AI Mode and AI Overview impressions together (no clicks, no query terms), a useful but blunt first-party signal.

> AI Mode rewards the site that has already answered the follow-up question. Rank buys you a chance; a clean answer to the exact sub-query is what actually gets quoted.

That cross-engine, multi-prompt read. Presence and citations on AI Mode tracked as its own line, alongside every other surface, daily rather than spot-checked. Is exactly what **Buffy Intel** is built for.

## How to get cited in Perplexity
Source: https://heybuffy.com/blog/how-to-get-cited-in-perplexity

[Perplexity](/blog/chatgpt-vs-google-vs-perplexity-product-discovery) is an answer engine: it responds to a question by searching the live web, synthesising what it finds, and showing numbered [citations](/glossary/citation) to the pages it used. Because every answer is grounded and sourced, getting *cited* is not a side effect of visibility in Perplexity. It **is** the visibility. This is part 5 of the engine guides, and it's the engine where citation mechanics are most transparent.

## How does Perplexity work?

Perplexity sits closer to "research assistant" than "chatbot." Three traits define it:

- **Citation-first by design.** Nearly every answer is [grounded](/glossary/grounding) in retrieved web pages and shows inline, numbered sources, so you can see precisely which pages an answer was built from.
- **Heavy [query fan-out](/blog/how-query-fan-out-works).** A single question is decomposed into multiple sub-queries, each retrieving its own sources, which are then synthesised into one answer with a combined source list.
- **Its own crawlers.** Perplexity documents two user-agents in our [crawler directory](/blog/ai-crawler-user-agent-directory): `PerplexityBot`, which builds the search index, and `Perplexity-User`, which fetches a specific page on demand at answer time. If either is blocked, you can't be cited.

As of mid-2026 Perplexity also layers in shopping and follow-up features (product cards, "buy" flows for Pro users, multi-turn refinement). Those surfaces evolve quickly, but the inputs don't change: reachable, accurate, extractable pages that a synthesiser can quote.

## What gets cited in Perplexity?

Perplexity narrows hundreds of candidate passages to the handful it quotes. The consistent selectors are the same five quality bars that govern AI citation generally, weighted toward retrieval:

| Selector | What it means for your page |
|---|---|
| Reachable | Not blocked to PerplexityBot/Perplexity-User; server-rendered HTML, not JS-only |
| Extractable | Answer-first passages, real headings, facts in lists and tables |
| Specific | Numeric, named, dated claims. Vague marketing copy gets skipped |
| Corroborated | Agreed by [multiple credible sources](/glossary/corroboration), not a lone assertion |
| Fresh | Recently updated; live retrieval [decays stale pages](/blog/content-freshness-citation-cliff) |

Perplexity also leans visibly on third-party and community sources for opinion-shaped questions. Reviews, roundups, and forum threads, so [earned placement in the lists it cites](/blog/why-ai-loves-listicles) matters as much as your own pages.

> In Perplexity there is no "page one" to win. There is a source list of five or six links per answer. Your job is to be one of them, on the questions your customers actually ask.

## How is it different from ChatGPT and Google AI Mode?

[ChatGPT](/blog/how-to-get-recommended-in-chatgpt) blends trained knowledge with live search and doesn't always cite; [Google AI Mode](/blog/how-google-ai-mode-works) grounds answers in Google's index and carries Google's ranking signals across. Perplexity is the most purely retrieval-and-citation-driven of the three: little baked-in opinion, almost everything grounded and shown. The practical upshot. Perplexity rewards clean, quotable, well-corroborated passages faster than entity reputation alone, which makes it a useful early signal for whether your content is genuinely extractable. For a side-by-side of all three on shopping intent, see our [product-discovery comparison](/blog/chatgpt-vs-google-vs-perplexity-product-discovery).

## The playbook to get cited in Perplexity

1. **Open the gates.** Allow `PerplexityBot` and `Perplexity-User` in robots.txt and verify with real-user-agent fetches that your CDN isn't [silently 403-ing them](/blog/is-your-cdn-blocking-ai-crawlers).
2. **Make every key page answer-first.** Lead each section with the direct answer in 40-60 words; Perplexity lifts the clean passage, not the buried one.
3. **Put facts in tables and lists.** Specs, steps, and comparisons are quoted far more readily than the same facts narrated in prose.
4. **Date and corroborate your claims.** Specific, dated, source-attributed statements survive Perplexity's retrieval filter; unattributable numbers get cut.
5. **Pursue earned coverage** in the reviews, roundups, and communities Perplexity cites for your category. Owned pages win brand and feature questions; [third-party sources win the "best" questions](/blog/get-into-ai-cited-best-lists).
6. **Keep competitive pages fresh** so live retrieval keeps finding current, dated content.

## How do you measure your Perplexity visibility?

Because Perplexity shows its sources, it's the easiest engine to audit, but a single check tells you little, since answers shift by phrasing, time, and follow-up. Take your highest-intent customer questions, snapshot the answers across engines on a schedule, and track two things over time: whether your **brand is named** and whether **your pages are cited** as sources. That cross-engine, multi-prompt read. Presence, citations, and sentiment tracked daily rather than spot-checked. Is exactly what **Buffy Intel** is built for.

## How to get named, not just cited, in AI answers
Source: https://heybuffy.com/blog/how-to-get-named-in-ai-answers

Being cited is not being named. An AI engine can lift a fact from your page, link it as a source, and never say who you are. A [ghost citation](/glossary/ghost-citation), and by one June 2026 count the single most common way brands appear in AI answers. **This playbook closes that gap: it's about making your brand name travel with your facts, so the engine attributes the claim to you instead of quietly using it.** It's the action companion to [ghost citations: cited but not named](/blog/ghost-citations-cited-not-named); the moves build on each other, roughly in order of leverage.

## 1. Bind your name to the fact on the page

The root cause is paraphrase: the model restates your fact in its own words, and if your name wasn't part of the claim, nothing survives to attribute. So write the claim and the source as one unit.

- Attribute your own data in-sentence: "**Buffy Intel's** mid-2026 analysis found…", not a free-floating statistic.
- Put the brand name near the numbers, in prose and in table captions, not only in the logo and footer.
- Use subject-predicate-object statements the model can lift whole ("Buffy Intel tracks AI visibility daily"), so the sentence carries the name if it's quoted.

The test: could a model copy your key sentence verbatim and still know who said it? If the name only lives in the page chrome, expect a ghost citation.

## 2. Be the origin of the claim, not a rehasher

Engines are far likelier to name the source of an *original* fact than to name the tenth site to repeat it. If you're restating someone else's number, the engine will (rightly) attribute it to them.

- Publish first-hand data, benchmarks, or definitions others don't have. The [original-data formats](/blog/from-clicks-to-citations) that get named because you're the only source.
- Coin and consistently use precise terms for concepts you own; a named concept carries its namer.
- Where you must cite others, add your own analysis on top, so there's a claim that is genuinely yours to name.

## 3. Strengthen the entity so the model associates the topic with you

Naming is an entity decision. A model names a brand when it's confident that brand *is* part of the answer, which is [entity strength](/blog/entity-strength-ai), the slowest but most durable lever.

- Ship consistent [Organization and author schema](/glossary/structured-data) so machines resolve "who" unambiguously.
- Keep naming consistent across your own site, profiles, and third-party mentions. Alternating names dilutes the association.
- Build knowledge-graph presence and topic co-occurrence so your name and your category are linked in the model's representation, not just on your pages.

## 4. Earn corroboration that repeats your name

The name that recurs across independent sources is the one a model learns to attach to a topic. This is the same [corroboration](/glossary/corroboration) mechanism that decides citations. Pointed at your name rather than your links.

- Pursue earned mentions in third-party coverage, reviews, and community discussion where your brand is *named*, not just linked.
- Aim for your name and your key facts to co-occur across sources, so the association is corroborated rather than self-asserted.
- Don't fake it: manufactured mentions get discounted, and [gaming the signal backfires](/blog/why-buying-aged-reddit-accounts-backfires).

## 5. Measure mention rate as its own line

You can't close a gap you don't track. Citation rate and mention rate decouple. The June 2026 Semrush study found a ~74.9% citation rate against a ~38.3% mention rate across four engines, with Gemini and ChatGPT nearly mirror-imaged, so measuring one hides the other.

| Metric | The question it answers | When it's low |
|---|---|---|
| Citation rate | Is my page used as a source? | Supply problem: reachability, extractability, freshness |
| Mention rate | Does the answer say my name? | Entity problem: weak association, no on-page attribution |

Track both, per engine and per market, and watch the mention rate climb toward the citation rate. That closing gap is the signal the work above is landing. This is exactly the [two-lens split](/blog/brand-mention-gap-vs-source-gap). Supply versus demand. Measured over time.

> Earning the citation is a content job; earning the name is an entity job. Make your brand name part of the fact on the page, be the origin of claims worth repeating, and let corroboration make the association stick, then measure the name, not just the link.

## What not to do

Don't chase the mention with tricks. Stuffing your brand name into every sentence reads as spam to both readers and models and won't survive paraphrase; buying mentions gets discounted the same way [manufactured citations do](/blog/can-ai-search-be-manipulated). The honest levers. Own the fact, attribute it to yourself, build the entity, earn corroboration. Are the ones that compound.

Getting named is a different discipline from getting cited, and it needs its own number on the dashboard. Tracking mention rate against citation rate, per engine and per market, is what **Buffy Intel** is built to do. Questions: support@flash.tech.

## How to get your brand recommended in ChatGPT
Source: https://heybuffy.com/blog/how-to-get-recommended-in-chatgpt

ChatGPT is the largest AI answer surface there is, and for a growing share of shoppers it's the first place a buying question gets asked. Getting recommended in it isn't a trick. It's the result of being **learnable** by the model, **retrievable** by its search layer, and **corroborated** by the sources it trusts. This guide covers how the machine works and the playbook that follows.

## How does ChatGPT decide what to say about brands?

Two pipelines feed an answer, and they reward different work:

1. **Trained knowledge.** OpenAI's training crawler, `GPTBot`, reads the open web; what it learns becomes the model's baked-in picture of your brand. Who you are, what you sell, how you're positioned. This picture updates slowly (model releases, not news cycles) and has no citations. If the model never learned you exist, you start every answer from zero.
2. **Live search.** For current, comparative, or factual questions, ChatGPT searches the web: an index fed by `OAI-SearchBot`, plus on-demand page fetches by `ChatGPT-User` when a user or the model opens a specific page. These answers carry **citations**: and the [fan-out](/blog/how-query-fan-out-works) means one shopping question becomes several sub-queries, each retrieving its own sources.

For shopping intents specifically, ChatGPT increasingly renders product results. Cards with images, prices, and links, assembled from merchant data and the open web (and, with the [Agentic Commerce Protocol](/blog/agentic-commerce-protocol-acp), a path to checkout inside the chat). The details keep evolving; the inputs don't: structured, accurate, reachable product data.

> ChatGPT doesn't rank ten blue links. It forms an opinion. Your job is to make sure that opinion was learned from you and your best coverage, not assembled from whatever it could find.

## What actually drives its recommendations?

Across the recommendation queries we track daily, the consistent drivers are:

- **Entity strength.** Brands the model "knows". [Consistently named, corroborated across many sources](/blog/entity-strength-ai). Get named confidently. Obscure or inconsistently-described brands get skipped or garbled.
- **Third-party corroboration.** For "best X" questions, ChatGPT leans hard on independent roundups, reviews, and community threads. [Listicles get cited several times more often than brand-owned pages](/blog/why-ai-loves-listicles) on commercial queries. Your own site wins the *brand and feature* questions; earned coverage wins the *category* ones.
- **Freshness.** Live-search citations skew heavily toward recently published or updated pages. Stale content [falls off a citation cliff](/blog/content-freshness-citation-cliff) within months.
- **Extractability.** Pages that answer a sub-question cleanly. A spec table, an answer-first paragraph, a real FAQ. Get lifted; pages that bury the answer don't.

## The playbook, in order

1. **Open the gates.** Allow `GPTBot`, `OAI-SearchBot`, and `ChatGPT-User` in robots.txt, and verify with real-user-agent fetches that your CDN isn't [silently 403-ing them](/blog/is-your-cdn-blocking-ai-crawlers). The [crawler directory](/blog/ai-crawler-user-agent-directory) has every token.
2. **Fix your entity.** One consistent brand name, a clear "what we are" sentence on your about/home pages, identical descriptions across your site, marketplaces, and profiles. The model can't recommend what it can't pin down.
3. **Win your owned queries.** Brand, product, and feature questions ("does X work for oily skin?", "X vs the older model") should be answered on *your* pages. Answer-first, with [structured data](/glossary/structured-data), covering the fan-out branches: uses, comparisons, ingredients/specs, who-it's-for.
4. **Make the catalog legible.** For shopping surfaces, [your product data is the storefront](/blog/prepare-product-catalog-for-ai-agents): complete attributes, conversational context, FAQs, reviews as crawlable text.
5. **Pursue earned coverage.** Pitch the independent roundups, reviewers, and communities that dominate category-level citations. This is PR work, but it's now also AI-visibility work.
6. **Refresh what matters.** Put competitive pages on a substantive update cadence so live search keeps finding current, dated content.
7. **Measure inside the answers.** Ask the engine your customers' questions, repeatedly, and track [presence, citations, and sentiment over time](/blog/how-to-measure-ai-visibility). ChatGPT is non-deterministic, so a single spot-check tells you almost nothing.

## What to do next

Run the gate check first (step 1). It takes ten minutes and it's the most common silent failure. Then pick your ten highest-intent buying questions and ask ChatGPT each one: note whether you appear, who gets cited, and how you're described. That baseline. Tracked daily across ChatGPT and every other engine, with the gaps turned into prioritised fixes. Is exactly what **Buffy Intel** does.

## How to measure your AI visibility
Source: https://heybuffy.com/blog/how-to-measure-ai-visibility

Once a brand accepts that AI answers matter, the next question is unavoidable: *how do we even measure this?* "AI visibility" isn't one number. It breaks into a handful of concrete things, each answering a different question.

## The five things worth tracking

Each answers a different question. You need the set, not a single number:

| Metric | The question it answers | Why it matters |
|---|---|---|
| Presence | Do you appear at all? | The floor, if you're not mentioned, nothing else counts. |
| [Share of Voice](/glossary/share-of-voice) | How do you stack up vs competitors? | Whether you're winning or losing the category's AI conversation. |
| [Citation Coverage](/glossary/citation-coverage) | Is your *own site* the source? | Being **cited**, not just mentioned, is a concrete trust signal. |
| [Brand Perception](/glossary/brand-perception) | *How* are you described? | "Premium" vs "budget" vs "dated". Framing shapes buyers before a human does. |
| Consistency | How reliable is all of the above? | AI is non-deterministic; reproducibility matters as much as any single reading. |

## Three things that make this hard to eyeball

1. **Non-determinism.** The same prompt yields different answers across attempts. One check tells you almost nothing; you need repeated sampling to see the real pattern.
2. **The engines disagree.** ChatGPT, Gemini, Claude, and Google's AI surfaces are built differently and will describe and rank you differently ([here's why](/blog/why-ai-cites-one-brand)). A single-engine check is a third of the picture, at best.
3. **The surface is huge.** "The questions that matter" run into the hundreds once you account for every product, use case, comparison, and the way real people phrase things. You can't hand-check that, and you can't hand-track it week over week.

> A screenshot of one good answer is a vanity metric. The thing that's actually decision-useful is the **trend**: presence, share of voice, sentiment, and citations, sampled repeatedly, across every engine, over time.

## From measurement to action

Measurement only earns its keep if it points at what to fix. The useful loop is: track the five metrics across engines → spot where you're absent, losing share, or framed badly → trace it to a cause (crawler access? thin/unstructured content? weak entity strength? a single under-performing engine?) → fix → watch the number move.

Doing that by hand. Hundreds of prompts, multiple samples each, across five engines, every day, turned into a trend and a prioritised fix list. Is exactly the job **Buffy Intel** automates.

## How to optimize for Google AI Overviews
Source: https://heybuffy.com/blog/how-to-optimize-for-ai-overviews

Optimising for [AI Overviews](/glossary/ai-overviews) is less exotic than it sounds: because they're grounded in Google's index, the work is mostly *strong SEO plus extractability*. Here's the checklist, in order.

## 1. Be eligible

Overviews pull from Google's index, so the prerequisites are the classic ones: your page is **indexable, crawlable, fast, and ranks** for the topic. If you don't show up in Search at all, you won't show up in the Overview. (And confirm AI/Google crawlers aren't blocked. In robots.txt or [at your CDN](/blog/is-your-cdn-blocking-ai-crawlers).)

## 2. Lead with the answer

Overviews quote **extractable passages**. Open each section with the direct answer in ~40-60 words, then elaborate. Use **question-style H2s** that match how people ask ("How long does X take?"). One self-contained answer per section. The same discipline that wins featured snippets.

## 3. Structure the facts

- Put specs, steps, and comparisons in **tables and lists**, not prose.
- Add **[structured data](/glossary/structured-data)**: `FAQPage` for Q&A blocks (engines love to lift these), `Article`, `Product` where relevant.
- Keep paragraphs short and one-idea-each so a clean chunk can be pulled.

## 4. Be specific and sourced

Vague claims get skipped; **specific, numeric, dated** ones get pulled. Replace "trusted by many" with "used by 40 D2C brands across 6 markets," and attribute data to its source. (More on this in [how to get cited by AI](/blog/how-to-get-cited-by-ai).)

## 5. Build authority and freshness

Overviews favour recognised, corroborated sources kept current. Strengthen your [entity](/glossary/entity-authority) (consistent facts across the web), earn third-party corroboration, and **refresh** competitive pages on a cadence. Recency is a ranking signal here too.

## 6. Cover the question, and its neighbours

Because Overviews are built by [query fan-out](/glossary/query-fan-out), answer the **sub-questions** around your topic, not just the head query. Interlinked content that covers the full intent wins more of the answer.

> AI Overview optimisation is 80% disciplined SEO (rank, be indexable, be authoritative) and 20% extractability (answer-first, structured, schema'd). If you're already strong in Search, you're most of the way there.

## Then measure

Optimising blind is guesswork. Track whether you're actually appearing and being cited in Overviews across the questions that matter, and what changed when you shipped a fix. That feedback loop is what [measuring AI visibility](/blog/how-to-measure-ai-visibility) (and **Buffy Intel**) is for.

## How to read an AI-visibility case study (using a 19-week Bing citation test)
Source: https://heybuffy.com/blog/how-to-read-an-ai-visibility-case-study

When a vendor reports that some change tripled their AI citations, the right first question isn't "how?". It's "compared to what, and how do they know it was the change?" A useful worked example landed in June 2026: a 19-week dataset, published by the brand-visibility platform waikay.io about its own site, reporting weekly Bing AI citations rising from a 167 average to 614. About a **3.7× lift**: after it added entity markup. It's a genuinely interesting result. It's also a textbook case for reading AI-visibility studies critically.

This is part of the [measuring AI visibility](/blog/from-clicks-to-citations) series, and a companion to [what Bing Webmaster Tools' AI data can tell you](/blog/bing-webmaster-tools-ai-visibility). The free, first-party source this study is built on. The goal here isn't to judge one vendor; it's a reusable lens for the flood of "we did X and citations jumped" posts.

## What did the case study report?

A large headline number, and a more complicated story underneath it. Over 19 weeks of Bing Webmaster Tools data. 11 weeks of baseline, the markup submitted in week 12, then 7 weeks after. The site reported the following, all attributed to waikay.io's own June-2026 write-up:

| Metric | Reported result |
|---|---|
| Weekly AI citations (avg) | 167 → 614 (~3.7×) |
| Citations per cited page (avg) | 3.65 → 8.55 |
| Peak weekly citations | 1,063 (week 19) |
| English-language raw volume | **down ~8%** |
| English citations by funnel stage | TOFU −80%, MOFU +44%, BOFU +406% |
| Share of total growth from non-English pages | ~75% (French + Spanish) |

The authors are commendably candid about the confounds: they note the non-English surge "likely" came from a deeper site re-crawl rather than the markup, and they list the limits themselves. A single domain, a short 7-week window, no controlled experiment. That candour is exactly what makes it a good teaching example.

## The four questions to ask of any AI-visibility case study

Run every "we did X, citations rose" claim through these four. The waikay study passes some and openly fails others, which is the point.

1. **Is there a control, or just a before-and-after?** A baseline isn't a control. If anything else changed in the window. A re-crawl, a freshness pass, a new backlink, an algorithm update. The before-and-after can't isolate the cause. Here the authors flag that a re-crawl plausibly drove ~75% of the lift, so the headline can't be cleanly credited to the markup.
2. **Who ran it, and do they sell what they measured?** Independence matters. This is a vendor measuring the effect of its own product on its own site. Self-reported, single-domain. That doesn't make it false; it makes it a hypothesis from an interested party, which is weaker evidence than an independent or [corroborated](/glossary/corroboration) result.
3. **Did the valuable citations move, or just the raw count?** Look at composition, not totals. English raw volume actually fell ~8%, while citations shifted down-funnel (commercial, bottom-of-funnel pages up sharply). Whether that's good depends on your goal, and it's invisible if you only read the 3.7× headline.
4. **Has it been replicated?** One site for seven weeks is an anecdote, not a pattern. A finding earns weight when it reproduces across domains and time. Until then, treat it as a prompt to run your own test.

> A 3.7× lift with no control, on one self-reported domain, where the vendor sells the thing being measured and a re-crawl could explain most of it, that's a hypothesis, not a proof. Read the limitations section as carefully as the headline.

## What's the durable takeaway, separate from the headline number?

Two things survive the scrutiny. First, **Bing Webmaster Tools is a real, free, first-party place to watch your own AI [citations](/glossary/citation) move**: which is why a study could be built on it at all, and why you can run the same before-and-after on your own site instead of trusting anyone's. Second, **citation totals and citation composition are different metrics.** A page can deepen. Earning more citations *per page*, as this site did (3.65 → 8.55). Even as raw volume dips, which echoes the broader pattern that focused, well-covered pages tend to be cited more thoroughly. That's a [citation-coverage](/glossary/citation-coverage) story, and it's more useful than any single multiplier.

What doesn't survive is the causal leap. "We added markup and citations tripled" quietly becomes "the markup tripled citations", and the authors' own re-crawl caveat shows why that step is unearned. The same discipline applies to the [entity-strength](/blog/entity-strength-ai) claims that fill this space: entity signals plausibly help, but proving it needs a control, not a coincidence.

## How to test a claim like this on your own site

Don't take the case study's word; reproduce the method honestly:

- **Establish a clear baseline** in [Bing Webmaster Tools](/blog/bing-webmaster-tools-ai-visibility) and your server logs before you change anything.
- **Change one thing at a time.** If you ship markup *and* trigger a re-crawl *and* add content in the same week, you've rebuilt the confound you were trying to avoid.
- **Watch composition, not just the total**: track citations per page and which funnel stages move, the way the [reporting stack](/blog/ai-visibility-reporting-stack) frames it, so a flat or falling raw count doesn't hide a real shift.
- **Give it time, and expect noise**: short windows over-read random spikes; citation activity is volatile, and [decays without freshness](/blog/content-freshness-citation-cliff).
- **Cross-check across engines.** Bing is one surface; a lift there may or may not show in Google AI Mode, Perplexity, or ChatGPT.

Reading case studies well is the same skill as [measuring your own AI visibility](/blog/how-to-measure-ai-visibility) well: insist on a baseline, separate correlation from cause, and watch composition over time across engines. Turning scattered per-engine signals into one honest, cross-engine scoreboard, so you can test what actually moves your citations instead of trusting a headline. Is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## How to see which AI bots are crawling your site
Source: https://heybuffy.com/blog/how-to-see-which-ai-bots-crawl-your-site

You don't have to guess whether AI engines can see your site. The evidence is already in your logs. Every well-behaved crawler announces itself by user-agent, and your server/CDN records each visit. Reading those logs is the fastest way to confirm you're actually reachable (and to catch a silent block before it costs you citations).

## Where to look

- **Server access logs.** Your web server (nginx, Apache) logs every request with its user-agent and the status code returned. Filter for AI crawler tokens.
- **CDN analytics.** If you're behind a CDN (Cloudflare, Fastly, etc.), its dashboard usually classifies bot traffic. Often with a dedicated "AI crawlers / AI bots" view.
- **A quick spot-check** without logs: impersonate a bot and read the status code directly (see below).

## What to filter for

Search your logs for the crawler tokens you care about (the full set is in [the AI crawler directory](/blog/ai-crawler-user-agent-directory)):

`GPTBot`, `OAI-SearchBot`, `ChatGPT-User`, `ClaudeBot`, `Claude-SearchBot`, `Claude-User`, `PerplexityBot`, `Google-Extended`, `Googlebot`, `Bingbot`, `CCBot`, `Bytespider`.

## What the logs tell you

Three things worth reading:

- **Who's visiting**: which engines crawl you at all. A bot that never appears can't cite you.
- **Status codes**: `200` means you served the page; **`403`/`401` means you're blocking that bot** (often at the CDN, regardless of what `robots.txt` says. See [is your CDN blocking AI crawlers?](/blog/is-your-cdn-blocking-ai-crawlers)).
- **What and how often**: which pages they fetch and at what frequency, mapped to the [train / index / answer lifecycle](/blog/ai-crawler-lifecycle) (training bots crawl broadly; answer bots fetch a single page on demand).

## The 30-second spot-check

No log access? Impersonate the bot and read the first response line:

```
curl -sI -A "GPTBot/1.2 (+https://openai.com/gptbot)" https://yourdomain.com | head -1
```

`HTTP/2 200` = reachable. `HTTP/2 403` = blocked. Repeat for the bots that matter.

## Verify identity for anything important

A user-agent is self-reported and can be faked. For decisions that matter, confirm the request's **IP** belongs to the operator (they publish ranges; some support reverse-DNS) rather than trusting the string.

> Your logs are the ground truth of AI reachability. "We allowed them in robots.txt" means nothing if the logs show 403s. The logs tell you what actually happened.

Reading logs is the manual version of a question worth answering continuously: are the engines reaching, crawling, and citing you, and did that change? Monitoring it across engines over time is what **Buffy Intel** is built to do.

## How to use Reddit to boost your AI search visibility
Source: https://heybuffy.com/blog/how-to-use-reddit-for-ai-search-visibility

Reddit is one of the most-cited sources in AI answers, and you earn that visibility by genuinely participating in communities, not by gaming them. AI engines lean on Reddit because it is dense with first-person experience and community consensus, the kind of [corroborated](/glossary/corroboration) signal they trust more than brand marketing. So the play for a brand is to be authentically present where your buyers already discuss your category.

## Why do AI engines cite Reddit so heavily?

Because AI engines favour community-edited, experience-rich sources over polished corporate copy, and Reddit is the largest pool of exactly that. The numbers, while volatile, point one direction:

| Finding | Source | As of |
|---|---|---|
| Reddit ~11.97% + Wikipedia ~13.15% of US ChatGPT citations (together >25%); WSJ, NYT, Bloomberg absent from the top 20 | 5W Research | June 2026 |
| Reddit among the most-cited websites in Google AI Overviews (Quora and Reddit lead) | Reported analyses | mid-2026 |
| Reddit leads AI citation share in Semrush's prompt analysis; LinkedIn cited in ~14.3% of ChatGPT Search, ~13.5% of Google AI Mode, ~5.3% of Perplexity responses | Semrush (325K-prompt study) | 2026 |
| Both OpenAI and Google signed paid data-licensing deals with Reddit | Reported | 2024 |

The pattern is consistent: when a question turns on lived experience. "Is X worth it," "best Y for Z". Engines reach for the forum where humans answered it. That is why Reddit shows up across [Google AI Mode](/glossary/google-ai-mode), [AI Overviews](/glossary/ai-overviews), ChatGPT, and Perplexity at once.

## Does posting on Reddit actually move AI visibility?

It can, but with real caveats you should price in before investing. Reddit visibility is **earned and volatile**, not owned. You do not control the page, a moderator can remove your post, and the citation share itself swings. Semrush's three-month study saw ChatGPT's Reddit citations collapse from roughly 60% of responses to around 10% in mid-September 2025 before recovering. A reminder that engines re-weight sources without warning.

So treat Reddit as one corroboration channel inside a broader strategy, not a silver bullet. The goal is to make sure that *when* an engine reaches for Reddit on your category, your brand is mentioned accurately and favourably by real people, which you influence by being genuinely useful, not by manufacturing threads.

## How do you earn AI visibility through Reddit?

Work the "participate first, mention later" sequence. Each step maps to a signal engines actually reward:

1. **Find the subreddits engines already pull from.** Search `site:reddit.com [your category]` and note which threads rank and which communities host them. Target both large subreddits (reach) and niche ones (engagement and topical authority).
2. **Build standing before you sell.** Spend weeks answering questions and sharing genuinely useful resources. Communities, and the engines reading them. Discount accounts that show up only to promote.
3. **Answer with specifics.** Verifiable, [numeric and named](/blog/how-to-get-cited-by-ai) answers ("ships in 3 days, $40, no subscription") are what gets lifted into an AI answer; vague praise gets skipped.
4. **Structure posts for extraction.** Lead with a one-line TL;DR, use clear headers and bullet lists. Clean structure helps engines segment and quote the passage. The same extractability discipline that wins on your own site.
5. **Let brand mentions be earned.** Disclose your affiliation, then let satisfied users and honest recommendations carry the name. An organic mention in a high-engagement thread is worth more than a self-post.
6. **Measure across engines over time.** Track branded-search lift and whether your brand surfaces in AI answers for your category, as a trend, not a one-off [snapshot](/blog/how-to-measure-ai-visibility).

| Tactic | Why it helps AI visibility |
|---|---|
| Genuine, sustained participation | Builds the authentic signal engines weight Reddit for |
| Specific, dated, numeric answers | High evidence density. The kind of passage models lift |
| TL;DR + headers + lists | Clean chunk boundaries for passage-level retrieval |
| Disclosed, earned mentions | Corroboration without the astroturfing penalty |
| Cross-engine measurement | Catches volatility before it becomes invisibility |

## What should you never do on Reddit?

Avoid anything that manufactures consensus. Vote manipulation, paid upvotes, fake accounts, and seeded "organic" reviews violate Reddit's rules and erode the exact authenticity that makes the platform valuable to engines. As we cover in [whether AI search can be manipulated](/blog/can-ai-search-be-manipulated), engines are actively learning to discount gamed and injected content, so the short-term lift rarely survives, and the brand risks being described as untrustworthy.

> Reddit rewards the brand that shows up to help, not the one that shows up to sell. The same authenticity that earns community trust is what makes an AI engine willing to quote the thread you're in.

The durable move is unglamorous: be the genuinely helpful presence in the communities your buyers already trust, give clear and specific answers, and let the mentions be earned. Then watch whether engines actually surface and recommend your brand for your category. Across ChatGPT, Google AI Mode, Perplexity, and AI Overviews, which is exactly what **Buffy Intel** tracks.

## How to tell if a GEO study or stat is trustworthy
Source: https://heybuffy.com/blog/how-to-vet-a-geo-study

**To judge a GEO or AI-visibility claim, ask which stage of the pipeline it measured, whether the test was live or simulated, how big and how recent it was, and whether anything independent corroborates it, then act only on findings that survive all four.** A July 2026 critical survey of 45 studies (Olivier Martinez, arXiv 2607.14035) found that most headline GEO numbers fail at least one of these checks, usually by measuring a late-stage lab metric and letting readers hear it as a traffic promise. This is the checklist that catches that, whether the claim comes from a vendor, a blog, or a peer-reviewed paper.

## Step 1: Which stage of the pipeline did it measure?

Separate the four stages before you read the number, because a gain in one says little about the others:

| Stage | The question it answers | Easy to move? |
|---|---|---|
| **Retrieval** | Were you pulled into the candidate set at all? | Hard, this is the real bottleneck |
| **Prominence** | How much of your wording did the answer use? | Easy, especially in a lab |
| **Citation** | Were you named or linked? | Medium |
| **Traffic** | Did a human actually click through? | Hardest to earn, rarely reported |

Most "+X% AI visibility" claims measure **prominence** (for example, [Position-Adjusted Word Count](/glossary/position-adjusted-word-count)) and invite you to hear **traffic**. The [survey's critique of the famous 40% figure](/blog/does-geo-actually-work) turns entirely on this gap: the gain was a prominence metric, not a retrieval or click gain. If a claim will not name its stage, stop reading it as a business result.

## Step 2: Was it a live engine or a simulated one?

Find out what the study actually tested against. A **simulated** engine synthesises an answer from a small, fixed set of documents the researcher supplies. That is excellent for isolating cause, but it removes the hardest part of real visibility: getting [retrieved](/glossary/retrievability) from millions of pages in the first place. A **live** test queries ChatGPT, Perplexity, Google AI Mode, or AI Overviews as they actually behave, with [query fan-out](/glossary/query-fan-out), reranking, and real competition.

Ask: how many competing sources were in play? A five-source, zero-sum testbed inflates relative percentages, because one source's gain is mechanically another's loss. Real niches with hundreds of competing pages show far smaller effects. Treat simulated numbers as direction; trust live, measured numbers for magnitude.

## Step 3: How big, how many engines, and how recent?

Weigh the sample and the shelf life, in this order:

1. **Sample size.** A handful of prompts or one brand per vertical is a signal, not a law. Ask how many queries, how many pages, how many brands.
2. **Engine coverage.** A finding on one engine rarely transfers; the survey found generic heuristics transfer poorly, and [citation overlap between engines is low](/blog/how-to-get-cited-in-perplexity). "Works on AI search" usually means "worked on one engine, once."
3. **Dates, not just publication date.** Check when the *test* happened and which model versions it used. AI engines change monthly, so a six-month-old citation study may describe a world that no longer exists, this is the [freshness cliff](/blog/content-freshness-citation-cliff) applied to research itself.

## Step 4: Does anything independent corroborate it?

Demand a second source before you act. A lone result, especially a single vendor reporting on its own product, is a hypothesis. [Corroboration](/glossary/corroboration) from an independent method or dataset is what moves it toward fact. Two useful tells:

- **Direction of incentive.** Does the party publishing the number sell the thing the number promotes? That does not make it false, but it raises the bar for corroboration.
- **Reproducibility.** Has anyone repeated the test and seen the same effect? The survey explicitly calls for repeated measurements, paraphrase controls, and human validation, if a study did none of these, hold its magnitude loosely.

> A GEO claim earns your action when it names the stage it measured, was tested on live engines at real scale, is recent, and is corroborated independently. Anything short of that is a direction to test, not a tactic to deploy.

## Step 5: Test it against your own measured visibility

End every appraisal by checking the claim on your own site, because even a well-built finding may not hold for your niche. Apply the change to a subset of pages, then track your [citation coverage](/glossary/citation-coverage) per engine before and after, watching **retrieval and citation, not just prominence**, so you catch the backfire case where a citation-friendly rewrite makes a page harder to retrieve. The broader method for that measurement is in [how to measure AI visibility](/blog/how-to-measure-ai-visibility) and [how to audit your site for AI visibility](/blog/how-to-audit-your-site-for-ai-visibility).

This is the discipline **Buffy Intel** is built around: it snapshots whether AI engines cite and recommend your brand across engines over time, so the GEO claims you keep are the ones your own data confirms, and the ones that failed this checklist quietly get dropped before they cost you.

## What is the IAB's AI Visibility Measurement Framework? The 4 P's explained
Source: https://heybuffy.com/blog/iab-ai-visibility-measurement-framework

**The IAB's AI Visibility Measurement Framework, published in August 2026 as "Measuring Visibility in the AI Era," is the first cross-industry standard for measuring how brands and publishers appear in AI-generated answers.** It defines a shared vocabulary — the *4 P's of AI visibility* — plus a two-tier quality standard and a provider-disclosure checklist, so that two tools measuring the same brand can finally be compared. It is the measurement counterpart to all the [GEO](/glossary/generative-engine-optimization) advice about *how to show up* in AI answers: a standard for knowing whether any of it is working.

This piece explains what the framework standardises, the metrics it names, how it separates trustworthy data from directional signal, and how it lines up with the way we already talk about [measuring AI visibility](/blog/how-to-measure-ai-visibility). Volatile specifics — adoption figures, platform user counts — are dated; the durable idea is a common language the market had been missing.

## Why did the industry need a measurement standard?

Because more than 20 companies now sell AI-visibility measurement, each with its own method, and they disagree. The IAB frames the problem bluntly: there is no common definition of a "mention," no standard for what counts as a citation, and no shared test for whether a tool's output is reliable enough to inform strategy. Two providers can hand the same brand different [share-of-voice](/glossary/share-of-voice) figures with no way to tell which is right.

The framework cites the scale of the shift, drawing on named third-party sources:

| Signal (per the IAB framework, mid-2026) | Figure | Attributed to |
|---|---|---|
| Brands that systematically track AI visibility | ~16% | IAB |
| Companies selling AI-visibility measurement | 20+ | IAB |
| ChatGPT weekly active users | 900M+ | OpenAI, via IAB |
| Google AI Overviews monthly users | 2.5B+ | Google, via IAB |
| Searches showing an AI Overview | "almost half" | Google, via IAB |
| Shopping queries showing an AI Overview | ~14% | via IAB |
| Possible traffic decline for unprepared brands | 20–50% | McKinsey, via IAB |
| Search-referral decline over two years (small / medium / large publishers) | 60% / 47% / 22% | Chartbeat via Axios, Mar 2026 |

The takeaway the IAB draws: budgets are ready to spend on measurement, but buyers "have no basis for evaluating what they are buying." Treat each figure as a dated, single-source datapoint — the framework aggregates them from other reports rather than measuring them itself.

## What are the 4 P's of AI visibility?

The framework organises every metric into four categories that form a causal hierarchy — presence has to come before prominence, and accurate portrayal before persuasion. Each metric ships with the disclosures needed to make it comparable across tools.

| P | Core question | Brand metrics |
|---|---|---|
| **Presence** | Does the brand appear? | Mention Rate, Citation Rate, [Share of Voice](/glossary/share-of-voice), Visibility Momentum |
| **Prominence** | Where, and how prominently? | Position |
| **Portrayal** | In what context, and how accurately? | [Sentiment](/glossary/sentiment-analysis), Framing, Hallucination Rate, Factual Inaccuracy Rate |
| **Persuasion** | Does visibility drive action? | Recommendation Strength, Post-Citation CTR |

A few definitions worth lifting, because they resolve arguments the market keeps having:

- **Mention Rate vs Citation Rate.** Mention Rate is how often you are *spoken about*; Citation Rate is how often you are *relied on as a source* (a linked or named reference). A high Mention Rate with a low Citation Rate is itself a signal — the model talks about you but does not treat your pages as authoritative.
- **Recommendation Strength.** The persuasion metric that separates "named as the best option for X, because Y" from "listed as one of several good options." It captures active endorsement, not mere appearance.
- **Hallucination Rate vs Factual Inaccuracy Rate.** A hallucinated mention is one the AI *fabricates*; a factual inaccuracy is an accurate mention tied to *wrong information from a real source*. Different causes, different fixes — and the framework insists providers report both per platform and surface them to clients rather than quietly filtering them out.

Publishers get a parallel set: Citation Rate, **Content Utilization Rate** (was your reporting substantively used, or just linked?), **Attribution Clarity**, Hallucination and Factual Inaccuracy Rates, Post-Citation CTR, and a **Citation Decay Rate** for how long content keeps getting cited — the standards-body version of the [freshness citation cliff](/blog/content-freshness-citation-cliff).

## How does the IAB tell good data from bad?

With a two-tier test: **directional** versus **decision-grade** measurement. Both are legitimate; the failure, the framework says, is treating directional data as decision-grade without noticing the gap.

| Criterion | Directional | Decision-grade |
|---|---|---|
| Purpose | Trend spotting, early signals, internal briefings | Budget allocation, agency reviews, executive strategy |
| Query volume | Fewer than 50 queries is "exploratory," not even directional | Large, diverse set with subcategory coverage; volume disclosed |
| Prompt-type coverage | At least two intent types | All four: informational, comparison, recommendation, transactional |
| Testing cadence | Monthly or quarterly | Weekly or more frequent |
| Reproducibility | Variation documented | Acceptable variation ranges defined within a 7-day window, with confidence levels |
| Platform coverage | One or more, single-platform acceptable with disclosure | Platforms covering a substantial majority of consumer AI traffic; per-platform results shown |

The framework is emphatic on one point that maps exactly to how [AI answers are non-deterministic](/glossary/answer-volatility): **"single-response measurement is not measurement."** A brand's visibility on a query is a *distribution*, not a value, so any number from one response per query is a sample of one. It recommends reporting a range — "approximately 22%, plus or minus 4 points" — over a bare "22%" that implies a precision the data cannot support.

> "AI platforms don't return the same answer every time, even to the same question. That's why we report ranges instead of single numbers. Changes inside the range aren't meaningful; changes outside it are." — the IAB framework's suggested language for briefing leadership.

## What should a measurement provider have to disclose?

This is the mechanism that makes the rest work. The framework lists the disclosures a buyer needs — platform and model-version coverage, prompt-library construction, query sourcing, data-collection architecture (active query simulation, passive panel, platform-native data, or a hybrid), hallucination and factual-accuracy classification, and how baselines are managed when a model changes. Its governing principle:

**Where a provider cannot or will not disclose against a required item, that absence should itself be treated as a signal.**

It sets a *minimum* disclosure tier for directional use and an *enhanced* tier expected of anything positioned as decision-grade, and names this as the foundation for a possible future IAB certification program. If you are choosing a tool, this is your question list — we walk through it in [how to vet an AI-visibility measurement provider](/blog/vet-ai-visibility-measurement-provider).

## How does this square with how we already measure AI visibility?

It confirms and sharpens it — there is no contradiction to resolve. Our own [five things worth tracking](/blog/how-to-measure-ai-visibility) map cleanly onto the 4 P's:

| Our metric | IAB category |
|---|---|
| Presence | Presence (Mention Rate) |
| [Share of Voice](/glossary/share-of-voice) | Presence (Share of Voice) |
| [Citation Coverage](/glossary/citation-coverage) | Presence (Citation Rate) |
| [Brand Perception](/glossary/brand-perception) | Portrayal (Sentiment, Framing) |
| Consistency | The non-determinism / reproducibility discipline |

The framework's value is not a new metric but a *shared* one, backed by disclosure rules — which is what turns a vendor claim into something a buyer can check. It is worth noting the scope: the IAB covers **organic, non-paid** AI visibility only. It does not address GEO or [AEO](/glossary/answer-engine-optimization) tactics, paid placement, or commerce attribution — those are flagged for future work, including a forthcoming IAB attribution framework. It measures *whether you show up and how*, not *how to make yourself show up*.

Buffy Intel is built around exactly this discipline: presence, share of voice, citations, sentiment, and consistency, sampled repeatedly across every engine and reported as a trend with its variability — not a single-response screenshot. If you want a measurement snapshot that already speaks the 4 P's, [see what Buffy Intel tracks](/blog/how-to-measure-ai-visibility).

## Can you influence what AI says about your brand? Training data vs. retrieval
Source: https://heybuffy.com/blog/influence-training-data-vs-retrieval

**Every AI answer about your brand is built from two things: what the model learned during training, and what it retrieves from the live web at answer time. You can barely move the first, and you can move the second a lot.** Training knowledge is baked into a model's weights and changes only when a lab retrains; [retrieval](/glossary/retrieval-augmented-generation) happens fresh on each query and rewards pages that are reachable, relevant, and clean. So the practical answer to "how do I change what AI says about me?" is: focus almost entirely on the retrieval layer. This piece explains the split and where your effort actually pays off.

The framing draws on a widely-shared BrightonSEO April 2026 recap published by Peec AI, an AI-visibility analytics vendor, plus a 2026 network-traffic teardown of ChatGPT. Both point the same way: your chances of influencing what a model retrieves are far higher than your chances of influencing what it was trained on.

## What is the difference between training data and retrieval?

A large language model holds two kinds of knowledge, and they behave completely differently for a brand trying to be described accurately.

| | Training data (parametric memory) | Retrieval (grounding) |
|---|---|---|
| Where it lives | Baked into the model's weights | Fetched from the live web at answer time |
| How fresh | Frozen at the [knowledge cutoff](/glossary/knowledge-cutoff) | As current as the page it just read |
| How you influence it | Indirectly, over months, by being consistently described across the web | Directly, now, by being reachable, relevant, and citable |
| Shows up as | Confident answers with no sources | Answers that cite or link the pages used |
| Your leverage | Low and slow | High and fast |

The distinction matters because the two layers fail in different ways. If a model describes an old version of your brand with total confidence and no sources, that is stale [parametric memory](/glossary/parametric-memory) talking. If it searches, reads a competitor's page, and cites that instead of yours, that is a retrieval problem you can fix.

## Why is retrieval the layer you can actually influence?

Retrieval is influenceable because it happens fresh on every query and reads whatever is reachable right now. Training is not, because you don't decide what a lab includes or when it retrains.

Most AI-search surfaces, from Google's AI Overviews to Perplexity, work by [retrieval-augmented generation](/glossary/retrieval-augmented-generation): they fetch relevant documents, then answer from what they fetched, then cite. That is why a page published this week can appear in an answer within days without waiting for a training cycle. Practitioner notes from BrightonSEO put it plainly: the battleground is prompts that trigger a web search, because those are the answers you can still shape.

Trained knowledge, by contrast, is set until the next model version. You can nudge it only indirectly, by being described consistently and correctly across enough of the web that the *next* training cycle learns the accurate version of you. That is real work with a long payoff, and it is worth doing, but it is not where this quarter's citations come from.

## Where do AI models get their sources, and how do you become one?

One useful mental model from the conference notes: the engine is a judge, the retrieved sources are witnesses, and you are the lawyer who has to prepare and put forward the witnesses. You don't get to write the verdict; you get to influence which evidence is in the room.

To be a witness the engine calls:

- **Be reachable.** An AI crawler that can't fetch or render your page can't retrieve it. Server-rendered HTML beats content locked in JavaScript, PDFs, or images. This is the first filter in [how ChatGPT picks sources](/blog/how-chatgpt-picks-sources).
- **Be relevant at the passage level.** Models don't read your whole page; they lift individual passages. Structure each section as a self-contained, answer-first [chunk](/glossary/content-chunk) so the exact answer is easy to extract.
- **Be corroborated.** Entities named across multiple credible sources are the ones most likely to make it into an answer. One page asserting a fact is weaker than the same fact echoed across your site, reviews, and independent coverage.
- **Be current.** Grounding favours fresh pages, and citations decay after roughly a quarter, so competitive pages need a [refresh cadence](/blog/content-freshness-citation-cliff).

## Does ranking in traditional search still feed retrieval?

Yes. Classic search rank and AI retrieval are correlated, and being visible in normal search raises your odds of being retrieved and cited, even though rank alone never guarantees it.

The Peec AI recap reports that a large share of URLs cited by Google's AI Overviews already rank in the traditional top 20, with the overlap notably lower for AI Mode, an indication that AI Mode reaches further down and wider than the classic results page. Treat those figures as directional single-source practitioner data, not audited benchmarks. The durable point is consistent with our own read that [Google rank does not reliably get you cited](/blog/does-google-rank-get-you-cited-by-ai): rank helps because a page that ranks is usually reachable, relevant, and indexed, exactly the traits retrieval rewards, but the AI engine re-selects at the passage level, so a well-structured page can be cited without a top rank, and a top-ranked page can be skipped.

> You can't rewrite what a model already believes about your brand. You can change what it reads the next time someone asks. Spend your effort where the answer is still being decided: retrieval.

## When does training data still matter?

Training still matters for two cases, so don't ignore it entirely. First, not every question triggers a search. A 2026 teardown of ChatGPT found it sorts questions into use-case buckets, and some are answered straight from trained memory with no web search at all, in which case only the model's parametric knowledge is in play. Second, the model's *default* associations, what it reaches for before any retrieval, are a training artefact, and being well-represented over time is how you become the brand it names by default.

The takeaway is not "ignore training." It is a matter of sequence and leverage: influence retrieval now, because you can, and let consistent, accurate, widely-corroborated presence across the web slowly improve what the next model learns. Being a clear, reachable, corroborated source about your own category is the one investment that pays into both layers at once.

Knowing which layer produced a given answer, and whether your retrieval work is actually moving citations, is hard to eyeball across engines. That is where **Buffy Intel** fits: it snapshots whether AI engines cite and recommend your brand over time, and shows whether an answer is grounded in pages it can point to or leaning on stale memory, so you can aim your effort at the layer you can actually move.

## How to influence your Reddit product page (when you can't edit it)
Source: https://heybuffy.com/blog/influence-your-reddit-product-page

**You cannot edit a Reddit product page, so you influence it in two places instead: the conversations it is written from, and the catalog that fills its commerce card.** Reddit generates the summary and quotes from redditor discussions, which means the only durable lever is earning honest, positive first-person experience in the relevant threads — and keeping your product feed clean so the buy link works.

This is the action companion to [what Reddit product pages are](/blog/reddit-product-pages). It assumes you have already decided Reddit is worth the effort; if not, start with the [decision framework](/blog/is-reddit-worth-it-for-ai-visibility). The steps below are ordered: earn the conversation, fix what it exposes, supply the catalog, then measure.

## Step 1: Find out what your product page already says

Before changing anything, read the raw material. Search `site:reddit.com` plus your product name and category, and read the threads that surface — those are the exact conversations a Reddit product page is built from. Note the recurring themes: what redditors praise, what they complain about, and which competitor gets mentioned as the better pick.

If the feature has reached your category, check whether a product page exists for your product inside Reddit's search and read its summary and quotes directly. Treat that summary as a mirror of your threads, not a marketing asset. The gap between what you claim and what redditors say is your work list.

## Step 2: Earn genuine discussion — never astroturf

The summary improves only when the underlying conversation does, and it has to be real. Reddit communities and AI engines both reward disclosed, first-person experience and punish manufactured hype. That rules out the shortcuts and points to the slow, durable moves:

| Do | Don't |
|---|---|
| Answer questions honestly where your product genuinely fits, disclosing your affiliation | Post covert promotion or reviews from brand-controlled accounts |
| Help satisfied customers share specific, detailed experiences | Buy aged accounts or pay for upvotes — see [why that backfires](/blog/why-buying-aged-reddit-accounts-backfires) |
| Participate consistently in the subreddits where your buyers actually are | Drop links and leave; treat Reddit as a one-off campaign |
| Let real detail (specs, use cases, edge cases) into the threads | Flood threads with generic marketing language |

The durable version of this is the full [Reddit AEO playbook](/blog/how-to-use-reddit-for-ai-search-visibility). The one-line rule: you are trying to make the true story of your product more visible, not to invent a better one.

## Step 3: Fix the real complaints the threads expose

The fastest way to change a community-written verdict is to remove the reason for the bad line. If redditors repeatedly cite the same defect — a connectivity bug, a sizing problem, a support delay — that theme will keep surfacing in the summary no matter how much positive discussion you add. Product and support fixes are AI-visibility work here, because the page is a live readout of customer experience.

> The only edit you can make to a Reddit product page is to the product. Change what customers experience, and the summary changes with it — usually a quarter later.

Prioritise the complaints that show up across multiple threads over one-off gripes, and let the community notice the fix in its own words rather than announcing it yourself.

## Step 4: Keep your product catalog clean so the buy link works

This is the one part of the page you control directly. Reddit's product pages can show a commerce card — image, price, and where-to-buy link — drawn from a Dynamic Product Ads catalog. If your feed is missing the product or carries a stale price or dead link, the summary can sell a shopper while the transaction leaks to a competitor with a working card.

Keep the same [product feed](/glossary/product-feed) discipline you would apply for any agent-driven surface: accurate titles, current prices, valid links, and correct availability. The broader version of this work — structuring your catalog so any [shopper agent](/glossary/shopper-agent) can transact — is covered in [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents) and the wider [agentic-commerce readiness](/blog/agentic-commerce-readiness) checklist.

## Step 5: Measure whether you actually surface — and re-check quarterly

Influence you cannot measure is guesswork. Track three things over time: whether a product page exists for your product, what its summary emphasises, and whether you appear in Reddit's shopping answers for the "which one should I buy" queries in your category. Then reconcile that with your visibility on the engines that cite Reddit — because the same threads feed both, a shift on Reddit often previews a shift in [product discovery across ChatGPT, Google, and Perplexity](/blog/chatgpt-vs-google-vs-perplexity-product-discovery).

Re-check on a quarterly cadence, since conversations refresh and the summary follows them. Manual spot-checks work for one product; across a catalog it becomes a monitoring job. **Buffy Intel** tracks where your brand surfaces across AI shopping and answer surfaces — including community-sourced ones like Reddit — snapshot over snapshot, so you can see the page changing shape and tie it back to the conversations driving it. Questions: support@flash.tech.

## What is information gain, and does it get you cited by AI?
Source: https://heybuffy.com/blog/information-gain-and-ai-citations

**Information gain is how much genuinely new information a page adds beyond what is already published for the same query.** A page that restates the consensus has low information gain; a page with a proprietary statistic, a first-hand test, or a detail no competitor covers has high information gain. It increasingly decides AI citations because engines retrieve and cite at the passage level — a page holding a fact no higher-ranked page provides can be cited even when it ranks outside the top results.

**Last reviewed: 28 August 2026.** The patent details below are from Google Patents (publication US11354342B2) and contemporaneous coverage (Search Engine Journal). The claim that recent Google updates lean harder on originality is *practitioner analysis*, attributed and hedged where it appears — Google's own update notes use generic language, so treat the direction as firmer than any single figure.

## What is information gain?

Information gain is a score for *how much a page adds* to what a reader already knows after seeing the pages that already rank. The term entered SEO through a Google patent, ["Contextual estimation of link information gain"](https://patents.google.com/patent/US11354342B2/en) (publication US11354342B2, filed 2018, granted 2024). The patent describes calculating, for a document, "the additional information" it contains beyond documents a user has previously viewed, then using that score to promote or demote follow-up results.

| Aspect | Detail |
|---|---|
| Origin | Google patent "Contextual estimation of link information gain" (US11354342B2) |
| Filed / granted | Filed 2018; granted 2024 |
| What it scores | Additional information in a document beyond what the user has already seen |
| Stated use in patent | Reranking follow-up results — promoting high-gain, demoting redundant pages |
| Confirmed in production? | No — Google has neither confirmed nor denied it uses this exact mechanism |

Source: Google Patents (US11354342B2); patent analysis via Search Engine Journal (2024). The honest reading: information gain is a concept Google has *patented and described*, not a factor it has confirmed by name. That is enough to treat it as a real lever, and not enough to quote a "score."

## Does information gain affect AI citations?

Yes — because AI engines select what to cite at the passage level, not the page level. When a model assembles an answer, it gathers hundreds of candidate [content chunks](/glossary/content-chunk) and narrows them to roughly a dozen, keeping the passages that are cleanly extractable, evidence-dense, and *non-duplicative*. A page whose only content is a restatement of the field adds nothing to that shortlist; a page with a unique, [corroborated](/glossary/corroboration) datapoint earns a slot.

- **Redundancy is a filter, not just a tiebreaker.** If five pages say the same thing, an engine needs one of them, not all five. The page with a detail the others lack is the one worth adding to the answer.
- **It partly decouples citation from rank.** Practitioner analyses of Google AI Overviews report that the share of citations coming from top-10 organic results fell sharply through 2025–2026 (widely cited as roughly 76% in mid-2025 to about 38% by early 2026 — single-source figures, directional). A page outside the top ten can still be cited if it holds a specific fact no higher-ranked page provides. We cover the rank side of this in [does Google rank get you cited by AI](/blog/does-google-rank-get-you-cited-by-ai) and [the most-cited domains in AI Overviews](/blog/most-cited-domains-ai-overviews).
- **It compounds across the fan-out.** A single answer is assembled from many sub-queries. A page with genuinely new material can be the unique source for one branch of the [query fan-out](/glossary/query-fan-out), which is how a mid-ranking page gets pulled into an answer it "should not" have made.

> If five pages already say it, an engine only needs one of them. Information gain is the reason the sixth page gets cited — it is the one that adds something the other five do not have.

## What did Google's March 2026 core update change?

Google confirmed a broad core update that ran **27 March to 8 April 2026**, describing it in its usual generic terms as "a regular update designed to better surface relevant, satisfying content for searchers from all types of sites." Google did **not** name information gain or originality as a target.

What changed is the *interpretation*. Several practitioners reported that sites leaning on original data and first-hand experience gained visibility while templated, rewritten, and generic AI-generated pages lost it — and framed that as a reweighting toward information gain (for example, DigitalApplied and Evertune analyses, mid-2026; single-vendor, self-reported). Treat those specific magnitudes as unverified. The durable, corroborated pattern underneath is the one the [Princeton GEO experiments](/blog/what-content-changes-lift-ai-citations) already established: pages that add statistics, first-hand detail, and cited evidence get lifted; pages that pad word count or restate the field do not. Information gain is the name practitioners now give that pattern, not a new algorithm you can see.

## How is information gain different from authority, E-E-A-T, and word count?

Information gain is about the *content of the page*, not the reputation of the domain or the length of the text. It is easy to confuse with adjacent signals, so separate them:

| Signal | What it measures | Can a small/new site win it? |
|---|---|---|
| **Information gain** | New information the page adds vs. what already exists | Yes — a unique datapoint beats a big brand's restatement |
| **Domain authority** | Aggregate link/reputation strength of the domain | Rarely quickly — it is slow to build |
| **E-E-A-T** | Experience, expertise, authoritativeness, trust of the source | Partly — first-hand experience helps fast; authority is slow |
| **Content length** | Word count of the page | No — length is not gain; padding lowers signal-to-noise |

Source: concept comparison from Google documentation and patent framing. The practical implication is the encouraging one for smaller brands: information gain is the lever least gated by [domain authority](/blog/does-domain-authority-affect-ai-citations) and page length. A short page with one fact nobody else has can out-cite a long page from a bigger domain that only summarizes the field — which is also why padding a page to hit a word count [does not help](/blog/does-content-length-affect-ai-citations).

## How do you build information gain into a page?

Add something the rest of the field does not have, then make it easy to lift.

1. **Bring original evidence.** Data from your own product logs, a first-hand test, a worked example, or an expert observation — anything a competitor cannot copy because they did not do it.
2. **Resolve a contradiction.** Where sources disagree, do the reconciliation on the page. A synthesis that settles a real conflict is itself new information.
3. **Cut the restated middle.** Remove the boilerplate that repeats what already ranks. High information gain means high signal-to-noise, not more words.
4. **Make the unique fact extractable.** State it specifically, numerically, and dated, in a sentence or table a model can lift whole — the [chunk-level](/blog/structure-content-into-extractable-chunks) discipline that gets a passage [cited by AI](/blog/how-to-get-cited-by-ai).
5. **Corroborate and attribute.** Cite where your claims are data; a unique fact that is also verifiable is safer for an engine to quote.

The test is simple: after reading your page, does a reader — or an engine — know at least one thing they could not get from the pages already ranking? If not, the page is [commodity content](/glossary/commodity-content), and commodity content is the first to fall out of AI answers as it [decays](/glossary/content-decay).

Information gain is the content half of AI visibility: original, specific, extractable material that gives an engine a reason to cite *you* rather than the ten pages that all say the same thing. Measuring whether that material actually earns citations — across ChatGPT, Google AI Overviews, Perplexity, and Claude, over time — is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Intent-driven category pages: match how shoppers actually ask
Source: https://heybuffy.com/blog/intent-driven-category-pages

**Name your category pages after what shoppers want, not what you sell.** A page called "jeans" matches a product; a page called "airport outfits" matches an intent, and intent is how people, and AI assistants, actually ask. As shopping moves into conversational AI, category and navigation pages built around shopper goals and situations are far easier to retrieve, cite, and recommend than pages named after your internal catalogue taxonomy. This is one of the highest-leverage structural moves an ecommerce site can make for AI visibility, and it sits above the product page, at the level of how your whole store is organised.

The pattern was a recurring theme in a widely-shared BrightonSEO April 2026 recap published by Peec AI, an AI-visibility analytics vendor. The reported results are single-vendor, conference-sourced figures, so treat the numbers as directional, but the underlying mechanism holds up against how [query fan-out](/glossary/query-fan-out) works.

## Why do product-named category pages underperform in AI shopping?

Product-named pages underperform because they answer the taxonomy question, not the shopper's question, and AI assistants search on the shopper's question.

When someone asks an assistant for help, the engine expands the request into many natural-language sub-queries, a process of [query fan-out](/blog/how-query-fan-out-works). Those sub-queries are phrased the way people think ("what should I wear for a long flight?", "trail shoes for wide feet"), not the way your merchandising team files inventory ("bottoms > denim > slim"). A category page that matches the intent language has a clean anchor to be retrieved against; a page named only for the product type does not.

Two shifts make this sharper in 2026:

- **Shoppers ask, they don't just search.** Conversational interfaces invite full-sentence, situational requests, so the gap between customer language and catalogue language is now exposed on every query.
- **The long tail is getting longer.** As assistants handle more of the phrasing, the head terms shrink and the specific, situational queries multiply, exactly the demand that intent pages capture and product-type pages miss.

## What does an intent-driven category page look like?

An intent-driven page is organised around a goal or situation and assembles products from across your catalogue to serve it. The contrast is concrete:

| Product-named (taxonomy) | Intent-driven (shopper goal) |
|---|---|
| Jeans | Airport outfits for long-haul comfort |
| Sneakers | Road shoes for wide feet |
| Dresses | Wedding-guest outfits under a budget |
| Backpacks | Cabin bags that fit carry-on limits |
| Blenders | Blenders for smoothies with frozen fruit |

Each intent page pulls the right items together, explains who and what it is for in plain language, and answers the natural follow-ups (fit, occasion, constraints) on the page. The BrightonSEO recap described a large fast-fashion retailer that moved from traditional product categories to intent-driven ones and reported a very large traffic uplift, with the featured items selling out. Read the specific percentage as directional single-source data; the reproducible lesson is that matching the page to the intent, not the product noun, is what unlocked the demand.

## How do you use the customer's own words in navigation?

Use the words your customers use, not the expert terminology your team uses internally, because the label is what both humans and AI match against.

The same recap reported that changing navigation from internal expert terms to customer language lifted key events and revenue for one retailer. The figures are single-source and should be hedged, but the principle is durable and testable: internal jargon ("technical outerwear", "occasion footwear") is invisible to a shopper who asks for "a warm waterproof jacket" or "comfy shoes for standing all day". Steps that work:

1. **Analyse problems, not keywords.** Start from the shopper's pain point or situation, then find the language they use to describe it.
2. **Mine the fan-out.** List the natural-language sub-questions your category triggers, and look for the common terms and concepts that recur, per the [content loop for fan-out queries](/blog/query-fan-out-content-loop). Those recurring phrases are your page titles and navigation labels.
3. **Rename to match.** Relabel navigation and category titles in that customer vocabulary, keeping the product-type structure underneath for classic search and site plumbing.
4. **Answer the branches on the page.** Cover the situational follow-ups (fit, use case, constraints) so the page is self-sufficient when an assistant lifts from it, the same discipline as [writing product pages AI can quote](/blog/write-conversational-product-pages).

> Your customers don't shop by your org chart. Name the page after the need they typed, assemble the products that meet it, and you have built the exact thing an AI assistant is trying to retrieve.

## How does this fit with the rest of your AI shopping work?

Intent-driven category pages sit above your product pages and your feed, and they complement both rather than replace them.

- **Feed and catalogue enrichment** ([preparing your catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents)) makes each product understandable to an agent.
- **Conversational product pages** ([writing PDPs AI can quote](/blog/write-conversational-product-pages)) make the individual item liftable.
- **Intent-driven category pages** make the *collection* discoverable for the situational, natural-language queries that assistants fan out into, and connect to how [Google AI Mode shoppers ask in attributes](/blog/why-ai-mode-users-search-in-attributes).

Done together, they cover the fan-out at every level: the situation, the comparison, and the specific product. Start with a handful of intent pages for your highest-value shopper situations, measure whether AI assistants begin surfacing them, and expand from what works.

Knowing whether these pages actually get cited and recommended, rather than just built, is the hard part. That is where **Buffy Intel** fits: it snapshots whether AI shopping assistants surface your store for the situational queries your customers ask, so you can see which intent pages earn recommendations and double down on the ones that do.

## Is AI-referred traffic more valuable? The 2026 data
Source: https://heybuffy.com/blog/is-ai-traffic-more-valuable

AI-referred traffic is now measurably more valuable than ordinary search traffic, according to Adobe Digital Insights' Q3 AI Traffic Trends Report (June 2026): in May 2026, AI-referred retail visitors converted at a **54% higher rate** and generated **53% more revenue per visit** than non-AI traffic. A complete reversal from a year earlier. This page collects the report's headline figures, each tied to its source and date.

**Last reviewed: 10 August 2026.** All figures below are from Adobe Digital Insights' Q3 AI Traffic Trends Report (June 2026) or the March 2026 Adobe Consumer Survey of 5,000+ US respondents, as noted, with an independent second-source corroboration from Similarweb added in the engagement section (August 2026). Adobe's web data covers more than one trillion visits to US retail sites and 100M+ SKUs. Large, but single-vendor and self-reported, so read the *direction* as firmer than any one percentage, and hedge anything you quote as "as of mid-2026."

## How fast is AI traffic growing in 2026?

AI-driven visit share kept climbing across every industry Adobe measured, well outside holiday peaks:

| Industry | AI visit-share growth (YoY, May 2026) | Source |
|---|---|---|
| Travel | **+194%** | Adobe Digital Insights, Q3 2026 |
| Retail | **+138%** | Adobe Digital Insights, Q3 2026 |
| Financial Services | **+105%** (19 straight months of growth) | Adobe Digital Insights, Q3 2026 |

Adobe's read: because AI visit share in May surpassed every month of 2025 *without* a seasonal lift, the shift is structural, not a holiday phenomenon. The March 2026 Adobe Consumer Survey adds that 54% of consumers say they are turning to AI more, and 58% had used AI in the past week. These are growth rates off a still-small base. Large multiples, modest absolute share, which is the same pattern other trackers report (see the broader [AI search statistics reference](/blog/ai-search-statistics-2026)).

## Does AI-referred traffic convert and spend more?

Yes, and the gap has inverted in the space of a year. For US retail in May 2026, Adobe reported AI-referred visitors outperforming non-AI traffic on every commercial metric:

| Metric (Retail, May 2026) | AI vs non-AI | Note |
|---|---|---|
| Conversion rate | **+54%** higher | A year earlier, AI converted at ~half the rate |
| Revenue per visit | **+53%** higher | Up from +37% in March; a year prior non-AI was worth **128% more** |
| Engagement rate | **+15%** higher | Strongest advantage since tracking began (Oct 2024) |
| Time on site | **+53%** more | April peak was +55% |
| Pages per visit | **+23%** more | Up from a 13% gap two months earlier |
| Bounce rate | **−36%** (less likely to bounce) | AI held an 17-20% band vs ~27% for non-AI |

The one-line summary Adobe draws: AI assistants are sending shoppers who arrive with intent rather than a fleeting click. This is also why AI's commercial impact is easy to under-count in analytics. Much of it [shows up as direct traffic](/blog/why-ai-traffic-shows-up-as-direct) rather than a labelled AI referral, so it needs [deliberate measurement](/blog/ga4-ai-referral-dashboard).

An independent dataset corroborates the engagement half of this. Similarweb's *Downstream Impact of AI Visibility* study (published 21 June 2026; US desktop panel, finance/travel/beauty, Jul–Dec 2025) reported that visitors influenced by an AI recommendation viewed **roughly twice as many pages** and spent **roughly twice as long** on site as visitors with no AI influence, and were **2.5x more likely** to visit the brand's site over the following seven days. Similarweb is a different vendor, panel, and set of industries than Adobe, so the agreement on direction (AI-referred visitors engage more deeply) is the useful signal — while both remain single-vendor and self-reported. Similarweb also found most of those visits arrive **days after the prompt and via search rather than a labelled AI link**, which is why the value is so easily missed; see [when AI-referred visits actually arrive](/blog/when-do-ai-referrals-arrive).

## What does the consumer survey say about AI shopping behaviour?

The March 2026 Adobe Consumer Survey (5,000+ US respondents) puts behaviour behind the traffic numbers:

- **39%** have used AI assistants for online shopping; **85%** of those say AI improved their shopping experience.
- **55%** turn to AI for inspiration and ideas. Most often *before* they begin shopping.
- **50%** click the links an AI assistant provides when shopping; **27%** complete purchases directly through those links.
- **79%** feel more confident in a purchase after using an AI assistant; **69%** say they are less likely to return an item bought with AI help.
- On trust: **66%** agree GenAI provides accurate results, and **38%** trust AI more than they used to.

The takeaway for brands: discovery increasingly *starts* in an AI answer, and the click. When it comes. Carries higher intent. Being present and accurately described at the inspiration stage is what feeds the rest of the funnel, which is the core argument for [getting recommended inside the answer](/blog/how-to-get-cited-by-ai).

## Is the pattern the same in travel and financial services?

Broadly yes, with sector-specific detail. AI-referred visitors engaged more deeply across all three industries Adobe tracked:

| Sector (May 2026) | Engagement | Time on site | Bounce | Notable |
|---|---|---|---|---|
| Travel | +21% | +70% (up from 61% in March) | −41% | Conversion gap narrowed from ~86% (Oct 2024) to 28% (May 2026), 67% narrower YoY |
| Financial Services | +8% | +27% | −18% | 89% trust AI for financial recommendations without human input; 46% of those fully follow the advice |

For travel, Adobe reported 86% of travelers had an improved experience planning via an AI assistant, using it for research (48%), inspiration (44%), budgeting (30%), and packing (21%). For financial services, 24% of consumers now use AI assistants for financial needs. Across all three sectors the same behavioural signal holds: AI sends visitors who have already researched and arrive ready to act.

## Which page types are most "AI-readable"?

Adobe's report introduces a **citation readability score**: its measure of how well a page's content can be parsed, understood, and surfaced by AI systems (structured, complete, and aligned to how models process information). Comparing the top 20% of companies by AI visit share against the bottom, Adobe found the biggest gaps at the *entry and discovery* layer:

| Page type | Readability advantage (top vs bottom performers) |
|---|---|
| Homepage | +52% |
| Search experience | +32% |
| Content pages (blogs, buying guides) | +23-30% |
| Exploration pages (brand landing, product detail) | +14-15% |
| Category / collection pages | +5% |

By retail sub-industry, citation readability (May 2026) was: **Cosmetics 63%**, Electronics 56%, Sporting Goods 51%, Apparel 51%, Grocery 48%, Furniture & Home 47%. A 16-point spread Adobe attributes directly to content strategy, with editorial, ingredient-education, and spec-rich pages reading best to AI. This is the same lesson the corpus reaches from first principles: [accessibility and clean structure predict AI-parseability](/blog/accessibility-and-ai-parseability), and structured, complete content is what gets [cited over a near-identical competitor](/blog/why-ai-cites-one-brand).

> The numbers will move, but the direction is the story: AI sends fewer visitors than search today, yet each one is worth more. More likely to convert, spend, and stay, and the pages AI can cleanly parse are the ones that win the visit in the first place.

## How should you use these figures?

Treat this as a dated reference, not a guarantee. Every number here is **single-vendor and self-reported**, drawn from Adobe's own web data and consumer survey; cite Adobe and the date when you reuse one, and prefer your own measured trend over any headline percentage. Because live retrieval favours recently-updated pages, we keep references like this on a [refresh cadence](/blog/content-freshness-citation-cliff) and update figures substantively as new data lands.

The figure that ultimately matters is your own: whether AI engines surface, cite, and recommend *your* brand, and whether that AI-referred traffic converts for *you*. Tracked over time across every engine. That measurement is exactly what **Buffy Intel** is built to provide.

## Is AI visibility winner-take-all in your industry? The 2026 concentration data
Source: https://heybuffy.com/blog/is-ai-visibility-winner-take-all

**AI visibility is winner-take-all in some industries and wide open in others, and the gap is now measurable.** In Semrush's 2026 AI Visibility Index, the top three brands held about **82.9% of News & Media** visibility and **76.9% of Consumer Electronics**, but only about **41.4% of Finance** and **42.2% of Industrial**. Your odds of being surfaced by an AI engine depend heavily on which of those two worlds your category lives in.

This is a dated reference, not a new dataset. **Last reviewed: 31 July 2026.** All figures come from Semrush's expanded 2026 AI Visibility Index (H1), an analysis of **126 million US AI-search prompts** from **January to April 2026** across ChatGPT, Gemini, Google AI Mode and Google AI Overviews, published 26 June 2026. It is single-vendor, US-focused and covers four engines, so read the *pattern* as firmer than any one percentage and cite "Semrush, 2026 AI Visibility Index" with the date when you reuse a figure. This page reconciles with two earlier cuts of the same index in our corpus: [how many sources AI engines cite](/blog/how-many-sources-ai-engines-cite) and [ghost citations: mentioned but not named](/blog/ghost-citations-cited-not-named).

## How concentrated is AI visibility by industry?

Sharply, and it varies more by category than most brands assume. Semrush measured the share of a category's total AI visibility held by its three most-visible brands. The higher the share, the more the answers in that vertical are dominated by a handful of names:

| Vertical | Top-3 brands' share of category visibility | Read |
|---|---|---|
| News & Media | ~82.9% | Near winner-take-all |
| Consumer Electronics | ~76.9% | Highly concentrated |
| Industrial | ~42.2% | Open — room to climb |
| Finance | ~41.4% | Open — room to climb |

Source: Semrush, 2026 AI Visibility Index (126M US prompts, Jan–Apr 2026). In the two concentrated categories, three brands own roughly four-fifths of everything the engines say; in the two open ones, the same top three hold under half, leaving the rest of the field genuinely contestable. Semrush's own framing is that less concentrated categories "may offer greater opportunities for brands to gain visibility over time." The one-word summary: **concentration is a property of your category, not of AI search as a whole.**

## Why do only 36 brands stay visible everywhere?

Because visibility rarely transfers across engines, so holding it on all of them at once is exceptionally rare. Semrush found only **36 brands**, which it calls the **Universal 36**, kept top-100 visibility across all four platforms in every month of the study. The list skews to internet-scale entities:

- **Named members include:** YouTube, Google, Reddit, Amazon, Facebook, Apple, Walmart, Disney, Nintendo.
- **What they share:** enormous [entity authority](/glossary/entity-authority) and constant third-party corroboration across the whole web, not a clever content trick.
- **What it implies:** for almost every other brand, visibility is engine-specific and must be earned and measured one engine at a time.

The Universal 36 are the exception that proves the rule. If fewer than three dozen brands on Earth are visible everywhere, then a strong showing on one engine tells you little about another, which is the same low-cross-engine-overlap finding we reconcile in [do a few domains dominate AI citations](/blog/ai-citation-domain-concentration). Chase the engines your buyers actually use, separately, rather than a mythical universal presence.

## Isn't this the same as the citation-fingerprint data?

No, and keeping the two apart matters. Three different "concentration" questions get muddled constantly:

| Question | Metric | Where we cover it |
|---|---|---|
| Which **brands** dominate a vertical's answers? | Brand-visibility concentration (this page) | Semrush top-3 share |
| Which **page types** get cited in a vertical? | [Citation fingerprint](/glossary/citation-fingerprint) | [Citation fingerprint by industry](/blog/ai-citation-fingerprint-by-industry) |
| Which **domains** do engines lean on overall? | Domain concentration | [Domain-concentration reconciliation](/blog/ai-citation-domain-concentration) |

This page is about *who* wins a category, not *what format* or *which domains* win generally. A vertical can be brand-concentrated yet still cite a wide mix of page types, or vice versa. Read each metric for the decision it informs: brand concentration tells you how crowded the head of your category is; the fingerprint tells you what to publish; domain concentration tells you which third-party sources are worth earning. Conflating them produces confident but wrong strategy.

> The useful question is not "is AI winner-take-all?" but "how concentrated is *my* category, and where is the open space within it?" An 80%-concentrated vertical and a 40%-concentrated one call for different plays, and the number is knowable before you spend a rupee on content.

## Does a mention even count as visibility?

Not on its own, and the distinction sharpens in concentrated categories. Semrush noted that on Gemini specifically, the overlap between the brands an answer *mentions* and the domains it *cites* can be as low as **30%** — a brand can be named without its own site being the source. Being mentioned inside a crowded category answer is worth far less than being the cited source, because a mention next to eight rivals is a footnote, while a citation is the recommendation. We unpack that gap in [ghost citations: mentioned but not named](/blog/ghost-citations-cited-not-named). Track both, and weight citation over mention where the field is crowded.

## What should you do with your category's concentration number?

Treat it as the first input to strategy, not a verdict. Concretely:

- **Measure your own top-3 concentration before planning.** The vertical averages above are directional; your specific prompt set may be more or less crowded. This is exactly what [measuring AI visibility](/blog/how-to-measure-ai-visibility) across many prompts and engines is for.
- **In a concentrated category, go around the head.** Head-on competition for the most-asked prompts against entrenched brands is slow. Long-tail sub-topics, specific comparisons, and [earned placement](/glossary/earned-media) in third-party sources are more winnable. The full playbook is in [how to compete for AI visibility in a concentrated category](/blog/compete-in-concentrated-ai-categories).
- **In an open category, climb the main prompts directly.** Where the top three hold under half, [entity strength](/blog/entity-strength-ai) and clean, citable pages can move you up the core questions, not just the fringes.
- **Don't chase universal visibility.** With only 36 brands visible everywhere, measure and win each engine separately rather than optimising for an impossible average.
- **Refresh, because concentration moves.** These are single-vendor figures from a four-month window; re-check as new editions land, on the same [freshness cadence](/blog/content-freshness-citation-cliff) any competitive reference needs.

The published averages set the scene, but the number that governs your plan is your own category's concentration, measured across the prompts your buyers actually ask and tracked per engine over time. That per-category, per-engine visibility measurement is exactly what **Buffy Intel** is built to provide. Questions: support@flash.tech.

## Is ChatGPT citing fewer listicles after GPT-5.6?
Source: https://heybuffy.com/blog/is-chatgpt-citing-fewer-listicles

ChatGPT is citing fewer listicles than it did before GPT-5.6. According to a 2026 analysis by AI-visibility platform Peec AI, comparing the same set of prompts the week before and the week after GPT-5.6 became ChatGPT's default mode, the share of [listicles](/glossary/best-of-list) cited by ChatGPT fell about **50.5%** and comparison pages about **32.1%**. Listicles are not gone — the model issues more background searches, and more precise ones, and pulls in more sources overall, which makes third-party roundups a smaller slice of a larger, more [first-party](/glossary/first-party-citation) citation set. This reference lays out the data, attributed and dated, and what it changes for AI visibility.

**Last reviewed: 21 August 2026.** All figures below are from Peec AI's before-and-after analysis unless noted. It is a **single-vendor, directional** study of one model transition, based on the same ~1 million tracked prompts and ~180 million sources measured a week before and a week after the rollout, so treat the exact percentages as a snapshot and cite "Peec AI, 2026" with the date when you reuse them. GPT-5.6 rolled out from July 2026 and widened to become the broadly-default ChatGPT mode through August 2026; treat "the default" as a mid-to-late-2026, still-moving state.

## How much did ChatGPT's listicle citations drop?

By about half, on Peec AI's numbers. The two formats that lost the most citation share were the two most associated with commercial-intent "best X" and "X vs Y" questions:

| Format | Change in ChatGPT citation share after GPT-5.6 |
|---|---|
| Listicles ("best / top" roundups) | **−50.5%** |
| Comparison pages ("X vs Y") | **−32.1%** |

Source: Peec AI, 2026 (same ~1M prompts, week-before vs week-after the GPT-5.6 default rollout). The drop is a change in *share of the citation mix*, not proof that any single listicle lost its citation — the total pool of cited sources grew at the same time, which is most of the story.

## Why did the mix shift toward first-party sources?

Because GPT-5.6 changed *how* it searches, not just what it cites. Peec AI isolates four shifts in the model's [query fan-out](/glossary/query-fan-out) — the hidden step where a prompt is expanded into background searches:

| What changed with GPT-5.6 | Peec AI figure |
|---|---|
| Fewer "top" fan-out searches | Share of "top" fan-outs **−75%**; average number per chat **−36.5%** |
| More searches per chat | About **+154%** more fan-outs per chat than GPT-5.5 |
| More sources per chat | About **25.55** sources cited per chat, vs **12.48** for GPT-5.5 (~2×) |
| Goes straight to the source | About **18.37%** of chats now include at least one fan-out using the `site:` operator |

The pattern: the model asks fewer open "what are the top tools" questions and more targeted, source-specific ones. When it uses the [`site:` operator](/glossary/site-operator) to scope a search to a named domain, it lands on that brand's own page rather than a generic roundup — so a larger share of citations resolves to first-party sources. The site:-operator surge is the mechanism we documented separately in [what ChatGPT's query fan-out targets](/blog/chatgpt-site-operator-fan-out-data); note the two datasets measure it differently (share of *chats* with at least one such fan-out here, versus share of *fan-out queries* there), so read them as the same direction, not the same number.

> ChatGPT did not fall out of love with listicles. It got better at searching — more queries, more precise queries, more sources per answer — and that alone makes any one third-party roundup a smaller part of the picture.

## Does an independent source confirm this?

Directionally, yes. A separate Promptwatch analysis dated 8 August 2026 reported that ChatGPT's use of the `site:` operator in its fan-out jumped from roughly 0.4% to about 17% of fan-out queries "overnight," and that the average number of searches per response nearly doubled around the same time — the same two shifts Peec AI attributes to GPT-5.6. Two independent practitioner datasets pointing the same way is stronger than either alone, though both are directional and version-specific. The durable claim is the one that survives the next model release: **more capable ChatGPT versions fan out more, and more precisely, toward specific first-party sources.**

## Does this contradict "why AI loves listicles"?

No — and the distinction matters, because getting it wrong would put two of our own pieces in conflict. Our reference on [why AI loves listicles](/blog/why-ai-loves-listicles) reports that third-party roundups are cited far more than brand-owned pages for commercial-intent queries. That finding still holds as a **cross-engine, commercial-intent baseline**: it is strongest on Perplexity and Google's AI Overviews, which lean hard on third-party roundups, and it is about *which format wins a "best X" answer*.

The Peec AI finding is narrower and directional: it is **ChatGPT-specific** and about a **change over one model transition**. Both are true at once:

- Listicles still dominate discovery and "best / top / vs" questions, especially outside ChatGPT.
- Where you *are* cited in a listicle, [your position inside it still compounds](/blog/listicle-rank-effect).
- On ChatGPT specifically, the third-party premium is narrowing as the model reaches for first-party sources by name — the same trend as its [brand-name fan-out searches](/blog/chatgpt-fanout-searches-for-brands).

## What should brands actually do about it?

Treat it as a "both," not a "switch." The move is not to abandon earned placement — it is to make sure your own pages can be cited when the model comes looking:

- **Keep earning listicle placement.** It still wins discovery and other engines. Pursue it as [earned placement in the best-of lists AI engines cite](/blog/get-into-ai-cited-best-lists), not self-listing pages.
- **Make your first-party pages citable.** With ChatGPT now targeting named domains, your specs, pricing, and official facts must be clean, [server-rendered, extractable text](/blog/prioritize-your-structured-data) — or the model narrows to your domain and finds nothing to lift.
- **Build the entity association.** The model reaches for brands it already links to a topic, so [entity strength](/blog/entity-strength-ai) is what earns the site:-scoped, first-party fan-out in the first place.
- **Measure per engine, over time.** A shift this size is exactly the kind of movement a spot check misses. Because the formats that win differ by engine and by model version, track ChatGPT, Gemini, Claude, and Google separately.

The honest read for late 2026: ChatGPT is rewarding clean first-party sources more than it did a quarter ago, while third-party roundups still carry discovery and other engines. Knowing which way *your* citations are moving — third-party versus first-party, engine by engine — is exactly what **Buffy Intel** is built to measure over time. Questions: support@flash.tech.

## Is GEO just SEO? What Google's official AI-search guide says
Source: https://heybuffy.com/blog/is-geo-just-seo

Mostly, yes, for Google's own surfaces. In May 2026 Google formalized its position in an official guide, "Optimizing your website for generative AI features on Google Search," which states plainly that optimizing for its AI features **is** search optimization, and that you don't need markdown, `llms.txt`, or any AI-specific files to appear. That's accurate for [AI Overviews](/glossary/ai-overviews) and AI Mode. It's incomplete as a whole-ecosystem strategy, because Google's guidance stops at the edge of Google's own products.

## What did Google actually say?

Google's guide makes two blunt claims. First, on the discipline: *"From Google Search's perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO."* Second, on tooling: you *"don't need to create machine-readable files, AI text files, markup, or Markdown to appear in generative AI search."* The reasoning is that Google's AI features are rooted in its core ranking and quality systems. [AI Overviews and AI Mode](/blog/how-google-ai-mode-works) pull from the same index that ranks classic results, so the same signals apply. Google representatives have repeated the message consistently since 2025, including that Google [does not crawl or use llms.txt](/blog/why-google-says-llms-txt-is-flawed).

## What does Google's guide say actually helps?

The guide's recommendations read like a disciplined SEO program, not a new playbook. Google emphasizes **non-commodity content**: material with unique insight beyond common knowledge, and lists concrete technical fundamentals.

| Google's recommendation | What it maps to |
|---|---|
| Unique, non-commodity content | Evidence density, first-hand data |
| Follow crawling best practices | Reachability. Don't block the bots |
| Use semantic HTML | Extractability. Clean, parseable chunks |
| Follow JavaScript SEO guidance | Content visible without executing JS |
| Strong page experience, minimize duplication | Quality and clarity signals |
| Merchant Center feeds + Google Business Profile | Structured product/local data |

Every row is something [answer-engine optimization](/glossary/answer-engine-optimization) already treats as table stakes. Google isn't negating the work; it's renaming it. Notably, "it's still SEO" *raises* the bar. [Structured data](/glossary/structured-data) and answer-first structure aren't optional extras, they're how the same index understands you well enough to synthesize an answer.

> "Still SEO" is not "do nothing new." It means the durable levers. Crawlability, semantic structure, structured data, and entity strength. Are the levers, on both classic and AI surfaces. There is no shortcut file.

## Where does Google's guidance stop?

At Google's property line. The guide speaks for Google Search's AI features. It says nothing about how ChatGPT, Perplexity, or Claude retrieve and cite, and those engines behave differently. They crawl with their own bots, weight sources differently, and some fetch files Google ignores. Citation overlap between engines is low, so a page ChatGPT loves may be absent from Perplexity's answer. That's the gap [GEO](/glossary/generative-engine-optimization) names: not a magic technique Google is debunking, but the reality that visibility now spans several engines you don't own, each measured separately.

So the honest reconciliation is this. For Google, do excellent SEO with an answer-first, well-structured, strongly-corroborated site. Exactly what the guide describes, and exactly what wins [AI Overviews](/blog/how-to-optimize-for-ai-overviews). Skip the [llms.txt and markdown mirrors](/blog/is-llms-txt-worth-it); Google won't read them and the evidence they help elsewhere is thin. Then treat the wider ecosystem as its own problem: the same fundamentals plus [entity strength](/blog/entity-strength-ai) and per-engine measurement. Google saying "it's still SEO" is a useful correction to file-based snake oil, not a reason to stop measuring where you're actually cited.

## What to do next

Read Google's guide as a checklist you can mostly already tick: crawlable, semantic, structured, non-commodity, no special files. If a "GEO" vendor is selling you an [AI-specific file](/blog/markdown-files-in-ai-overviews) as the lever, Google just told you it isn't. The lever is the same durable work, and knowing whether your pages actually pass it, across every engine and not just Google, is what **Buffy Intel** measures. Start with the fundamentals Google names; verify the result across the engines Google doesn't speak for.

## Is Google Trends broken? How AI query fan-out may be inflating search data
Source: https://heybuffy.com/blog/is-google-trends-broken

Google Trends is probably not "broken," but in 2026 it deserves more scepticism than it used to. Several practitioners have flagged mature, stable categories. Air fryers, car insurance, London hotels. Showing all-time-high "interest" that doesn't square with real-world demand. One widely-shared hypothesis is that **AI [query fan-out](/glossary/query-fan-out)** is inflating the signal by counting machine-generated sub-queries as human searches. Google has not confirmed any cause, so the honest read is: treat Trends as directional, not ground truth.

## What's actually being claimed?

The observation comes from practitioners, not from Google. The pattern they describe: keyword tools and Google Trends show **record interest in well-understood, slow-moving categories** where demand should be flat. A category like air fryers or car insurance has no reason to hit an all-time high. The products and the buyers haven't changed.

One practitioner's hypothesis, shared in a widely-circulated post, ties this to how AI search works. When an AI assistant answers a question, it often doesn't issue one search. It fans the question out into many backend sub-queries against Google and other sources. If those automated sub-queries land in the same measurement pipeline as human searches, the volume for terms *no human typed* gets inflated.

This is a hypothesis. It is plausible and it fits the pattern, but Google has not endorsed it, and other explanations (sampling changes, bot traffic, methodology shifts) are possible. State it as a hypothesis when you repeat it.

## How could query fan-out inflate the numbers?

[Query fan-out](/blog/how-query-fan-out-works) is the mechanism behind modern AI answers: one question becomes many searches.

- A user asks one question in an AI surface.
- The system decomposes it into sub-queries. Rewrites, comparisons, anticipated follow-ups, slot-filling for variables like price or location.
- It searches each sub-query, often in parallel, and synthesises the results into a single answer the user reads without clicking.

Independent analyses estimate that Google's AI Mode can fire on the order of ten sub-queries for a single question, while chat engines like ChatGPT tend to issue fewer. Figures that vary by query and are not officially published, so treat them as rough estimates. The point holds either way: **one human question can generate many machine searches.** If a measurement system can't cleanly separate the two, aggregate volume and "interest" rise without any change in human demand.

## Are humans really searching less?

The distortion hypothesis lands harder because human search behaviour appears to be moving the *opposite* way. According to clickstream analysis from Datos and SparkToro (reported mid-2026), Google searches per US user fell **nearly 20% year over year**: attributed largely to AI answers and instant results satisfying intent without follow-up searches. The same analysis put the decline in Europe at only about 2-3%, a much smaller shift.

> If human searches per person are falling while headline "interest" hits record highs, the gap is the tell: the curve may be tracking machine activity, not people. Read it as a signal to corroborate, not a number to plan against.

Treat both figures as vendor-reported and directional, but together they sketch a coherent picture: fewer human searches, more machine sub-queries, and aggregate signals that no longer map cleanly to real demand.

## What does this mean for brands?

Two kinds of decisions lean directly on keyword and Trends data, and both are exposed:

| Decision | Why it's exposed | Safer practice |
|---|---|---|
| Content planning | Topic priorities chosen by search volume may chase inflated terms | Plan around the questions buyers actually ask AI, not raw volume |
| Market sizing | Demand estimates built on keyword volume may overstate a flat category | Triangulate with first-party demand signals and sales data |
| Trend spotting | An "emerging" spike may be fan-out noise, not a real shift | Confirm against a second, independent source before acting |

The takeaway is not to abandon keyword data. It's still useful for the *shape* of demand. It's to stop treating it as the single source of truth in a [zero-click](/glossary/zero-click-search), [conversational-search](/glossary/conversational-search) world where much of the measured activity may be machines, not buyers.

## What should you trust instead?

Pair traditional keyword and Trends data with **answer-level signals**: the part of discovery that now happens inside AI answers. The questions worth tracking:

1. **Citation share**: across a representative set of prompts your buyers would ask, how often does an AI engine name or cite you?
2. **Recommendation rate**: when the question is "best X for Y," are you in the set the engine recommends?
3. **Movement over time**: is your share rising or slipping across engines, sampled repeatedly?

These signals measure whether real demand is reaching you, independent of whatever the search-volume pipeline is counting. (For the broader migration from search clicks to AI citations, see [from clicks to citations](/blog/from-clicks-to-citations); for the underlying numbers, the [AI search statistics 2026](/blog/ai-search-statistics-2026) reference keeps every figure attributed and dated.)

When keyword tools may be counting machine traffic, the more direct read on demand is whether AI engines actually surface and recommend you. Sampled across many prompts, repeatedly, on every engine. That measured answer-level visibility is exactly what **Buffy Intel** is built to track.

## Is llms.txt worth it? An honest take
Source: https://heybuffy.com/blog/is-llms-txt-worth-it

[llms.txt](/glossary/llms-txt) is a tidy idea: a Markdown file at your site root that hands AI a curated map of your most important pages. It's easy to be enthusiastic about. A `robots.txt` for the AI era. So here's the honest take, because over-promising on it is a disservice.

## The optimistic case

The pitch is reasonable. Instead of making an engine infer your site's structure from messy HTML, you tell it plainly: here are the key pages, here's what each is. For an AI trying to understand a site quickly, a clean, curated guide is genuinely helpful in principle.

## The reality (as of 2026)

It's a **proposed convention, not an honoured standard.** The major AI engines don't broadly read or act on `llms.txt` today, and there's no solid evidence it moves citations on its own. Adoption among sites is growing, but adoption by the engines that matter is the part that counts, and that hasn't arrived. Treat any claim that "adding llms.txt boosted our AI visibility" with skepticism; correlation in a fast-moving space is easy to misread.

> llms.txt is a bet on where the ecosystem is going, not a lever that works today. Add it like you'd add a sensible standard early, not like a growth tactic.

## So should you add it?

**Yes, but calibrate your expectations.** It's near-zero cost, has no downside, keeps you positioned if engines start honouring it, and signals you take AI readability seriously. Add it, keep it accurate, and move on.

What you should *not* do is treat it as a substitute for the things that actually drive AI visibility today:

- **Crawl access**: AI bots can reach you (robots + [CDN](/blog/is-your-cdn-blocking-ai-crawlers) both open).
- **Parseability**: clean, semantic, [answer-first](/blog/how-to-get-cited-by-ai) content in real HTML, not JS-only.
- **[Structured data](/glossary/structured-data)**: schema that labels what your content is.
- **Authority & freshness**: a strong [entity](/glossary/entity-authority), corroborated and kept current.

## The honest bottom line

Add `llms.txt`. Then forget about it and go do the work that moves the needle. The brands winning in AI search aren't winning because of a text file. They're winning because they're reachable, legible, authoritative, and measured. (We added one to this site for exactly this reason: cheap, future-proofing, not a crutch.)

## Is Reddit still cited in ChatGPT? The August 2026 collapse
Source: https://heybuffy.com/blog/is-reddit-still-cited-in-chatgpt

Reddit's visibility inside ChatGPT collapsed in mid-August 2026. According to Promptwatch's citation tracking, Reddit's share of ChatGPT Search citations averaged about **3.83%** from 18 July to 7 August, then fell to about **0.52%** by 14–17 August — roughly an **86% relative drop** — while ChatGPT kept *fetching* Reddit heavily. This reference lays out the data, attributed and dated, explains why a fetched-but-uncited page is a "[silent source](/glossary/silent-source)," and what the shift means for brands that lean on Reddit.

**Last reviewed: 23 August 2026.** The citation figures are from **Promptwatch** and corroborated across multiple August 2026 reports (Forbes, Yahoo, Search Engine Journal, G2). The fetched-but-uncited observation is from search consultant **Suganthan Mohanadasan** (suganthan.com), from a single-account traffic teardown. Promptwatch itself cautions that a data-collection artefact cannot be fully excluded, so treat the **size** of the drop as provisional while the direction is well-corroborated. Attribute "Promptwatch, August 2026" and date any figure you reuse.

## How far did Reddit citations fall in ChatGPT?

Steeply, and specifically in ChatGPT — not across AI search generally. The contrast with Google AI Overviews is the key evidence that this is an engine-level change, not an industry trend:

| Metric | Before (mid-Jul → 7 Aug 2026) | After (14–17 Aug 2026) | Relative change |
|---|---|---|---|
| Reddit share of **ChatGPT** citations | ~**3.83%** | ~**0.52%** | ~**−86%** |
| Reddit share of **Google AI Overviews** citations | ~**2.37%** (early Jul) | ~**2.10%** (mid-Aug) | ~**−11%** |

Source: Promptwatch, August 2026. Reddit's presence in Google AI Overviews barely moved and showed no single break point, while ChatGPT's fell off a cliff. Whatever changed, it changed inside ChatGPT — a reminder that [engines cite largely different sources](/blog/most-cited-domains-ai-overviews) and a drop on one is not a drop everywhere.

## Why is Reddit still fetched but not cited?

Because it appears to have become a **silent source** — a page ChatGPT reads during retrieval to shape its answer, but never links in the visible response. Suganthan Mohanadasan documented one ChatGPT conversation in which **84 of 221 retrieved entries were Reddit threads**, yet none were cited. He also observed that Reddit receives unusually wide [freshness windows](/blog/chatgpt-freshness-windows) — 365 to 3,650 days — so old threads stay eligible for the retrieval pool even as they vanish from the answer.

This is consistent with what we measured earlier: in [ChatGPT's site: operator fan-out data](/blog/chatgpt-site-operator-fan-out-data), Reddit was about **71.5%** of the *non-branded* domains ChatGPT targeted. Reddit is still being pulled in aggressively; what changed is whether that pull turns into a visible link. As Suganthan put it, Reddit now functions as "an invisible input" — opinions feed the answer while the credit goes elsewhere. That is the textbook definition of a [silent source](/glossary/silent-source): influence without attribution.

## What caused the ChatGPT drop?

The honest answer is: not fully known, and worth hedging. Two dated events line up with the decline, but neither fully explains it:

- **8 August 2026 — the search-format change.** ChatGPT's use of the `site:` operator jumped from about 0.4% to nearly 17% of fan-out queries the same day Reddit's share began slipping from the high-3s. This coincides with the broader move to the [new pipe-delimited search language](/blog/chatgpt-new-search-query-language) and its domain slot.
- **14 August 2026 — the sharper break.** Six days later Reddit's share dropped again, more steeply, which the format change alone does not account for.

> The fetching is documented and the citation collapse is documented; what cannot be proven from traffic alone is whether the fetched content still influences the answer invisibly. Report the what, hedge the why.

The six-day gap between the two events is why analysts, and we, stop short of a single-cause claim. A source-selection change is the obvious candidate; a measurement artefact is not excluded. Both are stated, neither is asserted as settled.

## Has this happened before, and is it permanent?

It has happened before and reversed. Independent trackers note Reddit saw a comparable ChatGPT citation dip earlier and then recovered, so the durable read is **volatile, not terminal**. Reddit remains a heavily-fetched source and a steady contributor to Google AI Overviews, and its content licensing and scale make a permanent zeroing-out unlikely. Treat the current level as a mid-2026 snapshot of a metric that has swung before, not a new constant.

## What should brands relying on Reddit do?

Reassess with your own data; do not overreact to a single-engine, possibly-provisional swing:

- **Measure the citation payoff, not the fetch.** Ask your real target questions and count how often Reddit threads are actually *cited* versus merely retrieved. If the payoff has collapsed for your queries, shift effort; if it hasn't, hold.
- **Keep Reddit as one input, not the strategy.** The collapse is a case study in single-point-of-failure risk — diversify across the sources your category's answers actually pull from.
- **Do not game it.** Authentic, genuinely-helpful Reddit participation still feeds AIO and may recover in ChatGPT; manipulative posting is exactly what source-selection changes are built to discount. The [Reddit AEO fundamentals](/blog/reddit-aeo-for-startups) and [how to influence your Reddit product page](/blog/influence-your-reddit-product-page) still apply — earn the mention, don't fake it.
- **Watch the trend across engines.** Because this moved on ChatGPT but not AIO, a per-engine view is the only way to see it; a blended number would have hidden the whole story.

The durable lesson under a volatile number: a source can be read constantly and cited rarely, and output-only measurement misses exactly that gap. Tracking what AI engines *retrieve* as well as what they *cite*, per engine and over time, is what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Is Reddit worth it for AI search visibility? A decision framework
Source: https://heybuffy.com/blog/is-reddit-worth-it-for-ai-visibility

Reddit is one of the most-cited sources in AI answers, but it isn't the right AI-visibility channel for every brand. Whether it's worth investing depends on five things: whether your buyers actually discuss your category there, how much AI engines already pull your brand from Reddit today, whether your customers can carry the mentions, whether you can commit to months of genuine participation, and the opportunity cost against your other work. A confident "no" on any of these is a legitimate reason to skip it.

This is the decision that comes *before* the [Reddit AEO playbook](/blog/how-to-use-reddit-for-ai-search-visibility) and the [founder-specific version](/blog/reddit-aeo-for-startups). Those assume you've decided to invest. This piece helps you decide whether you should.

## Why is Reddit such a big deal for AI visibility?

Because AI engines favour community-edited, first-person experience over brand marketing, and Reddit is the largest pool of exactly that. When a question turns on lived experience ("is X worth it," "best Y for Z"), engines reach for the forum where humans already answered it. The signal, while volatile, is consistent:

| Finding | Source | As of |
|---|---|---|
| Reddit ~11.97% + Wikipedia ~13.15% of US ChatGPT citations (together >25%) | 5W Research | mid-2026 |
| Reddit leads social-platform citation share across commercial categories | Tinuiti (Q1 2026 AI Citations report) | Q1 2026 |
| Reddit's ChatGPT citation share swung from ~60% to ~10% of responses in mid-Sep 2025 before recovering | Semrush (three-month study) | 2025 |
| Both OpenAI (~$70M/yr, reported) and Google (~$60M/yr, reported) signed paid data-licensing deals with Reddit | Reported | 2024 |

Treat the exact percentages as volatile, single-source and directional. The durable takeaway is that Reddit is *structurally* favoured by engines, which is exactly why the "obvious" move is to add it to every marketing plan. The framework below is how you check whether that obvious move is right for you.

## Should every brand invest in Reddit? No: here's how to decide

No. Reddit rewards a specific kind of brand and punishes a mismatched one with wasted effort. Test your situation against five criteria before committing a team:

| Criterion | Invest if… | Skip or deprioritise if… |
|---|---|---|
| **Audience fit** | Your buyers actively ask about your category in identifiable subreddits | The people discussing your category are mostly an audience your product isn't built for |
| **Current retrieval share** | You already appear in AI answers from Reddit, or clearly could | You measured it and Reddit is a tiny share of where you're retrieved |
| **Customer-led potential** | Real users would plausibly recommend you unprompted | The only voice that would ever mention you is your own marketing team |
| **Participation capacity** | You can commit months of genuine, non-promotional contribution | You need results this quarter and can't sustain community presence |
| **Opportunity cost** | Reddit is among your highest-leverage untapped channels | You have higher-ROI AI-visibility work you're not yet doing well |

The strongest signal is the middle row. On Reddit, the durable [citations come from earned mentions](/blog/cited-vs-recommended-in-ai-search). Satisfied customers naming you in a thread, not from a brand account posting about itself. If you can't picture a customer doing that, the channel is fighting your grain.

## When is Reddit NOT worth it?

Reddit is a poor investment when the honest answers to the questions above line up against it. Three patterns make it a clear skip:

1. **Audience mismatch.** If the threads about your category are dominated by small teams or hobbyists and you sell to enterprises (or vice versa), you may earn citations that never reach a real buyer. Read the actual threads before assuming your ICP is there.
2. **Negligible current pull.** Check how much AI engines already retrieve your brand or category from Reddit. If it's a rounding error and there's no obvious path to change that, the channel isn't where your visibility is decided. [How ChatGPT picks sources](/blog/how-chatgpt-picks-sources) shows retrieval is per-query and uneven.
3. **No genuine presence to build on.** Reddit's communities, and the engines reading them. Discount accounts that show up only to promote. If you can't commit to sustained, disclosed, genuinely-helpful participation, a thin promotional presence will underperform or get removed.

Saying no here isn't defeatist. "Do fewer things, but really well" is a defensible AI-visibility strategy, especially for a small team. The failure mode isn't skipping Reddit. It's a half-hearted, promotional Reddit effort that earns a ban and a reputation hit.

> Reddit is structurally favoured by AI engines, but that's a reason to *check* it, not a reason to force it. The brand that skips a poor-fit channel to do two others well usually beats the brand that spreads itself thin across all three.

## What's the honest alternative if you skip Reddit?

The same signal Reddit provides. [Corroborated](/glossary/corroboration), experience-rich evidence that engines trust. Can be built other ways. If Reddit isn't your channel, invest in the levers that are:

- **Specific, well-structured owned content** that answers your buyers' real questions with numeric, named, dated facts. The kind engines lift into answers.
- **Earned placement** in independent [best-of lists](/glossary/best-of-list) and reviews, where [commercial-intent citations actually concentrate](/blog/get-into-ai-cited-best-lists). Pursued on the merits, never by [renting a site's authority](/glossary/site-reputation-abuse).
- **[Entity strength](/blog/entity-strength-ai)**: consistent, corroborated presence across the trusted sources your buyers *do* use, which is the slow, durable lever no algorithm update penalises.

And if you do invest in Reddit, do it the earned way. Never by buying aged accounts or seeding fake threads, which [backfires at both Reddit's layer and the AI engine's](/blog/why-buying-aged-reddit-accounts-backfires).

Whichever way you decide, the input that de-risks it is measurement: know your current Reddit [citation](/glossary/citation) share before you commit, and track whether the channel actually moves your brand into AI answers over time, as a trend across engines, not a single snapshot. That before-and-after view of where you're retrieved and recommended is exactly what **Buffy Intel** measures.

## Your CDN might be blocking the AI crawlers you want
Source: https://heybuffy.com/blog/is-your-cdn-blocking-ai-crawlers

You did everything right. You opened up `robots.txt`, added an `llms.txt`, marked up your pages with structured data. And the AI engines *still* don't seem to see you.

Here's the trap almost nobody checks: the decision about whether a crawler even reaches your site is often made one layer **above** your site. At your CDN.

## robots.txt is a request; your CDN is the bouncer

`robots.txt` is a polite instruction a well-behaved crawler reads **after** it connects to your server. But a CDN or web application firewall (Cloudflare and friends) decides whether that connection is allowed **at all**: before your server, or your `robots.txt`, ever enters the picture.

So if the CDN returns a `403 Forbidden` to a crawler's user-agent, your wide-open `robots.txt` is irrelevant. The bot never gets far enough to read it. You can have the most welcoming robots file on the internet and still be a locked door.

## Why this is suddenly everywhere

In the last year, CDNs shipped one-click "block AI bots" controls, and some made blocking the **default**. As of **July 1, 2025, Cloudflare began blocking AI crawlers by default for new domains**: at sign-up you're explicitly asked whether to allow them, and the default posture is *deny*. (Existing domains weren't auto-flipped, but were handed the same controls.) Cloudflare even lets you decide **separately by what the bot does**: training vs. fine-tuning vs. inference, and offers a "pay-per-crawl" option to charge for access instead of a flat allow/deny. Add the wave of security plugins doing similar, and a lot of sites are now blocking AI bots without anyone on the marketing side knowing.

The tell-tale signature is specific:

- **Browsers** get through (200).
- **Googlebot** gets through (200). These rules usually whitelist classic search.
- **GPTBot, ClaudeBot, PerplexityBot** get a **403**.

Perfect for blocking scrapers. Catastrophic if you actually want to show up in AI answers.

## The 60-second check (do this now)

Pretend to be each AI crawler and see what your site returns:

```
curl -sI -A "GPTBot/1.2 (+https://openai.com/gptbot)" https://yourdomain.com | head -1
curl -sI -A "Mozilla/5.0 (compatible; ClaudeBot/1.0)" https://yourdomain.com | head -1
curl -sI -A "Mozilla/5.0 (compatible; PerplexityBot/1.0)" https://yourdomain.com | head -1
```

How to read it:

- `HTTP/2 200` → the crawler can reach you. Good.
- `HTTP/2 403` → you're blocking it, regardless of what `robots.txt` says. If you also see a `server: cloudflare` header on that 403, your CDN is the one saying no.

Now compare against a normal browser user-agent. **If the browser returns 200 but the AI bots return 403, your edge is the culprit**: not your code, not your robots file.

## How to fix it

- **Cloudflare:** Security → Bots → turn off *Block AI bots / AI Scrapers and Crawlers* (or set it to *Allow*). To keep general bot protection, add a WAF rule that explicitly allows the user-agents you care about: `GPTBot`, `OAI-SearchBot`, `ChatGPT-User`, `ClaudeBot`, `Claude-SearchBot`, `Claude-User`, `PerplexityBot`, `Google-Extended`, `CCBot`.
- **Other CDNs / WAFs / security plugins:** find the "AI bots" or "known bots" rule and allow-list those same agents.
- **Decide per bot, not all-or-nothing.** You might welcome live-retrieval and citation bots while making a separate call on training crawlers, that trade-off is worth a deliberate decision (more in [Should you let AI crawlers index your site?](/blog/should-you-let-ai-crawlers-index-your-site)).
- **Re-test** with the same `curl` commands. You're looking for 200s.

## The bigger point

Allowing access is necessary but not sufficient. A bot that *can* reach a page still has to be able to *parse* it. But access comes first. You can optimize every page on your site, and if the front door is returning 403 to the AI engines, none of it lands.

> An open `robots.txt` that's blocked at the CDN is the most common "invisible to AI" failure there is, and the easiest to miss, because it's silent and it lives in a dashboard marketers never open.

Check the door before you decorate the house. It's exactly the kind of silent gap an AI-readiness audit is built to catch, and the kind of regression ongoing monitoring with **Buffy Intel** flags the moment it reappears.

## How to keep AI crawlers reaching your site after the September 2026 default-block
Source: https://heybuffy.com/blog/keep-ai-crawlers-reaching-your-site

**If you want AI citations, don't let a changed default decide for you.** Cloudflare's [15 September 2026 defaults](/blog/ai-crawler-default-block-2026) block AI training and agent crawlers on ad-bearing pages for new and free-tier sites, while leaving search crawlers allowed. This is a five-step check to make sure the crawlers you actually want can still reach and cite your pages, whatever your CDN's default becomes.

This assumes you *want* AI visibility on most of your content. If your goal is to keep content out of AI entirely, the steps still apply — you just decide the other way at step 3.

## Step 1: Confirm whether the new default reaches you

Start by checking if you're in the affected subset. The September defaults apply to **new Cloudflare customers, new sites added by existing customers, and free-tier users who haven't changed their settings** — not to existing paid sites that already set their own bot rules. If you're a new or free site on Cloudflare, assume the default now leans toward blocking AI training and agent bots on ad pages, and plan to override it deliberately. If you're an established paid site, you're likely unaffected automatically, but audit anyway (defaults drift, and sites get re-provisioned).

## Step 2: Map which of your pages carry ads

The default only bites on **ad-bearing pages**, so find them. List the templates or sections of your site that serve advertising — often article pages, free tools, or high-traffic guides. These are the pages where training and agent crawlers will be blocked by default, and often the very pages you most want [cited](/glossary/citation) in AI answers. Pages with no ads aren't touched by this particular default, so you can prioritise the audit on the ad-supported set.

## Step 3: Decide per crawler class, not with one switch

Blocking is not one decision — it's several. Sort the bots by what they're *for* and choose per class:

| Crawler class | Keep allowed if you want… | Examples |
|---|---|---|
| Live-retrieval / answer | Citations in live AI answers | OAI-SearchBot, ChatGPT-User, PerplexityBot |
| Search indexing | AI Overviews / AI Mode presence | Googlebot, Bingbot |
| AI agent | Agents to complete tasks on your pages | Assorted agent user-agents |
| AI training | Future models to learn about you | GPTBot, Google-Extended, ClaudeBot |

For a brand chasing visibility, the live-retrieval and search rows are usually a clear *allow*. Training crawlers are the genuine judgment call — allow them to be learned, block them to protect proprietary work. Use the full [AI crawler user-agent directory](/blog/ai-crawler-user-agent-directory) to get the tokens right, and read the trade-offs in [should you let AI crawlers index your site](/blog/should-you-let-ai-crawlers-index-your-site).

## Step 4: Set explicit rules so you don't inherit the default

Once you've decided, write it down in your controls rather than leaving the default in place. In Cloudflare that means the managed AI-bot settings plus any bot-management or WAF rules; in [robots.txt](/glossary/robots-txt) it means per-user-agent groups. The point is the same: an explicit *allow* for the crawlers you want, on the pages you want, so a future default change can't silently close them. Remember that a robots.txt line is only a request — the CDN-level rule is what actually enforces on ad pages.

> A default is a decision someone else made for you. On the pages you monetise and want cited, replace it with one you made on purpose.

## Step 5: Verify what's actually allowed

Don't trust the settings screen — check the logs. Fetch a few key pages as the crawler user-agents you care about, or read your server/CDN logs, and confirm those bots get a `200`, not a challenge, a `403`, or a silent block. This is the same discipline as catching an [accidental CDN block](/blog/is-your-cdn-blocking-ai-crawlers): the only proof that a crawler can reach you is a successful fetch in the record. Re-check after 15 September 2026, and again whenever you re-provision or change plans. For an ongoing view of which bots actually reach you, see [how to see which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site).

## The short version

Confirm you're affected, find your ad pages, decide per crawler class, set explicit rules, and verify with logs. Do that once and a shifting default can't quietly cost you citations. Whether AI engines and agents keep reaching, citing, and recommending your pages after infrastructure defaults change underneath you is exactly what **Buffy Intel** monitors, snapshot over snapshot. Questions: support@flash.tech.

## How to keep your products visible to AI shopping agents
Source: https://heybuffy.com/blog/keep-products-visible-to-ai-shopping-agents

Most brands don't have Amazon's problem. While a few large marketplaces deliberately [wall off AI shopping agents](/blog/why-retailers-block-ai-shopping-agents), the typical brand has the opposite problem, it blocks agents *by accident* and never knows. To stay visible, do the reverse of a walled garden: keep the shopping agents reachable, keep your product facts legible, and keep checkout completable.

This is the action companion to the explainer on [why retailers block AI shopping agents](/blog/why-retailers-block-ai-shopping-agents). Below is a 6-step checklist, ordered from highest to lowest return.

## Step 1: Don't disallow the shopping crawlers in robots.txt

Check your [`robots.txt`](/glossary/robots-txt) and confirm you are not disallowing the agents that power AI shopping. The live-answer and search fetchers are the ones that matter for being *cited and recommended* right now:

| Agent | Company | Blocking it costs you |
|---|---|---|
| `OAI-SearchBot` | OpenAI | ChatGPT search and shopping placements |
| `ChatGPT-User` | OpenAI | "Find me the best X" live fetches |
| `PerplexityBot` | Perplexity | Perplexity shopping answers |
| `ClaudeBot` | Anthropic | Claude citations |
| `Google-Extended` | Google | Google's AI surfaces |

Blocking the *training* crawler (`GPTBot`) is a separate, defensible choice; blocking these *live* fetchers directly removes you from AI shopping answers. The full list is in the [AI crawler user-agent directory](/blog/ai-crawler-user-agent-directory).

## Step 2: Make sure your CDN or WAF isn't blocking agents behind your back

This is the most common own-goal, and it is invisible in normal analytics. A `robots.txt` that says "come in" means nothing if your CDN or bot-management layer returns a 403 to the agent first. Fetch three or four key product pages as `GPTBot`, `OAI-SearchBot`, `PerplexityBot`, and `ClaudeBot` and confirm you get HTTP 200, not a 403 or a challenge page. If you see blocks, work through [whether your CDN is blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers) and allow the user-agents explicitly. Do this check first; nothing downstream matters if the agent can't reach the page.

## Step 3: Expose every buying fact as server-rendered text

An agent lifts what it can parse. Put price, availability, variants, shipping, and return terms in the server-rendered HTML as plain text, not only inside JavaScript widgets, images, or PDFs. A [shopper agent](/glossary/shopper-agent) comparing options will use whatever it can read cleanly and skip whatever it can't, routing instead to a marketplace or review site that states the fact plainly. This is the same discipline behind AI-search [citation](/glossary/citation): if the fact isn't readable as text on the live page, it doesn't exist for the agent.

## Step 4: Add product structured data

Mark your buying facts up with [structured data](/glossary/structured-data) so the agent reads them without guessing. Use `Product` and `Offer` for price, availability, and condition, `FAQPage` for question-and-answer blocks, and `Organization` for your entity. Schema doesn't replace on-page text, agents read the visible content too, but it labels *what each fact is*, which reduces misreads when the agent weighs you against alternatives. Getting the feed and the markup right is the whole game in [agentic-commerce readiness](/blog/agentic-commerce-readiness) and in [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents).

## Step 5: Keep discovery and checkout completable on your own site

The surface a closed marketplace can never lock an agent out of is *your own storefront*, so make it work end to end. Search and filtering should function without a bespoke, JavaScript-only interaction an agent can't drive; cart and checkout steps should be reachable with real, semantic `<a>` and `<button>` elements. A page an agent can read but not act on wins the comparison and then loses the sale. This is the mechanics behind [discovering in AI but buying on your site](/blog/discover-in-ai-buy-on-your-site): own the transaction the marketplace is trying to keep.

## Step 6: Monitor across more than one engine

Presence is not uniform. A product visible in ChatGPT can be absent from Perplexity or Google's AI surfaces, because each routes through a different model with different recall, and because each shops a different set of open and closed sources. Track how you are surfaced and compared for the real tasks buyers hand an agent ("best X under $Y for Z"), across engines, not just whether you rank in classic search. The same fragmentation shows up in [how product discovery differs across ChatGPT, Google, and Perplexity](/blog/chatgpt-vs-google-vs-perplexity-product-discovery).

## What about agent checkout protocols like UCP and ACP?

Track and pilot them, but don't treat them as the entry ticket. Being *discovered and recommended* comes first and depends on the six steps above; open checkout standards like UCP and the [Agentic Commerce Protocol](/glossary/agentic-commerce-protocol) matter once an authorized agent is ready to transact. They are moving fast and still settling in 2026, so experiment lightly and fix the reachability and legibility fundamentals first, as covered in [WebMCP vs UCP](/blog/webmcp-vs-ucp).

> In a market where big platforms block on purpose, the brands that win AI shopping are simply the ones that never blocked by accident, and made their product facts easy to read.

Do this well and your products stay selectable by the agents already shopping on your customers' behalf. Knowing whether ChatGPT, Perplexity, Google, and the agents built on them can actually reach and recommend your products, across engines and over time, is exactly what **Buffy Intel** measures. Stay open and legible; verify the agent can find you.

## License, litigate, or block AI crawlers: which posture fits your site?
Source: https://heybuffy.com/blog/license-litigate-or-block-ai-crawlers

**Content owners are taking three distinct postures toward AI crawlers in 2026 — license, litigate, or block — and they optimise for different things.** Licensing trades access for revenue; litigation contests access that was allegedly taken covertly; blocking withholds access to protect content. None is universally right: the posture that fits depends on whether your value is the content itself, your legal resources, and how much you want to be [cited](/glossary/citation) in AI answers. This is a neutral, criteria-based comparison, not a recommendation of one path.

**Last reviewed: 13 August 2026.** The postures below reference public 2026 developments (licensing deals, the News Corp and Reddit lawsuits, Cloudflare's crawler-charging models); terms and defaults are moving, so treat specifics as dated. Each posture links to the deeper corpus piece on it.

## What are the three postures, side by side?

Each posture answers a different question: *how do I get paid, protect my work, or stay visible?* Here is the trade-off on the criteria that matter.

| Criterion | License | Litigate | Block |
|---|---|---|---|
| **Core goal** | Monetise access | Contest covert access | Protect content |
| **Effect on AI citations** | Preserved / encouraged | Neutral | Reduced (you become unreadable) |
| **Who it fits** | Sites with in-demand, licensable content | Large owners with evidence + resources | Content-is-the-product sites |
| **Cost / effort** | Deal-making or metering setup | High (legal) | Low technically, high in lost visibility |
| **Enforcement needed** | Metering / verified identity | Verified-identity evidence | Verified-identity CDN rules |
| **2026 example** | News Corp–OpenAI, Google–Reddit | News Corp v Brave; Reddit v Perplexity | CDN default-block on ad pages |

The one-line summary: **licensing and litigating are both ways to get value from access, while blocking gives up access — and citations — to keep content in.** All three depend on the same technical foundation: knowing who is really fetching you.

## When does licensing access make sense?

Licensing fits when your content is **in demand and identifiable enough to charge for**, and you would rather be paid for access than withhold it. In 2026 the direct-deal version is largely a large-publisher move: reported deals include News Corp–OpenAI (over $250M across five years) and Amazon–The New York Times ($20–25M/year), with most terms undisclosed.

For everyone else, the equivalent is **metered access** rather than a bespoke contract. Cloudflare's [pay-per-crawl and emerging pay-per-answer models](/blog/can-you-charge-ai-agents-to-crawl) let a site price or charge for crawler access at the edge, using the HTTP `402 Payment Required` status and the [x402](/glossary/x402) settlement standard. Licensing keeps you readable — and therefore citable — while capturing value, which is why it is the posture most compatible with wanting AI visibility. It is also the least mature: gated, early, and priced differently by provider.

## When is litigating the right posture?

Litigation fits **large content owners with clear evidence that access controls were bypassed**, not most sites. The 2026 cases show the shape: News Corp sued Brave (filed 22 July 2026) alleging disguised crawlers evaded its blocks, and a federal judge on 31 July 2026 largely refused to dismiss Reddit's "industrial-scale" scraping suit against Perplexity and its data-scraping suppliers. The full detail is in [the 2026 AI-scraping lawsuits](/blog/ai-scraping-lawsuits-2026).

For a smaller site, litigation is rarely practical. The realistic equivalents are **technical enforcement and documentation**: confirm crawlers by verified identity and record non-compliance in your logs, per [checking whether AI bots ignore your robots.txt](/blog/check-if-ai-bots-ignore-your-robots-txt). The indirect benefit of the big cases is real, though: if courts treat evading a block as unlawful, covert scraping gets riskier for everyone, strengthening sites that simply enforce clear rules.

## When should you block — and what does it cost?

Blocking fits sites where **the content itself is the product** — paywalled archives, proprietary datasets — more than brands that want to be recommended. The cost is direct: a crawler you block can't read you, so it can't cite you. [Blocking AI crawlers](/blog/should-you-let-ai-crawlers-index-your-site) trades AI visibility for content protection.

Two caveats make blocking harder than it looks:

- **A blanket block is rarely clean.** A single [user-agent](/blog/ai-crawler-user-agent-directory) can span search indexing, training, and agent fetching, so blocking "the AI bot" can also cut the search crawlers that feed AI Overviews. Decide per crawler class.
- **Enforcement needs verified identity.** Because a self-declared name is spoofable, a real block requires [verified-bot](/glossary/verified-bot) rules at the CDN (reverse-DNS-confirmed IP ranges), not a robots.txt line that non-compliant scrapers ignore. See [is your CDN blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers) for the failure mode where this happens by accident.

## Can you combine postures?

Yes, and most sophisticated owners do. The common pattern in 2026 is **license to the operators you want, enforce verified-identity access against the rest, and reserve litigation for clear, evidenced bypassing** — News Corp licenses to OpenAI and Meta while suing Brave. The postures are not mutually exclusive; they are tools applied per crawler and per content type. The one constant across all three is that they only work if you can tell who is really fetching you.

Buffy Intel measures the visibility side of whichever posture you pick — whether your content is being reached and cited across AI engines, so you can see what a block costs you or what licensed access earns you. Start with a snapshot of where you appear today. Questions: support@flash.tech.

## The listicle rank effect: why your position inside an AI-cited list matters
Source: https://heybuffy.com/blog/listicle-rank-effect

Getting placed into a third-party listicle that AI engines cite is the established play for commercial-intent visibility. The newer finding is that **where you rank inside that list is its own lever**: brands near the top of a cited listicle are named more often, and earlier, in AI answers than brands lower down. As of mid-2026, the position you hold inside the source list partly decides whether you make the AI's shortlist at all.

This piece collects the evidence. Every figure attributed and dated, and turns it into a plan. It builds on [why AI engines cite listicles in the first place](/blog/why-ai-loves-listicles); here the focus is the *ranking within* the list.

## What is the listicle rank effect?

The listicle rank effect is the pattern that a brand's **position inside a third-party roundup** (e.g. "best CRMs for startups") correlates with how visible that brand is in AI-generated answers, not just whether it appears. A higher slot in a cited list tends to mean the brand is mentioned more often, and named earlier, when an AI engine answers the category question.

The mechanism is straightforward. When an engine retrieves a trusted listicle to answer a "best X for Y" query, the order of that list is a signal it carries forward. The brand at the top reads as the strongest candidate; the brand at #9 reads as an also-ran. This is the position-bias side of [why AI loves listicles](/blog/why-ai-loves-listicles), and it sits alongside the broader finding on [where ChatGPT's product recommendations come from](/blog/where-chatgpt-product-recommendations-come-from), which traced most recommendations back to underlying search rank.

## What does the data show?

The clearest single study is **Peec AI's "Listicle Rank Effect" analysis** (Jan Ehrlinspiel, published 14 May 2026). It examined **nearly 200,000 AI responses** generating **5.7 million data points** across **eight AI engines**: ChatGPT, GPT-5 Search, Claude Sonnet 4, Gemini, Google AI Mode, Google AI Overview, Microsoft Copilot, and Perplexity. Over **September 2025 to March 2026**, across three markets: B2B SaaS, emerging MarTech, and US Finance.

The headline effect of moving a brand to **rank #1** inside a cited listicle:

| Market | Visibility lift at rank #1 | Named earlier in the answer | Extra mentions |
|---|---|---|---|
| B2B SaaS | **+16.5 percentage points** | 1.17 positions earlier | +0.43 |
| Emerging MarTech | **+13.4 percentage points** | 0.82 positions earlier | +0.67 |
| US Finance | Large but less predictable ordering | 1.80 positions earlier | +0.66 (not statistically significant) |

Source: Peec AI, *The Listicle Rank Effect* (May 2026). These are single-study, single-vendor figures across three categories. Treat the **direction** (top placement compounds) as firmer than any one number, and note the US Finance mention-count effect was flagged as not statistically significant.

Two independent findings point the same way. Practitioner analyses summarised by digitalapplied (2026) report that roughly **80% of brands mentioned in AI answers appear within the first three positions** of the source list. And our own reference on [where ChatGPT's recommendations come from](/blog/where-chatgpt-product-recommendations-come-from) cites a study where the #1 listicle slot was selected about **2.5× more often than chance**. Different datasets, same shape.

> Being included in a cited listicle gets you on the field. Being near the top of it is what gets you named, and named first. In the answer.

## Does being cited mean being recommended?

No, and this is the trap. A 2026 analysis by Lily Ray (reported by Search Engine Land) found that when a company's **own self-promotional listicle** was cited by Google AI Overviews, the promoting brand was **omitted from the actual recommendation about 69% of the time** (cited 323 times, the promoting brand left out in 224 of them). The page was used as a source; the brand still lost the recommendation to competitors named inside it.

That is the distinction between being [cited versus recommended in AI search](/blog/cited-vs-recommended-in-ai-search). The rank effect operates on the recommendation: it's about your brand's *position in a list an engine trusts*, not about getting your own page quoted. Self-ranking yourself #1 in your own roundup does not trigger it. Engines discount single-brand "best" pages, and Google reduced the visibility of self-promotional listicle sites in its **early-2026** demotion and again in its **May 2026 core update** (Search Engine Land, 2026).

## How do you earn a higher position, not just a mention?

Placement is earned, not bought, so the work is to become the candidate an independent author ranks near the top. The levers that move third-party rank are the same ones that make you a strong AI [citation](/glossary/citation) overall:

- **Be the obvious category fit.** Listicle authors rank by clarity of use-case. Make your specific niche ("expense cards *for startups*") unmistakable and concrete, with named features and numbers rather than vague claims.
- **Build [entity strength](/blog/entity-strength-ai).** Brands that co-occur with the category across the web. Reviews, mentions, comparisons. Are easier for an author (and a model) to place confidently near the top.
- **Get corroborated.** Consistent, third-party-verified facts about your product (pricing, capabilities, who it's for) reduce the risk an author takes ranking you high. This is the [corroboration](/glossary/corroboration) signal engines reward.
- **Pursue earned placement deliberately.** Our playbook on [getting into the best-of lists AI engines cite](/blog/get-into-ai-cited-best-lists) covers the outreach and proof side; the rank effect is the reason it's worth doing well rather than just getting listed anywhere.
- **Keep the lists fresh.** Listicles you appear in decay like any page. The [freshness signal](/blog/content-freshness-citation-cliff) means an updated roundup that ranks you well is worth more than a stale one.

## Why this matters for products and purchase

For commercial-intent questions, the AI's shortlist *is* the consideration set. If a shopper asks an engine for the best option and you're named first, you're in contention; if you're absent or buried, you're effectively invisible at the moment of decision. Industry surveys through 2026 (HubSpot's State of AEO, attributed and hedged) report a meaningful and growing share of buyers acting on AI-surfaced recommendations, so position in the AI's list increasingly shapes which brands get considered, even in zero-click journeys.

The honest caveat: these studies measure **visibility within AI answers**, not purchases directly. The causal chain from "ranked #1 in a cited list" to "more sales" passes through the shortlist, and shortlists are only one input to a buying decision. Measure the link you can see. Your position and presence across engines over time. Rather than assuming the sale.

That measurement is exactly what **Buffy Intel** tracks: where your brand appears in AI answers for the questions your buyers actually ask, which lists you're cited in, and whether your position is improving. Across every major engine, over time. Knowing you're in the roundup isn't enough; the rank effect is the reason you need to know *where*.

## Local AEO vs local SEO: how Google Business Profile, reviews & the map pack feed AI answers
Source: https://heybuffy.com/blog/local-aeo-vs-local-seo

Local AEO and local SEO share an ecosystem but not a scoreboard. AI answers are assembled from the same local web local SEO competes in. Google Business Profile, reviews, directories, so the foundational work transfers. But **AI Mode is a separate ranking system from the local map pack**, and winning one no longer guarantees the other. Here's what carries over and what's genuinely new.

## What transfers from local SEO?

Most of the foundation. AI localizes through the search/retrieval layer, so it reads the same signals local SEO has always optimized:

| Signal | Local SEO role | Local AEO role |
|---|---|---|
| Google Business Profile | Ranks you in the map pack | Feeds Google's AI surfaces directly |
| NAP consistency | Trust + dedupe across the web | Strengthens your entity for retrieval |
| Reviews | Pack ranking + conversion | Among the most-cited local sources |
| Local directories | Citations + referral | Third-party sources AI pulls from |
| Local content / city pages | Organic local rankings | Accurate content for AI to retrieve |

In Whitespark's November 2025 Local Search Ranking Factors survey of 47 local-search experts, Google Business Profile signals were the single biggest factor for the local pack (about 32% weight), while on-page signals led the new AI-search-visibility category. The inputs overlap heavily; get them right and you serve both surfaces.

## What's genuinely new?

Three shifts change the game even though the inputs rhyme:

- **The output is a synthesized answer.** Instead of a ranked list, you get a paragraph that may name you with no click. A [zero-click](/glossary/zero-click-search) recommendation. Being *named* matters as much as being clicked.
- **Citations skew to third parties.** Local AI answers lean heavily on directories and review sites rather than business websites, so earned presence in those sources carries more weight than in classic local SEO.
- **AI ranking is a separate system.** Which leads to the headline divergence below.

## Why doesn't winning the map pack guarantee the AI answer?

Because they're different systems. One 2026 study found that **28.5% of businesses appearing in Google's local 3-pack were absent from AI Mode** for the same query. So more than a quarter of pack winners simply didn't make the AI answer. The [knowledge graph](/glossary/knowledge-graph), reviews, and listings feed both, but the selection logic differs. AI Mode weighs the broader corroborated web, not just proximity and pack signals.

The practical consequence: **measure AI presence on its own**, don't infer it from map-pack position. You can dominate the 3-pack and still be missing from the AI summary above it.

> Winning the map pack and winning the AI answer are no longer the same achievement. They share inputs. Your profile, reviews, and listings, but a quarter of pack businesses don't survive into the AI answer. Track both, separately.

## How does the local ecosystem actually feed the AI answer?

The engine runs a location-aware search, retrieves from the local ecosystem, and synthesizes. Compared with the older [featured snippet](/glossary/featured-snippet), which lifted one source into a box. An AI answer blends *many* sources into one [citation](/glossary/citation)-bearing paragraph. So the brands that show up are the ones whose facts are consistent across the most sources the engine trusts. The deeper mechanics of how engines infer your city in the first place are covered in [how location shapes AI answers](/blog/do-ai-engines-know-where-you-are).

## What to do differently

- **Keep doing the local SEO fundamentals**: they're the shared foundation.
- **Invest harder in earned third-party presence**: directories and reviews punch above their weight in AI answers.
- **Stop treating map-pack rank as a proxy** for AI presence. Measure the AI answer directly.
- **Track citations and presence across engines**, not just position in one.

Local SEO got you ranked; local AEO gets you recommended, and the two now need separate scoreboards. Measuring AI presence and citations city by city, across every engine, alongside your familiar local signals, is exactly the gap **Buffy Intel** is built to close.

## Local AEO: how to get recommended in AI answers for your city
Source: https://heybuffy.com/blog/local-aeo-win-your-city

You can't train an AI to like your business, but you can win the layer it reads from. AI engines localize through web search, not the model, so getting recommended in AI answers for your city is won exactly where local search is won: in [listings, reviews, schema, and the local lists engines cite](/blog/do-ai-engines-know-where-you-are). This is the brand playbook for that work.

The short version: **make your local footprint complete, consistent, and corroborated, then earn your way into the third-party sources AI pulls for your city.**

## How does a brand even influence a local AI answer?

You influence the **retrieval layer**, never the model. When someone asks an engine for the "best [service] near me," the engine runs a location-aware web search and assembles its answer from what it finds: local listings, review platforms, directories, and "best of" roundups. Your job is to be accurate, present, and trusted across those sources so the engine has something correct to repeat.

That reframes the whole task. You are not "optimizing for ChatGPT." You are making your business the clearest, best-corroborated local entity an engine can find, and that work pays off across every engine at once, because they read overlapping sources.

## What's the local AEO playbook?

The levers are familiar from local SEO, re-pointed at citation rather than ranking:

| Lever | What to do | Why AI cares |
|---|---|---|
| Google Business Profile | Complete, verified, accurate categories, hours, services | Google's AI Overviews and AI Mode inherit its local signals |
| NAP consistency | Identical name, address, phone everywhere | Mismatches fracture your entity; engines trust consistent data |
| Reviews | Steady volume + responses across Google and niche platforms | Review sites are among the most-cited local sources |
| Local schema | `LocalBusiness` (or `MedicalClinic`, `LegalService`) with address + geo | Tells machines who and where you are, not guesses |
| Earned best-lists | Get into independent "best [X] in [city]" roundups | These third-party lists are cited far more than owned pages |
| City pages | One real page per location you actually serve | Gives engines accurate local content to retrieve |

The thread through all of it: **engines repeat the local web they can read**. Fix the inputs and the outputs follow.

## Why do reviews and directories matter so much?

Because most local AI citations don't point at the business. They point at third parties. In Whitespark's 2025 study of local AI Overviews, one worked example (plumbers in Houston) found about **60% of citations went to third-party publishers**: Reddit, Quora, Yelp, Thumbtack, HomeGuide and the like, with roughly **40% to individual businesses**. Directionally, that matches what other local-answer analyses report: the review-and-directory ecosystem is doing a lot of the citing.

So a brand that's invisible on the platforms shoppers trust is invisible in the answer, no matter how good its own site is. Build [citation coverage](/glossary/citation-coverage) where the engines actually look: claim and complete your directory profiles, earn reviews steadily, and respond to them.

## How do I earn the "best [X] in [city]" placements?

The same way you earn any independent citation. You don't write it yourself. A self-published "best plumbers in Houston (we're #1)" page is the one format engines reliably discount. Instead, pursue [earned placement in the independent local roundups](/blog/get-into-ai-cited-best-lists) that already rank and get cited: pitch local publications, get listed in reputable niche directories, and give review platforms genuine reasons to feature you.

> Local AI visibility is not won by shouting on your own page. It's won by being the business the trusted local sources already name. Accurately, consistently, and often enough that an engine repeats it.

## What about regulated, high-trust categories?

For [YMYL](/glossary/e-e-a-t) categories. Health, legal, finance. The bar is higher. A fertility clinic or a personal-injury firm competes in a space where engines weigh credibility and [corroboration](/glossary/corroboration) more heavily, and where `MedicalClinic` or `LegalService` schema, verifiable credentials, and consistent professional listings carry real weight. Get the entity facts right and corroborated; thin or inconsistent data is more costly here than anywhere else.

## What to do this quarter

1. **Verify and complete your Google Business Profile**: categories, services, hours, photos.
2. **Audit NAP consistency** across every listing and fix mismatches.
3. **Add local schema** (`LocalBusiness` or your category-specific type) with address and geo.
4. **Build review velocity** on Google and the niche platforms your category trusts.
5. **Pitch for earned inclusion** in independent local best-lists.
6. **Publish one real page per location** you actually serve. No templated stubs.

Doing this once is a start; knowing whether it moved your standing in AI answers, city by city and engine by engine, is the measurement problem, and that's exactly what **Buffy Intel** tracks. The next part of this series shows how to benchmark local AEO across cities so you can prove the work landed.

## How to make your website agent-readable
Source: https://heybuffy.com/blog/make-your-website-agent-readable

An agent-readable website is one an AI browsing agent can parse, navigate, and act on **cheaply and reliably**: without wasting tokens decoding the layout, scripts, and ads built for human eyes. As [agentic commerce](/glossary/agentic-commerce) grows, agents are a fast-growing visitor that reads tokens, not pixels, and a page that's hostile to them means slower tasks, more mistakes about your product, and a weaker shot at being the source an engine cites or buys from.

## Why does agent-readability matter?

Most pages are built for humans: visual layout, client-side scripts, ads, interstitials, and navigation that only makes sense rendered in a browser. An [AI crawler](/glossary/ai-crawler) or browsing agent has to wade through all of that to find the few facts it actually needs.

That has three costs. Agents burn tokens "reading" bloated pages, which is slow and expensive. They guess when structure is unclear, which raises the risk they state something wrong about your product. And the slowest, least reliable sites simply get used less as agents route around them.

The fix isn't a gimmick. It's the same discipline as accessibility and good SEO, aimed at a new reader. Pages that are clean for a screen reader are usually clean for an agent too; see [accessibility and AI-parseability](/blog/accessibility-and-ai-parseability).

## What does the evidence say so far?

Early data is encouraging but thin, and it's vendor-reported, so read it as directional. In a 2026 benchmark by the agent-infrastructure vendor TollBit, with browser-infrastructure company KERNEL, sites optimised for agents ("Agent Sites") were measured against their standard counterparts:

| Metric (vendor-reported) | Reported result |
|---|---|
| Time to complete a task | 24-35% faster on every site tested |
| Task completion rate | 100% across all five optimised sites |
| Steps per workflow | 18-38% fewer (fewer screenshots, fewer tokens) |

These figures come from a single vendor across five sites, self-reported, so treat them as a hypothesis to verify on your own properties rather than an industry benchmark. The direction. **Less to parse means faster, more reliable, cheaper agent tasks**: is consistent with how token-based retrieval works.

> Agents don't reward beautiful pages; they reward legible ones. Every token an agent spends decoding your layout is a token it isn't spending understanding your product.

## How do you make your site agent-readable?

A practical sequence, foundations first:

1. **Serve crawlable, server-rendered HTML.** If facts only appear after JavaScript executes, many agents never see them. Confirm your content is in the initial HTML and that your [CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers).
2. **Use real semantic structure.** Proper headings, lists, tables, and `<button>`/`<a>` elements, not `<div>` soup. Semantic markup is what lets an agent map the page without guessing.
3. **Expose a machine-readable representation.** Offer your core content as clean Markdown or text for simpler bots, while keeping the interactive HTML for advanced agents. The goal is that a bot can read semantically structured content directly instead of reverse-engineering a visual page.
4. **Label actions and state clearly.** Forms, buttons, and prices should be explicitly named and reachable, so an agent can complete a task. Add to cart, check availability. Without inferring what a control does.
5. **Put facts in [structured data](/glossary/structured-data).** Product, price, and availability markup tells an agent exactly what you sell instead of leaving it to parse prose.
6. **Trim what agents don't need.** Strip or de-prioritise ads, pop-ups, and decorative scripts on the paths agents use; every removed distraction is saved tokens and fewer wrong turns.

## How does this connect to getting recommended?

Agent-readability is the access layer. Necessary, not sufficient. An agent that can read and transact on your site still has to *choose* you, which is the work of being extractable, corroborated, and recommended across engines. Two adjacent pieces go deeper: [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents) covers the data side, and [agentic commerce readiness](/blog/agentic-commerce-readiness) covers the broader checklist for transacting with agents. (Wondering whether a dedicated [llms.txt](/glossary/llms-txt) file helps? We weigh that in [is llms.txt worth it](/blog/is-llms-txt-worth-it).)

Make the site legible first, then make it the obvious choice, and measure whether agents and engines actually surface you over time. Watching that visibility across every engine, sampled repeatedly, is what **Buffy Intel** is built for.

## Why is Google showing markdown files in AI Overviews?
Source: https://heybuffy.com/blog/markdown-files-in-ai-overviews

In early July 2026, SEOs noticed **Google AI Overviews pulling the raw contents of markdown (`.md`) files directly into their citations**: tables and text lifted from a page's underlying markdown rather than its rendered HTML. Google's John Mueller called the behaviour "unexpected" and said it does **not** mean Google treats markdown files any differently from other content. The short version: this is a crawlability curiosity, not a new ranking lever.

This is part of the [crawlers and technical](/blog/should-you-let-ai-crawlers-index-your-site) series and a close companion to our pieces on [why Google says llms.txt is flawed](/blog/why-google-says-llms-txt-is-flawed) and the [honest take on whether llms.txt is worth it](/blog/is-llms-txt-worth-it), because the underlying lesson is the same one, from a new angle.

## What did people actually see?

Markdown content appearing where you'd expect rendered page content. The observation was surfaced publicly by SEO practitioner Lily Ray, who posted (on Bluesky) an example of markdown-formatted tables showing up inside [AI Overview](/glossary/ai-overviews) citations and asked whether there was anything SEOs should read into it. John Mueller of Google replied directly:

> "That looks unexpected. Can you DM me the details?"

That reply is worth reading precisely. "Unexpected" is not "intentional," and it is not "a signal." It's Google's own engineer saying the surfaced markdown wasn't the product of a deliberate markdown-handling feature. Treat the whole episode as an anecdote from the field. A handful of observed examples in early July 2026, not a documented change to how AI Overviews are built.

## Why would a markdown file end up in an AI Overview?

Because Google indexes files on the open web, and a reachable `.md` file is just another file. There's no exotic explanation needed. If a markdown file is publicly accessible and not blocked from crawling, Google can fetch it, index it, and make it eligible to be surfaced. Including as a source in an AI Overview. The same way any HTML page is. Mueller's framing was exactly this: Google does not consume markdown files (or llms.txt) as special inputs for Search, so what happened is most likely that the crawler simply picked up a markdown file like any other document.

Two things make markdown a slightly more likely candidate to be lifted verbatim than you might expect:

- **Markdown is already clean, extractable text.** No navigation, no scripts, no chrome. Just headings, lists and tables. That's the exact shape retrieval and answer-generation systems find easy to parse, which is the whole reason we push for [semantic, parseable structure](/blog/accessibility-and-ai-parseability) in the first place.
- **Raw `.md` files are often published without anyone deciding they should be.** README files, documentation sources, exported content and build artifacts routinely sit at public URLs. Nobody wrote them as pages, but they're crawlable, so they're fair game.

## Does this mean markdown is a ranking or visibility lever?

No, and reading it that way is the trap. This is where the episode connects to the larger debate. Google's Mueller has repeatedly pushed back on the idea of publishing markdown-only pages "for the bots," and the reasoning is identical to the [llms.txt argument](/blog/why-google-says-llms-txt-is-flawed): a stripped, owner-controlled copy you create specifically to influence machines is a weak signal, not a strong one. A markdown file surfacing once by accident doesn't reverse that.

| Reading of the episode | Accurate? | Why |
|---|---|---|
| "Markdown gets a boost in AI Overviews" | No | Mueller: no special treatment; it's indexed like any page |
| "I should publish markdown mirrors of my pages" | No | Same weak-signal mistake as a [separate AI-only site version](/blog/separate-ai-version-of-your-website) |
| "Anything crawlable can be surfaced, including raw files" | Yes | A reachable `.md` file is eligible like any other document |
| "My canonical HTML is what I should invest in" | Yes | One set of clean, crawlable pages remains the durable play |

The pattern that keeps repeating: **you don't get to choose which version of your content a machine lifts.** You only get to control whether the *right* version. Your real, canonical, crawlable HTML page. Is reachable and clean enough to be the obvious choice.

## What should you actually do about it?

Audit what's crawlable, then invest in the canonical page. Nothing here calls for a new markdown strategy; it calls for hygiene and focus.

1. **Inventory your stray files.** Check whether raw `.md` files (READMEs, `/docs` sources, exported drafts, static build artifacts) are publicly reachable on your domain. Decide deliberately whether each *should* be indexable. If a markdown source duplicates a real page, you generally want the HTML page to be the canonical, indexable one.
2. **Don't block AI crawlers by accident, or leave the wrong things open.** This is the same discipline as [making sure your CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers): know what's reachable and to whom, in both directions.
3. **Keep your canonical HTML clean and answer-first.** The reason markdown looked "liftable" is that it's structured plain text. Your rendered pages should be, too. Real headings, lists and tables, server-rendered, with the facts in the text. Build that into the page you actually want cited, per [making your site agent-readable](/blog/make-your-website-agent-readable).
4. **Don't chase the anecdote.** One observed behaviour, called "unexpected" by Google itself, is not a roadmap. If you want to influence AI Overviews, the documented levers are still content quality, structure and corroboration. See [how to optimise for AI Overviews](/blog/how-to-optimize-for-ai-overviews).

The durable takeaway is the one this series keeps landing on: AI systems reward content that is reachable, clean and corroborated, and they discount signals you fully control. A markdown file drifting into an AI Overview is a reminder that *everything* on the open web is fair game, so put your effort into the one canonical version you want machines to find, and know exactly what else you're leaving reachable. Tracking which of your pages AI engines actually pull from is what **Buffy Intel** measures. Questions: support@flash.tech.

## How to find and match your industry's AI citation fingerprint
Source: https://heybuffy.com/blog/match-your-industry-citation-fingerprint

**To find your industry's AI citation fingerprint, collect your buyers' real questions, capture the sources each AI engine cites for them, tag every cited page by type, and see which formats recur — then invest in the winning format and check whether your own domain gets cited at all.** This turns the [per-industry fingerprint data](/blog/ai-citation-fingerprint-by-industry) into a workflow you can carry out for your own category.

The reason to bother: a July 2026 DeltaV Digital study of 25,337 citations found the dominant cited page type flips by vertical — listicles won about 61% of citations in B2B tech services, homepages about 55% in local medical aesthetics, program pages about 53% in higher education. Copying a generic checklist means optimising for the wrong format. The steps below are ordered so you know *what* to publish and *where* (owned versus earned) before you spend on content.

## Step 1: Gather your buyers' real questions

List 20–40 genuine questions your buyers ask AI engines about your category, spanning the intent branches an AI answer fans out into: definitions, comparisons, how-tos, buying decisions, and troubleshooting.

- Pull them from sales calls, support tickets, your site search, and the "People also ask" style follow-ups engines surface.
- Cover the [full question tree](/blog/how-to-get-cited-by-ai), not just your head term — engines assemble one answer from many sub-queries, so a thin query set gives a thin fingerprint.

## Step 2: Capture the cited sources per engine

Put each question through the engines your buyers actually use — ChatGPT, Perplexity, Gemini, Google AI Overviews, Google AI Mode — and record every source each answer cites.

- Log the URL, the domain, and which engine cited it.
- Keep engines separate. Citation patterns differ by engine, so a blended list hides which format wins where. This is the same per-engine discipline behind [auditing your site for AI visibility](/blog/how-to-audit-your-site-for-ai-visibility).

## Step 3: Tag each cited page by type

Assign every cited URL exactly one page type, from a short fixed list, so the tally is comparable across queries.

- A workable set: article/blog, listicle, product page, comparison page, homepage, how-to guide, program or service page, forum/UGC.
- Tally the share each type earns across your whole query set. The type with the largest share is the leading edge of your fingerprint. Comparison pages, in the DeltaV data, were a small share but the most *efficient* per retrieval — note efficiency as well as raw share.

## Step 4: Measure your own-domain citation share

Separate the cited sources into "your own domain" versus "third-party," and calculate the percentage that came from your site.

- This is the number that decides your strategy. In the DeltaV data, higher education earned about 74.7% of citations from its own domain, while B2B technology services earned **0.0%** — every citation was a third-party listicle or directory.
- **High own-domain share** → your own pages can be the citation; invest in [clean, structured, extractable pages](/blog/prioritize-your-structured-data).
- **Low own-domain share** → engines will not cite your site for these queries; prioritise [earned placement in independent lists](/blog/get-into-ai-cited-best-lists) and reviews.

## Step 5: Match the winning format, then raise its evidence density

Publish or earn placement in the format your fingerprint rewards — and make that format as citable as possible.

- If listicles win your category, pursue genuine inclusion in third-party [best-of lists](/glossary/best-of-list); if product or program pages win, make yours [quotable word-for-word](/blog/write-conversational-product-pages).
- Inside the winning format, apply the [edits that lift citations](/blog/what-content-changes-lift-ai-citations): a specific attributed statistic per claim, a credible quote, inline sources, and answer-first passages. Format gets you in the candidate pool; [evidence density](/glossary/corroboration) gets you kept.

## Step 6: Re-check per engine on a cadence

Re-sample the same query set quarterly, and after any major engine change, so you catch the fingerprint shifting before your citations fade.

- Compare like with like — same questions, same page-type tags — and watch for a format gaining or losing share over time.
- Citations decay after roughly a quarter, so pair the fingerprint check with a [freshness refresh](/blog/content-freshness-citation-cliff) on your highest-value pages.

> Do not guess your format from a generic checklist. Map which page types AI engines actually cite for your buyers' questions, check whether your own domain is ever among them, and put your budget where your category's fingerprint already points.

Doing this by hand once is useful; doing it continuously is where the value compounds, because fingerprints move as engines change. That is where **Buffy Intel** fits: it snapshots which page types, domains, and — crucially — whether *your own* pages get cited across engines for your category, over time, so you can see your fingerprint shift and re-point your content before your citations quietly decay.

## How to measure AI visits that arrive days after the prompt
Source: https://heybuffy.com/blog/measure-delayed-ai-visits

To measure AI visits that arrive days after the prompt, **widen your attribution window to at least seven days, treat branded search and direct as AI-influenced channels rather than waiting for a labelled referral, and read the deep-landing-page and branded-search fingerprints as your signal.** AI-referred traffic is late and indirect by nature — the measurement has to match. This how-to turns the [prompt-to-visit lag](/blog/when-do-ai-referrals-arrive) into a repeatable method.

## Step 1: Widen the attribution window to at least 7 days

The default same-session or same-day window is the first thing that hides AI. Gener8's July 2026 data shows the [prompt-to-visit rate](/glossary/prompt-to-visit-rate) climbing 9x to 10x between the 1-hour mark and 72 hours after a prompt; Similarweb measured its 2.5x visit lift over a **7-day** window. Set a look-back of at least seven days — longer for research-led categories like B2B SaaS, where visits keep accumulating past 72 hours. A last-click model that credits only the final touch will assign almost none of this to AI.

## Step 2: Stop waiting for a labelled AI referral

Most AI-influenced visits never carry an AI referrer. Similarweb found **55.9%** of them arrived via a search engine and only about **19.9%** arrived directly — the person re-searches the brand after an AI answer names it. So instrument the channels where the visit actually lands:

- **Branded search.** Track branded-query impressions and clicks in Search Console as a first-class AI signal, not a vanity metric. A lift here that follows your rising AI citations is AI demand arriving through search.
- **Direct-to-deep-page.** Capture the [dark traffic](/glossary/dark-traffic) that lands with no referrer, as covered in [why your AI traffic shows up as "Direct"](/blog/why-ai-traffic-shows-up-as-direct).
- **Labelled AI referrals.** Still worth a [dedicated GA4 channel](/blog/ga4-ai-referral-dashboard) — just treat it as the visible minority, not the whole channel.

## Step 3: Baseline the fingerprints before you change anything

You can only spot a lift against a baseline. Before a visibility push, record your normal levels of: branded-search volume, the share of "Direct" sessions landing on non-homepage URLs, and the new-user share on those deep-landing sessions. Someone typing your URL lands on the homepage; someone acting on an AI recommendation lands deep, on the specific page that answered them. A rise in deep, first-time "Direct" sessions is one of the cleanest fingerprints of AI-driven demand.

> Don't hunt for a single referrer that proves AI sent the visit — it usually isn't there. Watch three signals move together: branded search up, deep-landing direct sessions up, new-user share up, all in step with your tracked AI citations. That correlation is the honest evidence.

## Step 4: Segment by vertical and intent

A blended number lies. Gener8's prompt-to-visit rate ranges about 4x across categories (B2B SaaS 14.1% vs Apparel & Fashion 3.5% at 24 hours), and the *shape* of the lag differs too. Split your measurement by product line or intent type so a fast-converting category doesn't mask a slow one — and so your benchmark compares like with like.

## Step 5: Tie delayed visits back to the prompt that caused them

A late, indirect visit is only half the story; the other half is *which* AI answer set it in motion. Pair your traffic view with upstream visibility tracking — which prompts surface your brand, on which engines, and whether your pages are the cited source. When a branded-search lift follows a spike in citations for a specific topic, you have connected cause to effect across the lag. This is the join that last-click analytics can't make, and it is the core of the [reporting stack](/blog/ai-visibility-reporting-stack) that ties AI visibility to [converting traffic](/blog/prove-ai-traffic-converts).

## Step 6: Give it a quarter, and read it as a curve

Two lags stack here. The [citation lag](/blog/chatgpt-citation-lag) means a new page may not be cited for weeks; the prompt-to-visit lag means each answer's visits then arrive over days. Add the [three-month citation cliff](/blog/content-freshness-citation-cliff) and the honest evaluation window for a new page is a full quarter. Read AI's impact as a curve that builds and decays, not a same-day spike — and refresh competitive pages before the cliff rather than judging them dead early.

The method in one line: widen the window, measure search and direct as AI channels, fingerprint the deep-landing sessions, and connect the delayed visit to the prompt behind it. Doing that continuously, across every engine and over time, is exactly what **Buffy Intel** is built to provide.

## How to mine Search Console with regex to find AI-search questions
Source: https://heybuffy.com/blog/mine-search-console-for-ai-questions

Google Search Console (GSC) holds a trove of the real questions people already type to reach you, and a regex filter turns that into a list of the *question-shaped* queries worth building AI-citable content around. This method comes from a widely-shared June 2026 LinkedIn tip by SEO practitioner **Mark Williams-Cook**: instead of asking an AI to guess your query data, filter GSC's own Performance report by intent. Here's how, and how to use the output for AI search.

## Why mine Search Console for AI search at all?

First, an honest scope note. GSC reports **classic Google Search queries, not** the prompts people enter into [AI Mode](/blog/how-google-ai-mode-works), ChatGPT, or Perplexity, which no platform exposes as a clean log. So this is a **proxy**, not a direct AI-query feed. (One 2026 nuance: [AI Mode's own follow-up turns *do* land in this report](/blog/ai-mode-conversations-in-search-console) as conversational fragments — but they're unlabeled and can't be segmented, so the proxy framing still holds for AI intent overall.)

It's a good proxy, though. The longer, question-shaped queries you already rank for are exactly the intent AI engines decompose into sub-queries when they [fan out](/blog/how-query-fan-out-works). Mining them tells you which questions you have real demand and standing for. The strongest candidates to answer extractably and to add to your tracked [prompt](/glossary/prompt) set. It pairs directly with [how to choose which prompts to track](/blog/how-to-choose-prompts-to-track).

## How do you filter Search Console by regex?

The steps, per the source method:

1. Open **Google Search Console** and go to the **Performance** report.
2. Click **"+ New"** / **Add filter** at the top of the report.
3. Choose **Query**.
4. Switch the match drop-down to **Custom (regex)**.
5. Paste one of the intent patterns below and apply it.

The table then shows only the queries matching that intent. Export each one to build an intent-segmented map of the demand you already capture.

## Which regex patterns surface AI-search intent?

Each pattern isolates a different intent. Treat them as starting points and adapt to your vocabulary:

| Intent | What it surfaces | Regex (Query → Custom regex) |
|---|---|---|
| Informational | Guides, tutorials, how-tos | `\b(how to|guide|tutorial|step by step|tips|ways to|learn|explain|examples|meaning|definition)\b` |
| Comparison | "best", "vs", "alternative" | `\b(best|vs|versus|compare|comparison|alternative|better|cheaper|top|difference)\b` |
| Product / service | "is X good?", "where to buy X" | `\b(price|cost|buy|quality|brand|reviews|ratings|features|specifications|warranty|options|model)\b` |
| Transactional | Buying, pricing, locations | `\b(buy|purchase|cheap|discount|deal|coupon|order|near me|online|sale|in stock)\b` |
| Navigational | Brand, reviews, support | `\b(review|warranty|return policy|refund|complaint|feedback|legit|trustworthy|problems|issues)\b` |
| SaaS / tools | Tool-seeking queries | `\b(?:tool|software|app|platform|application|solution|suite|service)s?\b` |
| Likely questions | Queries of 4+ words | `(\w+\s){4,}` |

The SaaS/tools pattern is credited in the source to **Pietro Mingotti**; the 4+-word pattern catches the long, natural-language queries that look most like AI prompts. Apply each as a separate filter and read the *proportions*, which intents you already win, and which you barely show up for.

> The questions people already ask Google to find you are the cleanest signal of the AI prompts you should be answering. Extract them, then make each one a self-contained, answer-first chunk.

## What do you do with the extracted queries?

Turn demand into citable content and a tracking list:

- **Group by intent**, then check whether you have an **answer-first chunk** for each high-volume question. Gaps are your content brief. This is the [query fan-out content loop](/blog/query-fan-out-content-loop) in practice.
- **Promote the recurring questions to tracked prompts** so you can measure AI visibility, not just classic rank. The bridge to [why you might be invisible in AI search](/blog/why-youre-invisible-in-ai-search) despite ranking.
- **Refresh the pages** that win these queries, since live AI retrieval favours [recently-updated content](/blog/content-freshness-citation-cliff).

## What are the limits to watch?

Read this directionally, not as gospel. As practitioner **Ryan Jones** noted on the same thread, regex filters change GSC's metrics to sum across matching pages, which can **inflate impression counts**: so trust the *patterns and proportions*, not exact totals. GSC also samples and thresholds query data, and the same regex works in other tools that support it (such as Ahrefs) if you want a second view. And remember the headline caveat: this is classic-search demand standing in for AI intent, so corroborate it against your own AI-visibility snapshots.

That corroboration. Taking these real questions, posing them across ChatGPT, AI Mode, Perplexity, and Claude, and tracking whether your brand is named and your pages cited over time. Is exactly what **Buffy Intel** is built to do.

## Which domains does Google AI Overviews cite most? (mid-2026 data)
Source: https://heybuffy.com/blog/most-cited-domains-ai-overviews

**As of mid-2026, YouTube is the single most-cited domain in Google AI Overviews, at about 20.9% mention share, narrowly ahead of Reddit. The top of the list is dominated by video, community, and social platforms, not brand-owned sites.** This is a dated, fully-attributed reference to which domains Google's AI Overviews pull from most, why you'll see two different numbers quoted for YouTube, and what the pattern means for your own site.

**Last reviewed: 19 July 2026.** The share table below is from Ahrefs' Brand Radar, tracking every domain [AI Overviews](/glossary/ai-overviews) cited across more than 3 million US queries (published 1 June 2026). The out-of-top-100 and all-citation figures are from a separate Ahrefs analysis of 863,000 keyword SERPs and 4 million AI Overview URLs (data as of 2 March 2026). Both are single-vendor (Ahrefs), specific to Google's AI Overviews rather than every AI engine, and directional.

## Which domains does Google AI Overviews cite most?

Here is Ahrefs' ranked list of the top-cited domains in Google AI Overviews, by mention share, which Ahrefs defines as a domain's citations as a percentage of the summed citations of the top sources:

| Rank | Domain | Mention share | Type |
|---|---|---|---|
| 1 | youtube.com | ~20.9% | Video |
| 2 | reddit.com | ~19.6% | Community |
| 3 | facebook.com | ~11.6% | Social |
| 4 | google.com | ~6.0% | Search / owned |
| 5 | instagram.com | ~5.2% | Social |
| 6 | en.wikipedia.org | ~4.8% | Reference |
| 7 | amazon.com | ~4.0% | Commerce |
| 8 | quora.com | ~4.0% | Community |
| 9 | tiktok.com | ~3.6% | Video |
| 10 | walmart.com | ~0.9% | Commerce |

Source: Ahrefs Brand Radar, published 1 June 2026 (3M+ US queries). The one-line read: **AI Overviews cite video, community, and social platforms far more than any brand's own site.** Ahrefs counted 1,545,623 distinct YouTube pages cited, which is what pushes it to the top.

## Wait, is YouTube really cited more than Reddit?

Inside Google AI Overviews, yes, but the two are close enough to call co-leaders. YouTube's ~20.9% mention share edges Reddit's ~19.6%. The scope matters, though. Our [reconciliation of the citation-concentration studies](/blog/ai-citation-domain-concentration) notes Reddit is the more commonly reported **#1 source across engines** such as ChatGPT and Perplexity. There's no contradiction: this page is about Google AI Overviews specifically, where video leads, while Reddit's crown is an across-engine, community-heavy result. "Most-cited" always needs an engine and a denominator attached.

That denominator point also explains a number mismatch you'll come across. You'll see YouTube quoted at both **~20.9%** and **~5.6%**, and both are correct:

| What's being measured | YouTube figure | Source (date) |
|---|---|---|
| Mention share among the top cited sources | ~20.9% | Ahrefs Brand Radar (Jun 2026) |
| Share of **all** AI Overview citation URLs | ~5.6% | Ahrefs, 863K SERPs (Mar 2026) |
| Share of citations that ranked **outside Google's top 100** | ~18.2% | Ahrefs, 863K SERPs (Mar 2026) |

The ~20.9% is a share of the top sources' citations; the ~5.6% is a share of every citation across the whole dataset. Different denominators, same underlying reality: YouTube is the most-cited single domain either way. Read the pattern, not the point estimate.

## Why does Google AI Overviews lean on YouTube and social so heavily?

Three durable reasons, not a quirk of one month:

- **Google owns YouTube.** Google can index and understand YouTube's [multimodal](/glossary/multimodal-search) content, transcripts included, more readily than the open web, and it has an obvious incentive to surface its own video property in answers.
- **Community content carries first-hand experience.** Reddit, Quora, and forums hold the lived, specific answers Google's quality guidance keeps asking for, which is why they sit alongside video at the top.
- **AI Overviews citation is decoupling from classic rank.** Ahrefs found only about **38% of AI Overview citations now come from pages ranking in Google's top 10, down from about 76% a year earlier**, and roughly 18.2% of the citations that ranked outside the top 100 were YouTube URLs. We unpack that rank-decoupling in [does ranking on Google get you cited by AI](/blog/does-google-rank-get-you-cited-by-ai). A page no longer has to rank to be cited, which opens the door to video and community sources.

> In Google AI Overviews, the most-cited domain isn't a publisher or a brand. It's YouTube, narrowly ahead of Reddit. Video and community are where AI answers are sourced, and a classic top-10 ranking is no longer the price of admission.

## What does this pattern mean for your own domain?

That your homepage is unlikely to be the thing AI Overviews cites, and that's the point. Even the largest commercial domains sit low on the list (Amazon ~4.0%, Walmart ~0.9%), so the leverage is in earning presence on the platforms AI Overviews already trusts, then backing it with entity strength:

- **Publish extractable video.** Because YouTube is the #1 cited domain and Google owns it, well-structured video is a high-leverage, low-crowd surface. The method is in [how to earn AI Overview citations from YouTube video](/blog/how-to-earn-ai-citations-from-youtube), and the concept is [video AEO](/glossary/video-aeo).
- **Take community seriously.** Reddit and Quora carry real citation weight; see [how to use Reddit for AI search visibility](/blog/how-to-use-reddit-for-ai-search-visibility).
- **Build entity strength that travels.** A separate Ahrefs study of 75,000 brands (released May 2026) reported YouTube mentions correlated with AI brand visibility more strongly than any other metric, while link volume and page count correlated only weakly. Consistent, corroborated presence is the durable lever: [entity strength for AI search](/blog/entity-strength-ai).
- **Measure where you're actually cited.** Which domains an engine cites in aggregate is context; whether *your* brand shows up, on each engine, over time, is the signal. That's [how to measure AI visibility](/blog/how-to-measure-ai-visibility).

The domain leaderboard tells you where AI Overviews look for answers. What decides your visibility is whether your content, on the surfaces those engines trust, actually gets named and cited, measured on your own footprint and across engines over time. That is exactly what **Buffy Intel** is built to track.

## How to optimize your site for agentic browsers (Comet, ChatGPT, Dia)
Source: https://heybuffy.com/blog/optimize-for-agentic-browsers

To optimise for an [agentic browser](/blog/what-is-an-agentic-browser), make the **live page do the work the agent needs**: expose every decision-driving fact as server-rendered plain text, mark it up with schema, keep task flows completable, and confirm AI agents aren't blocked before they arrive. Agentic browsers, Perplexity's Comet, The Browser Company's Dia, and OpenAI's ChatGPT browsing agent (moved from the retired standalone Atlas into the ChatGPT app in August 2026), read the visible page and act across sites, so the durable rule is: if a fact isn't readable on the page as text, it doesn't exist for the agent.

This is the action companion to the explainer on [what an agentic browser is and how brands show up in one](/blog/what-is-an-agentic-browser). Below is a 6-step playbook, ordered from highest to lowest return.

## Step 1: Expose every decision-driving fact as extractable text

Put prices, specs, availability, shipping, and comparison facts in the server-rendered HTML as plain text, not only in JavaScript widgets, PDFs, or images. An agent reading the visible page lifts what it can parse; anything it can't read cleanly is skipped, and it will route to a third party (a review site, a marketplace) that does state the fact plainly.

- **Do:** state the price, the spec value, and the in-stock status as text on the page.
- **Avoid:** locking those facts in a script-rendered component, an image, or a downloadable PDF.

This is the single highest-return change, and it is the same discipline behind AI-search [citation](/glossary/citation): the agent, like the answer engine, uses whatever it can extract.

## Step 2: Mark it up with structured data

Add [structured data](/glossary/structured-data) so the agent reads your facts without guessing. `Product` and `Offer` for items (price, availability, condition), `FAQPage` for question-and-answer blocks, `Organization` for your entity. Schema doesn't replace on-page text, agents and engines read the visible content too, but it labels *what each fact is*, which reduces misreads when the agent compares you against alternatives. This overlaps directly with [agentic-commerce readiness](/blog/agentic-commerce-readiness), where clean product data is the whole game.

## Step 3: Keep task flows completable

Agentic browsers try to *act*, not just read. If the agent is asked to compare, add to cart, or start a booking, a flow it can't complete is a point where you fall out of the task. Check that:

- Search and filtering work without a bespoke, JavaScript-only interaction the agent can't drive.
- Cart, checkout, and booking steps are reachable and don't depend on undocumented client-side state.
- Key actions use real, semantic `<a>` and `<button>` elements, not `<div>` handlers, the same reason [accessibility and AI-parseability are one discipline](/blog/accessibility-and-ai-parseability).

A page an agent can read but not *act on* wins the comparison and then loses the task.

## Step 4: Make sure AI agents can reach you at all

None of the above matters if the agent is blocked at the door. Confirm your robots rules and, critically, your CDN or bot-management layer aren't returning 403s to AI agent traffic. A [CDN silently blocking AI crawlers and agents](/blog/is-your-cdn-blocking-ai-crawlers) is the most common own-goal: you look optimised, but the agent never sees the page. Verify reachability first, then optimise the content behind it, and treat your site as a legible [agent endpoint](/blog/websites-as-agent-endpoints).

## Step 5: Earn third-party corroboration

Agents surf review sites, comparison articles, and community threads when weighing options, so your presence *off* your own domain shapes what the agent recommends. You own your facts; you earn the recommendation. Pursue accurate representation in reviews and independent lists the way you would for [getting cited by AI](/blog/how-to-get-cited-by-ai), because the agent treats a corroborated option as safer to choose than a lone self-claim. This mirrors [how AI engines choose which brands to name](/blog/how-ai-engines-choose-brands).

## Step 6: Monitor across more than one engine

Comet, ChatGPT's in-app browser (OpenAI retired the standalone Atlas in August 2026), and Dia route through different AI models, so brand recall differs by surface. Watching one is watching one window. Track how you're summarised and compared for the real tasks your buyers hand an agent, "find the best X for Y", across engines, not just whether you rank in classic search. The same fragmentation shows up in [how product discovery differs across ChatGPT, Google, and Perplexity](/blog/chatgpt-vs-google-vs-perplexity-product-discovery); agentic browsers add another set of surfaces on top.

## What about agent protocols like WebMCP and UCP?

Track and pilot them, but don't rebuild around one yet. Standards for direct agent-to-site interaction, [WebMCP and UCP](/blog/webmcp-vs-ucp) among them, are moving fast and still settling in 2026. The legibility fundamentals above pay off whether an agent reaches you through a browser, a search engine, or a protocol, so do that work first and experiment with protocols lightly.

> Optimising for an agentic browser isn't a new channel to buy, it's making the page you already have readable and actionable enough that an agent can choose you without a fight.

Doing this well makes your site selectable by the agents already browsing on your customers' behalf. Knowing whether Comet, ChatGPT, Dia, and the AI engines behind them actually surface and recommend your brand, across engines and over time, is exactly what **Buffy Intel** measures. Make the live page actionable; verify the agent chose you.

## How to win AI Mode's 'Do' intent: a playbook for planning queries
Source: https://heybuffy.com/blog/optimize-for-ai-mode-planning

Planning is the fastest-growing thing people do in [Google AI Mode](/glossary/google-ai-mode). In Google's 2026 report *"How people are using AI Mode in the U.S."*, planning-style "Do" queries grew about **80% faster than AI Mode queries overall**: the fastest-growing behaviour Google named, ahead of "which" decision queries (+40%) and brainstorming (+30%). For any brand whose customers plan trips, workouts, projects, meals, or events, that makes the "Do" intent a direct channel. This playbook turns it into a content plan.

It draws on Google's documented usage data and applies the same method as the rest of the corpus. It is the "Do" companion to the [Decide/shopping](/blog/optimize-for-ai-mode-shopping) and [Learn](/blog/aeo-for-education-and-learning-content) playbooks. All figures are Google's own platform data, dated to mid-2026 and not independently audited, so read the direction (planning is a large, fast-growing use of AI search) as firmer than any single number.

## Why is the "Do" intent worth optimising for?

Because it is where AI Mode is growing fastest and where the questions are unusually answerable. Google groups AI Mode usage into five intents. Explore, Decide, Learn, Create, and **Do**: and reports how each grew against AI Mode queries overall:

| Behaviour | Intent | Growth vs AI Mode queries overall |
|---|---|---|
| **Planning** | **Do** | **+80% faster** |
| "Which" decision queries | Decide | +40% faster |
| Brainstorming | Explore | +30% faster |
| Image creation | Create | More than tripled since the start of the year |

Source: Google, AI Mode U.S. Insights report (mid-2026). Google describes "Do" as logistics, schedules, to-do lists, and exercise plans, and has surfaced planning inside AI Mode's Canvas planning experience. Two behaviours make planning content a natural fit: AI Mode queries are about **triple the length** of a classic search, and follow-ups grew **more than 40% per month**: the shape of someone working a task through step by step.

> A planner rarely asks one question. They ask what the steps are, in what order, how long it takes, and what they need, so the content that wins the "Do" intent hands over a complete, ordered plan, not a paragraph of encouragement.

## What does the planning question tree look like?

AI engines fan a single task into many sub-questions and assemble the answer from different sources. Cover the whole branch set, each as a self-contained chunk a model can lift:

| Branch | Example question | What to publish |
|---|---|---|
| The plan | "How do I plan a 3-day Kyoto trip?" | An answer-first, numbered plan |
| Order | "What order should I do this in?" | Steps in explicit sequence |
| Timing | "How long does each step take?" | Realistic, ranged durations |
| Prerequisites | "What do I need before I start?" | A what-you-need checklist |
| Logistics | "When and where do I do each part?" | Schedule, location, booking notes |
| Constraints | "What if I only have a weekend / small budget?" | Stated assumptions and variants |

Covering several branches well can get you cited multiple times in one answer. The [query fan-out](/glossary/query-fan-out) multiplier at work (the mechanics are in [how query fan-out works](/blog/how-query-fan-out-works)). The defining feature of planning content is that it must be *actionable*: a model should be able to lift a step, a duration, or a checklist item and drop it straight into the plan it is building for the user.

## How should you structure a planning page?

Apply the extraction rules that get any chunk selected, tuned for tasks:

- **Answer-first, then detail.** Open with the plan in brief. "A 3-day Kyoto trip breaks into arrival, temples, and day-trip", then expand each step. Give the model the shape before the specifics.
- **Real steps as an ordered list.** Sequences belong in numbered steps, not prose, and they map cleanly to [HowTo structured data](/glossary/structured-data).
- **Durations and quantities in tables.** Time, cost, distance, and counts are facts. Put them where a model can lift them, not buried in narrative.
- **State assumptions up front.** "This assumes two days and a mid-range budget." Scope clarity is one of the strongest signals a chunk gets selected.
- **One task per chunk**, so a section answers its question without the rest of the page.

This is the same discipline as [getting cited by AI](/blog/how-to-get-cited-by-ai) and [optimising for AI Overviews](/blog/how-to-optimize-for-ai-overviews); planning content simply leads with order, timing, and checklists.

## Why does specificity win planning queries especially?

Because a plan is only useful if its details are real. Vague planning content ("allow plenty of time", "pack accordingly") gives a model nothing to lift; specific, [corroborated](/glossary/corroboration) detail does. Make the actionable facts concrete and verifiable:

- **Name real durations, distances, and costs**: "the temple circuit takes about 4 hours on foot". Dated where they drift.
- **Give checklists, not adjectives**: an explicit what-to-pack or what-to-prepare list beats "be prepared."
- **Show the source of any hard number** (opening hours, prices, travel times) so it is safe to quote, and keep it current.

Over-claiming or inventing specifics is worse than omitting them: a plan that sends someone wrong is the fastest way to be described as unreliable. The opposite of the goal.

## How do you keep planning content cited over time?

Planning facts drift. Prices, hours, schedules, tooling, and live AI retrieval favours recently-reviewed pages, so put planning pages on a refresh cadence and make updates substantive (corrected times, new steps), never a bumped date. The mechanics are in the [content-freshness citation cliff](/blog/content-freshness-citation-cliff). Evergreen task structures ("how to plan a marathon build-up") decay slowly; time-bound plans ("2026 holiday shopping timeline") decay fast and need attention.

## Where should you start?

A focused first pass:

1. Pick one task your customers genuinely plan around your product or category.
2. Map its planning question tree (the table above) and write a self-contained chunk for each branch. Plan, order, timing, prerequisites, logistics, constraints.
3. Lead each with the answer, put durations and checklists in lists and tables, and add HowTo structured data.
4. State your assumptions and keep the hard numbers current and sourced.
5. Track whether AI engines cite and recommend you for the task. Across engines, over time.

That last step closes the loop. Knowing whether AI Mode and the other engines actually surface, cite, and recommend *your* brand for the tasks your customers plan. Tracked daily rather than spot-checked. Is exactly what **Buffy Intel** measures: presence, citations, and [share of voice](/glossary/share-of-voice) across every major engine.

## How to optimise your products for Google AI Mode shopping
Source: https://heybuffy.com/blog/optimize-for-ai-mode-shopping

Google's own AI Mode data gives D2C brands an unusually direct brief. According to Google's mid-2026 report on how people use [AI Mode](/glossary/google-ai-mode) in the US, shoppers **start on traditional Search, click into AI Mode, and ask follow-up questions**: and the attributes they ask about most are price, availability, colour, size, and material. The playbook below turns that data into the work: expose those exact facts as clean, liftable, [structured](/glossary/structured-data) statements so AI Mode can cite and recommend your products.

## What does Google's data say shoppers ask AI Mode?

Google reports that people often begin a shopping journey on Search and then move into AI Mode to go deeper. The top retail attributes they ask about, in Google's stated order:

| Priority | Attribute | What to expose on the page |
|---|---|---|
| 1 | Price | Current price, currency, any range or variant pricing |
| 2 | Location | In-store/near-me availability, shipping regions |
| 3 | Colour | Named colours per variant, not just swatches |
| 4 | Brand | Consistent brand name and descriptor |
| 5 | Availability | In-stock status, restock, lead time |
| 6 | Size | Size range, fit notes, a real size guide |
| 7 | Material | Fabric/components, care, origin |
| 8 | Style | Occasion, aesthetic, cut |
| 9 | Type | Category and sub-type in plain words |
| 10 | Quality | Durability, warranty, review-backed claims |

The pattern: shoppers ask for **concrete, factual attributes**, not marketing copy. A page that only shows colour as a swatch image or hides material in a spec graphic gives AI Mode nothing to lift. The fix is the same discipline as [writing product pages AI can quote](/blog/write-conversational-product-pages). Turn every attribute into a sentence *and* a structured field.

## The step-by-step playbook

1. **Stay indexable for the opening query.** AI Mode grounds in Google's index, so confirm Googlebot and Google's AI crawlers reach your product and category pages. Check you aren't [blocking them at the CDN](/blog/is-your-cdn-blocking-ai-crawlers). If Search can't retrieve the page, AI Mode can't cite it.
2. **Expose the top-10 attributes as plain sentences.** For each product, state price, availability, colour, size, material, and the rest as self-contained facts in text. "This trail shoe weighs 248g, comes in five colours, and ships free in 2 days", not locked in images.
3. **Mirror them in Product/Offer structured data.** Use `Product` + `Offer` markup so machines read price, availability, and attributes without guessing. See [preparing your catalogue for AI agents](/blog/prepare-product-catalog-for-ai-agents).
4. **Answer the "which one" follow-up.** Google reports "which" decision queries grew 40% faster than AI Mode queries overall. Add comparison and use-case context on the page ("best for wide feet", "vs the trail version") so you win the [fan-out](/glossary/query-fan-out) follow-up, not just the first query.
5. **Make quality verifiable.** Quality is a top-10 attribute, so back it with specifics. Warranty terms, durability tests, genuine review counts, because AI engines pull [verifiable, corroborated](/glossary/corroboration) claims over adjectives.
6. **Keep it fresh.** Price and availability are the top two attributes and they change; stale facts get a brand [described wrongly or dropped](/blog/content-freshness-citation-cliff), so keep the live fields accurate.

> AI Mode shoppers ask for price, availability, size, and material in plain words, so the brands that win the follow-up are the ones that wrote those facts as sentences, not buried them in a spec image.

## Why does this matter more in AI Mode than classic search?

Because AI Mode is conversational, the shopping decision plays out over several turns, each one fanning out again. A classic product listing only has to win the click; an AI Mode product has to **answer the follow-up question on the page**. Google's data shows those follow-ups cluster on a predictable set of attributes, which is good news, because it tells you exactly what to make extractable.

This is the same lesson the corpus reaches across categories: [what makes AI recommend a product](/blog/factors-ai-recommends-products) is reachability, specificity, corroboration, and freshness, not adjectives. For category-specific nuance, see the [fashion and apparel playbook](/blog/ai-visibility-for-fashion-brands) and the [electronics playbook](/blog/ai-visibility-for-electronics-brands), and for how the engines differ, the [ChatGPT vs Google vs Perplexity comparison](/blog/chatgpt-vs-google-vs-perplexity-product-discovery).

## How do you know it's working?

Don't guess. Measure. Take the high-intent shopping questions your customers ask (start from the attributes above), pose them in AI Mode, and track over time whether **your products are named** and **your pages are cited**, by attribute and by category. That cross-engine, multi-prompt read. Presence, citations, and sentiment tracked daily rather than spot-checked. Is exactly what **Buffy Intel** is built for.

## How to win Google AI Mode travel queries: a content playbook
Source: https://heybuffy.com/blog/optimize-for-ai-mode-travel

Travel is one of the top things people do in [Google AI Mode](/glossary/google-ai-mode). In Google's 2026 report *"How people are using AI Mode in the U.S."*, Travel sits among the top 10 topics people search, and "build travel itineraries" is one of the planning-style "Do" behaviours Google says grew about **80% faster than AI Mode queries overall**. Travel is unusual because it spans three intents that suit AI answers well: exploring destinations, deciding between options, and planning the trip. This playbook turns that into a content plan.

It applies the same method as the rest of the corpus and is the travel companion to the [Decide/shopping](/blog/optimize-for-ai-mode-shopping), [Do/planning](/blog/optimize-for-ai-mode-planning), and [Learn](/blog/aeo-for-education-and-learning-content) playbooks. All usage figures are Google's own platform data, dated to mid-2026 and not independently audited, so read the direction (travel is a large, fast-growing use of AI search) as firmer than any single number.

## Why is travel a strong fit for AI Mode?

Because a trip is a multi-part task, and AI Mode is where people now work multi-part tasks through. Google reports the average AI Mode query is about **triple the length** of a classic search and that follow-up queries grew **more than 40% per month**: exactly the shape of someone planning a trip step by step. Travel questions also cross all three of the intents that reward well-structured content:

| Intent | Travel example | What the traveller wants |
|---|---|---|
| Explore | "Where should I go for a warm week in March?" | Destination ideas, shortlists |
| Decide | "Which is better for families, X or Y?" | A fair comparison |
| Do | "Plan a 4-day itinerary for two" | A ready-to-follow plan |

Source: intents and growth from Google, AI Mode U.S. Insights report (mid-2026). A single trip fans out into destination, timing, budget, logistics, and bookings, so one strong travel hub can be cited several times in a single answer. The [query fan-out](/glossary/query-fan-out) multiplier at work.

## What does the travel question tree look like?

AI engines fan one trip into many sub-questions and assemble the answer from different sources. Cover the whole branch set, each as a self-contained chunk a model can lift:

| Branch | Example question | What to publish |
|---|---|---|
| Destination | "Where should I go for X?" | An answer-first shortlist with why-it-fits |
| Timing | "When is the best time to visit?" | Seasons, weather, and cost windows in a table |
| Itinerary | "What's a good 3-day plan?" | A day-by-day plan in numbered steps |
| Budget | "How much should I budget?" | Ranged, dated costs by category |
| Logistics | "How do I get around?" | Transport options, times, and passes |
| Stay | "Where should I stay?" | Areas and trade-offs, not a single pick |
| Constraints | "What if I only have a weekend / travel with kids?" | Stated assumptions and variants |

Covering several branches well is what earns multiple citations in one itinerary answer. The defining feature of travel content is that it must be *actionable and specific*: a model should be able to lift a day plan, a travel time, or a season note and drop it straight into the trip it is building for the user.

## How should you structure a travel page?

Apply the extraction rules that get any chunk selected, tuned for trips:

- **Answer-first, then detail.** Open with the trip in brief: "Three days in Lisbon breaks into old town, river, and a day trip", then expand each. Give the model the shape before the specifics.
- **Itineraries as ordered lists.** Day-by-day plans belong in numbered steps, not prose, and they map cleanly to [HowTo structured data](/glossary/structured-data).
- **Facts in tables.** Seasons, durations, distances, prices, and opening hours are facts. Put them where a model can lift them, not buried in narrative.
- **State assumptions up front.** "This assumes a long weekend, no car, and a mid-range budget." Scope clarity is one of the strongest signals a chunk gets selected.
- **One place or step per chunk**, so a section answers its question without the rest of the page.

This is the same discipline as [getting cited by AI](/blog/how-to-get-cited-by-ai) and [optimising for AI Overviews](/blog/how-to-optimize-for-ai-overviews); travel content simply leads with itineraries, seasons, and logistics.

> A traveller rarely asks one question. They ask where to go, when, for how much, and in what order, so the content that wins travel queries hands over a complete, ordered plan with real numbers, not a paragraph of wanderlust.

## Why does specific, attribute-rich detail win travel queries?

Because AI Mode travellers phrase their needs as [attribute queries](/glossary/attribute-query): "nonstop flights under a set budget", "family-friendly hotel with a pool", "walkable neighbourhood near the old town". A page that only says "great for families" gives a model nothing to match; one that names the concrete attribute does. This is the travel case of the broader shift covered in [why AI Mode users search in attributes](/blog/why-ai-mode-users-search-in-attributes). Make the [corroborated](/glossary/corroboration) facts concrete and verifiable:

- **Name real durations, distances, and costs**: "the airport train takes about 20 minutes and costs roughly the price of a coffee". Dated where they drift.
- **Expose place attributes explicitly**: season, walkability, family-friendliness, accessibility, price band, so a model can match a filtered request.
- **Show the source of any hard number** (prices, opening hours, transit times) so it is safe to quote, and keep it current.

Over-claiming or inventing specifics is worse than omitting them: an itinerary that sends someone to a closed attraction is the fastest way to be described as unreliable. The opposite of the goal.

## How do you keep travel content cited over time?

Travel facts drift fast. Prices, schedules, opening hours, and seasonal advice go stale, and live AI retrieval favours recently-reviewed pages, so put travel pages on a refresh cadence and make updates substantive (corrected times, new routes), never a bumped date. The mechanics are in the [content-freshness citation cliff](/blog/content-freshness-citation-cliff). Evergreen structures ("how to plan a first trip to Japan") decay slowly; time-bound pages ("2026 summer festival dates") decay fast and need attention. Because more than one in six AI Mode searches now use voice or images ([multimodal search](/glossary/multimodal-search), per Google), give photos honest, descriptive alt text so the facts in them are legible too.

## Where should you start?

A focused first pass:

1. Pick one trip your audience genuinely plans around your destination, product, or category.
2. Map its question tree (the table above) and write a self-contained chunk for each branch. Destination, timing, itinerary, budget, logistics, stay, constraints.
3. Lead each with the answer, put durations, seasons, and costs in tables, and add HowTo structured data to itineraries.
4. Expose place attributes explicitly, state your assumptions, and keep the hard numbers current and sourced.
5. Track whether AI engines cite and recommend you for the trip. Across engines, over time.

That last step closes the loop. Knowing whether AI Mode and the other engines actually surface, cite, and recommend *your* brand for the trips your audience plans. Tracked daily rather than spot-checked. Is exactly what **Buffy Intel** measures: presence, [citations](/glossary/citation), and [share of voice](/glossary/share-of-voice) across every major engine. The same behaviour shows up in the topline [AI Mode usage data](/blog/google-ai-mode-usage-data-2026) and in [how AI Mode works](/blog/how-google-ai-mode-works); this playbook makes it actionable for travel.

## How to optimise your homepage for AI referrals
Source: https://heybuffy.com/blog/optimize-your-homepage-for-ai-referrals

After ChatGPT's May 2026 branded-link shift, the homepage became the single page AI answers link to most often, and independent panels measured homepage share of ChatGPT referrals rising to roughly 60%. If your homepage is a slogan over a hero image with the facts locked in JavaScript, you are losing both the citation and the click. This playbook turns the homepage into a page AI can **read, link, and convert from**.

It is the practical companion to the data on [ChatGPT's branded-link shift](/blog/chatgpt-branded-links-referral-shift). The steps below assume a brand that wants AI engines to recognise it and send qualified visitors to the front door.

## Why is the homepage suddenly an AI landing page?

Because the link an AI answer adds when it names your brand is usually your **root URL**, not a deep page. As of mid-2026, after the 7 May branded-link change, Similarweb's panel showed homepage share of ChatGPT referrals moving from about 26-32% to roughly 60%, and Profound reported a similar shift across the sites it monitors (figures attributed to those vendors, single-source, dated).

The consequence is concrete: a curious buyer who asked ChatGPT about your category now arrives on your homepage cold, with no product-page context. The homepage has to do the job a search snippet used to do. Say what you are, and then route the visit onward.

## Step 1: State who you are in one extractable line

Open with a single, plain sentence that names your **category, what you do, and who it's for**: the kind of line a model can lift verbatim into an answer. "Buffy Intel is an AI brand-visibility platform that tracks where your brand appears in AI answers" beats "Reimagine your presence in the age of AI."

Put it in real heading and paragraph text near the top of the page, not inside an image or a video. This is the same [entity clarity](/blog/entity-strength-ai) that helps an engine associate your brand with your category. Say it once, clearly, and consistently with how you describe yourself everywhere else.

## Step 2: Make the homepage reachable and server-rendered

A page an AI can't fetch can't be cited or linked. Two checks:

- **Server-render the above-the-fold facts.** If your name, category line, and key links only appear after client-side JavaScript executes, many AI fetchers will read an empty shell. Expose the core facts in the raw HTML.
- **Don't block the bots.** Confirm your CDN and robots rules allow AI crawlers. A misconfigured edge rule silently drops you from answers. Diagnose it with our guide on whether [your CDN is blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers), and remember [accessibility and AI-parseability](/blog/accessibility-and-ai-parseability) are the same discipline.

## Step 3: Put your differentiators in plain, liftable facts

Replace adjectives with specifics. Engines lift verifiable, named, numeric claims and skip vague ones. On the homepage:

| Weak (skipped) | Strong (liftable) |
|---|---|
| "Fast setup" | "Live in under 5 minutes, no developer" |
| "Trusted by leading brands" | "Tracks visibility across ChatGPT, Gemini, Claude, and Perplexity" |
| "Industry-leading coverage" | "Daily snapshots across 5 major AI engines" |

Each row should be plain text on the page, not baked into a graphic. The point is to give a model a clean, self-contained fact it can quote when it names you.

> Your homepage is now the answer to "who is this brand?". Write it so an AI can lift the answer in one sentence, then click through for the rest.

## Step 4: Add Organization and WebSite schema

Label your entity so machines don't guess. Add `Organization` and `WebSite` [structured data](/glossary/structured-data) with your name, logo, a one-line description, and `sameAs` links to your verified profiles. This won't force a citation, but it reinforces [entity recognition](/glossary/entity-authority) and ties your homepage to the rest of your web presence. Keep the schema's description consistent with your above-the-fold line. Mismatched facts weaken the signal.

## Step 5: Route the referred visitor onward

A homepage that wins the link but dead-ends the visit wastes the referral. Because the visitor arrives without product context, give clear, descriptive internal links to the next step. Product, pricing, and your most useful resources. Using [semantic anchor text](/blog/how-to-get-cited-by-ai) that names the destination ("see pricing," "read the methodology"), never "click here." This both helps the human act and signals topical structure to the model.

## Step 6: Show corroboration and trust

A referred stranger needs a reason to believe you. Surface third-party signals. Named integrations, verifiable credentials, real coverage, that an engine and a human both read as authority. This is the [corroboration](/glossary/corroboration) layer that makes a brand safer to recommend, and it supports the harder goal of being [recommended, not just cited](/blog/cited-vs-recommended-in-ai-search).

## Step 7: Measure homepage AI referrals

You can't improve what you can't see. Build an [AI-referral view in GA4](/blog/ga4-ai-referral-dashboard) and watch the share of AI traffic landing on the homepage, but remember a large slice arrives with no referrer as [Direct](/glossary/dark-traffic), so [unmask it](/blog/why-ai-traffic-shows-up-as-direct) and read homepage Direct spikes alongside your referral data. Track the trend, not a single snapshot.

## A quick homepage checklist

- [ ] One plain sentence states category + what you do + who it's for, above the fold, in real text.
- [ ] Core facts are server-rendered and crawlable; AI bots aren't blocked at the CDN.
- [ ] Differentiators are specific, named, numeric, not adjectives.
- [ ] `Organization` + `WebSite` schema present and consistent with the page.
- [ ] Clear, descriptive links route the visit onward.
- [ ] Corroboration/trust signals are visible.
- [ ] AI referrals to the homepage are tracked over time.

The branded-link shift made the homepage a destination AI hands your buyers. Whether those handoffs are actually reaching you, and whether the answers name your brand in the first place. Is what **Buffy Intel** measures: presence, citations, and AI-referred traffic across every major engine, tracked over time.

## Paid, organic, and cited: the three separate systems behind AI Mode visibility
Source: https://heybuffy.com/blog/paid-organic-cited-ai-mode

**A single Google AI Mode result can carry a text ad, lean on organic rankings, and cite sources, but these are three separate systems, won three different ways, and they barely overlap.** A July 2026 study by the SEO platform SE Ranking (50,032 commercial keywords, US AI Mode, data collected 30 June 2026) found that for the keywords a brand advertised on, only about **11.5% of advertiser domains were cited** and about **85% did not rank organically** at all. Winning the ad auction, ranking in classic search, and being cited in the answer are distinct outcomes. This comparison lays out each channel neutrally: what it is, how you win it, and what it does and does not buy.

We treat the three as parallel channels rather than a funnel, because the data shows spending or ranking in one does not carry into the others. Figures below are single-vendor and reflect one mid-2026 snapshot; read them as directional.

## The three systems at a glance

| Channel | Who decides placement | How you win it | What it buys | What it does NOT buy |
|---|---|---|---|---|
| **Paid ad** | Ad auction (bid + ad quality) | Bid on commercial keywords | A labelled text slot in the result | A citation, or an organic ranking |
| **Organic ranking** | Classic search algorithm | SEO: relevance, links, technical health | A blue-link position; strong input to AI Overviews | A guaranteed AI Mode citation |
| **AI citation** | Retrieval + synthesis (fan-out) | Extractable, corroborated content; entity strength | Being named/linked inside the synthesised answer | A ranking or an ad slot |

The one-line summary: **each channel is won by a different mechanism, so each needs its own strategy and its own measurement.**

## What is the paid channel, and what does it actually buy?

The paid channel is Google's text [ads inside AI Mode](/glossary/ai-mode-ads), allocated by auction. In SE Ranking's commercial-keyword sample, **29.45%** of queries showed a text ad and **71.1%** of those placements showed two competing ads side by side, with ad presence rising from about 24% on sub-\$2 keywords to about 54% on keywords over \$10. So on expensive, high-intent commercial terms, ads are common and competitive.

What the paid channel buys is a visible, labelled slot and the click it can earn. What it does **not** buy is a citation: advertiser domains were cited only ~11.5% of the time (exact URLs 1.95%), and once brand strength and organic standing were controlled for, advertisers were cited no more than non-advertisers. Ads are a demand-capture tool, not an AI-visibility tool. (The full study is in [do Google AI Mode ads get you cited?](/blog/do-ai-mode-ads-get-you-cited).)

## What is the organic channel, and does it carry into AI Mode?

The organic channel is your classic search ranking, earned through SEO. It still matters, but it carries into AI Mode **weakly**. Earlier 2026 analyses found only about 19% of AI Mode citations came from the organic top-20, versus roughly 56% for AI Overviews, because AI Mode's [query fan-out](/glossary/query-fan-out) reaches well beyond the top-10 blue links (see [do AI Mode and AI Overviews cite the same sources?](/blog/ai-mode-vs-ai-overviews-citations)).

So organic work is not wasted: it wins classic clicks, feeds [AI Overviews](/glossary/ai-overviews) substantially, and a top ranking is a modest citation advantage in AI Mode. But it is neither necessary nor sufficient for an AI Mode citation. You can be cited without ranking on page one, and rank without being cited, a decoupling covered in [does Google rank get you cited by AI?](/blog/does-google-rank-get-you-cited-by-ai).

## What is the cited channel, and why is it the durable one?

The cited channel is being named or linked as a **source inside the synthesised answer**, the outcome that survives the shift to zero-click AI search. It is decided by retrieval and synthesis: AI Mode fans one question into sub-queries and lifts the passages that answer each branch cleanly. That rewards content that is reachable, answer-first, factual in text and [structured data](/glossary/structured-data) rather than images, [corroborated](/glossary/corroboration) by third parties, and backed by a strong brand [entity](/glossary/entity-authority).

> The ad you buy and the ranking you earn are inputs to other systems. The citation is the one that puts your brand inside the answer the user actually reads, and it can't be bought, only earned.

Because a strong entity is recognised across engines, the cited channel is also the most portable: the exact page an engine quotes is volatile, but a well-established brand keeps getting recommended across surfaces (see [brand-mention gap vs source gap](/blog/brand-mention-gap-vs-source-gap)). That durability is why we treat citations as the core AI-visibility asset. The method for earning them is in [how to get cited in Google AI Mode](/blog/how-to-get-cited-in-google-ai-mode).

## How should you budget and measure across the three?

Treat them as three lines, not one. A practical split:

- **Paid** — fund it for high-intent commercial capture, especially on costly keywords where ads dominate. Judge it on clicks and conversions, not on AI visibility.
- **Organic** — keep investing; it wins classic search and feeds AI Overviews, and it's a mild positive for AI Mode citation. Judge it on rankings and organic traffic.
- **Cited** — invest in extractable content, corroboration, and entity strength. Judge it on citation share across engines, tracked over time.

The failure mode is assuming one metric covers all three, seeing ad impressions or rankings climb and believing your AI visibility is healthy when the answer never names you. Measuring the cited line on its own, snapshot over snapshot and across every engine, is exactly what **Buffy Intel** does. It shows whether AI engines actually cite and recommend your brand, separate from whatever your ads and rankings are doing, so you can budget each channel on its own evidence.

## Phantom citations: what a 48,000-paper audit of hallucinated references means for AI-written content
Source: https://heybuffy.com/blog/phantom-citations-hallucinated-references

A July 2026 Microsoft preprint audited **48,095 accepted papers** from four of computing's most selective venues and found that **hallucinated citations have entered the permanent scholarly record**: references that look valid on the page, passed peer review, and yet point to no real work or to the wrong authors. At the reference level the failure rate is under 1%; at the paper level it reaches **roughly one in four accepted NeurIPS 2025 papers**. The gap between those two numbers is the whole story.

The paper is *"Phantom References: Hallucinated Citations That Survive Peer Review at Top-Tier Conferences"* by Mark Russinovich, Ram Shankar Siva Kumar and Ahmed Salem of Microsoft ([arXiv:2607.00738](https://arxiv.org/abs/2607.00738), posted 1 July 2026). It is a preprint, not itself peer-reviewed yet, and its authors are careful to frame their counts as a conservative lower bound. We treat every figure below as single-study, self-reported and directional, and we read it for the durable lesson it carries for anyone publishing content that AI systems will judge.

That lesson is not really about academia. It is about what happens to trust when [AI hallucination](/glossary/ai-hallucination) leaks out of a chatbot session and into the record, and it maps directly onto how AI search engines decide whom to cite.

## What did the Microsoft study actually measure?

It measured **citation identity, not truth.** The authors built an open-source pipeline called RefChecker that treats each bibliography entry as a checkable claim: does this reference resolve to a real work by the named authors? A citation is counted as *likely hallucinated* only when it fails at the level of identity. One of two ways:

- **Fabrication**: no indexed work matches the cited title, and the listed authors never produced anything matching it. The reference points to nothing.
- **Author-identity corruption**: a real paper with that title exists, but it's credited to a substantially different set of authors.

Crucially, the study **excludes ordinary bibliographic drift**: a wrong year, a venue change, a preprint that later became a proceedings paper, minor name variants. Those are logged but never counted. As the authors put it, the numbers "understate any broader notion of citation noise and are best read as a lower bound."

The scope matters, and the paper is honest about it: this checks whether a cited work *exists and is correctly attributed*, not whether the citing sentence is faithfully supported, nor whether the paper's science is correct. Citation-layer verification is **necessary but not sufficient** for integrity.

## How does the verification pipeline work?

By trying to corroborate every reference against multiple independent authorities, then escalating only the suspicious ones. This mechanism is the part worth studying closely, because it is a clean model of how machine trust is actually established.

RefChecker resolves each normalized reference against **Semantic Scholar, OpenAlex, CrossRef, DBLP and the ACL Anthology**, using DOIs, arXiv IDs and cited URLs where present. A reference is escalated when it can't be verified, when author overlap falls below a 60% threshold (for references with three or more authors), or when a DOI, arXiv ID or URL resolves to a different work. Escalated cases go to an LLM with web-search capability, which must find a *dedicated source page* for the cited work, not merely another paper that repeats the same citation. Before the metadata is re-checked. Only references that stay unsupported, or whose best match conflicts substantially on authorship, are counted.

Two design choices stand out. First, **no single source is treated as ground truth**: when the authorities disagree, the pipeline preserves the evidence rather than trusting one. Second, the LLM is used as an escalation-and-evidence step, never as the sole labeler; the final call rests on external database matches. In the study's configuration, the extraction model was Gemini 3.1 Flash Lite and the deep-search model was Claude Haiku 4.5. The whole scan of one venue's 3,703 papers and 221,281 references cost about **$157. Roughly four cents per paper.**

That "corroborate against many independent sources, distrust what you can't verify" logic is the same principle behind [why AI search resists manipulation](/blog/can-ai-search-be-manipulated) and why [self-serving content gets discounted](/blog/does-ai-generated-content-hurt-ai-visibility). It's [corroboration](/glossary/corroboration) as a trust filter, applied to a bibliography.

## Why does the failure look tiny and huge at the same time?

Because the answer changes with the denominator. This is the central finding, and it's easy to misread in either direction.

| Venue (2025) | Hallucinated refs, all references | Papers with ≥1 hallucinated ref | Papers with ≥2 (academic refs only) |
|---|---|---|---|
| ICLR | 0.38% | 18.7% | 1.9% |
| ICML | 0.54% | 23.3% | 3.4% |
| NeurIPS | 0.68% | 26.2% | 5.1% |
| USENIX Security | 0.81% | 34.9% | 4.8% |

*Source: Russinovich, Siva Kumar & Salem, arXiv:2607.00738 (2026); 2025 venue-years, self-reported.*

A sub-1% reference rate sounds negligible for a single bibliography. But a conference is not a single bibliography. ICLR 2025 alone held **221,281 extracted references across 3,703 papers**: so even 0.38% works out to **835 flagged references in 692 distinct papers.** Raising the bar to two flagged references in the same paper (a far more conservative signal, since one stray false positive no longer tips a paper) still leaves **roughly one in twenty accepted NeurIPS and USENIX Security 2025 papers** carrying at least two.

> "A conference is not one reference. It is hundreds of thousands. At that scale, the same rate yields an unverifiable citation in roughly a quarter of accepted NeurIPS 2025 papers.". *Phantom References*, arXiv:2607.00738

The authors also report a post-ChatGPT rise. The share of papers with two or more hallucinated references sits about **1.9× higher than the pre-2023 baseline**: and a high-count tail: single papers with 20 (NeurIPS), 13 (ICML and USENIX Security) and 8 (ICLR) likely hallucinated references. They are deliberately cautious about causation: the timing "is consistent with a change in authoring practice" but is not offered as proof that LLM-assisted writing caused the increase.

## Why didn't peer review catch them?

Because reviewers don't verify bibliographies, and the data shows it plainly. This is the finding with the sharpest implications beyond academia.

When the authors joined each paper's hallucination count to its review scores, the difference between clean papers and affected ones was **essentially zero**: a mean-rating gap of +0.02 at ICLR, +0.005 at ICML and +0.04 at NeurIPS, with affected papers rated, if anything, marginally *higher*. Slicing by acceptance tier told the same story (posters 20.4%, spotlights 23.5%, orals 20.3% affected). Most tellingly, on ICLR 2023 the accepted papers (mean reviewer rating 6.61) were affected 16.0% of the time and the rejected papers (rating 4.67, nearly two points lower) 16.9% of the time. **Almost identical**, despite a large gap in perceived quality.

The conclusion the authors draw is narrow and important: bibliographic integrity is **orthogonal to the quality signal reviewers extract.** Whatever peer review is good at, "does this citation resolve to a real work" is not one of those things. Independent audits agree. GPTZero reported finding at least one human-verified hallucinated citation in **50 of 300 scanned ICLR 2026 submissions**, each of which had already received three to five expert reviews, and the GhostCite analysis of 2.2M citations found **76.7% of surveyed reviewers admit they don't check references.** Convergent measurements from independent teams are what make the phenomenon credible.

## Is this just an academic problem?

No. It's a preview of the trust economy every publisher now operates in. Strip away the conference setting and the study describes a general failure mode: **AI tools make it trivial to produce polished, confident, well-formed references (and claims) that don't survive verification**: and the humans downstream rarely check. Substitute "buyer reading an AI answer" for "peer reviewer" and the risk is the same shape.

Author feedback in the study reinforces the point: the papers with the most failures weren't fraud, they were **workflow breakdowns**: bibliography entries generated or reformatted by LLM-based tools and then never verified, sometimes introduced at the camera-ready stage. Nobody in the pipeline owned the check. That is precisely the trap for a marketing or content team using AI to draft at scale.

Two durable lessons for AI visibility follow directly:

- **Verify AI-assisted content before you publish.** A fabricated statistic, a misattributed quote, or a link that resolves to the wrong thing is the content-marketing version of a phantom citation. It's cheap to make and expensive to trust. This is the concrete version of our standing rule that [mass-produced AI content can hurt you](/blog/does-ai-generated-content-hurt-ai-visibility). The risk isn't the tool, it's the unverified output. The industry now has a name for the low-effort end of this: ICML's 2026 review policy explicitly treats *"AI slop"* as interference.
- **Be the entity that survives the check.** The references that passed weren't the ones with the best prose. They were the ones that resolved cleanly against multiple independent authorities. For a brand, that means being findable, consistent and corroborated across sources you don't control, so that when an engine tries to verify a claim about you, it succeeds. That's the slow, durable work behind [entity strength](/blog/entity-strength-ai) and [why AI cites one brand over another](/blog/why-ai-cites-one-brand).

## How should you read a single-study result like this?

Carefully, and with its own caveats foregrounded. The same discipline we ask of [any AI-visibility case study](/blog/how-to-read-an-ai-visibility-case-study). The authors are unusually candid about the limits, and honesty about them is what makes the work trustworthy:

- **False positives are the primary limitation.** Most raw flags, on manual inspection, were *not* hallucinations. Mangled author strings, truncated titles, references corrupted during PDF extraction. A single automated flag "should never be treated as conclusive without review." The higher-threshold signals (two-or-more, and the five-plus tail) are the reliable ones.
- **"Does not exist" and "not yet indexed" are indistinguishable to a scanner.** Genuinely unpublished or very recently accepted work can be flagged even though it's real. A structural reason to keep humans in the loop.
- **It's a preprint, LLM-dependent, and single-team.** Results depend on the configured models and can shift as those models change; the paper is version 1, not yet through peer review itself.

None of that undoes the headline, because the headline rests on the *conservative* end of the measurement and is corroborated by independent audits. But it models the right posture: specific, dated, hedged, and cross-checked. That posture is the actual product here, for researchers and for brands alike.

The through-line is simple. Machine trust is earned by corroboration and lost by unverifiable claims, whether the claim is a citation in a NeurIPS paper or a statistic on your pricing page. Watching whether AI engines actually cite you, and whether the facts they repeat about you are the true ones. Is what **Buffy Intel** measures. Questions: support@flash.tech.

## How to prepare your product catalog for AI agents
Source: https://heybuffy.com/blog/prepare-product-catalog-for-ai-agents

For twenty years, merchants learned to write product data for machines that rewarded brevity. Google Shopping wanted short titles, tight attribute sets, and clean taxonomies, so catalogs were compressed into the minimum viable feed. AI agents flip the requirement: they read like attentive humans, they answer conversational questions, and they can only sell what your catalog actually *says*. The new playbook is enrichment, not compression.

This extends our [agentic-commerce readiness check](/blog/agentic-commerce-readiness), that piece asks whether an agent can find, understand, and buy from your catalog. This one is about the middle step: making the catalog *worth* understanding.

## Why is the old feed playbook failing?

Because the queries changed. Google shared at its 2026 I/O and Marketing Live events that the average AI Mode query is roughly **three times the length** of a traditional search, that **more than one in six** U.S. AI Mode searches now arrive as voice or image, and that planning- and decision-style queries are growing meaningfully faster than AI Mode usage overall. Shoppers aren't typing "running shoes men" anymore. They're asking "which running shoes work for a heavy runner with flat feet who mostly does treadmill?"

A terse feed can't answer that question. The agent fielding it goes looking for pairing advice, fit context, use cases, and trade-offs, and it pulls those from whoever provides them. If your catalog only carries a title, a price, and six attributes, the agent either skips you or describes you using someone else's words.

> The feed era rewarded merchants for saying as little as possible. The agent era rewards them for saying everything. In a structure machines can read.

## What should an enriched catalog contain?

Think of it as four layers, each one machine-readable text on (or linked from) the product page and feed. Agentic-commerce analysts. Notably Scot Wingo, whose Retailgentic newsletter calls the catalog the "gold dust" of agentic commerce. Have converged on the same direction: expand every layer of product context.

| Layer | What it includes | What it wins |
|---|---|---|
| Identity & specs | Complete attributes: materials, dimensions, sizes, identifiers, category, price, availability | Being *eligible* for the answer at all |
| Conversational context | Pairings ("works with…"), occasions, who-it's-for, how-to-use, care instructions | The long, specific queries agents actually field |
| Social proof as data | Review themes and counts exposed as crawlable text, not a widget | Trust signals the agent can quote |
| Objection handling | Product-level FAQs: sizing, compatibility, returns, "is this right for X?" | The follow-up questions that close or kill the sale |

The classic mistakes still apply at every layer: content locked in images, tabs that only render on click, or JavaScript an agent won't execute is invisible. Everything above should exist in server-rendered HTML with [structured data](/glossary/structured-data) labelling what it is.

## Where are the protocols heading?

The commerce protocols are standardizing exactly this enrichment. As of mid-2026, Google's Universal Commerce Protocol (UCP) defines expansion attributes for conversational commerce. Pairings, occasion suitability, links to documentation, and the [Agentic Commerce Protocol (ACP)](/blog/agentic-commerce-protocol-acp) from OpenAI and Stripe asks merchants for a rich product feed in its own shape. The details and names will keep moving; the direction won't. Every protocol is a consumer of the same underlying asset: a verbose, structured, truthful catalog.

That's the practical reassurance. You don't have to bet on a winner. Enrichment work done once feeds whichever surfaces matter: [AI Mode](/blog/how-google-ai-mode-works), ChatGPT, agent checkouts, and ordinary AI answers alike.

## Where does the enrichment content come from?

From context you already have, not from a model's imagination:

1. **Your search logs**: the exact phrases shoppers use, including the zero-result queries your catalog vocabulary doesn't cover.
2. **Cart and PDP behaviour**: what gets abandoned and what shoppers compare, which signals missing information (size doubts, compatibility questions).
3. **Review themes**: what buyers praise, complain about, and ask; the raw material for honest conversational attributes and FAQs.
4. **Support tickets and store-staff questions**: the objection list, pre-written.

One warning: don't point a general-purpose LLM at a product list and let it invent the enrichment. A model's generic priors about your product. Often absorbed from forums and video transcripts. Will write confident, wrong context into your catalog, and you'll spend the next year correcting the record. Generate *from your own data* (reviews, logs, spec sheets), and review before it ships. The goal is a catalog that's verbose **and** true.

## What to do next

Pick your ten most important products and read each PDP as an agent would: can it answer a long, conversational, "is this right for me?" question from the text alone? Fill the four layers where it can't, expose them in structured form, and then watch what the engines do with it, which answers you appear in, how you're described, and whether your own pages become the cited source. That feedback loop, across every engine, is exactly what **Buffy Intel** is built to report.

## How to prioritise your structured data using real adoption data
Source: https://heybuffy.com/blog/prioritize-your-structured-data

Schema.org's June 2026 [usage-statistics dataset](/blog/schema-usage-statistics-dataset) tells you how many sites actually use each schema type, which turns "what structured data should we add?" from an opinion into a prioritisation you can defend with data. This is a step-by-step method for auditing your own pages against real adoption: fix the near-universal basics first, add the high-value types for your content next, ignore the exotic long tail, and measure whether the markup moves your citations.

It assumes you already accept that [structured data](/glossary/structured-data) helps AI parse and cite your facts; the question here is *which types, in what order*. The companion reference explains the dataset itself; this is the playbook.

## Step 1: Cover the near-universal basics first

Start with the types the whole web uses, because a page missing them is below baseline for machine-legibility. Schema.org's May 2026 data puts these in the top adoption bucket (roughly **10M+ domains**):

| Priority | Type | What it declares |
|---|---|---|
| 1 | **WebPage** | What this page is |
| 2 | **WebSite** | The site as an entity (enables sitelinks/search box) |
| 3 | **Organization** | Who publishes it. Your brand identity |
| 4 | **BreadcrumbList** | Where the page sits in your hierarchy |

These four give an engine the *who* and *where* it needs to attribute you. If your CMS does not emit them, that is the first fix. It is the [entity-clarity](/blog/entity-strength-ai) foundation every other signal builds on, and part of making your site [agent-readable](/blog/make-your-website-agent-readable).

## Step 2: Add the high-value types for your content

Next, add the types that make *your specific facts* extractable, but only where the content genuinely exists. The high-leverage types for AI visibility, matched to page type:

- **Product / Offer**: on product pages, so an engine can lift your price, availability, and attributes cleanly. This is what wins commerce answers; see [writing conversational product pages](/blog/write-conversational-product-pages) and [preparing your catalogue for AI agents](/blog/prepare-product-catalog-for-ai-agents).
- **FAQPage**: on genuine Q&A sections, giving engines pre-formatted question-answer pairs to quote directly.
- **Article / BlogPosting**: on editorial content, with author and date, feeding freshness and authorship signals.
- **DefinedTerm**: on glossary and definition pages, labelling each term as a defined concept.

The rule for this step is **match schema to real content**. Adoption data shows these types are widely supported and safe to implement; it does not license marking up content you do not have. Fake FAQs or unearned reviews get ignored at best and penalised at worst.

## Step 3: Ignore the exotic long tail

Resist the temptation to add rare types for their own sake. The dataset's **under-1K-domain** bucket is full of specialised action types (`AllocateAction`, `AgreeAction` and the like) that almost no site uses. Usually for good reason.

> A schema type is worth adding when it describes content you actually have and helps a machine lift a fact. Never because it is rare and you hope it is a secret edge. Rare usually means niche, not advantageous.

The exception is the genuinely niche type that is *exactly right* for your vertical (medical, legal, government). Those sit in low buckets because their audience is small, not because they are low-quality, so a specialised type that precisely fits your content is worth it even at low adoption. The test is always fit-to-content, not popularity.

## Step 4: Validate and keep the markup crawlable

Structured data only counts if a machine can read it. After implementing:

- **Validate** every type with a schema/rich-results validator so malformed markup does not silently fail.
- **Server-render the JSON-LD**: if the schema only appears after JavaScript executes, some crawlers miss it, as covered in [do AI assistants render JavaScript](/blog/do-ai-assistants-render-javascript).
- **Confirm crawlers are not blocked** at the CDN or robots layer, or none of this is visible. See [is your CDN blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers).
- **Keep markup in sync with content**: schema that contradicts the visible page is worse than none.

Machine-legibility is the same discipline as [accessibility](/blog/accessibility-and-ai-parseability): clean, semantic, parseable structure serves both.

## Step 5: Measure whether it actually moved citations

Structured data is an input, not a guarantee, so treat this as an experiment with a before and after. Note your baseline AI citations and AI-referred traffic for the relevant queries, ship the markup, then watch the **trend over several weeks**: not overnight. Because AI answers are volatile and crawl-to-cite lag is real, read a smoothed line rather than a single reading, the same discipline as [getting cited by AI](/blog/how-to-get-cited-by-ai) generally. If citations for the target queries rise after the markup lands and stays crawlable, the schema is earning its place.

Then keep it current: the dataset refreshes monthly and best-practice types drift, so revisit your priorities on a [refresh cadence](/blog/content-freshness-citation-cliff) instead of treating structured data as a one-time project. Watching whether the markup you add actually changes how the engines surface, cite, and recommend your brand. Across every engine, over time. Is exactly what **Buffy Intel** is built to measure.

## How to protect your brand from AI answer poisoning
Source: https://heybuffy.com/blog/protect-your-brand-from-ai-answer-poisoning

**Answer poisoning is when someone seeds false or manipulated content into the sources an AI engine retrieves, so the model repeats it about your brand — and because engines corroborate rather than verify, a denial on your own site often isn't enough to undo it.** The defence is not one page; it is a loop: monitor your answers across engines, strengthen the canonical facts on your own domain, out-corroborate the false narrative with independent sources, and correct it at its origin. This is the defensive counterpart to earning visibility — protecting the answer you already have.

**Last reviewed: 19 August 2026.** This playbook assumes an established brand with existing AI presence. If no engine yet mentions you, your problem is a [brand-mention gap](/blog/brand-mention-gap-vs-source-gap), not poisoning — start there. The specific incident figures below are single-source and directional; the method does not depend on them.

## Why can't you just deny it on your own website?

Because an AI answer about an established brand is built mostly from what *other* people publish, not from your own pages. Reported 2026 comparisons found the large majority of an established brand's new AI mentions traced to third-party content — reviews, comparisons, forum threads — rather than the brand's own promotional pages (single-source, directional). So when a false claim is corroborated across several outside sources, your single denial is one voice against a chorus.

The mechanism is the [spam-detection gap](/blog/do-ai-engines-filter-out-spam): engines weight agreement across sources far more than they verify any individual claim. Some 2026 experiments seeded fabricated details about a fictional brand and watched models adopt them *despite* an official FAQ stating otherwise. The lesson is uncomfortable but clear: you defend an AI answer at the level of the whole corpus, not one page.

> A single denial on your own site is one voice against a chorus — you correct a poisoned AI answer by out-corroborating it, not by out-shouting it. This is different from [astroturfing](/glossary/astroturfing) (faking grassroots praise for yourself) and from [prompt injection](/glossary/prompt-injection) (smuggling instructions into a model) — poisoning corrupts the *retrieved sources* so the honest engine repeats a lie.

## Step 1: Monitor your brand's answers across engines

You cannot fix what you never see, so start with detection. Ask the questions your customers ask — "is [brand] legit?", "[brand] vs [competitor]", "does [brand] do X?" — across ChatGPT, Gemini, Claude, Perplexity and Google's AI answers, on a repeating schedule rather than once.

Watch for three tells:

- **A claim that is simply false or outdated** about your product, pricing, safety, or ownership.
- **A claim traceable to a single low-quality source** — the hallmark of a seeded narrative that hasn't yet been corroborated.
- **A divergence between engines** — a falsehood present in one engine and absent in others is often early, and easiest to stop before it spreads.

Log what each engine says and which sources it cites, so you can tell a genuine poisoning attempt from an ordinary [hallucinated citation](/glossary/citation-hallucination) or a stale fact.

## Step 2: Establish the canonical fact on your own domain

Your first-party page won't win by itself, but the engine still needs a clean, authoritative version to find — so make it unmissable. For each contested fact, publish a specific, dated, self-contained statement in extractable form:

1. **Answer the exact question** a poisoned answer gets wrong, in the first 40–60 words of a section, with a question-style heading.
2. **Be specific and dated** — "As of August 2026, [brand] does not do X" beats a vague reassurance, because named, dated facts are harder to overwrite.
3. **Use [structured data](/glossary/structured-data)** so the fact is machine-labelled, not left for the engine to infer.

Think of this as giving the engine the true canonical source it will reach for once corroboration catches up — necessary, not sufficient.

## Step 3: Out-corroborate the false narrative

This is the step that actually moves the answer, because it fights corroboration with corroboration. A lie repeated across five independent-looking sources beats one truthful page; the fix is to make the truth the better-corroborated story:

- **Earn independent third-party coverage** that states the correct fact — the [earned media](/glossary/earned-media) that engines trust more than owned pages.
- **Ensure high-authority references agree** — a Wikipedia entry, an industry directory, reputable reviews, and community discussion all stating the same accurate detail.
- **Seed nothing fake in return.** Fighting poisoning with your own manufactured consensus is both spam (now [named in Google's policy](/blog/google-spam-policy-ai-answers)) and self-defeating — it dilutes the very [corroboration](/glossary/corroboration) you're trying to build. Win with real, verifiable sources.

The goal is that the next time an engine gathers passages about the contested fact, the weight of credible agreement lands on the truth.

## Step 4: Correct or remove the poison at its source

Corroboration shifts the balance; removing the false source lowers the other side of the scale. Where the poisoning traces to specific content:

| Source of the false claim | Action |
|---|---|
| A page you can edit or influence | Get it corrected or updated directly |
| A third-party site or publisher | Request a correction with evidence; escalate to the platform's process if needed |
| A forum or community post | Reply with the correct, sourced fact; report clear disinformation or manipulation |
| A fabricated or impersonating site | Use the platform's abuse/trademark reporting; document it |

Removing or correcting the origin matters because engines re-crawl: cut off the seeded source and, as the [cited pool churns](/glossary/citation-turnover), the false claim loses the corroboration that kept it alive.

## Step 5: Keep watching — poisoning is a standing threat, not a one-time event

Treat this as a loop, not a project. After you have corrected the record, keep the cross-engine monitoring going and re-check the contested questions on a cadence, because a determined actor can re-seed and because AI answers drift on their own. Set a threshold — for example, the same false claim appearing in two engines — that triggers the playbook again from Step 3.

The durable position is the same one that earns citations in the first place: a reachable, specific, well-corroborated entity. A brand that is consistently and accurately described across the credible web is not just more visible in AI answers — it is far harder to poison, because the truth is already the best-corroborated story an engine can find.

---

Buffy Intel tracks how AI engines describe and cite your brand across every major engine, over time — so a seeded falsehood, a single bad source, or a slipping fact surfaces early enough to correct. To turn cross-engine monitoring into your answer-poisoning smoke detector, [start with Buffy Intel](https://heybuffy.com) or reach us at support@flash.tech.

## How to protect your site from agent hijacking (on-page prompt injection)
Source: https://heybuffy.com/blog/protect-your-site-from-agent-hijacking

You cannot patch an agentic browser, but you can keep your own pages from carrying the instructions that hijack a visitor's agent. The threat is on-page [prompt injection](/glossary/prompt-injection): an [agentic browser](/glossary/agentic-browser) reads your live page while acting for a user, and hidden instructions in your reviews, comments, ads, or embeds can be treated as if the user typed them. A 2026 University of Washington study found several agentic browsers where this can be pushed far enough to cross the [same-origin policy](/glossary/same-origin-policy). This playbook is the brand-side response: five steps to make your own pages a clean surface for the agents that visit them.

**Last reviewed: 27 August 2026.** This is a defensive how-to, not a threat report. It pairs with the data piece on [what the same-origin-policy finding means for brands](/blog/are-agentic-browsers-safe-for-your-site). The specifics below are conservative hygiene that helps regardless of which browser a visitor uses; treat the underlying research as single-study and directional.

## Why can my own page hijack a visitor's agent?

Because the agent reads everything on the page as potential input, and not all of that content is written by you. Any surface where third parties can put text — a review, a comment, an embedded widget, an ad frame, or invisible text an attacker slipped in — is a place an instruction can hide. The agent, working for your visitor, may act on it. So the goal is not to remove content; it is to make sure the content the agent reads cannot issue commands.

## Step 1: Audit your user-generated content

Start where strangers can already write on your page. Reviews, comments, ratings, community Q&A, and forum threads are the most common injection surface because they are, by design, third-party text you publish.

- Inventory every place a non-employee can submit text that renders on a page an agent might read.
- Strip or neutralise instruction-like patterns in submitted content (imperative phrasing aimed at a tool, embedded code, invisible characters).
- Render user content as inert text, never as anything an agent could mistake for a page instruction or a control.

## Step 2: Vet third-party embeds, ads, and scripts

Move next to the code you did not write but do publish. Ad frames, chat widgets, review platforms, and tag-manager scripts all inject content you do not fully control, and any of them can become a carrier.

- List every third-party embed and script on your key commercial pages.
- Drop anything you cannot justify; each one is a surface you are trusting on your visitor's behalf.
- Prefer vendors that sanitise their own output, and keep ad and widget content isolated from the parts of the page an agent needs to act on (prices, buttons, checkout).

## Step 3: Catch hidden and injected text

Then look for text a human never sees but an agent still reads. Attackers favour invisible instructions — white-on-white text, zero-size fonts, off-screen elements, `aria-hidden` traps — precisely because they slip past a person and reach the machine.

- Scan pages for content that is present in the markup but visually hidden, and confirm each instance is legitimate.
- Watch for text injected through comment fields, URL parameters, or profile fields that echo onto the page.
- Make "what does an agent read here that a human does not?" a standing check on templates that accept outside input.

> A person skims your page; an agent reads all of it. The safe assumption is that anything in your markup can become an instruction — so publish nothing you have not vetted as inert.

## Step 4: Sanitise every input that echoes onto a page

Apply the classic web-security discipline, now with a new reason. Any value from a URL, form, search box, or profile that gets reflected back into a page is a reflection point — the same weakness behind older injection bugs, with an agent as the new target.

- Escape and validate reflected inputs so submitted text cannot become active content.
- Give user-supplied text a clear, consistent boundary in the page so it reads as data, not direction.
- Keep the parts of the page an agent must trust — [structured data](/glossary/structured-data), prices, calls to action — populated only from your own systems.

## Step 5: Monitor your pages and your brand across agents

Finally, keep watching, because the surface moves. Content changes, vendors update, and new agentic browsers arrive; a page that was clean last quarter may not be now.

- Re-audit high-traffic commercial and checkout pages on a schedule, not once.
- Track how your brand is surfaced and acted on across agents over time, so a change shows up as a signal rather than an incident.
- Keep this distinct from [answer poisoning](/blog/protect-your-brand-from-ai-answer-poisoning) defence: that protects what engines *say* about you in their answers; this protects what a visitor's agent *does* on your page. Both are first-party-surface control; the fixes differ.

The honest read: you cannot make an agentic browser secure, but you can make your own pages a poor place to hide an instruction — which protects the people those agents work for and the trust your brand depends on. Keeping an eye on how your brand is discovered and acted on across AI surfaces, over time, is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## How to prove AI traffic actually converts (a measurement method)
Source: https://heybuffy.com/blog/prove-ai-traffic-converts

Once you can see AI-referred visits in analytics, the next question is the one finance asks: do they convert? You prove it by **isolating AI sessions, tying them to outcomes on both a last-click and an assisted basis, estimating the dark-traffic you can't see, and validating the relationship with a holdout or correlation test**: then reporting a conservative floor, not a hero number. The credibility of an AI-revenue claim comes from how honestly you handle what you *can't* measure.

This is the measurement companion to the [AI-referral dashboard build](/blog/ga4-ai-referral-dashboard): that piece gets the traffic into view, this one turns it into a defensible conversion story. It extends the [from clicks to citations](/blog/from-clicks-to-citations) scoreboard down into revenue.

## Why is AI traffic hard to tie to revenue?

Because the channel undercounts and the influence is often invisible. Two distinct problems sit between an AI answer and a row in your revenue report:

- **The dark-traffic undercount.** Many AI-driven visits arrive with no referrer. In-app clicks, redirects, and stripped headers, so they land in [Direct](/blog/why-ai-traffic-shows-up-as-direct) and a referrer-based count treats them as something else. Your visible AI channel is a floor, not the total.
- **The zero-click influence.** Much of AI's effect never produces an AI-referred click at all. The assistant shapes the shortlist inside a [zero-click](/glossary/zero-click-search) answer, and the purchase shows up later as branded search or direct. Last-click attribution credits the wrong channel.

Both problems push the same way: naive attribution *understates* AI's contribution. That's useful to know, because it means a conservative method is also a defensible one.

## What should I measure to prove conversion?

Four questions, each with its own metric and its own caveat. Treat them as a checklist rather than a single number:

| Question | Metric | Where it comes from | Caveat |
|---|---|---|---|
| Do AI sessions convert at all? | Conversion rate, revenue per visit | AI channel in [GA4](/blog/ga4-ai-referral-dashboard) | Visible referrals only. A floor |
| Are they worth more than other traffic? | RPV / conversion-rate index vs site average | Same, compared to baseline | Self-selection: high-intent buyers |
| Does AI assist conversions it doesn't close? | Assisted / multi-touch conversions | Multi-touch or path report | Models differ; pick one and disclose it |
| Is AI visibility moving outcomes overall? | Correlation of citations vs branded/direct, with lag | Visibility tool + analytics | Correlation is not cause |

The point of the table is that no single row proves the case. A high conversion rate on a tiny visible channel is easy to dismiss; pairing it with an assisted-conversion view and a correlation signal is what makes the argument hold.

## How do I separate AI-referred from AI-influenced?

Count them on different ledgers and never merge the two. **AI-referred** conversions are the ones where a visitor clicked through from an assistant and bought. Measurable, last-click, conservative. **AI-influenced** conversions are the ones AI shaped without a trackable click. The shortlist effect, surfacing later as branded or direct. This is the revenue-side echo of the [cited-versus-recommended](/blog/cited-vs-recommended-in-ai-search) distinction: being named in an answer changes behaviour even when no referral is logged.

Report them as two figures, not one blended estimate. The referred number is defensible on its own; the influenced number is an inference you support with the correlation test below, clearly labelled as such.

> The honest AI-revenue figure is a floor with a footnote, not a headline. Report the conversions you can trace, flag the influence you can infer, and name the visits you can't see. A number nobody can poke a hole in beats a big one that collapses under one question.

## How do I validate the relationship instead of assuming it?

With a holdout or a lagged correlation, because a raw before-and-after proves nothing on its own. A clean correlation between rising citations and rising branded/direct traffic is suggestive, but [reading a visibility case study critically](/blog/how-to-read-an-ai-visibility-case-study) means asking whether anything else changed in the same window. Two practical checks:

1. **Lagged correlation.** Track [citation coverage](/glossary/citation-coverage) and [share of voice](/glossary/share-of-voice) against branded-search and direct volume over several months. AI influence shows up with a lag, so look for movement that *follows* citation gains, not coincident spikes that a campaign could explain.
2. **A bounded holdout.** Where you can, hold a set of pages or a market steady while you improve AI visibility elsewhere, and compare the conversion trend. It won't be a perfect experiment, but a controlled comparison is far more persuasive than a single timeline.

Neither test delivers certainty, and saying so is part of the credibility. External evidence helps frame the result. Adobe Digital Insights reported in June 2026 that AI-referred retail visitors converted ~54% higher and drove ~53% more revenue per visit than non-AI traffic ([the 2026 data](/blog/is-ai-traffic-more-valuable)), but that's directional, single-vendor context, not a substitute for proving the pattern in your own numbers.

## How should I report it to stakeholders?

As a range with its assumptions on the page. A defensible AI-conversion report has four parts: the **traced** revenue (AI-referred, last-click), the **assisted** contribution (with the attribution model named), the **inferred** influence (from the correlation, clearly hedged), and the **blind spot** (the dark-traffic estimate you can't confirm). Present a conservative floor and a plausible range rather than a point estimate, and revisit it on a cadence. This is the revenue layer of the broader [AI-visibility reporting stack](/blog/ai-visibility-reporting-stack), and it pairs naturally with the [brand-mention versus source gap](/blog/brand-mention-gap-vs-source-gap) audit on the demand side.

Proving AI traffic converts is less about a clever query than about disciplined honesty: measure what you can, infer what you must, and disclose what you can't. That's the same standard **Buffy Intel** holds when it ties AI visibility to outcomes across every engine. Questions: support@flash.tech.

## How to turn query fan-out data into AI citations
Source: https://heybuffy.com/blog/query-fan-out-content-loop

The most reliable way to produce content AI engines cite is to let their own [query fan-out](/glossary/query-fan-out) tell you what to write, then measure which pages actually get cited and double down. The loop has three moves: **mine the fan-outs** behind the prompts you track for recurring themes, **publish focused content** against them, and **measure crawl-to-citation lag** so you keep winners and cut the rest. One practitioner reported using this loop to grow a brand-new domain's daily ChatGPT citations from about 200 to over 1,700.

A scope note up front: that 200→1,700+ figure is single-vendor and self-reported (Promptwatch's co-founder, June 2026). Directional evidence, not a guarantee. The *method* is what travels, and it lines up with how AI retrieval and crawling demonstrably work.

## What is the query fan-out content loop?

It's a content process driven by measurement instead of intuition. Rather than brainstorming topics, you observe the sub-questions AI engines generate when answering the prompts your customers actually ask, then write to those, and let citation data decide what to scale. Stated as a subject-predicate-object: the engine's fan-out tells you the demand, your content answers it, and your crawl-and-citation tracking grades the result.

It assumes you already track a realistic prompt set. If you haven't built one, start with [how to choose which prompts to track](/blog/how-to-choose-prompts-to-track). The loop is only as good as the prompts feeding it. The aim is deliberately modest and scalable: don't "over-engineer it," just keep the loop turning.

## Step 1: Mine the query fan-outs for recurring themes

When an AI engine answers a prompt, it quietly fans that one prompt into many sub-queries and gathers passages for each ([how query fan-out works](/blog/how-query-fan-out-works)). Those sub-queries are a direct readout of what the engine wants content for.

After a few days of tracking an organic prompt monitor, analyse the fan-outs across all of those prompts and look for patterns:

- **Repeated wording**: the exact phrases that recur across fan-outs are the language to write in.
- **Average number of fan-outs**: how many sub-questions a prompt tends to spawn, which sizes the topic.
- **Recurring sub-questions**: the branches that show up again and again are your content backlog, ranked by demand.

The output of step one is a list of themes grounded in real engine behaviour, not a guess. This is the same fan-out lens the corpus describes for [diagnosing where you're absent](/blog/why-youre-invisible-in-ai-search). Here it's turned outward, into a content plan.

## Step 2: Publish focused content against each theme

Write one clean, self-contained piece per recurring theme, in the wording the fan-outs revealed. The craft that makes a passage liftable is covered in [how to get cited by AI](/blog/how-to-get-cited-by-ai): answer-first chunks, facts in tables and lists, question-style headings, and specific, dated claims. The point of the loop is that you're not choosing topics in the dark. Each piece targets demand the engine has already shown.

Favour **focused, single-topic depth** over sprawling guides. Practitioner field data has repeatedly found that deep, single-topic explainers overtake broad comparison pages on citations over time, so the fan-out themes are best answered as a set of tightly-scoped pages, each owning one branch, interlinked into a hub.

## Step 3: Measure crawl-to-citation lag, then double down

This is the step most content programmes skip, and it's where the loop earns its keep. After publishing, measure two things per page: how long it takes to get **crawled** by AI bots, and how long until it starts getting **cited**.

Expect a gap between them. Crawling comes first, indexing second, citations third, so a page can be crawled heavily for weeks while earning zero citations, which is a [leading indicator, not a failure](/blog/chatgpt-citation-lag). Watching your [server logs for AI crawler hits](/blog/how-to-see-which-ai-bots-crawl-your-site) tells you a page has entered the pipeline before any citation shows up.

| Signal | What it means | What to do |
|---|---|---|
| Crawled, no citations yet (weeks 1-3) | Normal lag. Page is in the pipeline | Wait; don't judge it dead |
| Crawled, then cited | The theme and format are working | **Double down**: write more in that vein |
| Not crawled at all | Access or discovery problem | Check [crawler access](/blog/is-your-cdn-blocking-ai-crawlers) and internal links before judging content |
| Crawled heavily, still uncited after weeks | The piece isn't earning selection | Cut your losses and move on to the next theme |

> Once content is published, the only honest question is what got cited. Double down on the pages that win citations, stop investing in the ones that don't, and keep the loop turning. That continuous cycle is how daily citations compound.

The one caveat: only "kill" a page once you've ruled out access and parseability. A well-written piece that never gets crawled is a [reachability problem](/blog/is-your-cdn-blocking-ai-crawlers), not a content one, and killing it would be learning the wrong lesson.

## How long before the loop pays off?

Weeks, not days, and that's by design, because of the crawl→index→cite lag. The discipline is to let each piece clear that lag before grading it, then let citation data, not opinion, decide what you scale. Because live retrieval also favours recently-updated pages, winners need a [refresh cadence](/blog/content-freshness-citation-cliff) to keep their citations from decaying.

Running this loop by hand. Tracking prompts, analysing fan-outs, watching crawl logs, and attributing citations to specific pages over weeks. Is a lot of measurement. Doing that measurement continuously, across every engine, and turning it into a prioritised content signal is exactly what **Buffy Intel** is built to provide.

## The Reddit AEO playbook for early-stage startups
Source: https://heybuffy.com/blog/reddit-aeo-for-startups

Reddit is one of the most-cited sources in AI answers, and it is the rare visibility channel where an early-stage startup can out-earn an enterprise. AI engines favour the authentic, first-person experience Reddit is built on, and a credible founder answering real questions earns that signal in a way a big brand's approval process cannot. The play is a phased, genuinely-helpful presence in the communities where your buyers already debate, not a posting blitz.

This is the founder-and-small-team version of [using Reddit for AI search visibility](/blog/how-to-use-reddit-for-ai-search-visibility): same channel, but a phased method built for a two-person marketing team with no budget. The facts below draw on HubSpot's 2026 Reddit-for-startups playbook. A vendor source, so treat its figures as single-source and directional.

## Why does Reddit favour startups over enterprises?

Because Reddit rewards authenticity, not budget, and authenticity is the one thing a founder has that scale erodes. Reddit users spot inauthenticity fast, and an early-stage founder carries the credibility of being a real person with genuine experience. A large brand routing every post through legal and brand review reads as exactly the corporate voice communities (and the engines reading them) discount.

The evidence that Reddit matters for [AI visibility](/glossary/answer-engine-optimization) is consistent across independent sources:

| Finding | Source | As of |
|---|---|---|
| Reddit is the most-cited domain across LLM responses, often ahead of Wikipedia and YouTube | Semrush analysis of 200,000+ LLM citations | 2026 |
| Reddit leads social-media citations across 9 tracked product categories | Tinuiti AI Citations Trends Report Q1 2026 | Q1 2026 |
| 44% of marketers made a business purchase based on a brand discovered through an AI answer | HubSpot 2026 State of AEO report | 2026 |

The takeaway: when a question turns on lived experience, engines reach for the forum where humans answered it, and a founder can be the human who answers it well.

## What does "good" look like on Reddit (and what gets you banned)?

The dividing line is the **95/5 rule**: at least 95% of your presence adds real value. Answering questions, sharing experience, contributing, and 5% or less mentions your product, only when it is an obvious, directly relevant answer to a question someone asked. Reddit caps self-promotion and treats the rest as spam; r/SaaS, for instance, allows one product mention every 60 days and bans accounts that ignore it.

A post that earns both community trust and an AI [citation](/glossary/citation) tends to do five things:

- **Leads with the answer**: the same answer-first discipline that wins on your own site.
- **Addresses a real problem** aimed at a specific buyer, use case, and concrete outcome.
- **Earns engagement**: comments, upvotes, and cross-references in other threads.
- **Sounds like a person**: first-person, first-hand, not a corporate brand voice.
- **Connects to your owned content** only when it genuinely adds to the thread.

One caution worth pricing in: AI doesn't cherry-pick your positive mentions. Per HubSpot's playbook, citation rates for positive and negative brand [sentiment](/glossary/sentiment-analysis) on Reddit are roughly equal. Both around 5%, so if you have no presence, AI answers will fill the gap with whatever exists, including threads from unhappy customers.

## What is the phased Reddit AEO method for a lean team?

Three phases over about 90 days, so Reddit stays consistent without becoming a full-time job. Each phase maps to a signal engines reward.

| Phase | Window | What you do |
|---|---|---|
| 1. Listen and map | First ~2 weeks | Find the 3-5 subreddits where your buyer asks questions; search your category and brand across AI platforms and note every Reddit thread that surfaces; identify questions you could answer better than anyone currently does. |
| 2. Build credibility | Days ~15-75 | Contribute real answers consistently; model your posts on threads already cited in AI answers; no pitching. |
| 3. Originate content | Day ~75 onward | Turn the questions getting the most traction into owned posts and link them back to the thread. The Reddit-to-owned-content flywheel. |

For B2B startups, the map usually centres on communities like r/startups, r/entrepreneur, r/SaaS, r/marketing, r/sales, and r/growthhacking. Subreddit size matters less than you'd think: a mention from a niche, on-topic community often carries more retrieval weight than a generic high-authority backlink. As HubSpot's playbook puts it, AI engines pull from niche industry forums in indirect ways. Community recaps republished on a blog, niche newsletters getting indexed, so contribute where you can genuinely add value, not just where the subscriber count is highest.

> Credibility comes first, citation follows. If you're starting from zero, pick 3-5 subreddits where your buyers live and contribute real answers for 60-90 days before you even think about attribution.

## How do you connect Reddit to the rest of your AEO strategy?

Reddit doesn't work in isolation. It's one of the highest-trust inputs in a [corroborated](/glossary/corroboration) mix. AI models synthesise across your site, LinkedIn, third-party blogs, review sites, and forums, and the goal is a consistent, validated consensus about your brand across all of them. Reddit alongside [earned placement in the third-party best-lists AI cites](/blog/get-into-ai-cited-best-lists). Reddit's specific job is to supply the authentic, experience-based layer that polished marketing can't.

The flywheel is what makes it compound. Threads with real engagement show you what your buyers actually care about; turn the highest-traction questions into focused owned content and link back to the original thread. The thread makes the post more citable, and the post makes the thread more authoritative. The same single-topic-depth move that [breaks the citation ceiling](/blog/how-to-get-cited-by-ai). Just don't manufacture the consensus: as we cover in [whether AI search can be manipulated](/blog/can-ai-search-be-manipulated), seeded reviews and vote manipulation get discounted by engines and called out by communities, and a public call-out gets indexed too.

## How do you measure Reddit AEO performance?

Track five metrics as a trend across engines, not a single snapshot. These are the same signals that separate being [cited from being recommended](/blog/cited-vs-recommended-in-ai-search):

| Metric | What it measures | Early "good" |
|---|---|---|
| Mention rate | How often your brand appears in AI answers | Surfacing in 2 of 3 benchmark prompts, month on month |
| Citation share | How often your domain (or your Reddit threads) is cited | Your threads appearing for category prompts |
| AI referral traffic | Visits arriving from answer engines | Any consistent growth, however small |
| [Share of voice](/glossary/share-of-voice) | Your position versus competitors in AI answers | Growing share relative to rivals |
| Sentiment score | How AI describes your brand | Predominantly positive; neutral is fine early |

Start with a baseline: spend ten minutes asking Claude or Perplexity what they'd tell a buyer about your brand right now. What comes up, and what doesn't. Is your starting line. HubSpot reports its own AEO beta customers saw materially higher AI traffic, lead growth, and conversion than non-users, but those are vendor-stated, self-reported figures with no independent audit, so read them as directional, not a forecast for your brand.

Then watch the trend over time, across ChatGPT, Google AI Mode, Gemini, Perplexity, and Claude, which is exactly what **Buffy Intel** measures, so you can see your Reddit credibility turn into citations before it shows up in revenue. Questions: support@flash.tech.

## What are Reddit's product pages? How Reddit turns threads into AI shopping pages
Source: https://heybuffy.com/blog/reddit-product-pages

**A Reddit product page is a page Reddit generates about a specific product, built from what redditors already said about it.** When a product name is highlighted inside a thread, tapping it opens an AI-written summary of Reddit conversations across the platform, plus direct quotes — and, when the brand has supplied a catalog, a product image, price, and buy link. Reddit began testing these pages for US users in early 2026 and widened the shopping push at Cannes Lions in June 2026.

The part that matters for brand visibility: the summary is written from redditor conversations, not brand copy. A brand supplies the price tag, not the verdict. This piece explains what the feature is, how it works, and why it turns [earned media](/glossary/earned-media) into a shopping surface you can influence but not author. Volatile specifics — categories, geography, rollout dates — are dated to mid-2026; the mechanic is the durable part.

## What is a Reddit product page?

A Reddit product page is a product-specific "deep dive" assembled from community discussion. According to coverage of Reddit's early-2026 test (TechCrunch, February 2026) and its Cannes Lions 2026 announcement, a redditor reading a thread sees popular product names highlighted; tapping one opens a dedicated page for that product.

That page has two kinds of content, and only one of them comes from the brand:

| Part of the page | What it contains | Who it comes from |
|---|---|---|
| AI summary | A recap of what redditors across the platform have said about the product | Generated from Reddit conversations |
| Direct quotes | Verbatim lines pulled from real threads | Redditor comments |
| Commerce card | Product image, price, and a where-to-buy / buy link | The brand's product catalog (when supplied) |

Source: reporting on Reddit's shopping test (TechCrunch, February 2026) and Cannes Lions 2026 announcement. The split is the whole story: the editorial verdict is community-authored, while the brand contributes only the transactional card.

## How does a Reddit product page get built?

It is built from conversations first, then supplemented with a catalog. Reddit has described a community-first model: the page draws on products "directly mentioned by users from real conversations on related posts and comments," and only then layers in structured product data from partner catalogs.

The catalog data comes through Reddit's Dynamic Product Ads (DPA) infrastructure, which reached general availability in May 2025. When a brand's DPA feed includes the product, the page can show its image, current price, and a link out to a retailer. When there is no catalog entry, the page still exists — it just shows the community summary and quotes without a buy button. So the page is not something a brand opts into; it appears because redditors discussed the product, and the brand's catalog only enriches a page that already exists.

## Where do these pages show up in Reddit's AI search?

They surface inside Reddit Answers, Reddit's AI-powered search, when someone asks a shopping question. For product-related queries — Reddit's own examples include "best noise-cancelling headphones" and "electronic gift ideas for a college student" — the results can include a "Related Products" carousel at the bottom of the answer, showing products mentioned in the underlying discussions with pricing, images, and where-to-buy links. Selecting a card opens the product's page.

That places Reddit alongside the other engines that now answer "which one should I buy" directly rather than sending a click. It is a new [shopper-agent](/glossary/shopper-agent)-style surface built on top of the discussions Reddit already hosts — and Reddit is one of the most-cited domains in AI answers generally (see [the most-cited domains in AI Overviews](/blog/most-cited-domains-ai-overviews)), which is why this move compounds.

> On a Reddit product page, the review writes itself from what redditors already said. A brand supplies the price tag, not the verdict — so the comments people leave this quarter become the product page next quarter.

## Why does this matter for brands?

Because it converts scattered Reddit opinion into a single, durable, AI-summarised page per product — and brands can influence it only indirectly. Three shifts make it consequential:

- **The summary is not marketing you control.** You cannot write or approve the recap; it reflects the balance of what redditors said. A product with a recurring complaint in its threads gets a page that leads with that complaint.
- **It is a zero-click shopping surface.** A shopper can read the community verdict and tap a buy link without leaving Reddit — a [zero-click](/glossary/zero-click-search) purchase path where the deciding content is other people's comments.
- **Reddit sits upstream of other engines.** Because ChatGPT, Google AI Overviews, and others frequently cite Reddit, the same threads that feed a Reddit product page also feed the answers on other platforms. Reddit describes itself as the place where "over half of all online conversations related to purchasing decisions" happen — a self-reported, directional claim, but one that explains why the surface is being built here.

Reddit reported its search grew from roughly 60 million to 80 million weekly users year over year, and Reddit Answers from about 1 million to 15 million weekly users between early and late 2025 (Reddit, via TechCrunch). Treat the exact figures as single-source and dated; the direction — a fast-growing AI search surface now wired to shopping — is the point.

## How is a Reddit product page different from a "best tools" list?

It is community-authored and product-specific, not an editorial ranking. A [best-of list](/glossary/best-of-list) or a comparison article is written by one author making a case; a Reddit product page is a synthesis of many redditors' first-person experience, which is exactly the signal AI engines favour over brand marketing. That also makes it harder to game: there is no page to optimise directly, only the underlying conversation to earn honestly. It is closer to a live, aggregated review section than to a piece of [answer-engine-optimisation](/glossary/answer-engine-optimization) copy — and it is why the playbook for showing up well is an earned one.

## What should a brand do about it?

Focus on the one lever you have — the conversation — and supply a clean catalog so the commerce card renders. The full method is in the companion how-to, [how to influence your Reddit product page](/blog/influence-your-reddit-product-page): earn genuine positive discussion, fix the real issues redditors raise, keep your [product feed](/glossary/product-feed) accurate so the buy link works, and measure whether you actually surface. If you are still deciding whether Reddit deserves the investment at all, start with [is Reddit worth it for AI visibility](/blog/is-reddit-worth-it-for-ai-visibility) before the [Reddit AEO playbook](/blog/how-to-use-reddit-for-ai-search-visibility).

Knowing whether a Reddit product page even exists for your product — and what it says — is a monitoring problem, not a guessing one. That is what **Buffy Intel** tracks: where your brand surfaces across AI shopping and answer surfaces, snapshot over snapshot, so you see the page forming before a shopper does. Questions: support@flash.tech.

## Which schema types does the web actually use? Google and Schema.org's usage dataset
Source: https://heybuffy.com/blog/schema-usage-statistics-dataset

In June 2026, [Schema.org](/glossary/structured-data) and Google published a public dataset showing how often each Schema.org type and property appears across the web Google crawls. It answers a question SEO and content teams have argued about for a decade, *which structured-data types are actually used, and by how many sites*, with crawl data instead of guesses. This is a dated reference to what the dataset contains, how to read its domain buckets, and what it does (and does not) mean for AI visibility.

**Last reviewed: 1 July 2026.** All figures below come from Schema.org's announcement (4 June 2026), its usage-statistics documentation, and the dataset's first release (dated May 2026), corroborated by Search Engine Land and industry coverage. The counts are Google's crawl-based measurements, aggregated at the domain level and reported as ranges, so read the *direction* as firmer than any single number, and cite "Schema.org/Google, May 2026 release" when you reuse a figure.

## What is in the Schema.org usage dataset?

The dataset reports, for every Schema.org term, how many distinct domains use it. Schema.org announced it on **4 June 2026** as a collaboration with Google, framed as transparency into how the vocabulary is actually deployed on the web.

| Attribute | Detail |
|---|---|
| Announced | **4 June 2026** (Schema.org blog) |
| First data release | **May 2026** (file `2026_05.csv`) |
| Coverage | **958 Itemtypes** (types) + **4,587 predicates** (properties) = **5,545 entries** |
| Formats | **CSV and JSON** |
| Location | Canonical Schema.org **GitHub repository** (`schemaorg/schemaorg`, under the Google public-stats path) |
| Update cadence | **Monthly**: a new file per month, so trends are trackable over time |
| Measurement | Term frequencies within **Google's public web crawl** |

Source: Schema.org (blog + usage-statistics docs, 2026); coverage counts via industry reporting (ppc.land). Because a new file lands each month, the repository doubles as a longitudinal record. You can diff `2026_05.csv` against later months to watch adoption move.

## How does the "domain bucket" work, and why ranges, not counts?

The dataset counts **domains, not pages or markup objects**. Schema.org states the rule plainly: *"if you use the same term on 100 pages of your site, it still only counts as one domain using it."* A publisher with `Product` markup on half a million URLs is one domain in the tally, exactly like a shop with three.

Instead of exact totals, each term is placed in a **popularity range bucket**. The buckets seen in the first release span several orders of magnitude:

| Domain-count bucket | Reading |
|---|---|
| **10M+** | Near-universal. Foundational site-structure and identity types |
| **1M - 10M** | Very common. Mainstream commerce and content types |
| **100K - 1M** | Widely used within their niche |
| **10K - 100K** | Established but specialised |
| **1K - 10K** | Niche / vertical-specific |
| **< 1K** | Rare. Long-tail, experimental, or highly specialised terms |

Ranges exist for privacy and stability: aggregating to buckets avoids exposing exact per-site data and, as Schema.org notes, filters daily noise because *"web adoption trends change slowly."* The practical effect is that the dataset tells you an order of magnitude. "Millions of sites" versus "a few thousand", not a precise count.

## Which schema types does the most of the web use?

The top bucket is dominated by the types that describe **site structure and identity**, not fancy rich-result markup. Per the May 2026 release, the most widely adopted Itemtypes are:

1. **WebPage**
2. **WebSite**
3. **Organization**
4. **BreadcrumbList**
5. **ListItem**

Commerce aggregate types sit a tier down. **AggregateOffer** and **AggregateRating** land around the **1M-10M-domain** range, while specialised types such as `AllocateAction`, `AgreeAction`, and `AmpStory` fall into the **under-1K** long tail. The pattern is intuitive once stated: almost every site declares *what page this is* and *who publishes it*; far fewer mark up ratings, and only a handful use the exotic action types.

> The web agrees on the boring basics. WebPage, WebSite, and Organization are near-universal; the specialised types most SEO advice obsesses over live in the long tail. Adoption tells you what is common, not what will get you cited.

The counts confirm the [entity-clarity](/blog/entity-strength-ai) fundamentals we already recommend: `Organization` and `WebSite` markup. The schema that tells an engine *who you are* and *what site this is*. Is table stakes, used by the bulk of the crawlable web.

## What does this dataset mean for AI visibility?

It is a prioritisation input, not a ranking factor. Popularity in the dataset measures **adoption**, not citation performance. A type used by ten million domains does not earn you a citation, and a rare type is not automatically valuable. What the dataset usefully does:

- **Settles "is this type real / worth it?" debates.** Knowing a type sits in the 10M+ bucket versus the under-1K tail helps you decide whether it is a safe, well-supported choice or an experimental one.
- **Reveals table-stakes markup.** If the near-universal types (`WebPage`, `WebSite`, `Organization`, `BreadcrumbList`) are missing from your pages, you are below the web's baseline for machine-legibility. See [making your site agent-readable](/blog/make-your-website-agent-readable).
- **Guides which valid types to add next**, which we turn into a step-by-step method in [how to prioritise your structured data using this data](/blog/prioritize-your-structured-data).

The caveats matter, and Schema.org states them. The counts **reflect the web as indexed by Google**, so sites that block crawlers are undercounted. Markup formats. **JSON-LD, Microdata, RDFa**: are combined into one figure. And niche terms (medical, government) stay in low buckets despite being exactly right for their domain. The honest reading: use adoption data to avoid dead-end markup and to confirm the basics, but never treat "popular" as "better for citations."

Structured data still earns its place because it makes your facts easy for an engine to lift. The extractability half of getting [cited by AI](/blog/how-to-get-cited-by-ai) and of [accessibility-as-parseability](/blog/accessibility-and-ai-parseability). For commerce specifically, `Product`/`Offer` markup is what lets an engine quote your price and availability cleanly, a point we develop in [writing conversational product pages](/blog/write-conversational-product-pages). Schema is necessary, not sufficient: the markup has to match real content, and the facts underneath still have to be specific, accurate, and [corroborated](/glossary/corroboration).

Because the dataset refreshes monthly and adoption drifts, we keep references like this on a [refresh cadence](/blog/content-freshness-citation-cliff) and update the buckets substantively as new files land. Never a silent date-bump. The number that ultimately matters is not how many sites use a schema type, but whether the engines surface, cite, and recommend *your* brand for the questions your buyers actually ask. Tracking that across every engine, over time, is exactly what **Buffy Intel** is built to do.

## How to measure your social and video content in Google Search with platform properties
Source: https://heybuffy.com/blog/search-console-platform-properties

Google Search Console can now tell you how your Instagram, TikTok, X, and YouTube content performs inside Google Search, and that matters for AI visibility because your off-site content is a large, previously unmeasured part of what AI engines learn and cite about you. The feature is called **platform properties**: a Search Console property type that reports the clicks, impressions, and queries your social and video posts earn in Google Search, Discover, and Google News. Google introduced it on **7 July 2026** and rolled it out to all account holders worldwide by **29 July 2026**. This guide explains what it shows, what it deliberately leaves out, and how to use it as an AI-visibility signal.

**Last reviewed: 24 August 2026.** Details are attributed to Google's Search Central announcement and corroborating trade coverage, and dated because the feature is new and still widening.

## What do platform properties actually show?

They show how Google discovers and surfaces your off-site content — not the platform's own analytics. For a verified platform presence, Search Console reports the same core metrics you get for a website:

| Metric | Reported for platform content? |
|---|---|
| Clicks from Google | Yes |
| Impressions in Google | Yes |
| Search queries that surfaced it | Yes |
| Surfaces covered | Google Search, Discover, and Google News |
| Native platform analytics (in-app views, etc.) | No — this is Google-side data only |

The supported platforms are **Instagram, TikTok, X, and YouTube**. The data describes *Google's discovery* of that content, so it answers a question creators and brands could not answer before: when your video or post shows up in a Google search or in Discover, how often does that happen and for which queries? Because the metrics come from Google rather than the platform, they are directly comparable to your own website's Search Console data.

## Why does off-site content matter for AI visibility?

Because AI answers are assembled from across the web, not just your domain. Several of the most-cited sources in AI answers are platforms you do not own: [YouTube is the single most-cited domain in Google's AI Overviews](/blog/how-to-earn-ai-citations-from-youtube), and community and social content feeds both training and live retrieval. Your presence on those platforms is part of your [entity authority](/glossary/entity-authority) — the web-wide, corroborated footprint AI engines lean on when deciding [which brand to cite](/blog/why-ai-cites-one-brand).

Until now, a brand had no first-party Google signal for how that off-site content was being discovered. Platform properties give you one, for free. If your YouTube explainers or your X posts are surfacing in Google Search for the questions your buyers ask, that is a leading indicator that the same content is discoverable to the systems that build AI answers on top of Google's index.

> Your AI-visibility footprint is bigger than your website. Platform properties are the first free way to see how the off-domain half of it performs in Google — the part that feeds AI answers you do not control.

## What do platform properties deliberately leave out?

Several important things — and reading the report honestly means knowing them:

- **No AI performance report.** Website properties include the [Generative AI performance report](/blog/google-search-console-ai-performance-report) that shows impressions in AI Overviews and AI Mode. Platform properties, as of mid-to-late 2026, do **not**. So this measures classic Search, Discover, and News, not AI-answer impressions.
- **No cross-platform rollup.** Comparing performance across Instagram, TikTok, X, and YouTube requires manual export and reconciliation; there is no unified view.
- **Per-presence verification.** Each platform presence is verified separately, which is real overhead for anyone managing several. Creators above reported follower thresholds — 100,000 on YouTube, Instagram, or X, and 300,000 on TikTok — are enrolled automatically.
- **Reporting quirks.** Google notes, for example, that YouTube playlist reporting reflects the playlist page rather than the individual videos, which can inflate reach if mixed with video-level data.

The net: platform properties are a **proxy for discoverability, not a direct AI-citation metric.** Use them to see whether Google finds and surfaces your off-site content — a genuine leading indicator — but do not read them as proof of AI-answer inclusion.

## How should you use platform properties for AI visibility?

Treat them as one input in a per-surface measurement stack, not a standalone answer:

1. **Verify the platforms you actually invest in.** Start with YouTube if you publish video, since it carries the most AI-citation weight, then add the social presences that matter for your category.
2. **Read queries, not just totals.** The query list tells you which questions already pull your off-site content into Google — the same questions worth targeting with extractable, answer-first content on your own domain.
3. **Pair it with your AI-specific signals.** Combine it with your website's [AI performance report](/blog/google-search-console-ai-performance-report) and a purpose-built [AI-visibility measurement](/blog/how-to-measure-ai-visibility) view, so you cover discovery (platform properties), AI-answer impressions (the AI report), and citations (a dedicated tracker).
4. **Watch the trend per surface.** Because there is no rollup, keep a simple per-platform line over time; a rise in Google discovery of your video is a leading signal worth acting on before it shows up in citations.

The honest read for late 2026: platform properties close a real measurement gap — the off-domain content that feeds AI answers — but they measure Google discovery, not AI citations, so they belong alongside your other signals rather than replacing them. Stitching discovery, AI-answer impressions, and citations into one per-engine, over-time view is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.

## Do you need a separate 'AI version' of your website?
Source: https://heybuffy.com/blog/separate-ai-version-of-your-website

**For almost every site, no. A separate "AI version" isn't worth building.** The higher-leverage move is to make your one real website reachable and parseable. The 2026 evidence backs this: in an Ahrefs analysis of 137,210 domains, 97% of published [llms.txt](/glossary/llms-txt) files received zero requests in May 2026, with the major AI crawlers fetching ordinary HTML directly instead.

This matters because a popular strand of advice says the opposite: strip out your layout, remove the "noise," and hand language models a simplified, machine-only view. It sounds efficient. It mostly isn't, and it can quietly work against you.

## Should you build a stripped, machine-only version of your site for AI?

No, with one narrow nuance. There are two different things people mean by an "AI version," and only one is risky:

- **Serving the *same* content in a cleaner, more machine-legible form**. Semantic HTML, [structured data](/glossary/structured-data), and (for simple bots) a Markdown or text representation alongside your normal pages. This is sound, and we cover the how in [how to make your website agent-readable](/blog/make-your-website-agent-readable).
- **Maintaining a *separate, stripped* mirror**. A parallel "AI-only" site or a divergent simplified page that exists apart from what humans see. This is the one to avoid: it adds cost, invites divergence, and chases a benefit the data doesn't support.

The distinction is between *the same truth, more legibly* and *a second, different truth*. The first helps. The second is the trap.

## What does the llms.txt data actually show?

`llms.txt` is the clearest test case for the "give AI its own file" idea, and the 2026 numbers are blunt. Ahrefs analyzed domains that received traffic in May 2026 and looked at who actually fetched their `llms.txt`:

| Finding (Ahrefs, 137,210 domains, May 2026) | Reported figure |
|---|---|
| Domains publishing a valid `llms.txt` | ~28% (~38,000 sites) |
| Of those, files that received **zero** requests | **97%** |
| Files that got any requests at all | ~3% (~1,100 domains) |
| Of requests that did arrive, share from bots | ~96% |
| GPTBot share of AI requests | ~4.5% |
| OAI-SearchBot share of AI requests | ~0.7% |

Ahrefs reported that the major crawlers. GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended. Overwhelmingly skip the file and crawl HTML directly, and concluded the cons outweigh the pros for most sites (most defensible only where your audience uses coding agents). As of mid-2026, that's the state of play; it could change if an engine commits to reading the file, so date any claim you make about it. This is fresh confirmation of a verdict we'd already reached in [is llms.txt worth it](/blog/is-llms-txt-worth-it): cheap hygiene, not a lever.

## Why does a stripped "machine-only" page lose meaning?

Because a page is more than the words on it. As SEO engineer Jono Alderson put it in a June 2026 essay, "a page is not just a container for words. It's an editorial artefact" with "hierarchy, emphasis, framing and intent baked into it." Placement, prominence, and context change how information is interpreted; strip them away and you optimise for extraction at the cost of understanding.

A separate machine-only version creates three concrete problems:

- **Divergence.** Once two representations of the same content exist, they drift. The human page gets updated; the AI mirror lags, and now engines (and you) have two versions of the truth to reconcile.
- **Trust and cloaking risk.** Serving systematically different content to bots than to people is the definition of cloaking. Even when well-intentioned, it gives an engine a reason to distrust the source rather than cite it.
- **A shrinking payoff.** Models are getting better at rendering and reasoning over real pages, not worse. The simplified mirror you build today is a maintenance burden you'll still be carrying when the engines no longer need it.

> Optimise the page, not a shadow of it. A stripped mirror trades the signals models actually use. Structure, context, corroboration, for a short-lived convenience, and leaves you maintaining two versions of the truth.

## When is a machine-readable layer actually worth it?

When it's the *same* content, served more cleanly, at no divergence cost. Concretely:

- Exposing your core content as clean Markdown or text **for simple bots**, generated from the same source as your HTML so the two can't disagree.
- Sites whose customers genuinely use **coding agents**: the one audience Ahrefs flagged where a dedicated file is defensible.
- Adding `llms.txt` as **near-zero-cost hygiene**, accurate and auto-generated, with no expectation that it moves citations.

The test is simple: if the machine-readable layer is a *byproduct* of your real content, keep it. If it's a *separate thing a human has to maintain*, you've built the liability, not the asset.

## What should you do instead?

Spend the effort on the levers that the evidence supports. The same ones that make a page good for a screen reader make it good for an [AI crawler](/glossary/ai-crawler):

1. **Be reachable.** Server-rendered HTML, and confirm your [CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers).
2. **Be parseable.** Real semantic structure. Headings, lists, tables, real `<a>`/`<button>`, not `<div>` soup. See [accessibility and AI-parseability](/blog/accessibility-and-ai-parseability).
3. **Label your facts.** [Structured data](/glossary/structured-data) tells engines what things are instead of making them guess.
4. **Stay fresh and authoritative.** A current page from a corroborated [entity](/glossary/entity-authority) gets retrieved; a stale, lone-voice page doesn't, that's the [freshness cliff](/blog/content-freshness-citation-cliff) at work.

Make the one site you already have legible, current, and trustworthy, then measure whether engines actually surface it. Watching that visibility across every engine over time, so you can tell hygiene from a real lever, is exactly what **Buffy Intel** is built for.

## How Shopify's agentic storefronts decide which products an AI agent sees
Source: https://heybuffy.com/blog/shopify-agentic-storefronts

Shopify's [agentic commerce](/glossary/agentic-commerce) push has flipped the default: most eligible merchants' products are now syndicated to AI agents automatically. But two things decide whether an agent actually surfaces your product. **Shopify's Catalog ranks it first, then the agent re-ranks it on its own logic**: and a large share of what the agent reads about you is data Shopify *guessed* rather than data you stated. This is a teardown of that pipeline and the parts you control.

It assumes you already know what agentic commerce is, if not, start with [what is agentic commerce](/blog/what-is-agentic-commerce), and focuses on Shopify's specific implementation as of mid-2026.

## What changed in Shopify's Spring '26 Edition?

Shopify made agentic discovery the platform default. The Spring '26 Edition launched on **17 June 2026** with 150+ updates under an agentic-commerce headline; Agentic Storefronts had debuted in the Winter '26 Edition (10 December 2025) and were activated across stores through early 2026. The mechanism is the **Shopify Catalog**: eligible merchants' products are syndicated, by default unless opted out, to AI surfaces. Shopify names ChatGPT, Microsoft Copilot, Google AI Mode, Gemini, and the Shop app. Shopify reports that AI searches powered by the Catalog convert at roughly **2× the rate** of those built on scraped data. A Shopify-stated figure with no independent audit, so read it as directional.

The plumbing is the **Universal Commerce Protocol (UCP)**, co-developed with Google and backed by a wide group of platforms (Amazon, Meta, Microsoft, Salesforce, Stripe, Etsy, Target, Wayfair, among others). UCP is an open standard covering the journey from discovery to checkout. We've compared it to the browser-side approach in [WebMCP vs UCP](/blog/webmcp-vs-ucp); here the focus is what UCP does *inside* Shopify.

## How does the Shopify Catalog rank products, and why does the agent re-rank?

In two passes. Shopify's Catalog returns a ranked set of products for an agent's query; then the agent applies its own logic on top. Shopify's own admin reportedly warns, in effect, that *agentic storefronts often re-rank results on their own logic, so the preview can differ from what a shopper sees in the actual AI experience.* You optimise the input you control. The Catalog ranking, and accept that the final order is the agent's call.

According to a June-2026 teardown of Shopify's agentic documentation (by practitioner Ankit Mintocha, who runs the catalog-audit tool Atomz. Single-source, so treat the granular specifics as early and evolving), the Catalog scores five **listing-quality signals** per product:

| Signal | What it measures |
|---|---|
| Description completeness | Whether the product copy is full and specific |
| Image coverage | Whether the product is well-represented visually |
| Product reviews | Presence and depth of reviews |
| Variant & option completeness | Whether sizes, colours, and options are fully populated |
| Shop policy completeness | Whether shipping, returns, and store policies are filled in |

On top of those, Shopify's docs reportedly note that relevance "also depends on other signals such as popularity, customer engagement, and brand recognition". The slow-compounding [entity](/glossary/entity-authority) layer that sits separately and can't be filled in overnight. The five signals are the levers you can move this quarter; the engagement layer is the one [why AI cites one brand](/blog/why-ai-cites-one-brand) is really about.

## What does Shopify guess for you, and what can you override?

This is the most important distinction for a merchant. Shopify's **Global Catalog** attaches an *inferred* metadata block to every product response: attributes such as material, style, or occasion, predicted by Shopify's model from whatever data you already have. Those inferences may be missing or wrong depending on how complete your product data is.

> Half of what an agent reads about your product can be something Shopify's model guessed. Fill the same field as a metafield and the agent reads what you wrote instead. The difference between a guessed layer and a controlled layer is the part of agentic readiness you own.

So the override is concrete: where Shopify infers an attribute, **stating it explicitly as a metafield replaces the guess.** That is the same enrichment discipline as [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents) and [writing product pages AI can quote](/blog/write-conversational-product-pages). Only now there's a named mechanism showing exactly where an unstated fact gets filled by a model rather than by you.

One more constraint to plan around: the teardown reports that Shopify's server-side **query-time filters are currently limited to three**: Color, Size, and Target gender. Everything else still influences ranking but can't be used to *filter* at query time yet. If a shopper's agent asks for "waterproof" or "under 200 GSM," that lives in ranking, not in a filter. Another reason explicit, specific copy matters.

## How do agents discover and transact, and what can each one do?

Discovery is wide open; transacting is gated by identity. The teardown reports that every Shopify store now serves an `/agents.md` and related discovery files by default. Crucially, this is a **separate pipe from the open web**: your [robots.txt](/glossary/robots-txt) still governs open-web crawlers, but the Catalog syndicates product data to activated AI channels through a path robots.txt does not see, so the usual [CDN- and robots-level checks](/blog/is-your-cdn-blocking-ai-crawlers) don't tell you whether your Catalog feed is flowing.

What an agent can *do* then depends on how it identifies itself. Per the same teardown, UCP sorts agent traffic into three trust tiers:

| Trust tier | How it identifies | What it can do |
|---|---|---|
| Token | Verified token | Highest rate limits; **only tier that can complete a checkout** |
| Signed | Signed HTTP requests with a public key in a UCP profile | Lower limits; can create a checkout but not complete it |
| Anonymous | No identity | Catalog **read access only**; no checkout |

The pattern mirrors the [Agentic Commerce Protocol (ACP)](/glossary/agentic-commerce-protocol) and the broader payments work: discovery opens to everyone, but anything that touches a cart requires the agent to prove who it is. Treat the exact tier names and limits as early-2026 specifics that will move.

## The practical readiness checklist

If you sell on Shopify, the levers are now unusually concrete:

- **Complete the five signals.** Full descriptions, broad image coverage, reviews, every variant/option populated, and finished shop policies. These are scored per product.
- **State, don't let Shopify guess.** For any attribute that matters (material, style, occasion, fit), set it as a metafield so the controlled layer beats the inferred one.
- **Write for ranking, not just filters.** Only Color, Size, and Target gender filter at query time today; everything else rides on specific, parseable copy.
- **Confirm the feed, not just the crawl.** Catalog syndication bypasses robots.txt, so reachability checks alone won't confirm you're in the agent's view.
- **Decide your transaction posture.** Know which agent tiers you'll accept, given that only token-identified agents can complete a checkout.

Being syndicated by default means the floor is higher and the ceiling is the same as ever: an agent still has to *choose* you. Tracking whether AI agents and answer engines actually surface and pick your products, as Shopify's spec and the agents reading it keep shifting. Is exactly what **Buffy Intel** watches. Questions: support@flash.tech.

## Shopper agents: what brand-owned AI agents mean for product visibility
Source: https://heybuffy.com/blog/shopper-agents-and-product-visibility

A **shopper agent** is a brand-owned AI agent that carries the shopping conversation. From discovery through checkout and into service. In your brand's voice, and increasingly does so inside third-party AI surfaces like ChatGPT, Gemini, and Google AI Mode. The mid-2026 launches made the pattern concrete: Salesforce's Agentforce Commerce reached general availability, and Google rolled out a brand-voice "Business Agent" in Search. The shift is real, but deploying an agent is a new *channel*, not a new *ranking lever*. Whether an engine surfaces your product still depends on the same catalog and [entity](/blog/entity-strength-ai) work as before.

This is part of our [agentic commerce](/glossary/agentic-commerce) series. Here's what a shopper agent actually is, what changed this summer, and. The honest part. What it does and doesn't do for your visibility.

## What is a shopper agent?

A shopper agent is an AI agent that a brand deploys to handle the customer's shopping journey conversationally, rather than leaving the customer to navigate a site or a generic assistant. It answers product questions, compares options, completes checkout, and handles post-purchase service. Speaking in the brand's voice on the brand's behalf.

The mid-2026 packaging from Salesforce, as reported, splits the idea into three roles:

| Agent | Who it serves | What it does (as described) |
|---|---|---|
| Shopper Agent | Consumers | Carries the conversation "from discovery through checkout and into service," in the brand's voice |
| Buyer Agent | B2B buyers | Orchestrates procurement in the channels buyers use. Reported as WhatsApp and SMS |
| Merchant Agent | Operations teams | Organises catalogs and tunes sort/boost rules from plain-language instructions |

Google's comparable move is the **Business Agent**: described as a virtual sales associate that answers product questions in a brand's voice directly inside Search. The through-line across vendors: the brand fields its *own* agent, and that agent is surfaced where shoppers already are.

## What changed in mid-2026?

Brand-owned agents moved from preview to generally available, with distribution *into* the major AI engines as the headline. The dated, attributed picture:

- **Salesforce Agentforce Commerce** reached general availability in **late June 2026**, with the Shopper, Buyer, and Merchant agents live. Salesforce set **native ChatGPT integration to July 2026**, and **Google Search (AI Mode) and the Gemini app to follow later in the summer**.
- **Google** expanded its **[Universal Commerce Protocol](/blog/webmcp-vs-ucp)** and launched agentic shopping tools, including the Business Agent (with named launch partners such as Lowe's, Michael's, Poshmark, and Reebok) and a cross-retailer "Universal Cart," built with commerce platforms including Shopify, Etsy, Wayfair, Target, and Walmart.

Salesforce also reported some eye-catching commerce figures, that AI influenced about **20% of global online sales (~$262 billion)** in the past holiday season, and that retailers deploying their own shopper agents grew sales faster than those without. Treat these as **vendor-reported and directional**: they come from the company selling the product, and the causal claims are not independently verified. The durable fact is the *architectural* shift, not the marketing numbers: brands are now fielding their own agents inside the engines.

## Does deploying a shopper agent make your products more visible?

Not on its own, and this is the distinction that matters. A shopper agent gives your brand a *voice and a checkout* inside AI surfaces once a shopper is engaging with you. It does not decide whether the engine brings your product into the conversation in the first place. Those are two different layers:

- **Selection**: whether ChatGPT, Gemini, or AI Mode surfaces and recommends your product from the whole market. Is decided by [the factors that make an engine recommend a product](/blog/factors-ai-recommends-products): catalog richness, [structured data](/glossary/structured-data), reviews, entity strength, and corroboration. This is [answer-engine optimisation](/glossary/answer-engine-optimization).
- **Conversion**: how well you answer, compare, and close once you're in the consideration set. Is where a shopper agent helps.

A shopper agent with nothing behind it in the selection layer is a well-spoken salesperson no one is sent to. That's the same lesson as the [payment rails](/blog/agentic-commerce-payment-rails): plumbing that activates *after* the choice doesn't make the choice. The agent is the storefront-in-the-answer; being *shown* the storefront is still earned upstream.

## How do you get your products ready for shopper agents?

Make your catalog legible to machines and your brand trusted by engines. The same [agentic-commerce readiness](/blog/agentic-commerce-readiness) work, now with a clear payoff. In priority order:

1. **Enrich the catalog with conversational attributes.** Beyond price and title, expose answers to common product questions, compatible accessories, and substitutes. The exact attribute types Google added to Merchant Center for conversational surfaces. [Prepare your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents) covers the mechanics.
2. **Write [conversational product pages](/blog/where-chatgpt-product-recommendations-come-from)** that read like answers, not brochures, so both the engine and the agent can lift a clean, specific claim.
3. **Make your site an [agent-readable endpoint](/blog/websites-as-agent-endpoints)**: reachable, server-rendered, structured, and exposed through the shared commerce protocols agents speak.
4. **Invest in entity strength and corroboration.** A [strong, corroborated entity](/blog/entity-strength-ai) is what gets a brand recommended across engines, agent or no agent, and it's the layer no single vendor's tool can sell you.
5. **Measure per surface.** Deploying an agent doesn't tell you whether ChatGPT or AI Mode actually surfaces your products; only measurement does. Track each engine as its own line, over time.

> A shopper agent lets your brand speak and sell inside the answer. It does not decide whether the answer includes you. Win the selection layer first, then let the agent close.

The agentic storefront is arriving on every major engine at once, but the brands it lifts will be the ones the engines already choose to surface. Knowing whether AI engines and agents actually find, cite, and recommend your products, as these agents go live, is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## Should you let AI crawlers index your site?
Source: https://heybuffy.com/blog/should-you-let-ai-crawlers-index-your-site

Every brand's `robots.txt` quietly answers a question most marketing teams have never been asked: **are AI engines allowed to read your website?** It's a one-line decision with real consequences for whether ChatGPT, Gemini, Claude, and Perplexity can learn about your brand and cite your pages.

## The bots aren't all doing the same job

It helps to think in terms of what a crawler is *for*. The same company often runs several bots across the AI lifecycle:

- **Training crawlers**: e.g. `GPTBot` (OpenAI), `Google-Extended` (Google), `ClaudeBot` (Anthropic), `CCBot` (Common Crawl). These gather content that may inform future model training. Blocking them means the next generation of models learns *less* about you.
- **Live-retrieval / answer crawlers**: e.g. `OAI-SearchBot` and `ChatGPT-User` (OpenAI), `PerplexityBot` (Perplexity). These fetch pages at answer time to ground and cite a response. Blocking them means you're less likely to be *cited* in live AI answers.
- **Classic search crawlers**: `Googlebot`, `Bingbot`. These index for search, and increasingly feed AI surfaces like Google's [AI Overviews](/glossary/ai-overviews) and AI Mode too. One bot, several jobs.

The nuance: **a single token like `Googlebot` can span training-adjacent, indexing, and AI-answer use**: which is why "just block the AI bots" is rarely as clean as it sounds.

## The real trade-off

Blocking AI crawlers is sometimes defensible, if you're protecting proprietary content, or you simply don't want your writing in training sets. But for a **consumer brand that wants to be discovered**, the calculus usually runs the other way:

- If engines can't crawl you, they fall back to what *others* say about you. Retailers, reviews, competitors, and you lose control of the narrative.
- If retrieval bots can't fetch your pages, you forfeit citations to whoever they *can* read.
- The cost of allowing them is mostly bandwidth; the cost of blocking them is invisibility.

> For most brands, the goal isn't to keep AI out. It's to be the clearest, most-citable source AI can find.

## How to set it, concretely

It's all in `robots.txt`, addressed per user-agent. To welcome everyone (the simplest stance):

```
User-agent: *
Allow: /
```

To allow most but block a specific training bot, add a group for it:

```
User-agent: GPTBot
Disallow: /

User-agent: *
Allow: /
```

A few rules of thumb:

- **Decide per bot, not "AI: on/off."** You might welcome live-retrieval bots (citations) while making a separate call on training bots.
- **Don't accidentally block them.** Many sites disallow AI crawlers by inheriting an old rule or a security plugin's default, then wonder why they're invisible.
- **Allowing access is necessary, not sufficient.** A bot that *can* read a page still needs to be able to *parse* it. Clean, semantic HTML and structured data are what turn access into citations.

## What to do next

Open `yourdomain.com/robots.txt` and read it as an AI engine would: which of the bots above are allowed, and which are silently blocked? If you're a brand that wants to show up in AI answers and you're blocking the crawlers that make that possible, that's the first thing to fix, and the easiest.

Then make sure the pages they *can* reach are actually built to be understood. That's a bigger topic, and exactly what a site-readiness audit, and ongoing monitoring with **Buffy Intel**, are for.

## Why stablecoins are becoming a payment rail for AI agents
Source: https://heybuffy.com/blog/stablecoins-agentic-payments

AI agents are starting to settle payments in [stablecoins](/glossary/stablecoin). Dollar-pegged crypto tokens, and not only on the card rails everyone expected. The reason is narrow and technical: card networks carry a per-transaction fee floor of roughly $0.30, which makes the sub-cent payments a machine makes uneconomic. The 30 June 2026 launch of a broadly-backed dollar stablecoin, **Open USD**, adds infrastructure that agent payments could later ride on, though, importantly, it wasn't pitched as an agent product.

## Why would an AI agent pay with a stablecoin instead of a card?

Because the economics of a card break down at machine scale. A card transaction carries a fixed floor. Around **$0.30**: that is trivial on a $50 order and ruinous on a $0.01 one. Agents don't just buy groceries; they pay other agents, APIs, and data endpoints in tiny, frequent increments a card was never designed to carry.

According to a Keyrock report covered by CoinDesk in May 2026, agent activity on the **x402** micropayment scheme skewed exactly this way: across roughly **176 million** payments, the median transaction was **$0.01-$0.10**, and about **76%** fell below the ~$0.30 card-fee floor. Stablecoin settlement on some blockchains costs a fraction of a cent and clears in seconds, programmatically, without a card's authorisation round-trip. Treat the specific figures as vendor-reported and directional, but the direction is clear.

## How much are AI agents actually paying with crypto today?

Very little, in absolute terms. This is early. The same Keyrock report (via CoinDesk, May 2026) estimated AI agents settled a little over **$73 million** across roughly **176 million** blockchain transactions between May 2025 and April 2026. For scale, that is about **0.0001%** of the reported ~$46 trillion in annual stablecoin settlement volume.

A few more reported data points, all single-source and directional:

- Around **98.6%** of observed machine payments settled in **USDC** (issued by Circle).
- Fireblocks reported roughly **49%** of institutions already use stablecoins for payments, with more piloting.
- Agentic commerce overall is projected at **~$1.5 trillion** globally by 2030 (a forecast, not a measurement).

The honest read: agent-driven stablecoin volume is a rounding error today, but growing off a base of near-zero. A leading indicator, not a settled market. Hedge the numbers; watch the trend.

## What is Open USD, and how does it fit?

Open USD is a US-dollar-backed stablecoin announced on **30 June 2026** by **Open Standard**, an independent company governed by a board of its partners. Per reporting in CoinDesk and American Banker, more than **140** organisations signed on. Including Visa, Mastercard, Stripe, Coinbase, BlackRock, BNY, U.S. Bank, American Express, Google, and Shopify.

What makes it structurally different from existing stablecoins, as reported:

| Feature | Open USD (as reported, 30 Jun 2026) |
|---|---|
| Governance | Independent company; board of participating partners (not a single issuer) |
| Mint / redeem cost | No-cost for businesses |
| Reserve economics | Proceeds shared with partners, minus a management fee (vs. an issuer keeping the interest) |
| Timing | Slated to launch later in 2026 |
| Scale context | Stablecoin market >$300B as of mid-2026; projected ~$4T by 2030 |

**One honest caveat, stated plainly:** the primary coverage of Open USD made *no* mention of AI agents or agentic commerce. It is general money-movement infrastructure. The reason it belongs in this discussion is indirect but real. The same payment giants backing it are the ones building agent-payment rails, so a fee-free, broadly-backed dollar stablecoin is the kind of plumbing agent payments could later settle on. That's an inference about direction, not a claim about intent.

## Which standards let agents pay autonomously?

Several competing ones, none yet dominant. The point-in-time picture as of mid-2026:

- **x402**: a micropayment scheme built on the long-dormant HTTP `402 Payment Required` status, aimed at pay-per-call machine payments; the source of much of the agent data above.
- **AP2** (Agent Payments Protocol). Google's framework for letting agents pay with guardrails and mandates; reported to explicitly support stablecoins alongside cards.
- **Agent Pay for Machines**: a Mastercard capability announced in June 2026 for always-on machine payments, extending its tokenisation backbone.

These schemes have not converged, and which rails capture agent volume is still open. The durable takeaway is the *pattern*: agent payments are being wired with scoped authority, machine-speed settlement, and a choice of rail, not any single winning standard.

> Stablecoins are becoming a way for agents to move money at machine speed and machine cost. They don't make your product the one the agent decides to buy, that's still earned upstream.

## Where does this leave a brand?

Where the [card-rail story](/blog/agentic-commerce-payment-rails) left it: the payment layer is **settlement, not selection**. Whether an agent pays with a tokenised card or a stablecoin, the rail moves money *after* the agent has already chosen a product. It does nothing to make yours the one chosen.

That choice still turns on the layer above the rails. Catalog richness, [entity strength](/blog/entity-strength-ai), reviews, and how consistently other sources corroborate your claims. It's the same [answer-engine optimisation](/glossary/answer-engine-optimization) that decides whether an agent surfaces you at all, and it sits on top of the shared [commerce protocols](/glossary/agentic-commerce-protocol) that expose your catalog to agents in the first place.

So treat the stablecoin news as confirmation that the transaction layer is maturing on more than one rail, then spend your effort where selection is won. Knowing whether AI agents and answer engines actually surface and pick your products, as these rails mature, is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## Stripe's Agentic Commerce Suite: what the new payments layer means for brands
Source: https://heybuffy.com/blog/stripe-agentic-commerce-suite

If [agentic commerce](/blog/what-is-agentic-commerce) is shoppers letting AI agents discover and buy on their behalf, **Stripe's Agentic Commerce Suite (ACS)** is one of the first attempts to package the whole transaction. Discovery, checkout, fraud, and payments. Into a single seller integration.

## What Stripe's Agentic Commerce Suite is

ACS is a **single integration that lets a business sell through AI agents**. Per Stripe's seller documentation, it makes your products discoverable to agents and lets you accept agentic payments "across multiple commerce protocols," while minimising changes to your existing commerce stack. Stripe describes it as available to US businesses as of mid-2026, with some capabilities still in private preview.

In plain terms: instead of integrating separately with every shopping agent, you publish one catalog and configure checkout once, and ACS distributes that to the agents you enable. It spans four jobs Stripe groups under the transaction lifecycle: **discovery, checkout, fraud, and agentic payments**.

## How a seller feeds it

Agents recommend from data, not from your hero imagery, so the catalog feed is the foundation. Stripe's documentation describes three feeds on different cadences:

| Feed | Refresh cadence (per Stripe docs) | What it carries |
|---|---|---|
| **Product data** | About once a day | Titles, descriptions, images, categories, attributes |
| **Inventory** | About every 15 minutes | Stock levels, so agents don't show out-of-stock items |
| **Pricing** | About every 15 minutes | Prices, so the quoted price matches checkout |

Feeds can be uploaded by CSV, API, or SFTP, with platform and syndication-partner connectors described as coming. Stripe notes uploads are processed asynchronously and not guaranteed in submission order, and warns that stale inventory or pricing is a leading cause of failed agentic checkouts. Cadences and limits are point-in-time; treat them as a moving target.

## How checkout and payment work

ACS provides agents a **delegated checkout** that renders inside the agent's surface, but the **seller stays the merchant of record**: keeping control of shipping, tax, fulfilment, and which payment methods appear. Underneath sits a payments primitive Stripe calls the **Shared Payment Token (SPT)**: the agent collects payment details, but the seller, not the agent. Processes the charge, and the token can be scoped to a specific seller, amount, and time window. Stripe says it has not seen a material rise in fraud on agentic channels so far, partly because humans remain in the loop.

## The one thing it does not do

Here's the distinction that matters for brands, and it's easy to miss in the launch noise:

> Stripe's Agentic Commerce Suite is the *rails*. It puts you on the shelf and handles the sale. It does not decide *which* product the agent recommends in the first place.

ACS solves distribution and payment. It does not solve **selection**. When a shopper asks an agent "find me a waterproof jacket under ₹5,000," the agent still has to choose *whose* jacket to surface, and that choice turns on the richness of your product data, your [entity strength](/blog/entity-strength-ai), reviews, and how consistently other sources corroborate what you say about yourself. That is [answer-engine optimisation](/glossary/answer-engine-optimization), and it sits *on top of* the rails, not inside them.

The stack is crystallising into three layers, and it helps to know which one any given announcement is about:

| Layer | Examples | What it decides |
|---|---|---|
| **Protocols** | Agentic Commerce Protocol (ACP), Google's Universal Commerce Protocol (UCP) | The shared language for agents and merchants to transact |
| **Distribution & payments** | Stripe Agentic Commerce Suite, commerce platforms | How your catalog reaches agents and how the money moves |
| **Your catalog & reputation** | Product data, structured attributes, reviews, corroboration | *Whether the agent picks you* |

The [Agentic Commerce Protocol](/blog/agentic-commerce-protocol-acp), which Stripe co-authored with OpenAI, lives in the top row; ACS is Stripe's implementation in the middle row and is positioned to bridge multiple protocols over time. But spend on the rails without fixing the bottom row and you've built a fast checkout for a product no agent chooses to surface.

## What to do about it

Getting on a rails like ACS is necessary, not sufficient. The durable work is the same [catalog-readiness](/blog/agentic-commerce-readiness) groundwork that lifts ordinary AI visibility:

- **Make products discoverable**: crawlable pages, clean URLs, structured feeds.
- **Make the data complete**: full attributes, specs, [structured data](/glossary/structured-data), accurate taxonomy, not just a marketing paragraph. (See [preparing your catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents).)
- **Earn corroboration**: reviews and third-party mentions that agree with your own claims, so the agent trusts you enough to recommend you.

Adopt the rails when they reach your market; in the meantime, win the layer that decides selection. Knowing whether agents and answer engines are actually choosing your products, and tracking it as this stack shifts. Is exactly what **Buffy Intel** measures.

## How to structure a page into chunks AI can extract and cite
Source: https://heybuffy.com/blog/structure-content-into-extractable-chunks

**To make a page citable by AI, structure it as a set of self-contained chunks, each a single section that answers one question in an answer-first form an engine can lift without the rest of the page.** AI engines retrieve and cite at the passage level, so the unit of optimisation is the [chunk](/glossary/content-chunk), not the page. This is the practical companion to the finding that [content length is not the lever, coverage and extractability are](/blog/does-content-length-affect-ai-citations).

Work through the steps in order on your highest-value pages. The goal is a page where every real sub-question has its own clean, liftable answer.

## Step 1: Map the sub-questions the query fans into

AI answers are assembled through [query fan-out](/glossary/query-fan-out): one question becomes many sub-queries, each answered from a different passage. So start by listing the branches your topic fans into, not just the headline query.

- Write the core question, then its predictable branches: definitions, comparisons, specs, steps, troubleshooting, cost, and who-it's-for.
- Each branch you cover completely is a separate chance to be cited. Each one you skip is a citation that goes to a competitor.
- Turn each branch into one section. One question per chunk is the structural spine of the whole page.

## Step 2: Lead every section with the direct answer

Open each section with the answer in about **40–60 words**, then explain underneath. Never bury the answer mid-paragraph, an engine scoring passages keeps the ones where the answer is clean and up front.

- Sentence one states the answer plainly; the rest of the chunk supports it.
- Write the first two sentences so they could stand alone if lifted into an AI response, because they may be.
- This mirrors how a [featured snippet](/glossary/featured-snippet) is chosen, and the same answer-first passage often serves both classic and AI surfaces.

## Step 3: Keep each chunk self-contained and tight

A chunk should answer its question without depending on the paragraphs around it. Aim for roughly **100–300 words** per section, and state any scope up front.

- Open with conditions when they matter: "This assumes you already return HTTP 200 to AI crawlers."
- Don't reference "as we said above", a lifted chunk loses that context. Repeat the one fact it needs.
- If a section goes past ~300 words, it is usually answering two questions. Split it into two chunks.

## Step 4: Put facts in tables and lists, not prose

Specs, steps, comparisons, and criteria are extracted far more cleanly from tables and lists than from narrative. Different fan-out branches prefer different formats, so exposing the same facts structurally widens what an engine can lift.

- Use a table for anything with rows and columns: comparisons, criteria, specs, pricing tiers.
- Use numbered lists for sequences and bulleted lists for sets.
- End a table or list with a one-line summary tying it back to the point, so the takeaway travels with the data.

## Step 5: Use question-style H2s that match how people ask

Phrase each heading as the actual question its chunk answers ("How much does X cost?"), not a vague label ("Pricing"). Question headings help an engine match your chunk to a sub-query and make the page's structure legible.

- Mirror the natural language of the query, including the question word.
- Keep headings specific and self-explanatory, so the table of contents reads as a list of answered questions.
- Add [descriptive internal links](/glossary/retrievability) to related pieces and glossary terms so the chunk sits inside a topical cluster.

## Step 6: Stop padding, then measure per engine

Length is a byproduct of coverage, never a target. Add a section only when it answers a new question, and cut anything that repeats without adding a fact, keyword padding tested about 10% *worse* in the Princeton GEO experiment.

- Remove sentences that restate the target phrase without new evidence.
- After restructuring, track your [citation coverage](/glossary/citation-coverage) on each engine separately, and revisit high-value pages before they go stale.
- The benchmark percentages are not promises for your niche; your own measured citation share is the only scoreboard that counts.

> Cut the page into one self-contained, answer-first chunk per real question. That structure, not word count, is what lets an engine lift and cite you.

Structuring is only half the job; the chunks also need [evidence density, specific statistics, named quotes, and cited sources](/blog/add-citation-lifting-elements) so each one is worth lifting. Do both, and confirm the page is reachable and server-rendered first, because a chunk an AI crawler can't fetch can't be cited.

Doing this across a site is repetitive work whose payoff only shows up in citation share. That is where **Buffy Intel** fits: it snapshots whether AI engines cite and recommend your brand over time, so after you restructure a page into extractable chunks you can watch whether the change actually lifted your citations, engine by engine, rather than assuming it did.

## How to test whether a change actually moved your AI citations
Source: https://heybuffy.com/blog/test-if-a-change-moved-your-ai-citations

You can't know whether adding schema, refreshing a page, or rewriting an intro moved your AI citations from a single before-and-after, because citations drift on their own. To test it honestly, treat the change like a controlled experiment: **isolate one variable, baseline it, hold out a comparable control set, wait out the [crawl-to-cite lag](/blog/chatgpt-citation-lag), then read the delta against the control, not against zero.** This is the single-site version of the method behind large studies like the [controlled schema experiment](/blog/does-schema-markup-improve-ai-citations), and it's how you avoid mistaking [correlation for causation](/glossary/correlation-vs-causation).

This is the hands-on companion to that reference; read it for the finding, this for the method. Below is the test in six steps.

## Step 1: Isolate one change and write the hypothesis

You can only attribute an effect to a change you can name. Before touching anything, write one sentence: "adding `Product` schema to these 40 product pages will increase their [citations](/glossary/citation) on ChatGPT within six weeks." One variable, one page-set, one engine, one window.

The discipline is to change *one* thing. If you add schema *and* rewrite the copy *and* add FAQs in the same week, any movement is unattributable, you'll never know which edit did it. Stagger changes, or accept that you're testing the bundle, not the schema.

## Step 2: Baseline before you touch anything

A test needs a starting line. For the target pages and prompts, record where you stand now: which prompts you're cited in, on which engines, and how often, ideally as an average over a couple of weeks so a single volatile reading doesn't become your baseline. This is ordinary [AI-visibility measurement](/blog/how-to-measure-ai-visibility), captured deliberately before the change rather than reconstructed after.

Capture the raw detail, not just a score: the specific prompts, the engine, and whether you were cited or merely mentioned. You'll need that granularity in Step 5 to tell a real effect from a reshuffle.

## Step 3: Hold out a control set

This is the step that separates a real test from a guess. Pick a set of comparable pages, similar topic, similar current citation level, and *don't* change them. They're your control. Both groups live through the same engine updates, the same season, the same competitor moves, so whatever happens to the control is the background drift you must subtract.

- **Treated group:** the pages you change.
- **Control group:** similar pages you deliberately leave alone.
- **The signal:** how much the treated group moves *beyond* the control, not how much it moves in absolute terms.

Without a control, a rise that's really just an ecosystem-wide good week gets miscredited to your change, the exact trap a naive before-and-after falls into.

> The question is never "did citations go up after I made the change?" It's "did the pages I changed move more than the near-identical pages I didn't?" The control is what turns a story into evidence.

## Step 4: Wait out the crawl-to-cite lag

Give the change time to propagate. A page must be recrawled, reprocessed, and then selected at answer time, so effects show up in weeks, not days. Reading the result on day three mostly measures [answer volatility](/glossary/answer-volatility), not your edit.

Watch a smoothed trend over several weeks rather than any single snapshot. Heavy crawler activity with no citation movement yet is normal and expected, crawl volume tends to rise before citations do, so don't call the test dead in week two. Set the judging date in advance so you're not tempted to stop the moment the line ticks the way you hoped.

## Step 5: Read the delta honestly, and rule out confounders

Now compare. Did the treated group's citations rise *relative to the control* over the window? Before you conclude "yes," rule out the usual confounders:

- **Other changes:** did anything else ship to the treated pages, a template update, an internal-linking change, a [freshness](/blog/content-freshness-citation-cliff) bump, in the same window?
- **Composition:** are you counting citations, or has a mention simply been reclassified? Keep the two apart.
- **Sample size:** on a handful of pages, a two-citation swing is noise. Read the pattern across many prompts and pages, not one URL.
- **Direction of cause:** if the change and the citations both reflect a third factor (you refreshed your *best* pages), you've found a correlation, not a cause.

A move that survives all four is a credible, site-specific result. One that doesn't is a lead to investigate, not a conclusion to ship.

## Step 6: Decide, and size the claim to the evidence

Turn the result into a right-sized decision. If the treated group beat the control convincingly, roll the change out and keep watching. If it didn't, stop spending on that change, this is precisely how the [schema study's null result](/blog/does-schema-markup-improve-ai-citations) should redirect effort toward the levers that do move citations. Either way, state the claim at the confidence your sample supports: "on our site, for these pages, over six weeks" is honest; "schema works" from forty pages is not.

Testing changes this way, one variable, against a control, over a real window, is how you learn what actually moves *your* citations instead of copying tactics that were only ever correlations. Sustaining that measurement continuously, across every engine and over time, is exactly what **Buffy Intel** is built to do. Change one thing; prove it moved you. Questions: support@flash.tech.

## How to vet an AI-visibility measurement provider
Source: https://heybuffy.com/blog/vet-ai-visibility-measurement-provider

**To vet an AI-visibility measurement provider, judge the method, not the dashboard — because you cannot check an AI answer against a "correct" one, only check how the provider produced its number.** The IAB's August 2026 framework, *Measuring Visibility in the AI Era*, turns that into a concrete disclosure checklist. This walks through six questions to ask any vendor before you buy, each tied to a specific thing the framework says a provider should be able to tell you.

Two tools can report different [share-of-voice](/glossary/share-of-voice) figures for the same brand in the same category, and both can be internally consistent — the divergence lives in method. The framework's governing rule is worth keeping in front of you the whole way through: **where a provider cannot or will not disclose a required item, that absence is itself the answer.** This checklist is neutral; it applies to every tool, [Buffy Intel](/blog/how-to-measure-ai-visibility) included.

## The six questions at a glance

| # | Ask the provider | What a good answer looks like |
|---|---|---|
| 1 | Which platforms and model versions do you cover? | Named engines + model versions; a substantial majority of consumer AI traffic |
| 2 | How many queries, and how often? | Large, category-plus-subcategory set; 50+ minimum; weekly for decision-grade |
| 3 | How is your prompt library built and sourced? | Disclosed intent mix; grounded in real search data, not only synthetic |
| 4 | How do you sample each query? | Many responses per query, reported as a range — not a single response |
| 5 | How do you handle hallucinations and errors? | Detected, reported per platform, surfaced — never silently filtered |
| 6 | How do you manage baselines when a model updates? | Documented re-baselining; platform-driven shifts separated from real ones |

## 1. Which AI platforms and model versions do you cover?

Start here, because coverage caps everything else. A tool that watches only one engine sees a fraction of the picture, since engines cite and recommend [very different pages](/blog/ai-mode-vs-ai-overviews-citations). The framework's decision-grade bar is coverage of platforms that collectively represent a substantial majority of consumer AI traffic in your market — with per-platform results shown, not blended into one figure that hides the divergence. Ask for **model-version specificity** too: "ChatGPT" is not an answer; the underlying model changes behaviour.

## 2. How many queries do you issue, and how often?

Volume and cadence are the clearest directional-vs-decision-grade line. The framework treats **fewer than 50 queries** as exploratory — not even directional — and wants a large, diverse set with subcategory coverage (an "office chairs" program should also probe "ergonomic office chairs" and "office chairs for back pain"). On cadence: monthly or quarterly sampling is fine for trend-watching; weekly or more frequent is expected before you move budget on the data. Match the cadence to the decision — measuring weekly for a quarterly decision just buys you noise.

## 3. How is your prompt library built and sourced?

This is the most consequential choice a provider makes and the least visible to buyers. A query set heavy on "best X" recommendation prompts flatters brands that do well in recommendations and understates them everywhere else. Ask the provider to disclose its **intent-type mix** across the four types the framework names — informational ("what is X"), comparison ("X vs Y"), recommendation ("best X for Y"), and transactional ("where to buy X") — and whether queries are grounded in real consumer search data or generated synthetically. As the framework warns, strong reproducibility on a badly built prompt library just gives you "precise answers to the wrong questions."

## 4. How do you sample each query — once, or many times?

This is the question that separates real measurement from a screenshot. Because AI answers are [non-deterministic](/glossary/answer-volatility), the same query issued twice returns different brands, sources, and framing. The framework's line is that **"single-response measurement is not measurement"** — a brand's visibility on a query is a distribution, not a value. A credible provider samples each query multiple times and reports a *range* with a stated variability, so you can tell a real four-point move from ordinary jitter.

> A four-point change in share of voice is only meaningful if it is larger than the variation you'd see from re-issuing the same queries against the same platforms on the same day. Without a variability baseline, trend interpretation is guesswork.

## 5. How do you handle hallucinated and factually inaccurate mentions?

An AI answer can invent an association your brand has no connection to, or attach the wrong price or spec to a real mention. Both distort your metrics and carry brand-safety risk. The framework requires providers to **detect both, report them per platform, and surface flagged mentions to you rather than silently excluding them** — because you have a legitimate interest in knowing when and how AI misrepresents you. Treat the absence of any documented [hallucination](/glossary/ai-hallucination)-detection method as a material gap in a quality claim, not a rounding error.

## 6. How do you manage baselines when a model changes?

A model update can move your [share of voice](/blog/ai-share-of-voice-volatility) several points overnight with no change to your brand at all. The distinguishing skill of a serious program is telling a **platform-driven** shift (it appears across many brands or the whole category on one engine) from a **market-driven** one (isolated to your brand or specific query types). Ask how the provider documents re-baselining events — when one happened, what triggered it, and whether it reports pre- and post-update data as separate series rather than stitching them into one misleading trend line.

## Match the disclosure tier to the decision

The framework's closing move is a two-tier disclosure model: **minimum** disclosure (platform coverage, collection architecture, summary-level prompt-library and attribution logic) is enough to place a tool's output in context for directional use; **enhanced** disclosure (full query sourcing, prompt-library detail, panel validity, factual-accuracy classification, historical versioning) is what you should expect from anything positioned as decision-grade. A provider's willingness to give enhanced disclosure is itself a signal of methodological confidence.

Buffy Intel is built to answer these six questions out of the box — multi-engine coverage, hundreds of prompts sampled repeatedly, results reported as trends with their variability, and hallucinated or wrong mentions flagged rather than hidden. [See how Buffy Intel measures AI visibility](/blog/how-to-measure-ai-visibility), then hold us to the same checklist you'd hold anyone.

## WebMCP vs UCP: two paths to agentic commerce
Source: https://heybuffy.com/blog/webmcp-vs-ucp

If [agentic commerce](/blog/what-is-agentic-commerce) is the shift to AI agents buying on a shopper's behalf, **WebMCP** and **UCP** are two of the standards racing to make the "buying" part work, and they make opposite bets about *who runs the agent*. WebMCP assumes every shopper brings their own agent; UCP assumes most shoppers borrow a third-party one. Both are Google-backed, both are early, and a brand can prepare for both at once.

## What are WebMCP and UCP?

**WebMCP**: the Web Model Context Protocol. Is a proposed open web standard, introduced by Google at I/O 2026, that lets a website expose structured tools (JavaScript functions and HTML forms) to browser-based AI agents. Instead of an agent guessing its way through your interface by clicking, it calls machine-readable functions to complete a task. An experimental origin trial begins in **Chrome 149**, and Gemini in Chrome is set to support WebMCP APIs (all as of mid-2026, and still experimental).

**UCP**: the Universal Commerce Protocol. Is Google's standard for connecting merchants to its shopping surfaces (Search, Gemini, YouTube, Gmail) through a shared **Universal Cart**. A shopper can add items from any surface; the merchant stays the merchant of record and can offer native or embedded checkout. Google reported launch partners across major retailers, with a US rollout beginning in summer 2026.

## How do they differ?

The two standards overlap in goal. Let agents transact, but split on architecture:

| Dimension | WebMCP | UCP (Universal Commerce Protocol) |
|---|---|---|
| What it is | Proposed open web standard for exposing site actions as agent tools | Google's protocol + Universal Cart for its shopping surfaces |
| Whose agent acts | The shopper's **own** browser agent (e.g. Gemini in Chrome) | A **third-party** shopping agent / Google's surfaces |
| Underlying model | Decentralised. Every user brings their own agent | Centralised. Shoppers use a few large agents |
| What the brand exposes | Machine-readable tools (JS functions, HTML forms) | Catalog + checkout integration; a shared cart |
| Where checkout happens | On your own site, driven by the agent | In Google's surface or embedded; merchant of record retained |
| Status (mid-2026) | Experimental origin trial from Chrome 149 | US rollout from summer 2026 |

In short: WebMCP turns *your site* into something an agent can operate; UCP turns *Google's surfaces* into a place your catalog can be bought from.

## Decentralised vs centralised: why the distinction matters

The cleanest way to read the two is **"bring your own agent" (BYOA) versus "borrow an agent."** WebMCP is built for a decentralised future where every shopper has a personal agent that acts on sites directly. UCP is built for the centralised reality forming now, where a handful of large assistants and shopping surfaces broker the transaction.

That isn't a winner-take-all fight; it's two futures arriving on different timelines. The centralised model is shipping first because the big surfaces already have the users. The decentralised model depends on personal agents becoming common, which the Chrome origin trial is an early step toward.

> WebMCP bets that every shopper will bring their own agent; UCP bets that most shoppers will borrow someone else's. Brands that prepare for both stop having to guess which bet pays off.

## Where they sit in the agentic stack

It helps to place both in the four layers AI commerce moves through. **Train, index, inference, transact.** Training and indexing decide whether a model knows and can retrieve you; inference is the moment an agent reasons over options and shortlists. WebMCP and UCP are both **transact-layer** plays: they govern what happens *after* an agent has decided to buy, standardising how the purchase completes.

That puts them alongside the [Agentic Commerce Protocol (ACP)](/blog/agentic-commerce-protocol-acp) and [Stripe's Agentic Commerce Suite](/blog/stripe-agentic-commerce-suite). Different implementations of the same "let agents act and pay" movement. The names and details will keep shifting; the direction won't.

## What both ask of your brand

Here's the reassuring part: the groundwork is shared. Whether a shopper's own agent calls your WebMCP tools or a third-party agent buys through UCP, it acts on the same underlying asset. A complete, [structured](/glossary/structured-data), truthful catalog with machine-readable actions, clear entity signals, and corroboration across the web.

- **Make products discoverable and parseable**: crawlable, server-rendered pages with clean attributes (the same work in [preparing your catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents)).
- **Expose actions, not just content**: labelled forms and clear interactive elements are what a WebMCP tool definition wraps.
- **Earn the selection**: being transactable doesn't make you *chosen*. That still turns on catalog richness, [entity strength](/blog/entity-strength-ai), reviews, and [answer-engine optimisation](/glossary/answer-engine-optimization) sitting on top of the rails.

Adopt each standard when it reaches your market and surfaces. In the meantime, the durable move is the [readiness work](/blog/agentic-commerce-readiness) that feeds every protocol at once. Tracking whether agents and answer engines actually surface and choose your products, as this stack keeps shifting. Is exactly what **Buffy Intel** watches.

## Your website is becoming something AI talks to, not just reads
Source: https://heybuffy.com/blog/websites-as-agent-endpoints

Your website is quietly becoming a surface AI agents *act on*, not just a page humans read. A 2026 platform report logged about 102 million Model Context Protocol sessions in a single year. Early but real evidence that AI-to-website interaction is turning into routine infrastructure. The durable shift: a site now has two audiences, the human visitor and the AI agent, and the work of being legible to both is increasingly the same work.

The data here comes from Wix's 2026 State of Websites report, drawn from its base of about 310 million users. A single-vendor dataset, so the figures describe one platform's customers, not the whole web. Read them as directional.

## What did the MCP-adoption data actually show?

It showed AI managing websites at meaningful scale. MCP. The Model Context Protocol, an open standard that lets AI assistants connect to external tools and data through a consistent interface. Moved from novelty to routine on Wix in 2025:

| Metric | Figure | What it measures |
|---|---|---|
| Total Wix MCP sessions in 2025 | ~102 million | AI assistants connecting to Wix sites |
| Users connecting external AI tools to their site | ~32,000 | Site owners wiring up an AI like Claude |
| Sample | ~310 million Wix users | Scope of the report (single platform) |

Wix describes site owners using MCP to create and update content, search documentation, and debug issues, and external assistants like Claude managing a site "through natural conversation." Be precise about what this is: **most of these sessions are owners using AI to manage their own sites, not consumer shopping agents transacting on them.** That distinction matters, because it's tempting to read 102 million sessions as "agents are buying". They aren't, yet. What the number does signal is that the plumbing for AI-to-website interaction is being laid, fast.

## Why does this matter for AI visibility?

Because it confirms the direction every agentic protocol is pointing: the website is becoming a two-sided interface. For years a page had one job. Be read by a human (and, lately, crawled by an AI). Now a second job is emerging: be *callable* by an agent that wants to do something. Answer a question, pull a spec, start a cart.

> A website used to be a destination you sent people to. It's becoming an endpoint that machines query, and the brands that win will be legible to both at once.

This is the same theme as [making your website agent-readable](/blog/make-your-website-agent-readable), now showing up in usage data rather than guidance. It also sits alongside the consumer-side [agentic commerce](/glossary/agentic-commerce) protocols we've covered: [WebMCP vs UCP](/blog/webmcp-vs-ucp) on how browser agents and commerce agents reach a site, and [Microsoft's Web IQ](/blog/what-is-microsoft-web-iq) on grounding agents in live web data. The Wix figures are the owner-side mirror of that consumer-side shift. Both say the same thing: AI is becoming an active party in how websites are built, read, and acted on.

## What does the data *not* tell you?

It doesn't tell you that you need a separate "AI version" of your site, and it doesn't tell you consumer agents are transacting at scale yet. Two honest limits:

- **It's owner-side, not shopper-side.** The MCP sessions are largely people managing their own sites with AI. Useful as a signal of momentum, not proof that buying agents have arrived.
- **It's single-vendor.** The figures come from one platform's customers. They show a trend on Wix; they don't quantify the open web.

The trap to avoid is over-reacting by building a stripped-down machine mirror of your site. A move we've argued against in [whether you need a separate AI version of your website](/blog/separate-ai-version-of-your-website). A divergent mirror risks cloaking and drift. The better response is to make your *real* site legible to machines, not to build a second one.

## How should a brand get ready?

Invest in the fundamentals that serve both audiences, and watch the protocol layer without betting the roadmap on it:

- **Server-rendered, semantic HTML.** If a fact only appears after JavaScript executes, an agent may never see it. Expose it in the markup.
- **Clean [structured data](/glossary/structured-data).** Schema labels what things are so an agent doesn't have to guess; it's the cheapest agent-legibility win available.
- **Reachable by AI bots.** Confirm your [CDN isn't blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers) and that your pages are in the sitemap and internally linked.
- **Stay informed on protocols, experiment lightly.** WebMCP, UCP, and MCP are moving fast; track them and pilot, but don't pour budget into one standard while they're still settling. The same caution applies to [llms.txt](/blog/is-llms-txt-worth-it). A control you fully own is a weak signal.

The fundamentals are durable; the protocols are volatile. Do the legibility work now, because it pays off whether an agent reaches your site through search, a browser assistant, or a commerce protocol. Knowing whether AI agents and answer engines actually reach, read, and recommend your site. Across every one of those paths. Is exactly what **Buffy Intel** tracks. Questions: support@flash.tech.

## The 1-hour weekly AI-visibility routine for lean D2C teams
Source: https://heybuffy.com/blog/weekly-ai-visibility-routine

You do not need a dedicated GEO team to stay visible in AI answers. A lean D2C brand can hold its ground with a **repeatable one-hour weekly routine**: check access, snapshot a fixed set of prompts, triage the gaps, and ship one fix. The discipline matters more than the depth. AI answers shift constantly, so a steady weekly read catches regressions while they're still cheap to fix.

## Why weekly, and why time-boxed?

AI visibility is non-deterministic and fast-moving: the same prompt yields different answers across attempts and days, citations [decay after roughly a quarter](/blog/content-freshness-citation-cliff), and a single CDN rule change can drop you out of every engine overnight. A quarterly deep audit misses all of that. A short, consistent weekly cadence turns visibility into a trend you can act on, and keeps the work small enough that a busy team actually does it.

> The goal of the hour isn't to fix everything. It's to *notice* everything, fast, and queue the one fix that matters most this week.

## The hour, step by step

Keep the same fixed inputs each week (same prompts, same pages, same engines) so you're reading a trend, not noise.

| Minutes | Step | What you do |
|---|---|---|
| 0-10 | Gate check | Fetch key pages as AI crawler user-agents; confirm HTTP 200 |
| 10-35 | Prompt snapshot | Ask your 10 fixed prompts across the major engines; log presence + citation |
| 35-50 | Gap triage | Sort gaps into the two lenses (not named vs not cited) |
| 50-60 | One fix | Queue the single highest-leverage fix; note it for the week |

### 0-10 min: Gate check

Confirm AI engines can actually reach you. Fetch three or four key pages as `GPTBot`, `ClaudeBot`, `PerplexityBot`, and `OAI-SearchBot` and expect HTTP 200, not a 403. A [silent CDN block](/blog/is-your-cdn-blocking-ai-crawlers) is the most common reason a brand is never cited and never shows in analytics. The [crawler directory](/blog/ai-crawler-user-agent-directory) lists the tokens.

### 10-35 min: Prompt snapshot

Ask the same **ten** prompts across the engines your customers use ([ChatGPT](/blog/how-to-get-recommended-in-chatgpt), [Gemini](/blog/how-to-get-cited-in-gemini), [Perplexity](/blog/how-to-get-cited-in-perplexity), [Claude](/blog/how-to-get-cited-in-claude)). For each, log two things: are you **named** (presence), and is **your page cited** as a source ([citation coverage](/glossary/citation-coverage)). Don't agonise over the wording each week. [Pick the ten that matter](/blog/how-to-choose-prompts-to-track) and keep them stable.

### 35-50 min: Gap triage

Sort every gap into one of two lenses, because they need different fixes:

- **Not named (a demand-side gap).** The engine doesn't recommend you. Usually an entity or corroboration problem. You need [earned coverage](/blog/get-into-ai-cited-best-lists) and a stronger entity.
- **Cited but not recommended, or not cited at all (a supply-side gap).** Your pages aren't being lifted. Usually access, extractability, or freshness. The [two-lens audit](/blog/brand-mention-gap-vs-source-gap) covers this split in depth.

### 50-60 min: One fix

Queue the **single** highest-leverage fix this snapshot revealed. A CDN rule to loosen, a page to rewrite answer-first, a stale page to refresh, a roundup to pitch. One real fix a week compounds; a 30-item backlog you never start does not.

## What to track week over week

Five lightweight numbers, logged in a sheet, are enough to see direction:

- **Presence rate**: share of your ten prompts where you're named.
- **Citation coverage**: share where your own page is the source.
- **[Share of voice](/glossary/share-of-voice)**: you vs your top competitor across the set.
- **Gate status**: pass/fail on the crawler check.
- **Fix shipped**: the one thing you changed this week.

If you later want the full picture. [From clicks to citations](/blog/from-clicks-to-citations) and a proper [reporting stack](/blog/ai-visibility-reporting-stack). The weekly sheet is the on-ramp. For [D2C teams in India specifically](/blog/ai-shopping-in-india), the same routine applies; just phrase prompts the way your customers actually ask.

## What to do next

Block a recurring hour on the calendar this week and perform the gate check first. It's ten minutes and the most common silent failure. Doing this by hand across hundreds of prompts, every engine, every day, turned into a trend and a prioritised fix list, is exactly the job **Buffy Intel** automates, but the weekly hour is how a lean team starts before that.

## Which content changes actually increase AI citations? The Princeton GEO experiments
Source: https://heybuffy.com/blog/what-content-changes-lift-ai-citations

**Adding statistics, quotations, and citations to credible sources are the content changes that most reliably increase how often an AI answer pulls from your page, lifting visibility by up to about 40% in the foundational GEO experiment, while keyword stuffing made a page roughly 10% *less* visible.** That finding comes from ["GEO: Generative Engine Optimization"](/blog/what-is-geo-aeo), a 2024 study by Princeton University researchers (Aggarwal and colleagues, arXiv 2311.09735) that tested nine content edits against a simulated answer engine across 10,000 queries.

It is the closest thing [generative engine optimization](/glossary/generative-engine-optimization) has to a controlled experiment, so it is worth reading directly. The numbers below are relative gains inside a benchmark, not live-engine guarantees, and we flag the caveats plainly. But the ranking of what works, evidence over repetition, has held up.

## What did the Princeton GEO study test?

The researchers built **GEO-bench**, a benchmark of **10,000 queries across 9 datasets and 7 domains**, and simulated a two-stage generative engine: a search step retrieved the top five sources for a query, then GPT-3.5-turbo synthesised an answer that cited them. They then applied nine content edits to a source, one at a time, and measured whether the edited page showed up more prominently in the synthesised answer.

Two custom metrics carried the measurement, and both matter because a raw citation count misses *how much* of your content the answer actually used:

- **Position-Adjusted Word Count** — how much of your source's wording appears in the answer, weighted by how prominently it is cited. It rewards being quoted at length and early, not just linked.
- **Subjective Impression** — a model-rated score of how relevant, influential, and prominent your source feels within the answer, closer to how a reader would judge whose voice dominated.

The setup is a laboratory, not the live web. That is a strength for isolating *cause* and a limit for reading the exact magnitudes, and we return to it below.

## Which changes lifted AI visibility the most?

The evidence-adding edits won; the repetition-based ones lost. Here are the load-bearing results, all relative to an unedited baseline and all from the Princeton paper:

| Content edit | Reported effect on visibility | Read as |
|---|---|---|
| **Add statistics** (specific numbers) | ~+41% Position-Adjusted Word Count; ~+37% Subjective Impression | Strongest single edit |
| **Cite sources** (link authoritative references) | Up to ~+115% for a source ranked 5th | Biggest equalizer for lower-ranked pages |
| **Add quotations** (from credible sources) | ~+28% Subjective Impression | Strong, especially on perceived authority |
| **Fluency optimization** (clearer writing) + statistics | Beat every single method by ~5.5%+ | Combine, don't pick one |
| **Authoritative / easy-to-understand language** | Positive, smaller | Supporting edits |
| **Keyword stuffing** | ~10% *worse* than baseline | Actively harmful |

The one-line summary: **making your claims specific, quoted, and sourced is what moved the needle; padding the page with the target phrase moved it backwards.** Across methods and domains, targeted edits produced roughly **22–41%** improvements. The step-by-step way to apply them is in the companion how-to, [how to add the elements that lift AI citations](/blog/add-citation-lifting-elements).

## Why do these specific changes work?

Because a generative engine builds an answer by lifting and recombining passages, and it favours passages that are **self-contained, verifiable, and easy to attribute.** A specific statistic ("cut onboarding to under five minutes") is a clean, liftable unit; a vague claim ("streamlines onboarding") is not. A [citation](/glossary/citation) to a credible source and a named quotation both add [corroboration](/glossary/corroboration), the signal engines lean on to decide a passage is safe to repeat.

That also explains why keyword stuffing backfired. The engine is not counting how often you say the phrase; it is scoring whether your passage is the best evidence for the sub-question. Repetition adds no evidence and reads as low-quality, so it can push you *down*. This lines up with the broader finding that [AI search can't be reliably gamed](/blog/can-ai-search-be-manipulated) by manipulation tactics, and with our own guidance to [grow AI visibility without spam](/blog/grow-ai-visibility-without-spam).

> The changes that make an AI answer pull from your page are the same ones that make a human trust it: a specific number, a named source, a clean quotable line. Repetition is not one of them.

## How much should you trust these numbers?

Enough to act on the *ranking* of methods, not enough to quote the exact percentages as if they came from ChatGPT today. The honest limits, several of which the authors and later critics flag:

- **Simulated, not live.** The engine was GPT-3.5-turbo synthesising Google's top-5 in 2023. Today's engines use newer models, [fan a query out](/glossary/query-fan-out) into many sub-queries, and pull from far more than five sources.
- **A zero-sum, five-source arena.** With only five competing sources per query, a gain for one is a loss for another, which **amplifies relative percentages**. Real niches with hundreds of competing pages will show smaller effects.
- **Model-generated edits.** The optimizations were written by an LLM, not a human editor, so quality varied.
- **Domain-dependent.** Gains differed by topic; the paper explicitly calls for domain-specific tuning rather than one universal recipe.

What survives all of that is the mechanism and the pecking order: evidence-dense, well-attributed, cleanly written passages get lifted more than thin or padded ones. Treat the study as a **direction and a method**, and treat your own measured [citation coverage](/glossary/citation-coverage) on each engine as the number that actually counts.

## How does this fit what we already know?

It supplies the experimental backbone under advice the field mostly reached by observation. Our own [six factors behind AI recommendations](/blog/factors-ai-recommends-products) and [how to get cited by AI](/blog/how-to-get-cited-by-ai) both lead with specificity, corroboration, and clean extraction; the Princeton experiment is *why* those work. It also reinforces that [GEO is SEO's next layer, not a separate trick](/blog/is-geo-just-seo): the winning edits are editorial quality, not schema hacks. Note the study tested **content** edits, not [structured data](/glossary/structured-data), which is a labelling layer that helps machines parse what things are, a different and complementary lever, not one this experiment measured.

If you want to know whether these edits are actually moving your visibility, that is the loop **Buffy Intel** closes: it snapshots whether AI engines cite and recommend your brand over time, so you can apply the statistics, quotes, and sources this study validated and then watch your earned citation share respond, engine by engine, instead of trusting a benchmark percentage to hold for you.

## What content do AI engines quote most? A study of 3,200 cited passages
Source: https://heybuffy.com/blog/what-content-do-ai-engines-quote-most

**Structured, self-contained single sentences — statistic lines, definitions, and table rows — not flowing prose.** In MaxAEO's 2026 analysis of **3,200 passages** quoted by eight AI engines, statistic lines were quoted the most (about **22%** of all passages) and carried about **3.4x** the "pull" of plain narrative, which trailed every other format. Roughly **45%** of quoted passages were reproduced word-for-word. This reference lays out the full by-format breakdown and what it means for how you write for [extractability](/glossary/extractability).

**Last reviewed: 29 August 2026.** All figures below come from MaxAEO's "What Content AI Quotes Most" analysis (2026): 3,200 cited passages hand-classified from a fixed set of 600 informational queries in B2B SaaS, marketing, and tech, sampled over roughly 60 days across ChatGPT, Gemini, Perplexity, Claude, Copilot, Grok, Google AI Mode, and AI Overviews. It is **single-vendor and observational** — cite "MaxAEO, 2026" with the date, treat the ordering as firm and any single multiple as directional, and note the query set skews technical.

## What kinds of content do AI engines quote most?

Short, structured, self-contained sentences — and they win on two separate measures at once. "Share" is how often a format showed up among quoted passages; "pull lift" is how much more likely a passage of that format was to be quoted than plain narrative. Statistic lines led both:

| Passage format | Share of quoted passages | Verbatim rate | Pull lift vs. prose |
|---|---|---|---|
| Statistic lines | ~22% | ~61% | ~3.4x |
| Definition sentences | ~18% | ~44% | ~3.1x |
| List items | ~17% | ~35% | ~2.2x |
| Direct Q&A answers | ~14% | ~40% | ~2.5x |
| Table rows / cells | ~11% | ~58% | ~2.7x |
| Ordered steps | ~9% | ~33% | ~1.9x |
| Attributed quotes | ~5% | ~47% | ~1.6x |
| Plain narrative | ~4% | ~12% | 1.0x (baseline) |

Source: MaxAEO, 2026. The pattern is consistent with how [passage-level retrieval](/glossary/content-chunk) works: an engine scores candidate passages and keeps the ones that stand alone cleanly, so a sentence carrying one fact beats the same fact wrapped in three clauses of context. Table rows are the telling case — rare on most pages, so their *share* is modest, but per passage they punch far above prose, because a row is already a self-contained unit.

## How often do AI engines quote you word-for-word?

Close to half the time, and more often the more structured the passage is. Across the 3,200 passages, about **45%** were reproduced verbatim rather than paraphrased. The verbatim rate tracked structure directly: statistic lines (~61%) and table rows (~58%) were lifted unchanged far more often than plain narrative (~12%).

- **Median quoted passage: 28 words.** Long enough to carry one fact, short enough to lift whole.
- **70% of verbatim pulls fell in the 15-to-45-word range.** A sentence much longer than that is more likely to be paraphrased or skipped.
- The takeaway: write the sentence you would want quoted. If the fact you care about lives in a 60-word compound sentence, an engine is more likely to reword it — and a reword is where nuance and attribution get lost.

## Where in a section does the quoted sentence sit?

Almost always at the front. MaxAEO found **64%** of quoted passages were the first or second sentence of their section. That is the same answer-first discipline the [structure-a-page-into-extractable-chunks](/blog/structure-content-into-extractable-chunks) how-to argues for, now visible in the data: leading each section with the direct answer is not a style preference, it is where the quoting actually happens. The companion question — how page *length* and *position* interact, and why a fact buried deep in a long page rarely gets pulled — is covered in [where on a page AI engines quote from](/blog/where-on-a-page-do-ai-engines-quote-from).

## Does this contradict "coverage, not length" or the Princeton edit findings?

No — the three line up. This study measures *which passage formats get pulled once a page is retrieved*; the finding that [content length is not the lever, coverage is](/blog/does-content-length-affect-ai-citations) is about *whether the page gets pulled at all*. And the 2024 Princeton GEO experiment on [what content changes lift AI citations](/blog/what-content-changes-lift-ai-citations) — where adding statistics raised a source's [position-adjusted word count](/glossary/position-adjusted-word-count) by about 41% and keyword-stuffing lowered it — points the same way from a causal angle: statistic-dense, evidence-first passages travel best. It is also distinct from [which content formats survive over months](/blog/which-content-formats-survive-ai-citations): that measures durability of a page's citation; this measures which sentence an engine lifts today.

> AI engines quote sentences, not pages. Write each fact as a short, self-contained line — a statistic, a definition, a table row — and you hand the engine something it can lift unchanged.

## What should you do to get quoted more?

Reformat the facts you already have into the units engines lift, then confirm it moved your numbers.

- **Lead each section with a statistic line or a one-sentence definition.** Put the number and the claim in the first sentence, where 64% of quoted passages come from.
- **Turn spec-and-comparison prose into tables.** Row-and-column facts are lifted verbatim far more often than the same data in a paragraph, part of the discipline in [prioritising your structured data](/blog/prioritize-your-structured-data).
- **Keep quotable sentences to roughly 15-45 words.** One fact per sentence, so an engine lifts it whole instead of rewording it.
- **Attribute and date your statistics.** A specific, sourced number is both more quotable and safer to be quoted — the [corroboration](/glossary/corroboration) signal engines reward.
- **Measure per engine.** Formatting is a means, not the goal; track your [citation coverage](/glossary/citation-coverage) after you restructure, engine by engine, because none reports passage-level selection directly.

The honest read for late 2026: getting retrieved is about authority and corroboration, but getting *quoted* is about extractability — and extractability is a writing choice you control on every page. Watching which of your passages engines actually lift, and whether a rewrite changed that, is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## What is agentic commerce, and why brands should care now
Source: https://heybuffy.com/blog/what-is-agentic-commerce

For two decades, buying online meant a human doing the work: searching, opening tabs, comparing, adding to cart. **Agentic commerce** is the shift where an AI agent does that work *on the shopper's behalf*. Discovering options, comparing them against the person's stated needs, and increasingly completing the purchase itself.

Ask an assistant "find me a fragrance-free moisturizer for eczema under $30 and order it," and the agent fans the request into searches, assembles a shortlist, weighs the criteria, and, where the plumbing exists. Checks out. The person reviews a recommendation, not a search results page.

## The real change: from browsing to machine selection

The consequential part isn't the convenience. It's **who's doing the selecting**.

When a human browses, every brand on the shelf gets a glance. When an agent selects, it builds a small consideration set first, and if you're not in it, you're eliminated *before* a human ever looks. Discovery moves upstream of your website and upstream of the human eye. The "shelf" becomes the agent's shortlist, and the agent assembles that shortlist from what it can find, parse, and trust about your products.

> In agentic commerce, the buyer you have to win over first is a machine. If it can't find or understand your product, the human never gets the choice.

## Why brands should care now

Three reasons it's not a "later" problem:

1. **The interface is already moving into chat.** Shopping surfaces inside AI assistants, product cards in answers, and emerging checkout standards mean the path from "question" to "purchase" is collapsing into a single conversation.
2. **Machine selection rewards different things than a pretty PDP.** An agent doesn't see your hero image or your brand film. It reads [structured product data](/glossary/structured-data). Attributes, specs, availability, price, and the sources that describe you. Gaps that a human shopper forgives, an agent simply can't resolve.
3. **Readiness is uneven, so it's an edge.** Most catalogs aren't structured for machine selection yet. The brands that get ready early get chosen disproportionately while the field catches up.

## Two layers: visible, then buyable

It helps to separate two things:

- **Visibility**: does the agent find and recommend you at all? This is the AI-search/[GEO](/glossary/generative-engine-optimization) layer: be retrievable, well-structured, and trusted enough to make the shortlist.
- **Transactability**: once recommended, can the agent actually *buy* from you? This is the newer layer that checkout protocols are being built for.

You need both, in order. There's no point being purchasable if you're never surfaced, and no point being surfaced if the agent can't transact. The next articles in this series cover [the protocol making transactability real](/blog/agentic-commerce-protocol-acp), and [how to get your catalog ready](/blog/agentic-commerce-readiness) for both. It's also the frontier of what **Buffy Intel** watches: not just how AI describes your brand, but whether your products are positioned to be chosen.

## What is Amazon Rufus (Alexa for Shopping)?
Source: https://heybuffy.com/blog/what-is-amazon-rufus

**Amazon Rufus — which Amazon renamed "Alexa for Shopping" on 13 May 2026 — is Amazon's generative-AI shopping assistant, built into the Amazon app and website, that answers product questions in plain language and recommends items from Amazon's catalogue.** Amazon describes it as powered by generative and agentic AI and built on [Amazon Bedrock](/glossary/large-language-model), drawing on models including Anthropic's Claude Sonnet, Amazon Nova, and a custom model trained on Amazon's own product catalogue, customer reviews, and community Q&A. It is, in effect, an answer engine that sits on top of the world's largest product catalogue.

This piece explains what Rufus is, how it decides what to surface, and — the part that matters for brands — what actually influences whether your product gets chosen. It is part of our [agentic commerce](/glossary/agentic-commerce) series. Volatile specifics (the rename, feature names, adoption figures) are dated and attributed to Amazon; the durable point is that a huge slice of product discovery now happens inside a [conversational](/glossary/conversational-search), often [zero-click](/glossary/zero-click-search) answer.

## How does Amazon Rufus work?

A shopper types or speaks a natural-language question — broad ("what should I know before buying a tent?") or specific ("what's the battery life on this model?") — and Rufus returns a direct answer plus a curated set of product recommendations, inside the shopping app. Often the shopper decides without ever opening a traditional product page.

To answer, Rufus reads across four kinds of Amazon data and the wider web:

| Rufus draws on | What it pulls from the source |
|---|---|
| Product listings | Titles, bullet points, descriptions, structured attributes |
| Product images | Visual detail, and shopper-uploaded images via visual search |
| Customer reviews | Real-world experience, durability, fit, common complaints |
| Community Q&A | Direct answers to the questions buyers actually ask |
| Information from across the web | Broader context Amazon's models were trained or grounded on |

Practitioner teardowns link Rufus to Amazon's "COSMO" work on inferring shopper *intent* rather than matching keywords literally; Amazon's own descriptions emphasise reasoning over its catalogue, reviews, and community content. Either way, the behaviour that matters to a brand is the same: Rufus is choosing a well-supported answer, not sorting a keyword-ranked list.

## How big is Rufus, and how fast is it growing?

By Amazon's own mid-2026 figures, large and accelerating — treat these as Amazon's self-reported numbers, dated and un-audited:

| Metric (Amazon, reported mid-2026) | Figure |
|---|---|
| Customers who used Rufus in the past year | 250M+ |
| Monthly active users, year over year | +149% |
| Interaction volume, year over year | +210% |
| Shoppers who use it are "more likely to purchase" | 60%+ |

Amazon also says it shipped more than 50 upgrades in the period, including account memory tuned to your shopping history, 30- and 90-day price history, price alerts and an auto-buy feature (Amazon claims ~20% average savings), handwritten grocery-list scanning on iOS, visual search from uploaded images, influencer-storefront discovery, and agentic "Buy for Me" and "Shop Direct" capabilities that begin to act on the shopper's behalf.

> A quarter-billion shoppers a year now start with a question, not a search box. When the answer arrives with three products attached, the recommendation *is* the shelf.

## What does Rufus mean for whether your product gets chosen?

It raises the stakes on work you should already be doing, and it hands new weight to content you do not author. Because Rufus reasons over listings, images, reviews, and Q&A, the levers that decide whether it surfaces you are the same [six factors that make AI recommend a product](/blog/factors-ai-recommends-products) — reachability, coverage, specificity, corroboration, freshness, and clarity — applied to your Amazon presence:

- **A complete, specific listing.** Named, numeric, dated attributes — materials, dimensions, compatibility, what it fits, who it's for — give Rufus quotable facts. Adjectives give it nothing to lift.
- **Reviews and Q&A are now ranking inputs, not just social proof.** Rufus reads them to answer buying concerns. Genuine reviews that address durability, fit, and common objections, and answered community questions, are content that shapes what Rufus says about you — and you don't write it, so [earn it, don't fake it](/glossary/earned-media).
- **Accuracy and availability.** Wrong specs or out-of-stock detail propagate into the answer; a clean, current listing is the freshness signal.

The honest framing: Rufus is a **surface you earn placement in**, not a dial you turn. It is distinct from a [shopper agent](/blog/shopper-agents-and-product-visibility) you deploy yourself — Rufus is Amazon's assistant, closer to an answer engine for the Amazon catalogue. The deeper catalogue work carries over directly: everything in [preparing your product catalogue for AI agents](/blog/prepare-product-catalog-for-ai-agents) applies, and Rufus is one more surface to track alongside [ChatGPT, Google, and Perplexity for product discovery](/blog/chatgpt-vs-google-vs-perplexity-product-discovery).

## Can you measure whether Rufus surfaces your products?

Not through a first-party Amazon report today — Rufus does not expose a "how often were you recommended" dashboard. What you can do is treat it like any other AI answer surface: [keep your products visible to AI shopping agents](/blog/keep-products-visible-to-ai-shopping-agents), then sample the questions real buyers ask in your category and record whether your products appear, how prominently, and how they're described. That is exactly the presence-and-portrayal snapshot Buffy Intel takes across engines — and as agentic assistants like Rufus absorb more of the buying journey, being the product the answer recommends is the whole game. [See how Buffy Intel tracks it](/blog/how-to-measure-ai-visibility).

## What is an agentic browser, and how do brands show up in one?
Source: https://heybuffy.com/blog/what-is-an-agentic-browser

An agentic browser is a web browser with a built-in AI agent that can **act on the web, not just display it**: it reads pages, compares options across open tabs, fills forms, and completes multi-step tasks from a plain-language instruction. The best-known 2026 examples are Perplexity's **Comet** and The Browser Company's **Dia**, plus OpenAI's browsing agent, which moved from the standalone **ChatGPT Atlas** browser into the **ChatGPT app** in August 2026. For brands, they are a new and distinct place to be found, one that a chatbot-only visibility check can miss.

This explainer defines the category, maps the players (with numbers attributed and hedged, because they move fast), and explains how an agent decides which brands to surface. It is the concept companion to the practical [playbook for optimising your site for agentic browsers](/blog/optimize-for-agentic-browsers), and it sits alongside our work on turning [websites into agent endpoints](/blog/websites-as-agent-endpoints).

## What is an agentic browser?

An agentic browser is a browser whose core feature is an AI **agent** that can take actions on your behalf. You still browse normally, but you can also hand it a task, "compare these three laptops and tell me the cheapest with 32GB RAM", and it will open pages, read them, reason across them, and report back or act.

The shift is from **retrieving pages** to **completing tasks**. A traditional browser fetches a URL and renders it for a human to read. An agentic browser adds a layer that can read the rendered page itself, hold several pages in context at once, and chain steps together, closer to [conversational search](/glossary/conversational-search) with hands. It overlaps heavily with [agentic commerce](/glossary/agentic-commerce), because shopping, comparing, and checking out are exactly the multi-step tasks these agents are built for.

## How is an agentic browser different from an AI chatbot or a normal browser?

They occupy three different positions in the stack. The table separates them on the axis that matters for visibility: **where the answer is assembled and from what**.

| Surface | What it does | Where it gets facts |
|---|---|---|
| **Traditional browser** | Renders a page for a human to read | The one page you navigate to |
| **AI chat / AI Overviews** | Answers a question inside its own app or results panel | A retrieval index plus the model's training data |
| **Agentic browser** | Reads live pages and completes tasks across them | The **visible content of the real sites** it opens, synthesised |

The distinction is not cosmetic. An AI chat answer is assembled from a retrieval index; an agentic browser reads what is actually on the page in front of it, right now. That makes the live, rendered, extractable state of your site, not just how you were crawled weeks ago, the thing that decides whether the agent can use you.

## Which agentic browsers matter in 2026?

A small set of agentic-browsing surfaces leads the category as of mid-2026, each backed by a different AI lab and leaning toward a different job. The user counts below are **third-party estimates from browser-tracking analysts, directional and fast-moving**, not official figures, so treat the ordering as more reliable than the exact numbers, and note the OpenAI change flagged beneath the table.

| Surface | Maker | Emphasis | Reported scale (est., mid-2026) |
|---|---|---|---|
| **ChatGPT** (in-app browser) | OpenAI | Research and task execution; the ChatGPT app browses live sites, logs in, downloads files, and acts across tabs | Standalone *Atlas* browser was largest of the dedicated three (~10–15M MAU) before retirement |
| **Comet** | Perplexity | Research-first; pull quotes and cite sources while browsing | ~3–5M MAU |
| **Dia** | The Browser Company | AI-native everyday browser; successor to Arc | ~2–3M MAU |

Sources: browser-landscape estimates published by Presenc AI and DigitalApplied (2026); single-vendor and directional. For scale, Chrome still held roughly **71%** of the global browser market in early 2026 (widely reported), so agentic browsers are a small but fast-growing slice, concentrated among heavy AI users. Arc, the browser that proved appetite for a radically different UX, entered maintenance mode in 2025 when The Browser Company pivoted to Dia. **Update (6 August 2026):** OpenAI retired the standalone **ChatGPT Atlas** browser, launched October 2025 and switched off on 9 August 2026, and moved its agentic browsing into the ChatGPT app and a ChatGPT Chrome extension, on the reasoning that the browser is a feature rather than a standalone destination (OpenAI, via TechCrunch, July 2026). The capability didn't disappear; it changed shape, which is exactly why you anchor on the category, not the leaderboard.

## How does an agentic browser decide which brands to show?

By reading the visible page and synthesising across sources, favouring whatever it can extract cleanly. When an agent handles a "find me the best X" task, it does not consult a single ranking. It fans the request into sub-tasks, opens candidate pages, review sites, and listicles, and lifts the facts it can read as plain text, a browser-side version of [query fan-out](/glossary/query-fan-out).

Three behaviours follow from that, and they mirror how AI search already works:

- **Extractable facts win.** Prices, specs, and availability stated as server-rendered text get used; the same facts locked in JavaScript, a PDF, or an image are skipped. This is the same failure mode documented in AI-search [citation](/glossary/citation), and [structured data](/glossary/structured-data) helps the agent read you unambiguously.
- **Third-party corroboration is pulled in.** Agents surf review sites and comparison articles when weighing options, so how you appear off your own domain shapes the recommendation, echoing [how AI engines choose which brands to name](/blog/how-ai-engines-choose-brands).
- **Frictionless flows matter.** Because the agent may try to *act*, compare, add to cart, book, a form or checkout it cannot complete is a place you drop out of the task.

## Why are agentic browsers a distinct AI-visibility surface?

Because a brand can be visible in one AI surface and invisible in another, and agentic browsers route through different engines with different recall. Comet's outcomes are shaped by Perplexity's models; ChatGPT's in-app browsing by OpenAI's; Dia by its own stack. A brand that tracks only its plain-chat ChatGPT presence is watching one window.

One browser-landscape analysis (Presenc AI, May 2026, single-vendor and directional) estimated that **brands monitoring only ChatGPT miss roughly 20–30% of the dedicated agentic-browser surface**. Whatever the precise figure, the structural point holds: this is a separate place to measure, the same reason [product discovery differs across ChatGPT, Google, and Perplexity](/blog/chatgpt-vs-google-vs-perplexity-product-discovery). It also compounds [zero-click](/glossary/zero-click-search) behaviour, because the agent may complete the whole task, read, compare, decide, without the user ever clicking through to your site.

> An agentic browser doesn't visit your website so much as read it and act on it. If the fact it needs isn't on the visible page as plain text, you weren't a candidate for the task.

## What should brands do about agentic browsers?

Make the live page do the work an agent needs: expose every decision-driving fact as clean, server-rendered text; keep flows completable; and monitor how you are summarised and compared across more than one engine. The detailed steps, from extractable pricing to [agent-readable site structure](/blog/make-your-website-agent-readable), are in the companion [playbook for optimising for agentic browsers](/blog/optimize-for-agentic-browsers). The durable idea is simple: being **reachable, readable, and actionable on the live page** is what makes an agent able to choose you.

Knowing whether agents and AI engines are actually surfacing your brand, across ChatGPT, Perplexity, Google, and the browsers built on them, is exactly what **Buffy Intel** tracks, engine by engine, over time. Structure the live page for the agent; verify it was chosen.

## What is AP2 (Agent Payments Protocol)?
Source: https://heybuffy.com/blog/what-is-ap2

**AP2 (Agent Payments Protocol) is Google's open standard for letting an AI agent pay on a person's behalf while proving the person authorised it.** Before an agent spends, the human signs a tamper-proof digital contract — a *Mandate* — recording exactly what was approved. A merchant or bank can then verify, cryptographically, that the payment reflects real human intent, not an agent acting alone. Google announced AP2 in **September 2025** with more than **60** payment and commerce partners, and built it to work across cards, bank transfers, and stablecoins.

This piece explains what AP2 is, the problem it solves, how its three Mandates work, and where it sits relative to the [Agentic Commerce Protocol](/blog/agentic-commerce-protocol-acp) and [x402](/blog/what-is-x402). Volatile specifics — partners, adoption, rail mix — are dated and attributed; the durable idea is a signed proof of human authorisation that travels with an agent's payment.

## What problem does AP2 solve?

AP2 solves the trust gap that opens the moment an agent, not a person, initiates a payment. Card networks, banks, and merchants have decades of machinery built around a human clicking "buy." When a [shopper agent](/glossary/shopper-agent) pays instead, three questions have no built-in answer, and Google frames AP2 around exactly these three:

- **Authorisation** — did the user actually authorise this specific purchase, or is the agent acting beyond what it was told?
- **Authenticity** — can the merchant trust that the agent's request reflects the user's genuine intent, not a misunderstanding or a hallucination?
- **Accountability** — if a transaction is wrong or fraudulent, who is responsible, and what evidence settles the dispute?

Without a shared answer, every party has to either block agent payments or accept unpriced risk. AP2's response is to attach cryptographic proof of authorisation to the payment itself, so the answer travels with the transaction.

## How do AP2's three Mandates work?

AP2 works through three signed digital contracts called **Mandates**, each carried as a **W3C Verifiable Credential** — a tamper-proof, cryptographically signed record. Together they build a non-repudiable audit trail from the user's instruction to the final charge.

| Mandate | What it captures | Signed by |
|---|---|---|
| **Intent Mandate** | The rules of engagement — price limits, timing, and conditions — that let an agent act when the user is away | The user, up front |
| **Cart Mandate** | The exact items, prices, and details of a specific order, locked as an unchangeable record | The user (or auto-generated under a valid Intent Mandate) |
| **Payment Mandate** | A signal to the network and bank that an AI agent initiated the transaction, for risk visibility | The agent, linked to the Cart |

Source: Google Cloud AP2 announcement and protocol documentation, September 2025. The Mandates chain together so that what the user authorised, what the agent selected, and what was charged all reconcile — and any mismatch is visible.

## What is the difference between a human-present and a delegated payment?

The Mandate you start with depends on whether the person is there when the purchase happens.

- **Human-present (real-time).** The agent assembles a cart, the merchant cryptographically signs it, and the user gives final approval — producing a **Cart Mandate** the moment they say yes. This is the "buy these now" case, with the person in the loop.
- **Human-not-present (delegated).** The user signs an **Intent Mandate** in advance with explicit parameters ("buy the tickets the instant they drop, under $400"). When the conditions are met, the agent auto-generates a Cart Mandate under that authority — no further approval needed, because the boundary was pre-signed.

> AP2's insight is that "the user approved this" should be a signed artefact that travels with the payment — not a claim the agent makes about itself.

Both paths end in the same place: a verifiable record tying the charge back to something the human actually signed. The delegated path is what makes genuinely autonomous [agentic commerce](/blog/what-is-agentic-commerce) safe to underwrite, because the agent's freedom is bounded by a contract the user set.

## How does AP2 relate to A2A, MCP, and x402?

AP2 does not stand alone; it extends protocols agents already use. It builds on the **Agent2Agent (A2A)** protocol and Anthropic's **Model Context Protocol (MCP)**, adding the payments-authorisation layer those standards lack. Where MCP connects an agent to tools and data and A2A lets agents coordinate, AP2 governs the moment money moves.

For settlement, AP2 is **rail-agnostic**. It handles cards and bank transfers directly, and it reaches [stablecoins](/glossary/stablecoin) and crypto through the **A2A x402 extension** — the same [x402](/blog/what-is-x402) payment-request standard Google developed for this with Coinbase, the Ethereum Foundation, and MetaMask. In stack terms: AP2 proves the authorisation, x402 can carry the payment request for the crypto path, and a card network or blockchain does the actual settling.

## Where does AP2 sit next to ACP and the payment rails?

At the authorisation layer, distinct from checkout orchestration and from the rails. It helps to separate the stack an agent purchase moves through:

| Layer | Example | Job |
|---|---|---|
| Discovery / being chosen | [Answer-engine optimisation](/glossary/answer-engine-optimization) | Whether an agent surfaces and picks your product at all |
| Checkout orchestration | [ACP](/blog/agentic-commerce-protocol-acp) (OpenAI + Stripe) | Completing an order inside an assistant like ChatGPT |
| Payment authorisation | **AP2** (Google) | Proving a human authorised what the agent pays for |
| Payment request | [x402](/blog/what-is-x402) | The HTTP handshake that asks for, and confirms, payment |
| Settlement rail | [Cards or stablecoins](/blog/cards-vs-stablecoins-agent-payments) | Actually moving the money |

These are complementary layers, not competitors. A single agent purchase could be discovered through an answer engine, orchestrated through a checkout standard, authorised through AP2, and settled on a card or a stablecoin. As of mid-2026 none of these standards has converged into a single winner, and a brand does not need to bet on one — the transaction layer is being built to be plural. For a side-by-side of the three standards, see [ACP vs AP2 vs x402](/blog/agent-payment-protocols-compared).

## What does AP2 mean if you sell online?

Mostly, it is infrastructure you will accept rather than build by hand — but it lowers a real barrier. By giving banks and merchants a verifiable answer to "did the human authorise this?", AP2 makes them more willing to let agents transact at all, which enlarges the pool of purchases an agent can complete on your behalf. That is upside for any brand ready to be bought by machines, and it rides on the same [checkout-readiness](/blog/agentic-commerce-readiness) groundwork agentic commerce already asks for.

But AP2 settles *how* an agent pays and proves it was allowed to — not *whether* it picks you. That decision happens a layer up, at discovery, and it turns on whether an answer engine surfaces and recommends your product in the first place. That is exactly what **Buffy Intel** measures, snapshot over snapshot. Questions: support@flash.tech.

## What is GEO & AEO, and why brands can't ignore it
Source: https://heybuffy.com/blog/what-is-geo-aeo

For twenty years, getting found meant ranking on Google. A customer typed a query, scanned ten blue links, and clicked. Search Engine Optimization. SEO. Was the craft of earning those clicks.

That world is quietly ending. People increasingly *ask* instead of *search*: they pose a full question to ChatGPT, Gemini, Claude, or Google's AI Overviews and read a single synthesized answer. There are no ten links to scan. Often there's one paragraph, naming a few brands. If you're not in that paragraph, you're invisible.

**GEO and AEO are the disciplines of staying visible in that new world.**

## The two terms, in plain English

- **AEO. [Answer Engine Optimization](/glossary/answer-engine-optimization).** Being *the answer* to a question. When someone asks "what's the best fragrance-free moisturizer for eczema?", AEO is the work that makes an engine pull your product, your page, or your brand into its reply.
- **GEO. [Generative Engine Optimization](/glossary/generative-engine-optimization).** The broader practice of being *mentioned, cited, and recommended* across generative AI engines, not just for one question, but consistently, across the thousands of ways customers phrase their needs.

The distinction is academic in day-to-day work. Both come down to the same goal: **when an AI talks about your category, it talks about you. Accurately and favorably.**

## Why this matters now, not later

Three things changed at once:

1. **AI answers became the default surface.** ChatGPT, Gemini, and Claude have hundreds of millions of users between them, and Google now puts AI Overviews and AI Mode in front of ordinary searches. The "answer" is increasingly the destination, not a stepping stone to your site.
2. **Discovery moved upstream of your website.** A shopper can research, compare, and form a shortlist *entirely inside an AI conversation* before ever visiting a brand's site. By the time they land, the decision is half-made, and you may not have been in the running.
3. **The engines disagree.** ChatGPT, Gemini, and Claude are trained and grounded differently, so they describe and recommend brands differently. A brand can be a hero in one and absent in another. You can't manage what you can't see across all of them.

> If customers are forming opinions about your brand inside AI conversations you never see, that's not a content problem. It's a visibility blind spot.

## What "being visible" actually means

AI visibility isn't a single number. It breaks into a few concrete questions:

- **Presence**: does the engine mention you at all for the questions that matter?
- **Sentiment & framing**: *how* does it describe you? As the premium pick, the budget option, the dated incumbent?
- **[Citations](/glossary/citation)**: does it point to *your* pages as the source, or to a retailer, a review site, or a competitor?
- **[Share of voice](/glossary/share-of-voice)**: when several brands are named, how often is it you versus your rivals?
- **Consistency**: ask the same question five times and you may get five slightly different answers. Visibility you can't reproduce isn't visibility you can rely on.

### Why it's hard to do by hand

You could open five engines and ask a few questions. Many teams start there. But the answers shift by phrasing, by day, and by random chance; they differ across engines; and "the questions that matter" number in the hundreds once you account for every product, use case, and comparison. Eyeballing it doesn't scale, and it doesn't give you a trend you can act on.

## The good news: this is influenceable

AI engines aren't a black box you're at the mercy of. They read the open web, they favor clear and well-structured information, and they reward brands that make their facts easy to find and hard to misread. The rest of this series covers exactly how that works. How engines decide who to recommend, and the concrete moves that make your brand the one they pick.

That's the whole premise of **Buffy Intel**: see how every major AI engine describes your brand, every day, and get a prioritized plan to improve it.

## What is Microsoft Web IQ? Bing's grounding API for AI agents
Source: https://heybuffy.com/blog/what-is-microsoft-web-iq

Microsoft Web IQ is a suite of **AI-native grounding APIs**, announced in June 2026, that lets AI agents pull fresh, passage-level evidence from the web instead of whole documents. Microsoft frames it as a search engine built for agents rather than people. Fed by Bing's existing index but re-architected for machine consumption. For brands, it is another pipe through which an AI assembles an answer, and it rewards the same things [getting cited by AI](/blog/how-to-get-cited-by-ai) always has.

**As of late June 2026** the details below come from Microsoft's own announcement on the Bing blog; performance figures are Microsoft-stated and, where noted, from internal comparisons, so read them as vendor claims pending independent testing.

## What is Microsoft Web IQ?

Web IQ is a set of [grounding](/glossary/grounding) APIs that connect AI systems and agents to current information from across the open web. Where a person uses a search engine and reads the results, an agent calls Web IQ and receives evidence it can reason over. Retrieved from web pages, news, images, and video, then condensed into the passages most relevant to the query. Microsoft positions it for the "agentic era": the infrastructure an autonomous system uses to look something up mid-task.

| Attribute | What Microsoft states |
|---|---|
| What it is | AI-native grounding APIs for agents and AI systems |
| Built on | Bing's global index, re-architected for AI workloads |
| Latency | Sub-165ms at P95 (Microsoft-stated) |
| Retrieval unit | Passage-level extraction, not full documents |
| Quality metric | GDSAT. Grounding satisfaction across completeness, freshness, authority |
| Speed claim | ~2.5× faster than alternatives (Microsoft internal comparison) |
| Coverage | Web pages, news, images, video |
| Announced | June 2026 |

The table reflects Microsoft's announcement; the speed and latency numbers are the vendor's own and have not been independently verified.

## How is Web IQ different from a normal search API?

It optimises for a model's economics, not a human's reading. Three design choices stand out, all aimed at "fewer tokens in, better answers out, lower cost per call":

- **Passage-level extraction.** Instead of handing back a full page for the model to wade through, Web IQ returns the specific passages that answer the query. This maximises information density and minimises the tokens the calling model has to pay for.
- **Low latency for multi-step reasoning.** Microsoft reports sub-165ms P95 retrieval, fast enough to sit inside an agent's reasoning loop where a query may fan out into many sub-queries before an answer is composed.
- **A grounding-quality metric.** Microsoft introduced **GDSAT**, a measure of how well a retrieved set satisfies a query along completeness, freshness, and authority. A signal that the system is being tuned for *evidence quality*, not link ranking.

> A classic search API answers "what are the best pages for this query?" Web IQ answers "what is the most trustworthy, current passage a model can ground on right now?" That shift. From ranking pages to serving evidence. Is the whole point.

## What does Web IQ mean for getting cited in AI answers?

It raises the value of being passage-extractable. If agents adopt Web IQ as a grounding source, the unit they retrieve is the passage. Exactly the [chunk-level retrieval](/blog/how-to-get-cited-by-ai) that already decides AI citations. The implications line up with disciplines this site has argued for repeatedly:

- **Write self-contained, answer-first chunks.** Passage extraction can only lift a clean, standalone unit. A point buried mid-paragraph is harder to return than a section that opens with the answer.
- **Keep pages current.** Freshness is one of GDSAT's three axes, which echoes the broader [citation freshness cliff](/blog/content-freshness-citation-cliff). Stale pages score worse as grounding evidence.
- **Build the entity.** Authority is another GDSAT axis, so a corroborated, well-established [entity](/glossary/entity-authority) is more likely to be selected, consistent with [why AI tends to cite one brand](/blog/why-ai-cites-one-brand).

Web IQ doesn't introduce a new optimisation game; it puts a price on the one already in play. It also sits alongside other grounding pipelines. [How Claude web search works](/blog/how-claude-web-search-works) and [how Google AI Mode works](/blog/how-google-ai-mode-works), as part of a broader move from RAG toward [agentic retrieval](/blog/beyond-rag-agentic-ai-search).

## Does Web IQ change how AI crawlers read my site?

Mostly it reinforces Bing-side hygiene. Web IQ is built on Bing's index, so the [AI crawler](/glossary/ai-crawler) and indexing rules that already govern Bing apply, if BingBot can't reach or render your content, it can't become Web IQ evidence. Microsoft also says it respects robots protocols and publisher controls and is engaging open-web standards bodies (the IETF), which signals an intent to play inside the existing rules rather than around them.

Two honest caveats keep this in perspective. First, Web IQ is a **developer- and agent-facing grounding layer**, not a consumer product. Its real-world reach depends on which agents adopt it, which is unknown at launch. Second, "respects robots" is a stated commitment; as the corpus's [robots.txt compliance test](/blog/do-ai-assistants-respect-robots-txt) showed, the right move is still to enforce any genuine block at the [CDN](/blog/is-your-cdn-blocking-ai-crawlers), not to trust a text file. For most brands the priority is the opposite of blocking: making sure you're reachable and that you'd recognise the traffic if it arrived. Confirm the major bots in the [AI crawler user-agent directory](/blog/ai-crawler-user-agent-directory) aren't disallowed.

Web IQ is one more reason the fundamentals compound: be reachable, be passage-extractable, be current, be a strong entity. Whether an answer is grounded through Bing, Claude, Google AI Mode, or a Web IQ-powered agent, the brand that wins is the one whose evidence is easiest to trust and lift. Watching whether those answers actually name and cite you. Across every engine, as they shift. Is exactly what **Buffy Intel** is built to track. Questions: support@flash.tech.

## What is UCP (Universal Commerce Protocol)?
Source: https://heybuffy.com/blog/what-is-ucp

**UCP (Universal Commerce Protocol) is Google's open-source standard for the whole agentic shopping journey — how an AI agent discovers products, builds a cart, checks out, and tracks fulfilment across a merchant.** Google announced it on **11 January 2026** with retailers including Shopify, Etsy, Wayfair, Target, and Walmart, and endorsement from **more than 20** partners such as Visa, Mastercard, Stripe, and American Express. Where [AP2](/blog/what-is-ap2) proves an agent's payment was authorised, UCP orchestrates everything around that payment.

This piece explains what UCP is, the six things it standardises, how it relates to [AP2](/glossary/ap2) and the [Agentic Commerce Protocol (ACP)](/blog/agentic-commerce-protocol-acp), and what it asks of a merchant. Volatile specifics — partners, surfaces, rollout geography — are dated; the durable idea is a shared language for agent-driven commerce that no single company owns.

## What problem does UCP solve?

UCP solves the fragmentation that appears once AI agents start buying across many merchants. Every retailer already has its own checkout, its own cart format, its own order-status API. A human clicks through those one at a time without noticing. A [shopper agent](/glossary/shopper-agent) transacting across dozens of stores hits a different integration at each one, and that friction is what stops agentic commerce from scaling.

The protocol's answer is a common vocabulary: one agreed way to describe a product, add it to a cart, apply a discount, complete checkout, and report that an order shipped — so an agent learns the pattern once and reuses it everywhere. That is the same reason the web needed HTTP and email needed SMTP: shared primitives beat one-off integrations.

## What does UCP actually standardise?

UCP defines a set of functional primitives — the repeatable actions any agentic purchase needs — so a merchant exposes them once and any compliant agent can use them. As of its January 2026 specification, it standardises six:

| UCP primitive | What it covers |
|---|---|
| Product discovery | Surfacing catalog items and attributes an agent can shortlist from |
| Checkout | Initiating and completing a purchase on the shopper's behalf |
| Discount handling | Applying promotions, codes, and offers within the agent flow |
| Fulfilment | Shipping, delivery, and pickup options and status |
| Order management | Post-purchase state — confirmations, changes, returns |
| Identity linking | Connecting the shopper's identity to their account with the merchant |

Source: Google's Universal Commerce Protocol announcement and developer documentation, January 2026. The point of the table is that UCP is not just "agent checkout" — it spans the full lifecycle from finding a product to managing the order after it ships.

> UCP is the shared grammar of agentic commerce: describe a product, build a cart, pay, and track the order the same way everywhere, so an agent integrates once instead of once per store.

## How does UCP relate to AP2, ACP, and MCP?

UCP is the commerce-orchestration layer; it leans on other protocols for the pieces it deliberately does not own. Google states UCP is **compatible with AP2** for the payment step, and that merchants can implement UCP over ordinary **APIs**, the **Agent2Agent (A2A)** protocol, or the **Model Context Protocol (MCP)**. In plain terms: UCP runs the shopping journey, and when it reaches "pay," it hands off to AP2 to prove the human authorised the charge.

That makes UCP the closest Google counterpart to the [Agentic Commerce Protocol (ACP)](/blog/agentic-commerce-protocol-acp) from OpenAI and Stripe. Both orchestrate an agent-driven purchase; they are parallel bets from different ecosystems rather than layers stacked on each other. A useful way to hold it: UCP and ACP compete at the *journey* layer, while AP2 and [x402](/blog/what-is-x402) operate a layer *down*, at payment authorisation and payment request.

## Where does UCP sit in the agentic-commerce stack?

At the commerce-orchestration layer — above the payment protocols and the settlement rails, below the discovery decision of whether an agent picks you at all. Separating the layers keeps the growing protocol zoo legible:

| Layer | Example | Job |
|---|---|---|
| Discovery / being chosen | [Answer-engine optimisation](/glossary/answer-engine-optimization) | Whether an agent surfaces and selects your product |
| Commerce orchestration | **UCP** (Google) · [ACP](/blog/agentic-commerce-protocol-acp) (OpenAI + Stripe) | Running the journey: discover, cart, checkout, fulfil, manage |
| Payment authorisation | [AP2](/blog/what-is-ap2) (Google) | Proving a human authorised what the agent pays for |
| Payment request | [x402](/blog/what-is-x402) | The HTTP handshake that asks for and confirms payment |
| Settlement rail | [Cards or stablecoins](/blog/cards-vs-stablecoins-agent-payments) | Actually moving the money |

These are complementary layers, not competitors — except at the orchestration row, where UCP and ACP are genuine alternatives. A single purchase could be discovered through an answer engine, orchestrated by UCP, authorised by AP2, and settled on a card. As of mid-2026 no orchestration standard has won, so a merchant does not have to pick one; the durable work feeds all of them.

## What is the Universal Cart, and where does it run?

The **Universal Cart** is Google's first product built on UCP: a single cart a shopper fills across Google surfaces — Search, the Gemini app, and later YouTube and Gmail — and checks out once. Google reported the U.S. rollout beginning in the **summer of 2026**, starting with Search and the Gemini app, with expansion to Canada, Australia, and then the U.K., plus new verticals like hotel booking and local food delivery.

Crucially, **the brand stays the merchant of record.** A shopper can either check out natively with Google Pay in a few taps or transfer the cart to the merchant's own site to complete the purchase — either way the merchant keeps the customer relationship. Google also said it would introduce AP2-backed agent payments to these surfaces "in the coming months," starting with Gemini. These specifics are dated to mid-2026 and will move; the durable shape is a shared cart with the merchant, not Google, as seller.

## What does UCP mean if you sell online?

Mostly it is infrastructure you adopt rather than build, but it changes where a purchase can complete. If your catalog is exposed through UCP, an agent can discover, buy, and track an order from your store inside a surface like Gemini — without the shopper ever loading your site. Google's baseline for the Universal Cart is an active Merchant Center account and checkout-eligible products; the [readiness](/blog/agentic-commerce-readiness) and [catalog-enrichment](/blog/prepare-product-catalog-for-ai-agents) work you would do anyway is what feeds it.

But UCP settles *how* an agent transacts with you — not *whether* it chooses you. That decision happens a layer up, at discovery, and it turns on whether an answer engine surfaces and recommends your product in the first place. That is exactly what **Buffy Intel** measures, snapshot over snapshot. Questions: support@flash.tech.

## What is x402? The HTTP-native payment standard for AI agents
Source: https://heybuffy.com/blog/what-is-x402

**x402 is an open standard for paying over HTTP.** It revives the long-dormant `402 Payment Required` status code so a server can quote a price and a client can pay for a gated resource inside an ordinary web request, with no checkout page and no human in the loop. It was built for machines: an [AI agent](/glossary/shopper-agent) or app asks for a page, dataset, API call, or product, receives a `402` stating the price and where to pay, pays, and retries with proof attached. On **14 July 2026** the **Linux Foundation** launched the **x402 Foundation** to steward the protocol, with **40 members** including Google, Stripe, Visa, Mastercard, Cloudflare, and Coinbase.

This piece explains what x402 is, how its handshake works, who governs it, and where it sits relative to the [Agentic Commerce Protocol](/blog/agentic-commerce-protocol-acp) and the [card and stablecoin rails](/blog/cards-vs-stablecoins-agent-payments). Volatile specifics — membership, payment mix, adoption — are dated and attributed; the durable idea is HTTP-native payment.

## What does x402 actually do?

x402 turns a web request into a payment request. HTTP has reserved the `402 Payment Required` status code since the 1990s, but it sat unused for decades because there was no agreed way to state a price or settle a payment inside the protocol. x402 fills that gap: it standardises the small payload a server returns with a `402` — the price, the accepted asset, and where to pay — and the proof a client attaches when it retries.

The point is to let software pay software. A human buying a coffee doesn't need it; a fleet of agents each fetching a paid API a thousand times a minute does. Because the whole exchange happens inside normal HTTP, there is no redirect to a hosted checkout, no stored card, and no session for a person to click through. That makes it suited to the sub-cent, high-frequency payments that agents generate and cards can't economically carry.

## How does the x402 handshake work?

In four steps, all inside one request-and-retry over ordinary HTTP:

| Step | What happens |
|---|---|
| 1. Request | A client (agent, app, or crawler) requests a gated resource — a page, dataset, API, or MCP tool. |
| 2. `402` challenge | The server answers `402 Payment Required` with a small payload: the **price**, the **accepted asset**, and **where to pay**. |
| 3. Pay | The client settles the amount — today typically a stablecoin such as USDC — often in under a second. |
| 4. Retry with proof | The client repeats the request with proof of payment attached; the server returns the resource. |

Source: x402 Foundation / Linux Foundation launch materials and Cloudflare's x402 documentation, mid-2026. Coinbase, which built x402, describes settlement costs as "less than a fraction of a cent," with stablecoin transactions clearing sub-second on chains such as Base. Because the flow is just HTTP, any server behind a compatible gateway can charge, and any client that speaks x402 can pay, without either side building a bespoke billing integration.

## Who governs x402, and how big is it?

Since **14 July 2026**, x402 is governed by the **x402 Foundation under the Linux Foundation**, with the protocol contributed by **Coinbase** and developed under vendor-neutral, open governance. At the operational launch the Foundation listed **40 members** across payments, cloud, and blockchain.

The premier members are the tell: **Adyen, Amazon Web Services, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, MoonPay, Ripple, Shopify, the Solana Foundation, the Stellar Development Foundation, Stripe, and Visa.** Having the major card networks, two hyperscalers, and the leading stablecoin issuers at the same table is what separates x402 from a single-vendor experiment. Read the roster as evidence of serious backing, not of settled dominance — the standard is months old and its final shape is still being written.

> x402 is not a wallet, a coin, or a checkout page. It is the missing verb in HTTP: a standard way for one machine to ask another for payment, and be paid, without a human clicking anything.

## Cards or stablecoins — what does x402 settle in?

Both, in principle; mostly stablecoins today. x402 began as a **stablecoin-native** scheme — Coinbase built it around on-chain settlement (USDC on Base), which is why early live volume clears in [stablecoins](/glossary/stablecoin). Under the Linux Foundation, the standard is written to be **payment-type-agnostic**, spanning "traditional cards to stablecoins," so a card network can settle an x402 request just as a wallet can.

The economics explain the current tilt. According to a Keyrock report covered by CoinDesk in May 2026, agent activity on the x402 scheme ran to roughly **176 million payments** with a median of **$0.01–$0.10**, and about **76%** fell below the ~$0.30 card-fee floor — sub-cent territory where [stablecoin settlement](/blog/stablecoins-agentic-payments) is economic and cards are not. Treat those figures as vendor-reported and directional. The durable point: x402 is the transport; the rail underneath can be a card or a stablecoin, and today it is mostly the latter.

## Where does x402 sit next to ACP and the payment rails?

At a different layer from each. It helps to separate the stack an agent purchase actually moves through:

| Layer | Example | Job |
|---|---|---|
| Discovery / being chosen | [Answer-engine optimisation](/glossary/answer-engine-optimization) | Whether an agent surfaces and picks your product at all |
| Checkout orchestration | [ACP](/blog/agentic-commerce-protocol-acp) (OpenAI + Stripe) | Completing an order inside an assistant like ChatGPT |
| Payment request | **x402** | The HTTP handshake that asks for, and confirms, payment for a resource |
| Settlement rail | [Cards or stablecoins](/blog/cards-vs-stablecoins-agent-payments) | Actually moving the money |

The [Agentic Commerce Protocol](/blog/agentic-commerce-protocol-acp) orchestrates a full shopping order inside chat; Google's **AP2** (Agent Payments Protocol) is a rail-agnostic agent-payment standard; the [card networks](/blog/agentic-commerce-payment-rails) and stablecoins are the rails that clear funds. x402 slots in as the payment-request handshake that can front any of them. None has converged into a single winner as of mid-2026, and a brand does not need to bet on one — the transaction layer is being built to be plural.

## What does x402 mean if you sell or publish online?

Two things, and only one is about commerce. For merchants, x402 is plumbing you will likely accept rather than integrate by hand — the work that decides revenue still happens a layer up, at whether an agent [chooses your product](/blog/what-is-agentic-commerce) in the first place. For **publishers and API owners**, x402 is more novel: it makes *charging* an AI agent for access a real option, sitting between "allow every crawler free" and "block them." That is the pay-per-crawl model, and it changes the calculus of [letting AI crawlers in](/blog/should-you-let-ai-crawlers-index-your-site).

Either way, the standard settles *how* an agent pays, not *whether* it picks you. Whether AI agents and answer engines actually surface and recommend your products is exactly what **Buffy Intel** measures, snapshot over snapshot. Questions: support@flash.tech.

## When do AI-referred visits arrive? Days after the prompt, not minutes
Source: https://heybuffy.com/blog/when-do-ai-referrals-arrive

Most AI-referred site visits arrive **days after the prompt, not minutes**, and they usually land through **search or direct traffic, not a labelled AI link**. Two independent 2026 datasets point the same way: Gener8's *Tracking Prompts to Site Visits* report found the prompt-to-visit rate climbs roughly 9x to 10x from one hour to 72 hours after a prompt, and Similarweb found an AI recommendation made people 2.5x more likely to visit a brand's site over the next seven days.

**Last reviewed: 10 August 2026.** The figures below come from two named sources: Gener8's *AI Landscape: Tracking Prompts to Site Visits* (July 2026) and Similarweb's *The Downstream Impact of AI Visibility* (published 21 June 2026). Both are large but **single-vendor and self-reported**, so treat the *direction* as firmer than any single percentage, and hedge anything you quote as "as of mid-2026." Gener8's data is mobile-first (Android in-app and mobile web; iOS excluded under Apple's policy), covers the US and UK, spans August 2025 to June 2026, and is weighted to census benchmarks by gender, age (18–64) and region.

## How long after an AI prompt do people visit a site?

The delay is the headline. Gener8 measured a **prompt-to-visit rate** — the share of AI prompts in a category that lead the same person to a relevant site visit within a set time window — at 1 hour, 24 hours and 72 hours after the prompt. In every vertical, the rate multiplied between **9x and 10.3x** from the 1-hour mark to 72 hours:

| Vertical (US) | 1 hour | 24 hours | 72 hours | 1h→72h multiple |
|---|---|---|---|---|
| B2B SaaS | 2.7% | 14.1% | 25.6% | ~9.5x |
| Consumer Electronics | 2.2% | 10.2% | 19.9% | ~9x |
| Home Improvement | 1.1% | 5.0% | 10.0% | ~9x |
| Apparel & Fashion | 0.7% | 3.5% | 7.2% | ~10.3x |

*Source: Gener8, AI Landscape (July 2026), mobile, US, Aug 2025 – Jun 2026.*

The takeaway Gener8 draws is blunt: **most of a prompt's eventual visits take days, not minutes to materialise.** An AI answer plants intent; the click that acts on it often comes later, once the person is ready to research or buy. If you judge an AI answer's impact by the traffic in the first hour, you are measuring a small slice of what it will eventually send.

## Which categories convert prompts to visits fastest?

The rate differs sharply by vertical — about **4x** between the top and bottom at 24 hours. Gener8's US 24-hour prompt-to-visit rates:

| Vertical | 24h prompt-to-visit rate |
|---|---|
| B2B SaaS | 14.1% |
| Consumer Electronics | 10.2% |
| Home Improvement | 5.0% |
| Apparel & Fashion | 3.5% |

*Source: Gener8, AI Landscape (July 2026), mobile, US.*

B2B SaaS leads at every time mark, which Gener8 reads as research-led intent rather than typical shopping behaviour: people investigating software follow the trail to a vendor's site more readily than people browsing apparel. The lesson for measurement is that a single blended "AI traffic" number blurs categories that behave nothing alike — segment by vertical before you benchmark yourself.

## Does the AI platform change the prompt-to-visit rate?

Yes, but the ranking is stable even as the size of the gap moves. Gener8 found **Google AI Mode had the highest prompt-to-visit rate across all four verticals**, with ChatGPT second in every one and Google Gemini third. The gap ranged from about 1.5x to 2.1x over the third-place platform:

| Vertical (US, 24h) | Google AI Mode | ChatGPT | Gemini |
|---|---|---|---|
| B2B SaaS | 20.4% | 16.2% | 11.0% |
| Consumer Electronics | 13.2% | 10.7% | 8.6% |
| Home Improvement | 7.5% | 5.9% | 3.6% |
| Apparel & Fashion | 5.0% | 3.9% | 2.7% |

*Source: Gener8, AI Landscape (July 2026), mobile, US. Google AI Mode, ChatGPT and Gemini only.*

Gener8 adds an important caveat: [Google AI Mode](/blog/how-google-ai-mode-works) is usually reached *inside* a Google search rather than opened as a standalone destination, so its traffic likely skews toward more navigational, ready-to-buy intent than a standalone ChatGPT or Gemini session. That framing may explain part of its lead — a reminder that platform comparisons measure the surface *and* the intent that arrives there.

## How do those visits actually reach your site?

Not as an AI referral you can see. Similarweb's *Downstream Impact of AI Visibility* study traced where AI-influenced visits landed and found most arrive through **search**, not a citation link:

| Arrival channel | AI-influenced visits | Visits with no AI influence |
|---|---|---|
| Via a search engine | 55.9% | 40.4% |
| Direct (no referrer) | 19.9% | 38.8% |

*Source: Similarweb, The Downstream Impact of AI Visibility (June 2026), US desktop panel, Jul–Dec 2025.*

The behaviour behind the numbers: someone reads a recommendation in an AI answer, then re-searches the brand or returns to it later — so the visit records as branded search or direct, not as a click from the assistant. This refines, rather than contradicts, the corpus's existing finding that AI traffic [hides in the "Direct" bucket](/blog/why-ai-traffic-shows-up-as-direct): both are true, and the through-line is that an AI-driven visit **rarely arrives as a labelled AI referral**. Similarweb also reported the impact is real — an AI recommendation made people **2.5x more likely** to visit that brand's site over the following seven days — and that those visitors viewed roughly twice as many pages and stayed roughly twice as long, corroborating the [independent finding that AI-referred traffic is more engaged](/blog/is-ai-traffic-more-valuable).

## Is this the same as the citation lag?

No — and keeping the two apart matters for reading your own data. There are **two distinct delays** on the AI funnel:

> The citation lag is the weeks between an AI bot crawling your page and the engine citing it in answers. The prompt-to-visit lag is the hours-to-days between a person reading that answer and clicking through to your site. A page can clear the first and still see its visits arrive slowly across the following week.

The [citation lag](/blog/chatgpt-citation-lag) is a supply-side delay (crawl, then index, then cite). The **prompt-to-visit lag** is a demand-side delay (see the answer, then act on it). Stacked, they mean a page you publish today may not be cited for weeks, and then may not send its full visit volume for days after each answer — so the honest measurement window for a new page is a quarter, not a fortnight, and shorter than that will read as failure when it is really just latency.

## What predicts a higher prompt-to-visit rate?

A geeky finding worth noting for anyone modelling this: Gener8 reported that **heavier search intensity predicts a higher prompt-to-visit rate**, but **heavier GenAI use does not**. The top 10% of users by search volume drove a prompt-to-visit rate roughly 2x to 4.3x higher than the lightest decile. Yet across three of the four verticals, prompt-to-visit rate stayed flat or declined as GenAI-use intensity rose. The read: the people most likely to act on an AI answer are heavy *searchers*, not heavy *AI users* — consistent with the fact that the visit itself so often arrives through search. It also squares with Gener8's market-level finding that search volume kept climbing (US searches per user up ~15%, UK up ~20% since August 2025) even as AI adoption surged — AI is adding a discovery step, not replacing the search that closes it.

## How should you use these figures?

Treat this as a **dated reference, not a promise**. Every number here is single-vendor and self-reported; cite Gener8 or Similarweb and the date when you reuse one, and prefer your own measured trend over any headline percentage. Because live retrieval favours recently-updated pages, we keep references like this on a [refresh cadence](/blog/content-freshness-citation-cliff) and update them substantively as new editions land.

The practical shift is in how you *measure*: widen your attribution window past the first click, expect the visit in search and direct rather than a labelled referral, and read AI's impact as a curve that builds over days. Doing that — tying which prompts and citations surface your brand to the delayed, indirect visits they eventually send — is exactly what **Buffy Intel** is built to track. Start with the companion how-to on [measuring AI visits that arrive days after the prompt](/blog/measure-delayed-ai-visits).

## Where do ChatGPT's product recommendations come from? What a 13,000-citation study suggests
Source: https://heybuffy.com/blog/where-chatgpt-product-recommendations-come-from

For product and brand recommendations, ChatGPT mostly recommends what already ranks. A 2026 master's-thesis study that captured **1,650 prompt iterations across GPT-5.2, 5.3 and 5.5 plus Gemini**: and traced the **13,000+ citations** behind the answers. Found that **roughly 80% of recommended products traced straight back to search rank**, and that ChatGPT's Business tier grounded its answers in **Bing's top ten**. The honest conclusion from the researcher: for product recommendations, SEO is not dead. It is the **baseline requirement**.

This piece reports what that study found, what independently corroborates it, and what it means for getting [recommended in ChatGPT](/blog/how-to-get-recommended-in-chatgpt), with the caveats stated first, because the specifics are single-study.

## What was the study, and how solid is it?

A single-author study, scoped to one domain, with rich internal detail. Directional, not definitive. The work was conducted by Ali Şan Kaya (co-founder of an AI speech-and-translation company) as a master's thesis, and shared publicly in June 2026. Its scope and limits matter as much as its numbers:

- **What it covered:** 1,650 prompt iterations across GPT-5.2, 5.3, 5.5 and Gemini; 370,000+ search results and 13,000+ citations captured behind the answers.
- **What it was scoped to:** a single domain the author knows well (AI speech and translation tools), so the findings are deep but narrow.
- **How to treat it:** single-author, self-reported, one product category, observed over early-2026 model versions. The *figures* are one study's; the *direction* is what carries weight, especially where other research agrees.

State that scope up front and the rest of the data becomes usable rather than overclaimed.

## What did the study find about where recommendations come from?

That retrieval, not mystery, drives most product recommendations, and that the retrieval source differs by ChatGPT tier. The reported findings:

| Finding | What the study reported | How to read it |
|---|---|---|
| Rank is the baseline | ~80% of recommended products traced straight back to search rank | The dominant lever for being recommended |
| Business grounds on Bing | Business-tier citations skewed to Bing's top ten | A Bing top-ten spot is close to a prerequisite |
| Plus reads Google | Plus tier appeared to read scraped Google results, looking deeper than the top ten | Tier choice changes the source pool |
| A non-search channel exists | ~12-15% arrived via a channel the study labels "labrador". Wikipedia, arXiv, tech press | Authority sources get cited outside ranked search |
| Listicles dominate | The #1 listicle item was picked ~2.5× more than chance | Independent roundups remain a primary medium |

The researcher reported that GPT-5.5 exposed its retrieval source through a parameter the study calls `result_source` (with values such as `bing`, `serp`, and `labrador`) and a rank position the study calls `ref_index`. Treat those parameter names as one researcher's observation of model behaviour at a point in time. They are exactly the kind of [volatile detail](/blog/content-freshness-citation-cliff) that can change between versions. The durable point underneath them does not change: the engine retrieves from ranked search, so ranking in that search is how you become eligible to be recommended.

## Does anything independent corroborate this?

Yes. The core "Bing rank shapes ChatGPT recommendations" finding is [corroborated](/glossary/corroboration) by separate work, which is what lifts it above a single anecdote. Seer Interactive reported that roughly **87% of ChatGPT citations align with Bing's top results**. A Search Engine Land case study (Nogami and Tannenbaum, 2026) examined 68 iterations of a hotels prompt and found that the property winning more of Bing's top URLs appeared in ChatGPT far more often than a comparably-rated competitor that won on Google. Different methods, same direction: for ChatGPT, **Bing visibility predicts citation** better than Google visibility does.

> Three independent studies in 2026 point the same way: for product recommendations, AI does not invent a new winner. It mostly surfaces whoever already ranks, and for ChatGPT that increasingly means Bing. SEO didn't die; it became the entry fee.

One honest caveat travels with all of it: there is a live debate about whether search rank *shapes* the answer or merely *supports* a recommendation the model already leaned toward from training. The practical advice is the same either way, but don't overstate causation from correlation. The same discipline that applies to [reading any visibility case study](/blog/how-to-read-an-ai-visibility-case-study).

## Why are dated listicles becoming the dominant citation medium?

Because the models increasingly search with the year in the query, and year-stamped roundups are what match. The study reported that on GPT-5.2 in early 2026, only about **5%** of the models' [fan-out](/blog/how-query-fan-out-works) searches carried a year token; by GPT-5.5 in May 2026 that had risen to roughly **80%** ("best transcription tools 2026" rather than "best transcription tools"). As the searches got year-stamped, the share of **listicles among cited URLs rose to become the dominant medium**: because freshly-dated "best of 2026" roundups are exactly what those queries return.

That matches what we already knew: [AI engines lean on independent roundups](/blog/why-ai-loves-listicles) for commercial-intent queries, and the position you hold *inside* a cited list shapes whether you are recommended. The reported 2.5× edge for the number-one slot is the [listicle effect](/blog/cited-vs-recommended-in-ai-search) quantified for products.

## What should brands actually do about it?

Treat strong classic search rank as the price of entry, then layer the AI-specific moves on top. In priority order:

1. **Earn the ranked spot. Especially on Bing.** If Business-tier ChatGPT grounds on Bing's top ten, then Bing rank for your category and its [fan-out branches](/blog/how-query-fan-out-works) is foundational. This is the clearest evidence yet that [ecommerce SEO still matters for AI search](/blog/does-ecommerce-seo-matter-for-ai-search).
2. **Pursue earned placement in independent, dated roundups.** Get into the genuinely third-party "best of 2026" lists. Never a self-serving roundup naming yourself first. The [how-to for cited best-lists](/blog/get-into-ai-cited-best-lists) is the method.
3. **Build the authority channel too.** The "labrador" findings. Wikipedia, arXiv, reputable tech press. Say [entity authority](/blog/entity-strength-ai) gets you cited outside ranked search. Corroboration across the web is the slow, durable lever.
4. **Keep dated content fresh.** With ~80% of fan-outs now year-stamped, a "best 2025" page quietly drops out of a "2026" query. Freshness is no longer cosmetic; it decides eligibility.
5. **Measure where it actually happens.** Track citations and recommendations per engine, including the [retrieval-augmented](/glossary/retrieval-augmented-generation) Bing pipeline ChatGPT leans on. The [answer-level metrics](/blog/from-clicks-to-citations), not just rank.

The synthesis lines up with the [six factors that make AI recommend a product](/blog/factors-ai-recommends-products): reachability and rank get you retrieved, corroboration and freshness keep you cited, specificity gets you picked. This study is strong evidence that the first link in that chain. Ranked, retrievable, especially on Bing. Is doing more of the work than most AI-visibility advice admits.

Knowing your products mostly trace back to search rank is only useful if you can see, per engine and over time, which ones surface and which fall out. Measuring that. Across ChatGPT, Gemini, Perplexity and Google's AI surfaces. Is exactly what **Buffy Intel** does. Questions: support@flash.tech.

## Where do AI citations come from? Earned media, owned pages, and paid content
Source: https://heybuffy.com/blog/where-do-ai-citations-come-from

Overwhelmingly from **earned media** — independent third-party coverage such as news, reviews, and forums, not the pages a brand publishes or pays for. In Muck Rack's May 2026 "What Is AI Reading?" analysis of over **25 million links** cited by ChatGPT, Claude, and Gemini, earned media drove about **84%** of citations, while paid or advertorial content accounted for just **0.3%**. This reference lays out the source-type breakdown, how it differs by engine, and what it means for where you spend your [GEO](/glossary/generative-engine-optimization) effort.

**Last reviewed: 25 August 2026.** All figures below are from Muck Rack's "What Is AI Reading?" study (May 2026 edition, the third since July 2025) unless noted. It is a **single-vendor** analysis across three engines, so treat the direction as firm and any single percentage as directional, and cite "Muck Rack, 2026" with the date when you reuse a figure.

## Where do AI engines get the sources they cite?

Mostly from earned media, by a wide margin, with paid content almost nowhere. Here is the headline split across the 25 million-plus cited links Muck Rack analysed:

| Source type | Share of AI citations | Note |
|---|---|---|
| Earned media (total) | ~**84%** | Independent third-party coverage |
| Journalism (subset of earned) | ~**27%** | Across 20,000+ distinct outlets |
| Paid / advertorial | ~**0.3%** | Effectively negligible |

Source: Muck Rack "What Is AI Reading?", May 2026. The one-line summary: AI engines assemble answers out of what independent third parties have said, not out of what brands say about themselves or pay to place. That is the same pattern behind why independent [best-of lists](/glossary/best-of-list) get cited far more than brand-owned pages for commercial "best X" queries.

## Does the earned-media dominance hold across engines and over time?

Yes on both counts, which is what makes it worth planning around. Across three editions of the study since July 2025, earned media's share stayed in an **82–89%** band and journalism in a **25–27%** band — a stable pattern, not a single snapshot. But *which* sources each engine reaches for varies sharply:

| Engine | Cites sources in… | Avg. citations when it cites | Top cited domain |
|---|---|---|---|
| ChatGPT | ~96% of responses | ~5 | Wikipedia |
| Gemini | ~82% of responses | ~8 | Reddit |
| Claude | ~55% of responses | ~13 | PubMed Central |

Source: Muck Rack, 2026. Note this counts *cited links shown per response* on Muck Rack's corpus, which is a different measurement from the *sources pulled per answer* reported elsewhere — Semrush's 2026 index put [ChatGPT at about 15 sources and Gemini at about 3](/blog/how-many-sources-ai-engines-cite) using its own method. Read the two as complementary cuts, not conflicting numbers: the metrics, corpora, and dates differ, so do not stack them. The durable takeaway is the shape — the same earned-media dominance flows through a different favourite source on each engine, and one engine's staple (Reddit for Gemini, PubMed Central for Claude) can be near-absent on another. One more per-engine marker: Muck Rack found Axios in ChatGPT's top three cited domains across 13 of 17 industries.

## Why do AI engines lean on earned media instead of your own pages?

Because independent coverage is the [corroboration](/glossary/corroboration) signal engines trust most. A claim a brand makes about itself is one voice; the same claim carried by journalists, reviewers, and forums is many independent voices, which is exactly the evidence an answer engine weights when it decides whom to cite. Muck Rack's own read is consistent across editions: earned media is the dominant input, and it also found press releases appearing about 3.5 times more often in industry-trend answers than in "best-of" answers, so the *type* of earned coverage that lands depends on the question being asked.

This is why [earned media](/glossary/earned-media) is the durable lever and why faking it backfires — manufactured coverage reads as manipulation and can trigger penalties rather than citations.

## Does this mean your own pages don't matter?

No — it means owned and earned pages win different jobs. Muck Rack's ~84%-earned figure sits alongside a second finding from its 2026 State of PR survey that roughly **99%** of AI citations come from non-paid sources. The two reconcile cleanly: paid is ~0.3%, so nearly everything is non-paid, and within that non-paid pool earned media is the ~84% majority and brand-owned pages are the remainder. Owned pages still earn the [first-party citations](/glossary/first-party-citation) that matter for brand- and feature-specific questions, where your own site is the authoritative source.

> Earned media is how AI answers decide who to trust; owned pages are how they get the facts right. You need both, and paid placement earns you almost neither.

There is a live wrinkle worth dating: on **ChatGPT specifically**, a mid-2026 shift toward [fetching first-party domains directly](/blog/is-chatgpt-citing-fewer-listicles) after GPT-5.6 is nudging more of its citations toward brand-owned pages. That is an engine-specific, post-May-2026 movement, and it does not overturn the cross-engine, through-mid-2026 earned-media dominance measured here — it is a trend to watch alongside it, not a contradiction of it.

## What does this mean for your GEO strategy?

Spend where the citations actually come from: earned first, owned for the facts, paid almost never.

- **Pursue earned placement for evaluative and "best X" questions.** Independent reviews, journalism, and community coverage are where ~84% of citations originate — see [how to get into AI-cited best lists](/blog/get-into-ai-cited-best-lists) and how to [use Reddit for AI-search visibility](/blog/how-to-use-reddit-for-ai-search-visibility).
- **Keep owned pages clean and factual for brand and feature queries.** Server-rendered, extractable specs and pricing are what an engine lifts when it does cite your domain — the discipline in [prioritising your structured data](/blog/prioritize-your-structured-data).
- **Do not buy your way in.** At ~0.3% of citations, paid and advertorial content is the weakest AI-visibility lever there is.
- **Measure per engine.** Because each engine leans on a different top source, track ChatGPT, Gemini, and Claude separately rather than trusting one blended number — the reasoning in [who owns AI search visibility](/blog/who-owns-ai-search-visibility).

The honest read for late 2026: the source of an AI citation is far more often something a third party wrote about you than anything you published or paid for — so earned credibility, not self-promotion, is the core of AI visibility. Watching which earned and owned sources actually get cited for your brand, per engine and over time, is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## Where on a page do AI engines quote from? Position, length, and citation survival
Source: https://heybuffy.com/blog/where-on-a-page-do-ai-engines-quote-from

**Overwhelmingly from the top of the page.** In MaxAEO's 2026 controlled study, an identical claim placed in a page's intro survived into AI answers about **72%** of the time, versus about **24%** for the same claim mid-page — and on pages over **4,500 words**, mid-page claims survived just **9%** of the time while top-of-page claims held near **68%**. This reference lays out the position-and-length data and why the fix is leading each section, not writing shorter, for [extractability](/glossary/extractability).

**Last reviewed: 29 August 2026.** All figures below come from MaxAEO's "Page Length and AI Citations" study (2026): three topics in five depth variants (fifteen guides of 2,900-5,200 words), each probed with about 80 query phrasings across six AI surfaces (ChatGPT, Perplexity, Google AI Overviews, Gemini, Copilot), about **1,200 answer observations** over four weeks in June-July 2026. A single distinctive claim was rotated through five page positions using a Latin-square design; "survival" meant the claim appeared verbatim or paraphrased in the answer. It is a **first-party, controlled, directional** study — cite "MaxAEO, 2026" with the date, and note engines shift weekly and the topics lean B2B.

## Where on a page are AI engines most likely to quote from?

The start, by a wide margin, with a small lift at the end. Here is how the same claim fared at five depths:

| Position in page | Claim survived in answer | Cited with a link |
|---|---|---|
| Intro (top ~5%) | ~72% | ~61% |
| ~25% depth | ~51% | ~43% |
| ~50% depth (middle) | ~24% | ~18% |
| ~75% depth | ~38% | ~29% |
| Conclusion | ~46% | ~37% |

Source: MaxAEO, 2026. The shape is a U that heavily favours the opening: an intro claim survived roughly twice as often as a mid-page one. This matches the sibling finding that [64% of quoted passages are the first or second sentence of their section](/blog/what-content-do-ai-engines-quote-most) — engines reach for what sits early, both in the page and in each section.

## Do long pages get quoted less by AI?

Not at the top — only in the middle. Length barely touched top-of-page claims but steadily crushed mid-page ones:

| Page length | Middle-claim survival | Top-claim survival |
|---|---|---|
| 1,000-1,800 words | ~41% | ~78% |
| 1,800-3,000 words | ~27% | ~73% |
| 3,000-4,500 words | ~16% | ~70% |
| 4,500+ words | ~9% | ~68% |

Source: MaxAEO, 2026. Read the two columns together: a top claim held near 68-78% no matter how long the page ran, while a middle claim fell from about 41% to about 9% as the page grew. The lesson is not "write less" — it is that depth on the page is where citations go to die, so a long page needs every section to earn its own place at the top.

## Does this contradict "coverage, not length"?

No — it sharpens it. The finding that [content length is not the lever, coverage is](/blog/does-content-length-affect-ai-citations) says a comprehensive page wins by answering more of the sub-questions a query [fans out](/glossary/query-fan-out) into. This study adds the mechanism: a long page only captures those branches if each branch's answer is front-loaded in its own section. Because engines retrieve at the [passage level](/glossary/content-chunk), every section is a separate candidate, so "put it at the top" applies to each [chunk](/glossary/content-chunk), not just the document. That is exactly the answer-first, one-question-per-section structure the [extractable-chunks how-to](/blog/structure-content-into-extractable-chunks) prescribes — the position data is why it works.

> On the page as a whole, the middle is where citations go to die. The fix is not a shorter page — it is a page where every section leads with its answer, so each chunk is "at the top" of itself.

## What should you do about page position?

Structure long pages so no fact depends on where it sits in the scroll.

- **Lead the page with your single most important claim.** The intro is where survival peaks (~72%); do not build up to the point.
- **Front-load every section, not just the intro.** Each section is its own retrieval candidate, so put its answer in the first sentence and let the detail follow.
- **Split any section where the key fact has drifted past the halfway mark.** If it reads like two questions, it is two [chunks](/glossary/content-chunk) — give each its own answer-first opening.
- **Keep the page as long as coverage requires, no longer.** Length is safe when structure is right; it is unstructured depth, not word count, that loses citations.
- **Measure per engine after restructuring.** Track your [citation coverage](/glossary/citation-coverage) engine by engine, since none reports which passage it pulled.

The honest read for late 2026: a fact's odds of being quoted depend as much on *where* you put it as on *what* it says — and on a long page, only the front of each section is reliably in play. Watching whether a restructure actually moved your citations, engine by engine, is exactly what **Buffy Intel** measures. Questions: support@flash.tech.

## Which content formats survive in AI citations? The 'content graveyard' data
Source: https://heybuffy.com/blog/which-content-formats-survive-ai-citations

**In a 2026 study of 2.4 million AI citations, only 2.7% of domains held a citation across all seven months, while 57.2% were cited in a single month and then never again — and the thing that separated the survivors was content format, not brand size.** Somantra AI's "Content Graveyard" analysis found that comparison, FAQ, how-to and pricing pages persisted at roughly twice the rate, while pages labelled a "complete guide" were about 3.5x more common among the domains that vanished after one [citation](/glossary/citation).

**Last reviewed: 18 August 2026.** All figures below come from Somantra AI's *Content Graveyard* analysis (published 17 August 2026), a single-vendor read of one sector (Australian insurance) across ChatGPT and Google over seven months. It is directional, not definitive — cite "Somantra AI, 2026" with the date when you reuse a number, and treat the *pattern* (format predicts durability) as firmer than any single multiple.

## What did the 'content graveyard' study find?

That most of the web an AI engine cites is cited once and then forgotten. Somantra AI tracked **2,437,107 citation records across 28,725 domains** on ChatGPT and Google AI Overviews over a seven-month window (reported as November 2025 to July 2026) in the Australian insurance sector. The headline split is stark.

| Metric | Value |
|---|---|
| Citation records analysed | **2,437,107** |
| Distinct domains tracked | **28,725** |
| Engines | ChatGPT, Google (AI Overviews) |
| Window | **7 months** (Nov 2025 – Jul 2026, reported) |
| Cited in exactly one month, never again | **57.2%** of domains |
| Cited in all seven months | **2.7%** of domains |
| Sector | Australian insurance |

Source: Somantra AI, *Content Graveyard*, 2026. The one-line read: **being cited once is common and cheap; staying cited is rare.** Because it is one vendor measuring one vertical, read the magnitudes as directional — but a >20:1 ratio between one-and-done and always-present domains is a large effect by any measure, and it reframes the goal from *getting* cited to *staying* cited.

## Which formats survived, and which vanished?

The gap between the "content graveyard" and the durable minority was separated by format, not by how big the brand was. Structured, comparative and specific pages persisted; generic long-form guides did not.

| Content format | Citation behaviour |
|---|---|
| **Comparison-table** content | Among long-term survivors at ~**2x** the rate of one-citation domains |
| **Pricing / discount / savings** pages | ~**2x** more common among long-term survivors |
| **FAQ and how-to** pages | Correlated with persistence across the seven-month window |
| **"Complete guide"** pages | ~**3.5x** more common among domains that vanished after a single citation |

Source: Somantra AI, 2026. The pattern is consistent: the formats that survived are the ones that hand a model a clean, self-contained, specific answer — a row in a comparison, a priced option, a direct question-and-answer. The format that vanished is the one that buries the answer inside sprawling prose. As the study's authors put it, the differentiator is reproducible precisely because it is not about brand size:

> "If persistence tracked brand size, a smaller insurer would have no route into a durable citation position. Because it tracks format, the formula is reproducible."

## Does this mean long-form content is dead?

No — and this is where the finding is easy to misread. A separate 2026 analysis of AI-Overview citations found that word count barely predicts whether a page is cited at all; the real lever is **coverage**, because comprehensive pages answer more of the sub-questions a [query fans out](/glossary/query-fan-out) into, as we covered in [does content length affect AI citations](/blog/does-content-length-affect-ai-citations). Length and citation *capture* travel together only because thorough pages cover more branches.

The "content graveyard" data is about a different axis: **durability**, not capture. A long "complete guide" can win a citation on breadth this month and lose it next month, because a generic guide is interchangeable — a dozen other guides say the same thing, so the engine has no reason to keep choosing yours. A comparison table with your specific numbers, or an FAQ that answers one exact question, is harder to swap out. So the lesson is not "write less." It is: **make each section a specific, self-contained, comparative answer** — the [extractable chunk](/glossary/content-chunk) a model keeps selecting — rather than one long undifferentiated read.

## Why would format predict citation survival?

Because retrieval and citation happen at the passage level, and structured formats win the passage-level contest repeatedly. Three mechanisms line up.

1. **Extractability.** A model gathering candidate passages keeps the ones with clean boundaries — a table row, a priced line item, a Q-and-A pair — over a point buried mid-paragraph. Structured formats are pre-chunked; a "complete guide" makes the engine do the chunking, and an easier source usually wins.
2. **Specificity.** Comparison and pricing pages carry named, numeric, dated facts. Those are exactly the claims engines lift and the ones least likely to be duplicated by a competitor's generic page, so they hold their position longer.
3. **Reproducible substitution.** When the cited pool [churns](/glossary/citation-turnover), the engine replaces a source with the next-best answer to that sub-query. A generic guide has many near-identical substitutes; a specific comparison or spec table has fewer, so it survives more rounds of substitution.

Note these are correlational — Somantra observed format travelling with persistence, not a controlled experiment isolating format as the cause. But the mechanism is the same one that governs how [answer engines](/glossary/retrievability) select any chunk, which is why the direction is credible.

## Does this contradict our citation-turnover and freshness pieces?

No — it completes them. We have written that the cited pool churns fast (only about 10.6% of URLs survived six weeks in [how long AI citations last](/blog/how-long-do-ai-citations-last)) and that live retrieval favours [recently-updated pages](/blog/content-freshness-citation-cliff). Those pieces answer *how much* the pool turns over and *how fast a page decays*. The "content graveyard" data answers a third question: **given that the pool churns, who survives it?** The reconciliation is clean:

- **Turnover** says the set of cited sources is mostly replaced within weeks — true across studies.
- **Freshness** says stale pages get displaced first — a timing lever you control by updating.
- **Format durability** says that among pages competing to be re-cited, structured and specific formats win more rounds — a *structural* lever you control by how you write.

None of these say a citation is permanent. Together they say the same thing from three angles: **a citation is a position you defend**, and the defensible positions are fresh, specific, and structured. There is no contradiction — freshness is the clock, format is the moat.

## What should you actually do about it?

Publish for durability, not just for the first citation. The practical moves follow directly from the data:

1. **Vary the format deliberately.** Don't default every page to a long explainer. Mix in comparison tables, FAQ blocks, how-to steps, and pages that carry specific pricing or spec data — the formats that persisted.
2. **Pre-chunk your own pages.** Inside any long guide, break the answer into self-contained, question-led sections with tables and lists, so the engine lifts a clean unit instead of skipping the page.
3. **Be specific where competitors are generic.** Named, numeric, dated facts are both more citable and more durable, because they are harder to substitute.
4. **Watch durability, not just presence.** A single [citation](/glossary/citation-coverage) snapshot tells you nothing about whether you'll be there next month. Track [share of voice](/glossary/share-of-voice) and citation coverage as trends across many prompts and engines, and refresh the pages that matter before they age out.

The mistake the "content graveyard" exposes is treating a first citation as the finish line. On this data, most domains reach that line once and never return — and the ones that stay did it by publishing formats a model could keep choosing.

---

Buffy Intel tracks which of your pages are cited across AI engines, and — just as importantly — whether they *stay* cited over time, so you can see the difference between a one-month appearance and a durable position. If you want to know which of your formats are surviving the churn and which are already in the graveyard, [start with Buffy Intel](https://heybuffy.com) or reach us at support@flash.tech.

## Who owns AI search visibility? What the 2026 PR data says about the GEO ownership gap
Source: https://heybuffy.com/blog/who-owns-ai-search-visibility

In most organisations, no one clearly owns AI search visibility. Even though most agree it matters. **Muck Rack's 2026 State of PR report**, published 9 July 2026, found that **73%** of PR professionals call AI search visibility (also called [generative engine optimisation](/glossary/generative-engine-optimization)) at least somewhat important, yet **29%** say no one at their organisation owns it and **39%** aren't measuring it at all. That gap between importance and accountability is the story.

**What this data is, and isn't.** Muck Rack surveyed 1,115 PR professionals between 14 May and 12 June 2026, with 971 qualified responses. It measures practitioner *perception* inside the PR function, not audited business outcomes, so read it as a directional snapshot of how one profession sees the problem in mid-2026. The pattern it describes, though, matches what we see across teams: a new discipline that no existing job description quite covers.

## Who actually owns AI search visibility today?

Usually nobody, by name. The Muck Rack numbers describe a classic orphaned-discipline pattern. High stated importance, low assigned ownership, weak measurement:

| Finding (Muck Rack 2026 State of PR) | Share |
|---|---|
| Call AI search visibility strategically important | 73% |
| Say **no one** at the organisation owns GEO | 29% |
| Aren't measuring GEO success at all | 39% |
| Prioritise securing high-authority publication coverage | 55% |
| Focus on data-driven content and SEO | 50% |

Source: Muck Rack 2026 State of PR report (971 qualified responses, fielded 14 May-12 June 2026, reported 9 July 2026). The takeaway is not that teams don't care. Three in four do, but that caring hasn't turned into an owner or a scoreboard.

## Why is GEO ownership falling through the cracks?

Because AI search visibility spans three functions that rarely share a metric. It sits in the seams between them:

- **Earned media (PR / comms)**: earning third-party mentions, reviews, and coverage that engines cite.
- **Technical (SEO / web)**: making sure AI crawlers can reach, render, and extract those pages, and your own.
- **Content**: publishing the answer-first, extractable material engines lift from.

Each team owns one lever and none owns the outcome. When a brand is described wrongly in ChatGPT or missing from a Perplexity answer, PR points at SEO, SEO points at content, and the [citation](/glossary/citation) gap persists. This is the same "GEO builds on SEO, it doesn't replace it" point from [is GEO just SEO?](/blog/is-geo-just-seo). The disciplines overlap, so the ownership has to be deliberate rather than assumed.

## What does "99% of AI citations come from earned sources" mean for ownership?

It gives PR and communications a genuine claim to the lever, and a reason to partner with SEO rather than fence off the work. Muck Rack reports that roughly **99% of AI citations originate from non-paid, [earned](/glossary/earned-media) sources**, which lines up with the wider finding that independent listicles and third-party pages get cited far more often than brand-owned pages for commercial queries (see [how to get into AI-cited best-of lists](/blog/get-into-ai-cited-best-lists)).

> AI search visibility is not a channel one team can own alone. It is an outcome three teams produce together. Earned coverage, crawlable pages, extractable content, and it needs one person accountable for the result.

So earning coverage matters enormously, but earned coverage only helps if engines can crawl and cite it. That is why a purely-PR framing fails and a purely-technical one does too. The practical work is covered in [how to get named in AI answers](/blog/how-to-get-named-in-ai-answers) and [how to get cited by AI](/blog/how-to-get-cited-by-ai). Both of which cut across PR, SEO, and content.

## How should you assign ownership?

Assign one accountable owner over a shared metric, then let each team contribute its lever. A starter operating model:

1. **Name one accountable owner.** Not a committee. A single person answerable for the brand's AI-visibility metric. Where they sit (PR, SEO, or a dedicated role) matters less than that the seat exists.
2. **Agree one shared scoreboard.** Presence, [citation](/glossary/citation) share, and sentiment across the engines your buyers actually use. The metric set in [how to measure AI visibility](/blog/how-to-measure-ai-visibility). If 39% aren't measuring, this step alone is a lead.
3. **Map levers to teams.** PR owns earned coverage; SEO owns crawlability and structure; content owns extractable answers. Each reports into the shared scoreboard.
4. **Put it on a cadence.** A recurring review, not a one-off audit. The discipline in the [weekly AI-visibility routine](/blog/weekly-ai-visibility-routine).

The point is to convert 73%-say-it-matters into one-person-owns-it. Importance without an owner is how a discipline stays invisible inside the org even as it decides whether the brand is visible outside it.

## What happens if you leave it unowned?

The brand's AI presence drifts by default. No owner means no one notices when a competitor starts showing up in ChatGPT recommendations, when an engine adopts a wrong description, or when a CDN change quietly [blocks an AI crawler](/blog/is-your-cdn-blocking-ai-crawlers). Each of those is fixable, but only if someone is watching the [share of voice](/glossary/share-of-voice) and holds the number.

Closing the ownership gap starts with the scoreboard everyone can share. Knowing whether ChatGPT, Google's AI surfaces, Claude, and Perplexity actually find, cite, and recommend your brand. Tracked across engines over time, in one place PR, SEO, and content can all read. Is exactly what **Buffy Intel** is built to give a team. Make the number visible, and ownership follows. Questions: support@flash.tech.

## Why AI cites one brand and ignores a near-identical competitor
Source: https://heybuffy.com/blog/why-ai-cites-one-brand

Here's a scenario every brand eventually hits: you and a competitor publish near-identical posts on the same topic. Theirs gets quoted by ChatGPT and Perplexity. Yours never shows up. Same words, opposite outcome. Why?

The text reading "similar" to a human is not what the model retrieves on. The reasons split into two layers.

## Layer 1: the content & brand

Several things separate the cited post from the invisible one, and most have little to do with the prose:

- **[Entity strength](/glossary/entity-authority) of the *brand*, not the post.** Engines lean heavily on how well-established you are as an entity. Brand search volume, a Wikipedia/Wikidata presence, how often your brand co-occurs with the topic across the web. If your competitor is already a recognised name for "expense cards" and you aren't, their post inherits that authority even with identical wording.
- **Off-site corroboration.** There's a strong, documented bias toward third-party authoritative sources. If a claim is echoed on Reddit, G2, news, and review sites, the model treats it as corroborated and is comfortable citing it. The same claim sitting only on your own site reads as a lone, self-interested assertion.
- **Specificity.** Engines favour verifiable, numeric, named claims. *"Cut onboarding from 9 days to 36 hours across 1,200 customers"* gets pulled; *"streamlines onboarding"* doesn't. Even in otherwise similar posts.
- **Structural retrievability.** Retrieval works on **passages**, not whole pages. A post that answers the question in one clean, self-contained chunk. Clear question-style headings, an answer-first paragraph, schema markup. Beats one where the answer is diffused across the page.
- **Freshness.** There's roughly a **three-month citation cliff**: recently updated content gets favoured, and "publish and forget" posts decay. A refreshed page holds its citations.
- **Crawler access.** The mundane, decisive one: if the competitor is retrievable and you're blocking the crawler (or got caught by a [CDN default-block](/blog/is-your-cdn-blocking-ai-crawlers)), your content simply isn't in the index.

## Layer 2: the platform

Even with identical content, the engines don't share one mechanism, so outcomes legitimately differ:

- **Trained-in vs. retrieved-live.** A post absorbed into a model's training data (directly or via Common Crawl) can be "known" without any live search. A post that missed that window only appears if it's in the live index. Your competitor might be cited simply because they made an older training snapshot you didn't.
- **Different retrieval backends.** Perplexity and ChatGPT-search run their own real-time indexes and favour fresh, well-structured pages with clean source links. Google's AI Overviews lean on Google's existing index and classic ranking signals. Gemini weights the Google ecosystem. The same page can rank in one and not another.
- **Different source policies.** Some engines over-weight earned media and high-authority domains; some prefer recency. Perplexity is notably citation-hungry; ChatGPT is more selective; AI Overviews favour entities already strong in Google.
- **Different crawler permissions.** Allow `OAI-SearchBot` but block `ClaudeBot`, and you'll appear in ChatGPT but be absent from Claude. Purely a `robots.txt` artifact, not a quality signal (see [the crawler lifecycle](/blog/ai-crawler-lifecycle)).

## How to actually diagnose it

Don't guess. Compare:

1. **Crawler access** for both URLs (robots.txt + CDN + rendering).
2. **Index presence:** ask the same prompt across ChatGPT, Claude, Perplexity, and Gemini and log who gets cited.
3. **Off-site mentions** for each brand + topic.
4. **Structural & specificity signals** on each page.

> If the gap is consistent across every engine, it's content or entity strength. If it's specific to one or two engines, it's almost always crawler access or index coverage. The easier of the two to fix.

That cross-engine comparison. Same questions, tracked over time, logging exactly who gets cited and where. Is precisely what **Buffy Intel** does, so you're acting on a diagnosis instead of a hunch.

## Why AI loves listicles (and what brands should do about it)
Source: https://heybuffy.com/blog/why-ai-loves-listicles

If you've watched which pages AI engines actually cite, one format dominates: the listicle. The "best CRMs for startups," "top 10 expense cards," "X vs Y" roundups. And it's not close.

## The numbers

Multiple 2026 analyses. Including Search Engine Land's AI-citations study and AirOps' *2026 State of AI Search*. Converge on the same pattern (figures vary by study and shift over time):

- Third-party sources are cited roughly **6.5× more often** than brand-owned pages.
- **Listicles are the single most-cited format**: around **22-25%** of all citations, and roughly **40% of commercial-intent** citations (the "best X for Y" questions where a buyer is deciding). Brand product pages sit far lower, around **14%**.
- Nearly **90%** of third-party brand mentions originate from listicles, comparison pages, and review roundups.

## The mechanism, not just the stat

When a user asks *"what's the best expense card for startups,"* the model wants a **neutral-looking, multi-option** answer. A page that already lists several brands against criteria matches that shape perfectly. It reads as a survey of the market.

A page that lists only *your* products reads as a sales page, which the model is trained to treat as biased and therefore weaker as a citation. The roundup also has higher **entity density** (multiple named brands co-occurring with the category) and usually more verifiable specifics. Both things retrieval favours.

## Where each type wins

This doesn't mean owned content is pointless. It means it has a different job:

- **Listicles win discovery & commercial intent.** "best / top / vs / alternatives" queries. If you're not *in* those third-party lists, you're largely invisible for the highest-intent buyer questions. No matter how good your own blog is.
- **Your own pages win brand & feature queries.** "how does X work," "X pricing," "does X integrate with Y." Here the model wants the canonical first-party source, and that's you.

> The trap is writing more self-listing posts to compete with roundups. You'll lose. A brand blog that lists only its own products can't out-neutral an independent comparison.

## Has this changed on ChatGPT? (the GPT-5.6 shift)

The baseline above is cross-engine and about *which format wins a "best X" answer* — it still holds. But on ChatGPT specifically, the listicle premium narrowed after the **GPT-5.6** model became the default in mid-to-late 2026. A Peec AI before-and-after analysis (same ~1M prompts, week-before vs week-after the rollout, 2026) found the share of **listicles cited by ChatGPT fell about 50.5%**, and comparison pages about **32.1%**. The cause was not a demotion of roundups but a change in *how* the model searches: it issued fewer "top"/"vs" fan-out queries, generated about 154% more searches per chat, cited roughly twice as many sources per chat (~25.55 vs ~12.48), and increasingly used the `site:` operator to pull facts straight from [first-party pages](/glossary/first-party-citation). So listicles became a smaller slice of a larger, more first-party citation set — [ChatGPT is citing fewer listicles, in detail here](/blog/is-chatgpt-citing-fewer-listicles).

This does not overturn the strategy — it sharpens it. It is single-vendor, directional, and ChatGPT-specific (Google's AI Overviews and Perplexity still lean hard on third-party roundups). The read: **keep earning listicle placement for discovery and other engines, and make your own pages a clean, citable first-party source** so ChatGPT can lift them when it goes straight to your domain.

## The strategy that follows

1. **Get placed *into* the independent roundups.** Earned media. Being included in "best [category] tools" lists, review sites, and comparison content. Is higher leverage than trying to out-rank them with your own page. This is the single biggest move for commercial-intent visibility.
2. **Reserve owned content for what owned content wins:** brand-specific and feature-specific questions, plus genuinely educational explainers (like this one) that build entity strength.
3. **Mind the platform split.** Perplexity and Google's AI Overviews lean hardest on third-party roundups; ChatGPT leaned that way too but has been shifting toward first-party sources since GPT-5.6 (above); results also vary by region (US answers cite Reddit and listicles heavily). The same question can favour the roundup on one engine and your page on another, [which is why you measure across engines](/blog/why-ai-cites-one-brand).

The net for most brands: for "which is best" buyer questions, the multi-brand listicle wins decisively, so the work isn't more self-promotion, it's **getting into the comparison content that already gets cited**, and then tracking whether it's working across every engine. That tracking is what **Buffy Intel** is for.

## Why AI Mode users search in attributes, not keywords
Source: https://heybuffy.com/blog/why-ai-mode-users-search-in-attributes

AI Mode users have stopped typing keywords and started naming exact attributes. Instead of "flights to Lisbon", they ask for "nonstop flights to Lisbon under a set budget in March"; instead of "restaurant near me", they ask for one "with outdoor seating and vegan options". This is a direct consequence of how [Google AI Mode](/glossary/google-ai-mode) changed search behaviour, and it changes which pages get cited: the ones that expose the exact attributes a model can match against.

This piece explains the shift and what to do about it. It draws on Google's own AI Mode usage data (dated mid-2026, platform-reported, not independently audited) and applies the corpus method, so read the direction as firmer than any single number. For the raw figures see the [AI Mode usage data reference](/blog/google-ai-mode-usage-data-2026); this is the "why it matters" companion.

## Why did search shift from keywords to attributes?

Because the query format changed. A keyword search compresses intent into two or three words and leaves the rest implied; a [conversational](/glossary/conversational-search) AI Mode query states the whole requirement in a sentence. Google reports three behavioural shifts that push people toward naming attributes:

| Shift | Google's figure (mid-2026) | Why it produces attributes |
|---|---|---|
| Longer queries | Average AI Mode query is about **3× the length** of a classic search | More words means room to name filters, not just a topic |
| Conversational follow-ups | Follow-ups grew **more than 40% per month** | Each turn adds or refines an attribute |
| Multimodal input | More than **1 in 6** searches use voice or images | Spoken and image queries carry natural, detailed phrasing |

Source: Google, AI Mode U.S. Insights report (mid-2026). The pattern is the same across the [query fan-out](/glossary/query-fan-out): one request splits into attribute-level sub-questions ("nonstop?", "under budget?", "in March?"), and the engine assembles the answer from pages that satisfy each attribute. This is the search-behaviour side of [multimodal search](/glossary/multimodal-search): people say more, so they specify more.

## What does an attribute query look like across verticals?

The same behaviour shows up wherever people use AI Mode to decide or plan. Google's report and trade coverage of it name the concrete attributes people specify in three categories:

| Vertical | Attributes people specify | Source |
|---|---|---|
| Shopping | Price, location, colour, brand, availability, size, material, style, type, quality | Google, AI Mode U.S. Insights (mid-2026) |
| Dining | "Outdoor seating", "vegan options", "private party room" | Google report, as summarised by CMSWire (mid-2026) |
| Travel | Nonstop, budget band, season, family-friendly, walkable, accessible | Illustrative, from Google's travel/planning findings |

The shopping attributes are Google's own ordered list, reused from the [usage-data reference](/blog/google-ai-mode-usage-data-2026); the dining examples come from trade coverage of the report, so treat them as directional; the travel examples are illustrative of the same pattern, not a Google-published list. The through-line: whatever your category, buyers now state the properties they filter on, and the page that names those properties is the one a model can match.

> When a query names an attribute, only a page that names the same attribute can be lifted to answer it. Vague copy is not just weaker: it is invisible to the sub-question, because there is nothing for the model to match.

## Why do vague pages lose attribute queries?

Because retrieval and [citation](/glossary/citation) happen at the passage level, and a model matches an attribute in the query against an attribute stated on the page. "Great for families" cannot answer "hotel with a pool and connecting rooms"; "premium materials" cannot answer "waterproof and under a set price". The specific loses to nothing here, because the attribute simply is not present to be found. Three failure modes are common:

- **The attribute lives only in an image** (a spec chart, a menu photo), where a text-first crawler cannot read it.
- **The attribute is implied, not stated** ("comfortable for longer trips" instead of a named seat pitch or legroom figure).
- **The attribute is buried** mid-paragraph instead of in a table or list where it can be extracted cleanly.

Exposing attributes is the same discipline as [getting cited by AI](/blog/how-to-get-cited-by-ai): make the facts explicit, [corroborated](/glossary/corroboration), and structured.

## How do you expose the attributes AI engines match against?

State them as facts, in the formats a model can lift. This is the cross-vertical version of the product-attribute work in the [shopping playbook](/blog/optimize-for-ai-mode-shopping) and the place-attribute work in the [travel playbook](/blog/optimize-for-ai-mode-travel):

1. **List the attributes your buyers actually filter on.** Price, size, availability, dietary options, season, accessibility, whatever the category's [attribute queries](/glossary/attribute-query) name.
2. **Put them in text and tables, not only images.** A spec table beats a spec graphic every time for extraction.
3. **Add [structured data](/glossary/structured-data)** (Product, Offer, or the relevant type) so machines read the attribute as a labelled fact, not a guess.
4. **Answer the attribute follow-ups**, since AI Mode users refine conversationally: cover "and under budget?", "and nonstop?", "and vegan?" as their own chunks.
5. **Keep volatile attributes current and dated**, because live retrieval favours recently-reviewed pages.

## How should you measure this?

Track whether you appear for the attribute-level questions, not just the head term. A brand can rank for "hotels in Lisbon" and vanish the moment the query adds "with a pool and family rooms", because the page never named those attributes. So measure recall across the [fan-out](/blog/how-query-fan-out-works) of attribute follow-ups, and do it per engine and over time rather than spot-checking one prompt. That is exactly what **Buffy Intel** is built to measure: whether AI Mode and every other major engine surface, cite, and recommend your brand for the specific, attribute-rich questions your buyers actually ask.

## Why your AI traffic shows up as "Direct", and how to unmask it
Source: https://heybuffy.com/blog/why-ai-traffic-shows-up-as-direct

Open GA4, look at your channels, and you'll likely see a healthy "Direct" bucket you assume is people typing your URL or using a bookmark. A growing slice of it isn't. It's people who asked ChatGPT, Perplexity, or Gemini about a problem, clicked through to your page from the answer, and arrived with **no referrer attached**, so analytics had nowhere to file them but "Direct."

This is the single biggest blind spot in measuring AI visibility. If you can't see the traffic, you can't prove the channel is working, and you'll under-invest in the thing that's quietly becoming a real source of demand.

## Why the referrer disappears

GA4's logic is blunt: **a visit with no referrer header becomes "Direct."** Several common AI paths arrive exactly that way:

- **In-app clicks.** When someone taps a link inside the ChatGPT or Perplexity desktop or mobile app, the browser that opens often carries no referring URL. The visit looks like it came from nowhere.
- **Redirect hops.** Some engines route citations through a redirect or a link wrapper that drops the original source before it reaches you.
- **HTTPS quirks and privacy settings.** Referrer headers get trimmed in transit; a stricter referrer policy on the engine's side strips it entirely.

The result: a genuine, high-intent AI visit is indistinguishable from a bookmark click. Industry estimates of how much AI traffic lands this way vary widely, but the consistent finding is that **the visible AI referrals in your reports are only a fraction of the real total**: the rest is hiding in "Direct."

## Step one: capture the AI traffic that *does* carry a referrer

Not all of it is invisible. Web-based engines and some citation links do pass a source, and you can pull those into their own channel so they stop being lumped under "Organic" or "Referral." In GA4, build a **custom channel group** with a new channel. Call it *AI / LLM referral*. Defined by a regex condition on the source.

A starting pattern (extend it as new engines appear):

```
chatgpt\.com|chat\.openai\.com|openai\.com|perplexity\.ai|gemini\.google\.com|
bard\.google\.com|copilot\.microsoft\.com|bing\.com/chat|claude\.ai|
you\.com|poe\.com|phind\.com
```

Apply it as a "Source matches regex" rule in the channel group, ordered *above* Organic and Referral so AI hits get claimed first. From then on, every web-engine referral that carries a source rolls up into one line you can trend, compare, and tie to conversions.

> Capturing the visible AI referrals is the easy 30-40%. The harder, more valuable work is estimating the "Direct" portion you can't see directly.

## Step two: estimate the invisible portion

You can't reclaim a missing referrer, but you can *infer* AI-driven sessions inside "Direct" using signals a typed-URL visitor wouldn't have:

- **Deep landing pages.** Someone typing your URL lands on the homepage. Someone arriving from an AI answer lands deep. A specific blog post, a comparison page, a PDP that answered their question. A spike in "Direct" sessions landing on deep, content-rich URLs is a strong AI fingerprint.
- **New-user share.** AI-referred visitors skew toward first-time users, not returning bookmark-holders.
- **Query-shaped behaviour.** Long, specific dwell on a single answer-style page, often without a prior site visit.
- **Timing correlation.** "Direct"-to-deep-page sessions that rise in step with your tracked AI referrals and your [answer-level visibility](/blog/from-clicks-to-citations) are very likely the same demand, split across two buckets.

Build an exploration that isolates "Direct" sessions to non-homepage landing pages by new users, and you have a defensible **dark-traffic estimate**: not exact, but directionally honest, and far better than pretending the channel is zero.

## Why this is worth the afternoon

Two reasons. First, the traffic AI sends tends to be **high-intent**: the person already got a recommendation and clicked to verify or buy, so it often converts well above generic organic. Counting it as faceless "Direct" robs the channel of the credit that justifies investing in it. Second, you can't improve what you can't see: once AI referrals are a named line in your reporting, you can connect them to *which* pages get cited and act on it.

That second half, *which prompts surface you, on which engines, and whether your own pages are the cited source*. Is what happens upstream of the click, where GA4 can't reach. Pair this traffic view with [answer-level metrics](/blog/from-clicks-to-citations), and monitoring with **Buffy Intel**, to see the whole funnel: the answer that names you, and the visit it sends.

## Why your AI visibility changes even when your content hasn't
Source: https://heybuffy.com/blog/why-ai-visibility-changes-without-you

Your AI visibility can move even when you have not changed a word. AI engines quietly update how they turn one question into many background searches, and which sources they reach for, so the same pages can rise or fall on their own. A mid-2026 study by Peec AI, a GEO analytics firm, tracked ChatGPT's [query fan-outs](/glossary/query-fan-out) and retrieved sources over several months and caught the system shifting under its users, repeatedly. This piece lays out what it found, attributed and hedged, and what to do when the ground moves and your content didn't.

It is the temporal companion to [how query fan-out works](/blog/how-query-fan-out-works) (the mechanism) and [why your AI share-of-voice score swings](/blog/ai-share-of-voice-volatility) (the day-to-day noise). This is the slower story: directional drift across weeks and model versions.

## Why does visibility change when my content doesn't?

Because the retrieval system is not fixed. When your brand gets mentioned less, or your domain gets cited less, the reflex is to assume something on your page needs fixing. Often the real cause is upstream: the engine changed how it fans a prompt into sub-queries, which sources it trusts, or how many retrieval loops it performs. None of that is visible in the final answer, and none of it is under your control.

Peec AI frames the two metrics that matter as **brand visibility** (how often you are named in answers) and **retrieved sources** (how often your domain is pulled in as a source). Its mid-2026 research shows both can move purely because the model updated. The examples below are single-vendor, self-reported observations of mainly ChatGPT, so treat the exact numbers as directional; the pattern is the point.

> The default assumption when visibility drops is that you need to fix something on your side. Often the system simply changed which sources and sub-queries it prefers, with no change to your content at all.

## What shifts did the study actually catch?

Four documented shifts, all attributed to Peec AI's mid-2026 tracking of ChatGPT unless noted:

| Shift | What Peec AI observed | Read as |
|---|---|---|
| **Reddit spike** (ChatGPT only) | From ~end of May 2026, fan-outs increasingly appended "reddit" (e.g. "best lawn mower 2026" → "…reviews reddit"); Reddit's share of retrieved domains rose from just under 2% to about 5% (~150% relative), spiked for ~a month, then eased but settled at a **new, higher baseline** | A brief change can leave a lasting shift |
| **"Official" climb** (ChatGPT only) | The term "official" rose in fan-outs across languages (German *offiziell*, Spanish *oficial*, French *officiel*), in N-grams like "official site" and "official pricing"; retrieval impact was smaller because "official" is spread across many domains, with a slight lift for consumer-protection and government sites | The engine leaning toward authoritative sources |
| **arXiv overtakes Wikipedia** (ChatGPT 5.5/5.6) | arXiv's share of the *reference* source category (Wikipedia, encyclopedias, official docs, glossaries; ~7% of all citations) climbed from just under 1% in April to about 4% in July (~fourfold); Wikipedia's share of that category fell from ~40% in early March to about 7% by July; arXiv passed Wikipedia around end of June | Source preferences reorder over months |
| **Luna's precision turn** (ChatGPT 5.6 Luna) | Across ~5,000 prompts, Luna's fan-outs used the `site:` operator ~43% of the time (vs ~0.004% in 5.5), "official" ~22% (vs 1.4%), and year modifiers ~26% (vs 6.2%); it also performed more multi-step retrieval | Newer models search more like power-users |

Source: Peec AI, mid-2026, primarily observing ChatGPT; single-vendor and self-reported, so directional. ChatGPT 5.6 (the Sol/Terra/Luna tier family) was released by OpenAI on 9 July 2026, with Luna as the efficient tier, which independent coverage corroborates.

## Why did arXiv start winning quietly?

Because it became a [silent source](/glossary/silent-source): pulled in during retrieval but not always named or linked in the final answer. Peec AI reports that in a query for trail-suitable shoes for wide feet, arXiv was referenced six times during retrieval even though a science repository is not the obvious source, and that ChatGPT reads only the paper's abstract page, not the full document.

The move is not driven by a fan-out wording change; it reflects a broader tilt toward scientific reference material. The lesson for measurement: if you only watch the visible citations, you miss sources doing heavy lifting behind the scenes, and you miss the reordering entirely. Watching retrieved sources, not just named ones, is how you see it. It is the retrieval-side cousin of the [dark library effect](/glossary/dark-library-effect), where pages get read far more than they get clicked.

## What does ChatGPT 5.6 Luna's precision turn mean for me?

It rewards exact, structured, first-party facts. Peec AI reports Luna does more iterative retrieval: an initial broad fan-out, then targeted follow-up loops where the `site:` operator jumps from roughly 20% of the initial fan-out to over 80% of the first iteration. It increasingly pairs `site:` with **quoted attributes and negative operators**, essentially Boolean-precise searches for a specific value:

- `site:<brand>.com "<exact phone number>"` to find a service contact
- `site:<retailer>/productpage "organic cotton" "straight jeans" "black"` to match precise product attributes
- `"beige" "recycled polyester" "one-piece" women -aliexpress -instagram` to locate an exact item while excluding noise

The examples above are generalised from patterns Peec AI published, not any single brand's data. The takeaway is durable: as retrieval shifts from broad discovery toward [precision retrieval](/glossary/retrieval-augmented-generation), pages that state exact attributes, specifications, pricing, and service details, cleanly and machine-legibly, have a better chance of being the page a targeted search matches. This is consistent with our standing advice to [prioritise your structured data](/blog/prioritize-your-structured-data) and [prepare your product catalogue for AI agents](/blog/prepare-product-catalog-for-ai-agents); the Luna data raises the payoff.

## Isn't this just the same as answer volatility?

No, and keeping them separate matters. [Answer volatility](/glossary/answer-volatility) is short-term noise: ask the same question twice today and the brand list and citations wobble because the model samples differently each time. The drift Peec AI documents is **directional and slower**: a sustained change over weeks, driven by a model update, that shifts the baseline itself.

The practical difference is what you do about it. You ride out volatility by sampling many prompts and reading the trend. You respond to drift by noticing the baseline has moved, checking whether it moved for everyone or just you, and adjusting only if it is real and sustained. Confuse the two and you will either over-react to noise or miss a genuine change. This is why a single citation-rate snapshot is unreliable and why [measuring AI visibility](/blog/how-to-measure-ai-visibility) has to be continuous.

## What holds still while the system moves?

The durable levers. Model versions, preferred domains, and fan-out habits will keep changing; what keeps paying off across updates is narrower and more boring:

- **Be reachable and parseable.** Server-rendered HTML, crawlable by AI bots, in your sitemap. A source the engine can't fetch can't be retrieved no matter how it fans out.
- **State exact, structured facts.** Numeric, named, dated attributes in clean lists and tables are what a precision search can match; vague prose is not.
- **Build [entity strength](/blog/entity-strength-ai).** Being a corroborated, recognised entity in your category is the slow lever that survives whichever retrieval behaviour ships next.
- **Measure the retrieval side, over time.** Track mentions, retrieved sources, and fan-out behaviour as trends per engine, not one reading, so you can tell a model shift from a your-side regression.

The honest read for 2026: the biggest challenge is no longer just optimising content for AI, but understanding how the AI systems themselves evolve, so a shift you didn't cause doesn't get mistaken for a failure you have to fix. Watching mentions, cited sources, and fan-out behaviour drift across ChatGPT, Gemini, Claude, and Perplexity, over time, is exactly what **Buffy Intel** is built to do.

## Why buying aged Reddit accounts for AI visibility backfires
Source: https://heybuffy.com/blog/why-buying-aged-reddit-accounts-backfires

Buying aged, high-karma Reddit accounts to plant brand mentions and win AI citations fails twice. Reddit's anti-spam systems flag and ban the accounts. Often within weeks, and AI engines are learning to discount the manufactured signal even when an account survives. It is the 2026 equivalent of link farming, and it follows the same trajectory: a brief lift, then a penalty. Search Engine Journal put it plainly in a June 2026 analysis titled "Buying Reddit To Win AI Citations Is The New Link Farm."

This piece is the cautionary companion to [deciding whether Reddit is worth it](/blog/is-reddit-worth-it-for-ai-visibility) and the [earned Reddit playbook](/blog/how-to-use-reddit-for-ai-search-visibility). If you've decided Reddit matters for your category, this is the shortcut to avoid.

## Why would anyone buy aged Reddit accounts?

Because the logic looks airtight from a distance. AI engines cite Reddit more heavily than almost any other source, and Reddit's own rules make it hard for a brand-new account to post promotional links without being removed. So a market has emerged selling "aged" accounts. Years-old profiles with high karma and trusted posting histories. On the promise that a seasoned account can slip brand mentions into high-engagement threads at exactly the spots that get pulled into an AI answer.

Services have industrialised it. Search Engine Journal (Slobodan Manic, 29 Jun 2026) described one offering, RedRover, advertising "an army of agents publishing blog content & reddit posts" to get brands "cited by AI," and cited 404 Media reporting that manipulators reverse-engineer the question patterns models favour, then seed threads with brand mentions using warmed-up accounts with real posting histories. The pitch is scale; the reality is a dead account walking.

## Why do bought Reddit accounts almost always get banned?

Because Reddit's anti-spam systems are built specifically to catch the fingerprint of an account changing hands. The moment you buy an account, you inherit a profile whose history no longer matches its behaviour, and that mismatch trips multiple detectors at once. Practitioners who work the channel describe a consistent stack of flags (reported patterns, not official Reddit documentation):

| Flag | What trips it |
|---|---|
| **Email change** | Buyers immediately swap the email to their own; a sudden email change on a dormant account is a giant red flag |
| **IP / location jump** | An account that posted from one region for years suddenly logs in from a VPN, datacenter, or cheap proxy. Many of which are already blacklisted |
| **Device fingerprint change** | New browser, new device, new fingerprint; Reddit links accounts by device, the same tech it uses to catch ban evasion |
| **Behaviour shift** | Quiet for months, then five links a day in subreddits it never touched. No human behaves like that |
| **Farmed to begin with** | Many marketplace accounts were bot-farmed by reposting old viral content for karma, and are often pre-flagged before they're ever sold |
| **Sold twice** | Shady sellers resell the same account to multiple buyers, or keep the recovery email and take it back after payment |
| **Moderator review** | Human mods of real subreddits check post history; a karma-farmed account suddenly posting SaaS links stands out, and one report can trigger an admin review |

One Reddit marketer's widely-shared account describes a buyer spending $3,500 on ten aged accounts, all banned within weeks, with no recourse. You can't file a complaint about a black-market purchase. Treat that as an illustrative anecdote, not a statistic, but the mechanics behind it are well-documented. Worse, when Reddit bans a purchased account it often bans everything associated with it. Your IP, your device, sometimes your legitimate accounts, so a botched campaign can take down the clean presence you already had.

## Even if the account survives, does the citation stick?

Usually not, because the second failure happens at the AI engine, not at Reddit. Engines lean on Reddit precisely because it reads as authentic, [corroborated](/glossary/corroboration) human experience. A manufactured thread dilutes exactly the signal you're trying to borrow, and engines are actively learning to discount [gamed and injected content](/blog/can-ai-search-be-manipulated). A single planted mention, uncorroborated by real users, is the kind of low-evidence passage a model is most likely to drop.

There's a policy layer too. Google clarified in 2026 that its search spam policy covers [attempts to manipulate AI answers](/blog/google-spam-policy-ai-answers), and site reputation abuse and machine-generated abuse are named spam categories. The link-farm parallel is exact: bought backlinks produced a real ranking lift until Google's Penguin update filtered them and penalised the sites that relied on them. Manufactured Reddit signals are on the same arc. The manipulation degrades the trust the platform is valued for, which makes it a target for filtering. This is textbook [astroturfing](/glossary/astroturfing): fabricated grassroots consensus, which both platforms and engines are built to detect and discount.

## What's the durable alternative?

The alternative is unglamorous and it works: earn the mention instead of manufacturing it. The same authenticity that makes Reddit citable is only available to a brand that genuinely participates.

- **Let customers carry the name.** An earned mention from a real user in a high-engagement thread is worth more than any planted post, and it's the one thing anti-spam can't flag, because it's genuine.
- **Participate before you promote.** Build standing with helpful, disclosed contributions over months; the [earned Reddit playbook](/blog/how-to-use-reddit-for-ai-search-visibility) and the [white-hat AI-visibility method](/blog/grow-ai-visibility-without-spam) both start here.
- **Invest in [entity strength](/blog/entity-strength-ai).** Consistent, corroborated presence across the trusted sources your buyers use is the slow lever no update penalises, and it's built on [entity authority](/glossary/entity-authority), not bought profiles.
- **Pursue earned placement** in independent [best-of lists](/blog/get-into-ai-cited-best-lists) on the merits, never by renting authority.

> Buying aged Reddit accounts is the new link farm: a shortcut that works just long enough to feel clever, then collapses when the platform bans the accounts and the engine discounts the mention. The signal you actually want. Authentic, corroborated endorsement. Is the one thing you cannot purchase.

The honest play costs patience, not $3,500 in doomed accounts. Show up to help, let the mentions be earned, and measure whether engines actually surface and recommend your brand for your category over time, which is exactly what **Buffy Intel** tracks.

## Why Google says llms.txt is fundamentally flawed
Source: https://heybuffy.com/blog/why-google-says-llms-txt-is-flawed

On Google's *Search Off The Record* podcast (Episode 111, discussed June 2026), John Mueller explained the **fundamental flaw of [llms.txt](/glossary/llms-txt)**: because the site owner writes it about their own site, an AI system is designed not to trust it as a way of telling one website from another. A signal you fully control is a weak signal, which is why, in Google's view, llms.txt can't do the AI-discovery job many publishers hope it will. The reporting comes from Search Engine Journal's write-up of the episode; Mueller's position is Google's, and other engines may treat the file differently.

This is part of the [crawlers and technical](/blog/should-you-let-ai-crawlers-index-your-site) series and a direct companion to our earlier [honest take on whether llms.txt is worth it](/blog/is-llms-txt-worth-it). That piece gave the verdict. Cheap hygiene, not a lever. This one explains *why*, in Google's own framing.

## What did Google say about llms.txt?

That you can't be trusted to grade your own homework. Mueller's argument is about the trust model of retrieval, not the file format. In his words on the podcast:

> "Because it's basically you're telling these systems, like, I have the best website ever … So in an LLM system, it … basically, by design, can't trust what is here as a way of differentiating between different websites."

The logic is simple and durable. llms.txt is content the site owner authors about their own site. A curated list of "my most important pages." Every site owner has the same incentive to claim importance, so the file carries no information that separates a genuinely authoritative page from a self-promotional one. A retrieval system built to surface trustworthy evidence has to discount a signal that every publisher can set in their own favour.

## Why is a file you control a weak signal?

Because search has been here before, with the keywords meta tag. Mueller drew the parallel explicitly, and it's the clearest way to understand the flaw. The `<meta name="keywords">` tag let site owners declare what their page was about. Search engines stopped trusting it more than a decade ago for exactly one reason: it was owner-controlled and therefore trivial to manipulate. llms.txt sits in the same category.

| Property | Keywords meta tag | llms.txt |
|---|---|---|
| Who writes it | The site owner | The site owner |
| Verified against the page? | No | No |
| Standards body / enforcement | None | None |
| Incentive to inflate | High | High |
| How engines treat it | Ignored for 10+ years | Not broadly consumed (as of 2026) |

The pattern is the lesson: **the more completely you control a signal, the less a retrieval system can rely on it.** This is the same principle behind why coordinated, [self-serving AI content gets discounted](/blog/does-ai-generated-content-hurt-ai-visibility) and why [AI search resists manipulation](/blog/can-ai-search-be-manipulated). Trust in these systems is earned by corroboration from sources you *don't* control, not by assertions about yourself.

## What was llms.txt actually designed for?

A narrower job than discovery. Mueller said the original idea was *not* to make it easier for engines or LLMs to discover all of your content. It was closer to the reverse: if an AI **already knows about your site** and is operating on it, llms.txt might help it navigate. That is a real but modest use, and a long way from "publish llms.txt so AI finds you."

Even for the navigation job, Mueller suggested that emerging agent standards. Such as WebMCP, one of the [two paths to agentic commerce](/blog/webmcp-vs-ucp). Are better suited, because they're designed for an agent already interacting with your site rather than for discovery. The mismatch between what llms.txt was meant to do and what publishers use it for is the core of the confusion.

## So should you delete your llms.txt?

No. Nothing here says the file is harmful. As the [honest take](/blog/is-llms-txt-worth-it) concluded, it's near-zero cost, carries no downside, and positions you if engines ever start honouring it. Keep an accurate file if you have one; just don't expect it to move citations, and don't let it crowd out the work that does. The error is the expectation, not the file.

## What actually earns AI trust?

The signals you can't fake on your own. Mueller's closing point is that genuine discovery and ranking still depend on your HTML pages. What's actually on the open, crawlable web, not on a proprietary file. That points straight back to the durable levers:

- **Crawlable, semantic HTML.** Discovery happens through the pages themselves. Make them [reachable and parseable](/blog/make-your-website-agent-readable), not locked behind JS or a stripped [separate "AI version"](/blog/separate-ai-version-of-your-website).
- **[Structured data](/glossary/structured-data).** Schema labels what your content *is* in a verifiable, standardised way. The opposite of a free-text self-claim.
- **A corroborated [entity](/glossary/entity-authority).** Being described consistently by sources across the web is the trust signal llms.txt can't be, because you don't author it.
- **Freshness and depth.** Current, specific, genuinely useful pages are what retrieval systems lift, and what keeps you on the right side of the [citation freshness cliff](/blog/content-freshness-citation-cliff).

The takeaway isn't anti-llms.txt; it's a reminder of how AI trust works. You earn it by being legible and corroborated, not by telling the system you're the best. Tracking whether engines actually cite you, and which of your pages they pull from. Is what **Buffy Intel** measures. Questions: support@flash.tech.

## Why are retailers blocking AI shopping agents?
Source: https://heybuffy.com/blog/why-retailers-block-ai-shopping-agents

Some large retailers are now restricting AI shopping agents, blocking their crawlers in `robots.txt` and, in one 2026 case, winning a court order against an [agentic browser](/glossary/agentic-browser), to keep shoppers, data, and advertising revenue inside their own ecosystems. For your brand, the consequence is direct: where an agent can discover and buy your products increasingly depends on each platform's access rules, not only on how well your own site is built.

This explainer maps the walled-garden shift, sets out what is verifiable about the Amazon v. Perplexity ruling, and separates two things that are easy to confuse: gating agent *access* and adopting an open *checkout protocol*. It is the concept companion to the practical playbook on [keeping your products visible to AI shopping agents](/blog/keep-products-visible-to-ai-shopping-agents).

## What does "blocking AI shopping agents" actually mean?

It means a platform uses technical or legal controls to stop an AI agent from reading its pages or acting inside its accounts. There is no single lever; the blocks fall into three layers, from softest to hardest.

| Layer | Mechanism | Effect on an agent |
|---|---|---|
| **Crawl block** | Disallow an [AI crawler](/glossary/ai-crawler)'s user-agent in [`robots.txt`](/glossary/robots-txt) (e.g. `ChatGPT-User`, `OAI-SearchBot`) | The agent can't fetch live product data from that site |
| **Bot management** | CDN or WAF rules that challenge or 403 agent traffic | The page is unreachable even where `robots.txt` allows it |
| **Legal / access control** | Terms-of-service enforcement, or a court order against unauthorized account access | The agent is barred from acting inside logged-in areas |

The first two are the same mechanisms that can silently keep any brand out of AI answers; the difference here is that a platform is choosing to apply them deliberately, against shopping agents specifically. The third layer is newer and is where the Amazon v. Perplexity case sits.

## Which retailers are restricting agents, and how?

The market split into two postures through late 2025 and 2026: a few large players closed their doors to third-party agents, while others opened partner integrations. The clearest documented case of closing is Amazon.

According to reporting from Modern Retail (late 2025), Amazon updated its `robots.txt` to disallow OpenAI's `ChatGPT-User` (the fetcher that retrieves live web pages when a user asks) and `OAI-SearchBot` (which powers OpenAI's search product), on top of an earlier block of the `GPTBot` training crawler. The same reporting cited OpenAI's own economics research estimating that these agents field on the order of **50 million shopping-related queries a day** across the web, the traffic Amazon chose not to expose.

By contrast, other large retailers leaned in: Walmart and Target publicly announced ChatGPT shopping integrations over the same period, and platforms such as Shopify, Etsy, and Wayfair built toward open agent checkout. The takeaway is not "everyone is blocking"; it is that **access is now a strategic choice, and it differs by platform**, so an agent's ability to find your product can depend on whose storefront it is standing in.

## Why would a retailer block agents it could sell through?

Because an autonomous shopping agent threatens three things a large retailer controls today: ad revenue, first-party data, and the checkout relationship.

- **Advertising.** Sponsored product placements are one of the largest and fastest-growing businesses at the biggest retailers, worth tens of billions of dollars a year (reporting in late 2025 put Amazon's ad business in the mid-$50-billion range). An agent that reads a catalog and returns "the cheapest option that fits" can bypass sponsored listings entirely, and no one sees the ad.
- **Data and the relationship.** When a [shopper agent](/glossary/shopper-agent) transacts on a user's behalf, the retailer may lose the search query, the browsing signal, and the direct relationship with the buyer. A closed assistant (built in-house) keeps all of that.
- **Checkout control.** Owning the final purchase step, and its payment and returns data, is worth defending against an intermediary that inserts itself between shopper and store.

None of these motives require the retailer to think AI shopping is a fad. A platform can believe agentic commerce is the future and *still* prefer that it happen on rails the platform controls. That is the logic of a walled garden.

## What actually happened in Amazon v. Perplexity's Comet?

A U.S. federal court granted Amazon a preliminary injunction against Perplexity in an early legal test of agent access. The verifiable facts, corroborated across CNBC, GeekWire, Engadget, and Retail Brew:

- **The order.** On **10 March 2026**, District Judge **Maxine Chesney**, in San Francisco federal court, granted Amazon a preliminary injunction. It directed Perplexity to stop using its **Comet** browser agent to access shoppers' **password-protected** Amazon accounts and to **destroy Amazon data** it had previously collected.
- **The allegation.** Amazon, which sued in **November 2025**, argued that Comet accessed logged-in accounts "with the Amazon user's permission but without authorization by Amazon", and (per Amazon's filings, as reported) disguised its agent traffic to look like an ordinary Chrome browser. Reporting indicated Amazon's claims leaned on the federal Computer Fraud and Abuse Act; treat the exact statutory basis as reported rather than settled.
- **The response.** Perplexity called the suit a bully tactic, said it would "continue to fight for the right of internet users to choose whatever AI they want", and signaled an appeal.

Two cautions matter for how you read this. It is a **preliminary** injunction in active litigation, not a final judgment, and it turns on a narrow point, an agent acting inside a *logged-in, password-protected* account without the site's authorization, not on whether AI agents may read public pages at all. Public product pages and open feeds are a different question from automated action inside someone's account.

## Is blocking agents the same as leaving an open protocol like UCP?

No, and conflating the two is the most common misread. Gating agent *access* and adopting an open *checkout protocol* are separate decisions that live at different layers.

- **Access control** is about who may crawl your pages and act in your accounts, set through `robots.txt`, bot management, and terms of service.
- **Protocol adoption** is about the plumbing of a transaction once an authorized agent is transacting, standards like the [Universal Commerce Protocol](/blog/shopify-agentic-storefronts) (UCP) and the [Agentic Commerce Protocol](/glossary/agentic-commerce-protocol) (ACP).

A retailer can back an open commerce standard for the partners and agents it authorizes *and still* block crawlers or agents it hasn't sanctioned, the two are not in tension. So "Amazon blocked ChatGPT's crawlers" and "Amazon is among the platforms associated with UCP" can both be true: one is a decision about unauthorized access, the other about interoperable checkout for chosen partners. When you assess a platform, ask both questions separately: *can an agent reach me here, and if it transacts, on whose rails?*

> A walled garden isn't a bet against agentic commerce. It's a bet that the commerce will happen on the platform's own terms, with its ads, its data, and its checkout intact.

## What does the walled-garden shift mean for your brand's AI visibility?

That you should optimise for the surfaces you *can* control and never assume the whole web is reachable. Three durable implications:

1. **Your own storefront is your most reliable agent surface.** You set its `robots.txt`, its schema, and its checkout, so it is the one place a closed marketplace can't lock an agent out of. Keeping it open and legible is the highest-leverage move; that is the whole point of [discovering in AI but buying on your site](/blog/discover-in-ai-buy-on-your-site).
2. **Don't be the one accidentally blocking.** Many brands sit behind a CDN that quietly 403s AI agents. In a world where big platforms block *on purpose*, an *accidental* block is an unforced error, check whether [your CDN is blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers).
3. **Be present on more than one surface.** If one marketplace closes, open partner surfaces, your site, and third-party corroboration still carry you. Single-surface presence is fragile when access is a moving target.

The strategic picture is that AI product discovery is fragmenting, the same theme as [how discovery differs across ChatGPT, Google, and Perplexity](/blog/chatgpt-vs-google-vs-perplexity-product-discovery), and access decisions are now part of that fragmentation. The action companion, [how to keep your products visible to AI shopping agents](/blog/keep-products-visible-to-ai-shopping-agents), turns this into a checklist.

Knowing which agents and engines can actually reach and recommend your products, across surfaces and over time, is exactly what **Buffy Intel** tracks. Keep your own storefront open and legible; verify where an agent can still find you.

## Why you're invisible in AI search (and how to diagnose it)
Source: https://heybuffy.com/blog/why-youre-invisible-in-ai-search

**If you're invisible in AI search, the cause is almost always one of five layers, and they stack in order.** An engine has to *reach* your page, *recognise* you as an entity, *extract* a clean answer, find your claim *corroborated*, and see it's *fresh* enough to retrieve. Diagnose top-down: a brilliant page no crawler can fetch is invisible for a reason that has nothing to do with the writing.

Most "why am I not showing up?" panic comes from fixing the wrong layer. Rewriting copy when the real problem is a blocked crawler. Here's the ladder.

## Why am I invisible in AI search?

Because you're losing at one of these five layers, checked in this order:

| # | Layer | The question it answers | If you fail here… |
|---|---|---|---|
| 1 | Access | Can the engine fetch your page at all? | You're not in the index. Nothing else matters. |
| 2 | Entity | Does it recognise you as a name for this topic? | Your page is read but not trusted enough to cite. |
| 3 | Extractability | Can it lift a clean answer from the page? | Your facts are there but unquotable. |
| 4 | Corroboration | Does anything else confirm your claim? | You read as a lone, self-interested assertion. |
| 5 | Freshness | Is the page recent enough to retrieve? | You've decayed off the [citation cliff](/blog/content-freshness-citation-cliff). |

Work it from the top. Each layer assumes the ones above it are clear.

## Layer 1: Can AI engines even reach your pages?

The most common and most fixable cause. Content an engine can't fetch can't be cited. Full stop. Three things block access:

- **`robots.txt` rules** that disallow AI user-agents like `GPTBot`, `ClaudeBot`, or `PerplexityBot`.
- **CDN-level blocks**: many CDNs now challenge or deny AI bots by default. This is the silent one; see [is your CDN blocking AI crawlers](/blog/is-your-cdn-blocking-ai-crawlers).
- **JavaScript-only rendering**: if your facts only appear after scripts run, many crawlers never see them.

Confirm what's actually reaching you in [how to see which AI bots crawl your site](/blog/how-to-see-which-ai-bots-crawl-your-site), and understand the pipeline in [the AI crawler lifecycle](/blog/ai-crawler-lifecycle). Until access is clean, skip the other four layers.

## Layer 2: Do engines know you as an entity?

Engines lean heavily on how established you are as an [entity](/glossary/entity-authority). Your brand's search volume, [knowledge graph](/glossary/knowledge-graph) presence, and how often you co-occur with the topic across the web. Often more than on backlinks. A page from a recognised name inherits authority; an identical page from an unknown one doesn't.

This is the slow, durable lever. Be consistent and corroborated across the web so the model associates your name with the topic. The mechanics of why this decides citations are in [why AI cites one brand and ignores a near-identical competitor](/blog/why-ai-cites-one-brand) and [how AI engines choose which brands to recommend](/blog/how-ai-engines-choose-brands).

## Layer 3: Can a model extract a clean answer from your page?

Retrieval happens at the **passage level, not the page level**: a model lifts one self-contained chunk. If your answer is buried mid-paragraph or diffused across the page, it's effectively unquotable even when it's correct.

The fixes are structural: open each section with the answer in ~40-60 words, use question-style headings, put facts in lists and tables, and keep chunks self-contained. This is the same discipline as accessibility. [Accessibility and AI-parseability](/blog/accessibility-and-ai-parseability), and the craft is laid out in [how to get cited by AI](/blog/how-to-get-cited-by-ai).

## Layer 4: Is your claim corroborated anywhere else?

Engines favour claims echoed by multiple independent, authoritative sources. A figure repeated on Reddit, review sites, and the press reads as [corroborated](/glossary/corroboration) and safe to cite; the same figure sitting only on your own site reads as a lone, self-interested assertion.

So earned presence does work a brand page can't: third-party [best-of lists](/glossary/best-of-list) get cited far more than self-listing pages for commercial queries. Pursue placement in them rather than writing your own (see [how to get into the best-of lists AI engines cite](/blog/get-into-ai-cited-best-lists)). And keep it honest: trying to fake corroboration backfires, as we cover in [can AI search be manipulated](/blog/can-ai-search-be-manipulated).

## Layer 5: Is your page fresh enough to be retrieved?

Live retrieval favours recently-updated pages, and citations decay after roughly a quarter. The **three-month citation cliff**. A "publish and forget" page slides out of answers even if it once appeared. Put competitive pages on a refresh cadence with *substantive* updates (new data, corrected facts), not date-bumps. The evidence and cadence are in [the content freshness citation cliff](/blog/content-freshness-citation-cliff).

One caveat that prevents a false alarm: there's a documented crawl-to-cite lag of weeks. Training and search bots often crawl a new page heavily *before* the index starts citing it, so heavy crawling with zero citations is a leading indicator, not a failure. Don't judge a page dead in week two.

## How do you tell which layer is the problem?

Don't guess. Test across engines and read the pattern:

1. **Check access** for the URL: `robots.txt`, CDN response to AI user-agents, and whether facts are in the raw HTML.
2. **Run the same prompt** across ChatGPT, Claude, Perplexity, and Google's AI surfaces; log who gets cited.
3. **Read the pattern:** absent *everywhere* points to entity, extractability, or corroboration; absent on *some engines only* almost always means access or index coverage on those engines.
4. **Check freshness and off-site mentions** for the topic.

> If the gap is consistent across every engine, it's content, entity, or corroboration. If it's specific to one or two engines, it's almost always crawler access or index coverage. The easier kind to fix.

That cross-engine comparison. The same questions, tracked over time, logging exactly who gets cited and where. Is precisely what **Buffy Intel** does, so you can act on a diagnosis instead of a hunch. Start at the top of the ladder; you'll usually find the blocker before you reach the bottom.

## How to write product pages AI can quote word-for-word
Source: https://heybuffy.com/blog/write-conversational-product-pages

AI assistants don't read your product page and write a fair summary. They lift a **clean, self-contained sentence** from it and drop that line into the answer. So the practical goal of a conversational product page is narrow and winnable: make the exact sentence you want quoted the easiest sentence for an engine to pull. This how-to walks through the rewrite.

It pairs with [preparing your product catalog for AI agents](/blog/prepare-product-catalog-for-ai-agents), that piece is about *what data* to expose; this one is about *how to write the words* so they get quoted.

## Why won't AI quote a normal product description?

Because normal product copy is built to persuade, not to be extracted. Two habits block it:

- **Marketing fog.** "Elevate your everyday" and "thoughtfully designed" carry no quotable fact, so an engine skips them and quotes someone with specifics.
- **Buried facts.** The detail a shopper needs. The size range, the material, the compatibility. Sits mid-paragraph or inside a tab, where it can't be lifted as a standalone line.

An AI assembling an answer keeps passages that are specific, self-contained, and easy to extract. A description that's vague or tangled loses to one that isn't, even if the product is better.

## Step 1: Lead with the answer, not the pitch

Open the description with the one sentence that answers "what is this and who is it for," stated as fact.

- **Before:** "Meet the everyday essential you didn't know you needed."
- **After:** "A 240g merino base layer for cold-weather running, rated to roughly −5°C and machine-washable."

The second version is a sentence an engine can quote directly into "what's a good merino base layer for winter running?" The first answers nothing. Put the [answer-first](/blog/how-to-get-cited-by-ai) sentence at the very top of the copy, before any brand story.

## Step 2: Write self-contained, quotable sentences

Each key fact should stand on its own, because the engine may quote it without the sentence around it. State one idea per sentence, with the fact inside it, in roughly 12-20 words.

> Write the sentence you want repeated. Specific, self-contained, true, because that's the unit an engine lifts, and some quote only ~150 characters of it.

Avoid pronouns that point backwards ("it also comes in…"). Name the product or attribute so the line survives being lifted out of context. This is the same [extractability](/glossary/citation) discipline that decides which passages get cited anywhere.

## Step 3: Turn adjectives into attributes

Every vague claim is a missed quote. Convert them:

| Vague copy | Quotable rewrite |
|---|---|
| "Long-lasting battery" | "18-hour battery; ~2 hours to full charge" |
| "Fits most people" | "Fits wrists 14-19cm; adjustable strap" |
| "Premium materials" | "Full-grain leather upper, recycled-rubber sole" |
| "Ships fast" | "Dispatched within 24h; 2-4 day delivery in-country" |

The rewrites are quotable because they're [specific](/blog/factors-ai-recommends-products). Named, numeric, verifiable. Only state what's true; an engine that quotes a wrong spec damages the trust you need to be quoted again.

## Step 4: Answer the conversational branches

Shoppers ask AI long, specific questions, and the engine [fans them out](/glossary/query-fan-out) into sub-questions about fit, use, compatibility, and care. Cover those branches in the copy as plain statements:

1. **Who it's for / not for**: "Best for treadmill and road runners; not waterproof for trail use."
2. **What it pairs or works with**: "Compatible with standard 60mm filters."
3. **How to use or care for it**: "Hand-wash cold; air-dry to preserve the coating."
4. **The honest trade-off**: "Runs half a size small; size up for a relaxed fit."

Naming the trade-off honestly makes you *more* quotable, not less. Engines (and shoppers) trust a source that states limits.

## Step 5: Add a PDP FAQ for the objections

End the page with three to five real questions buyers ask before purchase, each answered in one or two self-contained sentences, marked up as `FAQPage` [structured data](/glossary/structured-data). The FAQ is the highest-yield part of a conversational PDP: it maps one-to-one onto the follow-up questions an engine fields, and each answer is pre-formatted to be lifted whole.

Source the questions from real signals. Search logs, support tickets, review themes, not from a model's guesses about your product. The questions shoppers actually ask are the queries you want to win.

## Step 6: Make sure the engine can reach it

None of this counts if the text isn't crawlable. Confirm the rewritten copy and FAQ render in **server-rendered HTML**, not JavaScript-only tabs or images, and that AI crawlers aren't [blocked at your CDN](/blog/is-your-cdn-blocking-ai-crawlers). A perfectly quotable sentence an engine can't fetch is invisible.

## What to do next

Take your best-selling product, read its page as an agent would, and rewrite the first sentence to answer "what is this and who is it for" as fact. Then convert the adjectives, add the FAQ, and confirm it's crawlable. Repeat across your hero products. Once the copy is quotable, the open question is whether engines are actually quoting it, which answers you appear in, and in whose words, and that's the loop **Buffy Intel** is built to measure.

## Do a few pages earn most of your AI citations? The hero-page pattern
Source: https://heybuffy.com/blog/your-ai-citation-hero-pages

**For most sites, a small number of pages earn the overwhelming majority of AI citations, while the rest earn none — the distribution is lopsided, not even.** This is a different finding from the well-known one that AI citations concentrate on a few *domains* across the web. This piece is about the concentration *inside your own site*: which of the pages you control actually get cited, and why it's so few.

The practical stakes are high. If you spread content effort evenly across your site on the assumption that any page might get cited, you are working against the grain of how engines behave. Knowing which pages are your citation hero pages — and pouring maintenance into those — is one of the highest-leverage moves in AI visibility. Every figure below is attributed, dated, and hedged; the durable claim is the *shape* of the distribution, not any single percentage.

## Why do citations pile onto so few of your pages?

Two mechanisms stack on top of each other. Neither is exotic, and together they make even distribution nearly impossible.

**Engines commit to a tight shortlist per answer.** An AI answer does not cite every page it reads. It reads broadly and cites narrowly. Perplexity has been reported across 2026 analyses to evaluate roughly ten pages per query but cite only three to five of them, and Google's AI Overviews draw the large majority of their cited sources from the top of the existing organic results rather than deep in the long tail (widely reported in 2026; directional, and it shifts by query type). So for any single question, only a couple of pages win the citation slot.

**Your buyers ask a bounded, repeating set of questions.** Real buyer queries cluster. The same dozen or two intents — what-is, how-much, versus, best-for, how-to — recur constantly, fanned out into sub-questions. Across that repeating set, the same strong page tends to win the same recurring question again and again.

Put the two together and citations compound onto whichever pages already answer your recurring questions best. A page that wins the definitional query wins it every time it's asked; a page that never wins anything stays at zero. The result is a lopsided curve, not a flat line. This is the same [tight-shortlist behaviour](/blog/how-many-sources-ai-engines-cite) that governs cross-web citations, turned inward on your own catalogue.

## How is this different from domain concentration?

They sound alike and are constantly confused, so keep the axes separate. One is about the whole web; the other is about your site.

| Axis | What it measures | Typical finding | Where we cover it |
|---|---|---|---|
| Cross-web **domain** concentration | Which domains, across the entire web, dominate all AI citations | A handful of community and reference domains own a large share; `.com`/`.org` alone ~90%+ (Profound, Aug 2024–Jun 2025) | [Do a few domains dominate AI citations?](/blog/ai-citation-domain-concentration) |
| Within-site **page** concentration | Which of *your own* pages get cited when AI answers about you | Lopsided: a small set of hero pages earns most; most pages earn none | This piece |

The domain axis tells you the web is a citation oligarchy and you often need [earned placement](/blog/get-into-ai-cited-best-lists) on sources you don't own. The page axis tells you that *even among the pages you do own*, effort should not be spread evenly. A brand can rank poorly on the domain axis (rarely cited web-wide) yet still have clear internal hero pages worth defending — and a brand cited web-wide still concentrates onto a few of its own URLs. Both are true at once; neither contradicts the other. Treat them as two dials, measured separately.

## What actually makes a page a hero page?

Not seniority or traffic — citability on a recurring question. The pages that become hero pages tend to share traits that make them the easy pick for an engine assembling an answer:

- **They answer one recurring question cleanly and answer-first**, so the extractable passage is right there. This is the payoff of [answer-first structure](/blog/how-to-get-cited-by-ai).
- **They carry evidence density** — a specific attributed statistic, a credible quote, inline sources — which is what [lifts a page from read to cited](/blog/what-content-changes-lift-ai-citations).
- **They are fresh.** Citations decay after roughly a quarter, so a page that was a hero six months ago and hasn't been touched can quietly fall off the [freshness cliff](/blog/content-freshness-citation-cliff).
- **They match the format your category rewards.** In some verticals the hero is a product or program page; in others it's a comparison or a how-to. That's your [citation fingerprint](/glossary/citation-fingerprint) deciding which page type can win at all.

Note what's *not* on the list: being your homepage, being your newest post, or getting the most human traffic. Hero pages for AI are defined by [which of your URLs actually get cited](/glossary/cited-pages), which is frequently not the page you'd expect.

> The mistake isn't publishing too little — it's spreading maintenance evenly across a site when your citations don't. Find the handful of pages engines already reach for, and make those pages undeniable, before you spend a day polishing a page no engine has ever cited.

## Why does this matter for how you spend?

Because uniform effort on a lopsided distribution wastes most of the effort. If ten pages earn nearly all your citations and ninety earn none, an even content-maintenance schedule spends 90% of its time where citations don't happen. Reweighting toward the hero pages does three things at once:

- **Defends citations you already have.** Hero pages are the ones most exposed to the freshness cliff and to competitors targeting the same recurring question. Letting them go stale is how visibility [drops without any obvious cause](/blog/diagnose-ai-visibility-drops).
- **Compounds what's working.** Adding evidence, updating figures, and building internal links *into* a page that already gets cited raises the ceiling on a proven winner, rather than gambling on an unproven page.
- **Reveals where you need earned coverage instead.** If a recurring, high-value question has no hero page of yours — engines only cite third parties for it — that's the signal to pursue [earned placement](/blog/get-into-ai-cited-best-lists) rather than to keep publishing owned pages the engines ignore.

None of this means stop publishing. New pages are how tomorrow's hero pages are discovered, and depth around a hero page is part of why it wins. It means: publish widely, but maintain narrowly, weighted to the pages the data proves are working. The companion how-to, [find your AI citation hero pages](/blog/find-your-ai-citation-hero-pages), turns this into a repeatable workflow.

## What should you do with this?

Treat the shape as durable and measure your own numbers, because the exact ratio is yours alone:

- **Find your hero pages before you assume them.** Capture which of your URLs get cited across engines for your buyers' real questions. The winners are often surprising. Keep engines separate — a hero on Perplexity may be invisible on Google AI Mode.
- **Reweight maintenance toward them.** Refresh, add evidence, and strengthen internal links on the pages that already earn citations, on a cadence, not once.
- **Flag the gaps.** Recurring questions with no owned hero page are earned-media targets, not more-owned-content targets.
- **Re-measure, because the curve moves.** Hero pages rise and fall as engines and competitors change. A page list captured once goes stale within a quarter.

The one number that beats every industry average is your own: which of your pages get cited, on which engine, trending which way. Tracking that per-page, per-engine over time — so your hero pages surface and you catch one slipping before your traffic does — is exactly what **Buffy Intel** is built to do. Questions: support@flash.tech.