GDPR Right to Be Forgotten for News Articles: How to File a Request That Survives Google's Review

What GDPR Actually Gives You (and What It Doesn't)

GDPR Article 17 creates a right to erasure - see also GDPR.eu - Right to Erasure explained for a plain-language overview. For news articles indexed in Google, this means de-indexing from EU versions of Google (google.de, google.fr, google.es, and all other EU national domains) and, under UK GDPR, from google.co.uk. It does not mean removal of the article from the publisher's website, it does not apply to google.com (the US version), and it does not affect other search engines by default.

The right is real and it is enforceable. Google processes well over 100,000 RTBF requests annually and grants a meaningful portion of them. Approval rates for news article de-indexing vary significantly depending on how the request is framed. Well-argued requests from private individuals about genuinely outdated content succeed at a substantially higher rate than vague submissions that assert privacy without demonstrating it. For a detailed look at how this process works, see our guide on whether does Google remove negative articles.

A note on UK GDPR post-Brexit: the UK incorporated the EU GDPR into domestic law as UK GDPR, effective January 1, 2021. For the purposes of right to be forgotten requests, UK GDPR is functionally identical to EU GDPR. UK residents use the same grounds, the same process, and file DPA complaints with the ICO rather than an EU authority. Nothing changed substantively for this purpose when the UK left the EU.

The Six Grounds: Which One Actually Applies to Your News Article

GDPR Article 17 lists six distinct grounds for erasure. Most people filing RTBF requests for news articles cite the wrong one, which is one of the primary reasons requests fail. For news articles, only two grounds are typically viable.

Ground 1: Data no longer necessary for the purpose collected (Article 17(1)(a))

The full text reads: "the personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed." This is the strongest ground for old arrest articles, outdated business information, or articles about private individuals whose circumstances have changed materially since publication.

"Necessary" is evaluated against the journalistic purpose at the time of publication, not the present. A 2013 local news article about a dismissed case may have served a legitimate journalistic purpose when it was written. The ongoing indexing of that article in 2026 may not be "necessary" for any current journalistic purpose, particularly if the underlying situation has been fully resolved and the person has no ongoing public role.

How to argue this ground: state what circumstances have changed, explain why the journalistic purpose that justified the original article has expired, and identify what ongoing harm the continued indexing causes. Time alone is not sufficient. Time combined with changed circumstances is a strong foundation.

Ground 2: Objection under Article 21(1) with no overriding legitimate grounds (Article 17(1)(c))

Article 21(1) gives you the right to object to processing "on grounds relating to your particular situation." For news articles, this means arguing that your particular situation (changed circumstances, time elapsed, harm caused, private individual status) outweighs the publisher's grounds for continued indexing.

This is a balancing test. It is the ground Google actually evaluates most carefully when reviewing news article requests, because it forces the requester to directly address the public interest exception. It requires you to say: here is my particular situation, here is why it outweighs the public interest in this article continuing to be indexed.

The other four grounds under Article 17 (consent withdrawn, unlawful processing, legal obligation, child data) rarely apply to standard news articles. Consent is almost never the legal basis for news article publication. Most news articles are not unlawfully processed. Only if the article involved data about a minor, and was published when the subject was under 16, would the child data ground come into play.

The Proportionality Test: What Google Actually Weighs

This is the section most guides skip entirely, and it is the reason most requests fail. Google does not grant erasure automatically when you invoke Article 17. They run a proportionality test: your right to erasure balanced against the public interest in the information remaining accessible.

The legal basis for this balancing is Article 17(3)(a): the right to erasure does not apply when processing is necessary "for exercising the right of freedom of expression and information." For news articles, Google's reviewers evaluate this exception by considering a set of factors about the article and the person requesting removal.

Factors that tip the balance toward erasure: Private individual status with no ongoing public role. No current public interest in the story. Significant time elapsed since publication. Documented changed circumstances (charges dropped, conviction served, professional situation resolved, matter concluded). Article about a minor incident with no lasting significance. Harm to the individual that is disproportionate to any realistic public benefit from continued indexing.

Factors that tip the balance against erasure: Public figure status, even a minor one, where the article relates to their public role. Article about the person's conduct in their professional or public capacity. Ongoing public interest in the story. Article that is accurate, current, and of genuine significance to the public. Person who was a public figure at the time of publication and whose situation has not materially changed.

How to Write the Grounds Statement That Survives Review

The grounds statement is the single most important part of a GDPR removal request. Google's reviewers receive thousands of submissions. Most fail not because the underlying situation doesn't qualify, but because the requester doesn't articulate why it qualifies. A well-structured grounds statement makes the reviewer's job easy. A vague one gives them nothing to approve.

1. 1
   State the Article 17 ground explicitly. Do not just say "I have a right to be forgotten." Write: "I am invoking my right to erasure under GDPR Article 17(1)(a) [or 17(1)(c)] for the following reasons:" This signals that you know the legal framework and have chosen the correct provision.
2. 2
   Identify yourself as an EU or UK private individual. State your country of residence and confirm that you have no public role or professional position that would make the article about your public conduct. Do not claim to be a private individual if you are a public figure, an executive of a public company, or a politician. The proportionality test will be applied whether you invoke it or not, and misrepresenting your status undermines credibility.
3. 3
   Describe the article specifically. State the URL, the publication date, the publication name, and specifically which information in the article relates to you. Do not summarize the entire article. Identify the specific personal data at issue: your name, your address, details of a legal proceeding, your employment, whatever the article contains about you specifically.
4. 4
   Argue the proportionality test directly. This is where most requests fail. You must address why the public interest exception under Article 17(3)(a) does not apply to this specific article. State: (a) why you are not a public figure in the sense relevant to this article, (b) why there is no ongoing public interest in this specific content, and (c) what changed circumstances mean the journalistic purpose of the original article has been fully served.
5. 5
   Document ongoing harm factually and briefly. Employment consequences, professional licensing effects, impact on professional relationships. Keep this factual and brief. One or two specific, documented harms are more persuasive than a lengthy emotional account. If you have written evidence (a rejection letter referencing the article, for example), note that you can provide it.
6. 6
   Attach supporting documentation. Court dismissal orders, evidence of changed circumstances, letters showing professional harm. Documentation transforms assertions into evidence. Requests with documentation are substantially more likely to succeed than those without.

What not to include: threats, references to lawyers being involved (save that for the DPA complaint stage if needed), emotional narratives about how the article has affected your family, general complaints about the publisher's conduct, or requests for Google to contact the publisher on your behalf.

Example argument structure for an old arrest article:

The Google RTBF Form: Exact Process

Google's official RTBF form for EU and UK residents is at support.google.com/legal/answer/6153474. Here is how to navigate each component correctly.

1. 1
   Select "Remove information shown in Google Search" and then choose the European privacy option. This routes your request to the team handling GDPR submissions. Selecting the wrong category routes you to a different process with different review criteria.
2. 2
   Your name field: enter your full legal name exactly as it appears in the article. If the article uses a variant spelling or a former name, note this in the explanation field. Google needs to verify the article is actually about you.
3. 3
   URLs to remove: provide the Google Search result URLs, not the article URLs. This is the single most common error. You need the search result link, not the address of the article on the publisher's site. To find this: search your name on google.fr, google.de, google.co.uk, or whichever EU national domain you use. Identify the result. Right-click the link and copy the URL. It will be a Google redirect URL. Provide this URL in the form. You can request removal from multiple EU national Google domains in a single submission.
4. 4
   Additional information field: this is where your grounds statement goes. Write it here in full. Be specific and legal in tone. Two to four well-constructed paragraphs. This field is the substantive basis on which your request will be reviewed.
5. 5
   Supporting documents: attach documentation here. Court orders, dismissal records, evidence of changed circumstances. The upload function accepts standard document formats.
6. 6
   Which Google versions to request: EU residents should check the EU national Google domain(s) relevant to their country and any others where the article surfaces for their name. UK residents should check google.co.uk specifically. You can request removal from multiple EU versions in a single submission.
7. 7
   After submission: you will receive a reference number. Keep this. You will receive an automated acknowledgment. Timeline: Google must respond within 30 days under GDPR, though they may extend to 90 days for complex cases. In practice, initial responses for straightforward cases often arrive in 7 to 14 days. Decisions are communicated by email to the address you provided.

When Google Rejects the Request: The DPA Escalation Path

Google rejects a significant portion of RTBF requests for news articles, typically by invoking Article 17(3)(a): the freedom of expression and information exception. Rejection is not the end of the process. It is the beginning of a different phase.

Step 1: Read the rejection letter carefully

Google's rejection emails are brief, but they do specify the basis for rejection. The most common rejection grounds are: "this content relates to your professional conduct or public role" (meaning Google has classified you as a public figure for RTBF purposes) and "this content is of ongoing public interest" (meaning Google has applied the freedom of expression exception). Both are contestable. If Google says the content relates to your public role and you believe you are not a public figure in the relevant sense, that is an argument to develop in a resubmission or DPA complaint.

Step 2: Resubmit with a stronger grounds statement

Before going to the DPA, consider whether your grounds statement directly addressed the specific basis for rejection. If the first submission was general and the rejection cited a specific reason, a targeted resubmission that addresses that reason with additional documentation sometimes succeeds. Attach anything you did not include the first time.

Step 3: File a complaint with your national DPA

DPA complaints are free to file, require no legal representation, and can compel Google to reconsider decisions the DPA finds were incorrectly made. The process varies slightly by country but follows the same general structure: you describe the article, explain your grounds, attach Google's rejection, and explain why you believe the rejection was incorrect under the proportionality test. The DPA reviews the case and, if it agrees with you, issues a decision that Google must comply with.

DPA complaints take 3 to 12 months to resolve. They are not fast. But they are effective in cases where Google made a clear error in applying the proportionality test. The CNIL has issued multiple decisions compelling Google to de-index news articles that were initially rejected. The ICO has done the same for UK residents. Filing a DPA complaint is a genuine escalation path, not a theoretical one.

Scope and Limitations: What RTBF Actually Achieves

Being honest about what RTBF accomplishes and what it doesn't is essential to knowing whether it will achieve your actual goal.

The practical impact for EU and UK residents whose primary concern is local or European search: RTBF is meaningful and impactful. If someone in France, Germany, the UK, or Spain searches your name, a successful RTBF request means they will not find the article through Google. For most people in this situation, that is exactly what they need.

For UK Residents: Post-Brexit Specifics

The UK's departure from the EU did not affect the right to be forgotten in any practical way for current purposes. UK GDPR entered into force on January 1, 2021 through the European Union (Withdrawal) Act 2018 and the Data Protection Act 2018. The substantive provisions of Article 17, the proportionality test, and the grounds for erasure are identical to EU GDPR.

For UK residents filing RTBF requests:

1. 1
   Use the same Google RTBF form at support.google.com/legal/answer/6153474. Select the European privacy law option and note that you are submitting under UK GDPR.
2. 2
   Specify that you are requesting removal from google.co.uk. If the article also surfaces on other EU Google domains, you can request those in the same submission, though your GDPR rights as a UK resident most clearly apply to google.co.uk.
3. 3
   If Google rejects your request, your supervisory authority is the ICO (Information Commissioner's Office), not an EU DPA. The ICO has an online complaints process that does not require legal representation. ICO complaint decisions have compelled Google to de-index articles that were initially rejected.

One forward-looking note: the UK is progressively developing its own data protection framework post-Brexit through the Data Protection and Digital Information Act and related ICO guidance. As of mid-2026, the UK's approach to RTBF has remained consistent with pre-Brexit practice, but practitioners should monitor UK ICO - Right to Erasure guidance for any divergence over time, particularly around how the public interest exception is applied to journalistic content. If your concern is about removing negative newspaper articles specifically, see our dedicated guide on removing negative newspaper articles.

Frequently Asked Questions