Google removed 2,418,000 URLs from EU search results under right-to-be-forgotten requests in 2024 alone, according to the company’s own transparency report. That number is the third-highest in the program’s history, and it is climbing faster than at any point since the 2014 ruling. Behind those numbers are individual people who managed to scrub specific search results that were ruining their job prospects, dating lives, professional reputations, or mental health. The right to be forgotten Google policy is real, it works in specific cases, and most people have no idea what their actual rights are in 2026.

The mistake most reputation management vendors make is selling vague “online cleanup” services that promise to make a search result disappear. Those services usually do not work. The thing that does work is matching your specific case to the specific legal or policy mechanism that applies. There are five different paths, depending on jurisdiction, content type, and the facts of your situation. Each has a different bar, a different timeline, and a different success rate.

The five paths to actual Google result removal

A close-up of the Google homepage on a laptop screen, the surface where every search-removal battle is ultimately fought and measured

Path one is the EU right to be forgotten request. This is the most powerful tool, but it only works if you are a resident of an EU or UK jurisdiction and the content meets the GDPR Article 17 test. Google evaluates each request against five criteria: whether the information is still relevant, whether it is in the public interest, whether you are a public figure, whether the information is true or inaccurate, and whether the content involves a sensitive category (health, religion, sexuality, financial status). The 2024 approval rate, per Google’s transparency report, was roughly 44 percent of submitted requests. Above 50 percent for private individuals, below 20 percent for public figures.

Path two is the US legal removal request. There is no general right to be forgotten in the US, but Google honors removal requests in specific narrow categories: court orders, copyright violations, personal financial information leaks, non-consensual explicit imagery (commonly known as revenge porn), and child safety content. Approval rates in these categories are high, often above 80 percent, but the bar to qualify is strict.

Path three is the source-removal request. Instead of asking Google to delist the URL, you ask the website hosting the content to remove the page entirely. This works for content on blogs, smaller news sites, and forums where the publisher will negotiate. It almost never works on major news sites (NYT, WaPo, Bloomberg) which have published-once-keep-forever policies.

Path four is the Wikipedia talk-page negotiation. If the offending content is a Wikipedia article, the Articles for Deletion (AfD) process is your tool. You file a deletion request explaining why the subject does not meet notability requirements. The process takes 2 to 4 weeks, requires you (or a third party) to argue policy with Wikipedia editors, and succeeds maybe 15 to 25 percent of the time for borderline-notable subjects.

Path five is the SEO suppression strategy. When delisting and removal both fail, you publish enough positive content about yourself that the negative result gets pushed below the first page of Google. This is the path most reputation management firms sell. It works for some cases (lifting page-one results to page two or three), fails for others (lifting page-one results that have high-DA news backlinks), and takes 4 to 18 months depending on the difficulty of the target result.

The 5 criteria that actually decide your right to be forgotten case

When Google reviews an EU right to be forgotten Google request, the team applies five criteria. Knowing these in advance dramatically changes how you write the request.

Criterion one is relevance over time. Information about a 10-year-old minor offense is rarely still relevant. Information about a 2-year-old fraud conviction usually is. The older the content, the higher your odds of approval.

Criterion two is public interest. Public figures (executives, politicians, celebrities) face a higher bar because the public has a legitimate interest in their conduct. Private individuals face a lower bar. If you are not a public figure, lead the request with that fact and your supporting evidence (no media coverage outside of one local outlet, etc.).

Criterion three is accuracy. If the underlying content is factually false, you have a strong case. If it is technically true but misleading by omission, you have a moderate case. If it is fully accurate and current, you have a weak case unless other factors offset.

Criterion four is sensitivity of category. Information about health, sexuality, religion, financial status, or political affiliation receives heightened protection. A search result that reveals your past medical history is much more likely to be delisted than a result about your business dealings.

Criterion five is the chilling effect on private life. If the result is actively harming your employment prospects, relationships, or mental health, document that harm in the request. Google’s reviewers weight specific documented harms higher than vague claims of distress.

Writing the request that actually wins

The submission form at google.com/policies/faq has a free-text section where you explain why the content should be removed. Most people fill this in with a paragraph of frustration and emotional appeal. That paragraph gets rejected.

The winning format is closer to a legal brief. State your name and jurisdiction (you must be an EU/UK resident for the GDPR mechanism). Identify each URL you want delisted, with the exact search query that surfaces it. For each URL, write three to five sentences mapping the content to the five criteria. Explain why it is no longer relevant, why you are not a public figure, why the content falls in a sensitive category, why it is causing documented harm. Include supporting documents: identity verification, evidence of the harm, supporting context.

The Google reviewer assigned to your case has maybe 20 minutes per request. Make it easy for them to approve. A well-structured 700-word request is far more likely to succeed than a 3,000-word emotional plea.

When source removal beats delisting

If the content lives on a smaller website that will engage in dialogue, source removal beats delisting. Removing the URL at the source means it disappears from every search engine, not just Google. It also prevents the page from being archived by Wayback Machine going forward (existing archives stay, but new captures stop).

The pitch to the website owner is straightforward. Identify yourself, explain why the content is causing specific harm, and ask politely for removal. If you have a legal basis (defamation, copyright infringement, GDPR), reference it. Do not lead with threats of legal action; that usually makes the publisher defensive and they keep the content live to prove a point.

For news sites, the better ask is “update” not “remove.” Most news organizations will not unpublish an article but will publish a correction or update that addresses your concern. An updated article ranks higher than the original in subsequent search results, effectively suppressing the original.

The Wall Street Journal, for example, will not unpublish stories but does publish corrections and follow-ups. A 2022 piece that paints you negatively can be paired with a 2026 follow-up that adds context. Google’s freshness signals will rank the 2026 piece higher, partially solving the problem without removal.

The Wikipedia problem and how to actually engage it

A statue of Lady Justice holding scales, the symbol of the legal framework that underwrites every right-to-be-forgotten claim

Wikipedia is the hardest case in reputation management. The platform’s biographies-of-living-persons policy allows for fact corrections but not for removal of a properly sourced article on a notable subject. If you have a Wikipedia entry you do not want, your options are limited.

The first option is to correct factual errors. Go to the article’s talk page, identify each error, cite the correct source, and let editors update the main article. Be civil and persistent. Most editors will engage in good faith if you do.

The second option is to file for deletion via the Articles for Deletion process. This succeeds only if the subject does not meet Wikipedia’s notability requirements (Wikipedia:Notability for general subjects, WP:BIO for people). If you are a CEO of a company with multiple major-press mentions, you almost certainly meet the notability bar and the AfD will fail. If you are a tangential figure with one minor news mention, you might succeed.

The third option, hiring a paid editor to clean up the article, is technically against Wikipedia’s policy but happens routinely. Paid editors must disclose their affiliation, and the work has to follow Wikipedia’s content policies. Done correctly, a paid editor can balance the tone, add missing context, and improve the article. Done badly, it gets the article flagged and locked, which makes the situation worse.

What reputation management vendors get wrong

Most reputation management firms sell SEO suppression as a one-size-fits-all solution. The pitch is “we will push the negative results to page two of Google for $4,000 to $25,000 per case.” This works sometimes. It also fails frequently, and the failures are expensive because the vendor has spent the money before the result is visible.

The honest first step in any case is a path-eligibility audit. Are you an EU/UK resident with a GDPR-eligible case? File the request first; it costs nothing. Are you a US resident with a court order? Use the legal removal path. Is the content on a small site? Negotiate source removal. Is it Wikipedia? Try the AfD or the correction path. Is it on a major news site? Negotiate an update, not a removal. SEO suppression is the path of last resort, not the path of first resort.

The vendors who lead with SEO suppression are selling the expensive solution to people who could have gotten the cheap or free solution first. If your vendor has not asked about your jurisdiction, the source of the content, the age of the content, and the specific URLs in question, get a different vendor. The right to be forgotten Google framework rewards specificity. So does every other removal mechanism. Vague reputation management strategy fails on every path.

If you are reading this because you have a specific Google result that is causing you specific harm, the next step is to identify which of the five paths actually fits your case. Get that right and the timeline collapses from years to weeks. Get it wrong and you spend $20,000 on the wrong vendor and end up exactly where you started.