Google DMA Fine: EU Slashes Search & Play Fees ⚡

Search: how Google presents its own services

The Commission said Google put its own shopping, hotel, transport and sports results ahead of rival services in Search. This isn't just about the fact that Google also offers competing services. A company can build its own services and show relevant answers.

The regulatory question is whether Google gives its services preferential treatment in ways that put comparable rivals at a disadvantage. That matters because Search is often the first place people look. If Google's own offering gets a prominent spot while a competitor is harder to find, the competitor may lose opportunities even when its product is competitive.

The Commission ordered Google to treat rival services fairly in Search results. In practice, "fairly" has to become real decisions about what shows up, where it shows up, and whether rival services have a real chance to compete. There isn't one single checkbox - implementation details will determine whether the change genuinely affects choice or just rearranges the page.

Google Play: whether developers can steer users elsewhere

The second fine focused on whether app developers can tell users about cheaper offers outside Google Play. That could include a developer's own website or another app store. The Commission's order required Google to allow developers to steer users away from its store.

The commercial stakes are straightforward. If developers can't clearly point users to an alternative way to buy, the app store tends to keep more control over the transaction. Even if external options are allowed in theory, the rules, fees, or the user journey could still make them feel impractical - meaning permission doesn't translate into something developers can actually use.

Because of that, the Commission's review can't stop at whether a policy was updated. It has to look at what developers can say, what charges apply, and what happens for users when they follow an external option. The key test is whether the route works in practice, not whether it exists "on paper."

The compliance deadline and potential penalties

The Commission gave Google 60 days to comply with the July orders. It also warned that if Google didn't comply, it could face daily penalty payments of up to 5% of Google's average daily worldwide turnover. Those daily penalties are an enforcement mechanism - something that could start if compliance isn't reached, not an automatic charge the moment the deadline passes.

That distinction matters because the €890 million figure relates to the findings in the decision. The daily payments are meant to create pressure to meet the ordered remedies. The current dialogue is part of how the Commission evaluates Google's measures. It doesn't, on its own, prove that the Commission has accepted Google's compliance or that enforcement is finished.

For the broader legal framework, the European Commission's Digital Markets Act overview explains the rules for designated gatekeepers. This dispute is specifically about how those obligations show up in product interfaces and commercial terms.

A dialogue is not the same as approval

Regulatory discussions are normal when implementing complex rules. Companies need to explain technical changes, and regulators need to check whether those changes meet the requirements. So the fact that there's a dialogue doesn't mean Google has already won an exemption - or that the Commission is endorsing every change.

A more useful way to read this is as a checkpoint. Google has made or announced adjustments; the Commission is reviewing them; and third parties will have a chance to weigh in. What happens next depends on whether the measures fix the issues the Commission identified.

There's also a difference between making a change and making one that lasts. A temporary interface test or a one-off fee adjustment can look different from a stable policy that developers can build into. Businesses care most about stability - rules that are clear enough for planning, budgeting, and customer support.

Google's objection is about product trade-offs

When the ruling was announced, Google criticized it. Kent Walker, the company's president of global affairs, said the decision would force Google to remove real-time search features, including live hotel and flight prices. He called it unfair competition.

This is more than a public-relations complaint. Real-time information can make Search more useful, and removing it could lower the quality of results for users. At the same time, a useful feature can also affect the competitive position of services that depend on Search for discovery. The challenge for regulators is to tell the difference between legitimate product quality and conduct that disadvantages rivals unfairly.

Those goals can clash. A remedy that protects competition but makes Search worse for users is a weak outcome. Likewise, preserving every feature but leaving rivals stuck with a structural disadvantage might not address what the Commission was worried about. In other words: the design and evidence matter more than broad claims from either side.

Search remedies need to work at the level of the result page

If a Search change is meant to matter, it has to change what users actually see - and what competitors can actually reach. A surface-level redesign might change labels or layout while leaving the underlying advantage intact. A meaningful remedy might still keep relevant Google features, but create a fairer chance for rival services to be noticed.

So the Commission's review should focus on outcomes like:

• Whether rival services get a fair opportunity to appear for relevant queries.
• Whether Google's own services are treated consistently with comparable alternatives.
• Whether useful information is preserved, including real-time details where appropriate.
• Whether the new presentation is clear enough for users to understand their options.

This isn't a guess about what the Commission will demand. It's a set of practical questions that separates a "looks different" interface tweak from a remedy that changes competitive conditions.

Play changes need to be usable for developers

The same principle applies to Google Play. A lower or revised fee may help, but the actual economic effect depends on the full set of terms. Developers need to understand what they pay, what they must disclose, and how users complete a purchase outside the store.

A usable external-payment route isn't just a link. It involves the messaging shown to users, the steps required to complete the transaction, any fees that still apply, and who handles support and refunds. If these costs and constraints make the alternative unattractive - or too hard to run - then even formal permission won't be worth much commercially.

For smaller developers, predictability is especially important. A large company can afford legal review and can test multiple payment flows. A smaller team often has to commit to one approach and build around it. Stable, clear rules reduce friction; frequent or ambiguous changes raise operating costs for everyone.

Third-party feedback provides a reality check

The Commission's plan to consult companies and other third parties matters because it brings operational evidence into the review. Regulators can check policies and technical submissions, but developers and competing services can describe what actually happens when these changes meet real customers.

That feedback only helps if it's specific. "This is unfair" is less useful than details about how a rival service shows up, which queries are affected, what fees apply to external transactions, and where users drop off during the purchase flow. The closer the feedback is to what people actually see and do, the easier it is to tell the difference between a cosmetic change and a real fix.

For app developers

Developers should model the full economics of any external purchase option, not just a headline fee. That means looking at charges, payment-provider costs, engineering time, customer support, and the impact on conversion. A route that looks cheaper per transaction can still cost more overall if it adds friction or creates extra support workload.

It also helps to document how the current setup works: what disclosures are required, what users see, where purchases can be completed, and what constraints apply. That gives you a baseline for comparing future changes and explaining concrete problems to the relevant parties.

For competing services

Rivals should track visibility across relevant searches rather than relying on a single screenshot or a vague sense that things improved. Search results can vary by query and context. Good comparisons use a repeatable method: record the query, location or market, the way results are presented, and how things change over time.

This kind of evidence doesn't replace the Commission's own assessment. It just makes the competitive impact easier to describe. The same logic applies to app distribution too: keep documentation on the terms, the user journey, and the costs that affect whether an alternative can compete.

For users

Users should expect the product experience to shift as these rules roll out. Some changes may make alternatives easier to find and clearer to reach. Others could affect how real-time information is displayed or how many steps it takes to complete a purchase.

The important test isn't whether the interface looks different. It's whether you can understand your options, compare them, and complete the action you intended without unnecessary friction. Competition rules matter to users when they change choice, price, quality, or control in a way that's tangible - not just theoretical.

A practical test for the next update

When new details appear, check them against four questions:

1. What changed? Identify the real interface, ranking or fee change, not just the announcement.
2. Who can use it? Confirm whether developers and rival services can use the option in practice.
3. What does it cost? Include fees, engineering, operations, and user friction.
4. What evidence shows an effect? Look for measurable changes in access, visibility, or choice.

This approach keeps the debate grounded and helps avoid treating every adjustment as either a complete solution or an outright failure before there's evidence.