Google's removal policy and Google's actual removal behavior are not the same thing. Most people who submit removal requests for negative news articles receive a rejection. Here's what happens after you submit, what rejection looks like, and why most defamation claims fail at the Google level before you ever get to court.
Google de-indexes, not deletes - the article stays live on the publisher's site but disappears from Google search results. Direct URL access still works.
Outdated content tool works for articles 6+ months old - temporary but often effective, especially when combined with other removal strategies.
Legal removal grounds Google honors: GDPR right-to-erasure (EU/UK residents), doxxing, non-consensual intimate images, minors' information, and court-ordered removals.
Personal embarrassment alone is not grounds for removal - Google requires legal, policy, or factual violations, not just reputational harm from true information.
Google does remove content from its search index. This is not a myth and not a rare event. Google processes millions of removal requests annually, and many of them succeed. Google's Transparency Report documents this at scale.
But qualifying under the policy and actually getting content removed are different things. The gap between them is where most people spend their time and frustration. The categories that qualify for removal are clear and relatively narrow. Most news articles that people want removed do not fall into any of them. That is not a failure of the system working incorrectly. It is the system working as designed.
Our complete de-indexing guide covers what the policy categories are in full detail. In brief: Google acts on personal information (doxxing, financial data, government IDs), copyright violations with valid DMCA documentation, CSAM, government-required removals, and EU and UK right-to-be-forgotten requests under GDPR right to be forgotten. Everything else, including content that is simply negative, embarrassing, unfair, or inaccurate without legal documentation, does not meet the threshold for removal. Note that even removing articles from Google's index does not affect removing articles from AI search results like ChatGPT, which requires separate approaches.
This article covers what the guide cannot afford space for: what happens after you submit a request. The mechanics of review, the realistic approval rates by request type, why defamation claims fail at the Google level before they fail anywhere else, and what to do when Google says no.
Google does not have a human reviewer assigned to every removal request. The volume makes that impossible. What actually happens is a multi-stage triage process where the request type determines the path.
For content categories where the policy violation is unambiguous and the documentation is well-established, automated systems handle the initial screening. CSAM is acted on essentially immediately by automated detection. DMCA requests with proper documentation and clear copyright ownership are processed in automated batches. Doxxing requests (home address, financial account numbers, government ID numbers, medical records) that clearly match Google's expanded personal information removal policy are screened quickly, with human review stepping in primarily for edge cases.
Turnaround for content that falls cleanly into these automated categories: 3 to 10 business days in most cases.
EU and UK RTBF requests under GDPR cannot be handled by automated systems because they require a proportionality assessment: weighing the requester's privacy interest against the public interest in the specific content. This evaluation requires judgment, not just pattern matching. Every RTBF request for news article content gets human review. Timeline: 7 to 30 days for an initial response, with the possibility of extension to 90 days for complex cases.
Requests submitted as defamation claims or general legal removal requests that don't fit cleanly into a standard category also go to human review. These have the longest timelines (30 to 90 days or longer) and the highest rejection rates. "Under review" in this context means your request is in a queue of similar submissions, and there is no way to follow up, accelerate, or check status. Submitting duplicate requests does not help and may cause confusion in the queue.
After submitting a removal request, you receive an acknowledgment email with a reference number. The status message "under review" means exactly that: your request is in the queue. There is no phone number to call, no follow-up form, and no way to check where your request stands. The only action that makes sense is waiting for the decision email. If you do not receive a decision within 90 days for a GDPR request (the legal maximum), you have grounds to escalate to your national DPA. For other request types, there is no statutory timeline, and Google's practice is to communicate decisions as they are made.
Most discussions of Google removal present the policy categories without addressing what the realistic outcomes are within each category. Here is an honest breakdown based on our experience across 1,000+ cases and publicly available data from Google's Transparency Report.
| Request Type | Realistic Approval Rate | Primary Reason |
|---|---|---|
| CSAM, doxxing, non-consensual intimate images | Very high | Clear policy violation, largely automated. These categories exist specifically to address severe harm and Google acts on them at high rates. |
| DMCA copyright (with proper documentation) | High | Established legal process, well-documented submissions processed efficiently. Approval rates are high when the copyright claim is legitimate and the documentation is correct. |
| Personal information (financial data, government ID) | Moderate to high | Policy is clear since the 2022 expansion. Requires documentation and correct submission pathway. Edge cases go to human review. |
| EU or UK RTBF (private individual, outdated or resolved content) | Moderate | Depends heavily on how well the grounds statement argues the proportionality test. Well-documented cases with clear changed circumstances succeed at meaningful rates. Vague submissions almost always fail. |
| EU or UK RTBF (public figure, current content) | Low | Google applies the freedom of expression exception more readily to public figures. The proportionality test is harder to win. |
| Defamation claims (US claimants) | Low | Requires court order in most cases. Google does not adjudicate defamation. Without a court order, approval is rare. |
| "This article is inaccurate" without documentation | Very low | Assertion without evidence. Google cannot verify the claim and has no basis to act. |
| "This hurts my reputation or business" | Near zero | Not a recognized removal category under any pathway. Reputational harm from accurate content is not a basis for removal. |
The pattern is consistent: requests that map to a clear policy category with proper documentation succeed. Requests that ask Google to adjudicate whether content is fair, accurate, or harmful without fitting into a defined category fail almost universally.
Defamation is the most common basis people cite when they contact us about news articles, and it is the basis that has the lowest realistic chance of producing a Google removal. Understanding why requires understanding what Google's actual role is in the information ecosystem.
Google's defamation removal policy requires either (a) a court order from a court with jurisdiction over the matter establishing that the content is defamatory, or (b) documentation meeting their specific standards, which in practice means a formal legal determination, not just an assertion. The reason is structural: Google is not a court. It cannot determine whether specific statements are defamatory under applicable law. Only a court can make that determination with legal force.
When someone submits a removal request saying "this article is defamatory," they are asking Google to do something it is not equipped to do: evaluate the legal status of a factual dispute it knows nothing about, under law that varies by jurisdiction, based on one side's characterization of the facts. Google's response to this is consistently the same: provide a court order and we will act.
If an article is genuinely defamatory, the correct sequence is: consult a defamation attorney to assess whether the content meets the legal standard, pursue the case against the publisher (not Google) if it warrants litigation, and if you obtain a favorable judgment or order that includes content removal, submit that court order to Google. Google acts on court orders. When the publisher removes or updates the content following legal action, Google's index updates as part of its normal crawl cycle.
The faster path for false but non-defamatory content: contact the publisher directly with documentation of the inaccuracy. Publishers have a professional and ethical interest in accuracy that Google does not. A publisher who published an article containing a factual error that can be documented will often issue a correction or update, sometimes remove the article entirely. The same result that would require litigation against the publisher and then a separate Google submission can sometimes be achieved with a single well-written correction request to the editor.
Despite low approval rates for defamation-framed requests, there are categories where Google is more proactive than most people expect. Leaked personal information, content targeting private individuals with no public role, and genuinely stale content about minor incidents involving private individuals are all areas where Google takes action more readily. The Outdated Content Tool also has a higher success rate than most people realize for content that is genuinely no longer live or has changed substantially at the source. If you have not tried that tool, try it first before pursuing formal legal removal pathways.
Google's rejection emails are brief. They state the basis for rejection without elaborating on the specific facts of your case. Here are the most common rejection formulations and what they mean in practice.
After a rejection, the options in priority order:
A significant number of people go through the full formal legal removal request process and miss the Google Outdated Content Tool entirely. For a specific set of situations, it is faster and has a higher success rate than any legal removal pathway. The situations where it applies are more common than people realize. For a broader look at removal options beyond Google, see our guide on removing negative articles from the internet.
The Google's Outdated Content Removal Tool requests that Google remove cached or outdated versions of content from search results. It is an index freshness tool. It works when the content at the source URL has materially changed (a correction was added, the article was substantially updated) or when the page no longer exists at the URL (the article has been taken down). It does not work for live, unchanged articles. Submitting an Outdated Content Tool request for an article that is still fully live at its URL will return an error or produce no effect.
The Outdated Content Tool is the right tool in three situations:
Go to Google's Outdated Content Removal Tool. Select "Outdated content." Enter the URL of the page as it appears in Google's search results. For legal removal requests, Google's content removal request page covers the full range of qualifying categories. Confirm that the page has been removed or the content has materially changed. Submit. Google reviews the request and, if the page confirms the claim (the URL returns 404, or the cached content no longer matches the live content), typically clears the cached version within one to two weeks.
The Outdated Content Tool will not work for a live, unchanged article. If you submit it for an article that is still fully published and unchanged at its URL, you will get an error or no result. The source must change first. The Outdated Content Tool's job is to accelerate Google's recognition of a change that has already happened, not to force removal of content that is still live.
Realistic timeline: 1 to 2 weeks for cache clearing if the submission is approved and the source confirms the change. This is faster than most formal legal removal processes and requires no documentation of legal grounds.
Not sure which pathway applies to your situation? Start with a free assessment. We'll identify whether publisher outreach, legal removal, RTBF, or the Outdated Content Tool is the right first step.
Start FreeStart with our free assessment. We'll identify which removal pathway applies to your situation and whether Google tools, publisher outreach, or RTBF is the right first step.