You are planning or reviewing a YouTube campaign, and a 90-second unskippable break on a television sounds like either premium attention or an expensive way to irritate viewers. The reality is narrower: YouTube has been testing longer ad blocks for some viewers using TV devices, with the skip option delayed for roughly 90 seconds and, in some reported cases, even longer.
That does not make 90 seconds the new rule for every YouTube impression. It also does not mean you should immediately commission a 90-second commercial. First separate the viewing device, the length of the ad break, and the length of any individual ad. Those are three different decisions.
What the 90-second timer actually tells you
The documented behavior concerns the period before a viewer can skip an ad block. Some TV viewers have waited as long as 90 seconds for that control to appear, while individual reported blocks have sometimes run beyond 90 seconds. Because the behavior is described at the ad-block level, you should not assume that one advertiser receives a single, uninterrupted 90-second placement.
The phrase “YouTube TV ads” can also cause confusion. The test concerns YouTube watched on television devices. It is not, on the available evidence, a platform-wide change limited to or defined by the separate YouTube TV service. Initial observations were concentrated on TVs rather than mobile phones or desktop computers.
What you observe
What you can reasonably conclude
What you should not assume
A skip countdown approaching 90 seconds on a TV
You may be seeing the longer ad-block test
Every YouTube viewer now receives a 90-second unskippable ad
Several ads before the skip control appears
The timer may represent a combined break
One advertiser owns the entire interval
The break appears on a short video
The test is not tied only to long-form content
The video’s length determines the ad load
The same behavior is absent on mobile or desktop
The experience may be specific to TV-device delivery
Your account, connection, or television is necessarily malfunctioning
Reports have found the format on both shorter and longer videos. That matters when you diagnose what happened. A long break before a short clip is not proof that the video’s creator selected that ratio, and a long video is not a reliable predictor that the test will appear.
Why YouTube is treating the living-room screen differently
A television is not simply a larger phone. It is usually a lean-back viewing environment, often watched from across a room and sometimes shared by several people. YouTube can therefore package TV-screen viewing more like traditional television inventory: longer breaks, greater room for brand storytelling, and a prominent full-screen placement.
For advertisers, the attraction is the combination of TV-like inventory with digital targeting and measurement. That can make YouTube more relevant to budgets previously reserved for conventional television. It does not make the format right for every objective.
Give TV-device inventory serious consideration when your campaign needs broad visual reach, your creative works without an immediate click, and your reporting can separate television delivery from mobile and desktop performance. Be more cautious when success depends on a fast site visit, a small-screen interaction, or a direct comparison with highly clickable placements.
The practical mistake is to treat all YouTube impressions as interchangeable. If TV-screen delivery is strategically important, give it its own hypothesis, creative review, and reporting view wherever your account data permits. Otherwise, aggregate campaign results can conceal whether the television portion added useful reach or merely added completed impressions.
Build a TV campaign without confusing forced exposure with attention
An unskippable placement guarantees an opportunity to be seen for a period of time. It does not guarantee that the viewer welcomed, understood, or remembered the message. Use that distinction to shape the campaign before you increase spending.
Write a device-specific hypothesis. Define what television delivery is meant to add, such as incremental reach or stronger brand response. “More completed views” is not enough on its own when viewers cannot skip.
Keep ad-break length separate from creative length. A timer approaching 90 seconds does not establish that advertisers have been given one 90-second commercial. Maintain a strong shorter edit, especially because 30-second unskippable formats are already part of YouTube’s TV-style approach. Only produce a longer version when the story genuinely needs it and the placement supports it.
Review the creative from across a room. Use readable text, uncomplicated frames, and clear product or brand identification. Let sound improve the message, but do not make audio the only way to understand it.
Set exposure guardrails. Use the frequency and sequencing controls available for your campaign type. Prepare more than one creative treatment when the campaign will run repeatedly. A longer break makes repetition more noticeable, not less.
Measure more than completion. Pair delivery metrics with the business signal the campaign is supposed to influence. Depending on the tools available to you, that could include incremental reach, brand-lift evidence, branded search behavior, or downstream conversions. Treat an unskippable completion as proof of delivery, not proof of persuasion.
Choose a tolerance signal before launch. Monitor frequency, creative fatigue, negative feedback, or another relevant indicator alongside your primary outcome. Decide in advance what would cause you to rotate creative, reduce exposure, or stop the test.
This last step matters because early viewer reaction has been largely negative, with some people considering ad blockers or third-party viewing apps. That response does not prove the inventory is ineffective, but it does expose the central risk: purchased visibility can rise while willingness to pay attention falls.
Do not use the skip timer as your proxy for engagement. If brand response remains flat while forced exposure and repetition climb, the campaign has not become more persuasive. It has only become harder to avoid.
Questions about YouTube’s unskippable TV ads
Are all YouTube ads on TVs now unskippable for 90 seconds?
No. The available information describes a test affecting some TV-device viewers, not a universal rule for every viewer, video, market, or campaign. Treat a 90-second countdown as evidence of the tested experience, not evidence of a complete platform rollout.
Is this specifically a change to the YouTube TV service?
Not on the available evidence. The reported distinction is based on viewing through television devices rather than mobile or desktop. “YouTube on TV” and the separate YouTube TV service should not be used interchangeably when you document or analyze the change.
Does a 90-second countdown mean one commercial lasts 90 seconds?
Not necessarily. The documented experience is an extended ad block before skipping becomes available. That interval may contain more than one ad, so advertisers should not turn the countdown into a creative specification without confirming the placement they can actually buy.
Why can the long break appear before a short video?
The initial test was not tied consistently to video length. It appeared with both shorter and longer content. Do not use the duration of the selected video to predict whether a long unskippable block will appear.
Before your next media plan is locked, label this correctly as a TV-device ad-block test. Keep a strong shorter creative cut, isolate TV-screen results where possible, and define both a success signal and a viewer-tolerance signal. That plan remains useful whether YouTube retires the test, keeps it limited, or expands it to more viewers.
Your page is indexed, technically sound, and even earns search impressions. Yet it rarely appears in AI answers, recommendations, or citation-style results. That usually isn’t a signal to add more keywords. It is a signal to find the exact point where discovery breaks.
Content visibility is a chain: access, extraction, intent matching, evidence, selection, and measurement. If you diagnose those stages in order, you can make a targeted change instead of rewriting a useful page on instinct.
Visibility is a chain, not a single ranking setting
A search engine or AI system must first reach the URL. It then has to extract the main content, determine what the page is about, match it to a user’s need, and decide whether the material is suitable to surface or reuse. A failure at any stage can look like the same outcome: no visibility.
This is why crawlability and AI visibility should be treated as related but separate requirements. Allowing a crawler through the door does not make an ambiguous page understandable. Clear writing and schema cannot compensate for a blocked, redirected, or non-indexable URL.
Distribution is also more fragmented than a conventional rankings report implies. A dataset covering 42 million Google Discover cards from December 2025 through February 2026 identified 20 selecting pipelines organized into six broad layers: core editorial, news urgency, trends, local or geographic content, social or video content, and commercial content. The sample came from hundreds of devices, so it is a substantial snapshot, but it is not a permanent map of every Google or AI system.
The practical lesson is narrower and more useful: different surfaces can select the same URL for different reasons. A traditional ranking, a Discover recommendation, and an AI citation should not be treated as three readings from one universal visibility score.
Key takeaways
If a system cannot fetch the final page, content changes will not solve the problem.
If the title, description, opening, headings, and structured data imply different purposes, the page’s intent is unclear.
If important claims lack context, dates, ownership, or supporting links, the material is harder to evaluate and safely reuse.
Google Search Console queries show the demand already reaching each page, making them a better starting point than a speculative keyword list.
Search, Discover, referral traffic, brand mentions, and AI answer citations need separate measurements.
Diagnose the earliest broken stage before rewriting
Start with the URL, not the copy. Work through the following checks in order and stop when you find a material failure. There is little value in polishing an answer that the relevant systems cannot reliably retrieve.
Confirm access. Open the public URL without an authenticated session. Check the response, redirects, canonical target, robots rules, and page-level indexing directives. Review any firewall, bot-management, or consent layer that could return a challenge instead of the article. If your organization blocks categories of crawlers, make that an explicit policy decision rather than an accidental side effect of a security preset.
Inspect the extractable page. Make sure the main answer, headings, lists, links, and evidence exist in the delivered document. Do not assume every retrieval system will execute a client-side application exactly as a human browser does. Remove overlays and template elements that obscure the opening or make navigation look like the main content.
Verify page identity. The title, meta description, visible heading, introduction, canonical URL, breadcrumbs, and structured data should describe the same resource. A page presented as a tutorial in one field and a product category in another creates unnecessary ambiguity.
Compare the promise with real demand. In Google Search Console, inspect the queries associated with this specific URL. Group them by the job the searcher is trying to complete, such as learning, comparing, troubleshooting, evaluating, or buying. Then compare the dominant job with what the page promises near the top.
Audit evidence and ownership. Mark claims that depend on a date, platform, version, dataset, or named organization. Add that context where it changes the answer. Identify the author or responsible publisher and link important factual claims to the material that supports them.
Check each outcome separately. Review organic search performance, Discover exposure where applicable, observable AI referrals, brand mentions, and citations in a controlled set of answer prompts. One healthy channel does not prove that the others are healthy.
The first failed stage determines the next action. Fix access before content. Fix a query-to-page mismatch before adding schema. Strengthen evidence and entity clarity when the page is reachable and relevant but difficult to quote or attribute. If all of those checks pass, improve distribution and measurement instead of forcing another rewrite.
Use Search Console to measure the intent gap
Most content briefs begin with the audience a business hopes to attract. Search Console shows the audience Google is already connecting to the page. The difference between those two groups is your intent gap.
That gap is about meaning, not merely shared words. Vector embeddings can place queries and page descriptions in the same semantic space, allowing their distance to be scored. A documented implementation compares page-level Search Console queries with the page’s meta description and uses the distance to identify weak alignment.
Treat such a score as a diagnostic proxy. It is not an official Google metric, it does not prove why a page ranks, and a high similarity score does not guarantee inclusion in an AI answer. Its value is prioritization: it helps you locate pages whose positioning is far from the demand already reaching them.
A query-to-page workflow that does not require a special tool
Export queries by page. Preserve impressions, clicks, position, page, and query so that demand remains attached to the URL receiving it.
Separate different kinds of demand. Keep branded or navigational searches distinct from problem, comparison, and transaction-oriented searches. They represent different reasons for reaching the page.
Cluster by user task. Group queries that ask for the same outcome even when they use different vocabulary. Do not create a separate intent simply because a synonym appears.
Write the demand in one plain sentence. Complete the statement: People reaching this URL mainly want to… If several unrelated endings carry meaningful demand, the page may be trying to do too many jobs.
Write the page promise. Read only the title, meta description, main heading, opening paragraphs, and section headings. Complete the statement: This page helps you… Use what is actually on the page, not what the content brief intended.
Choose a structural response. Keep the positioning when promise and demand agree. Refocus the opening and headings when the right answer is buried. Expand the page when it omits a necessary subproblem. Split the page when distinct audiences or tasks require incompatible answers.
Look for five common forms of mismatch:
Scope gap: searchers want an implementation answer, but the page stays at the strategy level.
Audience gap: the page addresses specialists while the queries come from beginners, or the reverse.
Stage gap: the page tries to sell while the dominant demand is educational, or teaches basics to people already comparing options.
Format gap: the query calls for steps, criteria, or troubleshooting, but the page provides a continuous essay.
Outcome gap: the copy describes a topic without resolving the decision or problem behind the query.
Do not rewrite the meta description in isolation just to improve semantic similarity. It is useful because it expresses the page’s promise compactly. If that promise changes, make the same intent visible in the heading, introduction, body, internal links, and structured data. Otherwise, you have improved the label while leaving the resource unchanged.
Build an answer asset without weakening the full page
An AI-visible page still needs to work as a page. Compressing everything into short definitions may make individual sentences easy to extract, but it can remove the qualifications and evidence that make the answer trustworthy. Build a clear answer core, then support it with the depth the decision requires.
Put the answer core near the top
Answer the main question in direct language before moving into background. State who the answer applies to, what conditions change it, and what the reader should do next. If the subject requires a sequence, expose that sequence in an ordered list. If it requires choosing among options, name the decision criteria before describing every option.
Use headings that identify an actual subproblem. A heading such as Diagnose the earliest broken stage tells a reader and a machine what the section resolves. Generic labels such as Overview or More information do not.
Use structured data as clarification, not decoration
Select the most accurate schema type for the visible resource. Mark up only information a visitor can verify on the page. Keep names, authorship, publisher identity, dates, breadcrumbs, and canonical references consistent across HTML and JSON-LD. When an organization or product appears across multiple pages, use stable identifiers and naming rather than creating slightly different versions of the same entity.
Schema cannot repair a blocked URL, substitute for a missing answer, or make unsupported claims trustworthy. Its useful role is disambiguation: it helps a system interpret the type of resource and the relationships already expressed in the visible content.
Make provenance part of the answer
Durable visibility in generative systems depends partly on consistent metadata, provenance, and trust signals. Give time-sensitive claims a date or version. Name the organization responsible for the content. Link to the originating evidence when a factual claim depends on it. Distinguish observed facts from your recommendation.
This is not a request to add a long author biography to every page. It is a request to remove uncertainty that matters. A reader should be able to tell who is making the claim, when it applies, what supports it, and whether it is a fact, interpretation, or recommendation.
Package the content for its genuine distribution context
The measured Discover environment separated selection into layers for editorial content, urgent news, trends, local material, social or video content, and commercial content. It also evaluated pipelines by reach, speed, exclusivity, and feed volume. Those dimensions explain why a URL can have broad reach, fast pickup, or exclusive distribution without performing identically across every surface.
Use only the attributes your content genuinely has. Preserve geographic specificity when the answer is local. Make publication and update context clear when timing changes the value. Treat an original video as a first-class resource when video is integral to the answer. Do not imitate urgency, locality, or trend relevance that the page cannot substantiate.
Measure search and AI visibility as a portfolio
A single visibility percentage collapses different systems, intents, and outputs into a number that is hard to act on. Use a small scorecard that keeps the stages separate:
Layer
What to record
What a weakness means
First response
Access
Public response, redirects, canonical, robots rules, indexing directives, and extractable main content
The resource may not be consistently retrievable or eligible
Fix the technical path before editing copy
Search demand
Page-level queries, impressions, clicks, and position from Search Console
Demand may be weak, changing, or attached to a different intent
Inspect query clusters and competing pages
Intent fit
Alignment between dominant query tasks and the title, description, opening, and headings
The page promise does not match the audience reaching it
Defend, refocus, expand, or split the page
Answer readiness
Direct answer, qualifications, evidence links, author or publisher, dates, and consistent structured data
The material may be relevant but difficult to interpret, attribute, or reuse
Clarify the answer and its provenance
AI presence
Mentions and citations from a versioned set of prompts, plus identifiable referral traffic where available
The page is not being selected consistently in the observed answer environment
Check intent, evidence, entity clarity, and competing answer formats
Discovery distribution
Discover or recommendation exposure reported separately from standard search
A distribution surface may value different timing, format, or contextual signals
Improve truthful packaging for that surface
For AI answer checks, record the full prompt, engine, date, locale, and any account state that could affect the output. Reuse the same prompt set when evaluating a change. A single answer is an observation, not a trend, and it should not trigger a site-wide rewrite.
Keep a change log for the URL. Record whether you altered access rules, positioning, the answer core, evidence, structured data, or distribution packaging. Then compare equivalent periods and inspect the metrics closest to the stage you changed. If you modify every layer at once, any improvement will be difficult to explain or repeat.
Choose one page with meaningful Search Console impressions and uncertain AI visibility. Run the diagnostic from access through measurement, fix the earliest material failure, and document that change. That gives you a defensible optimization process you can apply to the next page instead of another collection of AI SEO guesses.
Your PPC dashboard says conversions are up. Revenue, order value, or sales quality says otherwise. That gap usually means the account is optimizing for the easiest recorded action, not the outcome your business actually needs.
A conversion-focused PPC strategy fixes the problem in a specific order: define the valuable outcome, improve the signals sent to the platform, separate different kinds of intent, and test changes against business value. Automation can then help you pursue the right result instead of efficiently producing the wrong one.
Start with the conversion signal you actually want
A conversion is whatever your tracking setup labels as a conversion. It isn’t automatically a sale, a qualified lead, or a profitable customer.
This distinction matters because automated bidding learns from the outcomes you feed it. If a content download, an unqualified form submission, a valuable phone call, and a completed purchase all look equivalent, the system can favor whichever action is easiest to generate. Weighting conversion actions by their likelihood of producing value gives the platform a better representation of what the business wants.
Begin with a one-sentence campaign objective:
Acquire the right customer for this offer at an allowable cost, measured by the most reliable purchase, qualified-lead, revenue, or repeat-value signal available.
Then audit every conversion action against that objective:
List every action currently counted in campaign reporting and bidding.
Identify the business outcome that happens after each action: qualification, sale, revenue, retention, or no meaningful progress.
Classify the action as a primary outcome, a useful secondary signal, or a diagnostic event.
Assign relative values only where you can defend the differences with business logic or downstream data.
Remove weak proxy actions from optimization when they compete with stronger outcomes.
Observed action
How to treat it
Question to answer first
Purchase with recorded revenue
Use as a primary value signal when the revenue is reliable
Does revenue reflect the full order without duplicates or missing transactions?
Qualified phone call or sales-ready lead
Weight according to its downstream likelihood of becoming a customer
Can you distinguish a qualified inquiry from support, spam, or a poor-fit prospect?
Unqualified form submission
Keep secondary until qualification data proves its value
What share reaches the next meaningful sales stage?
Page view, content download, or other micro-conversion
Use for diagnosis or audience building, not as a substitute for revenue
Does this action predict a valuable outcome, or is it merely easy to complete?
A phone call isn’t inherently more valuable than a form submission. It deserves more weight only when your own qualification and sales data show that it is more likely to create value. The same rule applies to any conversion hierarchy: evidence should determine the weight, not a generic PPC convention.
Google’s planning direction reinforces the need for clear outcome signals. Performance Planner has stopped supporting Display and Video planning as well as impression-share-based plans, while its supported scope centers on conversion-oriented campaign types such as Search, Shopping, App, Demand Gen, Local, and Performance Max. That doesn’t make awareness activity worthless. It does mean you need your own explanation of what upper-funnel spend contributes instead of treating impressions as sufficient proof.
Don’t invent precise values merely to satisfy an automated system. False precision can redirect real budget. If the downstream value is unknown, preserve the action for reporting, investigate its relationship to sales, and keep the uncertainty visible until you have a defensible signal.
Route each kind of intent to the right campaign treatment
Conversion-focused targeting begins before you select a match type or audience. You need to know what the person is trying to accomplish and how close that intent is to a decision.
For every meaningful query or audience, ask three questions:
Who has a present problem and is likely to act now?
Who could become a buyer after an objection is answered?
Who is unlikely to buy because the offer, use case, price, or customer profile doesn’t fit?
This classification should change the ad, landing page, bidding signal, and degree of structural control. It shouldn’t remain a persona exercise in a planning document.
Use precision where the intent justifies it
High-intent, high-value terms can merit dedicated control. Selective single-keyword ad groups may improve message relevance and query precision where one term represents commercially important demand. That doesn’t justify rebuilding an entire account around single-keyword structures. Reserve the added maintenance for cases in which the intent and potential value make it worthwhile.
Competitor searches can also represent developed purchase intent. The person already understands the category and may be evaluating alternatives. A competitor campaign therefore needs a clear reason to choose your offer and a relevant landing page; a generic page wastes the intent you paid to capture.
Target Impression Share is another deliberate exception. It may support brand defense or visibility on strategically important non-branded terms, but it pursues presence rather than conversion efficiency. Use it only when visibility itself is the stated objective and the business accepts the possible efficiency tradeoff. Don’t present the result as a conventional acquisition win if cost per valuable outcome deteriorates.
Let automation explore inside visible boundaries
Broad match can discover demand you didn’t anticipate, but exploration needs a feedback loop. Combining it with assertive negative-keyword management lets the platform search broadly while you continually shape what qualifies. Several useful PPC tactics, including selective SKAGs, controlled broad match, competitor bidding, conversion weighting, and feed refinement, work because they improve the signals or boundaries around automation rather than rejecting automation outright.
Use this query-review loop:
Inspect the actual search query, not just the keyword that matched it.
Label its intent, customer fit, likely value, and relationship to the offer.
Exclude irrelevant or consistently poor-fit themes with negative keywords.
Move commercially important themes into a more controlled treatment when dedicated ads, bids, or landing pages would change the outcome.
Feed useful language from real queries back into ad copy and landing-page messaging.
Top-of-funnel queries require a different scorecard. They may contribute by building remarketing pools or strengthening audience signals even when their direct conversion rate is weak. Keep that spend identifiable, state the support role in advance, and don’t allow upper-funnel activity to hide inside the economics of high-intent acquisition.
Retargeting audiences can serve as a controlled environment for message and creative tests because those users already have some familiarity with the offer. A winning message can then be tested with colder audiences. Familiarity still changes behavior, so treat the retargeting result as a promising hypothesis rather than proof that the same creative will work everywhere.
Diagnose performance from revenue backward
When performance weakens, broad questions such as why did ROAS fall tend to produce broad answers. Diagnose the chain from the business result backward:
Spend to click to conversion to qualified outcome to sale to revenue to repeat value.
The first broken relationship is usually more actionable than the loudest metric in the interface. Use the following patterns as hypotheses to investigate, not automatic verdicts:
If conversion volume rises while Value/Conv. falls, the account may be finding easier but lower-value customers. Inspect audience, query, product, and order-value mix before celebrating the extra conversions.
If raw leads increase while qualified leads do not, improve the conversion hierarchy and customer filters before buying more traffic.
If qualified lead quality remains stable but sales decline, inspect the landing-to-sales handoff, offer, and downstream process rather than forcing a media-only explanation.
If relevant queries decline, examine match behavior and negatives before rewriting every ad.
If click-through performance improves without a better business result, the new message may be attracting attention without improving buying intent.
This is especially important when B2B and B2C demand overlaps. A campaign may collect many inexpensive consumer conversions while losing the higher-value business buyers it was meant to acquire. In that situation, stronger first-party audience inputs, specific audience segments, and value rules can emphasize B2B intent. That approach has been used to address lagging average order value reflected in Google Ads Value/Conv., but it still requires measurement: targeting a supposedly valuable group doesn’t guarantee valuable orders.
Evaluate economics at the deepest reliable level you possess. For ecommerce, revenue per order is more informative than order count, while contribution after variable costs is more useful than revenue alone when the necessary financial data is available. For lead generation, an expected value model can combine qualification likelihood, close likelihood, and customer economics. Use definitions approved by the people responsible for finance and sales rather than creating a parallel PPC version of profitability.
Customer lifetime value can justify a different acquisition decision from first-order revenue, but only when retention and repeat purchases are observable. Ask why customers stay, what causes another purchase, and which segments actually retain. Don’t raise allowable acquisition costs because an AI tool or a planning assumption produced an attractive lifetime-value story.
When you alter conversion values, audience rules, targeting, or campaign structure, log the change and the intended effect. Avoid simultaneously changing so many decision variables that you can’t tell whether performance moved because of better traffic, a different signal, a new message, or a changed offer.
Use AI to produce testable hypotheses, not synthetic certainty
Use prompts as structured briefs. Supply the offer, intended customer, price context, conversion action, observed performance pattern, and any known constraints. Then ask for hypotheses that can be checked against real query, CRM, sales, or order data.
Purchase intent prompt: Separate the audience into people likely to act now, people who need persuasion, and people who are poor fits. For each group, identify the observable evidence that would confirm or reject the classification.
Emotional context prompt: Identify the fears, frustrations, ambitions, and desired relief that could influence this customer. Distinguish plausible motivations from claims requiring customer evidence.
Objection prompt: Generate three to five credible objections to this offer. For each one, propose a response based on logic, emotion, and proof, but flag any proof the business must substantiate.
Value diagnosis prompt: Given rising conversion volume and falling Value/Conv., propose segment, query, audience, product-mix, and order-value explanations. Rank them by what can be checked with the available data.
Lifetime-value prompt: Explain why a customer might stay, buy again, or expand the relationship. Convert each idea into a retention hypothesis and specify what data would demonstrate that it is real.
The output is not customer evidence. AI can make an unsupported psychological profile sound convincing, invent proof, or favor a neat explanation for a messy performance change. Check proposed motivations against search terms, customer language, objections heard by sales, and observed buying behavior. Delete claims you can’t substantiate.
Turn each surviving idea into a compact experiment card:
Hypothesis: what you believe will change and why.
Audience: the specific intent or customer group being tested.
Variable: the message, creative, landing page, query treatment, audience input, or value signal you will change.
Primary measure: the valuable outcome that determines success.
Guardrails: the quality, cost, average-value, or downstream metrics that must not deteriorate unnoticed.
Decision: what you will scale, revise, or stop after interpreting the result.
A test is useful even when it loses, provided it isolates a meaningful decision. A higher click-through rate with weaker lead quality tells you the message attracted the wrong kind of attention. More conversions with lower order value tells you the platform responded to the signal but the signal didn’t represent enough value. Those are findings you can act on.
Key takeaways
Optimize for the deepest reliable business outcome, not the largest conversion count.
Give different conversion actions different treatment when their downstream value differs.
Apply tight control to commercially important intent and give automated discovery explicit boundaries.
Keep upper-funnel activity visible and judge it by its defined support role, not by impressions alone.
When results weaken, trace the path from revenue backward until you find the first relationship that changed.
Use AI to generate and rank hypotheses, then validate them with customer and performance data.
Start with one campaign, not an account-wide rebuild. Write its economic objective, audit the conversion actions influencing bidding, and inspect which queries or audiences produce the valuable outcome. Make the smallest signal or routing change that addresses the gap, record the expected effect, and let the next decision follow from business results rather than interface activity.
I’ve been noticing the rapid transformation in how brands are tracking user behavior online. With privacy laws tightening and browser extensions increasingly blocking data, the demand for cleaner data from ad platforms is higher than ever. This change urged me to explore server-side tagging as a solution.
By implementing server-side tagging, I’ve managed to reduce data loss while collecting cleaner, privacy-compliant data. This approach is invaluable, especially considering the experiences I’ve had with providers like Elevar and Littledata.
So, what exactly is server-side tagging, and in which situations does it really shine? Let’s dive into the details!
What is server-side tagging?
Traditionally, tracking scripts ran directly in the browser. However, with server-side tagging, these scripts operate on a server I control, giving me more control over data processing.
Here’s how it works: instead of sending data straight to multiple third parties from the browser, events are sent to a first-party server endpoint, often using a Google Tag Manager server-side container. The server then processes, enriches, and forwards this data to tools like Meta and Google Analytics.
This setup provides benefits such as more data control, a cleaner page performance, and better compliance with privacy laws.
Moreover, server-side tagging grants me the flexibility to enrich and transform data before it reaches ad platforms, standardizing event names, filtering out low-quality events, and adding custom parameters for better audience segmentation.
Is server-side tagging right for you?
While server-side tagging isn’t a one-size-fits-all solution, many brands find it essential, particularly if you:
You need to meet strict privacy or compliance requirements
Server-side setups allow for greater control over how data is processed and shared, supporting compliance with regulations like GDPR and CCPA.
You want faster website performance
In my experience, client-side tracking can slow your page down, but server-side tagging shifts data processing to the server, resulting in faster websites.
You want more accurate tracking (despite ad blockers)
Ad blockers can hinder client-side scripts, but server-side tagging circumvents many of these restrictions, making your data collection more reliable.
You’re investing heavily in paid media
For those heavily invested in platforms like Meta and Google Ads, achieving better data accuracy can significantly impact return on ad spend.
How to implement server-side tagging
When it comes to implementing server-side tagging, you have two main options: building it internally or using a service provider.
Option 1: Internal setup
Choosing an internal setup gives me complete control but requires technical expertise and ongoing maintenance. This involves setting up a GTM server-side container and adding logic for data processing.
Option 2: Use a server-side tagging service
Platforms like Elevar and Littledata offer turnkey solutions that integrate seamlessly with existing tools, allowing me to focus on strategy rather than technicalities.
Our direct experience: Littledata vs. Elevar
In my experience with Littledata and Elevar, each caters to different needs. Littledata is ideal for emerging brands with simpler tech stacks, while Elevar is suitable for those outgrowing entry-level solutions.
Investing in server-side tagging has transformed how I handle data, ensuring that I remain compliant with privacy laws while boosting site performance and data reliability across all my platforms.
You can hire an agency that improves a channel and still end up with a weaker growth system. Paid media may generate cheaper leads that sales cannot convert. Organic visibility may rise while qualified website visits fall. Marketing may create demand that service and operations are not prepared to support.
The answer is not a longer list of tactics. You need a growth operating model that connects customer states, discovery surfaces, commercial outcomes and decision rights. Once that model is clear, you can judge whether an agency will strengthen it or merely manage part of it.
Replace the single funnel with a growth operating system
Inbound marketing gave teams a coherent sequence: attract an audience, convert visitors and nurture leads. That logic remains useful, but it cannot carry the entire growth plan when discovery, evaluation, conversion and retention happen across different systems.
The old relationship between visibility and traffic is changing as well. An AI-generated answer can satisfy part of a search without sending the user to a website. A prospect can encounter a brand in an AI answer, validate it through search, read customer commentary, click a paid ad later and enter the CRM as direct traffic. A channel report may credit the final interaction while missing most of the journey.
A modern growth model should therefore answer four connected questions:
Model layer
Question to answer
Evidence you need
Commercial outcome
What business result are we trying to change?
A primary outcome, its definition and financial or operational guardrails
Customer state
What must become true for the customer to move forward?
Questions, objections, intent signals and points of friction
Discovery and delivery surfaces
Where can we create, capture, convert or retain demand?
A defined role for search, AI answers, content, paid media, sales and service
Learning loop
How will evidence change the next decision?
An owner, review cadence, decision threshold and change record
If one of these layers is missing, the agency will fill the gap with its own assumptions. A media agency may treat platform revenue as the outcome. An SEO agency may treat rankings as the outcome. A content agency may treat publishing volume as the outcome. Those measures can be useful, but none is a substitute for the business result you hired the partner to influence.
Build the growth brief before you write the agency brief
An agency request for proposal usually starts with services: SEO, paid search, content, analytics or AI optimization. Start one level higher. Describe the growth constraint first, then determine which capabilities are needed to remove it.
Name one primary outcome. State the business result, not the marketing activity. Pair it with guardrails that prevent a local win from damaging lead quality, margin, retention, brand standards or another important constraint.
Map the customer states. Identify what customers need when they are recognizing a problem, evaluating options, making a purchase, adopting the product and deciding whether to continue. Use the states that fit your business instead of forcing every journey into a generic funnel.
Locate the actual constraint. Determine whether the problem is insufficient demand, poor discovery, weak consideration, conversion friction, slow sales follow-up, onboarding failure or low retention. Do not commission more acquisition work when the binding constraint sits after acquisition.
Assign a job to every surface. Decide whether each channel is meant to create demand, capture existing demand, answer a question, support evaluation, convert intent or retain a customer. A surface can support several jobs, but it should have one primary role in the plan.
Define the learning loop. Record what will be observed, who interprets it, which decision it informs and who can approve the change. Reporting without a decision path produces dashboards, not growth.
This is especially important for SEO, answer engine optimization and generative engine optimization. They overlap, but they are not interchangeable line items. SEO can improve discoverability in conventional search. AEO can make an answer easier to extract and present. GEO can focus the work on how generative systems understand, retrieve and represent a brand. Your measurement plan should preserve those distinctions while connecting them to the same customer journey.
Do not force every visibility signal into an immediate revenue calculation. A metric can guide optimization without proving causal impact. Rankings, answer inclusion, brand mentions and qualified visits can show whether discovery is changing. CRM progression, revenue and retention can show whether commercial performance is changing. The agency should explain the relationship between those layers without pretending that one attribution model observes the entire journey.
Your completed growth brief can be one page. It should contain the primary outcome, guardrails, constrained customer state, surface roles, measurement definitions and unresolved questions. That page gives every prospective agency the same problem to solve and makes proposals easier to compare.
Divide ownership before you evaluate capabilities
A growth partner needs room to make decisions, but outsourcing execution does not transfer accountability for the business. Clarify what the brand owns, what the agency owns and what must be shared before discussing deliverables.
The brand should retain business truth. This includes commercial priorities, customer definitions, approved claims, margin constraints, risk tolerance and the final authority over budgets and data access.
The agency should own recommendations and agreed execution. It should identify opportunities, explain trade-offs, perform work within the approved boundaries and maintain a record of material changes.
Measurement should be shared. The agency may build reports, but metric definitions, attribution limitations and tracking changes must be visible to both sides. Neither party should be able to change the meaning of success silently.
Cross-functional decisions need one accountable lead. Someone must reconcile conflicts among marketing, sales, service and operations. A committee can contribute, but it cannot substitute for a named decision-maker.
This ownership map also exposes misleading claims of being full service. A long service menu tells you what an agency is willing to sell, not where it repeatedly performs strong work. Ask what percentage of clients actually use each advertised service. Then ask who leads that work, what other capability it depends on and where the agency normally brings in outside expertise.
Build a simple capability map for every service that matters to your brief. Record the service, client utilization, named practice lead, proposed account owner, proof artifact, dependencies and known limitations. A strong specialist can be a better fit than a nominally full-service agency if your team is prepared to integrate the work. A broad partner can be the better choice when coordination is the main constraint. The right answer depends on the operating model, not the size of the service catalog.
Audit the agency’s decisions, not its pitch language
Most agencies can produce a polished audit and a plausible list of opportunities. Your evaluation should reveal how the team prioritizes, measures, automates and changes course after the pitch is over.
Ask six questions that require operational answers
Which services are genuinely central to your business, and what percentage of clients use each one? Look for a precise denominator, a distinction between core and occasional work, and a candid explanation of where the agency is not the best fit. A service list with no utilization data does not establish depth.
How do you combine platform automation, AI optimization and human judgment? Ask which decisions are delegated to platforms, which inputs the team controls, which guardrails prevent undesirable optimization and what triggers human intervention. “AI-powered” is a label, not an operating procedure.
How does reporting lead to a decision? Have the team walk through an anonymized reporting environment. Ask them to start with the business outcome, trace the supporting indicators, identify an uncertainty and show the action that followed. Revenue and return on ad spend may belong in the view, but the team should also explain attribution assumptions and data limitations.
Who will work on the account, and what is the team’s relevant industry tenure? Get names, roles, responsibilities and escalation paths. Distinguish the senior experts who appear in the pitch from the people who will perform and review the work.
How does your team use generative AI on client work? Separate internal uses, such as analysis or drafting, from advertising-platform automation. Ask which client data can enter a tool, what receives human review, how outputs are checked and how material decisions are documented.
What would you inspect first to reduce waste without suppressing growth? A strong answer should describe a sequence: validate measurement, preserve a baseline, inspect settings and allocation, identify suspected waste, estimate the downside of a change and verify the effect after implementation. A promise to cut spend immediately is not evidence of efficiency.
Score each answer from zero to two. Give zero for a vague claim, one for a credible process without supporting proof, and two for a specific process backed by an artifact and a named owner. This produces a maximum score of 12, but the total is less important than the pattern. A partner that scores well on capabilities but poorly on measurement or ownership can create activity faster than it creates learning.
Set knockout conditions before the presentations begin. Examples include refusing to identify the delivery team, being unable to explain data handling, treating platform-reported attribution as unquestionable, or requesting unrestricted budget authority before measurement is validated. Predefined conditions prevent presentation quality from overriding operational risk.
Turn the winning answers into the working agreement
Anything important enough to influence agency selection belongs in the operating agreement. Otherwise, the senior strategist, reporting method or review practice that won the pitch may disappear during delivery.
Decision rights: Record who can change budgets, targeting, conversion events, content claims, schema, site templates and measurement configurations.
AI boundaries: Define approved uses, prohibited data, review requirements and the person accountable for an AI-assisted output.
Change control: Preserve the baseline, document material changes and record the expected effect before implementation.
Reporting logic: Require each review to show what changed, how confident the team is, what may have caused it, what decision follows and who owns that action.
Escalation: Specify what happens when tracking fails, automation pursues the wrong signal, spend moves outside an agreed boundary or results conflict across systems.
Capability continuity: Define how staffing changes are communicated and how critical account knowledge is transferred.
Give a new partner read access before authorizing material changes whenever the platform permits it. Validate conversion definitions, tracking and historical baselines first. Changing optimization events and budgets at the same time can make the result difficult to interpret, and automation can scale the wrong objective quickly. The safer sequence is to establish measurement, document the hypothesis, make a bounded change and inspect the result before expanding it.
The same discipline should continue after onboarding. Do not evaluate the relationship by deliverable volume alone. Evaluate whether the agency is improving decision quality: finding the real constraint, making uncertainty visible, reducing waste, connecting work across the journey and leaving your team with a clearer understanding of what to do next.
Key takeaways
A modern growth model connects commercial outcomes, customer states, discovery surfaces and a defined learning loop.
Write the growth problem before selecting services. Otherwise, every agency will frame the problem around what it sells.
Keep business truth and final accountability with the brand while giving the agency explicit execution and recommendation rights.
Test full-service claims with client utilization, named specialists, dependencies and proof of repeatable delivery.
Evaluate platform automation and internal generative AI separately; both require clear inputs, guardrails, review and escalation.
Convert important pitch promises into decision rights, reporting rules, staffing commitments and change-control procedures.
Before your next agency conversation, complete the four-layer growth model for one important constraint and send the six audit questions in advance. Ask every contender to answer with artifacts, named owners and explicit limitations. The partner that can work inside that level of clarity is far more useful than one that merely offers the longest list of channels.
Your campaign can be configured correctly inside every advertising platform and still produce a measurement mess. The ad attracts an interaction, the tag records an event, analytics classifies it differently, and the bidding system optimizes toward something nobody intended.
The fix is not another dashboard or another tag. You need one traceable chain from the format a person sees to the business outcome you want, with a clear role and a test at every handoff.
Key takeaways
Define each conversion in business terms before configuring it in Google, Meta, Google Tag Manager, or an analytics property.
Give ad formats, tagging, measurement, and automation separate jobs and separate acceptance tests.
Treat every new ad format as a new measurement surface, especially when one unit presents several locations or choices.
Reuse an established data layer through official platform templates where supported, but verify mappings and duplicate events before publishing.
Do not increase spend until you can trace one test action from the page or app through the tag, platform, report, and optimization setting.
Build one conversion contract before touching platform settings
Advertising platforms encourage you to start with their menus: choose an objective, install a tag, select an event, and launch. That sequence is convenient, but it lets each platform define your measurement model. The same customer action can then become a primary conversion in one account, a secondary event in another, and an analytics event with a third meaning.
Start with a conversion contract instead. This is a short specification for what happened, why it matters, and how every system should represent it. For each event, record:
You may be optimizing product pages for the click while Google is redesigning shopping around a different outcome: identify a suitable product, validate the choice, and potentially complete the purchase inside AI Mode or Gemini. That changes where ecommerce visibility is won.
You now need two connected systems. The first makes your catalog understandable and competitive during AI-assisted discovery. The second lets an approved product move through an in-search transaction without introducing price, availability, identity, or payment failures. Here is how to prepare both without confusing checkout access with search visibility.
The new commerce funnel starts in the product graph
A conventional SEO funnel assumes that search earns a click, the product page creates confidence, and the merchant site completes the sale. Google’s emerging commerce model can compress those stages. A user may describe a need conversationally, receive product recommendations, compare options, and check out without following the familiar sequence of search result, landing page, cart, and checkout.
Generic titles, missing identifiers, weak attributes, or unusable images make the product hard to match and compare.
Product page
Do the details support the product record and the buyer’s decision?
The page and feed describe different variants, benefits, prices, or availability.
Commerce integration
Can the selected product be purchased successfully in the Google experience?
The discovery record cannot be resolved to the correct variant, checkout state, identity, or payment flow.
Use those layers to triage problems correctly. Low discovery visibility is usually a matching and data-quality problem before it is a checkout problem. A visible product that cannot complete a transaction is an integration problem. A product that earns attention but not purchases may have a merchandising, offer, or expectation problem. Putting every weak result under the label of SEO hides the part that actually needs work.
Make the product feed an organic discovery asset
Many merchants let the paid media team own the only feed. That arrangement keeps campaigns running, but a feed shaped around bid relevance and advertising conventions is not automatically the best representation of how people search organically. Paid and organic outputs can share a catalog while applying different rules to titles, descriptions, and supporting attributes.
Build records around the language of product selection
The title is your highest-priority matching field. Write it so a person can identify the product without seeing the image or visiting the page. Start with the product type and add the attributes that genuinely distinguish the item, such as brand, material, capacity, size, color, compatibility, or intended use. The useful combination depends on the category. Do not force every possible modifier into every title, and do not repeat words merely to make the record longer.
A good test is to compare the title with the phrases a buyer would naturally use when narrowing a choice. If shoppers distinguish your products by capacity and compatibility, those attributes deserve more attention than internal collection names. If the title could apply equally to many products in your own catalog, it is probably too vague for an AI system to select confidently.
Use accurate GTINs where the product has them. Correct identifiers help Google match identical products, combine relevant information such as reviews, and understand that two differently worded listings refer to the same item. Well-matched products with accurate GTINs can receive up to 40% more clicks. Never invent an identifier or reuse one from a different variant.
Supply both clear standard images and useful lifestyle images. The standard image should make the product easy to identify. A lifestyle image should add context, scale, or use information rather than obscure the item. Image problems can also cause Merchant Center disapprovals, so treat asset validation as feed health, not decoration.
Use product_highlight for concise buyer benefits. Replace empty claims such as high quality with concrete outcomes. A statement about handling light rain during a commute tells the buyer more than an unsupported adjective.
Use product_detail for structured specifications. Put filterable facts such as dimensions, material, capacity, and compatibility into the structured field that represents them. Do not bury every decision-critical fact in prose.
Keep the feed and product page synchronized. A refined feed title cannot compensate for a page that represents a different variant, price, feature set, or availability state. The two surfaces should describe the same purchasable product.
Create a controlled organic output
You do not need two unrelated catalogs. You need one reliable product source and a controlled way to publish an organic-oriented output without letting paid campaign conventions overwrite it. Depending on your commerce stack, that may be a dedicated feed or a dedicated set of transformation rules. Either way, document which fields are canonical, which fields may vary by channel, and who approves each change.
The potential impact is material, but it should not be treated as a guaranteed benchmark. In one major ecommerce implementation, an organic feed produced a 10% month-over-month increase in organic listing click-through rate and a 4% increase in purchase rate. A product-level test recorded 92% higher free-listing revenue, 83% more visibility, and a 14% increase in add-to-cart rate. Another organic optimization set generated 35,000 impressions at a 1.4% click-through rate, which was 55% above the paid click-through rate for the same period. Those results establish that feed changes can be commercially important; they do not establish a universal lift for every catalog.
Run your own controlled evaluation:
Select a coherent product group with enough existing activity to measure.
Record its free-listing impressions, click-through rate, add-to-cart rate, purchase rate, and revenue before changing the feed.
Change one field family at a time when practical. A title test is easier to interpret if you do not simultaneously replace every image and description.
Keep a version log that connects each feed change to the affected product IDs.
Compare product-level outcomes, not only catalog-wide averages. A large category can conceal both strong winners and harmful rewrites.
Check paid performance separately. An organic improvement does not prove that the same wording should replace a paid title optimized for a different matching and bidding context.
The goal is not to make the organic feed sound conversational at any cost. It is to make the product record precise in the language buyers use while preserving exact identifiers, specifications, and variant distinctions.
Prepare for UCP without mistaking checkout for ranking
Approval opens a transaction path; it does not establish a search-ranking benefit. Treat discovery eligibility and transaction readiness as separate workstreams unless Google explicitly documents a connection. A product still needs strong, consistent data to be selected. UCP then addresses whether the selected item can move through checkout inside the Google experience.
Google has also added a native_commerce attribute for UCP-powered purchase buttons. Do not treat that attribute as a shortcut around integration quality. A buy button attached to stale price, availability, or variant data creates a more immediate failure than a conventional listing because the shopper is already trying to transact.
Confirm the access path. Check Merchant Center for UCP onboarding availability and follow the interest and approval process. Do not promise a launch date internally until the account has access.
Assign a catalog system of record. Every purchasable variation needs a stable mapping between the feed record and the item your checkout can fulfill. Resolve duplicate identifiers and unclear parent-variant relationships before transaction testing.
Map the checkout data contract. Identify which system owns product identity, selected variant, price, availability, buyer identity, payment state, and transaction outcome. Document how a change in one system reaches the others.
Use the available sandbox. Merchant Center onboarding includes a testing sandbox, identity linking, and checkout APIs. Test successful transactions as well as unavailable products, changed prices, unresolved identities, declined payments, and interrupted requests.
Define operational ownership. SEO can improve matching, but commerce, engineering, privacy, security, payment, and customer-support owners need responsibility for the parts they control. Decide who pauses native checkout when catalog or transaction data becomes unreliable.
Activate only after reconciliation. The feed, product page, commerce system, and transaction response must resolve to the same product and offer. If they do not, keep the safer redirect-based journey until the mismatch is fixed.
This is where cross-team collaboration becomes practical rather than ceremonial. SEO contributes query language and matching logic. Commerce owns product truth and fulfillment constraints. Paid media teams often understand feed tooling and disapproval management. Engineering owns the integration path. Each team should have a named field or state to maintain, not a general instruction to support AI commerce.
Measure discovery and checkout as one journey, not one metric
In-search checkout weakens the old assumption that a successful search interaction produces a website session. When a customer can purchase inside an AI interaction without being redirected to the merchant site, traffic alone becomes an incomplete measure of both SEO and commerce performance.
Build a measurement chain that follows the product as far as your available data allows:
Catalog health: Track active products, rejected or disapproved items, identifier coverage, image issues, and unresolved feed-page discrepancies. A product excluded before matching cannot generate a meaningful visibility or conversion signal.
Discovery: Track impressions and click-through rate by product, product group, query class, and Google surface where those dimensions are available. Separate free listings from paid placements.
Consideration: Track the interactions you can observe between a product impression and checkout. Keep website engagement separate from native interactions so a change in surface mix does not look like a sudden behavioral collapse.
Transaction: Track checkout attempts, successful purchases, failures, and the product or variant involved. Preserve a reference that lets commerce and analytics teams reconcile the transaction with the originating product record.
Business outcome: Compare completed orders and revenue with website sessions and site-based orders. A decline in site traffic is not automatically lost demand if more transactions are completing elsewhere. It is also not automatically good news; you need reconciled purchase data to tell the difference.
Capture a baseline before enabling native checkout. After activation, segment results by surface and product group rather than comparing one blended total with the previous period. Otherwise, a shift from website checkout to Google checkout can be mistaken for an SEO loss, while a surge in product impressions can be mistaken for commercial growth without completed purchases.
Document your attribution rule as part of the integration. Decide how you will classify a purchase discovered in AI Mode, completed through native checkout, and fulfilled by your commerce system. The rule matters less than using it consistently and making its limits visible. Do not allow SEO, paid media, and commerce dashboards to claim the same order independently.
You should also watch for substitution. Native checkout may replace a transaction that would otherwise have occurred on your site, or it may capture demand that would have been lost through extra steps. Compare the full order picture rather than assuming every native purchase is incremental or every missing session represents cannibalization.
Key takeaways
Google commerce visibility begins with product data, so Merchant Center feed quality is now part of organic and AI search optimization.
Optimize organic titles around the attributes buyers use to identify and distinguish products, while preserving accurate GTINs, specifications, images, price, and availability.
Use a dedicated organic feed or controlled organic transformation rules instead of forcing paid and free listings to share every optimization decision.
Treat UCP as a checkout capability, not a ranking shortcut. Discovery quality must be solved before native transaction readiness can help.
Prepare stable product mappings, clear system ownership, sandbox failure tests, and a safe way to pause native checkout when data becomes unreliable.
Measure catalog health, discovery, transaction outcomes, and total orders together because website sessions no longer represent the entire shopping journey.
Start with a catalog reconciliation, not a checkout build. Choose a representative product family and align its titles, identifiers, attributes, images, page details, price, and availability. Then name the owner of every field and transaction state. That work improves discovery whether or not UCP access has reached your account.
When access becomes available, take the same reconciled products through the sandbox before expanding. You will learn more from a small group with traceable data and observable failures than from activating native checkout across a catalog whose product truth is still disputed.
If your organic sessions are falling while your brand still appears in AI answers, you do not have one visibility problem. You have at least three: whether machines can access your content, whether answer systems select it, and whether people visit after seeing it.
Those stages need different measurements and different fixes. Separate them, and you can tell whether to improve a page, investigate a ranking change, strengthen attribution, or restrict a crawler before it consumes more value than it returns.
Key takeaways
Measure content access, AI mentions and citations, referral sessions, and business outcomes separately. A lost click is not automatically lost visibility.
Diagnose impressions, rankings, click-through rate, and AI referrals before editing content. Ranking loss and referral loss can happen together, but they are not the same failure.
Give answer systems a clear, supportable answer while giving people a practical reason to visit, such as a workflow, template, decision tool, original data, or implementation detail.
Classify bots by identity and business role. Allow, rate-limit, license, challenge, or block them according to their value, cost, and contractual status.
Build a visibility ledger that follows the whole journey
Sessions used to serve as a rough proxy for search visibility because discovery commonly led to a results page and then a click. An AI interface can now retrieve a page, use its information, mention its brand, cite its URL, and still satisfy the user without sending a visit. One traffic graph cannot show which of those events occurred.
Use a ledger with three distinct stages:
Access: a search crawler, training crawler, or real-time fetcher can retrieve the page.
Selection: an answer system uses the information, mentions the brand, or links to the page.
Referral and value: the user visits, engages, subscribes, generates a lead, or completes another meaningful action.
The distinction matters because the gap can be severe. Akamai measured application-layer traffic across websites, apps, and APIs from July through December 2025 and found AI bot activity up 300% during 2025. Within that analysis, AI-chatbot referrals delivered about 96% less traffic than traditional search, while only about 1% of users clicked sources cited in AI answers. Treat those figures as directional evidence, not universal benchmarks: your result will depend on your audience, query mix, business model, and the interfaces that expose your content.
Layer
Record
What a change can indicate
First response
Traditional search exposure
Impressions, query, landing page, market, and average position
Changes in demand, ranking, eligibility, or query mix
Segment the loss before changing pages
Traditional search referral
Clicks, click-through rate, sessions, and landing-page outcomes
A difference between being shown and being chosen
Inspect result presentation, search features, intent, and page promise
AI selection
Accurate brand mentions, linked citations, cited URLs, and factual errors across a fixed prompt set
Whether the brand is represented and whether an owned page receives attribution
Check entity clarity, answer structure, evidence, and page accessibility
AI referral
Raw referrer, channel, landing page, engagement, conversion, and revenue where available
Whether observed visibility produces visits and business value
Improve the post-answer reason to visit and the landing experience
Whether retrieval consumes infrastructure without a corresponding benefit
Allow, rate-limit, license, challenge, or block by bot class
For AI selection, build a repeatable prompt panel rather than collecting convenient screenshots. Include the questions that matter at each stage of your customer’s decision, then preserve the exact prompt, interface, language, market, date, response, mention, citation, and cited URL. If you operate across languages or countries, maintain separate panels; visibility in one market does not establish visibility in another.
Choose prompts from real search queries, support questions, sales objections, and tasks associated with your important pages.
Run the same prompts under comparable conditions. Changing the wording and the interface at the same time makes the result difficult to interpret.
Record an accurate mention separately from a linked citation. A brand can be visible without receiving an owned link.
Check whether the answer represents the brand, product, author, and claim correctly. An inaccurate mention is not a visibility win.
Annotate content releases, schema changes, crawler-policy changes, major deployments, and confirmed search updates beside the results.
Create simple rates from this ledger: prompts with an accurate mention divided by prompts checked; prompts with an owned citation divided by prompts checked; and AI-referred conversions divided by identifiable AI-referred sessions. Keep the underlying counts beside every rate. A perfect percentage from a tiny or changing prompt set can create more confidence than the measurement deserves.
Normalize recognizable AI referrers into a reporting channel, but preserve the raw referrer and landing page. Do not depend on campaign parameters for links you do not control. Some interfaces expose little or no useful referral information, so analytics should be treated as the observable portion of AI traffic, not a complete census of AI influence.
Separate ranking loss from click loss before editing content
A traffic decline near an algorithm update invites a quick rewrite. That can destroy useful evidence and change the page before you know what failed. Start by marking the rollout window. The March 2026 Google core update ran from March 27 through April 8, finishing after 12 days and 4 hours. A comparison that mixes rollout days with stable periods cannot cleanly separate the before and after states.
Annotate the confirmed update window and every important site change, including migrations, template releases, internal-link changes, rendering changes, and crawler rules.
Compare matched periods outside the rollout. Account for normal seasonality, promotions, and demand changes that affect the same queries.
Segment by query group, page type, directory, market, and device. Sitewide averages can conceal a concentrated loss in one template or topic.
Inspect impressions, position, clicks, and click-through rate together. Then compare those patterns with your sampled AI visibility and AI-referral data.
Review the affected page group only after the failure mode is visible. Preserve an export or snapshot before making material changes so you can evaluate and reverse them.
Use the pattern, not one metric, to choose the next action:
If impressions and positions decline for the same queries and pages, investigate a ranking, relevance, eligibility, or demand problem. Do not assume that a lower sitewide average tells you which one.
If impressions remain broadly stable while clicks and click-through rate decline, the result is still being shown but fewer searchers are choosing it. Inspect the result-page features, title and snippet promise, intent fit, and competing ways the query is answered.
If traditional search remains stable while sampled AI citations or identifiable AI referrals decline, check machine access, citation selection, brand ambiguity, and measurement coverage before rewriting the page.
If sessions decline but qualified leads, subscriptions, or revenue do not, quantify the commercial effect before setting a traffic-restoration target. Not every lost informational click has the same value.
If several layers decline at once, keep separate workstreams. A content review cannot repair broken bot access, and a crawler rule cannot make an unsatisfying page more useful.
Google’s standing position is that a core-update decline does not necessarily mean something is wrong with the site, and meaningful recovery may depend on a later update. That is a reason to avoid panicked reversals, not a reason to wait passively. Review whether affected pages deliver helpful, reliable, people-first information, especially where the page promise and the actual answer have drifted apart.
Create pages that can be cited and still deserve a visit
Trying to withhold the basic answer is a poor response to zero-click search. It frustrates readers and leaves answer systems with weaker material to interpret. State the answer clearly, support it, and make the rest of the page valuable after the answer is known.
A citation-ready, visit-worthy page usually needs these layers:
A decisive answer: address the page’s main question directly instead of making the reader extract it from a long preamble.
Scope and qualifiers: state the country, language, platform, version, date, audience, or conditions that change the answer. A technically correct statement can still mislead when its scope is hidden.
Evidence: connect important claims to their originating authority, underlying data, or documented method. Distinguish a fact from an inference or editorial recommendation.
Entity clarity: use consistent names for the organization, product, author, location, and service. Explain relationships that a reader should not have to infer from branding alone.
A decision layer: show trade-offs, applicability, exclusions, and common misreadings so the reader can decide whether the answer fits their situation.
An action layer: provide the procedure, checklist, template, calculator, original data, implementation detail, or troubleshooting path that helps the reader complete the task.
This structure makes the central claim easy to identify without turning the page into a disposable definition. The answer earns selection; the decision and action layers earn the visit.
JSON-LD can clarify what a page represents, but it is not a referral strategy and it does not guarantee selection in an AI answer. Use the schema type that matches the visible content, connect related entities consistently, and validate the markup after publishing. Do not place claims, reviews, authorship, dates, or relationships in structured data that the page itself does not support.
Apply the same discipline to freshness. Show a meaningful update date when the substance changed, identify version-dependent instructions, and remove contradictions between the page, its metadata, and its structured data. Changing a date without revising stale information creates a freshness signal for the editor, not new value for the reader.
Before consolidating or unpublishing a weak page, check its inbound links, internal links, ranking queries, citations, conversions, and role in a topic cluster. Preserve a copy and plan the appropriate destination before removing a URL. A careless cleanup can erase authority or break an existing citation even when raw sessions look unimportant.
Turn AI crawler access into an explicit business policy
More machine access does not automatically produce more discovery, attribution, or revenue. It can also increase server and CDN costs. The 300% rise in AI bot activity observed during 2025 makes bot classification an operating issue, not merely a security log to review after something breaks.
Start by separating training crawlers, which collect material for model development, from real-time fetchers, which retrieve current content to answer a live request. Their timing, potential value, and commercial relationship differ. A single allow-or-block rule ignores those differences.
Bot class
Possible business role
Policy options
Main risk to check
Search or discovery crawler
Makes pages eligible for a discovery surface
Verify and allow under controlled limits
Blocking can remove a path to visibility
Authenticated licensed agent
Accesses content under agreed commercial terms
Allow only within authenticated scope and limits
Unverified requests may exceed the agreement
Real-time answer fetcher
Retrieves current information for an immediate answer
Allow, rate-limit, or license according to measured value and cost
Fresh content may be consumed without useful attribution or referral
Training crawler
Collects content for model development
Allow, block, or license according to rights and commercial policy
Direct referral value may be weak or unobservable
Unknown or abusive scraper
No verified legitimate role
Challenge, rate-limit, block, or cautiously tarpit
Spoofed identities and false positives can misclassify traffic
A user-agent string is a claim, not proof. Where an operator publishes a verification method, use it. Keep agent identity, request behavior, targeted URLs, bandwidth, origin load, and any referral or licensing value in the same review. That turns a vague bot debate into a policy decision supported by observable costs and benefits.
Observe before enforcing. Establish which agents request which page groups and how much infrastructure they consume.
Verify identity. Do not grant privileged access or apply a punitive rule solely from a self-declared bot name.
Assign a role. Record whether the agent supports discovery, live answering, training, a licensed relationship, or no recognized purpose.
Choose the least disruptive effective control. Options include scoped access, caching, rate limits, authentication, challenges, blocking, and carefully tested tarpitting.
Stage material changes with a rollback path. Watch crawl activity, indexation, sampled AI citations, referrals, server load, and user errors after enforcement.
Review licensing and content-rights terms with appropriate legal counsel before charging for access or signing an agreement. A crawler configuration cannot determine ownership or contractual rights.
Robots directives can communicate preferences to compliant agents, but they are not authentication or an access-control wall. Enforce sensitive or paid access with controls that can identify and authorize the requesting agent. If you use tarpitting, apply it only after careful classification: deliberately slowing the wrong traffic can harm legitimate discovery or user-facing performance.
Emerging approaches such as Know Your Agent identity verification and TollBit pay-per-crawl access are intended to turn retrieval into an authenticated, manageable transaction. Treat that model as an option to evaluate, not guaranteed replacement revenue. The commercial case still depends on enforceable identity, demand for your content, contract terms, delivery cost, and the value of any visibility you give up by restricting access.
Your next move should come from the first broken link in the chain. Build the ledger, mark known update and deployment dates, test the questions that matter, and classify the agents consuming your pages. Then change one layer at a time and keep a rollback path. That is how you protect visibility without mistaking every lost click for a lost audience.
Embrace audience engineering to influence AI decisions, manage ad spend wisely, and connect with high-value customers through creativity and data.
I’m witnessing a significant transformation in the paid media landscape as platforms shift from manual targeting to AI-driven audience discovery. This change is redefining how we approach advertising, with automation tools consolidating campaigns, obscuring data, and favoring prediction algorithms over manual selection.
This transition requires me to innovate by mastering the art of audience engineering. By doing so, I ensure I’m equipped with strategies to thrive in this evolving landscape.
The End of Manual Targeting as I Knew It
Previously, I depended on detailed keyword lists and demographic filters to pinpoint my ideal audience. I directed platforms about where to focus and paid to access the desired market.
However, these options are now outdated:
Google has transitioned to Performance Max, which eliminates keyword-specific targeting in favor of more fluid groups and signals.
Meta’s Advantage+ automates demographic focus, turning my role into that of a signal provider instead of an audience selector.
Microsoft’s inclusion of this model confirms this is an industry-wide evolution.
While traditional targeting seems to have vanished, it has merely moved to the internal structures of the platforms where algorithms dictate the direction based on their indigenous data.
The Rise of Audience Engineering
My role shifts from targeting to engineering as it becomes more about guiding algorithms than manually selecting audiences.
From Targeting to Teaching
The distinction is crucial. Traditionally, targeting emphasized choosing audiences, but now it’s about educating AI with comprehensive conversion data, targeted creativity, and insightful first-party data.
Previously, I might have targeted CFOs with job filters, but now I feed the AI robust data (e.g., “deal closed” signals) to characterize valuable prospects and devise creative content tailored to their needs.
The New Competitive Discipline
Embracing this transformation gives me an edge. By finetuning conversion signals, honing creative content, and fortifying data systems, I ensure our performance remains robust.
The performance gap now relies on the quality of signals, making audience engineering pivotal for success.
The Three Levers that Now Drive Targeting
I focus on optimizing these three crucial AI inputs to ensure effective audience segmentation:
1. Conversion Signal Quality
By providing the algorithm with relevant business outcomes rather than superficial metrics, I encourage it to find results that truly matter.
Using tools like Offline Conversion Imports (OCI) and the Conversions API (CAPI), I ensure our data highlights genuine sales by leveraging value-based bidding techniques.
2. Creative as a Targeting Mechanism
With no demographic filters, my creative content now acts as the primary targeting tool, filtering users through its message.
If my creative targets niche pain points, the AI connects with users aligned with that perspective, even without traditional filters.
3. First-Party Data as Competitive Moat
Our customer lists and engagement signals become core learning elements for the algorithm, replacing third-party signals and offering a competitive edge.
Essentially, I’m arming the AI with a guide to discover the most profitable audiences.
How This Plays Out in Real Campaigns
The journey to AI-led targeting isn’t just theoretical. Within our agency, managing over $215 million in media spend annually, we have evaluated this approach across different platforms, witnessing its power firsthand.
Advantage+ Audiences in Practice
One long-standing client had a specific perception of their audience based on a vast history of accurate data. Initially, our campaigns ran with tightly controlled targeting to maintain efficiency.
Transitioning to Advantage+ allowed for data-driven optimization, revealing an unexpectedly lucrative older demographic, improving their click-through rates by 37% and conversion rates immensely.
Broader AI-optimized targeting cut costs and raised revenue — outperforming past manual methods.
By aligning goals with data and creative, we found valuable segments conventional targeting schemes previously overlooked.
Microsoft PMax Placement Transparency and Advanced Audience Signal Targeting
Another client benefited from a Microsoft PMax test, effectively targeting high-intent prospects using internal data across several Microsoft networks, seeing notable increases in performance metrics each month.
This trial highlighted the importance of combining strategic oversight with smart AI deployment, enhancing the algorithm’s reach while maintaining disciplined campaign direction.
The balance between scale and strategic input preserved efficiency and bolstered overall performance.
The Risks Nobody is Talking Enough About
While automated targeting offers significant advantages, it’s essential to understand its limitations. Here’s what I strive to avoid:
Garbage In, Garbage Out
Poorly defined conversion objectives, weak data quality, or junk data hinder performance and mislead the algorithm. Feeding it quality information and focused outcomes is crucial.
An overly broad goal without distinct signals results in quantity over quality, which doesn’t necessarily translate to business success.
The Self-Reinforcement Trap
If the seed data has biases, the AI will continuously optimize for those biases, possibly neglecting valuable audience segments.
These underrecognized biases present inherent risks in leveraging automated systems without mindfulness.
Automation Without Oversight
Platforms promote broad automation, but I recognize the need for continued oversight to realign campaigns with business goals.
Constant monitoring is essential to ensure objectives are met, avoiding a passive management style.
Creative Complacency
As automation advances, creative strategy becomes a crucial differentiator and shouldn’t be neglected.
Crafting compelling creative that addresses core customer issues is vital in distinctively standing out.
How to Put Audience Engineering into Practice
Here’s how I integrate audience engineering into everyday operations:
Restructure Creative: Focus on intent signals, addressing what beliefs inspire conversion.
Predefine Guardrails: Establish performance boundaries before unleashing the algorithm, allowing for better campaign control.
The Future Belongs to Audience Engineers
The era of manual targeting is closing, but precision remains crucial. Audience engineering acts as an invaluable skill, unlocking AI’s full potential to achieve maximum results in this dynamic landscape.
If you are comparing AI search optimization agencies, the hard part is not finding firms that promise more visibility. It is identifying which one can turn your content, technical foundation, brand knowledge, and authority into a coherent program without selling you a renamed SEO retainer.
Define the job before you ask agencies to solve it
AI search optimization is not a single deliverable. It is a set of connected activities intended to make your brand and content easier for AI systems to retrieve, understand, represent accurately, cite, and recommend when the context warrants it.
That distinction matters during procurement. If your brief says only that you want to improve AI visibility, every agency can interpret the assignment in a way that matches what it already sells. One may propose content production, another may lead with JSON-LD, and another may offer a monitoring dashboard. Those services can be useful, but none is a strategy by itself.
Start by defining the change you want across four layers:
Representation: AI-generated answers describe your company, products, people, and claims accurately.
Discovery: your brand or content appears for relevant questions where you have a legitimate reason to be included.
Evidence: the answer can connect its claims to useful, authoritative pages rather than merely mentioning your name.
Action: the visibility supports a sensible next step, such as visiting a product page, reading supporting evidence, comparing options, or contacting your team.
This framing prevents a common measurement mistake. A brand mention, a linked citation, an accurate recommendation, a referred visit, and a qualified conversion are not interchangeable outcomes. Record them separately. Otherwise, a dashboard can show improvement while the answers remain inaccurate or commercially irrelevant.
Your agency brief should give every contender the same operating context:
Your priority products, services, audiences, markets, and buyer situations.
The questions people ask while identifying a problem, comparing approaches, checking trust, and making a decision.
The pages, databases, documentation, and internal experts that act as your sources of truth.
Claims that require legal, compliance, technical, or subject-matter approval.
Your current content, development, analytics, public relations, and editorial resources.
The systems the agency may advise on and the systems it will actually be allowed to change.
The business outcomes you ultimately care about, along with the earlier signals you can observe before those outcomes occur.
Include a baseline rather than asking the agency to invent one after work begins. For each important question, save the exact wording, the AI service used, the date, the resulting answer, any linked citations, and whether the brand representation was accurate. Keep the relevant landing-page and conversion data alongside those observations when available.
A useful objective might be: improve accurate inclusion and citation for priority decision questions, direct qualified visitors toward authoritative pages, and establish a repeatable process for finding and fixing representation gaps. It is specific enough to guide a proposal without pretending that you control an external answer engine.
Inspect whether the strategy works as a connected system
A credible agency should be able to explain how audience demand, content, entity signals, technical access, outside authority, and measurement reinforce one another. It does not need to perform every activity itself. It does need to identify the dependencies and tell you who owns each one.
Question and intent discovery
Keyword research is useful input, but it does not fully describe the questions people put to an assistant. Ask how the agency will build a working set of questions from customer language, sales objections, support issues, product comparisons, documentation gaps, and conventional search demand.
The result should be organized by user task, not presented as a shapeless list of prompts. Someone defining a problem needs a different answer from someone comparing vendors or checking whether a solution fits a regulated workflow. That difference affects the required evidence, page format, and appropriate call to action.
Watch for invented precision. A prompt list becomes useful when the agency can explain why each question matters, which audience it belongs to, what a good answer must contain, and which page should support it. A large list with no decision context is inventory, not strategy.
Content and entity clarity
The agency should examine whether your pages answer the target questions clearly and whether the supporting claims are specific, consistent, and attributable. It should also distinguish between a missing page and a weak page. Publishing something new when an existing authoritative page needs a clearer answer can create duplication and split maintenance effort.
For each priority page, the plan should identify its subject, intended audience, direct answer, supporting evidence, related entities, internal links, maintenance owner, and next action. This turns vague advice such as improve content quality into an editable specification.
Entity consistency matters as well. Product names, company relationships, leadership details, service areas, and other defining facts should not conflict across core pages and structured data. Ask how the agency will find discrepancies and decide which internal record is authoritative before it recommends markup or rewrites.
Technical access and structured data
The technical review should cover whether important information is available on stable, indexable URLs; whether internal links make relationships understandable; whether canonicalization or access rules create conflicts; and whether templates hide, fragment, or duplicate key answers.
JSON-LD belongs in this workstream, but it should describe facts that users can verify on the page. Structured data can clarify the type of entity or content being presented and expose defined relationships in a machine-readable form. It cannot manufacture expertise, prove an unsupported claim, or rescue content that never answers the question.
Ask for a structured data inventory rather than a promise to add schema. The inventory should connect each proposed type and property to a visible fact, a source-of-truth field, an eligible page template, a validation method, and an owner responsible for keeping the information current.
Authority, distribution, and measurement
An on-site plan is incomplete if it ignores how the brand is represented elsewhere. Relevant mentions, expert contributions, documentation, original evidence, partnerships, public relations, and other legitimate forms of distribution can help establish context beyond your own domain. The agency should explain which activities are justified by the audience and where another team must participate.
Measurement completes the system. The agency should connect each recommendation to an observable change: a clearer answer on the page, corrected entity information, valid structured data, stronger citation coverage, more accurate AI representation, useful referred traffic, or a downstream business action. If the plan jumps from publishing content directly to revenue without showing the intermediate signals, you will struggle to diagnose either success or failure.
Test agency claims with evidence, not vocabulary
Most contenders can discuss AEO, GEO, AI SEO, entities, retrieval, citations, and structured data. Terminology tells you that the team follows the market. It does not tell you whether the team can diagnose your situation, prioritize work, implement recommendations, or separate its contribution from unrelated changes.
Use the same evidence request for every finalist:
Evaluation area
Ask to see
Evidence that matters
Relevant experience
A comparable, sanitized case narrative
The starting condition, diagnosis, intervention, implementation owner, observed change, and limits of the result
AI search expertise
A live explanation of one priority question and page
Clear reasoning across intent, answer quality, entities, technical access, authority, and measurement
Measurement
A sample baseline and recurring report
Raw prompts, captured answers, citations, accuracy judgments, dates, page metrics, and change history behind any summary score
Implementation
A sample content brief, technical ticket, or schema specification
Named owners, dependencies, acceptance criteria, quality checks, and a route from recommendation to release
Brand fit
An explanation of how the plan changes for your audience and constraints
Choices tied to your products, source material, risk, market, workflow, and business goals
Commercial clarity
A scope showing included and excluded work
Separate visibility into strategy, tools, production, development, outreach, reporting, and optional work
Do not accept a case study that starts with a result. Ask what was happening before the work, what changed, what else changed at the same time, and what evidence would weaken the agency’s interpretation. A team that can discuss confounding factors and uncertainty is giving you more useful information than one presenting a smooth success story with no audit trail.
A working session is especially revealing. Give each finalist the same page, target audience, and small group of priority questions. Ask the team to talk through what it would inspect first, which assumptions it would verify, what it would avoid changing prematurely, and how it would turn the diagnosis into tasks. You are assessing the reasoning process, not asking for unpaid strategic work.
Ask who will actually do the work after the sales process. You need to know which roles will handle strategy, content, technical analysis, JSON-LD, analytics, and project management; whether those people are assigned to your account; and where subcontractors or software-generated work enter the process. Senior expertise in a pitch has little value if delivery depends on an unnamed team using an undefined workflow.
Several claims deserve immediate scrutiny:
Guaranteed placement in generated answers. An agency cannot control the output of an external AI service, so it should promise defined work and transparent measurement rather than a specific placement.
A proprietary visibility score with no underlying observations. A score can summarize data, but you still need access to the prompts, outputs, citations, classification rules, and sampling conditions behind it.
Schema as the complete solution. Markup is one technical layer and should be connected to accurate visible content, source-of-truth data, and ongoing maintenance.
Content volume as the primary strategy. More pages can add duplication, inconsistent claims, and editorial debt when question coverage and page purpose have not been mapped first.
A monitoring dashboard presented as optimization. Monitoring can expose a problem; it does not research, edit, implement, validate, distribute, or govern the fix.
AI search results credited entirely to ordinary organic growth. Ask the agency to separate conventional search improvement, branded demand, public relations activity, product changes, and AI-specific observations wherever the available evidence allows.
Recommendations with no implementation owner. A technically correct audit still fails if nobody can convert it into approved changes in your CMS, codebase, data layer, or editorial process.
Build your scorecard before proposals arrive. Evaluate strategic fit, evidence quality, technical breadth, content judgment, measurement rigor, implementation clarity, governance, team continuity, and commercial transparency. Decide which criteria matter most for your current constraint. A company with strong in-house developers may need strategic and editorial depth, while a lean team may need a partner that can carry more implementation.
Put measurement, ownership, and change control in the scope
AI-generated answers can vary with prompt wording, service, context, and time. That makes a single screenshot weak evidence. It does not make measurement pointless. It means the method must preserve enough context for you to distinguish an observation from a trend and a trend from a business outcome.
For each monitored question, the measurement record should retain:
A stable identifier, exact wording, audience, intent, and market or language context when relevant.
The AI service, capture date, and other available execution context.
The complete answer or a faithful stored capture, not only a yes-or-no brand mention.
Whether the brand appears, what role it is assigned, and whether the description is accurate.
Every visible citation and whether it points to your site, another source, or no accessible supporting page.
The owned page intended to answer the question and its publication or revision history.
Referred visits, meaningful on-site actions, and business outcomes when those can be observed responsibly.
Keep three layers separate in reporting. Visibility observations describe what appeared. Quality judgments describe whether the answer and citation were useful and accurate. Business outcomes describe what people did. Combining all three into one number hides the very information you need for prioritization.
Require a change log beside the baseline. It should connect recommendations to approved work, affected URLs or templates, release dates, validation results, and subsequent observations. Without that record, the agency can report movement but cannot show which intervention may have contributed to it.
The scope should also resolve ownership before work starts:
Who approves the question set and can add or retire monitored questions.
Who controls analytics, monitoring, CMS, schema, repository, and reporting access.
Who supplies subject-matter evidence and approves sensitive claims.
Who writes, edits, develops, validates, publishes, and maintains each type of change.
Who owns the resulting briefs, dashboards, configurations, structured data specifications, and historical captures.
How open recommendations and data are handed over if the engagement ends.
Retain administrative control of your own site, analytics, and core business data. Give the agency the access required for its role, but avoid making your ability to operate dependent on an account only the vendor controls. The same principle applies to prompt histories and reporting data: you should be able to inspect and export the evidence used to evaluate performance.
If uncertainty remains, use a bounded pilot to test the working relationship. Give it a defined audience, question set, group of pages, deliverables, implementation route, evidence method, and decision point. The purpose is to learn whether the agency can diagnose, communicate, ship, and measure within your environment. A short pilot should not be treated as proof that every market-level outcome will move.
Compare the cost of the full operating model, not only the agency fee. A proposal may exclude monitoring software, content production, development, design, public relations, or subject-matter review. Make those dependencies visible so a cheaper retainer does not become the more expensive program after implementation begins.
Key takeaways before you sign
Define AI visibility as a set of observable outcomes: accurate representation, relevant inclusion, useful citations, qualified action, and business impact.
Give every agency the same priority audiences, questions, pages, constraints, baseline, and implementation boundaries.
Look for a connected strategy spanning intent, content, entities, technical access, structured data, authority, distribution, and measurement.
Ask for raw evidence behind case narratives and visibility scores, including prompts, answers, citations, dates, changes, and limitations.
Reject guaranteed placements, schema-only plans, volume-first content programs, and dashboards presented as complete optimization.
Put owners, access, deliverables, acceptance criteria, change history, data control, handover, and excluded costs into the scope.
Your next move is straightforward: choose one important audience, one decision journey, a manageable set of questions, and the pages that should support the answers. Capture the baseline, send the same brief to each finalist, and require each team to show how it would move from diagnosis to an implemented, measurable change.
Select the agency whose reasoning remains clear when the evidence is incomplete. The right partner will make assumptions visible, define what it can and cannot control, and leave your organization with a stronger operating system for AI discovery rather than a collection of unexplained tactics.
