CrushPress.AI

Month: January 2026

  • Google Antitrust Data and Ad Remedies: What to Prepare

    Google Antitrust Data and Ad Remedies: What to Prepare

    If you manage paid search, organic visibility, or a search product, the dangerous mistake is to model Google’s antitrust remedies as one switch. Access to an index, access to interaction data, syndication of results, and syndication of ads create different opportunities, controls, and failure modes.

    Start with timing. Google sought to pause parts of the remedy while its appeal was pending, while the challenged search and ad syndication provisions could operate for five years. A remedy can appear in a judgment without being available in a partner product. Before changing a contract, budget, privacy policy, or technical integration, verify the operative order, effective date, and implementation terms with the relevant partner and legal counsel.

    The remedies split into four operational layers

    The phrase “data sharing” hides several systems that should not share one forecast. The court’s Section IV framework reaches index information, search-interaction data, core results, and ads. Each layer answers a different competitive problem and creates a different kind of exposure.

    Remedy layerWhat could be shared or syndicatedWhat it means operationally
    Web index dataURLs in Google’s index, a DocID-to-URL map, and metadata such as crawl frequencyA qualifying rival could reduce the work needed to discover and prioritize pages. This does not create a public index dashboard for every publisher or SEO.
    Search-interaction dataSearch logs used by Glue and RankEmbed, including detailed interaction informationA recipient would gain potentially valuable signals, but would also need controls for authorized use, privacy, retention, security, and downstream access.
    Core search syndicationGoogle’s core results and search features for qualifying competitors for five yearsA third-party surface could display Google-derived results without independently reproducing the same index and ranking stack.
    Ad syndicationGoogle search ads under court-constrained commercial terms, with query and pricing information involved in operating the relationshipA competitor could add monetization more quickly, while advertisers would face another distribution path whose traffic quality and controls must be evaluated.

    The first important distinction is sharing versus publishing. A requirement to serve qualified competitors is not a promise that advertisers, agencies, site owners, or the public will receive raw Google data. Unless your company satisfies the applicable qualification requirements and signs the necessary terms, assume you have no direct access.

    The second distinction is syndication versus source-code transfer. Google is not warning only about someone receiving auction software. Its position is that repeated observation at large scale could reveal targeting logic, relevance factors, and auction behavior. When you assess an integration, separate three things: data expressly delivered under contract, information visible during normal operation, and patterns a high-volume participant might infer.

    The third distinction is direct distribution versus a distribution chain. The judgment permits competitors to sub-syndicate Google ads to third parties. That makes the identity, incentives, and controls of downstream participants part of the product. A direct partner’s security review is not enough if several other businesses can receive the inventory or related data.

    Do not translate a requirement for terms no less favorable than existing agreements into one public price. Google’s current arrangements are customized around traffic quality and technical configuration. Applying comparable economics to materially different partners could produce unpredictable volume or poor pricing. Evaluate the effective cost and quality of each route, not the legal phrase in isolation.

    The alleged harms are testable mechanisms, not settled outcomes

    Two transparent search and advertising pipelines are examined side by side with sensors, ranking modules, distribution junctions, and privacy filters in a digital laboratory.

    Google is the party seeking to pause these obligations, so its claims should be treated as arguments from an interested participant. They still identify concrete failure mechanisms worth testing. The disciplined response is to build controls around those mechanisms without assuming that every predicted harm will occur.

    Index access could change discovery and spam incentives

    A complete URL map could let a competitor avoid much of the work involved in discovering the web. Crawl-frequency metadata could reveal which areas Google revisits most often. Google also argues that exposing spam-related scores or signals could help bad actors learn what its systems detect and then adjust their tactics.

    Those mechanisms do not prove that an authorized recipient will publish more spam, and they do not mean SEOs will receive a usable ranking score. Do not rewrite content around rumored fields or secondhand interpretations of a dataset. Establish a pre-change baseline instead: indexed landing pages, organic impressions, crawl activity, referring surfaces, conversions, and obvious spam anomalies. Match the comparison period to your site’s publishing cycle and seasonality.

    If visibility changes later, identify the result’s provenance before diagnosing a ranking change. A competitor may have crawled the URL independently, received it through syndication, or generated an answer from another system. Those paths can produce a similar screen for the user while requiring completely different corrective actions from you.

    Ad fraud risk rises when the traffic chain becomes opaque

    Large-scale ad delivery can expose more behavioral patterns than a small integration. Google argues that repeated queries could help outsiders infer aspects of targeting, relevance, and auction operation. Sub-syndication adds another problem: the company with the direct agreement may have less incentive or ability to police every downstream placement.

    One abuse pattern described by Google involved adding the names of wealthier countries to queries while routing lower-cost international traffic to ads. The resulting click-fraud losses were allegedly measured in tens of millions within a couple of months. That example does not establish that new syndicators will behave the same way. It does show why query integrity, geography, placement identity, and conversion quality belong in the same fraud review.

    Do not label every conversion decline as fraud. We would require at least two independent anomalies before escalating: a click-volume change outside the campaign’s normal range, a mismatch between click and conversion geography, systematic additions to query text, an unexplained shift in partner volume, or a sharp deterioration in post-click outcomes. Preserve the raw evidence, isolate the suspect route, and use the contractual dispute process before making a broad account change.

    Nominally favorable pricing can still produce weak economics

    A partner can receive apparently favorable terms and still send traffic that performs poorly. Price per click, revenue share, and conversion rate describe different parts of the transaction. Unpredictable query volume can also turn an acceptable test into an uncontrolled budget event.

    Compare syndicated routes using business outcomes after conversion lag, invalid-traffic adjustments, refunds, and downstream fees. Keep each new route in its own reporting line. If it is mixed into an established campaign, aggregate performance can hide a low-quality partner until substantial spend has already moved.

    Access to interaction data does not create permission to reuse it

    The search logs at issue include detailed user interactions. Google says compelled sharing could create privacy, misuse, and leakage risks even when contracts restrict recipients. Detailed data is not necessarily directly identifiable, but that distinction cannot be assumed without a data dictionary and a review of the actual fields.

    Before connecting any newly available search dataset to analytics, a CRM, an advertising profile, or an AI training pipeline, document its permitted purpose, level of aggregation, retention period, deletion process, security controls, audit rights, and downstream-transfer rules. New access is not user consent. If the legal basis or contractual permission is unclear, keep the data outside production systems until privacy and legal reviewers approve the intended use.

    Build a readiness plan without betting on the appeal

    Hands organize blank contract materials, API modules, data controls, a sandbox model, monitoring lights, and contingency paths on a conference table.

    You do not need to predict the final legal outcome to prepare. Most of the useful work is reversible: clarify ownership, record the baseline, define acceptance gates, and make new traffic or data separable from existing operations.

    1. Create a remedy register. For each obligation, record its legal status, effective date, duration, eligible recipient, covered data or inventory, downstream rights, internal owner, and the evidence supporting each entry. Use separate labels for ordered, operative, and commercially available; they are not synonyms.
    2. Map your current chain. For ads, connect each campaign to its network, direct partner, known sub-partners, placement or referrer data, billing path, and conversion pipeline. For organic and AI visibility, connect each URL to the crawler, index, display surface, referral, citation, and measured outcome. Mark every unknown rather than filling it with an assumption.
    3. Capture a baseline before exposure changes. Preserve traffic quality, conversion lag, click and conversion geography, query themes where available, invalid-traffic adjustments, indexed URLs, crawl patterns, organic conversions, and referring surfaces. Use enough history to represent your normal seasonality.
    4. Set a contractual gate. Require clear rules for data purpose, retention, deletion, audits, incident notice, sub-syndication, query transformations, invalid traffic, refunds, and the ability to pause distribution. A promise of comparable terms is not a substitute for these controls.
    5. Isolate every new test. Give new syndicated inventory a separate campaign or reporting segment, distinct tracking, and a budget limited to what the business can afford to lose during validation. Do not blend it into a core acquisition channel until traffic quality and reconciliation have been demonstrated.
    6. Plan around states, not dates. Model a continued stay with no operational access, a constrained implementation with direct qualified partners, and a broader implementation that includes downstream syndication. Attach a measurable trigger to each action, such as an operative order, published qualification rules, a signed agreement, or a technically verified feed.
    7. Prepare an incident path. Name the person who can pause spend or disconnect data, identify which logs must be preserved, define who reviews suspected fraud or privacy exposure, and document the notification and refund process. Rehearse that path before a high-volume integration starts.

    Questions paid media teams should ask before buying inventory

    A new inventory offer should not move into campaign setup until the provider can answer these questions in writing:

    • Is the provider a direct Google syndication partner, a sub-syndicator, or another downstream participant?
    • Which domains, apps, result pages, and additional partners can display the ads?
    • Can the provider report traffic, costs, invalid-click adjustments, and conversions at the same level at which you can pause or dispute traffic?
    • Can query text be modified, expanded, or combined with geographic terms before the ad request is made?
    • How are click geography, user location, and conversion geography validated and reconciled?
    • How do traffic quality and technical configuration affect pricing, and what happens if volume differs materially from the forecast?
    • Which party investigates fraud, how quickly can delivery be stopped, and when are credits or refunds available?

    If a provider cannot identify the inventory chain or explain its dispute and refund rules, the safe decision is not to spend through that route yet. A small isolated test is appropriate only when the loss is bounded and the business can measure the result independently.

    What SEO, AEO, and GEO teams should measure differently

    Search syndication makes provenance more important than surface appearance. A URL displayed by a competitor may have arrived from that competitor’s crawler or through Google-derived results. An AI answer may then cite, summarize, or ignore that result through another decision process.

    • Classify visibility as independently crawled, independently indexed, syndicated, or cited by a generative system. Do not collapse those states into one rank-tracking field.
    • Track display visibility and referral traffic separately. A syndicated result could appear without a distinctive crawl from the service that displays it, while a crawl does not prove the URL was shown to users.
    • Do not assume inclusion in Google’s index guarantees inclusion in a competing result set or citation in an AI answer. Discovery, indexing, ranking, syndication, and generative citation remain separate decisions.
    • When a snippet or answer is wrong, capture the query, URL, surface, wording, and time. Determine whether the error came from the upstream result, a downstream transformation, or the generative layer before changing the page.
    • Treat any new index map or interaction dataset as governed data. Verify provenance, contractual rights, freshness, permitted use, and deletion requirements before incorporating it into an SEO tool or model.
    • Keep canonical URLs, crawl directives, structured data, and core entity facts consistent. These controls will not determine every downstream use, but they give independent and syndicated systems a stable representation to work from.

    Do not apply noindex, change canonical targets, or block crawlers merely in response to a rumored implementation. Those changes can remove legitimate visibility. Confirm the actual behavior first, then use a reversible test on a limited set of non-critical URLs if a platform-specific control needs validation.

    Key takeaways

    • Google’s antitrust remedies involve four distinct layers: web index data, search-interaction data, core result syndication, and ad syndication.
    • Qualified access is not public access, and syndication is not the same as receiving Google’s source code.
    • Google’s warnings about spam, privacy, fraud, reverse engineering, and pricing are contested claims, but each describes a mechanism you can monitor and control.
    • Advertisers should require visibility into the complete distribution chain, isolate new inventory, and reconcile clicks with geography and business outcomes.
    • SEO, AEO, and GEO teams should distinguish independent crawling, indexing, syndication, and generative citation before diagnosing a visibility change.
    • No budget, contract, data-use, or technical decision should rely on the remedy headline alone; verify the operative order and implementation terms.

    Your next move should be a remedy register and a clean performance baseline, not a speculative budget reallocation or content rewrite. When an operative requirement or real partner offer appears, insist that the data and traffic chain be put on paper. That gives you evidence for a fast decision without making the business depend on the outcome of an appeal.

    References

  • Google Demand Gen Commerce Updates: A Practical Playbook

    Google Demand Gen Commerce Updates: A Practical Playbook

    You may be looking at Demand Gen because paid social is getting harder to scale, or because YouTube creates attention that your conversion reports struggle to explain. Google’s commerce updates give you three new levers, but each solves a different problem.

    The practical question isn’t whether to adopt every new feature. It is whether shoppable connected TV, dynamic travel offers, or branded-search attribution closes a specific gap in your customer journey. Start there, and you can test the updates without turning a product announcement into an open-ended budget request.

    What changed, and what each update actually does

    The three additions sit under the same Demand Gen umbrella, but they are not interchangeable:

    The first two features change what a prospective customer can see or do. The third adds an attribution signal. That distinction matters: a new measurement report does not improve the buying experience, and a shoppable ad does not by itself prove that the resulting sales were incremental.

    Match the feature to the constraint in your funnel

    Three connected scenes show television shopping, adaptive travel offers, and a search-to-purchase path overcoming different journey obstacles.

    Use shoppable CTV when the missing link is product action

    Shoppable CTV is most relevant when viewers understand your product from video but have no natural next step from the television screen. The testable idea is simple: can adding a product interaction to that viewing experience produce more conversions without weakening return on investment?

    Do not begin by moving a large video budget. Begin with a product set that makes the test interpretable. Favor products that are easy to recognize visually, have a clear use case, and are supported by dependable price and availability data. The item presented in the ad should also be easy to find at the destination. A viewer who meets a different product, price, or offer after acting on the ad has not experienced a media failure; they have experienced a broken handoff.

    • Make the product and its main benefit understandable at television viewing distance. Do not rely on dense copy or small interface details to explain the offer.
    • Check the full path from the video impression to the product action and final destination. Look for changes in item identity, price, availability, or promotional language.
    • Judge the test primarily on conversions, conversion value, CPA, or ROI, according to your business model. Video engagement can diagnose creative response, but it should not replace the commercial outcome.
    • Document what adding CTV is expected to change. If the hypothesis is merely that the campaign will reach more people, the test is too vague to justify a performance conclusion.

    Use Travel Feeds when changing offers make creative stale

    Travel Feeds address a different source of friction. Hotel pricing and availability can change faster than a team can rebuild conventional video assets. Connecting Hotel Center allows those offer details, along with property ratings, to populate dynamic video ads.

    The feed becomes part of the advertising experience, so feed quality is campaign quality. Before increasing spend, sample the properties and offers being promoted. Compare the price, rating, and availability presented in the ad journey with what a traveler encounters when moving toward a booking. Decide how your team will identify unavailable properties, inconsistent prices, and destinations that no longer match the promoted offer.

    • Audit Hotel Center data before evaluating the creative. Incorrect or incomplete offer data can make capable media look ineffective.
    • Review a representative mix of properties rather than checking only the most visible or highest-volume listing.
    • Assign ownership for feed corrections. A media buyer who can identify a mismatch but cannot route it to the person responsible for hotel data will repeatedly diagnose the same problem.
    • Keep the booking outcome as the primary metric. Dynamic assembly reduces creative and offer friction; it does not remove the need to evaluate booking quality and campaign economics.

    Use Attributed Branded Searches when last-click reports hide influence

    Demand Gen can affect what people search for after seeing an ad, even when the eventual search or conversion does not look like a direct response to the original impression. Attributed Branded Searches are designed to expose that brand-search activity across Google and YouTube.

    That makes the metric useful, but not equivalent to revenue. A rise in attributed brand searches can indicate that the campaign created interest. It cannot, on its own, tell you whether those searches produced profitable, incremental customers. Read it beside conversions, conversion value, CPA, ROI, and any customer-quality measure your business already trusts.

    Because a Google representative must activate the feature, treat access as a pre-launch dependency rather than an item to chase after the campaign ends. Ask the representative to confirm eligibility, the activation date, the metric definition, the reporting location, the applicable attribution window, and any limitations that could affect interpretation. Record those answers with the campaign brief so nobody later compares two reports built on different rules.

    Build the measurement plan before you move budget

    A desk with connected devices, interaction tokens, measurement checkpoints, and budget tokens waiting behind a transparent gate.

    The updates make Demand Gen more measurable, but more metrics do not automatically create a clean test. You still need a decision framework that separates commercial outcomes from diagnostic signals.

    1. Write one falsifiable hypothesis. For example: adding TV screens will increase conversions while maintaining ROI, or feed-driven hotel video will increase bookings without exceeding the campaign’s CPA constraint. Avoid a bundle such as improving awareness, engagement, sales, and efficiency at once.
    2. Select one primary outcome and one guardrail. The outcome might be purchases, bookings, conversion value, or another completed business action. The guardrail might be CPA or ROI. Branded search and video engagement should remain supporting signals unless they are genuinely the business objective.
    3. Lock the comparison rules. Use consistent conversion actions, value rules, attribution settings, and reporting periods when comparing Demand Gen with an existing campaign or channel. If those controls cannot be aligned, label the comparison as directional rather than causal.
    4. Record operational diagnostics. For commerce, inspect product continuity and availability. For travel, inspect Hotel Center data and the offer-to-booking path. For brand measurement, confirm that Attributed Branded Searches were active during the period being evaluated.
    5. Define the next decision before results arrive. State what would justify a limited scale-up, what would trigger a feed or landing-path repair, and what would cause the test to stop. You do not need to invent universal thresholds; use the economics your account must already meet.

    Once the campaign is running, interpret combinations of signals instead of celebrating one favorable number:

    Signal patternWhat it may meanWhat to do next
    Conversions rise while ROI holds or improvesThe commerce path may be creating useful additional demand at acceptable efficiency.Verify order or booking quality, repeat the result, and scale gradually.
    Attributed brand searches rise but conversions remain flatThe campaign may be generating interest that the offer, destination, or conversion path is not capturing.Do not declare a revenue win. Inspect search destinations, landing experiences, offer consistency, and conversion tracking.
    Video engagement improves but commercial outcomes weakenThe creative may attract attention without qualifying the right buyer or making the next action clear.Rework the product promise and handoff before adding budget.
    Travel ads show inconsistent offers or weak deliveryHotel Center data or campaign configuration may be obscuring the media result.Resolve feed accuracy and eligibility questions before concluding that the channel failed.

    Use Google’s performance figures as test inputs, not forecasts

    Google reports that Demand Gen campaigns featuring TV screens generated 7% more conversions at the same ROI. LG Electronics also reported a 24% higher conversion rate than paid social while reaching high-value customers at a 91% lower CPA. Those figures make a reasonable case for testing the channel, but they are vendor-reported results rather than a guaranteed outcome for your account.

    The LG comparison is especially easy to misuse. Without matching details for audience, geography, campaign period, conversion action, creative, and attribution model, a 91% CPA difference cannot become your forecast. Even the phrase “paid social” can conceal campaigns with different objectives and levels of maturity.

    • Use the 7% figure to support the question, “Is a controlled CTV test worth running?” Do not insert it automatically into a revenue plan.
    • Use the LG result as evidence that Demand Gen can compete with paid social under some conditions, not that it will always outperform it.
    • Put the comparator beside every benchmark in your internal presentation. A percentage without its baseline, campaign objective, and measurement rules is not an operating target.
    • Let your account’s conversion quality and unit economics decide whether to scale. A lower reported CPA is not valuable if it produces lower-value customers or bookings that do not hold.

    Key takeaways

    • Shoppable CTV is a commerce-path update: use it when YouTube viewing creates product interest but the television experience lacks a clear response mechanism.
    • Travel Feeds are an offer-assembly update: audit Hotel Center data because price, rating, and availability accuracy directly affect what the traveler sees.
    • Attributed Branded Searches are a measurement update: activate the feature through a Google representative before launch and interpret it beside commercial outcomes.
    • Google’s 7% conversion figure and LG Electronics’ paid-social comparison can justify a test, but neither should be treated as an account forecast.
    • The strongest rollout ties one feature to one constraint, one primary outcome, one efficiency guardrail, and a written scale-or-stop decision.

    Before your next campaign-planning meeting, write a one-sentence hypothesis and the two numbers that will decide whether you scale or stop. Then introduce only the Demand Gen feature capable of moving that hypothesis. That keeps the update focused on a business decision instead of letting it become a reason to spend first and explain the result later.

    References

  • Google Campaign Mix Experiments: A Practical Testing Guide

    Google Campaign Mix Experiments: A Practical Testing Guide

    You need to decide whether the next dollar belongs in Search, Performance Max, Shopping, Demand Gen, Video, or App. Looking at campaign-level ROAS alone will not answer that question. Changing one part of the account can alter what the other campaigns capture, so the decision has to be evaluated at the portfolio level.

    Google Campaign Mix Experiments gives you a way to compare complete campaign combinations rather than treating every campaign as an isolated unit. Used carefully, the beta can tell you whether a different mix produces a better business result. Used casually, it can produce a confident-looking answer to a badly framed question.

    Start with the spending decision, not the campaign list

    A useful mix experiment begins with a decision you could make after seeing the result. “Test Performance Max” is not a decision. “Determine whether moving budget from the current Search and Shopping mix into a Search and Performance Max mix improves conversion value at the same total budget” is.

    Write your hypothesis in this form:

    If we change [one portfolio variable] while holding [the important controls] constant, we expect [primary metric] to improve enough to justify [the account change].

    Campaign mix experiment hypothesis template

    The phrase “enough to justify” matters. A measurable difference is not automatically a commercially important difference. Before launch, define the smallest improvement that would cover the operational cost, additional complexity, or risk created by the proposed mix. That threshold is your materiality rule.

    Choose one primary metric that matches the decision:

    • ROAS fits a revenue-efficiency decision when your conversion values are dependable.
    • CPA fits a cost-efficiency decision when the counted conversions have reasonably comparable business value.
    • Conversions fits a volume decision when generating more qualified actions is the main objective.
    • Conversion value fits a growth decision when total value matters more than efficiency alone.

    Google supports reporting around ROAS, CPA, conversions, and conversion value. You can inspect all of them, but naming one primary metric in advance prevents a common analytical mistake: searching the results for whichever metric makes the preferred arm look best.

    Key takeaways

    • Frame the experiment as a portfolio-level business decision, not a request to identify the best individual campaign.
    • Change one meaningful variable between arms and keep the other important conditions aligned.
    • Keep total budgets comparable unless total spend is explicitly the variable under test.
    • Avoid shared budgets and material account changes while the experiment is running.
    • Preselect the primary metric, confidence interval, materiality rule, and minimum duration before looking at outcomes.
    • Plan for at least six to eight weeks, but do not assume that duration alone guarantees a decisive result.

    Build arms that isolate one portfolio variable

    Two balanced experiment trays contain matching campaign modules with one controlled difference between them.

    An experiment arm is one complete version of the campaign portfolio. The beta supports up to five arms, and the same campaign can appear in more than one arm. That flexibility is valuable because you can preserve the common parts of the account while changing only the element you need to evaluate.

    More arms are not inherently better. Every additional arm creates another comparison and divides the available traffic. Use the fewest arms that can answer the decision. For many questions, a current-state control and one alternative are enough.

    The framework covers Search, Performance Max, Shopping, Demand Gen, Video, and App campaigns. Hotels campaigns are excluded. That breadth lets you test a cross-channel plan, but it does not remove the need for a clean experimental contrast.

    DecisionWhat changes between armsWhat should stay aligned
    Channel budget allocationThe distribution of budget among campaign typesTotal portfolio budget, measurement, and other material settings
    Consolidation versus fragmentationThe number or structure of campaignsTotal budget, business objective, and the intended audience or inventory scope
    Bidding strategyThe bidding approach being evaluatedCampaign mix, budget treatment, targeting, and measurement
    Targeting optionThe selected targeting treatmentBudgets, bidding, creative treatment, and the rest of the portfolio
    Feature adoptionThe feature is used in one arm and not the otherEverything not required to enable that feature

    Suppose you change campaign structure, bidding, targeting, and budget distribution in the same arm. A winning result tells you that the package performed differently, but not which change caused it. You also cannot tell whether one helpful change compensated for another harmful one. That may be acceptable when the package itself is the business decision, but it is a poor design when you need reusable knowledge.

    Budget handling deserves particular care. If you want to test the mix, keep the total planned budget equal and change its internal allocation. If you want to test a higher total spend level, make total spend the sole intended difference. Do not quietly give the preferred arm both a different campaign combination and more money; the result will not distinguish the effect of mix from the effect of spend.

    Traffic can be allocated among arms with splits starting at 1%, and reporting is adjusted to the smallest split so the comparison remains fair. Treat 1% as a configuration boundary, not a recommendation. A very small arm may receive too little information to resolve a commercially modest difference, especially when conversions are sparse. The better question is whether every arm can accumulate enough relevant outcomes during the planned window.

    Protect the comparison for the full test window

    A strong setup can still fail after launch. New promotions, tracking changes, creative replacements, altered conversion values, revised targets, and unplanned budget moves can all change the conditions under which the arms are being compared. If those interventions affect the arms differently, you no longer have the experiment you designed.

    Plan to run a campaign mix experiment for at least six to eight weeks. This is a minimum operating window, not a promise of statistical certainty. An account with limited conversion volume or a small true difference may still produce a wide range of plausible outcomes after that period.

    Before launch, complete a short preflight:

    1. Validate measurement. Confirm that the conversions and values feeding the primary metric represent the business outcome you intend to optimize. Fix tracking before the experiment, not during it.
    2. Check arm symmetry. Verify that the total budgets and non-tested settings are aligned wherever the hypothesis requires them to be.
    3. Remove shared-budget dependencies. Google advises avoiding shared budgets during these experiments. A shared budget can redistribute spend across campaigns and obscure the portfolio treatment you meant to test.
    4. List prohibited changes. Record which budgets, bidding settings, targets, campaign structures, features, and measurement rules must remain untouched.
    5. Record unavoidable events. If a promotion, inventory interruption, landing-page failure, or other business event occurs, document when it began, which campaigns it affected, and whether it compromised comparability.
    6. Set review dates. Monitor for broken delivery or measurement, but do not repeatedly judge the winner from early fluctuations.
    7. Define stop conditions. Separate genuine operational failures, such as broken tracking, from ordinary underperformance. A disappointing early result is not by itself evidence that the experiment is invalid.

    The instruction to avoid significant changes does not mean ignoring a serious problem. If tracking fails or an arm cannot deliver as designed, protect the business and correct the problem. Then decide whether the comparison remains interpretable or needs to be restarted. The mistake is pretending that a materially altered test still answers the original hypothesis.

    Keep a change log even when no restart is needed. Record the date, affected arms, reason, and expected impact of every intervention. When the result arrives several weeks later, that log will help you distinguish a real portfolio effect from a mid-test account event.

    Read the portfolio result before diagnosing campaigns

    A large magnifying lens frames an interconnected campaign system while smaller lenses point toward its individual components.

    The Experiment summary should answer the question you wrote before launch: did one complete mix improve the primary business metric enough to change your decision? Campaign-level reporting then helps you understand where the portfolio difference appeared. Reversing that order invites cherry-picking.

    One campaign can improve while the portfolio remains flat or declines. Another campaign can look weaker while the total arm improves because the mix is capturing demand more efficiently as a whole. Campaign-level movement is diagnostic evidence; it is not a substitute for the arm-level result.

    Google lets you view experiment reporting with 95%, 80%, or 70% confidence intervals. Choose the interval before reading the outcome. A more conservative interval demands stronger evidence and will generally produce a wider range. A lower interval accepts more uncertainty. Switching among them until a preferred arm appears convincing turns an analytical setting into a result-shopping tool.

    Read the result through three separate lenses:

    • Direction: Which arm currently appears better on the primary metric?
    • Uncertainty: Does the interval leave room for a materially different conclusion, including a meaningful loss?
    • Materiality: Is the likely difference large enough to justify the budget move, structural complexity, or operational burden?

    Do not collapse those questions into a single winner label. A positive point estimate with a broad interval can still be inconclusive. A statistically clear but commercially tiny improvement may not justify rebuilding the account. An interval that includes little or no difference does not prove that the arms are identical; it means this run did not resolve the difference precisely enough under the selected standard.

    Use the metric in the context of its inputs. ROAS and conversion value depend on the quality of the values assigned to conversions. CPA can look healthier when the mix generates cheaper but less valuable actions. Conversion volume can increase while efficiency deteriorates. These are not reasons to abandon a primary metric. They are reasons to make sure it represents the decision before the test begins and to use the other metrics as context rather than alternate finish lines.

    Turn the finding into a controlled account decision

    The result should lead to one of three actions: adopt the alternative, retain the current mix, or collect more evidence. Write the rule before launch so the post-test discussion is about evidence and tradeoffs rather than stakeholder preference.

    • Adopt: The alternative improves the preselected primary metric, the uncertainty is acceptable under the chosen interval, and the effect exceeds your materiality threshold.
    • Retain: The alternative is worse, creates an unacceptable downside, or fails to produce enough benefit to cover its complexity and cost.
    • Collect more evidence: The plausible range includes outcomes that would lead to different business decisions. Treat this as unresolved, not as a tie and not as permission to select the preferred narrative.

    If you adopt a winning mix, implement the treatment you actually tested. Adding new targeting, changing bids, moving the total budget, and restructuring campaigns during rollout creates a new package whose performance was never evaluated. Make the validated change first, observe it under normal account conditions, and treat later improvements as separate decisions.

    If the result is inconclusive, do not automatically rerun the same design. First identify why the answer remained unclear. The true difference may be too small to matter, an arm may have received too little useful traffic, the primary outcome may be too sparse, or account changes may have weakened the comparison. Rerun only when you can improve the design or when resolving the decision is worth another full testing window.

    A compact decision record makes the learning reusable. Save these fields with the result:

    • The business decision and one-sentence hypothesis
    • The campaigns and settings included in every arm
    • The single intended difference between arms
    • Total budget treatment and traffic allocation
    • The primary metric and materiality threshold
    • The preselected confidence interval
    • The planned and actual run dates
    • All material account or business events during the test
    • The arm-level result and relevant campaign-level diagnosis
    • The final decision, owner, and implementation boundary

    Your best first use of Campaign Mix Experiments is the largest unresolved allocation decision that can still be isolated cleanly. Write the hypothesis, name the metric, and sketch the control and alternative on one page. If you cannot explain exactly what changes and what stays fixed, the experiment is not ready to launch.

    References

  • Personal Intelligence in Google AI Mode: An SEO Playbook

    Personal Intelligence in Google AI Mode: An SEO Playbook

    If your AI Mode reporting assumes that every tester should receive the same answer for the same prompt, Personal Intelligence breaks that assumption. Once someone connects personal Google content, a short query can be interpreted through preferences, plans, relationships, places, and interests that were never typed into the search box.

    That does not make AI search visibility immeasurable. It changes what you have to measure. The useful unit is no longer just a query and a URL; it is a query, an account state, a personal context, an answer, and any citations shown with it.

    Key takeaways for SEO and GEO teams

    • Personal Intelligence lets eligible users connect Gmail and Google Photos to AI Mode, with responses potentially drawing on a wider Google context that includes YouTube history.
    • The announced Labs experiment was opt-in and limited to U.S. personal accounts with AI Pro or Ultra access. Workspace business, enterprise, and education accounts were excluded under the launch conditions.
    • Two people can enter the same prompt but present different underlying needs. A single screenshot or rank position therefore cannot represent universal AI Mode visibility.
    • Content should make its suitability explicit: who it serves, which situation it addresses, what constraints apply, and which facts support the recommendation.
    • JSON-LD can clarify entities and relationships already visible on a page, but it should not be treated as a switch that forces personalization or earns an AI Mode citation.

    Confirm access before diagnosing an AI Mode problem

    The announced rollout placed Personal Intelligence inside a Labs experiment. Its launch eligibility was narrow: AI Pro and Ultra subscribers using personal accounts in the United States could opt in, while Workspace business, enterprise, and education users could not. Treat those as experiment launch conditions, not permanent availability rules.

    Availability was being added to eligible subscriber accounts as the rollout progressed, but the personalization feature itself required consent. If the option was available, the manual setup path was:

    1. Open Google Search and select the profile control.
    2. Choose Search personalization.
    3. Open Connected Content Apps.
    4. Connect Workspace and Google Photos.

    The Workspace connector label should not be confused with eligibility for a managed Workspace account. Under the stated experiment rules, the account still had to be personal. The connected experience could use context spanning Gmail, Google Photos, and YouTube history.

    Before treating a missing or inconsistent result as an SEO issue, record the test conditions: personal or managed account, subscription tier, country, Labs access, opt-in state, connected apps, and relevant history settings. If one of those conditions differs, you are not reproducing the same search environment.

    Do not ask employees or clients to expose private email or photo libraries merely to make a test repeatable. Use voluntary participants, collect only the observations needed for the test, and redact screenshots before they enter tickets, presentations, or shared reports. A personalized response can reveal contextual details even when the original prompt looks harmless.

    Measure citation variance, not one universal ranking

    Three researchers test the same blank query on separate computers that show different answer blocks and source tiles.

    Traditional rank tracking works by holding the query and environment as steady as possible. Personal Intelligence introduces an account-level input that an anonymous crawler cannot reproduce. The practical question changes from “Where did this URL rank?” to “Under which observable contexts did this source become useful enough to appear?”

    This matters most for prompts whose answer depends on taste, history, relationships, or current circumstances. The feature’s example uses include family getaway planning, an anniversary scavenger hunt, a child’s bedroom theme, fashion preferences, book recommendations, and other identity-shaped choices. Those are context-sensitive tasks by design, so variation is not automatically a tracking error.

    Test stateWhat it tells youWhat to record
    Personal Intelligence offProvides a non-connected baseline for the exact prompt.Prompt, account eligibility, answer, cited domains, and cited URLs.
    Personal Intelligence on with connected contentShows how the answer changes when personal context is available.Connected-app state, answer differences, recommendations, and citations.
    Personal Intelligence on for another consenting userReveals whether a different context produces a different source set.Only broad, non-sensitive context labels plus the resulting citations.
    Managed Workspace accountChecks whether the test is outside the announced launch eligibility.Account type and whether the feature is present; do not treat absence as a content failure.

    Keep one set of context-sensitive prompts and one control set with little need for personal interpretation. If every result changes, your environment may be unstable. If variation concentrates in planning and recommendation tasks, the pattern is more consistent with personalization doing useful work.

    For each valid test session, log:

    • The exact prompt and any follow-up prompt.
    • Whether Personal Intelligence was available and enabled.
    • Which permitted content connections were active.
    • A short description of the answer’s framing, without copying private details.
    • Every cited domain and URL, including where the citation supported the response.
    • Whether your brand was named without a link, cited with a link, or absent.
    • Whether the cited page actually matched the recommendation or merely supplied a supporting fact.

    Report citation presence as a distribution across valid observations, with the numerator and denominator visible. Do not turn one personalized session into a claim that a site “ranks first in AI Mode.” The accounts are not controlled duplicates, and their histories can differ in ways you cannot inspect or isolate. This is scenario testing, not a clean causal experiment.

    Make public content usable under more personal contexts

    You cannot optimize for the contents of an unknown person’s inbox or photo library. You can make a public page precise enough for an AI system to recognize when it fits a need revealed by that private context. The distinction keeps your strategy grounded: optimize the public evidence and applicability of the page, not the private profile.

    State suitability in language that can be resolved

    Generic superlatives provide little help when an answer must adapt to a specific person. Replace broad claims such as “best getaway for everyone” with explicit conditions: departure area, trip length, transport requirements, activity level, indoor or outdoor emphasis, intended audience, and meaningful limitations. Use only attributes you can substantiate.

    Apply the same discipline outside travel. A book recommendation page can identify themes, reading mood, subject matter, format, and who may not enjoy the selection. A decorating page can separate room size, practical constraints, style, and maintenance needs. The goal is not to create a page for every imagined persona. It is to expose the decision variables already necessary for a good recommendation.

    Build answer blocks around real decisions

    Place the direct answer near the question it resolves. A recommendation should name the option, explain why it fits, state the conditions under which it stops fitting, and link to the evidence or details needed to act. Descriptive headings, concise summaries, comparison criteria, and clearly labeled caveats make the page easier to interpret without stripping away useful depth.

    Separate stable facts from editorial judgment. Opening hours, eligibility, dimensions, compatibility, and included features are different kinds of claims from “ideal for a relaxed weekend” or “better for adventurous readers.” When those claim types blur together, neither a person nor an AI system can easily determine what is verifiable and what is a recommendation.

    Use JSON-LD to confirm the visible page

    Choose the most specific applicable Schema.org types and properties for the entities actually described on the page. Keep names, URLs, authorship, offers, dates, and other marked-up attributes consistent with the visible content. If an important condition matters to the recommendation, explain it in the page copy instead of hiding it in structured data.

    Do not invent audience traits, reviews, ratings, availability, or relationships because they might appear useful to an AI system. Structured data is a machine-readable representation of claims you already publish; it is not a place to manufacture relevance. It can reduce ambiguity, but it does not guarantee inclusion in an AI Mode answer or citation set.

    Strengthen the citation target, not just the topic match

    A page can match a topic yet remain a poor citation target. Make the responsible organization or author identifiable. Show when material was published or materially updated where that timing matters. Define the scope of the recommendation, support consequential claims, and maintain a stable canonical URL. If the useful evidence sits behind an unclear interface or is scattered across unrelated pages, consolidate the answer or create deliberate internal links between its parts.

    Brand consistency matters here as an interpretation problem, not a repetition exercise. Use the same organization, product, location, and author names across visible copy, metadata, structured data, and linked profile pages. Do not solve ambiguity by stuffing variants into every paragraph.

    Run a practical Personal Intelligence visibility cycle

    Five connected workstations form a loop using objects for access checks, context testing, citation review, content editing, and answer comparison.

    A useful operating cycle starts with one decision area where personal context could materially change the answer. Work through it in this order:

    1. Map the decision variables. Identify what would make one recommendation suitable and another unsuitable, such as location, constraints, preferences, timing, compatibility, or intended user.
    2. Create paired prompts. Use the same core request with Personal Intelligence off and on, then include a control prompt that should require little personal interpretation.
    3. Identify your eligible pages before testing. Write down which pages genuinely answer each scenario and why. This prevents you from declaring every absent citation a platform failure.
    4. Test with consenting users who meet the relevant access conditions. Record account and connection states without collecting their underlying messages, images, or sensitive history.
    5. Classify the outcome. Distinguish a direct citation, a supporting citation, an unlinked brand mention, a competitor citation, and no relevant citation.
    6. Inspect the content gap. Check whether the cited page was clearer about suitability, constraints, evidence, entities, or the action a reader should take.
    7. Improve the public page. Add missing decision criteria, clarify unsupported ambiguity, align structured data with visible claims, and strengthen internal paths to the best answer.
    8. Repeat under documented conditions. Keep experiment availability and account state attached to the result so later reports do not compare incompatible environments.

    Avoid three shortcuts. Do not manufacture fake email or photo histories to chase a preferred result. Do not use a personalized screenshot as universal ranking proof. Do not create thin pages for guessed private traits. Each shortcut produces noisy evidence and encourages content that is less useful to the real person making the decision.

    Start with the content cluster where your recommendations depend most on context. Establish the non-connected baseline, run opted-in tests with appropriate consent, and log citation variance alongside the conditions that produced it. The teams that preserve this context will be able to improve their content; the teams that keep reporting a single rank will mostly document contradictions.

    References

  • How to Measure SEO Performance Amid AI Search Volatility

    How to Measure SEO Performance Amid AI Search Volatility

    Your organic click line has stopped moving, AI answers keep changing, and someone wants a verdict: Is SEO failing, or is measurement behind the market? A single traffic total cannot answer that. It can stay flat while high-intent pages improve, awareness pages lose clicks, brand mentions spread, or AI systems represent the business inconsistently.

    You need a performance model that separates demand, discovery, answer representation, authority, and business outcomes. That gives you a defensible explanation for what is happening and a safer basis for deciding what to change.

    Treat volatility as a diagnostic input, not a strategy brief

    The language surrounding AI search moves faster than most operating strategies should. In 2025, 43% of a group of visible SEO leaders still used SEO in their LinkedIn headlines, compared with 21% using AI and 3% using GEO. Yet 59% mentioned GEO in their posts and 63% mentioned AIO. Public enthusiasm was moving faster than professional positioning.

    Those figures came from 2,025 LinkedIn posts by 75 SEO voices, with sentiment scored using VADER. That makes them useful evidence about industry discourse, not a representative survey of adoption or proof that any particular optimization method works. The distinction matters. A new label can spread without creating a new technical foundation.

    Separate three kinds of volatility before you interpret a dashboard:

    • Narrative volatility is a change in what practitioners call the work or which tactic dominates public discussion.
    • Surface volatility is a change in where and how a search platform presents ranked results, generated answers, citations, links, or brand mentions.
    • Portfolio volatility is the movement inside your own site: one topic cluster gains while another loses, even when the total remains flat.

    Each type calls for a different response. Narrative volatility may justify learning and a contained experiment. Surface volatility calls for observation across several discovery environments. Portfolio volatility calls for page-, topic-, and journey-level diagnosis. None of them automatically justifies a site-wide rewrite.

    Write an action rule before the next movement occurs. For example: a lost AI mention triggers inspection, not remediation. A repeated loss across priority prompts, combined with weaker discovery for the same commercial topic and a decline in qualified outcomes, earns a deeper investigation. This prevents a noisy answer snapshot from becoming a budget decision.

    Measure five layers instead of one traffic total

    Five transparent planes form an exploded stack containing pulses, branching routes, a prism, a constellation, and solid geometric shapes.

    Clicks remain useful, but they occupy only one part of the discovery-to-outcome chain. A resilient scorecard shows where that chain changed. It also keeps a visibility gain from being mistaken for revenue and keeps a traffic plateau from being mistaken for failure.

    Measurement layerQuestion it answersEvidence to retainDecision it supports
    DemandAre people still expressing this need?Query-theme and impression patterns, interpreted alongside rank and page coverageWhether the market, season, vocabulary, or addressable topic set has changed
    DiscoveryCan your relevant pages be found?Eligible landing pages, query coverage, rank distribution, impressions, clicks, and click-through patternsWhether to repair technical access, page targeting, snippets, or content coverage
    Answer representationDoes an AI-generated answer include and describe the brand correctly?Stable prompt checks, brand inclusion, cited or linked pages, factual accuracy, and competitor contextWhether the problem concerns inclusion, citation, entity clarity, or inaccurate synthesis
    AuthorityDo independent sources corroborate the brand and its claims?Relevant citations, earned mentions, referring coverage, expert participation, and community discussionWhether stronger evidence and off-site recognition are needed
    Business contributionDid discovery produce a valuable action?Qualified leads, sales, revenue, pipeline, subscriptions, or another agreed outcomeWhether visibility is reaching the right audience and supporting the business

    Build this scorecard around topic clusters and buyer-journey stages, not just individual URLs. A URL is an implementation unit. The business question is usually larger: Are we becoming more discoverable for a problem, a product category, or a decision that matters to a particular audience?

    1. Define the measurement unit. Combine a topic or need, an audience or persona, a journey stage, and the pages intended to serve it. Keep branded and non-branded discovery separate where the distinction changes the decision.
    2. Record traditional search evidence. Retain the query themes, landing pages, impression patterns, click behavior, rank distribution, and any crawl or indexing problem associated with the unit.
    3. Add controlled AI checks. Preserve the exact prompt, discovery surface, available environment details, locale, observation date, answer, brand inclusion, links, citations, and factual errors. Keep a stable prompt set for comparison and a separate exploratory set for finding new behavior.
    4. Attach authority evidence. Track which independent pages, publishers, podcasts, experts, and relevant communities repeat or validate the claims that matter to the topic.
    5. Join the unit to business outcomes. Use the same conversion definition across comparison periods. If attribution is incomplete, label it incomplete rather than treating unknown contribution as zero.

    Keep the raw measures visible even if you create a summary score. A single AI visibility index can hide an important distinction: the brand may appear more often while being cited less often, or it may retain inclusion while the answer becomes factually worse. Those are different problems.

    Use comparable periods and consistent filters. Annotate site releases, migrations, tracking changes, content updates, and major distribution campaigns. If the measurement method changed at the same time as the result, you do not yet have a performance conclusion.

    Use flat traffic as a branching diagnosis

    A steady ribbon of light enters a glass junction and divides into paths that rise, descend, spread into mist, and reach a glowing object.

    A flat click line is not a business verdict. Traffic measures acquisition. It does not, on its own, tell you whether demand expanded, search capture weakened, lead quality improved, AI visibility changed, or gains and losses cancelled each other out.

    Start by calculating each segment’s contribution to the net change. The total is simply the combined movement of its parts. When one cluster gains and another loses by a similar amount, the total conceals both events.

    1. Confirm comparability. Check that the periods use the same tracking definitions, market scope, device treatment, and complete reporting windows.
    2. Decompose the total. Split it by branded versus non-branded discovery, topic cluster, page type, journey stage, and any market or device distinction that could change the action.
    3. Sort segments by contribution to change. Look at gains and losses separately instead of starting with the net figure.
    4. Move one layer upstream. If outcomes fell, inspect landing-page and intent mix. If clicks fell, inspect impressions, query coverage, snippets, and rankings. If AI representation changed, inspect claim consistency, cited pages, and external corroboration.
    5. State a testable explanation. Record what changed, the evidence supporting it, what remains unknown, and which next observation could disprove the explanation.

    Common patterns should lead to different decisions:

    • Impressions rise while clicks remain flat. Click-through rate has fallen across the measured set, but that does not reveal why. Inspect the query and page mix. New awareness visibility can expand the denominator while commercially important clicks remain healthy. If losses concentrate on decision-stage queries, the same top-line pattern deserves a faster response.
    • Traffic remains flat while qualified outcomes improve. If tracking and outcome definitions stayed stable, the existing traffic is producing more value. Protect the clusters responsible, examine whether the landing-page mix shifted toward higher intent, and avoid rewriting successful pages merely to chase session growth.
    • Traffic grows while qualified outcomes weaken. More visits are not compensating for poorer business yield. Compare new versus established landing pages, journey stages, and conversion paths. The problem may be low-intent acquisition, a weaker offer path, or broken measurement rather than insufficient reach.
    • The total is flat while clusters move in opposite directions. Do not prescribe a site-wide fix. Diagnose the losing cluster for coverage, relevance, technical access, representation, and authority. Preserve the gaining cluster unless its business contribution is poor.
    • Traditional discovery is steady while AI inclusion is erratic. Treat this first as representation volatility. Check whether the brand name, entity relationships, product facts, and supporting evidence are consistent across the canonical page, structured data, and independent references before changing templates or content architecture.

    A useful performance note should therefore say more than “traffic was flat.” It should identify which audience need and journey stage moved, which layer changed first, whether the movement reached business outcomes, and what evidence would justify action. That is a diagnosis a stakeholder can challenge and a team can use.

    Build assets that work in ranked and synthesized results

    Volatility-resistant content is not content that never changes. It is an asset whose value survives a change in interface because it answers a real need, carries evidence, fits into a clear topic structure, and can be understood outside its original page.

    Persona- and buyer-journey-led content hubs provide a practical structure for that work. Build each priority hub so it supports awareness, evaluation, and decision-making instead of publishing isolated articles around whichever acronym is currently popular.

    1. Anchor the hub with a canonical explanation. State what the subject is, who it is for, the problem it solves, the important limitations, and the next decision. Keep names and core facts consistent.
    2. Cover the real question sequence. Add supporting pages for definitions, common questions, alternatives, evaluation criteria, implementation concerns, and buying intent where the audience genuinely needs them.
    3. Add evidence that can travel. Original data, a transparent method, expert insight, concrete examples, and clearly bounded claims give other people and systems something specific to reference.
    4. Connect the pages deliberately. Internal links should show how an early-stage question leads to a deeper explanation, proof, comparison, or decision page. Do not leave the relationship to keyword overlap alone.
    5. Express visible facts in JSON-LD. Use structured data to clarify entities and relationships already supported on the page. Keep markup aligned with the visible content and update both together.

    Structured data is a translation layer, not an authority generator or an AI-inclusion switch. It can make a page’s meaning less ambiguous. It cannot compensate for a thin claim, an inconsistent identity, or the absence of independent recognition.

    That independent recognition is part of the asset. Relevant publishers, mainstream coverage, respected podcasts, and engaged Reddit communities can extend a brand’s digital footprint when the contribution is worth citing. The goal is not to manufacture mentions on every platform. It is to place useful evidence where the intended audience already pays attention.

    Run this as a loop: create a defensible claim or useful resource, publish the complete version in the appropriate hub, adapt it for relevant external contexts, record the resulting mentions and citations, and watch whether discovery and business outcomes change. Repurposing should preserve the evidence while changing the format for the audience. Repeating the same promotional sentence across channels adds little.

    When performance weakens, classify the repair before editing:

    • Technical repair: the intended page is unavailable, inaccessible, duplicative, poorly connected, or otherwise difficult to discover.
    • Content repair: the page does not answer the relevant question, contains stale or inconsistent facts, lacks needed depth, or mismatches the journey stage.
    • Authority repair: the page is useful but its important claims lack independent validation, expert support, citations, or distribution.
    • Measurement repair: the team cannot distinguish a genuine performance change from a tracking, prompt, reporting, or segmentation change.

    This classification keeps you from using content production to solve every problem. More pages will not repair broken tracking. Schema will not create third-party trust. Digital PR will not fix an inaccessible canonical page.

    Set action rules before the dashboard moves

    Your operating model should be calmer than the industry feed. Fewer than half of the visible voices examined maintained a consistently positive and stable stance toward AI-related SEO terminology. That does not make the discussion useless. It means popularity and sentiment are weak substitutes for evidence from your own audience, content portfolio, and outcomes.

    • Correct immediately when your own foundation is broken. Restore unavailable pages, repair failed tracking, correct inconsistent canonical facts, and address technical defects that prevent reliable discovery or measurement.
    • Investigate when evidence repeats across layers. A recurring loss across priority prompts becomes more meaningful when the same topic also loses traditional discovery, external corroboration, or qualified outcomes.
    • Hold when only one noisy observation changes. Preserve the record, repeat the check under comparable conditions, and look for confirmation before editing a stable content system.
    • Experiment when the opportunity is plausible but unproven. Isolate the tactic, define the intended layer of impact, preserve a comparison, and avoid making the experiment dependent on a new label being permanent.

    Maintain a change log that connects each meaningful intervention to its hypothesis. Record the affected topic cluster, the layer expected to move first, the downstream measure that should follow, and the condition that would cause you to stop or reverse the change. Without that record, normal volatility can be misread as proof that the most recent edit worked.

    At each review, ask four questions in order: What moved? Where in the discovery-to-outcome chain did it move first? Which independent measure corroborates it? What is the smallest reversible change at that layer? Those questions turn a dashboard discussion into an operating decision.

    Key takeaways

    • Treat AI-generated answers as an additional discovery and representation layer, not a reason to discard technical SEO, useful content, or authority building.
    • Diagnose performance by topic cluster, audience, and journey stage because a flat site-wide total can conceal consequential gains and losses.
    • Pair clicks with demand, traditional discovery, AI representation, independent authority, and business outcomes.
    • Act when several layers corroborate a problem; observe when a single prompt, label, or headline moves.
    • Keep structured data aligned with visible facts, build evidence worth citing, and distribute it where the intended audience is already active.

    At your next performance review, replace “Did organic traffic grow?” with “Which topic and journey stage moved, where did the path change, and did business contribution follow?” If your scorecard cannot answer, repair the measurement before rewriting the site. When the evidence does identify a problem, make the smallest change at the failing layer and watch what happens downstream.

    References

  • Maximize Ecommerce Success with Demand Gen & Performance Max

    Maximize Ecommerce Success with Demand Gen & Performance Max

    When Google introduced Demand Gen campaigns in 2023, I saw them as a promising way to boost engagement across platforms like YouTube, Discover, and Gmail.

    Initially, they felt experimental, straddling the line between awareness and performance, but they’ve come a long way since.

    Now, the creative flexibility and enhanced audience control make Demand Gen a go-to campaign type for my ecommerce clients.

    This strategy allows me to scale revenue in a controlled manner, maintaining brand consistency while testing creative approaches to drive conversions.

    I’ve found that Demand Gen delivers the best results when strategically paired with Performance Max and Search campaigns.

    Advertising with Demand Gen is ideal if you crave more control.

    One major drawback of Performance Max is its lack of transparency and manual control.

    If precise targeting, placement, or creative control is essential, Demand Gen stands out as the better option.

    Performance Max auto-generates ads from your uploads, relying on Google’s AI to mix and match for the best performance.

    This makes it crucial to provide top-notch creative assets.

    For example, a fitness brand might create separate asset groups for products like leggings, shorts, and vests.

    While this helps target relevant audiences, the control isn’t exhaustive.

    However, Demand Gen offers far superior flexibility.

    It allows me to upload, preview, and tweak ad combinations before launch, adapting each creative to its unique placement.

    For instance, I can customize YouTube ads for in-feed, in-stream, and Shorts placements.

    This control is perfect for ecommerce brands focusing on creative precision, message testing, and maintaining a strong visual identity.

    Dig deeper: The Google Ads Demand Gen playbook

    Using Demand Gen alongside Performance Max can be incredibly effective if you leverage their roles within the customer journey. They enhance each other rather than compete.

    Demand Gen builds awareness and sparks interest by reaching higher-funnel audiences before they actively start product searching.

    Conversely, Performance Max focuses on converting lower-funnel users who are primed to purchase.

    ```json { "alt": "Collage featuring the Google Pixel Watch and Fitbit Sense 2 with various display cards and interactive elements.", "caption": "Discover seamless integration with Google Pixel Watch and Fitbit Sense 2. Explore features and styles that keep you connected and healthy, right at your fingertips.", "description": "The image showcases a collage of the Google Pixel Watch and Fitbit Sense 2, emphasizing their sleek design and advanced functionality. The central focus is a profile of a person interacting with the Google Pixel Watch, surrounded by smaller display cards of the Fitbit Sense 2. Interactive social media elements like likes and dislikes hint at user engagement. The arrangement suggests an interactive and user-friendly interface, highlighting features like health tracking and connectivity options. Keywords: Google Pixel Watch, Fitbit Sense 2, health tech, smartwatches." } ```

    For example, a fitness retailer might utilize Demand Gen for lifestyle videos and discovery ads promoting their latest activewear.

    When a potential customer begins to research or exhibit purchase intent, Performance Max engages with tailored Shopping and Search ads to finalize the sale.

    I’ve set up feed-only Performance Max campaigns, providing only a product feed within the asset group.

    This restricts Performance Max activities to Shopping placements, focusing it sharply on direct conversions.

    Meanwhile, Demand Gen operates across platforms like YouTube, Gmail, Discover, and Shorts, covering the upper and mid-funnel with more visual, creative content focused on awareness.

    This configuration minimizes overlap between campaign types while ensuring user engagement throughout the funnel, from brand discovery to purchase.

    For larger accounts with flexible budgets, this dual structure drives holistic performance and clearer attribution.

    In contrast, smaller accounts seeking efficiency should prioritize mastering high-intent campaigns before layering in Demand Gen once the core conversions are stable.

    The diverse campaign types now offer advertisers more flexibility than ever, yet it requires understanding Google’s restructuring of video and discovery products.

    Dig deeper: Why Demand Gen is the most underrated campaign type in Google Ads

    Since July 2025, Google’s Video Action Campaigns (VACs) have been replaced by Demand Gen.

    It streamlines Google’s visual placements into one campaign type, including YouTube in-stream, Shorts, in-feed, Gmail, and Discover.

    This change is significant. VAC was successful for ecommerce, particularly for conversion-centric video. Its removal underscores Google’s encouragement to embrace Demand Gen.

    The advantage is that Demand Gen provides stronger creative control and diverse testing options across YouTube placements.

    If you previously ran VAC campaigns, they are now under Demand Gen. Ensure your top-performing assets and audiences have migrated correctly, then use the new controls to optimize performance.

    Audience control is a significant benefit of Demand Gen, and it’s a reason why I consistently use it for ecommerce.

    Demand Gen allows precise audience creation, letting me decide who sees the ads.

    I can select placements, merge audience types, and allocate the budget strategically.

    It’s the only Google Ads campaign type supporting lookalike audiences, valuable for brands focused on acquiring quality leads.

    ```json { "alt": "Google Ads campaign settings screen showing various ad channel options.", "caption": "Maximize your reach by choosing from various Google Ads channels like YouTube, Discover, and Gmail to tailor your advertising strategy.", "description": "This image displays a Google Ads campaign setup screen on a laptop. The interface allows users to select ad channels including YouTube, Discover, Gmail, and the Google Display Network. Each option is highlighted with checkboxes that can be selected to target specific audiences and surfaces. This setup enhances the versatility and reach of digital marketing campaigns, providing advertisers with the tools to optimize ad delivery across multiple Google platforms." } ```

    While Performance Max utilizes audience signals over fixed targeting, Demand Gen excels for control, testing, and segmentation strategies.

    In mid-2025, Google rolled out an open beta for advertisers to opt out of specific Demand Gen channels manually.

    This means I can now control ad display, excluding Discover or YouTube Shorts if they don’t align with my objectives or creative format.

    This small but significant update offers more control, a feature often lacking in many of Google’s automated campaign types.

    Dig deeper: Google Ads rolls out channel control for Demand Gen campaigns

    In early 2025, Google introduced product feed integration for Demand Gen campaigns. This change allows me to link the Google Merchant Center feed, incorporating live product data directly into visual ads.

    This development bridges performance and branding for ecommerce, enabling storytelling through creative visuals while displaying actual products.

    For instance, a fashion retailer can showcase a new collection in a video advert while featuring shoppable product cards below.

    This update positions Demand Gen as a hybrid between Shopping and Display, a much-anticipated capability among ecommerce advertisers.

    Demand Gen typically demands a larger budget than other campaign types.

    Google recommends starting at about £100 per day per campaign or 20 times your target CPA/tROAS, whichever is higher.

    Practically, the £100-per-day baseline is a viable starting point for effective data collection and optimization. Lower budgets restrict data flow and slow progress.

    Demand Gen complements your broader Google Ads strategy, rather than replacing Search or Performance Max.

    It’s a premium, visually led campaign type that boosts awareness leading to conversions, particularly effective when you have accurate measurement, a clean product feed, and clearly defined audiences.

    The table compares Demand Gen and Performance Max on key aspects that matter to advertisers.

    Dig deeper: Google pushes Demand Gen deeper into performance marketing

    Performance Max excels in scale but can be opaque.

    Demand Gen offers the control advertisers have demanded—genuine creative testing, audience precision, and placement visibility.

    For sustainable ecommerce growth, I recommend using both. Performance Max captures demand, while Demand Gen creates it.

    Together, they form a comprehensive framework for scalable and sustainable growth.

    Inspired by this post on Search Engine Land.

    crushpress.ai community screenshot
  • How to Choose an Industrial Marketing Agency That Fits

    How to Choose an Industrial Marketing Agency That Fits

    If you are choosing an industrial marketing agency, a polished proposal is the easy part. The harder question is whether the team can learn a technical offer, earn access to your subject-matter experts, reach the people involved in the purchase, and show what became qualified pipeline.

    A candidate pool gives you names. A disciplined selection process tells you which agency can actually do the work. Use the framework below to prepare your brief, test technical fluency, compare proposals, and protect the engagement before you sign.

    Write the buying brief before you build the shortlist

    Do not begin with a list of services you think you need. Begin with the commercial problem the agency must help solve. Otherwise, every proposal will describe a different interpretation of success, and you will be comparing presentation quality rather than strategic fit.

    Prepare a compact decision brief with the following information:

    • Commercial outcome: State whether the priority is qualified pipeline, entry into a market, distributor support, aftermarket growth, account expansion, product adoption, or another defined business result.
    • Offer boundary: Name the products, services, applications, territories, and customer segments that are in scope. Identify what is explicitly out of scope.
    • Buying group: List the people who use, specify, approve, purchase, install, maintain, or resell the offer. Do not flatten them into a generic buyer persona.
    • Available evidence: Inventory approved specifications, certifications, performance data, technical drawings, case material, expert commentary, customer proof, and product imagery. Mark anything that requires legal, engineering, or customer approval.
    • Valuable conversion: Define the actions that matter, such as a qualified request for quote, sample request, site visit, consultation, drawing download, specification download, phone call, or distributor inquiry.
    • Measurement path: Identify the CRM stages, lead-status definitions, sales owner, and reporting systems that will determine whether marketing activity produced useful demand.
    • Operating constraints: Document restricted claims, regulatory reviews, channel conflicts, brand requirements, development limitations, subject-matter expert availability, and internal approval steps.

    Replace goals such as “increase awareness” or “generate leads” with language your sales team can recognize. For example, define what information an inquiry must contain before sales can quote it, which customer types are commercially attractive, and which inquiries should be excluded. If marketing and sales cannot agree on a qualified inquiry, an agency cannot optimize toward one.

    Set your disqualifiers at the same time. These might include weak analytics capability, no technical review process, outsourced execution with no named owner, unclear account ownership, or an unwillingness to work inside your claims-approval rules. A disqualifier should remain a disqualifier even when the pitch is impressive.

    Test industrial fluency with a real working session

    A plant engineer explains an opened industrial pump assembly to two marketing specialists during a hands-on workshop.

    An agency does not need to arrive knowing every detail of your process. It does need a credible method for learning technical material without turning it into vague benefit copy. You can see that method more clearly in a working session than in a capabilities deck.

    Give each finalist the same public product or service page and the same application context. Ask the proposed team to work through these questions with you:

    • What does the offer do, where does it fit, and where does it not fit?
    • Which facts are clear, which are unsupported, and which require an expert to verify?
    • Who uses the offer, who specifies it, who approves it, and who controls the purchase?
    • What operational problem brings a buyer to the page, and what information would help that buyer continue evaluating?
    • What proof would make the central claim credible?
    • Which search questions, comparison questions, and implementation questions should the content answer?
    • What should the visitor do next, and what would make that action useful to sales?
    • What would the team need from engineering, product, sales, service, compliance, or distribution before publishing?

    Pay attention to the questions the agency asks. Strong discovery separates facts from assumptions, notices exclusions and tradeoffs, and identifies the internal expert who can resolve each uncertainty. Weak discovery paraphrases the existing page, adds generic adjectives, and starts recommending channels before the buying problem is understood.

    Ask for evidence of the working process, not just customer logos. Useful evidence can include a redacted content brief, an interview guide for a technical expert, a claims-review workflow, a campaign measurement specification, a reporting example, or a before-and-after explanation of how a technical page was improved. The closest match is not always an identical industry. Comparable product complexity, buying risk, sales motion, and review constraints can be more revealing than a familiar vertical label.

    Confirm who produced each example and whether those people will work on your account. Agency credentials matter less when the proposed delivery team did not create the work being shown.

    Judge the channel plan as a connected demand system

    Unbranded communication tools connect through illuminated cables to a transparent pipeline leading toward a sales meeting area.

    Industrial demand rarely fits neatly inside a single campaign report. A buyer may discover a problem through search, compare technical approaches, return through a branded query, download a drawing, speak with a distributor, and enter the CRM under a different source. Your agency should design the content, channels, conversion paths, and measurement rules as parts of the same system.

    Make technical content useful before making it plentiful

    Ask the agency to propose a page architecture based on buyer tasks, not a publishing quota. Depending on your offer, that architecture may include:

    • Product or service pages that explain fit, exclusions, specifications, constraints, evidence, and the appropriate next action.
    • Application pages that connect an operating condition or use case to a suitable solution without pretending every product fits every environment.
    • Technical answer pages that address selection, compatibility, troubleshooting, maintenance, installation, or implementation questions your experts can answer accurately.
    • Comparison and alternative pages that explain meaningful tradeoffs rather than declaring your offer universally superior.
    • Proof pages that organize approved performance evidence, certifications, case material, processes, and expert qualifications.
    • Commercial access pages that help a visitor request a quote, locate a distributor, submit project details, download the correct resource, or reach the appropriate team.

    For search, answer engines, and generative systems, the fundamentals still have to be present on the page. The agency should make products, services, applications, organizations, and expert claims unambiguous; answer important questions directly; connect related pages with purposeful internal links; and use applicable structured data that agrees with the visible content.

    Ask who selects the structured-data types, who validates the markup, how conflicts with existing plugins or templates are handled, and what triggers an update when the page changes. JSON-LD can clarify machine-readable facts. It cannot repair an unsupported claim, a confused page, or missing evidence. Treat guaranteed rankings, guaranteed AI citations, and guaranteed inclusion in generated answers as disqualifiers.

    The same discipline applies to paid search, paid social, email, industry media, distributor programs, and event support. For every proposed channel, require the agency to state:

    • Which audience condition or buying task the channel addresses.
    • Which offer and asset the audience will encounter.
    • Which next action is appropriate at that stage.
    • Which signal will indicate useful progress.
    • Which evidence would cause the team to change or stop the tactic.

    Make measurement survive the sales handoff

    A useful measurement design follows the path from campaign or source to landing page, conversion, CRM record, sales disposition, and opportunity. A dashboard that stops at impressions, clicks, rankings, or sessions cannot tell you whether the agency is attracting commercially relevant demand.

    Require a measurement specification before launch. It should identify each tracked action, the data captured with it, the CRM destination, the person responsible for follow-up, the treatment of duplicates and spam, and the check used to catch broken forms or tags. Campaign identifiers, call tracking, form fields, consent handling, and offline sales updates should fit the systems you actually use.

    Marketing should not invent revenue attribution after the fact, and sales should not leave every lead status blank. Agree on shared definitions before judging performance. The most useful report shows not only what happened, but which audience, message, page, offer, or channel should receive more investment, correction, or removal.

    Compare proposals by evidence, dependencies, and ownership

    Standardize your evaluation before proposals arrive. Mark each requirement as mandatory or preferred, then record the evidence as confirmed, assumed, or missing. This prevents a polished presentation from quietly compensating for a fatal weakness elsewhere.

    Evaluation areaEvidence to requestWarning sign
    Technical discoveryProduct and buyer hypotheses, open questions, expert-interview plan, and claims-review processGeneric personas and recommendations formed before technical discovery
    StrategyClear connection between the commercial objective, buyer task, channel role, offer, and conversionA menu of tactics with no decision logic
    Content qualityRepresentative brief, source requirements, technical review steps, and approval ownershipA production-volume promise with no accuracy workflow
    SEO, AEO, and GEOPage architecture, query and intent mapping, entity clarity, internal linking, structured-data governance, and update planGuaranteed rankings, citations, or generated-answer placement
    MeasurementEvent definitions, CRM mapping, lead-status rules, dashboard example, and data-quality checksReporting limited to visibility and traffic
    Delivery teamNamed roles, allocation assumptions, escalation path, and examples produced by the proposed teamSenior specialists sell the engagement but disappear from delivery
    Commercial modelIncluded deliverables, client dependencies, media treatment, change-control process, and acceptance criteriaA vague retainer that leaves scope and accountability open to interpretation
    Ownership and accessWritten terms for accounts, data, source files, creative assets, tracking, code, and transition supportCritical systems remain under an agency-controlled identity

    Ask every finalist to solve the same working problem and use the same evaluation areas. Do not score a claim such as “we can handle analytics” as evidence. Score the measurement design, sample output, named owner, and proposed quality checks.

    Reference conversations are more useful when you ask about operating behavior. Find out who actually performed the work, what the client had to supply, how the agency handled technical corrections, whether reporting changed decisions, and what happened when priorities shifted. Speak with the people who will manage and execute your engagement as well as the people selling it.

    Contract for learning, ownership, and a clean handoff

    The contract should turn proposal language into operating rules. Have the appropriate commercial and legal owners review the terms before signature. Unclear ownership or access provisions can make an agency change expensive, interrupt measurement, or leave you without editable assets.

    Resolve these points in writing:

    • Scope and acceptance: Define included and excluded work, review rounds, approval criteria, and the process for changing priorities.
    • Client dependencies: Name the access, technical experts, product data, approvals, development support, and sales feedback your team must provide.
    • Claims governance: Identify who can approve performance claims, comparisons, certifications, customer references, and regulated language.
    • Account control: Use company-controlled identities for analytics, advertising, search tools, tag management, domains, repositories, and other critical systems. Give the agency the access it needs without making it the only administrator.
    • Asset ownership: Address final assets, editable source files, research, keyword maps, content briefs, templates, tracking specifications, structured data, custom code, and historical reporting.
    • Data handling: Define permitted access, storage, retention, deletion, confidentiality, and incident responsibilities for lead, customer, employee, and account data.
    • Fees and spend: Separate agency fees, media spend, software costs, production expenses, and pass-through charges so the budget can be reconciled.
    • Transition: Specify how credentials, documentation, files, active campaigns, reporting history, and open work will be transferred when the engagement ends.

    If important uncertainty remains, structure the initial phase around a decision checkpoint. Useful outputs include approved positioning, a claims and evidence inventory, a prioritized page architecture, a measurement specification, a representative deliverable, and an execution plan with dependencies. You can then continue, revise the scope, or stop based on visible work rather than optimism.

    Key takeaways

    • Brief the agency in commercial and sales language before discussing channels.
    • Test the proposed team on a real product, application, and buying problem.
    • Look for a disciplined learning and technical-review process, not superficial familiarity with industry terminology.
    • Evaluate content, SEO, AEO, GEO, paid media, conversion, CRM handling, and reporting as a connected demand system.
    • Require evidence for every capability claim and reject guarantees the agency cannot control.
    • Keep critical accounts, data, editable assets, and documentation accessible through company-controlled systems.

    Your next move is practical: finish the decision brief, choose a representative working problem, and send both to every serious finalist. The strongest choice will be the team whose reasoning stays coherent from product truth and buyer need through conversion, sales acceptance, and measurable pipeline.

    References

  • How to Choose a Healthcare or Medtech Marketing Agency

    How to Choose a Healthcare or Medtech Marketing Agency

    You may be staring at several polished agency proposals that all promise strategy, content, search visibility, and growth. The difficult part isn’t finding a capable-looking firm. It is determining which firm understands your revenue path, can work safely inside your approval process, and will let you verify what it actually contributes.

    The market is crowded enough that 2026 screens of medtech SEO agencies began with more than 60 firms, while a separate assessment of healthcare marketing agencies also began with more than 60. You will narrow that field much faster with a precise buying brief, an evidence-weighted scorecard, and a realistic working test.

    Write the brief around the revenue path, not marketing services

    An illustrated medtech revenue path connects a device demonstration, compliance review, hospital procurement, clinical use, and revenue tokens.

    Healthcare and medtech sit near each other on an industry map, but they do not automatically create the same agency brief. A provider organization may need to turn local demand into qualified appointment requests. A medtech company may need to educate clinicians, administrators, procurement stakeholders, distribution partners, or other participants before a commercial conversation can advance.

    If you ask for SEO, content, paid media, or AI optimization before defining that path, agencies will sell the services they already deliver. Start with the change your organization needs and work backward to the marketing capability.

    If you market a practice or care-delivery organization

    • Name the service line and location you need to support. Local visibility for a specific service is a different assignment from national brand building.
    • Define a qualified conversion. It might be an appointment request, a call that meets your intake criteria, or a professional referral inquiry. A raw form submission is not automatically a useful lead.
    • Describe the path after conversion. Tell the agency who receives the inquiry, how eligibility or fit is assessed, and where the result is recorded.
    • State operational constraints. If a location, clinician, or intake team cannot absorb additional demand, more traffic can create a worse patient experience without improving the business.
    • List the people who approve medical statements, patient-facing language, advertising claims, and reputation responses. The agency needs to design around that workflow.

    If you market a medical technology

    • Map the audience chain. Separate the people who use the technology, evaluate it, approve it, purchase it, distribute it, and search for information about it.
    • Name the decision friction. You may need category education, technical explanation, economic justification, evidence discovery, or help distinguishing the product from an established alternative.
    • Choose a meaningful commercial action. A demo request, distributor inquiry, sales-accepted conversation, or engagement from a target organization can be more informative than undifferentiated lead volume.
    • Document the evidence boundary. Give the agency the approved language, supporting material, prohibited claims, required review steps, and owner of each decision.
    • Identify geographic and organizational complexity. A single-market campaign should not be scoped like a multi-region program that must balance central messaging with local relevance.

    Turn those decisions into a short brief before you take another sales call. Include the business outcome, audience, current obstacle, desired conversion, geographic scope, approval owners, evidence constraints, available assets, required systems, and definition of a qualified result. Add explicit non-goals as well. If brand awareness is not the assignment, say so. If the agency will not control paid media, website development, or sales operations, say that too.

    This brief makes proposals comparable. It also reveals whether an agency can reason from your problem or merely translate its standard package into healthcare language.

    Match the agency model to the bottleneck you actually have

    Specialist healthcare agencies do not all solve the same problem. Available models span authority building, local search, international programs, full-service marketing, long-term content, technical web work, reputation management, and combined search and social strategies. None of those models is universally superior. The right one removes the constraint that is currently preventing progress.

    • Choose a local-search specialist when patients must discover a particular location or service in geographically relevant results. Ask for evidence of location architecture, business-profile management, local content judgment, review workflows, and conversion tracking through intake.
    • Choose an authority-and-content specialist when your audience cannot make progress without credible education. Ask to see how topics are selected, how subject-matter experts participate, how claims are checked, and how content connects to an intended commercial action.
    • Choose a technical website and SEO firm when crawlability, site structure, publishing friction, accessibility, performance, or an impending rebuild is the main constraint. Require a clear division between diagnosis, implementation, design, content migration, validation, and ongoing optimization.
    • Choose a reputation-led agency when trust signals, inconsistent profiles, or the handling of public feedback is obstructing demand. Ask who is authorized to respond, which issues are escalated, and how the work connects to brand and search visibility without exposing sensitive information.
    • Choose a multi-location or international specialist when central control and local relevance keep colliding. Ask the agency to show how it governs shared templates, local pages, market-specific review, brand consistency, and reporting across regions.
    • Choose an integrated firm when channel coordination is the bottleneck. A broad agency can be useful when the same strategy must govern web, search, content, advertising, and social execution. Make it identify the owner of the integrated plan; a bundle of separate channel teams is not automatically integration.
    • Choose a social-and-search model when audience discovery genuinely crosses those surfaces. Require a clear role for each channel and a method for recognizing when social attention creates branded search, site engagement, or a qualified inquiry.
    • Choose an AI-search specialist only when it can turn generative engine optimization into inspectable work. Some firms now market GEO alongside conventional Google SEO, with visibility in recommendations from platforms such as ChatGPT as an objective. Ask for the target questions, baseline observations, content changes, authority work, measurement method, and limitations behind that objective.

    Do not buy a larger service bundle just because it appears more complete. If the real problem is medical-content production, adding paid media and social posting may increase coordination before it increases performance. Conversely, a narrow SEO firm may be the wrong choice when your website, analytics, intake process, and brand message all need coordinated repair.

    Ask each agency to identify the bottleneck in its own words. Then ask what it would defer. A credible prioritization includes work that should not happen yet.

    Score evidence before you score the presentation

    A scorecard prevents the most confident presenter from quietly becoming the default choice. One cardiology-focused evaluation considered 73 specialist firms and weighted average review score at 30%, healthcare experience at 25%, leadership experience at 15%, active client portfolio at 10%, compliance expertise at 10%, median employee tenure at 5%, and media references and case studies at 5%.

    That weighting is a useful starting structure, not a universal procurement rule. Adjust the emphasis before opening proposals. A sensitive content program may deserve more emphasis on compliance and subject-matter workflow. A rebuild may require more scrutiny of technical delivery. A highly specialized device may make relevant audience and category experience more important than the size of the agency’s general healthcare portfolio.

    CriterionBenchmark weightEvidence to request
    Average review score30%Recurring themes from clients with comparable scopes, including what happened when delivery was difficult. Treat a rating as a lead for verification, not proof by itself.
    Healthcare industry experience25%Work involving a similar audience, business model, review burden, and conversion path. General healthcare logos do not establish experience with your particular problem.
    Leadership experience15%The named person accountable for strategy, their relevant background, and their actual involvement after the sale.
    Client portfolio size10%Relevant active work, team capacity, possible conflicts, and an explanation of how resources will be assigned to your account.
    Compliance expertise10%An actual workflow for evidence, medical review, advertising review, privacy-sensitive access, escalation, approval, and revision history.
    Median employee tenure5%The expected delivery team, continuity of key roles, and the handoff plan if a strategist, writer, or account lead changes.
    Media references and case studies5%Cases that define the starting problem, agency contribution, measurement method, relevant constraints, and result. Ask which parts can be independently verified.

    Rate the evidence behind each answer as verified, plausible but unverified, or absent. Keep that confidence judgment separate from the agency’s claimed capability. A beautiful case study with an undefined baseline should not outscore a less dramatic example with a clear method and comparable scope.

    Set disqualifiers before scoring. Reasonable examples include refusal to follow your medical or legal review process, uncertainty about who owns core accounts and content, an unexplained need for sensitive data, a material client conflict, or guarantees of rankings and AI recommendations that the agency cannot control. A disqualifier should represent unacceptable exposure, not merely a preference.

    Put finalists through one real working session

    Healthcare and agency professionals collaborate around a table with a medical device, blank evidence cards, approval tokens, and workflow blocks.

    References and proposals tell you what an agency wants you to believe. A controlled working session shows you how its team thinks. Give every finalist the same redacted scenario and the same information. Do not share real patient information or sensitive commercial material merely to make the exercise realistic.

    1. Present the business problem without prescribing the channel. Ask the team to identify the audience, conversion, unknowns, constraints, and likely bottleneck before proposing tactics.
    2. Request a prioritized first phase. The team should distinguish prerequisites from experiments and explain what it would postpone. Listen for dependencies on your website, analytics, subject-matter experts, intake operation, or sales process.
    3. Test the content workflow. Provide a fictional or already approved example claim and ask how it would become a page, campaign, or answer-ready content asset. Require the team to identify where evidence, medical review, compliance review, and final approval enter the process.
    4. Trace measurement from discovery to business outcome. Ask the agency to draw the path from a search result, AI answer, advertisement, or social interaction through the website and into the system where your organization accepts or rejects the inquiry.
    5. Examine the AI-search plan separately. Ask which user questions it will monitor, how it will assess brand mentions and citations, which on-site changes it expects to make, how structured data fits the work, and how it will distinguish visibility from a qualified outcome.
    6. Review the operating model. Confirm the day-to-day team, decision rights, meeting purpose, reporting inputs, revision process, account ownership, content ownership, data access, and offboarding handoff.

    Make compliance visible in the workflow

    Compliance expertise should produce more than a badge in a capabilities deck. Ask the agency to draw the route from topic selection to evidence collection, drafting, subject-matter review, compliance or legal review, publication, monitoring, and later revision. Every handoff needs an owner. The agency should also be able to explain what happens when a reviewer rejects a claim or when approved language changes.

    If the work could involve information your organization treats as protected or sensitive, let your privacy, security, compliance, and legal owners determine the access and contractual requirements before access is granted. An agency’s familiarity with HIPAA or healthcare advertising standards does not replace your organization’s review or professional legal advice.

    Watch how the agency reacts to limits. Strong teams ask for the evidence they need, mark unresolved claims, and adapt the message. Weak teams treat review as a final proofreading step or assume that careful wording can rescue an unsupported promise.

    Treat GEO as auditable work, not a separate pile of AI copy

    A defensible healthcare GEO program still needs content that is understandable, medically accurate, and connected to authority. A documented cardiology approach combines accessible medical content and authority building with GEO and conventional Google search. Use that combination as a diligence framework, not as proof that any agency can guarantee inclusion in a particular answer.

    Ask the finalist to show the chain of reasoning: which audience question matters, what information an adequate answer requires, what your site currently lacks, which approved evidence supports the response, what content or structured information will change, and how visibility will be observed over time. It should also separate work on your own site from third-party authority or mentions that it cannot directly control.

    Do not accept isolated screenshots as a complete measurement system. Require a repeatable query set, a record of the conditions under which observations were made, visibility and citation tracking, site-engagement measures, and a connection to qualified commercial or patient-access outcomes. The agency should acknowledge uncertainty and variation instead of converting every appearance into a success claim.

    Make reporting follow the lead beyond the form

    Marketing reports often stop at the easiest event to count. Your decision should not. Ask who will connect an inquiry to intake acceptance, a scheduled interaction, a sales disposition, or whichever downstream status your organization uses. If that connection cannot be made yet, the proposal should identify the data gap and assign responsibility for closing it.

    The agency should distinguish three things: activity it completed, visibility or engagement that followed, and business outcomes that may have multiple causes. That separation protects you from both exaggerated credit and premature blame. It also makes optimization possible because you can see whether the problem is discovery, conversion, qualification, or follow-up.

    Key takeaways for a defensible agency decision

    • Define the audience, business outcome, qualified conversion, approval path, and non-goals before requesting channels or deliverables.
    • Choose the agency model that removes your present bottleneck. Local search, content authority, technical web work, reputation, integrated marketing, and GEO are different capabilities.
    • Use weighted criteria to control the decision, but adjust the emphasis before you see agency proposals.
    • Score the quality of evidence separately from the claimed capability. Comparable work and a transparent method matter more than a familiar logo.
    • Test finalists with the same redacted working scenario. Observe how they diagnose, prioritize, handle claims, design measurement, and respond to constraints.
    • Keep medical, privacy, compliance, and legal decisions with the qualified owners inside your organization. Agency expertise should support that governance, not replace it.
    • Require AI-search work to identify target questions, content and authority gaps, observable changes, measurement limits, and the connection to a meaningful outcome.

    Before your next agency call, reduce your assignment to one sentence: for this audience, we need this measurable action to improve, within these evidence and operating constraints. Send the same brief to every finalist and require each one to show its reasoning against it. The best choice is the team that gives you the clearest, safest, and most verifiable path from audience need to business result.

    References

  • SEO Consultant Turns Efforts Into Support for Immigrant Families

    SEO Consultant Turns Efforts Into Support for Immigrant Families

    I’ve decided to transform my expertise in SEO into a powerful fundraising initiative to assist those affected by recent ICE raids in Minnesota. Instead of standing by, I’m trading my consulting hours for donations to support immigrant families in need.

    The tipping point for me came when recent events in Minnesota crossed ethical lines I had drawn. I felt a strong urge to act rather than just watch from the sidelines. I shared my initiative on LinkedIn and my blog, inviting the community to join this cause.

    What’s happening. I’m leveraging my skills by offering my services in return for donations through GiveMN. This Minnesota-based platform channels funds to families and individuals hit hardest by the ICE raids.

    Within just seven hours, we raised $1,850, which soon increased to $1,950. It’s heartwarming to see backing from renowned SEO agencies, SaaS companies, and individual practitioners rallying behind this cause.

    Why we care. My efforts showcase a vital aspect of the search marketing industry: our community’s ability to rally resources for broader social causes. This isn’t just about professional skills; it’s about standing up for humanity and activating swift collective action.

    Catch up quick. The fundraiser springs from widespread outrage following the launch of Operation “Metro Surge” by federal immigration authorities in December. This operation deployed roughly 3,000 ICE and Border Patrol agents into the Twin Cities, resulting in significant unrest.

    The operation triggered issues like racial profiling, unwarranted home invasions, detentions at workplaces, and tragically, the shooting of 37-year-old Renee Nicole Good in downtown Minneapolis, sparking massive protests.

    What I’m saying. As I put it, “This is NOT about politics. This is about treating all people as humans.” It’s a call to action to see beyond political lines and focus on our shared humanity.

    Inspired by this post on Search Engine Land.

    crushpress.ai community screenshot
  • How Google Counts Impressions When One URL Appears Twice

    How Google Counts Impressions When One URL Appears Twice

    You see your page cited inside an AI Overview and again as a traditional blue link. It looks like two pieces of search-result real estate, so you expect Google Search Console to report two impressions. It won’t.

    When the same URL appears in both places for the same query and search experience, Google Search Console records one impression rather than two. Once you understand what is being counted, you can stop treating the result as a tracking fault and start measuring the extra visibility separately.

    Key takeaways

    • The same URL appearing in an AI Overview and a traditional blue link produces one Search Console impression for that search experience.
    • Google treats an AI Overview as one position, with the links inside it sharing that position under the usual impression rules.
    • Repeated appearances of the same URL in the current set of results are aggregated rather than counted as separate impressions.
    • One impression does not mean there was only one placement. It means Search Console has compressed those placements into one URL-level count.
    • Keep Search Console performance data and observed SERP placement data in separate reporting layers if you need to evaluate AI Overview visibility.

    The counting rule follows the URL, not the number of boxes

    One webpage tile branches into two different search result placements while passing through a single counting gate.

    An impression is tied to the visibility of a link within the current set of search results. Google does not issue another impression merely because the same URL is presented in a second search feature on that results page.

    This matters because an AI Overview may contain several links while occupying a single position. Each link in the Overview shares that position and remains subject to the standard visibility rules. If one of those URLs also appears in the blue links below, the extra occurrence does not create a second impression for that URL.

    What happens in one search experienceHow to interpret the impression countWhat not to assume
    The same URL appears in an AI Overview and a blue linkOne impression is counted for that URLThe second placement was not necessarily missed or ignored
    The same URL appears more than once in the current resultsThe occurrences are aggregatedEach visual instance does not receive its own impression
    The user scrolls past the URL and returns to itNo additional impression is created within that results experienceRepeated visibility does not restart the counter
    Two different URLs from the same site appearThe same-URL clarification does not determine the resultDo not extend a URL-level rule to an entire domain without separate evidence

    The last distinction is important. The rule is about the same URL. It does not establish that every appearance from the same brand, domain, or group of similar pages will be consolidated. When you investigate a discrepancy, compare URLs rather than counting logos, domains, or visually similar listings.

    One impression does not mean one placement

    Search Console’s count is easy to misread as an inventory of everything Google displayed. It is not. In this situation, one impression can represent a URL that occupied two visibly different parts of the results page.

    That compression limits what you can conclude from the number alone. A single recorded impression cannot tell you whether the searcher noticed the AI Overview citation, the blue link, or both. It also cannot isolate the incremental effect of securing both placements.

    • Do conclude: the URL received one qualifying Search Console impression under Google’s counting rules.
    • Do not conclude: the URL appeared only once on the results page.
    • Do conclude: the Search Console impression total should not be manually doubled to reflect two observed placements.
    • Do not conclude: the second appearance had no value simply because it did not add another impression.
    • Do conclude: dual placement can reinforce brand visibility and credibility.
    • Do not conclude: that reinforcement produced a specific traffic or conversion lift unless you have separate evidence.

    This is the practical distinction between measurement and presence. Search Console measures the impression according to its rules. The results page may still give the searcher two opportunities to encounter your page. Those are related facts, but they are not interchangeable metrics.

    Audit dual appearances without rewriting Search Console data

    If your dashboard appears to be missing an impression, first test whether the expected second impression came from counting the same URL twice on one results page. Use a short audit that preserves the reported data while documenting the SERP layout.

    1. Define the suspected duplication. Record the query, the URL, and the two elements in which you observed it. Use labels such as AI Overview and blue link instead of writing only that the page ranked twice.
    2. Verify that it is the same URL. Do not treat two pages from one domain as though they were automatically one reporting unit. If the displayed addresses differ, flag that difference rather than forcing the same-URL rule onto them.
    3. Capture the search-result composition. Note whether the URL appeared in the AI Overview, the traditional results, or both. This is placement evidence, not an adjustment to Search Console.
    4. Leave the Search Console impression unchanged. If the same URL occupied both placements in the same search experience, one impression is the expected result. Adding a second impression in a spreadsheet would make your derived total incompatible with Google’s count.
    5. Check the reporting model. A dashboard that creates one row per SERP feature may duplicate a shared impression when those rows are added together. Keep the impression in one performance record and store the placement labels separately.
    6. Repeat the observation before making a strategic claim. A single captured results page can confirm that dual placement is possible. It cannot, by itself, establish how often the pattern occurred across the full reporting period.

    This process also helps you identify the real problem. If the count matches the same-URL rule, there is no impression-counting error to fix. The missing element is a separate record of where the URL appeared.

    Report Search Console performance and SERP coverage separately

    A divided workspace shows one recorded impression on an analytics screen and two observed placements on a search results page.

    A useful report needs two layers. The first preserves Google’s performance data. The second describes the search features you observed. Combining them into one placement-based impression total creates false precision.

    Search Console performance layer

    Keep the query, URL, impressions, and other Search Console metrics together. Do not clone the record simply because the URL also appeared in an AI Overview. If you create separate AI Overview and blue-link rows, allocate placement labels without assigning the same impression to both rows and then summing them.

    SERP observation layer

    For each observation, store the query, exact URL, whether an AI Overview link was present, whether a blue link was present, and whether both occurred together. Include when the observation was made so nobody mistakes a captured result for a permanent search layout.

    The clean reporting language is: dual placement was observed, while Search Console counted the same URL once under its impression rules. Avoid saying that impressions doubled, that Search Console undercounted visibility, or that the second appearance generated a known incremental benefit. None of those claims follows from the impression total.

    Use the same distinction when setting targets. Search Console impressions can track reported URL visibility over time. A separate coverage field can track whether you are present in an AI Overview, a blue link, or both. That gives stakeholders two honest signals instead of one inflated number.

    The next time one URL occupies both parts of the results page, don’t adjust the impression count. Add a dual-placement annotation, preserve Google’s number, and evaluate the extra surface coverage as its own signal.

    References