What the Commission's Google DMA findings cover

On 23 July 2026, the European Commission found Google non-compliant with the DMA over Google Search and Google Play. The findings concern self-preferencing and restrictions on steering consumers to other purchase channels. A separate Commission guidance on Android AI interoperability and Search data sharing came on 16 July.

What did the Commission find?

The Commission announced two decisions finding Google in breach of the Digital Markets Act, or DMA. One addressed self-preferencing on Google Search: the Commission said Google favoured its own services. The other addressed Google Play, where it found restrictions on businesses directing consumers to alternative purchase channels, often cheaper ones. The supplied account does not identify the services or businesses affected, nor does it explain the detailed reasoning behind either decision.

What does steering mean here?

Steering means a business directs a consumer to another channel to complete a purchase. The Commission’s account says Google put restrictions in place that limited businesses’ ability to do this through Google Play. It does not describe the restrictions themselves or explain which alternative channels were covered. As a result, the finding identifies the issue but does not show how it applies to any particular business.

What is self-preferencing?

In this context, self-preferencing means a service favours its own services. The Commission said Google breached the DMA through self-preferencing on Google Search. The supplied source does not state how that preference appeared, which results or services were involved, or what evidence the Commission relied on. Those details would be needed to assess the decision’s precise implications for businesses using Search.

What was the Android guidance about?

On 16 July 2026, the Commission provided Google with guidance about AI interoperability on Android and sharing Google Search data under the DMA. Interoperability means that different systems or services can work together. The source does not set out technical requirements, a deadline, or the steps Google was asked to take. It also does not describe this guidance as one of the non-compliance decisions announced on 23 July.

Has Google responded, and what happens next?

The supplied source material contains no response from Google to the findings or guidance. It also gives no remedy, penalty, appeal, or compliance timetable, so those details remain unknown on this record. Further published information would be needed to explain the required changes and how the Commission will assess compliance. The immediate distinction is between the 16 July guidance and the two 23 July findings.