Artifact GuideEU DMA

DMA self-preferencing compliance examples

This page helps review product changes that can favour a gatekeeper's own services or products in ranking, indexing, crawling, search results, marketplace display, app-store placement, social feeds, video surfaces, or virtual-assistant answers.

The examples are based on DMA Article 6(5), Article 2 definitions of ranking and search results, recital examples of preferential treatment, and the Article 11 compliance-report template.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
7

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 25, 2026
Overview

The does not prohibit a designated gatekeeper from showing its own product merely because it is its own, or from that product highly when the same transparent, fair, and non-discriminatory conditions produce that result. It prohibits more favourable treatment of the gatekeeper's own services or products than of similar third-party services or products in ranking and related indexing and crawling. Start the review with the listed core platform service and product surface, identify the comparison set, and test the criteria, eligibility rules, data inputs, manual interventions, presentation, and outcome. The examples below are Sorena review patterns derived from Article 6(5) and the recitals, not Commission decisions or approved safe harbours.

Section 1

What Article 6(5) covers

Scope the review to a designated gatekeeper, a core platform service listed in the designation decision, and a surface where goods, services, apps, videos, marketplace offers, social posts, , or assistant responses receive relative prominence.

The DMA definition of is broad. It covers relative prominence in online intermediation services, online social networking services, video-sharing platform services, virtual assistants, and relevance in online , regardless of the technical presentation method and even where only one result is communicated.

  • In scope: , related indexing, related crawling, display prominence, ratings, linking, voice results, and other measures with equivalent effect when they favour the gatekeeper's own service or product.
  • In scope: , including paid or unpaid results, direct answers, embedded products or services, and information displayed alongside organic results.
  • In scope: products or services offered by the gatekeeper itself or through a business user it controls, compared with similar third-party products or services on the same covered surface.
  • Out of scope for this page: general app uninstall, switching, interoperability, advertising transparency, and data-access obligations unless the same release also changes , indexing, crawling, or display prominence.
Section 2

Application examples derived from the DMA

Use these examples as review patterns, not as a substitute for checking the exact designated core platform service and release facts. Each example should be tested against whether the gatekeeper's own product receives a better position or equivalent advantage than a similar third-party product.

A compliant implementation should be able to explain the condition, apply it consistently to similar own and third-party offerings, and preserve product evidence showing that the rule was followed before and after release.

On 23 July 2026, the Commission adopted a final Article 6(5) non-compliance decision against Google. It found that Google gave its own shopping, hotel, transport, and sports services more prominent Google Search treatment, including top placement and enhanced visuals and filters that similar third-party services did not receive. The Commission imposed a EUR 460 million fine for that breach and ordered Google to end the non-compliance. This is an official enforcement example; the remaining examples are Sorena review patterns, not Commission-approved implementations.

  • Online search: a direct answer, specialised result group, embedded widget, or vertical box should not reserve better placement for the gatekeeper's own service when similar third-party services compete for that same result surface.
  • Marketplace search or browsing: , badges, filters, default sorting, sponsored/organic separation, and product-card display should not give the gatekeeper's own retail offer or controlled seller a more favourable position than similar third-party offers through legal, commercial, or technical means.
  • App store distribution: , editorial collections, category rankings, recommendation modules, ratings display, and install prompts should use transparent, fair, and non-discriminatory conditions where the gatekeeper's own app competes with similar third-party apps.
  • Video-sharing or social feeds: feed prominence, recommendation slots, preview formats, labels, and linking should not give the gatekeeper's own videos, services, or controlled business users preferential treatment over similar third-party offerings.
  • Virtual assistant or voice result: a single spoken answer, default service suggestion, link, or handoff can still be under the DMA, so the release review should test whether the gatekeeper's own product is favoured when similar third-party products are available.
Section 3

Product evidence to keep for each example

The evidence file should let a reviewer reconstruct the user journey, the comparison group, and the reason each own or third-party result received its position. Keep pre-release and post-release evidence together because small interface, policy, or algorithm changes can create a issue.

Evidence should be specific to the surface. A generic competition-policy memo is not enough if the product change affected crawling priority, index inclusion, feature eligibility, result grouping, default sort order, result-card format, ratings treatment, or a voice-assistant handoff.

  • Surface inventory: the core platform service, affected route or interface, countries or user groups, own services/products on the surface, and similar third-party services/products.
  • explanation: the parameters, eligibility rules, labels, weights, feature gates, quality signals, policy rules, and manual interventions used to rank, classify, or make results more prominent.
  • Comparison evidence: sampled queries or journeys, own-versus-third-party placements, before/after screenshots, crawl/index logs where relevant, experiment results, and known exceptions.
  • Fairness controls: tests showing that neutral quality, safety, legal, or relevance criteria apply consistently and do not mask preferential treatment for the gatekeeper's own offering.
  • Change record: product requirement document, engineering ticket, legal review, release approval, rollback criteria, monitoring dashboard, and owner for post-release complaints or anomalies.
Section 4

Article 11 reporting linkage

Article 11 connects product evidence to the gatekeeper's formal compliance reporting. Within 6 months after designation, the gatekeeper must provide the Commission with a detailed and transparent report on measures implemented to ensure compliance with Articles 5, 6, and 7, and must publish and provide a non-confidential summary. The report and summary must be updated at least annually.

For examples, do not wait until annual reporting to assemble evidence. Every release that changes , indexing, crawling, or display prominence should produce report-ready material that can be lifted into the Article 11 compliance report, the non-confidential summary, or an annex.

  • Map each Article 6(5) control to the affected core platform service and the specific surface.
  • Maintain a concise explanation of the measure, the implementation date, product/service/device scope, geographic scope, and the pre-release situation it replaced.
  • Keep evidence of customer-experience changes such as interface changes, choice screens, warning messages, system updates, available functionality, and journeys to access functionality.
  • Prepare a non-confidential version that is self-standing enough for third parties to provide meaningful input without exposing protected confidential information.
  • When the compliance report is updated, highlight differences from the previous version, including relevant annex changes.
Section 5

Release-review controls

Build the review into product release gates for search, marketplace, app-store, feed, video, virtual-assistant, and indexing systems. The control should apply before launch, during experiments, when manual boosting rules change, and when a new gatekeeper-owned product enters a ranked surface.

The release owner should block launch or escalate where the team cannot identify similar third-party offerings, cannot explain why the gatekeeper's own result receives its position, or cannot produce neutral criteria that apply to own and third-party products alike.

Does DMA Article 6(5) only apply to classic search-result ?

No. The DMA definition of covers relative prominence across listed core platform service types and Recital 52 says ranking includes display, rating, linking, voice results, and one-result experiences. A review should therefore cover , marketplace display, app-store placement, social feeds, video recommendations, and virtual-assistant answers when the other Article 6(5) facts are present.

What should a release team save to support Article 6(5) compliance?

Save the affected core platform service and surface, the own and third-party comparison set, or prominence parameters, screenshots or journey samples, before/after results, engineering and policy changes, legal review, release approval, monitoring plan, and the Article 11 report-ready explanation.

  • Trigger: any change to crawling, indexing, signals, result grouping, default sort, prominence labels, recommendations, voice answers, marketplace badges, editorial placement, or feature eligibility.
  • Reviewer set: product owner, or search engineering owner, competition counsel, data or analytics owner, and compliance-report owner.
  • Required question: does the change make a gatekeeper-owned or controlled product easier to discover, more prominent, more trusted, or more likely to be selected than a similar third-party product?
  • Required test: compare own and third-party results across representative journeys, including queries or contexts where the gatekeeper's own product is eligible and where it is not.
  • Post-release monitor: track complaints, anomalies, manual overrides, policy exceptions, and metrics that show own products gaining prominence after the release.
Primary sources

References and citations

digital-markets-act.ec.europa.eu
Referenced sections
  • Official 23 July 2026 source for the final Article 6(5) non-compliance finding, the more prominent placement and presentation given to Google's own services, the EUR 460 million self-preferencing fine, and the order to end the breach.
digital-markets-act.ec.europa.eu
Referenced sections
  • The template links compliance reporting to technical, customer-experience, remuneration, and terms changes.
"any changes to the customer experience made in connection with the implementation of the measure concerned"
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission page for designated gatekeepers, core platform services, designation decisions, and case references.
"In total, 23 core platform services provided by those gatekeepers are currently designated."
eur-lex.europa.eu
Referenced sections
  • Article 6(5) is the binding self-preferencing rule for ranking and related indexing and crawling; Article 2 defines ranking broadly enough to cover presentation, organisation, communication, and single-result experiences.
"The gatekeeper shall not treat more favourably, in ranking and related indexing and crawling, services and products offered by the gatekeeper itself"
eur-lex.europa.eu
Referenced sections
  • Article 11 sets the compliance-report timing, non-confidential summary, and annual update obligation.
"the gatekeeper shall provide the Commission with a report describing in a detailed and transparent manner the measures it has implemented"
eur-lex.europa.eu
Referenced sections
  • Recitals 51 and 52 explain the covered service contexts and that ranking includes display, rating, linking, voice results, one-result experiences, and measures with equivalent effect.
"software applications which are distributed through software application stores, or videos distributed through a video-sharing platform"
Related guides

Explore more topics

DMA Anti-Circumvention Design Review for Gatekeeper Product Changes
Review DMA Article 13 anti-circumvention risks in gatekeeper product, interface, contractual, commercial, and technical changes with obligation mapping and evidence records.
DMA Article 11 Compliance Report Template FAQ
How gatekeepers should use the DMA Article 11 compliance report template to document obligation-by-obligation measures, evidence, updates, and non-confidential summaries.
DMA Article 6 Business User Data Access Guide
Official source guide to EU Digital Markets Act Article 6 data access for business users, end users, authorised third parties, consent boundaries, and evidence handoffs.
DMA Article 6(7) and Article 7 interoperability obligations
Official source guide to DMA interoperability duties: Article 6(7) operating-system feature access, Article 7 messaging interoperability, request handling, security conditions, and compliance evidence.
DMA Articles 5, 6 and 7 obligations mapped to CPS evidence
Map EU Digital Markets Act Articles 5, 6 and 7 obligations to affected core platform services, product evidence, legal owners, and Article 11 compliance-report artifacts.
DMA compliance program and monitoring for gatekeepers
Build a DMA compliance program around Article 8 effective compliance, Article 11 reporting evidence, Article 13 anti-circumvention controls, and Article 28 compliance-function governance.
DMA Core Platform Service Scoping
Scope EU Digital Markets Act core platform services by service category, designation evidence, user thresholds, and Form GD service-boundary records.
DMA core platform services FAQ
FAQ on EU Digital Markets Act core platform services: Article 2 service categories, gatekeeper designation evidence, user thresholds, service scoping, and Article 11 reporting.
DMA CPS Obligation Matrix Workflow: Articles 5, 6, 7 and Article 11 Evidence
Build a DMA core platform service obligation matrix that links each designated CPS to Articles 5, 6 and 7 duties, product owners, designation evidence, Article 11 report artifacts and review gates.
DMA designation intake workflow for gatekeeper notifications
Build an official source DMA designation intake record covering core platform service classification, Article 3 thresholds, Form GD evidence, Commission handoff, and Article 11 readiness.
DMA enforcement, penalties, and remedies: Commission powers and evidence
Follow DMA enforcement from investigation and preliminary findings to non-compliance decisions, fines, daily payments, interim measures, commitments, and remedies.
DMA Gatekeeper Compliance Checklist for Articles 5, 6, 7 and 11
A cited EU Digital Markets Act checklist for designated gatekeepers: core platform service scope, Article 5/6/7 controls, Article 11 report evidence, anti-circumvention checks, and review gates.
DMA Gatekeeper Designation Guide: Article 3 thresholds, Form GD, and Article 11 readiness
A cited EU Digital Markets Act guide for assessing Article 3 gatekeeper thresholds, scoping core platform services, preparing Form GD evidence, handling rebuttal annexes, and planning Article 11 compliance reporting.
DMA gatekeeper thresholds: what counts and when to notify
Standalone FAQ on the EU Digital Markets Act gatekeeper thresholds, Article 3 notification timing, Form GD evidence, and active user-count methodology.
DMA interoperability requests: Article 7 and Commission guidance
How DMA Article 7 messaging interoperability requests work, including phased functions, the three-month operational deadline, reference offers, evidence, and safeguards.
DMA penalties and fines: caps, triggers, and enforcement evidence
Compare DMA Article 30 fine ceilings, the narrow 20% repeat test, 1% procedural fines, and Article 31 daily payments, with decision-specific examples.
DMA Product Change Review Workflow for Articles 5, 6, 7, 11 and 13
Review DMA-relevant product releases for Article 5, Article 6, Article 7, anti-circumvention, Article 11 evidence, and product-owner/legal signoff.
DMA vs Data Act: gatekeeper duties compared with EU data-sharing rules
Compare the EU Digital Markets Act and EU Data Act by scope, actors, data access, interoperability, reporting, evidence, and enforcement without merging distinct obligations.
DMA vs DSA: Digital Markets vs Services Act
Compare the EU Digital Markets Act and Digital Services Act by covered services, regulated actors, core duties, reporting, dates, evidence, and enforcement.
DMA vs EU competition law: gatekeeper obligations, Article 11 evidence, and enforcement
Compare the EU Digital Markets Act with EU competition law: ex ante gatekeeper and core platform service duties, Articles 5 to 7, Article 11 reports, penalties, and evidence records.
DMA vs GDPR: gatekeeper data obligations compared
Compare DMA gatekeeper duties with GDPR rules for personal-data processing, consent, lawful basis, portability, accountability evidence, and enforcement.
EU Digital Markets Act Article 11 Evidence Calendar
Build a DMA Article 11 compliance-report calendar with the correct designation trigger, service annexes, evidence owners, annual updates, and publication gates.
EU Digital Markets Act checklist for gatekeeper compliance
A source-grounded Sorena DMA checklist for designated gatekeepers and core platform services, covering scope, Articles 5, 6 and 7 obligations, Article 11 reporting, evidence, anti-circumvention, and governance.
EU Digital Markets Act compliance: gatekeeper obligations and evidence
DMA compliance guide for designated gatekeepers: core platform service scoping, Articles 5, 6 and 7 controls, Article 11 reports, anti-circumvention checks, interoperability evidence, and enforcement risk.
EU Digital Markets Act deadlines and compliance calendar
Calculate DMA notification, designation, service-compliance, Article 11 reporting, concentration-notice, and profiling-audit deadlines from the correct legal trigger.
EU Digital Markets Act FAQ: gatekeepers, DMA obligations, reports, and enforcement
Concise FAQ on the EU Digital Markets Act for gatekeeper designation, core platform services, Articles 5, 6 and 7 obligations, Article 11 reports, interoperability, business-user data access, compliance evidence, and enforcement.
EU Digital Markets Act requirements for gatekeepers
DMA requirements for designated gatekeepers: core platform service scope, Articles 5, 6 and 7 obligations, Article 11 reporting, anti-circumvention, evidence, remedies, and fines.
EU Digital Markets Act timeline: application, designation, reporting, and review
DMA timeline separating fixed legal dates, threshold and designation clocks, recurring reports, service-specific decisions, final enforcement, and the first Article 53 review.
EU DMA Applicability Test: gatekeeper thresholds, core platform services, and evidence
Test whether the EU Digital Markets Act may apply to a platform service using the DMA gatekeeper criteria, core platform service categories, EU user thresholds, notification steps, and evidence records.
EU DMA Article 11 Compliance Reporting Guide
Official source guide to EU Digital Markets Act Article 11 compliance reports: report purpose, template evidence, non-confidential summaries, annual updates, and submission steps.
EU DMA do's and don'ts for product teams
Product release checks for designated DMA gatekeepers: Article 5, 6 and 7 obligations, anti-circumvention review, data access, interoperability, self-preferencing and Article 11 evidence.
What do DMA Articles 5, 6, and 7 require from gatekeepers?
FAQ explaining how EU Digital Markets Act Articles 5, 6, and 7 group gatekeeper obligations, what product evidence they require, and how Article 11 reporting connects.