Google’s €890M DMA fines: what “self‑preferencing” really means for your SEO, app growth, and AI-era visibility
The EU just hit Google with €460M for Search self-preferencing and €430M for Google Play steering restrictions under the DMA. Here’s what could change in SERPs and app distribution—and what SMEs and agencies should do now to protect traffic, conversions, and AI search visibility.
Author: Marius Dosinescu, AYSA.ai
Europe just delivered one of the clearest signals yet that the “platform advantage” era is entering an enforcement phase. Under the EU Digital Markets Act (DMA), the European Commission issued two separate fines against Google—€460 million related to Google Search and €430 million related to Google Play—totaling €890 million. The reporting that brought this to the search industry’s attention (and summarized the Commission’s position) was published by Search Engine Land.
This isn’t just a “big tech vs. regulators” headline. If you run an ecommerce store, a hotel, a clinic, a local service business, a SaaS company, or an agency—your visibility and acquisition costs are shaped by how Google can (and cannot) surface its own modules, and how mobile ecosystems can (and cannot) restrict your relationship with customers.
In this editorial, I’m going to translate what these fines mean in operational terms: what could change in Search layouts, what the “steering” issue in Google Play implies for customer ownership, how AI-driven discovery complicates all of it, and what an SME can actually do next week to reduce risk.
Table of contents
- Concise summary
- Key takeaways for SMEs and agencies
- What happened: two DMA fines, one theme
- DMA context: why the EU cares about default advantages
- Self-preferencing in Search: the practical SEO meaning (not the legal one)
- What might change in Google Search (and what probably won’t)
- Who is most exposed: shopping, hotels, transport, sports—and everyone adjacent
- Google Play and “steering”: why this is bigger than app developers
- Where AI search collides with DMA: visibility without clicks, answers without attribution
- What can go wrong: the three failure modes I see coming
- A practical monitoring plan: what to measure weekly (and why)
- A 60-day action plan for SMEs (realistic, not theoretical)
- Where AYSA.ai fits: monitoring + approved execution, not “advice only”
- What to do next
- Sources and further reading
Concise summary
The European Commission fined Google €460M for allegedly giving preferential placement and presentation to its own services in Search (shopping, hotels, transport, sports) and €430M for Google Play practices that allegedly restrict how developers can communicate offers and contract with users outside Google Play. Google has 60 days to comply or risk additional periodic penalty payments (as described in the Search Engine Land coverage, which quotes the Commission’s position). For businesses, the implication is simple: Search layouts and distribution rules are now a regulated surface. That will increase volatility and regional differences, which means you need tighter Monitoring, faster execution, and a plan that doesn’t assume “Google will always look the same.”
Key takeaways for SMEs and agencies
- This is not only about rankings. The enforcement focus is about preferential treatment through placement, visuals, filters, and modules—not only the blue-link order.
- Expect more EU-specific SERP behavior. If you operate in Europe (or depend on European traffic), anticipate more layout experiments and compliance-driven changes.
- App distribution is a customer ownership issue. “Steering” restrictions influence whether you can move a customer from platform-controlled checkout to your own relationship (billing, support, retention).
- AI discovery makes Attribution harder. Even if self-preferencing decreases in some modules, AI answers can still compress Clicks; your job becomes: be the best source the model wants to cite, and capture demand downstream.
- Operational excellence wins. The edge isn’t knowing the news; it’s running a weekly loop: monitor → identify changes → prepare improvements → get approval → ship.
- AYSA’s role: AYSA is built for that loop—monitoring, preparing recommended website changes, asking for approval, and executing the accepted improvements (instead of leaving you with a PDF and a shrug). See: Monitoring and AI Search Visibility.
What happened: two DMA fines, one theme
According to Search Engine Land’s coverage of the Commission’s announcements, the European Commission issued:
- €460 million related to Google Search, for alleged self-preferencing: giving Google’s own services (shopping, hotels, transport, sports) preferential treatment over third parties.
- €430 million related to Google Play, for alleged non-compliance with obligations affecting developers’ ability to communicate offers and contract with users outside Google Play, and for steering-related fees and fee duration that the Commission viewed as non-compliant.
The Commission also set a compliance clock: 60 days to comply, or Google risks periodic penalties (as described in the same coverage).
Here’s the business translation: the EU is telling a gatekeeper, “You can’t write the rules in a way that permanently advantages your own products inside the marketplace you control.”
Now for the uncomfortable part: if your acquisition depends on that marketplace—Search or an app store—your revenue is tied to how those rules evolve, how quickly compliance is implemented, and how aggressively competitors respond.
DMA context: why the EU cares about default advantages
The DMA is designed to regulate “gatekeepers”—companies whose platforms function like essential infrastructure for reaching customers. The core idea is not controversial in business terms: when one company both (1) runs the marketplace and (2) competes inside it, there is a built-in incentive to tilt outcomes.
You don’t need to take a political position to recognize the practical reality: regulators are now trying to shape incentives and outcomes in digital markets where switching costs are high and discovery is centralized.
If you want to read the primary text (not commentary), start with the official DMA regulation in EU law: Regulation (EU) 2022/1925.
Two implications matter for operators:
- Compliance is dynamic. The rules don’t freeze the product; they pressure the product to evolve.
- Enforcement creates product churn. Even if the “end state” is fairer, the transition period is messy—experiments, rollbacks, regional differences.
Self-preferencing in Search: the practical SEO meaning (not the legal one)
“Self-preferencing” sounds like legal jargon, but the mechanism is very simple: when Google has a competing product, it may be displayed in a way that wins attention and clicks—because Google controls the layout.
Search Engine Land’s summary of the Commission’s position describes preferential treatment via prominence at the top of the page and enhanced visuals/filters for Google’s own services compared to third parties.
For SEO, this matters because modern Search is not a list. It’s a page composed of components:
- Organic listings (traditional SEO)
- Rich results (schema-driven enhancements)
- Maps/local packs
- Shopping modules
- Hotel modules
- Sports widgets
- “People Also Ask” and other question refinements
- AI-generated answers in some experiences (depending on region and query)
So when regulators talk about “preferential treatment,” they’re not only talking about whether your page is #3 or #5. They’re also talking about:
- Pixel real estate: are you pushed below the fold?
- Visual hierarchy: does a module have images, ratings, price filters, or interactive controls?
- User flow: does the click keep the user inside Google’s own journey?
That’s why many businesses feel “my SEO is fine but traffic is down.” Their rankings didn’t collapse; the page composition changed.
What might change in Google Search (and what probably won’t)
No one outside Google and regulators can promise exact SERP changes. We also shouldn’t pretend we know the precise remedies before they’re implemented. But we can be realistic about the types of changes that often appear in compliance-driven product updates:
1) More explicit equal treatment in modules
If the Commission’s position is that third-party services should be treated fairly and non-discriminatorily relative to Google’s own services, then one plausible response is changes to how third parties are included and presented in module-like areas (shopping/hotels/etc.). That could mean:
- More third-party inclusion in “comparison” experiences
- Different labeling or separation of Google-owned vs third-party results
- Adjusted ranking and eligibility criteria inside modules
2) More regional SERP fragmentation
DMA applies in the EU. That can translate into different UI behavior in European markets versus the U.S. or other regions. For global businesses, this is an analytics problem:
- EU traffic may behave differently even for the same queries
- EU conversion paths may change if SERP modules drive different entry pages
- EU competitors may suddenly gain more surface area
3) What probably won’t change: your need to be the best answer
Even in a more “neutral” marketplace, competition doesn’t decrease; it increases. If third parties get more visibility, you’ll be competing with more capable aggregators and vertical specialists—especially in hotels, shopping, and transport.
The evergreen truth remains: your content, your product pages, your entity signals, and your conversion experience still decide whether visibility turns into revenue.
Who is most exposed: shopping, hotels, transport, sports—and everyone adjacent
The Search-related fine specifically references shopping, hotels, transport, and sports in the Commission language quoted by Search Engine Land. Those verticals are obvious hotspots because users often want structured comparisons, filters, and quick answers.
But exposure doesn’t stop there. If you’re adjacent, you’re still impacted:
- Retail brands that rely on product discovery (not just Branded Search)
- Local businesses whose demand is influenced by “best of” lists, directories, and aggregators
- Publishers and affiliates who monetize “top X” comparison pages
- SaaS companies where category searches often trigger comparison-style results and AI answers
Here’s a simple rule: the more your customer journey starts with “compare,” the more you should care about marketplace neutrality and SERP composition.
Concrete SME scenario: a boutique hotel in Barcelona
Imagine a 40-room boutique hotel in Barcelona that historically got steady bookings from Google search queries like:
- “boutique hotel gothic quarter”
- “best hotel near [landmark]”
- “hotel deals Barcelona September”
What can happen over the next quarter?
- If hotel modules change to include more third-party options, the hotel could gain visibility in new placements—or lose it to stronger OTAs and meta-search providers.
- If the layout changes, the hotel’s organic listing might drop below more interactive elements, reducing clicks even if the rank stays similar.
- If AI summaries answer “best areas to stay” and recommend properties, the hotel needs stronger entity signals and content clarity to be cited or recommended.
The hotel’s winning strategy is not “hope regulators help me.” It’s: strengthen direct demand, improve eligibility for structured surfaces, and run tighter monitoring so you catch layout shifts early.
Google Play and “steering”: why this is bigger than app developers
The Google Play fine is easy to ignore if you don’t run an app. Don’t. The Commission language summarized by Search Engine Land focuses on whether developers can freely communicate/promote offers and conclude contracts with users outside Google Play, including through other app stores, and whether steering-related fees and fee duration exceed what the Commission views as DMA-compliant.
At a business level, the issue is: who owns the customer relationship?
When platforms restrict steering, they make it harder to:
- Move a user to a cheaper payment rail
- Offer discounts that bypass platform fees
- Bundle products across web + mobile
- Collect first-party data with clearer consent flows
Even if you’re not an app developer, the logic applies to any platform dependency—marketplaces, social commerce, or search experiences that keep users “inside” the platform journey.
Why this matters to ecommerce and local services
Many ecommerce brands and local services are building lightweight apps for repeat customers, loyalty, appointment management, or subscriptions. If distribution and payments stay platform-controlled, margins and retention strategies are constrained.
DMA enforcement increases the probability of alternative flows becoming more viable in the EU. But again, businesses shouldn’t wait for the perfect policy outcome. The right move is to build a channel mix where your website, email, and organic brand demand matter—not only app store algorithms.
Where AI search collides with DMA: visibility without clicks, answers without attribution
The DMA conversation is about marketplace fairness. AI search introduces a separate (but overlapping) problem: the interface itself is changing from “results” to “answers.”
Even if self-preferencing is reduced in certain modules, AI-generated answers can still:
- Compress clicks for informational queries
- Shift traffic from “research pages” to “transaction pages” (or remove traffic altogether)
- Change what “ranking” means—your brand can be recommended without a visible link, or cited inconsistently
This is where AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) stop being buzzwords and become operational disciplines. You need to structure your site so it’s easy for machines to understand:
- Who you are (entities)
- What you sell/offer (products/services with clear attributes)
- Where you operate (locations, service areas)
- Why you’re credible (proof, policies, expert content, reviews handled correctly)
AYSA’s approach to AI-era discovery is built around that: measure your brand’s presence in AI-driven surfaces and then execute the improvements on your site with approval-driven workflows. Start here: AI Search Visibility.
What can go wrong: the three failure modes I see coming
When big platform rules change, most businesses don’t lose because of the change itself. They lose because of how they respond. Here are the three failure modes I expect to be common.
Failure mode 1: “Wait and see” until the quarter is already lost
Compliance windows (like the 60 days referenced in the Search Engine Land coverage) are short. SERP/UI changes can be rolled out in phases. If you wait for “certainty,” you’ll be reacting after competitors already adapted.
Failure mode 2: Misattribution—blaming SEO when the page changed
Many teams will see traffic drops and assume they need more content or more links. Sometimes yes—but often the issue is:
- CTR changes caused by layout shifts
- Competitor modules gaining prominence
- Your snippet losing rich result enhancements because of technical drift
The fix starts with measurement discipline, not guesswork.
Failure mode 3: Channel monoculture
Some brands are “Google-only.” Some are “app-only.” Some are “marketplace-only.” Every enforcement action is a reminder that dependency is a risk. You don’t need to abandon Google—you need to balance it with owned assets and repeatable processes.
A practical monitoring plan: what to measure weekly (and why)
If you run an SME, you can’t spend your life watching SERPs. But you also can’t outsource your future to quarterly reports. The right middle ground is a weekly monitoring rhythm focused on leading indicators.
1) SERP composition checks (not just rank)
- For your top revenue queries, record what appears above organic: shopping/hotel widgets, local packs, “things to know,” AI answers, etc.
- Track changes by region (EU vs non‑EU, or country-by-country if that’s how you operate).
2) CTR and impression trends by query class
In Google Search Console, watch for “same impressions, fewer clicks.” That often signals a layout/attention shift, not a relevance drop.
3) Landing page mix changes
When modules shift, the pages that earn traffic can change. If your blog traffic drops but product pages gain, your conversion strategy must adjust—fast.
4) AI visibility checks
Track whether AI experiences recommend your brand in your category and whether citations align with the pages you want to win. AYSA supports this type of monitoring and turns findings into execution-ready recommendations: AYSA Monitoring.
5) Technical drift and structured data health
When SERP features become more competitive, schema and clean site structure become table stakes. The goal isn’t “schema everywhere.” The goal is: schema where it increases eligibility for the surfaces that matter.
If your team needs an overview of AI SEO tooling that supports this operational loop, start here: AI SEO Tools.
A 60-day action plan for SMEs (realistic, not theoretical)
The Commission’s stated compliance timeline (60 days, as covered by Search Engine Land) is a useful forcing function even if you’re not Google. Use it as your own cadence.
Days 1–7: establish baseline and risk map
- List your top 20 non-branded queries by revenue contribution (even if indirect).
- Capture current SERP layouts descriptively (modules present, above-the-fold composition). Don’t rely on memory.
- Segment by region (EU vs non‑EU) if you have international traffic.
- Define your “visibility surfaces”: organic listings, local pack, product results, hotel results, etc.
Days 8–21: shore up eligibility and clarity
- Improve page clarity: what you offer, who it’s for, pricing cues, location/service area, policies.
- Prioritize structured data for the pages that compete in module-heavy SERPs (products, locations, organization, FAQs where appropriate).
- Strengthen internal linking so your key money pages are unmistakably important.
- Fix technical issues that suppress rich results (template errors, duplication, slow pages, indexation bloat).
Days 22–45: build resilience beyond the SERP
- Create demand capture assets: comparison pages, “why choose us,” use cases, and decision guides that convert.
- Build owned retention: email capture, SMS where appropriate, loyalty for repeat purchase.
- Improve conversion on entry pages: if Google sends fewer clicks, every click must convert more often.
Days 46–60: operationalize monitoring + execution
- Set weekly KPIs: SERP composition changes, CTR, AI visibility, conversion rate by landing page type.
- Create a change pipeline: recommendations prepared, approvals gathered, changes shipped, outcomes measured.
This is the gap most SMEs fall into: they can see changes, and they can talk about changes—but they can’t ship changes consistently. That’s exactly what we built AYSA to fix.
Where AYSA.ai fits: monitoring + approved execution, not “advice only”
Most SEO tooling stops at insights. Most agencies stop at recommendations. But DMA-driven volatility and AI-era discovery require an execution system that behaves more like operations than “marketing projects.”
AYSA is designed as an SEO/AEO/GEO execution system:
- Monitors your site and visibility signals over time (not a one-off audit). See Monitoring.
- Prepares recommended website changes (technical, content, structural) to improve performance.
- Asks for approval before changes go live—so you stay in control.
- Executes accepted changes, turning strategy into shipped work.
That model matters specifically in moments like this. When Search layouts or distribution rules change, the businesses that win are the ones that can:
- Detect the change early
- Decide what it means for their funnel
- Ship improvements quickly without breaking the site
If you want to explore how AYSA supports AI-era visibility (not only classic SEO), start with AI Search Visibility. If you want to evaluate fit and cost, see Pricing. For ongoing thinking and tactical guidance, browse the AYSA blog.
What to do next
- Pick 10 revenue-driving queries and document the SERP layout in your core EU market(s) and your main non‑EU market.
- Check Search Console for CTR compression: same impressions, fewer clicks.
- Audit “module eligibility” pages: product pages, hotel/service pages, category pages—ensure they’re clear, fast, and structured.
- Decide your dependency risk: what % of new customers come from Google? from app stores? from marketplaces?
- Set a weekly monitoring cadence and assign an owner (internal or agency).
- Adopt an execution loop: monitor → recommend → approve → ship. If you’re missing this, evaluate AYSA: Monitoring and AI SEO Tools.
Sources and further reading
- Search Engine Land – Google fined €460 million over self-preferencing Search and €430 over Google Play (industry coverage used as the primary research lead for this editorial)
- EUR-Lex – Regulation (EU) 2022/1925 (Digital Markets Act) (primary legal text)
- AYSA – AI Search Visibility
- AYSA – Monitoring
- AYSA – AI SEO Tools
- AYSA – Pricing
- AYSA – Blog
Disclosure note: This editorial uses the provided Search Engine Land article as a research lead and cites it directly. Where implementation details are not publicly verified in the provided research context, I’ve framed them as analysis rather than fact.
Continue the AI search topic inside AYSA.
Use these pages to connect the article with AI SEO tools, AI visibility monitoring, AI Overviews and approved website execution.
Turn this topic into a website action plan.
Use these AYSA hubs to move from reading to technical fixes, AI visibility monitoring, research, glossary context and approval-first SEO execution.
