Category: Legal

EU Scrutiny of Google’s DMA Compliance: A Marketer’s Plan

If European search contributes meaningful traffic, leads, subscriptions, or sales to your business, the main risk isn’t missing the EU’s announcement. It is discovering a performance change later and having no reliable baseline to explain what moved, where it moved, or whether the ruling had anything to do with it.

The European Commission opened its investigation of Google’s search business under the Digital Markets Act in March 2024. Competition Commissioner Teresa Ribera has said a decision will come, but she hasn’t committed to a date. You should use that uncertain window to prepare your measurement, ownership, and response process – not to guess the verdict.

The ruling, the remedy, and the search change are different events

A regulatory finding does not automatically tell you what a search results page will look like, when Google will alter a system, or how users will respond. Those are separate stages. Treating them as a single event is how teams end up attributing every ranking, cost, and traffic fluctuation to regulation.

Work with three distinct clocks:

The legal clock: What the Commission decides, which conduct it addresses, what remedies it requires, and when any obligations take effect.
The product clock: What Google actually changes in search presentation, ad delivery, ranking systems, pricing mechanics, reporting, or access for competing services.
The performance clock: When those changes become visible in impressions, clicks, costs, conversions, referrals, citations, or revenue.

Do not start the product or performance clock merely because a headline appears. First confirm that the final decision requires an operational change relevant to your market. Then confirm that a change has been deployed. Only after that should you test whether your data moved in a related way.

Political pressure is also not a substitute for a decision. A coalition of 18 lobby groups and civil society organizations has asked for a substantial fine and definitive remedies. That request tells you enforcement pressure is high; it does not establish what the Commission will order. Likewise, Google’s approximately 90% share of the EU search market explains why the consequences could be broad, but market share alone does not predict the remedy.

Create an internal tracking record now. Keep confirmed facts, outside demands, possible outcomes, observed Google changes, and measured business effects in separate fields. That small distinction will prevent speculation from hardening into an unsupported performance explanation.

Watch four search surfaces, not one ranking chart

Four abstract search interfaces show web results, local listings, product discovery, and an AI-style answer panel around a central workstation.

A conventional rank tracker can tell you that a URL changed position. It cannot, by itself, show whether the page gained usable visibility, whether a new search feature displaced it, whether paid inventory changed above it, or whether an AI-generated answer absorbed the click. Your monitoring needs to cover the whole search experience.

Surface	Baseline to preserve now	Signal worth investigating	First response
Organic search	Query group, landing page, country, language, device, impressions, clicks, click-through rate, average position, and visible result features	A sustained EU-specific change across related queries, pages, or result types rather than an isolated ranking movement	Inspect the actual results pages and identify which element gained, lost, or changed placement before editing content
Paid search	Campaign, country, device, query class, impressions, click volume, cost per click, impression share, conversion rate, and cost per acquisition or return on ad spend	Costs or delivery patterns moving in affected EU segments while comparable segments remain relatively stable	Check auction, placement, demand, budget, and conversion-quality signals before changing bids
AI Overviews and publisher visibility	Feature presence on a fixed query sample, cited domains, cited URLs, brand mentions, organic clicks, and publisher referrals	A repeatable change in feature frequency, source selection, citation prominence, or downstream traffic	Separate changes in AI presentation from ordinary blue-link ranking changes and record both
Competitive discovery	Referral sources, partner traffic, comparison-service visibility, branded search demand, and assisted conversions	New or expanded discovery paths producing qualified visits or conversions	Validate traffic quality and attribution before reallocating acquisition resources

The Commission is also examining Google’s use of AI Overviews and its ranking of news publishers. Keep that scrutiny on a separate line in your change log. It may overlap with the same search ecosystem, but you should not assume every AI Overview or publisher-visibility change is part of the pending DMA decision.

This distinction matters for diagnosis. If ordinary rankings remain stable but citations inside AI-generated results change, you have a source-selection or presentation question. If ad costs move while organic layouts remain stable, you have an auction or demand question. If impressions remain steady but clicks fall after a result-page change, you have a click-distribution question. Each pattern calls for different evidence and a different response.

Build an EU search baseline before you need one

A useful baseline is not a single export labeled “Europe.” EU markets differ by language, query demand, competition, device use, campaign structure, and commercial importance. Aggregate reporting can hide a serious movement in one market behind stability in another.

Define the affected business scope. List the EU countries, languages, domains, subdirectories, storefronts, publications, and campaigns that matter to you. Assign an owner to each material segment.
Freeze meaningful cohorts. Preserve groups for branded and non-branded queries, informational and commercial intent, product or service families, news content where relevant, and the landing pages that generate business outcomes. Do not rebuild the groups after performance changes.
Add comparison segments. Use comparable non-EU markets, stable query groups, or unaffected product lines as diagnostic references. A comparison is not proof of causation; it helps show whether a movement is localized or part of a wider change.
Record the visible search environment. For a fixed query sample, capture date, country, language, device, result order, ad presence, Google-owned modules, competing services, AI-generated features, citations, and other elements that can alter attention or clicks.
Connect visibility to outcomes. Pair rankings and impressions with clicks, qualified sessions, conversions, revenue, subscription starts, lead quality, and paid acquisition costs. A visibility change with no business effect deserves a different response from a revenue change.
Log confounding events. Record site migrations, content releases, schema changes, consent changes, campaign edits, promotions, outages, seasonality, and unrelated Google updates. Without this log, a regulatory explanation can become the default simply because it is prominent.

Keep raw exports or snapshots as well as dashboards. A dashboard can be reconfigured, filtered incorrectly, or lose historical dimensions. Your preserved data should let another analyst reconstruct what users could see and what the business measured before any compliance-related rollout.

Do not rewrite your JSON-LD in anticipation of an unknown remedy. Structured data should continue to describe the page’s real entities, offers, authorship, organization, products, articles, and relationships accurately. A regulatory change to distribution or presentation does not make inaccurate schema useful. If Google later publishes new eligibility or implementation requirements, evaluate those documented requirements against your existing markup and change only what the page supports.

Apply the same discipline to AEO and GEO work. Clear answers, explicit entity relationships, attributable claims, and crawlable supporting detail remain useful, but they are not a workaround for a platform-level compliance change. Measure traditional Google visibility, AI-generated search visibility, and citations in other answer engines separately so a gain in one channel does not conceal a loss in another.

Prepare for scenarios without pretending to know the remedy

A strategy team examines three branching, unlabeled search-market scenarios on an illuminated planning table.

Your plan should cover plausible operational outcomes without presenting any of them as the expected verdict. The goal is not to forecast Brussels. It is to know which evidence would trigger which action.

A penalty arrives without an immediate visible search change

A financial penalty can dominate coverage while producing no immediate change that users or advertisers can see. In that scenario, annotate the decision date but leave content, bids, and technical implementation alone unless the data or the remedy gives you a reason to act. Continue monitoring for a later rollout rather than forcing a same-day explanation onto normal volatility.

A remedy changes result presentation or access

If a remedy affects how Google presents its own services, rival services, publishers, or other result types, position alone will be an incomplete metric. Compare the same queries before and after deployment. Record which modules appear, how much prominence they receive, which destinations win the click, and whether the new traffic converts.

Do not immediately rewrite pages that lose clicks while retaining rank. First determine whether the content became less competitive or whether another interface element intercepted attention. Content changes address the first problem; measurement, distribution, and channel changes may be needed for the second.

Ad serving, ranking, or pricing mechanics change

The pending decision could affect ad serving, ranking, or pricing dynamics, but the direction and size of any effect are not known. Paid search teams should preserve campaign-level and market-level baselines now, including the relationship between cost, placement, demand, conversion quality, and revenue.

If costs move, do not assume the compliance decision caused them merely because the dates are close. Check whether demand, competitors, match behavior, budgets, creatives, landing pages, tracking, or conversion mix changed at the same time. When financial exposure is material, use capped and reversible bid or budget adjustments while you investigate. A sweeping change can create additional cost and destroy the comparison you need.

AI Overview or news-publisher action moves on a separate track

A change involving AI Overviews or publisher ranking may be important without being the remedy in the core DMA search case. Label the responsible proceeding or product update whenever you can confirm it. If you cannot, describe the observation plainly – such as a change in citation frequency or publisher clicks – and leave the cause unassigned.

That restraint improves your decisions. It also keeps executive reporting credible when several regulatory investigations, product releases, and market shifts are unfolding in the same ecosystem.

Key takeaways and the response plan to use

The EU decision, Google’s implementation, and the resulting performance effect should be tracked as separate events.
A fine or demanded remedy is not evidence that a visible search change has already happened.
Segment EU performance by country, language, device, query type, page group, and paid or organic channel before relying on an aggregate trend.
Monitor search-result composition, AI citations, ad delivery, costs, clicks, and business outcomes – not rankings alone.
Keep AI Overview and news-publisher scrutiny separate from the core DMA case unless the final decision explicitly connects them.
Preserve accurate structured data and content facts; do not make speculative technical changes for an unknown remedy.
Use reversible commercial adjustments until multiple related signals support the same diagnosis.

When the decision is published

Read beyond the headline. Obtain the official decision or authoritative summary and identify the finding, conduct in scope, required remedies, geographic scope, covered services, effective dates, and unresolved points.
Write a short decision brief. Separate confirmed obligations from possible product implications. Include an explicit “unknown” section so assumptions remain visible.
Map each remedy to an observable surface. Assign organic search, paid search, analytics, publisher, AI visibility, legal, and product owners only where their systems are genuinely affected.
Annotate your measurement systems. Record the decision date, announced implementation dates, and first observed rollout separately. Do not use one generic marker for all of them.
Compare against the preserved baseline. Look for related movements across geography, device, query groups, search features, clicks, costs, and conversions. An isolated metric is a prompt to investigate, not a conclusion.
Choose the smallest reversible response. Adjust monitoring, experiments, bids, distribution, or content only to the degree supported by evidence. Preserve a comparison group wherever the business can safely do so.
Report causality carefully. Use “coincided with” or “followed” until you can connect the legal requirement, the deployed product change, and the measured effect. Timing alone does not establish cause.

If the ruling creates legal obligations for your own company, counsel should interpret those obligations. For the search and marketing teams, the immediate job is operational: preserve evidence, identify the actual implementation, and protect performance without making speculative changes.

You do not need a confident prediction to be ready. You need a clean EU baseline, named owners, a record of what changed, and a rule that no irreversible action happens before the evidence identifies the affected surface. Put those pieces in place while the decision is still pending, and the eventual verdict becomes a manageable measurement event rather than a scramble.

References

CrushPress.AI – EU’s Verdict on Google’s Compliance: A Game Changer for Digital Markets

March 23, 2026

How to Find and Close Law Firm Referral Conversion Gaps

A trusted contact recommends your firm by name. The prospective client sounds ideal. Then nothing happens. They never call, or they start an inquiry and disappear before scheduling.

That does not necessarily mean the referral was weak. Before contacting you, the prospect may search for the firm, inspect a lawyer’s profile, look for experience with the exact legal issue and ask an AI assistant for another opinion. Your digital presence and intake process must confirm the trust transferred by the referrer. If either introduces doubt, a strong referral can lose momentum.

Key takeaways

A referral earns serious consideration, not an automatic consultation or engagement.
Most referral losses can be investigated as credibility, specificity, authority or friction gaps.
The best validation page mirrors the precise reason the firm was recommended, identifies the relevant lawyer and offers an obvious next step.
JSON-LD can clarify the relationship among the firm, its lawyers, locations and services, but it cannot compensate for vague or unsupported claims.
Measure each handoff separately so you can distinguish a marketing problem from an intake, qualification or scheduling problem.

A referral starts a validation journey, not a straight line

The referrer has already done valuable work. They have transferred some of their credibility to your firm and given the prospect a reason to pay attention. But the prospect still has questions: Does this firm really handle my kind of matter? Is this the lawyer I was told about? Does the firm’s public record support the recommendation? Can I see what to do next?

The difference between what the prospect was promised and what they can corroborate is a referral validation gap. It appears after the recommendation but before a productive conversation with the firm. That location matters. If you only examine retained clients or completed intake forms, the people who vanished during validation remain invisible.

Think of the journey as a sequence of trust handoffs:

Recommendation: Someone associates your firm with a specific problem, lawyer or result they believe you can pursue.
Verification: The prospect checks your website, search results, professional profiles, reviews or AI-generated answers.
Contact: They decide whether the available evidence justifies a call, form submission or consultation request.
Intake: Your team confirms fit, handles the inquiry and establishes the appropriate next step.
Engagement: The prospect makes a separate decision about retaining the firm under the applicable terms.

A break at one stage should not be blamed on another. A prospect who cannot find the recommended practice on your website has a validation problem. Someone who starts a form but abandons it has encountered friction. A qualified caller who waits without knowing what comes next has an intake problem. Treating all three as a generic conversion issue leads to unfocused redesigns and more content that does not answer the original doubt.

Start by reconstructing the promise that brought the prospect to you. Review referral notes, intake records and the language your lawyers hear from frequent referral partners. You are looking for the actual expectation: a named lawyer, a narrow matter type, a particular client situation, a location or a combination of these. That expectation becomes the standard against which the public journey is audited.

Diagnose the four places trust can break

Referral losses become easier to fix when you classify the first point of doubt. The four useful categories are credibility, specificity, authority and friction. They can overlap, but one usually appears first in the prospect’s journey.

Gap	Question in the prospect’s mind	What to inspect	First repair
Credibility	Does this look like the firm I was promised?	Firm and lawyer names, current biographies, office details, visible credentials, page condition and consistency across profiles	Make identity, relevant credentials and contact information immediately clear and consistent
Specificity	Do they handle my exact kind of matter?	Page titles, headings, service descriptions, lawyer experience, examples and answers to matter-specific questions	Create or improve a page that addresses the recurring referral reason in the prospect’s language
Authority	Can anything outside this recommendation confirm the expertise?	Professional profiles, third-party mentions, search results, AI answers, entity consistency and structured data	Correct public facts, connect corroborating profiles and make supported claims machine-readable
Friction	How do I take the next step, and what will happen?	Mobile navigation, phone links, form fields, required information, confirmation messages, routing and follow-up	Offer one clear action, request only what intake needs and set an accurate expectation for the response

A credibility gap is not merely an unattractive design. It can be a former lawyer still presented as current, inconsistent firm names, an incomplete biography, an office address that conflicts with another profile or credentials buried below generic promotional copy. Correctness and recognizability matter more than visual novelty.

A specificity gap often hides behind a technically accurate but broad practice page. A prospect referred for a narrow commercial dispute does not receive much reassurance from a heading that only says commercial litigation. They need enough detail to recognize their situation and understand why the named lawyer or team is relevant. You do not need to predict the merits of an individual case. You do need to show that the category is familiar.

An authority gap appears when your own claim has no accessible support. A biography may call a lawyer experienced, but search results, professional listings and publicly retrievable material do not connect that person to the matter. AI systems may then omit the firm, confuse lawyers with similar names or repeat incomplete information. Structured data can clarify supported facts, but independent corroboration still matters.

A friction gap happens after the prospect is persuaded enough to act. Common symptoms include an unclear primary call to action, a form that asks for more information than initial triage requires, a phone number that is difficult to use on mobile, no confirmation that a request arrived or no explanation of what follows. These details are especially costly because the person has already crossed the harder trust threshold.

Audit the journey from the prospect’s side. Search the firm name, the referred lawyer and the specific issue. Repeat the check on mobile. Inspect the landing page a searcher is most likely to reach rather than starting from the homepage. Ask representative questions in the AI interfaces your audience may use, then record whether the firm appears, whether the description is accurate and which public information seems to support the answer. The first material contradiction or missing answer is usually the most valuable repair.

Build a page that confirms the exact referral promise

Your homepage cannot validate every referral. Its job is orientation. A referral-specific service page, lawyer biography or focused landing page should do the confirming.

Build these pages around recurring referral reasons, not every keyword variation you can imagine. If several trusted contacts send people to a particular lawyer for a defined kind of matter, the site should provide a short path connecting that lawyer, that problem and the next step. The page needs to answer the prospect’s validation questions in a sensible order:

Match the expectation in the heading. Name the specific service or problem clearly. A prospect should not have to infer it from a broad department label.
Define the relevant scope. Explain the kinds of situations the page covers, the clients it serves and any geographic or jurisdictional boundary needed to understand the offering.
Identify the responsible lawyer or team. Link to current biographies and make each person’s role clear. Do not force the visitor to search the staff directory again.
Show support for the claim. Use accurate credentials, representative experience, authored material, speaking activity or other evidence the firm is permitted to publish. General praise is not evidence.
Explain the next step. State what the prospect can request, what information is appropriate to share initially and what happens after submission.
Provide one dominant action. Make the consultation request, call or other intake route easy to find and use on the device in the visitor’s hand.

The opening screen should carry most of the recognition work. Include the matter, the relevant lawyer or team where appropriate, the firm identity and a clear action. Awards, office photography and general brand language can support that information, but they should not displace it.

Specific content needs boundaries as much as detail. State what the service covers without suggesting that every visitor has a viable claim or that an outcome is assured. Do not turn a landing page into individualized legal advice. Before publishing testimonials, awards, representative matters or response commitments, have the responsible lawyer verify accuracy, permissions, confidentiality and the professional-advertising rules that apply in each relevant jurisdiction.

Internal links should preserve the same chain of meaning. A lawyer biography should link to the specific service. The service page should link back to the lawyer. Relevant educational content should identify its author and lead to the appropriate intake route. Breadcrumbs and navigation should make the broader practice relationship understandable without forcing the prospect back through the homepage.

Do not publish a page and assume the wording matches the referral. Read it next to the expectation you reconstructed. If the referral promise is about a named lawyer handling a narrow issue but the page leads with a generic firm slogan, the gap remains. The test is not whether the page sounds polished. It is whether a prospect can say, with minimal interpretation, that they reached the right firm for the reason they were given.

Make your authority readable by people, search engines and AI

Your reputation may be obvious inside a professional network and nearly invisible outside it. Search engines and AI answer systems work from accessible information, not private referral history. They need consistent entities, explicit relationships and public evidence that supports the firm’s claims.

Begin with the visible facts. Use the same current firm name, lawyer name, office information and service terminology across the website and maintained third-party profiles. Correct old biographies and duplicate location records. Link to authoritative professional profiles where appropriate. A citation, directory entry or publication byline should corroborate a real fact, not exist merely to increase the number of mentions.

Then use JSON-LD to describe what the page already says. Depending on the page and the facts available, Schema.org types such as Organization or LegalService can represent the firm, Person can represent an individual lawyer, and BreadcrumbList can describe the page’s place in the site. Stable @id values can connect those entities across pages. Relevant properties may describe the canonical URL, contact details, address, service area and maintained profile links.

The governing rule is simple: markup must mirror visible, accurate content. Do not use structured data to manufacture an award, specialty, review, office, service area or affiliation that a visitor cannot verify. Do not add an FAQ entity unless the questions and answers are actually present on the page. Schema can reduce ambiguity; it cannot turn an unsupported assertion into authority or guarantee that an AI system will mention the firm.

Use this sequence when reviewing the implementation:

Choose the canonical page for each firm, lawyer, office and recurring service concept.
Confirm that its visible text is complete, current and approved.
Assign only Schema.org types that accurately describe the entity represented on that page.
Give each important entity a stable identifier and connect related entities rather than creating isolated markup fragments.
Validate the syntax and compare every material property with the visible page.
Recheck the output after biography, office, service or branding changes.

AI visibility needs its own audit, but not a one-off vanity search. Create a controlled set of questions based on genuine referral language. Include branded verification questions, lawyer-and-matter questions and unbranded service questions. Record the interface or model, the wording, the date, the answer, the firms mentioned and the cited or linked evidence when the interface provides it.

Answers can vary by system, session and available retrieval, so one favorable response is not a ranking report. Look for repeated failure patterns instead. If the system recognizes the firm but assigns the wrong service, fix entity and content clarity. If it recognizes the service but not the relevant lawyer, strengthen that connection on both pages and in the markup. If competitors are consistently supported by clearer third-party evidence, the missing layer is authority rather than another rewrite of your homepage.

Remove intake friction and measure each handoff

A prospective client and intake specialist use a smartphone and appointment calendar at a tidy desk beside an open consultation room.

A validation path is unfinished until a persuaded prospect can act. The intake experience should preserve the context and confidence built by the referral rather than making the person start over.

Use an action label that tells the prospect what they are requesting. Make phone numbers usable on mobile. Keep the initial form to information the team truly needs for routing and conflict or fit screening. Avoid inviting detailed or highly sensitive case facts into a general web form; move that exchange to an appropriately secure, approved process. The confirmation screen and message should acknowledge receipt, state the response window the team can reliably meet and avoid implying that submission alone creates an attorney-client relationship.

Preserve referral context in the handoff. An optional referral-source field can help, but do not depend on the prospect knowing a formal organization or campaign name. Pass the landing page and selected service into the intake record when your privacy practices and systems permit it. If a receptionist or intake specialist receives the inquiry, they should be able to see the matter category and the lawyer or page that prompted the contact.

Measure the journey as separate stages:

Referral identified
Relevant validation page reached
Contact action started
Contact completed or call connected
Inquiry screened as an appropriate fit
Consultation offered and scheduled
Engagement completed

You will not be able to identify every referred visitor before they contact you. Use observable cohorts honestly: dedicated partner links without personal information, referral landing pages, a voluntary intake field, call-source notes or another privacy-appropriate mechanism. Do not inflate the denominator with visitors whose source you cannot establish.

The useful rates correspond to different decisions. Contact completion rate compares completed inquiries with started contact actions. Qualified consultation rate compares scheduled consultations with referred inquiries that met the firm’s criteria. Engagement rate compares opened matters with completed referred consultations. Keep definitions stable so a change in intake labeling does not masquerade as a conversion improvement.

Read the drop-off pattern before choosing a fix:

Validation-page visits are visible but contact actions are scarce: inspect credibility, specificity and authority before redesigning the form.
Form starts are healthy but completions are weak: inspect required fields, error handling, mobile usability, privacy concerns and unclear expectations.
Inquiry volume is healthy but fit is poor: align the page and referrer-facing language with the matters the firm actually accepts.
Qualified inquiries do not become scheduled consultations: inspect routing, response handling, availability and the clarity of the next step.
Consultations occur but engagements do not: examine expectation-setting and the consultation process instead of attributing the loss to website traffic.

Referral traffic is often too limited or uneven for a rapid A/B test to produce a dependable answer. Use the evidence you actually have. Establish a baseline, fix the earliest known break, annotate the change and compare the same stage over an appropriate later period. Pair the numbers with intake notes and reasons for loss. A smaller, clearly defined cohort is more useful than a large blended conversion rate covering unrelated practices and acquisition channels.

Start with one valuable, repeatable referral path. Write down the promise, reproduce the prospect’s verification journey and fix the first place your public presence fails to confirm it. Once that path is coherent from recommendation through intake, turn its page structure, entity connections and measurement stages into a template for the next referral category.

References

CrushPress.AI — Boost Law Firm Conversions by Bridging Referral Gaps

March 20, 2026

What the Reddit-SerpApi Scraping Fight Means for SEO Data

If your SEO or AI workflow retrieves Reddit material from Google result pages rather than from reddit.com, you may be tempted to label it indirect public data and move on. The Reddit-SerpApi dispute shows why that shortcut is dangerous: the address you requested is only one part of the legal and operational analysis.

SerpApi is asking a federal court to dismiss Reddit’s amended complaint. Reddit alleges that large amounts of its content were extracted through Google Search. SerpApi counters that it accessed Google pages, that Reddit does not own most user posts, and that Reddit has not adequately established technical circumvention or concrete harm. Those are opposing positions, not judicial findings. Until the court rules, neither side’s argument gives your team permission to treat a similar pipeline as settled law.

Key takeaways

Fetching a Google result page instead of visiting Reddit directly changes the facts, but it does not automatically eliminate copyright or access-control questions.
Audit the actual payload. URLs, rankings, dates, short snippets, full comments, and complete threads create different copying and provenance issues.
Public visibility and technical circumvention are separate questions. A page can be publicly viewable while the collection method still encounters controls that demand legal review.
Content ownership and platform licensing are also separate. A user’s ownership of a post does not, by itself, prove that every third-party reuse is lawful.
Your safest immediate investment is traceability: retain acquisition routes, response fields, control events, transformations, retention rules, and downstream recipients for every dataset.

The dispute turns “scraping” into five separate questions

Five symbolic lenses surround a transparent pipeline carrying abstract content tiles, with a doorway, hand, blank documents, circuit gate, and application modules representing different areas of review.

Calling a system a scraper tells you almost nothing about its legal posture. A useful review separates who holds rights, what was copied, where the response came from, how the collector reached it, and what harm is alleged. Mixing those questions is how a technical description such as “we only queried Google” gets mistaken for a legal conclusion.

Question	Disagreement in the case	What your team should preserve
Who holds rights in the material?	SerpApi relies on Reddit’s user arrangements to argue that users retain ownership and Reddit generally holds a non-exclusive license.	The creator, platform, applicable terms, asserted license, and rights basis for each collected field.
What exactly was copied?	SerpApi argues that the examples identified by Reddit include dates and short fragments that are not protectable expression.	Representative payloads showing whether you store metadata, snippets, comments, threads, media, or combinations of those fields.
Which system returned the data?	SerpApi says it accessed Google Search pages rather than interacting directly with Reddit.	Requested hosts, final URLs, redirects, response headers, collection jobs, and the origin assigned to each field.
Was a technical measure circumvented?	SerpApi says Reddit has not shown an encryption breach or authentication bypass and characterizes the pages it accessed as publicly available.	Authentication states, challenge pages, block responses, rate-limit events, bot defenses, retries, proxy changes, and any code intended to handle them.
What harm followed?	SerpApi argues that Reddit has not adequately pleaded tangible harm caused by its conduct.	Collection volume, retention, redistribution, customer access, substitution for the original service, incident reports, and takedown history.

Keep the five answers independent. If Reddit cannot establish ownership of particular user posts, that may weaken an ownership-dependent theory, but it does not prove that every use of those posts is lawful. If a date or fragment lacks enough expression to be copyrightable, that does not resolve how the system obtained it. If no access control was circumvented, that may answer one DMCA theory without answering every other issue raised by the collection and reuse.

The current procedural posture matters too. A motion to dismiss challenges whether the complaint states legally sufficient claims; it is not a factual finding that the challenged conduct was lawful. If the claims survive, that likewise means they can proceed, not that Reddit has already proved liability.

Why the Google layer is not a legal shield

An indirect pipeline has at least three layers: Google returns a search page, that page contains material derived from Reddit, and your system stores or republishes some part of the result. The host that returned the bytes is relevant, but it does not identify every party with an interest in the content or collection method.

Reddit’s allegation involving a decoy post created solely for Google’s crawler is important for that reason. Reddit uses the alleged appearance of that material to support its account of how the defendants acquired Reddit-derived content through Google. SerpApi answers that an ordinary user could see the same material in public search results. The court still has to decide whether Reddit’s allegations are legally sufficient and, if the case proceeds, what the evidence establishes.

There is also an upstream problem. Google separately alleges that SerpApi bypassed bot protections while scraping licensed search functionality. SerpApi has sought dismissal there as well, arguing that the DMCA is being used to restrict access to public search results. In practical terms, routing collection through a search engine may exchange one platform-access question for another rather than remove the question entirely.

For an SEO, AEO, or GEO system, review both sides of that route. First ask whether the collector was permitted to obtain the search response in the manner used. Then ask what rights and restrictions may follow the Reddit-derived material inside that response. Do not let a clean answer at one layer stand in for an answer at the other.

Run a field-level audit before expanding collection

Gloved hands sort the separated fields of a generic web record into color-coded trays beside a magnifying lens, privacy shield, timer, and source trail.

Your lawyers cannot evaluate a label such as “SERP data,” and your engineers cannot implement advice framed only as “reduce scraping risk.” Give both groups a field-level map of the system. This is not a substitute for legal advice about your particular facts; it is the evidence package that makes useful advice possible.

Map the complete request path. Record the initial host, redirects, rendered page, APIs or browser automation involved, proxy layer, authentication state, and retry logic. Distinguish a request sent to Google from a later request sent to Reddit.
Define the collection unit. List every retained field: query, rank, result URL, title, date, snippet, author name, subreddit, comment text, thread text, media, and cached page. Do not describe a full-thread archive as metadata merely because the job began on a search page.
Attach provenance to each field. Store the page that supplied it, the underlying content platform when known, the collection time, and the transformation applied. A field should not lose its origin when it moves from raw storage into a feature table, embedding index, model corpus, or customer export.
Document the rights theory instead of assuming one. For each field, state why the organization believes it may collect, retain, transform, and distribute that material. Flag any theory that reduces to “it was public” for legal review.
Preserve control events. Log authentication prompts, denied responses, block pages, rate limits, bot challenges, and code changes made in response. Do not instruct a collector to evade a control while waiting for counsel to decide whether the control matters.
Trace every downstream use. Separate internal measurement from customer-facing display, bulk export, dataset resale, AI training, retrieval-augmented generation, and verbatim output. The same input can create a materially different question when the product begins returning the original text to other people.
Build deletion and shutdown paths. You should be able to stop one connector, one field, one customer export, or one corpus without taking the entire product offline. Also identify derived stores, such as embeddings and caches, that would otherwise survive deletion of the raw record.

The resulting audit record can be compact. For each collection job, capture the system owner, requested host, content origin, fields retained, controls encountered, asserted rights basis, retention period, downstream recipients, deletion path, and stop trigger. If your team cannot fill in one of those entries, mark it unknown rather than turning an assumption into policy.

Payload minimization is especially useful while the law remains contested. A rank-monitoring feature may need a result URL and position but not a permanent archive of every Reddit snippet. A citation feature may need a URL and a short display label but not the full discussion. An AI discovery tool may need topical signals while having no product reason to reproduce complete comments. Delete fields that do not support a named function, and stop collecting them at ingestion rather than relying only on later cleanup.

Be equally precise about AI use. “Used for AI” can mean measuring whether Reddit appears in search results, retrieving a passage at query time, generating embeddings, fine-tuning a model, or displaying source text beside an answer. Record those as distinct operations. Otherwise, a rights review performed for internal analytics can silently become the justification for a customer-facing content product it never evaluated.

Plan for the ruling without betting your product on it

A result for either side will be easy to overread. A dismissal based on Reddit’s ownership allegations would not necessarily approve every method of collecting Google results. A ruling focused on short, unprotectable fragments would not automatically cover full comments or threads. A conclusion that the alleged conduct did not amount to circumvention would depend on the controls and access path before the court, not on the generic fact that software performed the request.

A dismissal with prejudice would end Reddit’s claims against SerpApi in this instance. It would not function as a universal license for SERP scraping, Reddit reuse, or AI training. Conversely, if the amended complaint survives dismissal, that would allow the litigation to continue without establishing that every comparable SEO tool is unlawful.

You can make several product decisions now without predicting the winner:

Freeze expansion of any job whose access route, collected fields, or response to technical controls cannot be reconstructed.
Replace blanket claims such as “public data is safe to scrape” with a review that names the host, payload, controls, rights basis, and downstream use.
Separate collection modules by platform and field so one disputed input can be disabled without breaking unrelated search intelligence.
Require approval before an internal dataset becomes a customer export, training corpus, or feature that displays source language.
Give legal and engineering owners the same incident trigger: a new block mechanism, authentication requirement, complaint, takedown request, or material change in collection volume should reopen the review.
Preserve enough technical history to explain what the system did before a dispute begins. Reconstructing access behavior after logs have expired leaves both counsel and engineers working from memory.

Your immediate job is not to decide whether Reddit or SerpApi will win. It is to make your own pipeline explainable and stoppable. If you cannot identify who returned the data, who created it, what you retained, which controls you encountered, and where the material went next, pause the expansion and complete that map first.

References

CrushPress.AI – SerpApi Challenges Reddit’s Allegations in Court Showdown

March 13, 2026

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

Category: Legal

The ruling, the remedy, and the search change are different events

Watch four search surfaces, not one ranking chart

Build an EU search baseline before you need one

Prepare for scenarios without pretending to know the remedy

A penalty arrives without an immediate visible search change

A remedy changes result presentation or access

Ad serving, ranking, or pricing mechanics change

AI Overview or news-publisher action moves on a separate track

Key takeaways and the response plan to use

When the decision is published

References

A referral starts a validation journey, not a straight line

Diagnose the four places trust can break

Build a page that confirms the exact referral promise

Make your authority readable by people, search engines and AI

Remove intake friction and measure each handoff

References

Key takeaways

The dispute turns “scraping” into five separate questions

Why the Google layer is not a legal shield

Run a field-level audit before expanding collection

Plan for the ruling without betting your product on it

References

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