Category: Legal

DMA Search Fairness: What SEO Teams Should Measure Now

If your organic click-through rate or direct conversions fell after DMA-related search changes, don’t assume your rankings failed. An extra comparison layer, a different result layout, a new intermediary, or a longer route to conversion can produce the same dashboard symptom.

The honest verdict on DMA search fairness is not proven. The rules were meant to curb gatekeeper self-preferencing, but reported outcomes include more user friction, lower click-through rates, fewer direct bookings, and no clear weakening of Google’s central position. To decide what is actually happening, you need to measure user utility, business access, competitive opportunity, and market power separately.

Search fairness is four questions, not one metric

The Digital Markets Act was passed in 2022 and came into force in March 2024. Its search-market logic was straightforward: a dominant gatekeeper should not give its own services an unfair advantage over competing services.

That principle addresses a real problem. Google has been accused of promoting services such as Google Shopping ahead of alternatives that may serve the user better. But restricting self-preferencing does not automatically produce a competitive market, a better user journey, or stronger outcomes for independent businesses. Those are different tests.

Dimension	Question to ask	Evidence worth tracking	Misleading shortcut
Procedural neutrality	Are Google-owned and independent services receiving comparable treatment?	Eligibility, placement, labels, link treatment, and destination types across matched queries	Counting how many links appear on the page
User utility	Can the searcher complete the intended task without avoidable detours?	Steps to completion, intermediate domains, refinements, backtracking, abandonment, and completion rate	Assuming more visible choices always create a better experience
Business access	Do independent providers receive qualified visits and direct conversions?	Click destination share, conversion per search impression, assisted conversions, and direct-conversion share	Using impressions or rankings without following the journey to its outcome
Contestability	Can a challenger win and retain demand without depending on the same gatekeeper?	Diversity of destinations, durable gains across query groups, new-entrant visibility, and reliance on a single acquisition route	Treating one established intermediary’s traffic gain as proof of an open market

This distinction prevents two common analytical errors. A less convenient interface does not, by itself, prove that competition became less fair. A more competitive market can impose some short-term friction while users and businesses adjust. The reverse is also true: giving several services a place on the results page does not establish fairness if Google still controls the gateway, the rules, and most demand.

One survey involving 5,000 European consumers reported a more cumbersome online experience, with respondents even expressing willingness to pay to restore aspects of the previous integrated experience. That is an important warning about user utility. It is not, on its own, a complete measure of market contestability. The right response is to retain the warning while refusing to make it answer a different question.

Build a scorecard around the complete search journey

An isometric search journey moves from a magnifying glass through result cards and a comparison layer to a confirmed direct transaction, with measurement symbols at each stage.

A DMA impact analysis should begin with a specific user task, not an account-wide traffic graph. Choose a query cohort tied to one decision: compare an offer, find a provider, reach a product page, start a booking, or complete a purchase. Then map every step from the search result to the final action.

Define matched query cohorts. Keep branded and non-branded searches separate. Split informational and transactional intent, and separate devices when their result layouts differ. An account-wide average can conceal the exact queries on which a new handoff appeared.
Record the visible search interface. For each cohort, capture result types, ordering, labels, proprietary modules, comparison services, organic links, and the domains receiving the first click. Preserve dated snapshots so later analysis does not depend on memory.
Measure the full funnel. Connect impressions and average visibility to clicks, landing sessions, qualified actions, conversion rate, direct conversions, and assisted conversions. A traffic metric tells you where attention moved; it does not tell you whether the business relationship survived the move.
Count handoffs and friction. Record how many domains and decisions sit between the result and the intended action. Look for repeated searches, backtracking, abandonment, and paths that send the user from Google to an intermediary before reaching the provider.
Segment destination ownership. Classify clicks going to Google-owned experiences, independent comparison services, publishers, marketplaces, and the provider’s own site. Without this classification, a declining organic CTR cannot reveal who captured the lost demand.
Use a credible comparison. Compare the same query cohorts before and after an observable interface change. Where possible, use comparable unaffected markets or journeys as controls, while accounting for seasonality, demand shifts, promotions, device mix, and unrelated ranking changes.
Set the interpretation rules first. Decide which combinations would indicate better user utility, stronger business access, or greater contestability before looking at the result. This reduces the temptation to label any favorable business movement as proof of fairness.

A simple before-and-after chart is rarely enough. Search demand, ranking systems, result features, brand activity, and conversion conditions can all move during the same period. If you do not control for those changes, the DMA becomes a convenient explanation rather than a demonstrated cause.

Your scorecard should also preserve trade-offs instead of averaging them away. If independent providers receive more qualified visits while users take an extra step, business access may have improved while user utility weakened. If users face more steps and independent providers receive fewer direct conversions, the implementation is failing both tests. If one large intermediary captures most displaced clicks, the market may have redistributed attention without becoming meaningfully more contestable.

Diagnose lower clicks and direct bookings before changing SEO

An analyst examines four connected search and conversion layers whose different paths converge on the same weakened outcome signal.

Reported declines in click-through rates and direct bookings are consequential, but neither metric explains its own cause. The same decline can originate at several points in the journey, and each one calls for a different response.

Visibility loss: Impressions, positions, or eligible appearances decline for the affected query cohort. Investigate relevance, technical eligibility, content quality, competitor movement, and result-layout changes before blaming regulation.
SERP interception: Visibility remains broadly stable while CTR falls and a different result type captures attention. Identify whether the click moved to a Google-owned surface, an independent service, or another publisher. Those movements have very different fairness implications.
Handoff friction: The user clicks but must pass through an additional service before reaching the provider. Measure the completion rate at every transition. A new competitive option is not useful to the business if qualified demand repeatedly disappears at the handoff.
On-site conversion loss: Landing sessions remain stable while conversion rate falls. Check page experience, message consistency, availability, offer changes, and measurement integrity. That pattern is less likely to be explained by search-result fairness alone.
Attribution loss: The final conversion still occurs, but the added intermediary changes how the journey is credited. Reconcile search clicks, referral sessions, assisted conversions, and transaction records before declaring that demand vanished.

The destination of a lost click matters as much as the loss itself. If your page loses traffic to an independent service that better satisfies the query, your business performance fell while procedural competition may have improved. If the click moves into a gatekeeper-owned unit, weaker performance may coincide with continued self-preferencing. If the click moves to a dominant intermediary, the result could replace one dependency with another.

Direct bookings need the same care. A lower direct-booking count can reflect lower demand, weaker visibility, an interrupted handoff, an attribution change, or transactions migrating to an intermediary. Report those causes separately. Otherwise, a single metric will mix an SEO problem, a user-experience problem, and a market-structure problem into one number no team can act on.

Act on the layer that actually failed

What search and content teams can change

You cannot optimize away a gatekeeper problem, but you can make your own part of a fragmented journey easier to discover, understand, and measure.

Maintain query-level evidence. Keep a recurring record of high-value result pages, their features, and their click destinations. Interface evidence is essential when traffic moves without an obvious ranking loss.
Preserve destination data. Classify referrals and assisted paths by surface and intermediary. Do not combine direct, organic, comparison-service, and marketplace journeys into a single acquisition bucket.
Reduce post-click uncertainty. Make the landing page complete the promise made in the result. Put the decision-critical information and next action where the visitor can find them without another search.
Keep structured data aligned with visible content. Accurate schema can reduce ambiguity about the entity, offer, page purpose, and relationships represented on the page. It will not reverse a DMA-induced layout change or prove that a market is fair.
Design for both direct and assisted discovery. Give intermediaries and AI-driven answer systems clear, consistent facts while preserving a strong path to the provider’s own page. Measure whether those external surfaces introduce qualified users or merely absorb the relationship.
Report performance and fairness separately. Your executive dashboard should distinguish what happened to your business from what happened to the market. A regulation can hurt one company without reducing competition, or help one company without creating a fair system.

What regulators would need to demonstrate

A credible fairness claim requires more than evidence that Google changed a layout or exposed additional links. Regulators would need to show that independent services can acquire qualified demand, users can still complete tasks at an acceptable level of friction, and challengers can become viable without remaining dependent on the same gatekeeper.

Enforcement also has to change incentives. A fine that leaves the gateway, behavior, and economic advantage intact can become an operating cost rather than a competitive remedy. Structural options, including breaking up a monopoly, address a different layer of the problem than interface rules do. They also carry much larger consequences and require a stronger evidentiary case; they should not be treated as a cosmetic extension of search-result regulation.

The practical decision rule is simple: if a remedy changes presentation but does not reduce dependency, expand viable entry, or improve independent access to demand, it is managing the symptom. If it improves supplier access while adding user friction, it has created a trade-off that must be measured and refined. Calling either outcome an uncomplicated success hides the work still required.

Key takeaways

The DMA’s equal-treatment goal is a rule for gatekeeper conduct, not proof that search outcomes became fair.
User convenience, business performance, procedural neutrality, and market contestability are separate dimensions. A single CTR or satisfaction metric cannot represent all four.
The survey of 5,000 European consumers is a meaningful warning about added friction, but consumer sentiment alone cannot establish whether independent competition improved.
Lower CTR and fewer direct bookings should trigger a journey diagnosis: visibility, SERP interception, handoff friction, on-site conversion, and attribution each require a different response.
A fairer result would let independent services gain qualified demand and become viable without simply shifting dependency from Google to another powerful intermediary.
SEO teams should preserve query-level SERP evidence, classify click destinations, connect discovery to final outcomes, and keep fairness reporting separate from company performance.

Your next move is to choose one commercially important query cohort and map it from result page to completed action. Record who receives each click, how many handoffs the user encounters, and where qualified demand disappears. Repeat that measurement after material interface changes. You will then know whether you are facing an SEO issue, a user-experience issue, a distribution shift, or a gatekeeper problem – and you can stop asking one metric to answer four different questions.

References

Search Engine Land – Is the Digital Markets Act Improving Search Fairness?

March 9, 2026

Google EU Political Ads Compliance: A 2026 Account Workflow

If you manage a Google Ads account, the EU political advertising declaration can look like a routine yes-or-no setting. The real risk sits behind that setting: you can choose the wrong answer, apply the right answer at the wrong scope, or let a future campaign inherit a declaration that no longer fits.

Google required advertisers to confirm whether their active campaigns include EU political ads by March 31, 2026. If you completed the task, you still need a control for new campaigns. If you missed it, your immediate job is to verify the account, submit or correct the declaration where possible, and document what you found.

Treat the declaration as a classification decision

An analyst examines a campaign card on a decision table surrounded by civic, policy, and European geographic symbols.

The declaration applies across active campaigns, including campaigns you believe are obviously commercial. You cannot satisfy the requirement merely by deciding that political advertising is not part of your usual strategy. Google is asking for a recorded campaign status, so silence is not a substitute for selecting an answer.

Start by separating two questions. The first is whether a campaign should be classified as an EU political ad. The second is where you should record that classification in Google Ads. The platform gives you tools for the second question, but a setting does not resolve a genuinely uncertain legal classification.

Review the actual campaign rather than its name or internal purpose. Look at the ads, landing pages, intended audience, geographic reach, sponsor, and subject matter. If those facts leave reasonable uncertainty about whether a campaign is political advertising, route the decision to the person responsible for legal or regulatory compliance. Your marketing team can assemble the evidence, but it should not improvise a legal conclusion just to clear an account notification.

Submitting the Google field addresses the platform’s declaration request. It does not, by itself, prove that the campaign satisfies every legal obligation that may apply to political advertising in the EU. Treat the declaration as one compliance control, not as a complete legal review.

Choose the declaration scope that matches your account

Google provides three ways to record the answer. The right route depends on whether your campaigns share the same classification and whether you have a reliable review step for future launches.

Declaration route	Where you use it	When it fits	Main control risk
Campaign level	Open the individual campaign’s settings and use the EU political ads option	One campaign needs review, or the account contains mixed campaign types	Reviewers may apply inconsistent answers across similar campaigns
Multiple campaigns	Open the Campaigns tab and use the EU political ads option for the selected campaigns	Several reviewed campaigns require the same answer	An incorrect selection can spread the answer to campaigns that were not meant to be included
Account level	Confirm once for existing and new campaigns	The entire account is known not to contain EU political ads and future launches are controlled	A later campaign can inherit the account-level No even when it needs separate treatment

If all existing campaigns are non-political and your organization does not run political advertising, an account-level No is usually the cleanest option. It covers existing and new campaigns, reducing repetitive work. Google also allows that choice to be overridden later.

Do not use account-level No merely because most campaigns are commercial. A mixed account needs campaign-level decisions. The bulk tool is useful when many campaigns have already received the same classification, but it should be the final application step rather than a shortcut around reviewing them.

Build a record you can defend and update

The interface records an answer, but your internal file should explain why that answer was chosen. This matters when another administrator changes the account, an agency takes over, or someone later asks whether a campaign was included in the review.

Create a list of every active campaign in the account. Do not review only the campaigns currently spending the most.
Collect the facts needed for classification: ad creative, landing pages, targeting, geographic reach, sponsor, and subject matter.
Mark each campaign Yes, No, or Unresolved in an internal worksheet or ticket. Unresolved is a temporary review state, not the answer you submit to Google.
Send unresolved classifications to your legal or compliance owner before applying a bulk or account-level declaration. If the answer could create legal exposure, obtain advice appropriate to the campaign and jurisdiction rather than relying on a general checklist.
Select the narrowest Google Ads scope that accurately reflects the reviewed campaigns. Use the account-level option only when one answer genuinely fits the whole account and its launch process.
Record the submission date, account ID, campaigns covered, reviewer, final answer, and basis for the decision. Retain a screenshot or export showing the state you submitted.

This record is not paperwork for its own sake. It lets you distinguish a reasoned decision from an accidental default. It also makes correction faster: you can identify which campaigns were covered without reconstructing the account as it existed when the declaration was made.

Stop future campaigns from inheriting the wrong answer

A secure archive of campaign records connects to a verification gate that checks new campaign tiles and diverts one for review.

The efficiency of an account-level No creates its main weakness. Because the choice applies to new campaigns as well as existing ones, a later campaign can enter the account under an answer selected for an earlier portfolio.

Add the EU political ads decision to your campaign launch approval. The person creating a campaign should not have to interpret the law alone, but they should have to identify whether the campaign needs compliance review.

Require a recorded EU political ads status before campaign activation.
Route every Yes or Unresolved status to the designated compliance owner.
Override the account-level answer when a reviewed campaign requires different treatment.
Recheck the declaration when creative, landing pages, geographic reach, sponsorship, or subject matter changes materially.
Include the setting in account handovers so a new agency or administrator understands the inherited default.

Ownership should be explicit. A paid media operator can maintain the setting, a campaign owner can provide the facts, and a legal or compliance specialist can resolve difficult classifications. If everyone assumes someone else owns the declaration, it becomes an account notification that gets cleared without a defensible decision.

EU political ads declaration FAQ

Does an account-level No cover campaigns created later?

Yes. Google’s account-level confirmation applies to existing and new campaigns. That makes it efficient for an account that does not run EU political ads, but it also means you need a pre-launch check in case the account’s campaign mix changes.

Can you change the declaration after submitting it?

Yes. Google allows the account-level choice to be overridden. Correct a known error promptly, then update your internal record with the new answer, the date, the affected campaigns, and the reason for the change. Do not leave conflicting screenshots or worksheets that make the current decision unclear.

What should you do if you missed March 31, 2026?

Open the account and inspect the current declaration state, campaign settings, and account notifications. If the relevant control remains available, submit an accurate answer after reviewing the campaigns. If a declaration is already present, verify whether it is correct rather than assuming another administrator handled it properly. Escalate a blocked interface through the platform’s support route, and send uncertain legal classifications to qualified counsel or your compliance team.

A missed deadline creates a compliance gap, but it does not tell you by itself what enforcement action has occurred. Verify the account instead of speculating. Your next concrete move is to assign an owner, inventory the active campaigns, and record the correct declaration at the appropriate scope.

References

Search Engine Land — Google contacts advertisers with a mandatory EU political ads deadline

March 6, 2026

Google v. SerpApi: What the Scraping Fight Means for SEO
If your rank tracker, competitive dashboard, or AI-search monitoring workflow depends on a SERP API, the Google-SerpApi dispute is not remote legal theater. It is a data-supply-chain issue: an upstream collection method could affect the coverage, cadence, cost, and reliability of the measurements you use.

That does not mean your tools are about to stop working. SerpApi has asked a court to dismiss Google’s claims, and the competing positions have not been resolved. Your practical job is to identify where scraped Google data enters your operation, separate collection failures from real search changes, and prepare a fallback before either problem reaches a client report or automated decision.

Key takeaways
- A motion to dismiss is not a ruling that SerpApi acted lawfully, and allowing Google’s claims to proceed would not prove that Google is right.
- The central dispute is whether the DMCA can apply when a service accesses public, no-login search pages while overcoming Google’s anti-bot controls.
- A court ruling could influence the risk, availability, and economics of third-party SERP collection, but it will not answer every legal question about scraping.
- SEO and GEO teams should treat this as a vendor-dependency issue now: document data lineage, preserve methodology metadata, define validation checks, and build replacement paths for critical reports.
The dispute turns on access, protection, and reuse

The fact that a search result is visible in a browser does not settle the case. Google alleges that SerpApi evaded bot-detection and crawling controls through rotating bot identities and large networks, then collected and resold material from Search features that included licensed images and real-time data. Those are allegations, not judicial findings.

SerpApi answers that it collects the same public-facing information a person can see without authentication. It says it does not decrypt a protected system or breach a login barrier. It also argues that Google does not own much of the underlying material displayed in its results and is trying to use the Digital Millennium Copyright Act to protect its platform and advertising interests rather than copyrighted works.

That creates three questions that are easy to collapse into one:
- Who owns the material? Google may display text, images, and facts originating elsewhere, but the ownership analysis can differ by element and license.
- What do the technical controls protect? Google’s theory connects its anti-bot systems to protected Search content. SerpApi’s theory is that controls serving platform or advertising interests do not become copyright-protection measures merely because they obstruct automated access.
- What is being done with the collected data? Viewing a public page, collecting it automatically, operating at scale, and reselling the resulting dataset are different activities. A conclusion about one does not automatically resolve the others.
SerpApi invokes hiQ v. LinkedIn and Impression Products v. Lexmark to support its position that technical barriers should not let a platform monopolize public-facing information. Those precedents are part of SerpApi’s argument; they do not predetermine how the court will characterize Google’s systems, the material displayed in Search, or SerpApi’s conduct.

The procedural posture matters just as much. A motion to dismiss generally tests whether pleaded legal claims can go forward. It is not a full trial of disputed facts. If the motion succeeds, you must still read which claims were dismissed and on what grounds. If it fails, Google has cleared a procedural threshold, not won the lawsuit.

Do not mistake the widely repeated $7.06 trillion figure for a judgment, settlement demand, or likely damages award. It is SerpApi’s theoretical calculation of potential penalties under Google’s interpretation of the DMCA. It illustrates how expansive SerpApi believes that interpretation could become; it does not predict the financial outcome.

Each possible outcome has narrower meaning than the headline

The unhelpful way to read this dispute is as a referendum on whether public data is always free to scrape. The useful way is to ask what a particular ruling establishes, which legal claim it addresses, and which operational assumptions it puts under pressure.
- If the motion is granted: the challenged claims may be legally insufficient in their pleaded form. That would support SerpApi’s defense, but it would not create a universal license to scrape any public website for any purpose.
- If the motion is denied: Google’s claims may proceed into later stages. That would not be a finding that every allegation is true or that all automated collection from public pages violates the DMCA.
- If Google ultimately prevails on its anti-circumvention theory: providers using similar collection methods could face greater legal and technical pressure. Customers might experience narrower feature coverage, higher costs, slower collection, provider consolidation, or abrupt service changes.
- If SerpApi ultimately prevails: the result could strengthen the position that access to public, no-login search results cannot be restricted through the DMCA theory Google advances here. Separate questions involving contracts, content rights, licenses, misrepresentation, or other causes of action would still depend on their own facts and law.
The pressure also extends beyond one search platform. Reddit filed claims against SerpApi and others in October 2022, alleging indirect collection through Google Search, concealed identities, and industrial-scale activity. That broader conflict is a warning for data buyers: a provider can face objections from the platform being queried, the owners of material appearing in results, or both.

For planning purposes, classify the case as unresolved upstream risk. Do not describe scraping as definitively lawful because the pages are public. Do not tell stakeholders that all third-party SERP APIs are unlawful because Google filed a complaint. Neither statement follows from the current procedural stage.

Your measurement can fail before the legal question is settled

SEO teams rarely consume scraping infrastructure directly. They see a rank, a feature flag, a competitor count, a screenshot, or an AI-visibility score. That abstraction is convenient until the collection layer changes and the dashboard continues presenting its output as if the underlying observation were stable.

Four failure modes deserve explicit checks:
- Coverage loss: a provider may stop returning a result type, location, device class, language, or page depth. A missing observation can then be misreported as a lost ranking or absent feature.
- Sampling drift: stronger blocking can change which successful requests survive. Your trend line may compare two different samples even though the dashboard label has not changed.
- Latency: retries and collection friction can make a supposedly current result older than expected. This matters when you are investigating a launch, algorithm change, reputation event, or volatile query.
- Provider continuity: legal expense, infrastructure changes, or tighter access controls can alter pricing and service levels even before a final ruling.
The operational rule is simple: separate a market signal from a collector signal. A sudden loss of rankings across one geography may reflect Google Search, but it may also reflect an endpoint, parser, proxy pool, localization setting, or feature-classification change.

Preserve enough metadata to test that distinction. For every observation that can trigger a decision, retain the provider, collection time, requested location, language, device, result type, and methodology version where your agreement permits it. Store raw response evidence or a rendered capture when you are contractually and legally allowed to retain it. Treat an empty response as unknown until the system can distinguish a genuine absence from a failed collection.

For an owned website, Google Search Console can corroborate changes in impressions, clicks, and average position, but it cannot reproduce a live competitive SERP or explain every feature-level observation. A second data vendor may help, although two vendors can share similar collection dependencies. Manual checks on a small, predefined diagnostic query set provide another useful signal, provided they use consistent location, language, device, and personalization conditions.

The same discipline applies to AEO and GEO reporting. If a system derives an AI-search visibility score from Google result features, a missing mention may mean that the brand disappeared, that the feature was not collected, or that the parser stopped recognizing it. Keep the captured answer or result evidence separate from the calculated score. Never let a score of zero stand in for missing evidence.

When a major shift appears, ask three questions before changing content: Did the search experience change? Did the acquisition method change? Did the interpretation layer change? If you cannot answer all three, annotate the report and withhold automated recommendations until you have corroboration.

Audit your SERP-data dependency in six steps
1. Build a dependency register. List every rank tracker, SERP API, competitive-intelligence platform, AI-visibility product, internal script, and agency feed that observes Google results. Record the provider, endpoint, markets, device profiles, collection cadence, retention period, and downstream reports or automations.
2. Mark decisions, not just systems. Identify what happens when each field changes. A number viewed by an analyst is lower risk than a field that changes bids, rewrites briefs, triggers client alerts, evaluates staff, or publishes customer-facing claims. Give the highest scrutiny to inputs that cause action without human review.
3. Ask vendors method-specific questions. Find out which outputs depend on automated access to public Google pages; which use official or licensed interfaces; how the vendor distinguishes blocked requests from absent results; whether methodology changes are disclosed; what incident notices you receive; and how quickly you can export historical data. Request written answers for critical services.
4. Design a replacement by use case. Use first-party performance data for owned-site outcomes where it fits. For competitive rankings, define a smaller priority query set that can be checked through another method. For feature monitoring, preserve time-stamped evidence. For AI-search tracking, keep prompt, response, model or interface, location conditions, and scoring logic separable so one unavailable feed does not erase the whole record.
5. Add a collection circuit breaker. Set the reporting system to flag abrupt changes in response completeness, feature frequency, geography coverage, timestamps, or error rates. When the check fires, label the period as potentially incomplete, pause automated recommendations, and notify the people who consume the affected metric.
6. Escalate the right legal questions. If your organization directly operates scraping infrastructure, bypasses technical restrictions, resells SERP data, distributes licensed images or real-time content, or makes contractual promises about uninterrupted access, obtain advice from counsel familiar with copyright, the DMCA, data licensing, and relevant contracts. A general blog cannot determine the exposure of a particular implementation.
Your vendor review should also cover commercial concentration. Switching from one collector to another is not a complete fallback if both depend on materially similar access methods. Ask what can be replaced with first-party data, what can tolerate reduced frequency, what requires independent verification, and what has no realistic substitute. The last category needs an explicit owner and a documented decision about acceptable downtime.

Do not wait for a final judgment to run the test. Pick one business-critical SEO or AI-visibility report this week. Trace every external field to its acquisition method, mark the fields that cannot be independently verified, and simulate one reporting cycle with the primary feed unavailable. You will learn more from that exercise than from trying to predict the court.

When the next ruling arrives, read the claims and procedural grounds before changing policy. Until then, keep public visibility, technical access, content ownership, and commercial reuse as separate questions. That distinction will make both your legal review and your search measurement substantially more reliable.

References
- Search Engine Land — SerpApi files motion to dismiss Google’s scraping lawsuit
February 23, 2026

Google Search Antitrust Appeal: An SEO Readiness Plan

If you manage SEO or AI visibility, don’t treat Google’s antitrust appeal as an algorithm update. Nothing in the current record gives you a reason to rewrite pages, change schema, or explain a rankings dip.

The practical issue is distribution: which search engine or AI app people encounter first on their browser or device. That can redirect discovery and traffic even when every ranking system stays exactly the same. Your job now is to establish a clean baseline, define the events that would justify action, and avoid making expensive changes based on legal headlines alone.

What the appeal changes – and what it does not

There are two separate questions in this case: whether Google unlawfully maintained a monopoly and what the court should do about it. U.S. District Judge Amit Mehta found in August 2024 that Google illegally maintained its search monopoly through default-placement agreements. The current government appeal challenges the remedy imposed after that finding.

Following a remedies trial in 2025, the judge declined to order two of the government’s most consequential proposals: separating Chrome from Google and completely prohibiting payments for default search placement. The resulting remedy instead requires Google to rebid default search and AI app agreements annually.

That distinction matters. Annual rebidding creates a recurring commercial decision point, but it does not prevent Google from paying for placement or guarantee that a partner will select another provider. The Department of Justice and participating states are appealing because they want the appellate court to revisit whether that remedy is strong enough to restore competition.

The initial appeal filings did not disclose the government’s complete legal argument. Chrome and Google’s default arrangement with Apple are expected to be central issues, but an expected point of dispute is not an ordered remedy. The U.S. Court of Appeals for the D.C. Circuit must still review the challenge.

Confirmed: The government is appealing the remedies decision.
Confirmed: The trial court did not order a Chrome breakup or a complete ban on default-placement payments.
Confirmed: The remedy requires annual rebidding of covered default search and AI app agreements.
Unresolved: Whether the appellate court will preserve, strengthen, or require reconsideration of that remedy.
Not indicated: An immediate change to Google’s ranking systems, Search Console, structured-data support, or search advertising platform.

The appeal concerns access to users, not page rankings

Three unbranded devices send different paths toward the same unchanged arrangement of webpage cards.

Google’s default agreements matter because a preselected service captures user attention before a person actively compares alternatives. Google has spent more than $20 billion per year on default arrangements with companies including Apple and Samsung. The trial court treated those agreements as a mechanism through which Google protected its search position.

For an SEO team, this creates an important diagnostic rule: a change in traffic is not automatically a change in rankings. If a browser or device starts sending more users to another engine, your Google positions could remain stable while Google organic sessions decline. A site could also gain visits from a competing engine without improving there, simply because more people were directed to it.

Ranking change: Your relative position inside a search engine changes.
Distribution change: The browser, device, or app sends a different share of people to each discovery service.
Behavior change: People use search, an AI answer interface, or direct navigation differently even though defaults and rankings remain stable.

Those mechanisms require different responses. A ranking loss calls for query, page, competitor, and technical analysis. A distribution shift calls for engine, browser, device, and referral analysis. A behavior shift calls for journey and conversion analysis. Combining all three under a label such as “organic volatility” hides the decision you need to make.

The inclusion of AI app agreements in the remedy makes the same distinction relevant to generative discovery. An AI service’s availability as a default or integrated option can affect how often people use it, but that does not establish which brands it will cite or recommend. Track access and visibility separately: referrals show whether the service sends visits, while prompt-level checks help you notice whether your brand appears in its answers.

Critics argue that the remedy leaves the original competitive mechanism largely intact. Yelp’s public-policy team has said that continuing to permit default-placement payments is unlikely to restore competition, while also warning that Google’s search indexing and ranking power could extend into generative AI. That is an interested party’s position, not a prediction of what the appellate court will order, but it identifies the commercial link marketers should watch.

Plan for three outcomes without betting on any of them

A useful contingency plan connects each legal outcome to an observable business signal. It does not assign false probabilities or move budgets before the signal appears.

Planning scenario	What could change	What you should do
The annual-rebidding remedy remains	Default placements face recurring negotiation, but payments and continued Google placement remain possible.	Watch contract renewals and measured traffic by engine, browser, and device. Do not assume each rebid will produce a new default.
Default-payment restrictions become stricter	Search access could become more contestable among providers, creating a distribution shift without a Google ranking change.	Wait for persistent audience and conversion movement before reallocating effort. Evaluate each engine by qualified outcomes, not raw visit share.
Chrome separation returns as a remedy	Browser ownership and search distribution could be separated, although the implementation details would determine the real effect.	Model Chrome traffic independently, but do not assume Chrome users would automatically leave Google Search. Reforecast only when product or default behavior is known.

The table is a trigger map, not a forecast. A court decision may also require more proceedings before users see any product change. Keep legal milestones, implementation announcements, and actual audience data on separate lines in your reporting. That prevents a possible remedy from being presented internally as an accomplished market shift.

A readiness plan for SEO and AI discovery teams

A small team monitors abstract traffic signals around a table with three parallel pathway models in a modern operations room.

You can prepare without guessing how the appeal will end. The useful work is measurement and portability: knowing where discovery comes from and making your content understandable outside one distribution channel.

Save a pre-change acquisition baseline. Record organic sessions, qualified actions, conversions, and revenue by search engine. Add browser, device type, geography, and landing page where your data volume and privacy controls permit. Preserve the reporting definition so a later comparison does not mix a market shift with a tracking change.
Separate branded from non-branded discovery. A rise in direct brand demand and a rise in generic search visibility are different gains. Use query data where it is available, and label traffic that cannot be classified instead of forcing it into a confident category.
Pair Google data with cross-channel evidence. Search Console is essential for understanding Google impressions, clicks, queries, and pages, but it cannot describe another engine’s audience. Use analytics, server logs, and the equivalent webmaster data offered by other engines to complete the view.
Create a distribution-change alert. Flag an engine, browser, or device shift only when it exceeds your normal variation and persists beyond one reporting interval. Then check tracking releases, consent behavior, campaigns, seasonality, rankings, and site incidents before connecting it to the antitrust case.
Measure AI discovery as its own pathway. Track identifiable AI referrals, the landing pages they reach, and the actions those visitors complete. Maintain a stable set of high-intent prompts for visibility checks, but label the results as sampled observations rather than market-wide usage data.
Make important information portable. Keep key facts in crawlable page content, use descriptive headings, identify the organization and author clearly, and connect claims to supporting evidence. Apply relevant JSON-LD only when it matches visible content. Schema can reduce ambiguity for machines; it does not guarantee a ranking, citation, or AI recommendation.
Define response thresholds before pressure arrives. Write down what would justify a technical investigation, a content experiment, or a budget change. For example, a court headline alone triggers monitoring; a confirmed product-default change triggers a forecast update; a persistent shift in qualified conversions triggers channel reallocation analysis.
Route contract questions to counsel. If your company operates a browser, device, search service, or AI app covered by distribution agreements, the language of a final order could affect legal and commercial obligations. Marketing analysis is not a substitute for reviewing those agreements with qualified legal counsel.

Do not respond by cloning content for every search engine or adding unsupported schema in the hope that more markup creates broader visibility. Maintain one authoritative version of each page, keep structured data consistent with it, and investigate material engine-specific differences only when measurement shows a real gap.

Key takeaways

The government is appealing the strength of the Google Search remedy; this is not evidence of a Google ranking update.
The current remedy allows default-placement payments to continue but requires covered search and AI app agreements to be rebid annually.
A stricter remedy could change which service users encounter first, causing traffic movement without corresponding ranking movement.
Chrome separation and tighter limits on Google’s Apple agreement are potential areas of dispute, not current requirements.
Your best preparation is a stable cross-engine baseline, browser and device segmentation, independent AI visibility measurement, and trigger-based decision rules.

Start by preserving your acquisition baseline and assigning one owner to connect court developments with verified product changes. When the next headline arrives, ask one question before touching content or budget: what changed for users in the product? If the answer is “nothing yet,” keep measuring.

References

Search Engine Land – DOJ, states appeal Google Search antitrust remedies ruling

February 4, 2026

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 layer	What could be shared or syndicated	What it means operationally
Web index data	URLs in Google’s index, a DocID-to-URL map, and metadata such as crawl frequency	A 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 data	Search logs used by Glue and RankEmbed, including detailed interaction information	A recipient would gain potentially valuable signals, but would also need controls for authorized use, privacy, retention, security, and downstream access.
Core search syndication	Google’s core results and search features for qualifying competitors for five years	A third-party surface could display Google-derived results without independently reproducing the same index and ranking stack.
Ad syndication	Google search ads under court-constrained commercial terms, with query and pricing information involved in operating the relationship	A 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.

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.
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.
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.
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.
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.
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.
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

January 22, 2026

Ad Approval Is Not Legal Clearance: A Marketer’s Checklist

Your campaign has passed Google or Meta review, the launch date is set, and someone has saved the approval notice. You can run the ad. You cannot conclude that the ad, offer, targeting, or data use complies with every law that may apply.

Treat platform approval as permission to use a platform under its rules, not as a legal opinion. That distinction should change who reviews a campaign, what evidence you preserve, and which changes send a live ad back through review.

Platform approval answers a narrower question

An ad platform reviews submissions for compliance with its advertising policies, account rules, technical requirements, and enforcement systems. Those policies can overlap with legal obligations, but the two systems have different purposes.

Whatever combination of automated and manual checks a platform uses, its approval is not a warranty, an indemnity, or advice from your lawyer. Passing review means the platform allowed that submission to run at that point; ad approval is not legal protection.

The distinction works in both directions. A platform may prohibit material that the law would allow because it wants a stricter environment. A platform’s approval also cannot establish that your evidence supports every claim, that you have all necessary rights, or that the campaign complies in every place where it appears.

Decision layer	Question it should answer	Typical owner
Platform policy	May this creative, destination, account, and targeting setup run on this platform?	Paid media or campaign operations
Legal compliance	Are the message, offer, disclosures, rights, targeting, and data practices lawful in the applicable context?	Legal or compliance
Commercial and reputational risk	Is the campaign accurate, fair, consistent with the product, and acceptable for the brand?	Product, brand, and business leadership

A small team may have one person coordinating all three layers. That is workable only if the decisions remain separate. A single checkbox labeled approved conceals which question was answered, by whom, and for which campaign version.

Build a two-gate approval workflow before launch

An overhead view shows platform, legal, privacy, and marketing reviewers examining campaign materials at two separate checkpoints.

Do not wait for a platform decision and then ask whether legal review is necessary. By that point, the launch date and media budget can make a careful review feel like an obstacle. Put the platform gate and the legal gate beside each other in the campaign plan.

Freeze a review version. Give reviewers the exact creative, copy, landing page, offer terms, audience, locations, schedule, tracking setup, and data sources that you intend to launch. A headline without its destination or targeting context is not a complete submission.
Run the platform-policy gate. Check the platform’s current rules for the account, product category, creative format, destination, and targeting method. Record restrictions or exceptions rather than reducing the result to pass or fail.
Run the legal-compliance gate. Test claims, disclosures, pricing, rights, endorsements, targeting, and data practices. Identify the locations and audiences in scope. Escalate questions that depend on applicable law to qualified counsel before launch.
Attach support to every material claim. Preserve the evidence that existed when the decision was made. The evidence should match the wording, scope, audience, and conditions of the claim rather than merely relate to the same product.
Record two sign-offs. Platform clearance and legal or compliance clearance should have separate owners, dates, scopes, conditions, and campaign version numbers.
Inspect the live experience. Check the rendered ad, destination, disclosures, form fields, pricing, and tracking after launch. Dynamic assembly, device layouts, and landing-page publishing can produce an experience that differs from the reviewed files.

Your sign-off record should identify the campaign and version, platform and account, audience and geography, reviewed landing-page URL, named reviewers, decision dates, restrictions, unresolved issues, and the event that will trigger another review. If evidence or permission expires, record that date too.

For dynamic or automatically assembled advertising, reviewing one mockup is not enough. Review the combination rules, prohibited pairings, data inputs, and a representative set of rendered ads. Capture examples from the live campaign so you can connect an actual impression to the rule set that produced it.

Test the risks a platform cannot clear for you

Legal review should not be a vague request to make the ad safe. Give the reviewer defined questions and the material needed to answer them.

Claims and substantiation: List each factual, performance, savings, outcome, comparative, testimonial, and implied claim. For each one, record the likely audience takeaway, supporting evidence, material limitations, evidence owner, and valid-through date. Evidence for a narrow result does not automatically support broader wording.
Disclosures and overall impression: Check whether a viewer can understand qualifications, limitations, sponsorship, or other material information in the ad’s real format. A disclosure that appears only after a click may not correct the impression created before the click. Small print is also a poor fix for a headline that points in the opposite direction.
Price and offer terms: Verify the displayed price, included items, eligibility conditions, fees, duration, renewal terms, deadlines, inventory limitations, and geographic restrictions. The creative and landing page must describe the same offer.
Audience and targeting: Document who can receive the ad, why that audience was selected, and whether age, location, inferred traits, uploaded lists, exclusions, or sensitive information create additional obligations. Platform availability of a targeting feature does not decide whether your use of it is lawful.
Data collection and sharing: Map the information collected after an impression or click, its source, intended use, recipients, retention, and the permission or other basis relied on. Include pixels, forms, audience uploads, matching, measurement partners, and downstream systems rather than reviewing only the visible page.
Intellectual-property and publicity rights: Confirm that you own or have permission to use the copy, images, video, music, trademarks, customer material, testimonials, and likenesses in every version. A platform’s technical ability to accept an asset does not establish those rights.
Jurisdiction and product category: Ask which requirements apply based on the advertiser, audience, product, transaction, and data flow. New locations, languages, or high-consequence product categories deserve a fresh decision, not a copy of the previous approval.

Use an explicit escalation rule. Legal or compliance review should occur before launch when a campaign makes a material outcome claim, uses a testimonial or comparison, depends on a disclosure, presents a complex offer, collects or shares audience data, uses third-party rights, targets a legally sensitive audience, enters a new jurisdiction, or promotes a regulated or high-consequence product.

If the answer turns on a particular law, contract, regulator, or factual dispute, general marketing guidance is not enough. Send the complete campaign packet to counsel qualified for the relevant jurisdiction and subject matter. The safe alternative to guessing is to narrow or pause the campaign until the question is resolved.

Re-review material changes and preserve the evidence

A campaign manager compares two altered ad versions beside organized folders, approval tokens, and a locked evidence archive.

Approval belongs to a defined version and context. It should not travel automatically to a new headline, landing page, price, audience, location, data flow, or dynamically generated variation.

Send a campaign back through the relevant gates when any of these changes:

The wording, visual, testimonial, comparison, or implied product outcome.
The landing page, form, checkout flow, disclosure, price, eligibility rule, renewal condition, or offer deadline.
The audience, targeting method, exclusion, geography, language, schedule, or placement context.
The source, collection, matching, sharing, measurement, or retention of user data.
The product facts or supporting evidence, including evidence that becomes outdated, contradicted, withdrawn, or narrower than the live claim.
The rules used to generate or personalize creative combinations.
The risk picture after a complaint, rights claim, legal demand, platform enforcement action, or regulator inquiry.

Do not interpret a later platform disapproval as proof that a law was broken. Identify the exact policy and affected asset. Then decide separately whether the same facts raise a legal issue. The reverse remains true as well: continued platform approval does not resolve a complaint or legal concern.

When a credible concern appears, pause the affected ads if continued delivery could compound the exposure. Preserve the exact creative, destination, targeting settings, audience logic, approval notices, change history, evidence, and live captures before editing anything. Removing an ad may reduce ongoing risk; deleting the record can make it harder for counsel to determine what ran and how far the issue spread.

Next, scope the problem. Identify every affected version, platform, account, audience, location, time period, and destination. Route legal demands, regulator contact, uncertain jurisdictional questions, and potentially material exposure to qualified counsel. Document the reason for any correction and the conditions that must be met before restart.

Keep the final campaign packet after the media stops. It should contain the reviewed assets, evidence, approvals, exceptions, live captures, material changes, complaints, corrective actions, and restart or retirement decision. An approval screenshot can support that history, but it should never be the entire history.

Key takeaways

Platform approval answers whether an ad may run under platform rules; it does not provide legal clearance.
Use separate platform-policy and legal-compliance gates, even if one person coordinates both.
Review the complete campaign context: creative, destination, offer, audience, geography, rights, tracking, and data use.
Attach evidence to the exact claim it supports and record limitations, ownership, and expiry.
Treat material campaign changes, credible complaints, and new jurisdictions as new review events.
Preserve the version that actually ran before correcting or removing it, and involve qualified counsel when the issue depends on applicable law or could create material exposure.

Before your next campaign launches, replace the single approved field in your workflow with two named decisions and a versioned evidence packet. That small structural change makes it much harder to mistake media access for legal protection.

References

Search Engine Land – Why ad approval is not legal protection

December 23, 2025

Google-SerpApi Scraping Lawsuit: An SEO Team Playbook

Your rank tracker can keep returning data while the legal and commercial assumptions underneath it have already become a business risk. If your dashboards, client reports, competitive research, or AI visibility monitoring depend on SerpApi or another reseller of Google results, you need an exposure map before a court outcome, not a prediction of who will win.

Google’s claims remain contested, and filing a lawsuit does not prove them. But the dispute targets the collection method, the content being collected, and the resale of that content. Those issues can affect service continuity, field coverage, pricing, and historical comparability long before they establish a legal rule.

What the lawsuit does and does not establish

Google is not merely objecting to someone looking at a public results page. It alleges that SerpApi evaded security measures and crawling controls to collect and resell search-result content. More specifically, Google accuses SerpApi of:

Circumventing technical protections and standard crawling controls.
Disregarding website directives intended to limit content access.
Using cloaking, rotating bot identities, and large bot networks to avoid detection.
Taking licensed material from search features, including images and real-time data, and selling access to it.

Those are Google’s allegations, not findings of fact. SerpApi denies wrongdoing, argues that public search data should remain accessible, and has invoked the First Amendment in defending its position. It also warns that restrictions of this kind could damage an open web.

Do not turn that disagreement into either of two unsupported conclusions: that every form of SERP collection is unlawful, or that anything visible in a browser is automatically unrestricted. The real questions are more specific:

How was the data accessed?
Which technical controls or publisher directives applied?
Does the result contain material licensed from another provider?
What exactly is being stored, transformed, displayed, and resold?
Which party assumes the risk if access is restricted?

This distinction matters when you evaluate a supplier. A provider’s broad statement that its data is public does not answer a narrower allegation about evading controls or redistributing licensed content. You need enough provenance to understand the service you are buying, even if the provider cannot disclose its entire technical system.

Audit your SERP dependency before the data changes

Analysts trace branching data connections from a generic search-results source to rank tracking, reports, research, storage, alerts, and AI monitoring tools.

Start with operational exposure rather than courtroom speculation. The goal is to identify what would break if a provider removed fields, reduced request volume, changed its collection method, raised prices, or stopped serving a particular Google feature.

Find direct and indirect dependencies. Search your scripts, workflow automations, data warehouse jobs, dashboards, reporting templates, and vendor integrations for SerpApi and other SERP data services. A platform can expose search data without making its upstream supplier obvious, so ask embedded vendors as well.
Separate the data classes. Record whether each workflow uses organic links, snippets, images, knowledge features, shopping information, local results, or real-time features. The lawsuit’s emphasis on allegedly licensed feature content makes a generic label such as “Google data” too vague for risk review.
Map every downstream commitment. Note which datasets feed internal research, executive reporting, client deliverables, automated alerts, product features, or contractual service levels. A low-volume feed can still be critical if a customer-facing report depends on it.
Capture a baseline. Preserve your field dictionary, query settings, market and device assumptions, freshness expectations, failure rate, and representative outputs, subject to your retention rights. Without a baseline, a provider-side methodology change can look like a ranking or visibility change.
Assign a fallback. Name the replacement method, the owner who can activate it, and the reporting limitation it introduces. “Find another API” is not a fallback plan unless you have tested how its definitions and coverage differ.

Classify the dependency by the consequence of failure, not by the number of API calls:

Dependency	Practical response	Important limitation
Ad hoc research	Save query definitions and identify a manual sampling method.	A small manual sample may not reproduce the provider’s location, device, or personalization assumptions.
Recurring internal dashboard	Test a second data path and annotate any supplier or methodology change.	Two providers may label positions and search features differently.
Client or executive reporting	Document the dependency, establish a change-notice process, and prepare a reporting caveat.	Combining incompatible series can create a false trend.
Customer-facing product feature	Review the contract, test graceful degradation, and define who can activate the contingency.	A legal remedy after disruption will not restore immediate availability.

For information about your own site’s Google performance, a first-party source such as Google Search Console may cover part of the need. It does not reproduce a complete results page or provide a like-for-like replacement for competitive SERP monitoring. Treat it as one layer of a fallback, not a universal substitute.

When you test an alternative, overlap the old and new methods before combining their data. Compare query interpretation, country and location handling, device type, result-feature definitions, missing fields, freshness, and error behavior. If the series are not comparable, start a new baseline and mark the break instead of presenting it as an SEO movement.

Put collection provenance into vendor review

Two reviewers inspect a transparent data chain linking generic web collection, a vendor server, and an analytics workstation beside blank compliance documents.

Do not ask only, “Is this legal?” That invites a sales assurance rather than a useful explanation. Ask questions that expose the collection path, rights assumptions, and continuity plan:

What is the origin of each data class? Ask the provider to distinguish directly collected Google output, third-party licensed data, transformed data, estimates, and information obtained through another supplier.
How does the service respond to access restrictions? You do not need instructions for evading controls. You do need to know whether the provider stops, substitutes data, reduces coverage, or changes methods when access is limited.
Which fields may contain third-party licensed material? Images and real-time features deserve separate treatment from ordinary organic URLs because Google has specifically raised licensed-content allegations.
What changes first under pressure? Ask whether a restriction would affect certain countries, devices, result types, request volumes, freshness levels, or historical exports before the entire service failed.
How will customers be notified? Request the provider’s process for communicating collection-method changes, field removals, legal restrictions, and material coverage loss.
Can you export your history and metadata? Historical values without query settings, timestamps, markets, device assumptions, and field definitions may be impossible to interpret after migration.
How does the contract allocate risk? Have qualified counsel review warranties, indemnities, termination rights, notice obligations, permitted uses, and retention terms in the context of your actual implementation.

A vendor contract cannot guarantee uninterrupted access to an external platform. It can clarify responsibility, but you still need a technical fallback. Keep those two workstreams separate: counsel assesses legal exposure, while your data and SEO teams protect continuity and measurement quality.

Answers that should slow your decision

“The data is public.” This does not explain whether technical controls were bypassed or whether some fields contain licensed material.
“Everyone collects search results.” Industry prevalence does not tell you how this provider operates or what rights attach to each data class.
“Customers have never had a problem.” That does not establish a continuity plan, a notification process, or a contractual remedy.
“Our method is completely legal.” An unqualified conclusion is less useful than a written explanation of the access model, relevant rights, and scope of the assurance.
“We cannot discuss any aspect of collection.” A provider may protect proprietary details, but complete opacity prevents you from performing even basic supplier-risk review.

If your own collection code, or a method disclosed by a supplier, appears to bypass access controls or conceal bot identity, do not expand that deployment until qualified legal counsel has assessed the actual facts. This operational checklist cannot determine whether a particular system is lawful.

Protect AI visibility and SEO reporting without changing strategy

The provenance question extends beyond a direct SerpApi account. Reddit has separately accused SerpApi, Perplexity, Oxylabs, and AWMProxy of participating in an indirect scraping chain involving Google results. Reddit says it planted a trap item visible only to Google’s crawler that later appeared in Perplexity results. SerpApi denies the allegations.

That claim does not prove how every named party obtained every item. It does illustrate why data lineage matters: your dashboard may receive information through several suppliers, and the company selling you the final metric may not be the company collecting the underlying result.

For an AI visibility, AEO, or GEO platform, document the measurement chain with the same care you would apply to a rank tracker:

Label whether each metric comes from a directly observed model response, a Google result, a third-party dataset, or an inferred score.
Retain the query or prompt, timestamp, market, device, search feature, and model or product identifier when those fields are available.
Require a methodology changelog so a collection change cannot quietly become an apparent visibility gain or loss.
Keep observed facts, such as whether a brand appeared, separate from proprietary scores or estimates.
Rebaseline a metric when its supplier, collection path, feature definition, or model surface changes materially.
Do not use Google SERP coverage as an unlabeled substitute for direct measurement of an AI system. Search visibility and model-response visibility answer different questions.

The lawsuit itself is not evidence of a Google ranking update, a change to structured-data processing, or a new standard for earning AI citations. Do not rewrite content, remove JSON-LD, or change your internal-link strategy because litigation was filed. Change the governance around the data used to judge those activities.

Predefine the events that will trigger action: a supplier notice, unexplained field loss, a sustained change in failure behavior, a restriction on a result type, a material pricing change, or a change in collection methodology. Then name who decides whether to continue, degrade the report, activate a fallback, or start a new measurement baseline. That prevents a technical incident from turning into an improvised legal and client-communication decision.

Key takeaways

Google’s claims against SerpApi are contested allegations, not a judgment that all SERP data collection is unlawful.
Your immediate exposure is operational as well as legal: access, fields, prices, and historical comparability can change before the case is resolved.
Audit direct APIs and hidden upstream suppliers across dashboards, reports, automations, and AI visibility tools.
Ask how each data class was obtained, which rights apply, what degrades under restriction, and how methodology changes are disclosed.
Use overlapping tests and explicit baseline breaks when changing providers; otherwise a measurement change can masquerade as an SEO trend.
Keep your content and schema strategy tied to search performance evidence. The lawsuit calls for stronger data governance, not reactive optimization changes.

Your next move is concrete: inventory every workflow that depends on full Google results, classify its business impact, and send the seven provenance questions to each supplier. You do not need to predict the verdict to make your measurement stack less fragile.

References

CrushPress.AI – Google’s Legal Battle: SerpApi Accused of Unlawful Data Scraping

December 19, 2025

AI Search Visibility Without Giving Up Content Control

You want AI systems to recognize and cite your expertise, but you don’t want a generated answer to replace the page, dataset, or original work that paid for it. A blanket allow-or-block decision cannot resolve that conflict.

The workable approach is to decide separately what should be discoverable, available for live answers, eligible for model training, or kept behind real access controls. Connect those decisions to business value and rights status before anyone edits a crawler directive.

Stop treating crawl access as one permission

Traditional search indexing, result previews, live retrieval for an AI answer, and model training are different uses. A platform may offer separate controls for some of them, combine others, or provide no control that matches the choice you actually want to make.

Google-Extended shows why the distinction matters. It can prevent content from being used for Gemini training without preventing live website information from contributing to AI-generated answers. Content already indexed by Google may also remain eligible to appear in AI Overviews. Blocking training, therefore, is not the same as blocking answer generation.

The European Commission’s antitrust investigation puts this lack of choice at the center of the dispute: publishers argue that they cannot meaningfully reject generative use without jeopardizing search visibility. The investigation does not settle what is lawful for your content, but it does expose the strategic mistake of treating search inclusion as consent to every downstream use.

For every important group of URLs, answer four separate questions:

Should an ordinary search crawler be allowed to index this content?
Should a search result be allowed to display a preview or snippet?
Do you want an AI system to retrieve this page when constructing a live answer?
Do you want the content used to train or improve a model?

Do not assume that one directive answers all four questions. Write down the desired outcome first, and then identify whether each platform provides a documented control for it.

A robots.txt rule is also not a security boundary. It communicates a preference to crawlers that honor it; it does not make public material confidential or prevent every form of copying. If disclosure of a dataset, licensed report, client deliverable, or proprietary method would cause serious commercial or legal harm, protect it with authentication or another genuine access control. If ownership or licensing terms are unclear, have intellectual-property counsel review them before changing access or reuse terms.

Build a rights-to-visibility matrix before changing directives

Hands arrange different content assets beside separate open, limited, and locked access mechanisms on a planning table.

Make decisions at the URL-family level rather than applying one sitewide rule. A public glossary, a product page, an original investigation, and a licensed database do not carry the same discovery value or substitution risk.

Decision factor	What to record	How it should affect your posture
Business role	Discovery, authority building, conversion, support, or paid deliverable	Discovery content usually benefits from broader access; a paid deliverable needs a stronger boundary
Rights status	Owned, licensed, contributor-supplied, user-supplied, or uncertain	Uncertain or restricted rights require review before you authorize new uses
Substitution risk	Whether a generated answer could satisfy the need without a visit	High-risk pages may need a useful public summary with the full asset kept under access control
Visibility dependency	Search impressions, qualified visits, leads, sales, or assisted conversions	Do not restrict a high-dependency URL group without a baseline and rollback plan
Distinctive value	Original data, reporting, methodology, tools, templates, or expert analysis	The harder the asset is to replace, the more deliberate its public surface should be
Available controls	Crawler, directive, affected product, documented behavior, and owner	Implement only controls that match the intended use closely enough to justify the tradeoff

Turn that matrix into an implementable policy:

Group URLs by template and business function. Start with categories such as public reference content, commercial pages, original editorial work, licensed material, and authenticated assets.
Assign a default posture to each group: open for discovery, public but bounded, restricted, or licensed for specific uses.
Record which team owns the decision. SEO can explain visibility consequences, but it should not silently decide rights questions for editorial, product, or legal teams.
Inventory the current robots.txt rules, page-level directives, authentication boundaries, and contractual restrictions before changing anything.
For each crawler instruction, record the exact crawler and product behavior it is meant to affect. Do not infer behavior from the directive’s name.
Apply the first change to a non-critical URL family. Preserve the previous configuration, capture the baseline, and define the condition that would trigger a rollback.

The same caution applies to noai, nopreview, and similar emerging conventions. A label does not tell you which systems honor it, whether it affects training or live retrieval, or whether it changes ordinary search eligibility. Platform-specific documentation has to answer those questions.

Make the public layer easy to cite and hard to confuse

Protecting high-value material does not require making your whole brand invisible. A stronger architecture separates a public reference layer from the asset that contains the complete commercial value.

Build a useful public reference layer

The public page must contain enough substance to deserve selection. A vague teaser gives an answer engine little reason to cite you, while publishing the entire asset may let the generated response replace you.

Put the core answer in fully rendered HTML. Googlebot can process JavaScript well, but other AI crawlers may not render a JavaScript-dependent page reliably.
Use descriptive headings and answer one recognizable question directly under the relevant heading. Follow the short answer with scope, exceptions, evidence, and the next action.
Name your organization, authors, products, and subject entities consistently. Make authorship, expertise, editorial responsibility, and update history visible rather than leaving authority to be inferred.
Add structured data that agrees with the visible content. Appropriate schema, complete metadata, and meaningful image alt text can help machines connect the page to the correct entities, but markup does not grant a license or compel an AI system to cite you.
Show provenance for consequential claims. Identify who produced original data, explain the method at a useful level, state important limitations, and distinguish an observed fact from your interpretation.
Give the reader a reason to continue beyond the extracted answer: an interactive tool, complete dataset, implementation workflow, downloadable resource, consultation path, or transaction that the summary cannot reproduce.

Generic explanations are especially vulnerable to substitution because the answer contains little that belongs distinctly to your entity. The public layer should carry something attributable: a clear framework, original evidence, a named expert’s analysis, a transparent method, or a maintained record of change.

Keep the irreplaceable asset behind a real boundary

Keep full proprietary datasets, premium templates, licensed archives, and account-specific outputs behind authentication when public exposure is not an acceptable cost of discovery.
Publish a useful summary only if you are comfortable with that summary being publicly accessible and potentially reused.
State ownership and permitted uses in clear terms, and provide a licensing or permissions contact for organizations that want broader access.
Do not publish confidential material and rely on a bot instruction to protect it. Remove it from public delivery or require authorized access.

This creates a deliberate exchange: machines can understand what you know and why your entity is relevant, while the complete experience or asset still requires a relationship with you.

Measure whether visibility creates value or merely extraction

A central content repository sends a controlled stream toward a search beacon while a valve limits a larger extraction pipe.

Organic sessions alone no longer describe search performance. Many AI interactions end without a click, so referral traffic cannot capture every useful mention or every instance in which your material satisfies the user elsewhere.

Some publishers have reported traffic declines of 20% to 50% on informational queries. That range is not a forecast for your site. It is a warning that rankings can remain visible while the economic value of the result changes.

Capture a baseline before changing access controls, then monitor five layers:

Answer visibility: Use a fixed set of important prompts and record whether your brand, product, expert, or content appears. Keep the prompt wording stable enough to compare observations.
Attribution quality: Record whether the answer names you, links to the correct page, represents the claim accurately, and distinguishes you from similarly named entities.
Discovery: Track ordinary search impressions, clicks, AI referrals that can be identified, landing pages, and changes by URL family.
Business value: Measure qualified conversions, assisted conversions, sales conversations, subscriptions, branded search, and other downstream outcomes that matter to the page’s assigned role.
Exposure: Review server logs for crawler activity and document cases where protected or distinctive material appears elsewhere without the attribution or use you expected.

Interpret combinations of signals instead of chasing a single metric:

If AI mentions rise and qualified conversions also rise, the public layer is probably supporting discovery even when direct clicks are limited.
If mentions rise but links and downstream value do not, inspect whether the answer reproduces too much of the page, the citation is missing, or the page lacks a compelling next step. Blocking should not be your automatic first response.
If visibility falls after a directive change, compare crawler logs, indexing, and the affected URL family against the recorded intent. Roll back when the lost discovery is more valuable than the use you prevented.
If an AI answer misstates your position, improve the page’s explicit definitions, entity relationships, evidence, and limitations. Preserve examples of the error so you can determine whether the problem changed.
If licensed, confidential, or access-controlled material is reproduced, preserve the output, URL, date, relevant access logs, and configuration. Escalate to the platform and qualified counsel rather than trying to settle the rights question through SEO settings alone.

Keep a change log with the affected URL family, intended behavior, implementation owner, prior configuration, observed result, and rollback condition. Without that record, a later traffic change will tempt the team to assign causation to whichever AI event is most visible.

Key takeaways

Search indexing, snippets, live AI retrieval, and model training are separate uses, even when a platform does not provide separate controls for all of them.
Google-Extended can address Gemini training without necessarily removing indexed content from AI Overviews or preventing live use in generated answers.
Make rights decisions by URL family and business role, not with one sitewide allow-or-block rule.
Schema and clear HTML improve machine understanding; they do not create access control, waive rights, or guarantee attribution.
Use authentication for assets that must remain protected. Crawler preferences are not a substitute for a security boundary.
Judge AI visibility by attribution, accuracy, qualified outcomes, and exposure as well as traffic.

Your next move is to choose one important URL family and complete the rights-to-visibility matrix before touching its directives. Capture the current configuration and performance, decide which uses you actually want, and change only the control that can credibly serve that decision. The durable strategy is neither maximum exposure nor total disappearance. It is a deliberately designed public surface with a defensible boundary around the value you cannot afford to give away.

References

December 19, 2025

Google Ad Manager Price Floors After Antitrust Scrutiny

If you searched for Google Ad Manager pricing because you are worried that Google changed what the platform costs, the consequential change is elsewhere. In this context, pricing refers to auction controls: publishers can again set different price floors for different bidders.

That gives you more control over yield and competition, but it does not guarantee more revenue. A higher floor can improve the price of impressions a bidder still wins, reduce that bidder’s win rate, shift wins to other demand, or leave you with weaker monetization. The practical job is to test the restored control without mistaking a higher CPM for a better business result.

The change is about auction floors, not an Ad Manager fee

A price floor is the minimum a bid must meet under the applicable rule. It is a filter inside the auction, not a promise that a buyer will pay the floor, not a guarantee that an impression will sell, and not a product subscription price.

The newly relaxed rules let you apply different minimums to different bidders. For example, one buyer could face a $5 minimum while other buyers face a $2 minimum. Those figures illustrate the control; they are not recommended floor values. Your own demand and inventory data should determine the numbers.

Term	What it means	What it does not mean
Price floor	The minimum a bid must meet under a rule	A guaranteed CPM or sale
Unified pricing	Covered bidders face the same floor	Every bidder submits the same bid or wins equally often
Bidder-specific pricing	Different bidders can face different minimums	Every higher floor will increase revenue

The history explains why this restoration matters. Before 2019, publishers had more latitude to apply higher floors specifically to Google. Google then required uniform pricing, removing that lever. After more than six years, unified pricing rules have been renamed pricing rules and bidder-specific floors have returned.

The important distinction is control. Unified pricing constrained how you could respond when one bidder had different information, buying power, or auction behavior. Bidder-specific pricing lets you treat those demand sources differently, but it leaves you responsible for proving that the difference improves yield.

Antitrust pressure matters because pricing control shapes competition

Four streams of colored bid tokens pass through separate threshold gates toward one transparent digital auction chamber.

A floor rule does more than choose a revenue target. It establishes the terms under which demand sources compete for your inventory. When the company operating key auction infrastructure also participates across the ad-tech supply chain, restrictions on publisher pricing discretion can attract scrutiny over self-preferencing and access for rival technology.

The regulatory backdrop is substantial. U.S. authorities accused Google of anti-competitive conduct and proposed ending unified pricing, while European authorities imposed a €2.95 billion fine and demanded that Google stop self-preferencing within the ad-tech supply chain. The U.S. claims should still be understood as allegations and proposed remedies; the European fine is a regulatory action. They should not be flattened into one universal legal conclusion.

Google’s stated position is that the update should make it easier for publishers and advertisers to work with competing ad-tech providers while minimizing disruption across display, video, and app advertising. That is Google’s explanation of the change, not proof that every competitive concern has been resolved.

For your team, the useful lesson is narrower. A product rollback made under antitrust pressure restores an operational choice; it does not decide how you should use that choice, resolve the wider litigation, or answer whether a particular pricing configuration complies with your contracts and applicable law.

Keep three questions separate when discussing the update internally: what regulators alleged, what Google changed, and what your auction data shows. Mixing them leads to bad decisions, such as raising Google’s floor to make a political point even when the configuration lowers publisher revenue.

A higher floor can improve CPM while reducing yield

A raised metallic threshold lets a smaller number of bright bid orbs reach an inventory grid while other bids divert to alternate paths.

The central mistake is to judge a pricing rule by CPM alone. CPM describes the value of sold impressions. Your business result also depends on how frequently the affected bidder clears its floor, whether other bidders replace lost wins, how much inventory sells, and how much revenue the tested inventory produces overall.

If the affected bidder continues to meet the higher floor, realized CPM on its winning impressions may improve.
If that bidder stops clearing as often and competing demand replaces it at acceptable prices, your bidder mix can change without a severe revenue loss.
If replacement demand is weak, the higher floor can reduce the affected bidder’s win rate without producing enough revenue elsewhere.
If you raise several floors at once, you may see a different total result but be unable to identify which rule caused it.

This is why bidder-specific floors should be treated as yield-management controls, not surcharges or penalties. The identity of a bidder may justify testing a different minimum, especially where its buying position or data advantages differ. It does not tell you in advance which floor maximizes the value of an impression.

Metric	Question it answers	Common misread
CPM	Are sold impressions earning more?	Assuming a CPM increase proves total yield improved
Affected bidder win rate	How did the rule change that bidder’s auction share?	Calling any decline a success without checking replacement demand
Sold volume or fill	Did other demand absorb the available opportunities?	Ignoring impressions that monetized poorly or did not sell
Revenue for the tested inventory	Did the same inventory produce a better overall result?	Comparing periods with materially different traffic or demand
Bidder mix	Did competition broaden or merely shift?	Calling a transfer to one fallback bidder diversification

A useful result therefore has several parts: the floor changes bidder behavior as expected, the resulting CPM is acceptable, replacement demand remains healthy, and the tested inventory earns more overall. If only the first metric improves, you have changed the auction without yet proving a yield benefit.

Key takeaways

Google Ad Manager’s pricing update concerns publisher auction floors, not a published change to an Ad Manager fee schedule.
Publishers can set different minimums for different bidders instead of applying one unified floor across them.
A price floor is an eligibility threshold, not a guaranteed selling price or revenue increase.
The rollback arrived amid U.S. antitrust allegations and a €2.95 billion European penalty tied to self-preferencing concerns.
Evaluate bidder-specific floors with CPM, win rate, sold volume, bidder mix, and revenue for the same tested inventory.
Start with a reversible, isolated test rather than changing an entire account at once.

Test bidder-specific pricing without putting total yield at risk

A live floor change can reduce revenue, so document the current configuration and define a rollback condition before touching a broad inventory set. You want a test that can answer one question cleanly and can be reversed if the trade-off is poor.

Run the smallest useful experiment

Map the existing rule. Record the current floor, affected bidders, eligible inventory, and any exceptions. If you cannot describe the present state, you will not be able to attribute the result of a change.
Select one coherent inventory cohort. Start with a single ad unit, format, or similarly consistent slice. Separate device or geography where those dimensions attract materially different demand.
Capture a baseline. Record CPM, the affected bidder’s win rate, sold volume or fill, bidder mix, and revenue for that inventory before the change. Note traffic or demand shifts that could make the periods incomparable.
Write the hypothesis. State which bidder will receive a different floor, why its current behavior justifies the test, and what combination of revenue and auction metrics would count as improvement.
Change one variable. Adjust one bidder-specific floor while keeping the inventory cohort and other relevant settings stable. Multiple simultaneous floor changes create an attribution problem.
Read the metrics together. A higher CPM is encouraging only when the decline in win rate or sold volume does not erase the gain. Check where lost wins moved and whether competition became broader or merely shifted to another buyer.
Roll back or expand deliberately. Reverse the rule if the predefined downside appears. Expand only after the same mechanism holds across comparable observations; do not copy a successful floor blindly to inventory with different demand.

Avoid the three most expensive misreads

“CPM rose, so the test worked.” CPM can rise while fewer impressions sell or total revenue falls. Use revenue from comparable inventory as the business check.
“Google won less, so competition improved.” A lower win rate for one bidder is not enough. Determine whether several rivals became more competitive or whether wins simply moved to one fallback source.
“Regulators opposed unified pricing, so every differentiated floor is safe.” The rollback restores product flexibility; it does not approve your specific configuration. If bidder-specific treatment could affect contractual obligations or create legal uncertainty in your jurisdiction, have qualified legal counsel review it before a broad rollout.

Begin with one stable inventory cohort, one bidder, one documented hypothesis, and one rollback condition. The useful outcome of the antitrust-driven change is not the ability to set a more aggressive number; it is the ability to make a measurable pricing choice and keep it only when the full auction result supports it.

References

Search Engine Land – Google scraps unified pricing rules in Ad Manager after antitrust pressure

December 17, 2025

Legal GEO Agencies: How to Choose the Right Partner

You are not choosing a legal GEO agency because your firm needs another marketing acronym. You are choosing one because prospective clients can now encounter an AI-generated answer before they see a search result, visit a practice-area page, or recognize your firm’s name. The right partner must improve that discovery path without weakening factual accuracy, attorney-advertising compliance, or your control over the firm’s digital assets.

The market does not make that choice easy. By the first half of 2025, the field was crowded enough for 43 law firm GEO agency contenders to be evaluated. A large field creates apparent choice, but labels such as GEO, AEO, AI SEO, and AI visibility do not tell you what an agency actually delivers. You need to evaluate the operating model behind the label.

Map the agency landscape to your actual bottleneck

Generative engine optimization is the work of making an organization and its information easier for generative systems to retrieve, understand, verify, and use in an answer. It overlaps with SEO, content strategy, structured data, digital public relations, entity management, and reputation work. That overlap explains why very different agencies can all sell a service called GEO.

Most legal GEO providers can be understood through four broad operating models. These are not rigid categories, and a capable agency may combine several. Use them to identify the provider’s center of gravity:

Legal SEO agencies with a GEO practice: These providers usually begin with crawlability, search demand, practice-area architecture, local visibility, and content. They are a sensible fit when your conventional search foundation is weak. Verify that GEO adds prompt research, citation analysis, entity work, and answer-level measurement rather than merely placing a new name on an existing SEO package.
GEO or AEO specialists: These agencies tend to start with generative answer surfaces, prompt sets, cited-source patterns, brand mentions, and entity clarity. They may suit a firm with mature SEO operations that needs a dedicated AI-search layer. Verify their understanding of legal review, local discovery, jurisdiction-specific content, and attorney-advertising restrictions.
Content and authority specialists: These providers concentrate on expert content, editorial positioning, third-party mentions, and digital PR. They can help when your website is technically sound but your firm lacks corroborating authority beyond its own domain. Verify that they can diagnose technical and entity problems rather than treating every visibility gap as a publishing problem.
Technical and structured-data consultancies: These providers focus on information architecture, structured data, feeds, entity reconciliation, and machine-readable consistency. They can resolve foundational ambiguity, but technical markup alone is not a complete GEO strategy. Verify who will improve the underlying legal content and build credible external corroboration.

Choose the model that matches the constraint. If search systems cannot reliably crawl or interpret your pages, start with technical and entity work. If your pages are accessible but generic, stale, or jurisdictionally vague, prioritize legal editorial operations. If your firm publishes strong material but appears nowhere outside its own properties, authority development may matter most. If you cannot tell whether any of this is working, fix measurement before funding a larger content program.

This diagnosis also prevents an expensive mismatch. A firm with contradictory attorney biographies does not primarily need more blog posts. A firm with accurate, useful content but weak independent recognition does not primarily need another schema deployment. Make each agency name the bottleneck it believes it is solving and show the evidence behind that diagnosis.

Define success before an agency defines it for you

A legal GEO program can generate impressive-looking reports without answering the commercial question: is the firm becoming easier for the right person to discover and evaluate? Avoid that trap by defining the measurement system in your brief, before you review proposals.

Build a query portfolio, not a keyword list

Traditional keywords remain useful, but generative searches often contain a situation, constraints, follow-up questions, and evaluation criteria. Build a prompt portfolio around the decisions your prospective clients make. It should cover:

Branded accuracy: Questions about your firm, attorneys, offices, services, credentials, and public contact information.
Problem discovery: Questions asked before a person knows the legal name of the relevant practice area.
Service evaluation: Questions comparing approaches, qualifications, jurisdictional coverage, or the factors involved in choosing counsel.
Local and jurisdictional intent: Questions in which location, court, governing law, licensing, or service area materially changes the answer.
High-consideration questions: Questions about process, possible costs, timelines, evidence, risk, and what information someone should prepare before contacting a lawyer.

Do not put confidential intake facts or identifiable client information into this prompt set. Use public facts, redacted patterns, or hypothetical wording approved by the firm. If an agency wants real client material for testing, require a documented data-handling review before sharing anything.

Keep a stable benchmark set for comparison while allowing a separate exploratory set for emerging questions. For every observation, record the exact prompt, product or answer surface, date, visible location or account context, response, cited pages, brand mentions, factual errors, and relevant call to action. Generative output can change between runs, so a visibility score without the underlying observations is not auditable evidence.

Separate four outcomes that vendors often blur together

Retrievability: Can the system access and interpret the firm’s relevant information?
Visibility: Does the firm appear as a mention, cited source, or possible provider for the agreed prompt portfolio?
Accuracy: Are descriptions of attorneys, services, locations, qualifications, and legal topics correct and appropriately qualified?
Qualified demand: Does visibility contribute to relevant visits, consultations, or intake rather than merely producing more brand mentions?

A mention is not necessarily a citation. A citation is not necessarily a recommendation. A recommendation is not necessarily a qualified inquiry. Your reporting should preserve those distinctions instead of compressing them into one proprietary score.

There is also no single permanent AI rank equivalent to a fixed position you can purchase or guarantee. Responses can depend on the wording of the prompt, available sources, product behavior, user context, and changes outside the agency’s control. Treat a promise of guaranteed placement as a warning sign. A credible agency should commit to defined work, transparent evidence, and measurable coverage, not an answer it does not control.

Inspect the complete GEO delivery system

Researchers, legal reviewers, and technical specialists work across connected stations containing source materials, compliance checks, publishing tools, and analytics.

A proposal should connect technical access, entity clarity, content quality, external corroboration, measurement, and legal governance. If any component is missing, ask who owns it. Work divided between your agency, web team, attorneys, public-relations provider, and intake team still needs one accountable workflow.

Technical access and entity clarity

The agency should examine whether important pages can be crawled, rendered, indexed, and reached through coherent internal links. It should identify conflicting canonical signals, accidental noindex rules, thin duplicates, broken redirects, fragmented office information, and practice pages that compete with one another. Publishing more content before resolving those issues can expand the ambiguity.

For a law firm, entity work should reconcile the firm name, offices, attorneys, practice areas, jurisdictions, credentials, public profiles, and relationships between them. An agency should be able to explain which property is authoritative for each fact and how corrections move across the firm’s site and legitimate external profiles.

Structured data can make those relationships more explicit, but it must describe visible, supportable information. Appropriate organization, legal-service, person, address, article, and breadcrumb markup may help machines interpret a page. Markup must not introduce awards, ratings, locations, services, or credentials that a user cannot verify on the page. Ask for validation results, a mapping between each field and its visible source, and a process for updating markup when attorneys or offices change.

Legal content that is answerable and reviewable

Good legal GEO content should answer a defined question directly, state the jurisdiction or scope where it matters, explain material conditions, and give the reader a sensible next step. It should also make authorship, legal review, and update responsibility clear. A disclaimer does not repair inaccurate or overbroad legal information.

Ask how the agency turns one topic into a coherent information structure. The answer should address the main page, supporting questions, internal links, attorney and practice relationships, source maintenance, consolidation of overlapping pages, and updates when the underlying law or the firm’s services change. A publishing quota without a maintenance plan creates a growing accuracy liability.

Require a firm-side lawyer or ethics reviewer familiar with the relevant jurisdiction to approve claims about results, specialization, credentials, testimonials, comparisons, and past matters. Attorney-advertising and professional-conduct requirements vary, and an outside marketing agency should not make the final compliance judgment. Unsupported superlatives and invented expertise are dangerous in page copy, structured data, directory profiles, and AI-generated drafts alike.

External corroboration rather than manufactured signals

Generative systems may encounter information about your firm on third-party sites as well as your own domain. The agency should therefore audit which external pages appear around your priority questions, which ones describe the firm, whether those descriptions are accurate, and where credible gaps exist.

Ask how the provider distinguishes legitimate authority development from low-value placement. A relevant editorial mention, accurate professional profile, or genuinely useful expert contribution serves a different purpose from bulk links on unrelated sites. The plan should name the audience and information gap each placement is intended to address. “More backlinks” is not an adequate GEO rationale.

Governance, correction, and data handling

No agency can directly control every answer generated by a third-party model. It can, however, detect recurring errors, trace likely contributing pages, correct owned information, request appropriate corrections from external publishers, and document whether the error persists. Require a correction workflow with an owner, evidence log, escalation path, and closure rule.

Ask which AI tools the agency uses, what it uploads, whether submitted material may be retained or used to improve third-party systems, who can access project data, and what happens to that data after the engagement. Do not permit confidential case files, privileged communications, unannounced matters, intake records, or personal information to be placed in external AI tools without an approved legal, privacy, and security process. Synthetic or redacted test data is the safer default.

Select an agency with a proof-based procurement process

Law-firm leaders review anonymized evidence folders, technical samples, ownership documents, and abstract performance dashboards during an agency selection meeting.

Give every finalist the same brief. Include your priority practices, jurisdictions, office structure, target audiences, known technical constraints, approval requirements, prompt portfolio, and available analytics. Comparable inputs make it harder for polished presentations to hide weak diagnosis.

Then ask each finalist to assess a small, public portion of your current footprint. The exercise should use no confidential data and require no production access. You are looking for the quality of its reasoning: what it notices, how it separates evidence from inference, which constraint it prioritizes, and how it would verify the result.

Evaluation area	Evidence to request	Weak response to notice
Baseline	Exact prompts, answer captures, cited URLs, factual-error log, and stated testing context	A single visibility percentage with no underlying observations
Diagnosis	A prioritized explanation connecting technical, entity, content, authority, and measurement findings	A generic recommendation to publish more content
Implementation	Named deliverables, responsible owners, dependencies, approval steps, and acceptance criteria	A list of activities with no definition of completion
Legal quality control	A workflow for jurisdictional review, claims approval, corrections, and documented updates	Reliance on AI drafting plus a general website disclaimer
Measurement	Raw prompt-level evidence connected to citations, accuracy, site behavior, and qualified intake where measurable	Brand mentions presented as leads or revenue
Data and ownership	Written terms covering credentials, content, structured data, dashboards, prompt sets, exports, retention, and deletion	Critical assets available only inside the vendor’s account

Your proposal review should force clear answers to the following questions:

What does the agency’s GEO service add beyond its ordinary SEO, content, public-relations, or technical work?
Which part of our current visibility problem does the agency believe is most important, and what evidence supports that conclusion?
How will it distinguish a brand mention, a linked citation, a favorable description, a recommendation, a site visit, and a qualified inquiry?
Which prompts and answer surfaces will be monitored, and will we receive the raw observations behind every aggregate score?
Who writes, verifies, legally reviews, publishes, and maintains each deliverable?
How are confidential information, personal data, prompts, drafts, account credentials, and third-party AI tools handled?
Does the agency work with competing firms in the same practice and market, and what conflict or exclusivity terms apply?
Which content, code, markup, accounts, dashboards, research, and historical data can we export if the engagement ends?

Do not let a case study substitute for this examination. Even a real result may depend on a different practice area, market, domain history, brand, content library, or measurement method. Ask the agency to show the starting condition, work performed, evidence captured, and limits on what can be attributed to GEO. If it cannot explain the mechanism, the headline result is not useful for your decision.

The contract should make the operating model concrete. Define deliverables and acceptance criteria; separate agency responsibilities from firm dependencies; identify third-party costs; preserve your approval rights; prohibit unsupported factual or performance claims; address conflicts, confidentiality, data retention, and AI-tool use; and guarantee usable exports of firm-owned assets at termination. Have qualified counsel review terms that affect confidentiality, intellectual property, professional obligations, privacy, or liability.

Walk away from guarantees of permanent AI placement, schema-only “optimization,” undisclosed bulk AI publishing, unverifiable proprietary scores, fabricated citations, or a refusal to provide raw evidence. Also be cautious when an agency treats every unfavorable answer as a content-volume problem. Sometimes the correct action is to repair a fact, consolidate pages, clarify an entity relationship, improve an external profile, or stop publishing material that no longer deserves to exist.

Key takeaways and your first move

Choose an agency for the bottleneck it can solve, not the GEO label it places on its services.
Define a prompt portfolio and preserve raw answer-level evidence before accepting any visibility score.
Measure retrievability, visibility, accuracy, and qualified demand separately.
Require technical access, entity clarity, useful legal content, external corroboration, and governance to work as one system.
Keep legal approval, sensitive data, account access, and ownership of project assets under firm control.
Reject guaranteed placements and demand a traceable connection between diagnosis, work performed, and observed change.

Your next move is to write a one-page decision brief before contacting more agencies. Name the practices and jurisdictions in scope, the audiences you need to reach, the public facts that must remain accurate, the prompt categories you will test, the internal reviewers who can approve work, and the assets the firm must own. Send the same brief to each finalist and select the team that returns the clearest diagnosis, evidence trail, and operating plan. That discipline will tell you more than any agency ranking can.

References

First Page Sage – Top GEO Agencies Revolutionizing Legal SEO in 2025

December 15, 2025

Category: Legal

Search fairness is four questions, not one metric

Build a scorecard around the complete search journey

Diagnose lower clicks and direct bookings before changing SEO

Act on the layer that actually failed

What search and content teams can change

What regulators would need to demonstrate

Key takeaways

References

Treat the declaration as a classification decision

Choose the declaration scope that matches your account

Build a record you can defend and update

Stop future campaigns from inheriting the wrong answer

EU political ads declaration FAQ

Does an account-level No cover campaigns created later?

Can you change the declaration after submitting it?

What should you do if you missed March 31, 2026?

References

Key takeaways

The dispute turns on access, protection, and reuse

Each possible outcome has narrower meaning than the headline

Your measurement can fail before the legal question is settled

Audit your SERP-data dependency in six steps

References

What the appeal changes – and what it does not

The appeal concerns access to users, not page rankings

Plan for three outcomes without betting on any of them

A readiness plan for SEO and AI discovery teams

Key takeaways

References

The remedies split into four operational layers

The alleged harms are testable mechanisms, not settled outcomes

Index access could change discovery and spam incentives

Ad fraud risk rises when the traffic chain becomes opaque

Nominally favorable pricing can still produce weak economics

Access to interaction data does not create permission to reuse it

Build a readiness plan without betting on the appeal

Questions paid media teams should ask before buying inventory

What SEO, AEO, and GEO teams should measure differently

Key takeaways

References

Platform approval answers a narrower question

Build a two-gate approval workflow before launch

Test the risks a platform cannot clear for you

Re-review material changes and preserve the evidence

Key takeaways

References

What the lawsuit does and does not establish

Audit your SERP dependency before the data changes

Put collection provenance into vendor review

Answers that should slow your decision

Protect AI visibility and SEO reporting without changing strategy

Key takeaways

References

Stop treating crawl access as one permission

Build a rights-to-visibility matrix before changing directives

Make the public layer easy to cite and hard to confuse

Build a useful public reference layer

Keep the irreplaceable asset behind a real boundary

Measure whether visibility creates value or merely extraction

Key takeaways

References

The change is about auction floors, not an Ad Manager fee

Antitrust pressure matters because pricing control shapes competition

A higher floor can improve CPM while reducing yield

Key takeaways

Test bidder-specific pricing without putting total yield at risk

Run the smallest useful experiment

Avoid the three most expensive misreads

References

Map the agency landscape to your actual bottleneck

Define success before an agency defines it for you

Build a query portfolio, not a keyword list

Separate four outcomes that vendors often blur together

Inspect the complete GEO delivery system

Technical access and entity clarity

Legal content that is answerable and reviewable

External corroboration rather than manufactured signals

Governance, correction, and data handling

Select an agency with a proof-based procurement process