Google Rejected Your RTBF Request. Here Is What to Do Next.

Why Google Rejects So Many RTBF Requests for News Articles

Google receives hundreds of thousands of Right to Be Forgotten requests each year. For requests concerning news articles specifically, the rejection rate is significantly higher than for other content types. Understanding why requires a brief look at how Google interprets its legal obligations under the GDPR.

Article 17 of the GDPR establishes the right to erasure, commonly referred to as the right to be forgotten. However, Article 17(3) carves out explicit exceptions. Article 17(3)(a) provides that the right to erasure does not apply where processing is necessary for exercising the right of freedom of expression and information. This is the exception Google invokes most frequently when rejecting requests related to news coverage.

Google's application of this exception is broad and often mechanical. Because news articles are, by definition, journalistic content, Google treats them as presumptively protected under the freedom of expression carve-out. The burden effectively falls on the requester to overcome that presumption by demonstrating that the balance between privacy and freedom of expression tips in their favor. Google's automated and semi-automated review process is not well-equipped to assess the nuanced proportionality questions that GDPR Article 17 actually requires.

Google also frequently invokes the concept of "ongoing public interest" without clearly articulating what makes a specific article's subject matter a current public concern. A decade-old business dispute or a resolved criminal matter may still receive a rejection citing public interest, even where that interest has demonstrably diminished over time.

What Google's Rejection Email Actually Says, and What It Means

Google sends a standard rejection email when it determines that a URL does not qualify for de-listing. The language in these emails is formulaic and often frustrating in its vagueness. Knowing how to read the rejection accurately matters, because the specific phrasing determines what your next step should be.

The most common rejection language states something similar to: Google has carefully reviewed the request and determined that the content appears to be relevant to your professional life, and that there is public interest in the information remaining accessible. This phrasing signals a rejection based on the professional life exception or the public interest exception, or both.

A second common formulation states that the content relates to your conduct as a public figure, or that you appear to play a prominent role in public life. This invokes the reduced privacy expectations that apply to politicians, business executives, public officials, and others who voluntarily enter the public sphere.

A third type of rejection simply states that insufficient grounds were provided to establish that the link should be removed. This is the most actionable rejection because it signals that Google did not find your justification compelling rather than categorically refusing on freedom of expression grounds. A stronger resubmission can directly address this.

The Four Most Common Rejection Reasons for News Articles

1. Freedom of Expression and Public Interest

This is the most frequently cited rejection basis for news articles. Google applies Article 17(3)(a) and argues that de-listing the article would interfere with the public's right to access information that serves a legitimate journalistic purpose. The key question that Google's review often fails to address adequately is whether that public interest remains active and proportionate to your ongoing privacy harm. An article about a legal dispute that concluded years ago may no longer serve genuine public interest at a level that justifies continued harm to an individual's reputation.

2. Content About a Public Figure

If Google characterizes you as a public figure, it applies a higher threshold for RTBF approval. Politicians, company directors, executives, celebrities, and others who have voluntarily entered public life receive reduced privacy protection regarding their public roles. However, public figure status is not absolute. Even public figures retain privacy interests in matters genuinely outside their public role, and the "public figure" characterization itself can be challenged where it is applied to people who did not voluntarily seek public prominence.

3. Content Still Relevant to the Public

Google sometimes rejects requests on the basis that the content remains relevant to the public's understanding of current events, ongoing issues, or matters of continued concern. This ground is frequently applied too broadly. The GDPR's proportionality requirement demands a genuine balancing exercise: the specific harm to the individual must be weighed against the specific ongoing public benefit of the article's searchability under that person's name. Generic relevance is not sufficient justification for sustained privacy harm.

4. Insufficient Grounds Stated in the Original Request

A significant number of rejections occur not because Google categorically refuses on legal grounds, but because the original request failed to articulate compelling grounds. Many people submit RTBF requests without explaining why the specific article causes disproportionate harm, what has changed since the article was published, or why the balance of interests favors removal. This category of rejection is the most directly addressable through resubmission. See our GDPR RTBF request template for guidance on how to structure grounds that address this problem.

Option 1: Resubmit with a Stronger Grounds Statement

If Google's rejection cited insufficient grounds, or if you believe your original submission did not adequately address the proportionality balance, a targeted resubmission is the logical first step. A stronger resubmission is not simply a repeat of the original request. It must directly address the specific rejection reason Google cited and provide additional substance that changes the calculus.

• 1
  Identify the exact rejection reason from Google's email. Quote the specific language Google used. Your resubmission should open by acknowledging that prior request and directly engaging with the reason given for rejection. Generic resubmissions that do not respond to the stated reason are likely to receive the same rejection.
• 2
  Strengthen the proportionality argument. Explain specifically how the continued searchability of this article under your name causes harm disproportionate to any ongoing public benefit. Quantify where possible: has the article cost you professional opportunities? Has it been cited by others in ways that compound its impact? Is the underlying matter resolved, meaning there is no active public interest in the information?
• 3
  Address the passage of time explicitly. The GDPR's proportionality analysis gives significant weight to the age of information. An article that was newsworthy at publication may no longer serve genuine public interest several years later, particularly where the underlying matter was resolved. State clearly how much time has passed and what has changed.
• 4
  Attach supporting documentation. Include any documentation that supports your grounds: court records showing dismissal or acquittal, settlement agreements, regulatory closure letters, evidence of employment impact, or medical documentation where health grounds are relevant. Google's review process is more responsive to documented claims than bare assertions.
• 5
  Address the public figure argument directly if applicable. If Google cited your status as a public figure, consider whether that characterization is accurate for your specific circumstances. If you are a private individual who happened to be covered in a news article, state this clearly and explain that you did not voluntarily enter public life in connection with the subject matter of the article.

For detailed guidance on structuring a grounds statement, see our article on how to file a Google Right to Be Forgotten request and our guide specifically on RTBF requests for news articles.

Option 2: File a Complaint with Your National Data Protection Authority

Filing a complaint with your national Data Protection Authority is the most powerful escalation available after a Google rejection. DPA complaints are free to file. They carry legal weight that Google must take seriously. And when a DPA upholds a complaint, its decision is binding: Google is legally required to comply.

The DPA complaint process is not a passive review of your original RTBF request. The DPA investigates independently. It may request detailed reasoning from Google about why the rejection was made, assess whether that reasoning is consistent with GDPR obligations, and issue a formal decision. In cases where the DPA finds that Google's rejection was incorrect, the DPA can issue an order requiring Google to de-list the URL in question.

This pathway is underused. Many individuals who receive a Google rejection accept it as final and abandon the process. In practice, DPA oversight is exactly the mechanism the GDPR envisioned to hold data controllers accountable for their decisions. Google is a data controller for purposes of RTBF requests, and the DPAs are its regulators.

Key National DPAs for RTBF Complaints

What the DPA Complaint Process Looks Like

Once you file a complaint, the DPA acknowledges receipt and opens an investigation file. The DPA will typically notify Google of the complaint and request a written explanation of why the RTBF request was rejected. Google is required to respond. The DPA evaluates both positions and may request additional information from you or from Google.

Timeline: most DPA complaints resolve within three to twelve months from filing. Complex cases, or those involving novel legal questions, can take longer. During this period, maintain organized records of all correspondence: your original RTBF submission, Google's rejection email, any follow-up communications, and all documents you have filed with the DPA.

If the DPA upholds your complaint, it issues a formal decision. That decision may require Google to de-list the specific URL or URLs from European search results. Google can challenge a DPA decision through judicial review in some jurisdictions, but in practice Google complies with most upheld complaints rather than litigate each one individually.

Option 3: Pursue Editorial Removal at the Source

Regardless of how your RTBF process unfolds, pursuing removal of the article at the source publication is the most effective long-term strategy available. This approach does not depend on Google's internal review process or on a DPA investigation. If the publisher removes the article, it disappears from Google's index entirely once the index is refreshed, without any RTBF decision required.

Editorial removal has significant advantages over RTBF de-listing. A successful RTBF de-listing removes the URL from Google Search results in European Economic Area countries and the UK. The article itself remains on the publisher's website, remains accessible to anyone who navigates directly to the URL, remains indexed on Bing, DuckDuckGo, and other search engines, and remains searchable in the United States version of Google. Editorial removal eliminates all of these problems simultaneously.

Publisher outreach requires a different strategy than RTBF submissions. Publications are not legally required to remove accurately reported articles. However, many publishers will consider removal or significant editing in circumstances where the underlying matter has been resolved, where the continued publication causes disproportionate harm to a private individual, where the article contains inaccuracies or where context has materially changed, or where the article is old and no longer serves active journalistic purpose.

A well-crafted removal request to a publisher typically includes a factual account of what has changed since publication, documentation supporting that account, a proportionality argument explaining the ongoing harm versus the diminished public value of continued publication, and a specific, reasonable ask such as removal, significant editing, or de-indexing instruction via a noindex meta tag.

RemoveNews.ai specializes in this process. Direct publisher contact by an individual, without professional representation, frequently results in no response or a flat refusal. Specialist representation significantly improves outcomes by framing requests in terms publishers respond to and by navigating editorial gatekeepers effectively. For a broader discussion of this process in the context of GDPR, see our guide on the right to be forgotten and news articles under GDPR.

Scenario Reference: Next Steps by Rejection Type

What a Successful DPA Complaint Looks Like

A successful DPA complaint follows a recognizable pattern. The DPA opens the case, notifies Google, and requests Google's reasoning for the rejection. Google provides a written explanation to the DPA. The DPA evaluates whether Google's reasoning is consistent with the GDPR's requirements, including the proportionality principles established by the CJEU and elaborated in EDPB guidance.

Where the DPA finds that Google applied the freedom of expression exception too broadly, failed to conduct a genuine proportionality assessment, or otherwise rejected the request in a manner inconsistent with Article 17 and its exceptions, the DPA issues a formal decision upholding the complaint. That decision specifies the URL or URLs that must be de-listed and sets a compliance deadline.

The most important factor in a successful complaint is the quality of the proportionality argument. A DPA is not simply reviewing whether your privacy interests are affected. Every RTBF request involves some privacy interest. The question is whether those interests outweigh the freedom of expression and information interests at stake in the specific case. A compelling complaint frames this balance clearly, provides evidence, and explains why Google's weighting of those interests was wrong.

Complaints that document specific, ongoing harm, such as lost employment, damaged professional relationships, or documented mental health impact, tend to perform better than abstract privacy arguments. Complaints that demonstrate the underlying matter is fully resolved and no longer active public concern tend to succeed more often than complaints about recent or ongoing matters.

For matters specifically affecting UK residents, the ICO has published guidance on search engine complaints that explains its decision-making criteria in detail. Our dedicated guide on the UK right to be forgotten and the ICO covers that process specifically.

Common Questions About RTBF Rejections and Appeals