I recently came across an intriguing study that shows AI tools are now responsible for generating 45 billion monthly sessions globally. This accounts for an impressive 56% of all search engine activity, according to Graphite.io CEO Ethan Smith.
The analysis combines web and mobile app usage across leading AI platforms and suggests that AI activity matches 56% of global search use and 34% in the U.S.
The surge is particularly evident in mobile applications like ChatGPT, Gemini, Perplexity, Grok, and Claude.
Why it matters: AI is broadening the horizons of discovery, rather than limiting the demand for search. Since 2023, combined usage across search engines and AI assistants has increased by 26% globally. It’s clear that having visibility in both LLMs and traditional rankings is crucial.
Key insights: The report dives into the performance of the top five LLM products—ChatGPT, Gemini, Perplexity, Grok, and Claude—and compares them to the biggest search engines. Here are some standout insights:
AI platforms generate 45 billion monthly sessions worldwide.
Within the U.S., AI accounts for roughly 5.4 billion monthly sessions.
An astounding 83% of global AI usage takes place within mobile apps (75% in the U.S.).
ChatGPT is leading the charge, representing 89% of AI sessions globally.
When looking at search-like prompts, AI usage constitutes 28% of the global search and 17% within the U.S.
The report leaves out prompts in the “doing” or “expressing” categories. According to OpenAI, around 52% of prompts focus on seeking information, akin to traditional search queries.
Reading between the lines: Most forecasts comparing AI and search focus only on website traffic, often just Google.com and ChatGPT site visits. This approach overlooks much of AI’s impact.
The research suggests these comparisons undervalue AI activity by a factor of 4-5 times because a significant chunk occurs on mobile apps.
The analysis takes into account various LLMs and search engines, rather than only comparing Google and ChatGPT.
What to keep an eye on: Google remains a dominant force in discovery, but the report estimates its share of search-related activity has declined from 89% in 2023 to 71% by the fourth quarter of 2025.
While global AI usage seems stabilized since July 2025, the U.S. usage is still on a rapid climb—up about 300% year over year by December 2025.
I’ve been keeping an eye on the latest developments in AI advertising, and it’s time to prepare for something big: ChatGPT ads are on the horizon. As consumers shift towards shopping through AI prompts, ChatGPT could potentially rival search as a powerful demand-capture channel, leading to a redirection of ad budgets.
Recently, OpenAI began testing ads in ChatGPT for a limited group of U.S. users, clearly marking these placements as sponsored content. Based on the platform’s internal dynamics, it won’t be long before this feature becomes widely available.
As advertisers, we have a unique opportunity to tap into a fresh demand-capture channel. However, it’s crucial to approach this space with clear expectations and understanding.
For ChatGPT advertising to truly succeed, consumer behaviors will need to evolve. And even if they do, remember that ChatGPT won’t expand the market but rather, redistribute it.
Why ChatGPT is Embracing Ads
It’s no shock that ChatGPT is moving towards advertising. Running an LLM query is estimated to be ten times the cost of a simple search query. With users generating 2.5 billion prompts daily, expenses pile up swiftly.
The core difference here isn’t just a model shift; it’s the data landscape. Over the years, users have fed personal information into ChatGPT, giving it insights unmatched by traditional advertising tools. The burning question is how ChatGPT will use this data to target its users effectively.
Advertisements have traditionally relied on repetition to generate demand, whereas search meets buyers with intent. ChatGPT might forge a similar path, equipped with more user context.
Imagine this: asking which security camera works with a certain system and receiving an informed answer and purchase link because the platform already knows about your existing setup.
Should this happen, ChatGPT could be the first new demand-capture channel since Google’s PPC ads launched two decades ago. Yet, obstacles remain.
Today’s AI queries largely lack buying intent, serving more informational needs. When buying happens, the conversion tracking might fall short due to users completing purchases on platforms like Amazon or Google after doing their research on ChatGPT.
Don’t be discouraged; such challenges are surmountable. Google’s journey from a homework help tool to shopping powerhouse wasn’t overnight. Likewise, ChatGPT will need time to educate consumers about shopping through AI.
While a brand-new demand-capture platform is exciting, have realistic expectations about its potential.
Market Share Reality Check
Despite the capabilities of AI, it won’t expand the advertising marketplace. ChatGPT ads won’t magically bring a wave of new consumers.
Instead, it will capture pieces of the existing market shared by Google, Meta, and Amazon. It’s more about shifting budgets rather than expanding them.
Competition will be fierce, particularly with Google’s AI platform, Gemini, presenting a formidable challenge. Market consolidation seems inevitable as AI races towards profitability.
The Differentiator: Hyper-Personalization
AI’s true edge might be in hyper-personalization. With their vast knowledge of user preferences, these platforms can deliver perfectly tailored recommendations.
This feature could make AI incomparable, offering personalized results seamlessly. However, this comes with risk, as hyper-personalization might feel invasive to some users.
If AI can maintain trust and avoid crossing privacy boundaries, its personalized convenience will likely be favored by most.
Steps to Take Now
While widespread ChatGPT advertising is still on the horizon, preparation is key. Here’s how to get ahead:
Align on Measurement: Consider research-heavy metrics and assisted conversions.
Optimize Mobile UX: Ensure a smooth, fast purchasing experience to avoid loss in demand capture.
Plan Early Tests: Testing carries risks but can provide an early competitive edge.
Being strategic now will set the stage for success when ChatGPT advertising becomes fully operational.
Your Google Ads account can now change in meaningful ways without your team hand-building every asset or adjusting every bid. That creates leverage, but it also creates a control problem: the platform can move faster than your creative approvals, measurement checks, and business reporting.
If you are wondering what remains for a PPC team when Google automates more of campaign execution, the answer is not less responsibility. Your leverage moves upstream. You decide what the system may generate, which business signals it should optimize, how performance will be verified, and when a machine-made result is unacceptable.
Automation has moved PPC’s leverage point upstream
The day-to-day advantage in paid search no longer comes only from manipulating bids, expanding account structures, or producing more variations by hand. Modern PPC work is shifting toward data infrastructure, measurement, analysis, and experimentation because automated media buying depends on the systems and signals around it.
This changes the job from operating every campaign control to designing a reliable control system. Google can choose placements, assemble assets, and optimize delivery, but it cannot infer an unrecorded business objective. It does not know that one lead type is valuable and another consumes sales time without closing unless your data makes that distinction usable.
You still own four decisions:
Business objective: Define the outcome that deserves budget, such as a completed sale or a qualified opportunity, rather than treating every measurable action as equally valuable.
Signal design: Decide which events are primary optimization inputs, which are diagnostic, and how online activity connects to downstream revenue.
Creative permission: Specify what Google may generate or modify, which assets require approval, and which claims must remain unchanged.
Independent evaluation: Judge the campaign against business economics and a trusted dataset, not only the performance story inside the ad platform.
That is the central PPC transformation. Automation handles more execution, while your team becomes accountable for the quality of the instructions, permissions, and evidence surrounding it. Automation is not autonomous accountability.
Put explicit guardrails around machine-generated assets
Creative automation can alter more than layout. In one Performance Max rollout, eligible videos without a voice track could receive AI-generated narration. Google selected words from advertiser-supplied headlines and descriptions, generated a voice-over, and layered it onto the original video as a new asset. Advertisers were given until March 20 to opt out through video enhancement controls.
The important detail is not simply that Google can generate speech. It is that text written for one context can become the raw material for another. A short headline that works beside a product image may sound abrupt when spoken. A phrase that relies on surrounding visual context may become a stronger standalone claim in narration. A brand name, technical term, or location may also need a specific pronunciation.
Treat every automated enhancement setting as part of your production workflow. A default in the campaign interface can now affect the final creative a prospect sees and hears.
Use an asset-governance checklist before enabling automation
Inventory the controls. Record which campaigns permit video, text, image, or other asset enhancements. Assign a named owner to each setting so a default does not become an accidental policy.
Classify the copy. Separate flexible promotional language from wording that requires exact approval. Headlines and descriptions should not be approved only for their original placement if Google may reuse them elsewhere.
Read reusable text aloud. Check whether each line remains accurate, natural, and complete without the landing page, image, or preceding line to explain it.
Supply intentional assets where delivery matters. If voice, pacing, pronunciation, or silence is an important part of the creative, provide an approved version or use the available enhancement control instead of leaving the outcome implicit.
Inspect the rendered result. Review the actual combination shown to users. Checking the component headlines and video separately will not reveal every problem created during assembly.
Keep a decision record. Note the setting, approval status, reviewer, and reason for allowing or restricting generation. That makes later changes auditable when the interface or default behavior changes.
You do not need to reject every machine-made asset. Let the system work when the underlying copy can safely stand alone, the transformation is reversible, and someone can inspect the output. Use an authored asset or disable the enhancement where exact wording, delivery, or approval is material and no dependable review path exists.
Signal quality is now part of bidding strategy
Creative automation gets attention because you can see it. Signal automation is less visible and often more consequential. Google Ads can optimize only toward the events and values it receives. If your account labels a weak lead as a success, more automation can make the system faster at acquiring the wrong outcome.
Start with the business event, not the tag. Define what the company is willing to pay for, where that event becomes trustworthy, and which system owns the final status. Then work backward through the CRM, analytics implementation, website, and ad platform.
The deliverable is not a prettier dashboard. It is a dependable model in which spend and revenue can be joined without repeated manual exports, competing definitions, or unexplained changes between teams.
Measurement architecture preserves the meaning of a conversion
A tracking and measurement architect designs how events are collected under the applicable consent and privacy requirements. The work can include client-side and server-side tracking, Google Tag Manager and server containers, Consent Mode frameworks, conversion API integrations, and deduplication logic.
This role matters because a campaign can appear to improve or deteriorate when the real change happened in tracking. If CPA moves unexpectedly or the ad platform diverges sharply from the business’s trusted system, check event collection, consent behavior, duplicate handling, and data freshness before rewriting the campaign strategy.
Analysis separates platform success from business success
A data analyst connects campaign metrics to profitability, customer cohorts, lead quality, and churn. This is where a plausible platform narrative gets challenged. Reported return on ad spend is not the same as contribution margin, and a low platform CPA is not automatically valuable if the acquired customers or leads perform poorly after conversion.
The analyst should be able to explain which definition, time range, cohort, and data model produced a conclusion. AI can accelerate queries and surface patterns, but a confident interpretation is not necessarily a correct one. Statistical reasoning and business context remain part of the job.
CRO improves the economics before you add more spend
A conversion-rate optimization and experimentation lead examines the entire path from impression to revenue. Heat maps can help locate friction, while controlled tests determine whether a proposed change actually improves the outcome. A weak conversion rate can push acquisition costs upward, so scaling media before addressing funnel friction may simply buy more exposure to the same problem.
These are capabilities, not mandatory job titles. A smaller team may have one person wearing several hats. The important safeguard is explicit ownership. The person who implements tracking should not silently redefine the business KPI, and the person reporting campaign performance should be able to question the platform’s numbers.
Audit the signal chain before increasing automation
Write a plain-language definition of the primary business conversion and identify the system in which it becomes final.
Separate primary optimization events from secondary diagnostic actions. A page view, form start, and completed qualified lead should not become interchangeable merely because all three can be tracked.
Map every handoff from browser or server event through analytics, the CRM, the warehouse, and Google Ads.
Check for missing events, duplicates, stale refreshes, broken joins, and inconsistent timestamps before interpreting campaign movement.
Compare platform counts with the trusted business dataset using the same event definition and time range. A mismatch without aligned definitions is not yet a useful diagnosis.
Document which conversion actions and values bidding may use. Revisit that choice whenever the sales process, product economics, consent setup, or tracking implementation changes.
If this chain is unreliable, prompting an AI assistant for a new campaign strategy will not repair it. The model may produce polished recommendations from inputs that do not represent the business.
Keep human judgment focused on business questions
The strongest case for human PPC expertise is not that people should manually reproduce every task automation can perform. It is that someone must decide whether the machine is solving the right problem and whether the apparent result survives an independent check.
Build campaign reviews around questions that the interface cannot settle by itself:
Business outcome: Did revenue quality, margin, lead acceptance, or another defined commercial result improve?
Measurement integrity: Did tracking volume, consent behavior, deduplication, data freshness, or event definitions change during the same period?
Audience and offer: Is the result concentrated in a particular cohort, product, location, or offer that changes its economic meaning?
Creative behavior: Which asset was actually served, and did an automated transformation alter the wording, format, voice, or context?
Funnel performance: Did the landing experience improve, or did the campaign merely send more traffic into the same friction?
Evidence strength: Does the conclusion come from a credible comparison or experiment, or only from movement in a dashboard?
Use a simple experiment record for material changes. State the hypothesis, the primary KPI, the business guardrails, the eligible audience, the comparison method, and the decision rule before looking at the result. Keep exploratory segments separate from the primary conclusion so an interesting slice of data does not quietly replace the question you intended to answer.
Heat maps, generated summaries, and platform recommendations can all help you find where to investigate. They do not prove causation. A dashboard describes what was recorded; a well-designed experiment helps you decide what to change.
This is also where agencies and in-house teams should redefine their value. Producing more manual campaign edits is a weak differentiator when the platform can automate them. Designing reliable signals, governing creative generation, testing business hypotheses, and translating performance into economic decisions are harder to commoditize.
Key takeaways for rebuilding your PPC operating model
Google Ads automation shifts PPC work upstream: objectives, data, permissions, and verification now matter more than the volume of manual edits.
Headlines and descriptions may become inputs for other formats, including generated narration, so approve copy for reuse rather than only for its original placement.
A conversion signal is an instruction to the bidding system. Do not make an event primary until its definition, collection, deduplication, and business value are understood.
Platform ROAS and CPA are diagnostic metrics, not final proof of profitability. Reconcile them with revenue quality, margin, cohorts, and the business’s trusted records.
PPC teams need four connected capabilities: data engineering, measurement architecture, business analysis, and conversion experimentation.
Every new AI feature needs a release-management decision: allow it, constrain it, supply an authored alternative, or disable it where the available controls permit.
Product launch cycles should trigger operational reviews, not just note-taking. Google scheduled Marketing Live 2026 for May 20 alongside Google I/O on May 19-20, with the advertising event acting as a recurring venue for changes involving AI, campaign automation, and performance measurement. The proximity of those events is a planning signal, not proof that every announced capability should be enabled immediately.
For each material release, capture the affected campaign type, the default state, any opt-out timing, the assets or signals it may change, the person authorized to approve it, and the evidence required to keep it enabled. Test within a controlled scope when practical, inspect the real output, compare platform reporting with business outcomes, and preserve a rollback path where the product permits one.
Your next move is concrete: choose one automated campaign, trace its primary conversion back to the business system, inspect every enabled asset enhancement, and assign an owner to each gap you find. That single review will tell you whether AI is amplifying a sound PPC system or merely accelerating its weaknesses.
If your organic click-through rate or direct conversions fell after DMA-related search changes, don’t assume your rankings failed. An extra comparison layer, a different result layout, a new intermediary, or a longer route to conversion can produce the same dashboard symptom.
The honest verdict on DMA search fairness is not proven. The rules were meant to curb gatekeeper self-preferencing, but reported outcomes include more user friction, lower click-through rates, fewer direct bookings, and no clear weakening of Google’s central position. To decide what is actually happening, you need to measure user utility, business access, competitive opportunity, and market power separately.
Search fairness is four questions, not one metric
The Digital Markets Act was passed in 2022 and came into force in March 2024. Its search-market logic was straightforward: a dominant gatekeeper should not give its own services an unfair advantage over competing services.
That principle addresses a real problem. Google has been accused of promoting services such as Google Shopping ahead of alternatives that may serve the user better. But restricting self-preferencing does not automatically produce a competitive market, a better user journey, or stronger outcomes for independent businesses. Those are different tests.
Dimension
Question to ask
Evidence worth tracking
Misleading shortcut
Procedural neutrality
Are Google-owned and independent services receiving comparable treatment?
Eligibility, placement, labels, link treatment, and destination types across matched queries
Counting how many links appear on the page
User utility
Can the searcher complete the intended task without avoidable detours?
Steps to completion, intermediate domains, refinements, backtracking, abandonment, and completion rate
Assuming more visible choices always create a better experience
Business access
Do independent providers receive qualified visits and direct conversions?
Click destination share, conversion per search impression, assisted conversions, and direct-conversion share
Using impressions or rankings without following the journey to its outcome
Contestability
Can a challenger win and retain demand without depending on the same gatekeeper?
Diversity of destinations, durable gains across query groups, new-entrant visibility, and reliance on a single acquisition route
Treating one established intermediary’s traffic gain as proof of an open market
This distinction prevents two common analytical errors. A less convenient interface does not, by itself, prove that competition became less fair. A more competitive market can impose some short-term friction while users and businesses adjust. The reverse is also true: giving several services a place on the results page does not establish fairness if Google still controls the gateway, the rules, and most demand.
One survey involving 5,000 European consumers reported a more cumbersome online experience, with respondents even expressing willingness to pay to restore aspects of the previous integrated experience. That is an important warning about user utility. It is not, on its own, a complete measure of market contestability. The right response is to retain the warning while refusing to make it answer a different question.
Build a scorecard around the complete search journey
A DMA impact analysis should begin with a specific user task, not an account-wide traffic graph. Choose a query cohort tied to one decision: compare an offer, find a provider, reach a product page, start a booking, or complete a purchase. Then map every step from the search result to the final action.
Define matched query cohorts. Keep branded and non-branded searches separate. Split informational and transactional intent, and separate devices when their result layouts differ. An account-wide average can conceal the exact queries on which a new handoff appeared.
Record the visible search interface. For each cohort, capture result types, ordering, labels, proprietary modules, comparison services, organic links, and the domains receiving the first click. Preserve dated snapshots so later analysis does not depend on memory.
Measure the full funnel. Connect impressions and average visibility to clicks, landing sessions, qualified actions, conversion rate, direct conversions, and assisted conversions. A traffic metric tells you where attention moved; it does not tell you whether the business relationship survived the move.
Count handoffs and friction. Record how many domains and decisions sit between the result and the intended action. Look for repeated searches, backtracking, abandonment, and paths that send the user from Google to an intermediary before reaching the provider.
Segment destination ownership. Classify clicks going to Google-owned experiences, independent comparison services, publishers, marketplaces, and the provider’s own site. Without this classification, a declining organic CTR cannot reveal who captured the lost demand.
Use a credible comparison. Compare the same query cohorts before and after an observable interface change. Where possible, use comparable unaffected markets or journeys as controls, while accounting for seasonality, demand shifts, promotions, device mix, and unrelated ranking changes.
Set the interpretation rules first. Decide which combinations would indicate better user utility, stronger business access, or greater contestability before looking at the result. This reduces the temptation to label any favorable business movement as proof of fairness.
A simple before-and-after chart is rarely enough. Search demand, ranking systems, result features, brand activity, and conversion conditions can all move during the same period. If you do not control for those changes, the DMA becomes a convenient explanation rather than a demonstrated cause.
Your scorecard should also preserve trade-offs instead of averaging them away. If independent providers receive more qualified visits while users take an extra step, business access may have improved while user utility weakened. If users face more steps and independent providers receive fewer direct conversions, the implementation is failing both tests. If one large intermediary captures most displaced clicks, the market may have redistributed attention without becoming meaningfully more contestable.
Diagnose lower clicks and direct bookings before changing SEO
Visibility loss: Impressions, positions, or eligible appearances decline for the affected query cohort. Investigate relevance, technical eligibility, content quality, competitor movement, and result-layout changes before blaming regulation.
SERP interception: Visibility remains broadly stable while CTR falls and a different result type captures attention. Identify whether the click moved to a Google-owned surface, an independent service, or another publisher. Those movements have very different fairness implications.
Handoff friction: The user clicks but must pass through an additional service before reaching the provider. Measure the completion rate at every transition. A new competitive option is not useful to the business if qualified demand repeatedly disappears at the handoff.
On-site conversion loss: Landing sessions remain stable while conversion rate falls. Check page experience, message consistency, availability, offer changes, and measurement integrity. That pattern is less likely to be explained by search-result fairness alone.
Attribution loss: The final conversion still occurs, but the added intermediary changes how the journey is credited. Reconcile search clicks, referral sessions, assisted conversions, and transaction records before declaring that demand vanished.
The destination of a lost click matters as much as the loss itself. If your page loses traffic to an independent service that better satisfies the query, your business performance fell while procedural competition may have improved. If the click moves into a gatekeeper-owned unit, weaker performance may coincide with continued self-preferencing. If the click moves to a dominant intermediary, the result could replace one dependency with another.
Direct bookings need the same care. A lower direct-booking count can reflect lower demand, weaker visibility, an interrupted handoff, an attribution change, or transactions migrating to an intermediary. Report those causes separately. Otherwise, a single metric will mix an SEO problem, a user-experience problem, and a market-structure problem into one number no team can act on.
Act on the layer that actually failed
What search and content teams can change
You cannot optimize away a gatekeeper problem, but you can make your own part of a fragmented journey easier to discover, understand, and measure.
Maintain query-level evidence. Keep a recurring record of high-value result pages, their features, and their click destinations. Interface evidence is essential when traffic moves without an obvious ranking loss.
Preserve destination data. Classify referrals and assisted paths by surface and intermediary. Do not combine direct, organic, comparison-service, and marketplace journeys into a single acquisition bucket.
Reduce post-click uncertainty. Make the landing page complete the promise made in the result. Put the decision-critical information and next action where the visitor can find them without another search.
Keep structured data aligned with visible content. Accurate schema can reduce ambiguity about the entity, offer, page purpose, and relationships represented on the page. It will not reverse a DMA-induced layout change or prove that a market is fair.
Design for both direct and assisted discovery. Give intermediaries and AI-driven answer systems clear, consistent facts while preserving a strong path to the provider’s own page. Measure whether those external surfaces introduce qualified users or merely absorb the relationship.
Report performance and fairness separately. Your executive dashboard should distinguish what happened to your business from what happened to the market. A regulation can hurt one company without reducing competition, or help one company without creating a fair system.
What regulators would need to demonstrate
A credible fairness claim requires more than evidence that Google changed a layout or exposed additional links. Regulators would need to show that independent services can acquire qualified demand, users can still complete tasks at an acceptable level of friction, and challengers can become viable without remaining dependent on the same gatekeeper.
Enforcement also has to change incentives. A fine that leaves the gateway, behavior, and economic advantage intact can become an operating cost rather than a competitive remedy. Structural options, including breaking up a monopoly, address a different layer of the problem than interface rules do. They also carry much larger consequences and require a stronger evidentiary case; they should not be treated as a cosmetic extension of search-result regulation.
The practical decision rule is simple: if a remedy changes presentation but does not reduce dependency, expand viable entry, or improve independent access to demand, it is managing the symptom. If it improves supplier access while adding user friction, it has created a trade-off that must be measured and refined. Calling either outcome an uncomplicated success hides the work still required.
Key takeaways
The DMA’s equal-treatment goal is a rule for gatekeeper conduct, not proof that search outcomes became fair.
User convenience, business performance, procedural neutrality, and market contestability are separate dimensions. A single CTR or satisfaction metric cannot represent all four.
The survey of 5,000 European consumers is a meaningful warning about added friction, but consumer sentiment alone cannot establish whether independent competition improved.
Lower CTR and fewer direct bookings should trigger a journey diagnosis: visibility, SERP interception, handoff friction, on-site conversion, and attribution each require a different response.
A fairer result would let independent services gain qualified demand and become viable without simply shifting dependency from Google to another powerful intermediary.
SEO teams should preserve query-level SERP evidence, classify click destinations, connect discovery to final outcomes, and keep fairness reporting separate from company performance.
Your next move is to choose one commercially important query cohort and map it from result page to completed action. Record who receives each click, how many handoffs the user encounters, and where qualified demand disappears. Repeat that measurement after material interface changes. You will then know whether you are facing an SEO issue, a user-experience issue, a distribution shift, or a gatekeeper problem – and you can stop asking one metric to answer four different questions.
You have traced a suspicious backlink pattern to one top-level domain, and the cleanup looks repetitive: domain after domain ends with the same suffix. Google accepts a single disavow directive that can cover that entire TLD, but convenience is exactly what makes the option dangerous.
The line is simple. The decision behind it is not. Before you use it, you need to distinguish one bad website from a genuinely TLD-wide pattern and confirm that you are willing to disregard every useful link signal caught in the same scope.
First, confirm which kind of domain-wide disavowal you mean
Two different scopes are easy to conflate. A domain-level directive targets one named domain. A TLD-level directive reaches every domain using that top-level domain.
domain:example.abc identifies the specific domain example.abc.
domain:abc identifies the entire .abc top-level domain.
The second form is the unusually broad one. It asks Google to disregard links from unrelated websites simply because they share the same ending. It does not remove those links from the web, contact their owners, or make the referring pages disappear.
Google’s John Mueller confirmed that the bare domain:abc form can cover a whole TLD. He also cautioned that you cannot preserve selected domains beneath that directive and that every TLD is likely to contain some good sites. The behavior remains undocumented because its scope is so broad.
That limitation should control your choice. If you want Google to retain signals from even one important site on .abc, the TLD-wide directive cannot express your intent. Disavow the unwanted domains individually instead.
Require evidence at the same scale as the action
A shared suffix is a clue, not a verdict. Several poor links from several domains can still represent a small cluster rather than a problem with the entire TLD. Before reaching for the broad directive, test whether your evidence is genuinely broad enough.
Check distribution. Determine whether the pattern appears across many independent domains or is concentrated in a limited, repeatable set. A limited set supports domain-level action.
Check context. Review the referring pages, site identities, link placement, and relevance. Do not classify a domain solely from its suffix or an unfamiliar language.
Look deliberately for exceptions. Search the candidate TLD for publishers, communities, partners, directories, or other sites whose link signals you would want to keep.
Define the problem. Record why these links belong in a disavow file. An unusual TLD or an unattractive page is not, by itself, evidence that the entire namespace should be excluded.
Test your confidence. If your conclusion changes when you inspect beyond the most obvious examples, your classification is not stable enough for TLD-wide action.
What your review finds
Appropriate scope
Unwanted links are concentrated in a known set of domains
Handle those domains individually
The TLD contains a mix of unwanted and valuable sites
Use individual domain directives and preserve the valuable sites
The pattern spans the TLD and no reviewed exception needs to be preserved
Consider domain:abc
The sample is incomplete or your classification is uncertain
Do not use the TLD-wide directive yet
Volume should tell you where to investigate, not how broadly to act. A large pile of links can originate from a small number of domains. In that case, a whole-TLD directive expands the scope without improving the precision of the cleanup.
Build an audit trail before editing the disavow file
A TLD-wide decision should be reproducible by someone who did not perform the first review. Create a small evidence sheet rather than relying on a filtered backlink view that may be difficult to reconstruct later.
List every observed referring domain using the candidate TLD.
Attach representative linking URLs to each referring domain so the classification can be checked.
Record the page context, relevance, and reason each domain appears unwanted.
Mark every legitimate or uncertain domain separately instead of forcing it into a binary spam label.
Search specifically for an exception that would make whole-TLD treatment unacceptable.
Write the final scope decision: individual domains, the entire TLD, or no change pending further review.
This record gives you a practical stopping rule. One legitimate domain does not prove that every other domain is useful, but it does prove that domain:abc cannot preserve the distinction you have found. If that exception matters, narrow the scope.
Keep uncertainty visible as well. A domain you have not confidently classified belongs in an uncertain group, not automatically in the unwanted group. The TLD-wide line leaves no room for that nuance once it is applied.
Add the directive without losing control of the change
For a placeholder TLD written as .abc, the special directive is:
domain:abc
The value is the bare TLD label. Do not turn it into a sample hostname if your reviewed decision truly covers the entire TLD. Conversely, do not use the bare label when your evidence supports action against only particular domains.
Start from the current working version of your disavow file rather than rebuilding it from memory.
Save a dated copy of that version before making the change.
Add the whole-TLD line only after the audit and exception check are complete.
Record the candidate TLD, the evidence reviewed, the reason for the decision, and who approved it in a separate change log.
Review the exact scope once more before submitting the updated file through Google’s link disavow tool.
Do not try to create an exception by placing a preferred domain elsewhere in the file. The whole-TLD directive has no carve-out mechanism. Individual directives from the same TLD are also redundant once the broader line is present; the broader instruction already captures them.
A saved pre-change file and a written decision record will not make a poor classification harmless, but they prevent an opaque change. If a valuable domain is discovered later, you can identify why the broad line was added and reassess the scope from evidence rather than recollection.
Key takeaways
domain:abc can target links from every website using the .abc TLD, not just one domain.
A TLD-wide directive cannot preserve selected domains that you still value.
Use the broad form only when the backlink pattern and your review both support TLD-wide treatment.
Mixed, incomplete, or uncertain evidence calls for narrower domain-level work or more investigation.
Keep the prior disavow file, the reviewed examples, and the reason for the scope decision.
Before adding a whole-TLD line, try to find one domain under that suffix whose link signals you would want Google to retain. If you find one, stop and narrow the scope. If you do not, document the review and make domain:abc a deliberate final step rather than a shortcut.
Your rankings can look respectable while organic sessions keep sliding. That does not automatically mean your SEO has failed. The answer may have moved upstream, into a featured result, an AI Overview, or an assistant response that satisfies the user before a visit happens.
The same dashboard pattern can also come from lost positions, weaker snippets, stale information, indexing trouble, or changing demand. If you label every decline an AI problem, you will fix the wrong thing. You now need to determine where discovery broke, measure visibility before the click, make your pages easier to retrieve, and extract more value from the visitors who still arrive.
Key takeaways
Do not treat falling clicks as proof that an AI system is citing you. Separate click interception from an actual loss of search visibility.
Add citations, brand mentions, share of voice, sentiment, and AI-influenced visits to your reporting. Rankings and sessions show only part of the journey.
Write self-contained answer passages with clear scope, evidence, qualifications, and next steps. Do not hide the useful answer inside a long introduction.
Build authority beyond your own domain. Reviews, expert coverage, community discussions, newsletters, and video can corroborate what your site says.
Give an AI-referred visitor a focused landing experience. Detailed educational content and conversion pages have different jobs.
Diagnose the traffic loss before changing your content
Zero-click behavior is no longer an edge case. More than 65% of searches may now end without a click, while AI Overviews have been reported in about 16% of desktop searches and 41% of mobile searches. Those figures explain why a page can remain visible without receiving the traffic it once did. They do not prove that every lost click went to an AI answer.
Start by grouping your query-and-page data according to the pattern you can actually observe. The pattern determines the investigation:
Observed pattern
What it may mean
What to check next
Impressions are steady or rising, but clicks are falling
An answer feature may be intercepting clicks, your result may have moved lower, or competing snippets may have become more persuasive
Compare position and click-through rate by query, then inspect the live results for AI Overviews, featured snippets, knowledge panels, video results, and changed titles
Impressions and clicks are both falling
Your page may be losing eligibility or demand, not merely losing clicks to an answer surface
Your brand is mentioned in AI answers but your pages are not cited
The brand may be recognized through third-party material while your owned content is not being selected as evidence
Identify which outside pages are shaping the answer, then improve the relevant owned page and the consistency of external descriptions
AI referrals are small but produce meaningful actions
Low volume may be masking high intent
Track the referring assistant, landing page, conversion action, and resulting value separately from general organic traffic
For the first pattern, compare query-level impressions, average position, clicks, and click-through rate across equivalent periods. If position and impressions hold while click-through rate drops after a result page gains a direct-answer feature, click interception becomes a plausible explanation. If both position and impressions deteriorate, work on search eligibility and relevance before blaming AI.
Then inspect AI answers separately. A search performance report cannot tell you that an assistant quoted, cited, summarized, or ignored your page. An impression-click gap is a signal to investigate, not evidence of an AI citation.
Build an AI visibility scorecard you can repeat
Traditional analytics begin when a platform records an impression or a visitor reaches your site. AI-mediated discovery can happen before either event. Your measurement system therefore needs a controlled set of questions that represents the market you want to influence.
Build that set from real customer language: search queries, sales questions, support requests, on-site searches, and objections heard during evaluation. Include several kinds of intent:
Understanding: questions asking what a concept means, how it works, or why it matters.
Evaluation: questions about alternatives, selection criteria, trade-offs, and suitability for a particular situation.
Implementation: questions asking for steps, requirements, examples, or troubleshooting help.
Risk: questions about limitations, failure modes, cost, compatibility, or consequences.
Run the same question set across the AI interfaces your audience actually uses. Record the interface, model when visible, date, prompt, response, cited URLs, brands mentioned, answer framing, and any resulting referral. Because generated answers can vary between runs, treat the scorecard as a trend instrument rather than a census of everything an AI system knows.
Your scorecard should distinguish five measurements:
Citation coverage: the share of tested questions for which an AI response links to your domain. Preserve the exact cited URL so you can see which page and passage appear to be winning.
Brand mention coverage: the share of responses that name your brand, whether or not they cite you. A mention and an owned citation are not interchangeable.
Share of voice: your citations and mentions as a share of all tracked brands within the same fixed question set. Keep the denominator and prompt set stable so movement remains interpretable.
Brand sentiment: whether the response presents the brand positively, neutrally, negatively, or with a material qualification. Save the language that supports the label instead of recording an unexplained opinion.
AI-influenced traffic: visits and conversions attributable to assistant referrals. Report volume, conversion rate, landing page, and outcome together.
The combinations are often more useful than any metric alone. Frequent mentions with few owned citations point toward a content-selection or corroboration gap. Low mentions and low citations suggest a broader authority or category-association problem. Strong citation coverage with little traffic may still represent successful answer visibility, but you will need a separate way to value that exposure. Referral traffic with weak conversion usually points to a mismatch between the AI answer’s promise and the destination page.
Automated visibility platforms can scale this work, but do not buy a dashboard before defining the questions, entities, competitors, and decisions it must track. A carefully maintained manual benchmark is more useful than a large report whose prompts and scoring rules you cannot inspect.
Engineer content for retrieval, trust, and corroboration
AI search does not reward a page simply because it is long. The useful unit is the passage that answers a question clearly enough to extract and credible enough to reuse. That shifts the editing question from “Did we cover the keyword?” to “Can a reader or machine identify the answer, its scope, and the reason to trust it?”
Give each important answer a complete, self-contained block
Organize important sections around the question a reader is trying to resolve. A strong answer block usually performs these jobs in order:
State the answer: place the direct response in the opening sentence or short paragraph beneath the heading.
Define the scope: name the product, audience, market, version, or condition to which the answer applies.
Show the basis: provide evidence, a method, a concrete example, or a link that supports the claim.
Handle the exception: explain the trade-off or circumstance in which the answer changes.
Give the next action: tell the reader what to inspect, choose, calculate, or change.
This is not a command to turn every page into a pile of shallow FAQs. Use question-and-answer structure where a distinct question exists, and use prose where the reader needs explanation or judgement. Clear headings, concise summaries, bullets, comparison tables, and unambiguous question-and-answer pairs improve retrievability. Dense narrative that delays the answer makes extraction harder and frustrates the person reading it.
Do not repeat the same generic definition across many pages. Decide which URL owns the complete answer, link supporting pages to it, and remove contradictions. A coherent information architecture gives search systems a clearer canonical explanation and gives your editors one place to maintain it.
Make expertise and freshness visible on the page
Claims of expertise are weak evidence. Show the work instead. Name the author or reviewer, explain why that person is qualified for this topic, state how recommendations were derived, link important claims, and identify meaningful limitations. If you conducted an original analysis, describe the dataset and method closely enough for someone to understand what the result does and does not establish.
Freshness matters when an answer can change. An older page can be passed over for a newer treatment of the same question, even when much of the older explanation remains useful. Audit pages that influence important queries. Replace obsolete figures, verify product behavior, revise examples, repair broken citations, and expose a genuine update date. Changing a date without changing the substance does not make the answer more reliable.
Use AI to accelerate research organization, outlining, or editing if it helps your workflow, but keep a subject-matter expert responsible for the final claim. Remove generic transitions, unsupported certainty, fabricated examples, and passages that merely restate the heading. Human review matters because the page must survive a reader checking the details, not merely a classifier parsing the text.
Keep educational passages neutral enough to function as evidence. A page that says your product is the obvious choice for everyone gives an answer engine little reason to trust the comparison. State who each option suits, what it requires, where it falls short, and which criteria change the decision. You can still reach a clear recommendation after acknowledging the trade-offs.
Create corroboration beyond your own domain
Your website is only one input into an AI system’s representation of your brand. Reviews on G2, Capterra, and Google, community discussions on Reddit, third-party tutorials, newsletters, and YouTube videos can all contribute to the external evidence surrounding a brand. This is why a company with modest owned content can still appear prominently when independent sources describe it consistently.
Start with the claims that matter most: what category you belong to, who the product serves, which problems it solves, and what makes it materially different. Audit how those claims appear on your site, review profiles, partner pages, interviews, directories, and community discussions. Correct factual conflicts where you control the page. Where you do not, offer verifiable information rather than demanding favorable wording.
Make accurate company facts, product descriptions, expert biographies, and supporting evidence easy for partners and journalists to verify.
Contribute useful data, demonstrations, commentary, or tutorials to publications and creators whose audiences overlap with yours.
Encourage authentic customer reviews through a consistent process, but never script praise or manufacture community discussion.
Track third-party URLs that receive AI citations. They reveal which independent voices and content formats carry authority for your topic.
Compare external descriptions with your preferred positioning. Repeated disagreement may indicate a product-perception problem, not a wording problem.
Consistency does not mean publishing identical marketing copy everywhere. It means that independently written material converges on the same verifiable facts. That kind of corroboration is harder to manufacture and more useful to both buyers and answer systems.
Turn fewer, higher-intent clicks into measurable outcomes
A shrinking click pool makes each qualified visit more important. Early tracking indicates that traffic from LLM referrals may convert at three to five times the rate of other sources. Treat that range as directional, not a promise for your site: referral labeling, audience, offer, and conversion definitions can all affect the result.
Preserve the referral detail instead of burying these visits inside a broad channel. For each assistant referral, record the destination, action taken, conversion value where appropriate, and the question or topic that likely led there. A small channel that consistently reaches high-value pages deserves different treatment from a large channel producing casual visits.
The destination must continue the answer that earned the click. Keep educational pages deep and well supported; they need nuance for readers and retrievability for answer systems. Keep conversion landing pages focused:
Lead with a header that states the offer, intended user, and value without requiring a scroll to understand it.
Use a single primary call to action tied to the reason the visitor arrived.
Keep supporting points brief and place the most relevant proof close to the decision.
Remove competing messages that force the visitor to decide what the page is about.
Create separate landing pages when offers, audiences, or conversion goals differ materially.
Check that the page fulfills the promise made by the cited passage, third-party description, or AI response.
Put the work in a practical order. Establish a fixed visibility benchmark for a commercially important topic. Diagnose the search patterns for the pages already associated with it. Rewrite the strongest candidates into complete answer blocks, verify their evidence and freshness, then map the external sources that shape the same conversation. Finally, inspect the path from every measurable AI referral to its conversion action.
Before commissioning more content, apply that sequence to the topic closest to a real business outcome. You will learn whether the immediate constraint is search eligibility, passage quality, external authority, or the landing experience. That diagnosis gives you a defensible next investment instead of another round of undirected publishing.
It’s fascinating to see the evolution of Google’s AI Mode and how it increasingly cites Google itself. In fact, almost one out of every five sources in its AI-generated answers now originates from Google, often guiding users back to more Google searches.
Why does this matter to us? As someone deeply involved in the world of digital content and SEO, I’m aware that AI search should highlight the best online sources. If Google prioritizes its own content, there’s a risk that we might encounter fewer direct links and see a reduction in traffic as users remain within Google’s ecosystem.
So let’s delve into the details. Research by SE Ranking reveals that Google.com is the most cited source within AI Mode responses, making up 17.42% of all references. This makes Google more mentioned than even the combined total of the next six well-known platforms: YouTube, Facebook, Reddit, Amazon, Indeed, and Zillow.
In an accelerated trend, back in June 2025, Google referenced itself in only 5.7% of AI-generated answers, but now that figure has tripled.
Almost one out of five AI citations is from Google. When considering YouTube, Google-owned properties account for about 20% of all sources.
This self-referencing is quite pronounced, with AI Overviews linking heavily to Google properties such as Maps, Images, and YouTube. AI Mode expands on this by further embedding users within the Google environment, often through presenting additional search results rather than directing them to external sites.
This strategy keeps users engaged with Google platforms where monetized content such as ads and reviews can be found.
What’s changed? Previous research showed that Google was mostly citing Google Business Profiles. However, this trend has shifted:
Travel: 53.18% of citations
Entertainment & hobbies: 48.74% of citations
Real estate: 30.54% of citations
Interestingly, the one area where Google is not the top source is Careers and Jobs, where Indeed appears more than three times as often as Google.
The data supporting these findings were gathered by SE Ranking, who analyzed 68,313 keywords across 20 industries, reviewing over 1.3 million AI Mode citations to determine how frequently Google.com was referenced.
59% of citations now direct to conventional Google search results.
36.1% still reference Google Business Profiles.
A smaller portion links to Google Support (1.7%), Google Flights (0.1%), and other Google services.
Often, these AI citations are accompanied by a mini search results panel beside the answer, effectively creating a new search opportunity.
Industry differences are also evident. Google dominates citations across several topics, but some sectors show a stronger dependency on Google:
Travel: 53.18% of citations
Entertainment & hobbies: 48.74% of citations
Real estate: 30.54% of citations
Interestingly, the one area where Google is not the top source is Careers and Jobs, where Indeed appears more than three times as often as Google.
The data supporting these findings were gathered by SE Ranking, who analyzed 68,313 keywords across 20 industries, reviewing over 1.3 million AI Mode citations to determine how frequently Google.com was referenced.
If your shopping plan starts and ends with getting products into a native ChatGPT checkout, it is aimed at a moving target. The more durable opportunity is to help ChatGPT understand your products, select them for the right shopping questions, and send an informed buyer into a purchase path that works.
Treat ChatGPT as a decision channel, not merely a checkout
A shopper rarely begins with your product identifier. They begin with a constraint: a budget, use case, compatibility requirement, delivery concern, size, material, feature, or reason another option did not work. ChatGPT can influence which products enter the shortlist before the shopper reaches a retailer.
Build around three separate jobs:
Eligibility: Give AI systems enough accurate product information to determine when an item fits the request.
Selection: Supply clear evidence, limitations, comparisons, and policies that help the shopper choose among plausible options.
Conversion: Preserve the selected product, variant, price, and context when the shopper moves to your site or connected app.
Do not combine these jobs into a single metric. A product can be recommended but lose the sale during the handoff. It can receive qualified visits but fail because the product page contradicts the information used during discovery. It can also convert well once visited yet remain absent from relevant AI answers because its differentiators are vague or inaccessible.
Use a measurement ladder instead. Monitor whether your products appear for a stable set of relevant shopping questions. Track identifiable traffic from AI surfaces when a referrer, campaign parameter, or app link survives the handoff. Measure product-detail views, variant selections, add-to-cart actions, checkout starts, and purchases. Add a post-purchase discovery question if your analytics cannot observe the complete journey. Keep those signals separate so that a weak checkout does not get mistaken for weak discovery.
Build a product truth layer before creating more content
AI shopping optimization breaks when the same product has different facts across its page, structured data, feed, app, and checkout. A persuasive description cannot compensate for conflicting prices, ambiguous variants, or stale availability. Establish one operational product record and make every public representation inherit from it.
For each product and variant, maintain the fields a buyer actually needs to make a decision:
A stable product identifier, variant identifier, canonical URL, and exact product name.
Brand, category, intended use, defining features, dimensions, materials, compatibility, and other category-specific attributes.
Current price, currency, availability, condition, and a clear relationship between the parent product and its variants.
Images that correspond to the selected variant rather than a generic family image.
Shipping scope, fulfillment limitations, return conditions, warranty terms, and any purchase restrictions that can change the decision.
Evidence for material claims, with unsupported superlatives and vague labels removed.
Use Product and Offer JSON-LD to represent applicable facts in a machine-readable form, but treat markup as a copy of the truth rather than a separate marketing layer. The name, price, currency, availability, URL, image, brand, SKU, and offer details in the markup should agree with the visible page. If a rating, price range, or availability claim is not supported on the page, do not manufacture it in structured data.
JSON-LD is also not an inclusion switch for ChatGPT. It reduces ambiguity and gives machines a cleaner representation of the page; it does not guarantee that a product will be discovered, recommended, or ranked. Visible product copy still needs to explain fit, tradeoffs, and purchase conditions in language a shopper can understand.
Before expanding the work, run a sampled audit that compares the visible page, rendered JSON-LD, feed output, app view, cart, and checkout. The release gate should be simple: no sampled price, currency, availability, product identity, or variant mismatch. If you cannot meet that gate, adding more discovery content will amplify unreliable information.
Create pages around shopping constraints, not keyword permutations
A conventional product page often describes what an item is without explaining when someone should choose it. ChatGPT shopping questions tend to expose that gap because the user can combine several conditions in one request. Your content needs to resolve those conditions explicitly.
Build a question map from the language already present in customer support, on-site search, product reviews, returns, sales conversations, and merchandising filters. Group the questions by decision type:
Fit: Who is this product for, and when is another option more suitable?
Compatibility: What systems, sizes, accessories, materials, environments, or use cases does it support?
Tradeoffs: What does the buyer gain, and what must they accept in exchange?
Comparison: Which factual criteria distinguish this item from the closest alternatives?
Purchase conditions: What will shipping, setup, returns, replacement, or ongoing use require?
Map each question to the most appropriate page instead of forcing every answer into the product description. Put item-specific facts on the product page. Use category pages to explain selection criteria. Use comparison pages when buyers repeatedly choose between named options. Use support content for setup and compatibility details, then link it directly from the commercial page.
On a product page, answer the decision in a useful order: state the best-fit use case, show the facts supporting that fit, disclose meaningful limitations, explain the available variants, and present the purchase conditions. A clear not-suitable-for statement is often more useful than another paragraph of universal claims. It helps an AI system and a human buyer avoid a recommendation that will produce a return or a poor experience.
Comparison content should define the decision rule before declaring a winner. If the correct choice changes with budget, environment, compatibility, or desired feature, say so. Do not create a false universal ranking merely to target a best-product query. A conditional answer is more accurate and more reusable across the specific prompts shoppers actually ask.
Keep decisive facts in visible HTML. Structured data can reinforce those facts, but it should not contain essential claims that a shopper cannot verify on the page. The same principle applies to FAQs: publish them when they answer recurring purchase questions, not as a container for hidden keyword variants.
Make the external handoff trustworthy and measurable
The handoff is now a core part of ChatGPT shopping strategy. If discovery occurs in an AI conversation and the purchase occurs in a retailer app or site, any lost product context creates friction at the point of highest intent.
Resolve links to the exact product and selected variant whenever the originating surface provides that context. Show the same name, image, price, availability, and offer conditions the shopper just encountered. Keep return and shipping information easy to find before checkout. Avoid sending a buyer to a category page where they must reconstruct the selection from scratch.
Trust matters alongside technical capability. Consumers are accustomed to familiar purchase processes such as Apple Pay, Google Wallet, and Amazon. An external checkout is not automatically a strategic failure if it gives the buyer a recognizable, reliable place to complete the transaction. The failure is an external handoff that changes the offer, loses the variant, hides important terms, or cannot be measured.
Instrument the journey with a shared product and variant identifier across the landing view, variant selection, add-to-cart, checkout start, and purchase events. Add campaign parameters to links you control, but do not depend on referrer data alone. App transitions and privacy controls can interrupt the chain. Use session-level analytics, transaction data, and a customer-reported discovery field to create a more defensible view.
Run a narrow pilot before rebuilding your commerce stack:
Select a category in which buyers ask meaningful comparison or compatibility questions.
Audit the product truth layer and correct disagreements across pages, schema, feeds, apps, carts, and checkout.
Create or revise content for the real constraints that determine product fit.
Test every discovery-to-product link, including variant resolution, offer consistency, mobile behavior, and return paths.
Record baseline discovery, referral, engagement, cart, checkout, and purchase signals before judging the pilot.
Review failed recommendations and abandoned handoffs as separate problems, then fix the layer responsible for each one.
Expand only when the pilot can answer three operational questions: Did the right products appear for the right constraints? Did the landing experience preserve what the shopper selected? Did qualified AI-led visits produce downstream commercial actions? If one answer is unclear, improve its measurement before scaling.
Key takeaways
Optimize first for accurate product discovery and selection; native ChatGPT checkout is not the only route to value.
Separate eligibility, selection, and conversion so you can locate the actual failure in the journey.
Create one product truth layer and keep visible pages, JSON-LD, feeds, apps, carts, and checkout consistent.
Answer fit, compatibility, tradeoff, comparison, and purchase-condition questions in visible content.
Treat an external checkout as a designed handoff, preserving the exact product, variant, offer, and measurement context.
Pilot connected commerce narrowly and expand only after catalog accuracy, customer trust, and attribution are working together.
Start with a narrow product category and inspect the journey from a constrained shopping question through the completed order. Fix the first point where product truth, decision support, or handoff context breaks. That work will remain useful whether ChatGPT sends the transaction to your site, a connected app, or a future commerce protocol.
Your Google Business Profile is accurate, your location page is live, and you rank for at least some local searches. The uncomfortable question is what happens when a potential customer asks Google an open-ended local question and receives an AI-generated answer instead of a familiar list of links.
The practical response is not to chase a separate set of AI keywords. Make your business identity easy to verify, keep every important fact consistent, and publish enough location-specific information for an answer system to understand when your business is relevant. That work supports local packs, conventional results, AI Overviews, and other AI-assisted discovery without betting your strategy on one interface.
Local AI visibility starts with a resolvable business identity
That distinction matters because local AI optimization is not simply another ranking exercise. A system may need to establish that your business exists, determine where it operates, understand what it offers, and decide whether the evidence is strong enough to include in an answer. Schema can make facts explicit, but it cannot turn conflicting information into reliable information.
You should also avoid treating every Google AI experience as the same destination. Google Search is oriented toward information, engagement, and connections to the web, while Gemini is positioned more as an assistant for productivity and creation. Those products share technology but follow different objectives, and their eventual degree of convergence remains unsettled. Build facts that can travel across systems instead of optimizing around a guessed interface.
Key takeaways
Treat local visibility as an entity-confidence problem before treating it as a content-volume problem.
Create one approved record of your business name, location, contact details, hours, services, and service area.
Make visible page content, Google Business Profile data, citations, reviews, internal links, and structured data tell the same story.
Use schema to confirm facts that people can also see on the page, not to introduce a more convenient version of the business.
Measure factual accuracy and visibility separately across standard search, local results, AI Overviews, and Gemini.
Write a canonical local fact sheet before editing schema
Most consistency problems begin inside the business. The website owner has one phone number, the operations team has another, and an old directory still lists the number used before a move. A schema plugin then reproduces whichever version happened to be entered during setup.
Create a canonical fact sheet for each location. This is an internal operating record, not marketing copy. Give one person or team responsibility for approving changes, then use the record whenever you update the website, profiles, directory listings, or structured data.
Identity: Record the customer-facing business name, the most accurate primary business category, and a short factual description of the operation.
Location: Distinguish a staffed customer-facing location from an office, headquarters, mailing address, or service area. Do not let one address imply a function it does not have.
Contact details: Choose the public phone number, canonical location-page URL, and any official appointment or enquiry URL.
Availability: Record normal operating hours and identify services that follow different schedules. If customers can visit only by appointment, say so in visible language.
Offerings: Use the service names customers will see on the website and confirm which location actually provides each one.
Geographic scope: List the areas the business genuinely serves. Keep a service area distinct from an address and from places you merely hope to target.
Official profiles: Maintain the URLs of the Google Business Profile and other profiles that clearly represent the same business entity.
Resolve ambiguity instead of encoding it
A fact sheet is useful only if it contains decisions. If the storefront sign, website header, and profile use different names, do not copy all three into different schema fields. Decide which customer-facing identity is correct, determine whether the alternatives still serve a legitimate purpose, and plan a coordinated correction.
Apply the same discipline after a relocation, rebrand, acquisition, phone-system change, or adjustment to opening hours. Old information is not harmless just because it appears on a low-priority page. It can still create another version of the entity for machines and customers to reconcile.
Do not place aspirational claims on the fact sheet. A city you want to enter is not yet a service area. A service you plan to launch is not an available offering. A shared building is not evidence of a customer-facing branch. Structured data should describe the operation customers can actually use.
Align every place Google can compare
Once the canonical record is approved, audit the surfaces that can confirm or contradict it. Work from high-consequence identity facts down to descriptive enhancements. A wrong address, closed status, or phone number can block a customer journey; a less-than-perfect description usually does not deserve priority over those failures.
Signal
What to inspect
Common conflict
Corrective action
Visible website content
Header, footer, contact page, location page, service pages, and booking instructions
The footer shows current hours while an old contact page shows a previous schedule
Update the reusable template and every page that states the fact
Internal links and site structure
Navigation, location finders, breadcrumbs, service links, and XML sitemap entries
Current pages still point to a retired location URL
Link to the canonical live location page and remove obsolete paths from normal navigation
Google Business Profile
Name, category, address or service area, phone, hours, website URL, and listed services
The profile and website describe different operating scopes
Correct the underlying business record, then update both surfaces from it
Citations and directories
Prominent industry, regional, and customer-facing listings
An old brand, address, or phone number remains active
Correct the profiles most likely to be encountered or reused, keeping the same canonical facts
Reviews and reputation context
Recent customer language and references to a location, brand, or service
Customers continue to refer to a former name or location
Do not rewrite customer reviews; clarify the transition on properties the business controls
Structured data
Rendered JSON-LD, not only the fields displayed in a plugin dashboard
A theme or second plugin emits an outdated duplicate business entity
Fix the generating component and leave one coherent representation of each entity
Do not turn consistency into a demand that every description be word-for-word identical. A directory may need a short category label while a service page needs a detailed explanation. The facts must agree even when the wording and level of detail differ.
Audit from the customer’s point of view as well as the database owner’s. If one page says a branch is open but its booking link offers no way to select that branch, the site is making two operational claims. Fix the journey, not just the sentence.
Use LocalBusiness schema as a confirmation layer
LocalBusiness structured data converts important business facts into explicit relationships and properties. Its value is clarity: it can help a machine distinguish the entity’s name from a page heading, the business address from a publisher address, and the location URL from a general site URL. In AI-assisted local search, that clarity helps reduce uncertainty about who the business is, what it does, and where it operates.
It is not a private channel for claims that the visible page cannot support. If the page says the office closes at one time and openingHoursSpecification says another, the markup has created a conflict. If areaServed lists places the page never discusses and the business does not genuinely serve, the markup is not providing stronger optimization; it is weakening the integrity of the entity record.
Use the most specific LocalBusiness subtype that accurately represents the business. Specificity is useful only when it is true.
Give each real location a stable page URL and a stable @id so repeated references can point to the same entity.
Match name, url, telephone, address details, and opening hours to the approved record and visible page.
Add areaServed only for genuine service coverage. Do not use it as a list of geographic keywords.
Use sameAs for official profiles that represent the same entity, not for any page that happens to mention the business.
Include only properties your team can keep current. More markup creates more maintenance obligations.
Inspect the rendered output after theme, plugin, template, or location-data changes. A correct admin form does not prove that the live page emits one correct graph.
Keep multi-location entities separate
A multi-location organization should not collapse every branch into one ambiguous local entity. Give each genuine location its own visible facts and structured-data identity, then connect it to the parent organization where that relationship is accurate. This lets a system answer a local question with the appropriate branch instead of inheriting a headquarters address, organization-wide phone number, or service that is unavailable locally.
The same caution applies to practitioners operating inside a larger business. Represent a practitioner, department, location, and parent organization as distinct entities when they are distinct in the real world. Do not merge them merely because one plugin form is easier to complete.
No schema property guarantees a local ranking, an AI citation, or inclusion in an AI Overview. The useful test is narrower: does the markup make the correct business easier to identify without disagreeing with the rest of the web presence?
Create answerable local pages, then keep them synchronized
Consistency helps a system trust a fact, but it does not establish relevance to every local question. Your location pages must also explain the decisions customers are trying to make. A page containing only a business name, map, phone number, and generic brand copy identifies a place but says little about why that place fits a particular need.
Write for local decisions
Start the page with a plain statement of what the location provides and where it provides it. Then answer the questions that materially change whether someone can use the business.
Which services are available at this location, and which are not?
Is the address a place customers can visit, or does the business travel to them?
What geographic area does the team actually serve?
Are there appointment, access, delivery, or availability conditions a customer needs to know before acting?
What should a customer do next: call, book, request a quote, visit, or choose another location?
Which page provides the best supporting detail for each important service?
Use internal links to connect a location to the services genuinely available there, and connect service pages back to the appropriate locations. That structure gives people a usable path and gives machines a clearer relationship between the organization, its branches, and its offerings.
Avoid manufacturing near-identical city pages that change only a place name. They repeat a target phrase without adding evidence about local availability. If you cannot state what is operationally different or specifically useful for a location, strengthen the primary service-area or location page instead of multiplying weak pages.
Use a change protocol
Local information drifts when operational changes are handled as one-off edits. Treat every change to a name, address, phone number, schedule, service, location status, or service area as a coordinated release.
Approve the new fact in the canonical record and note when it becomes effective.
Update the visible website content, including reusable headers, footers, contact modules, and booking instructions.
Update the structured-data generator and inspect the JSON-LD rendered on the live page.
Update the corresponding Google Business Profile fields.
Correct important citations and official profiles that still expose the previous fact.
Check internal links, redirects, sitemap entries, and location finders if a URL or location status changed.
Record what was changed so a later audit can distinguish an overlooked property from a system that has not yet reflected the update.
Measure each discovery surface separately. For standard search, local results, AI Overviews, and Gemini, record whether the business appears, whether the displayed facts are correct, which page or profile is surfaced, and whether the result offers a usable next action. A correct answer with no visibility is a relevance problem. Visibility with the wrong hours or location is an entity-accuracy problem. Those failures need different fixes.
Begin with one commercially important location and one service customers regularly seek there. Approve its fact sheet, compare every major signal, repair the highest-consequence conflict, and only then expand the process across the rest of the business. That gives you a repeatable local AI visibility system rather than another markup project that goes stale after launch.
