What changed in branded search?
A branded query includes a company or product name. It might be a bare name such as a software company, or a task-shaped search such as a brand plus pricing, reviews, login, or support. Historically, many teams treated this traffic as relatively predictable: the official site ranked prominently, and the reporting question was whether people clicked it. An AI Overview adds a Google-written summary and a separate set of cited sources to that results page.
The recent change is an observed rise in how often that summary appears for branded terms in several third-party datasets. Google has not announced a named rollout specifically for brand queries, and its triggering rules are not public. Search Engine Land's report covered the DemandSphere spike, while Chris Long, co-founder of Nectiv, reported seeing Overviews for 93 of 100 enterprise names in a SerpApi check. Long's quick test helped surface the issue, but it is a different sample from the later platform studies.
For a marketer, the risk is not simply that an AI block takes space. It can describe a brand using a pricing page, an old review, a creator's video, a local listing, or a news article. Some of those sources may be useful; others may be stale or wrong. The practical question is whether the resulting answer helps a customer make the right decision.
Three studies, three denominators
The biggest mistake in this story is repeating “83% of brand searches” as if someone counted every Google search. The findings come from tracked sets with different geography, devices, query definitions, and collection methods. They are strong reasons to investigate your own brand; they are not a universal probability for every query.
AI Overview presence in its tracked branded queries, September 29; 26.12% on September 1.
AI Overview presence in its US desktop branded-keyword crawls, September 29.
Share of citations pointing to brand-owned sites in its separate 100-brand US sample.
DemandSphere: a rapid September change in its tracked set
Ray Grieselhuber, DemandSphere's founder, published a daily series for branded keywords tracked once per day through DemandMetrics, across markets and devices. AI Overview presence rose from 26.12% on September 1 to 82.06% on September 29, with a 90.48% peak on September 27. The path was uneven: several days earlier in September fell back toward 30%. That volatility matters when you choose a baseline. DemandSphere counts an Overview whenever it appears, regardless of whether the named brand is cited.
Ahrefs: a separate US desktop result set
Ryan Law and Xibeijia Guan at Ahrefs analyzed 232.8 million US desktop result crawls from July through September, including 92.5 million branded-keyword crawls. On September 29, 82.91% of branded-keyword results in that set contained an AI Overview. Their September monthly average was 73.3%, compared with 65.1% in August and 61.3% in July. A daily snapshot and a monthly average answer different questions; neither should be substituted for the other.
Ahrefs also checked 100 exact brand names at 14 weekly points. On September 30, 63 of those 100 names showed an Overview. Of those 63, 48 appeared in the first result position. That small exact-name panel is separate from the much larger branded-keyword crawl set. A plain brand name can behave differently from “[brand] pricing” or “[brand] alternatives.”
Slate: whose pages supply the answer?
Slate's 100-brand US study asked a different question. Across 93 brand answers and 652 unique citations, 29% of cited URLs pointed to a brand-owned site. Slate ran 144 searches over September 30 and October 1, rerunning names that did not initially show an Overview or had an obvious rendering issue. Its results came from one logged-out US location and a chosen brand list, so they cannot describe every market. But they show why presence alone is a thin measure: the answer may appear often while most of its citations come from elsewhere.
What can a branded AI Overview get wrong?
An Overview is most useful when it helps a person verify what a business does and where to go next. The same format becomes costly when it answers an important question with the wrong date, location, price, or policy. Slate's researchers found a mix of news, video, Wikipedia, Shopping and Maps citations in their sample; they also saw answers that included old information, ambiguous names, local mismatches, and forum-sourced details. Those are observed examples, not evidence that every brand's answer is inaccurate.
High consequence claims
Prices, refund terms, availability, contact details, safety facts, regulated claims, and whether a product is still supported. An error here can affect a real customer decision.
Representation and context
The wrong business with the same name, outdated positioning, an unofficial video, a review about an older version, or a competitor cited without clear context.
A third party being cited is not automatically a problem. An independent review or a news story may answer a question better than a brand page. The concern is claim fidelity: does the visible statement accurately reflect current facts, and can a reader verify it? Chris Long's initial post warned that external sources could shape brand perception; Ahrefs later found Wikipedia, YouTube, and LinkedIn common among external citations in its own exact-name panel.
Do not jump from an Overview's presence to a revenue-loss estimate. Broader AI Overview studies have reported lower organic click-through rates, but the new branded-search datasets did not measure the counterfactual for your specific name. A brand query may be navigational, informational, or transactional; even searches containing the same name can have different intent. The way to learn what happened to your business is to collect an answer audit alongside your own branded search and conversion data.
How to audit your brand in 30 minutes
Start with a small, repeatable sample. An audit that captures the query, device, country, date, answer, and cited sources is more useful than a single screenshot. You can run the first pass manually and repeat it weekly. If your company serves several markets, sample the places that matter rather than treating one US desktop view as global.
1. Choose 10 to 20 branded queries
Include your exact company name and common product names, plus the searches most likely to affect a decision: pricing, reviews, alternatives, support, returns, locations, and a current offer if one exists. For ambiguous names, add a category or location qualifier. Keep the list fixed for the first month so a changing query mix does not masquerade as a change in Google's behavior.
2. Record the search conditions
For each query, record the date and time, country, language, device, whether you were signed in, whether an Overview appeared, and where it appeared relative to your organic listing. Capture the full answer and every visible citation. Slate saw 16 of 44 repeated searches change between showing and not showing an Overview, so one check is a snapshot. Repeat important queries at least a few times before calling a change durable.
3. Check claims against first-party evidence
Read each factual statement as a customer would. Mark whether it is accurate, uncertain, outdated, or wrong. Link the canonical source for the correct fact: your live pricing page, product documentation, policy, location page, or a reliable independent source. Separate a factual mistake from language you simply would have written differently.
4. Classify citations and note the source of each problem
Tag each citation as brand-owned, independent editorial, user-generated, platform listing, or competitor-owned. Record whether the cited page actually supports the claim. Count citations, but also read the text: a brand-owned link in a source list does not guarantee the answer describes your brand correctly.
5. Save an evidence row and screenshot
Create one row per query and check. A useful row has: query, market, device, check date, Overview present, position, claim, severity, cited URL, owner, proposed correction, and recheck date. Save screenshots for material errors; the live answer may change before someone reviews your report.
| Query | Observed claim | Evidence | Next action |
|---|---|---|---|
| [Brand] pricing | Outdated starting price | Current pricing page + cited URL | Correct source, then recheck |
| [Brand] support | Unofficial phone number | Official contact page + cited URL | Escalate as high priority |
PikaSEO's AI Overview Analyzer can help you inspect a sample of keywords and sources. Check the result's data-source label before using it in a report: live SERP observations and AI estimates are different kinds of evidence. For the audit of exact wording and citations, retain your own screenshots and notes.
Prioritize corrections by customer harm
A large citation count can distract from one dangerous false statement. Start with the claims most likely to mislead a person. Put an incorrect payment term, wrong business phone number, or obsolete safety notice ahead of a slightly awkward company description. Treat an ambiguous brand name as a special case: if the answer describes another organization altogether, document both entities and the query conditions before editing your site.
Factually wrong
A claim can affect purchases, trust, safety, access, or legal understanding.
Outdated or incomplete
The source was once accurate but misses a material product or policy change.
Presentation issue
The answer is broadly true but could be clearer or more current.
When a brand-owned page is the weak source, edit that page where the customer would expect the answer. Make its facts explicit, current, and easy to verify. If Google cites an old third-party article, ask its publisher to correct a verifiable error and provide the current source. If a forum thread or unofficial listing shows an incorrect contact detail, use that platform's correction process. For local businesses, review the Google Business Profile information customers actually see.
Technical eligibility matters too. Google's AI search guide says a page must be indexed and eligible to appear with a snippet to be considered for generative AI features. If your authoritative page is blocked, canonicalized away, or unavailable, fix that before asking why another site is cited. A technical SEO audit can surface common crawl and page issues, but it cannot guarantee an AI citation.
Where the brand's own result still earns a click, make that result useful. A clear title and description help people recognize the official page. PikaSEO's SERP Preview helps check how your snippet reads; it does not simulate the AI Overview or its final placement. Update real pages for readers first, then let the search result reflect those pages.
Measure presence, accuracy, and business impact separately
A good branded-search dashboard has several columns, not one “AI visibility score.” First, track presence: in how many checks did an Overview appear for each fixed query and market? Second, track answer quality: how many material claims were correct, disputed, or outdated? Third, track citation mix: which of the answer's sources were owned and which were independent? Keep citations and brand mentions distinct. A citation to your domain can appear in an answer that barely discusses your business.
Then review outcomes. In Search Console's standard performance report, compare branded query clicks, impressions, and click-through rate over comparable periods, filtered by country and device where possible. Check landing-page sessions and conversions in analytics. Annotate product launches, campaigns, seasonality, and site changes. A simultaneous CTR drop and higher AI Overview presence is a lead to investigate, not proof of causation. A reliable before-and-after conclusion needs a stable query set and enough time to rule out other changes.
Google's generative AI performance report, announced in June and listed as rolled out worldwide by August 31, shows impressions for your URLs in AI Overviews and AI Mode. It provides page, country, device, and date views. Its current documentation describes impression data, not an exact branded-query answer audit, click attribution by query, or a measure of whether a generated claim is true. Use it as one evidence layer alongside the SERP checks and your standard performance data. Google also says some sites may not see the report if they have insufficient impressions.
Record a weekly snapshot rather than changing copy after every fluctuation. If you fix a wrong price on Monday, the next search may still show a cached or different source. Log the change date, recrawl and indexing evidence if available, the following Overview observations, and any change in branded clicks or leads. This gives an editor a defensible history instead of a sequence of alarming screenshots.
What Google actually recommends
Google's own guide to generative AI features keeps the foundation familiar: make useful, original pages that people can access and that Search can index. A page must be eligible to show a snippet. Google also points businesses toward accurate Merchant Center and Business Profile information where relevant. Those steps help customers in ordinary Search too; none promises placement in a branded AI Overview.
The guide explicitly rejects several popular shortcuts. It says Google Search does not need an llms.txt file, special AI markup, artificial “chunking,” or paid mentions designed to influence answers. Structured data may still support ordinary search features and help describe entities, but there is no schema that forces an AI Overview citation. The strongest response to a false brand claim is accurate source material and a documented correction path, not a new file named for an AI crawler.
For brands already investing in content, this suggests a narrow editorial review: identify the real questions people ask with your name, check whether your pages answer them completely, and correct pages that contain stale facts. PikaSEO's Helpful Content Checker can help you review an existing page's substance; your factual source of truth still needs a human owner. Our earlier articles on overall AI Overview prevalence and YouTube as an AI citation source provide broader context, but a brand audit should stay focused on your own queries and claims.
There is no confirmed timetable for this observed branded-query pattern to stabilize. DemandSphere's daily series moved sharply within September; Slate found that repeat checks of the same brand name could return different results. Recheck a fixed sample, update your evidence, and change your plan when the customer-facing answer changes. That is more useful than treating a late-September percentage as a permanent property of Google Search.
Frequently asked questions
Key takeaways and next steps
Branded AI Overviews are common in the new tracked datasets, and they deserve a place in brand-search reporting. The 83% figures describe specific samples; they do not say what Google shows for every company or how many customers stop clicking. A separate citation study found that most links in its sampled brand answers pointed beyond the brand's own site. Together, those findings make a factual, repeatable audit worthwhile.
- Choose a fixed list of valuable brand queries and record the market and device for each check.
- Save the answer, position, claims, and citations; repeat checks before declaring a trend.
- Correct high-consequence errors at their sources, starting with facts you own.
- Watch branded clicks, conversions, and AI impressions as separate signals over time.
The best outcome is simple: when someone searches for your business, they receive an accurate account and can reach the right page. Start with the queries customers already use, then expand the audit only when the first set reveals a real issue.
Research and documentation
- DemandSphere daily branded-query series
- Ahrefs US desktop and exact-name study
- Slate 100-brand citation study
- Chris Long's initial brand-query observation
- Google's AI search optimization guide
- Google's generative AI performance report
- Google's report launch announcement
- Search Console performance documentation
About the Author

Co-Founder & SEO Execution
Co-founder of PikaSEO. 11 years in corporate tech, then bootstrapped entrepreneur. Leads SEO execution and content-led growth for SaaS companies.