When a publisher won't remove an article, getting it de-indexed from Google is the next most powerful move. De-indexing doesn't delete the article -- it makes it invisible in search. The article still exists on the publisher's server, but Google stops showing it to anyone who searches your name. For most people whose primary concern is what shows up when someone Googles them, de-indexing achieves the same practical result as removal.
De-indexing removes an article from Google search without requiring the publisher to delete it -- the page remains on the publisher's server but disappears from search results.
Multiple de-indexing pathways exist: GDPR/Right to Be Forgotten, outdated content removal, legal court orders, and publisher-side technical signals including noindex and robots.txt.
GDPR applies to EU residents and in some cases to content about EU residents regardless of where they live -- with approval rates of approximately 50-60% for qualifying requests.
Google's outdated content removal tool works for content that has been substantially changed or deleted and is one of the fastest available de-indexing paths.
Google maintains an index of web pages -- the massive, constantly-updated database it searches when someone types a query. That index contains hundreds of billions of URLs, each with associated signals about relevance, authority, and content. When Google de-indexes a URL, it removes that URL from the index entirely, meaning it will no longer appear in any search results for any query. The underlying page still exists on the publisher's server -- they haven't deleted anything -- but Google won't serve it to any user under any circumstances.
The mechanism is important to understand: de-indexing is not the same as blocking a specific search query. It removes the page from all search results, for all queries, permanently (or until the page is re-indexed). For most practical reputation management purposes, if something doesn't appear in Google search, it effectively doesn't exist for the vast majority of people searching for it. Studies consistently show that fewer than 5% of searchers navigate past the first page of results, and virtually no one navigates to a page that doesn't appear at all.
De-indexing can happen several ways: Google can choose to de-index a page on its own (for example, if the page returns a 404 error, violates Google's webmaster guidelines, or contains malware), or Google can process a formal request to de-index. The formal request pathways are what this guide covers -- and which pathway is available to you depends on your specific situation, your geography, and the current status of the article itself.
Removal means the publisher has deleted the page from their server -- it returns a 404 (not found) or 410 (gone) HTTP status code. The page no longer exists anywhere. De-indexing means Google has stopped showing the page in search results, but the page may still exist on the publisher's server. Someone who has the direct URL of a de-indexed page can still navigate to it and read it. It simply won't appear in search results.
This distinction matters in several ways. A de-indexed page can still be found by someone who has the direct URL -- if the article has been widely shared, emailed, or posted to social media, those links still work. A de-indexed page may still appear in Bing, DuckDuckGo, Yahoo, and other search engines that maintain their own separate indexes, completely independent of Google's decisions. And if the publisher adds new content to the page, acquires new links pointing to it, or removes a technical noindex signal, Google may re-crawl and re-index it at any time without notice.
For most clients, de-indexing from Google is sufficient -- it addresses the primary concern of what appears when someone Googles them. But for the most sensitive situations involving public figures, ongoing legal matters, or content that has been widely circulated, both de-indexing from all major search engines and publisher removal are typically pursued together. De-indexing and removal are not mutually exclusive strategies -- they address different aspects of the problem and are often pursued in parallel.
When a client asks "can you remove this article from Google?" what they almost always mean is "can you make it stop showing up when someone searches my name?" De-indexing achieves that goal just as completely as publisher deletion, for the purposes of Google search. The distinction matters primarily if you're concerned about other search engines or people accessing the article through direct links.
EU residents -- and in some cases non-EU residents for content that appears in EU-localized search results -- can request that Google de-index URLs containing their personal information when that data is outdated, irrelevant, inaccurate, or was processed without a legal basis. This right, established by the Court of Justice of the European Union in the 2014 Google Spain ruling and codified in the General Data Protection Regulation (GDPR), is one of the most powerful de-indexing tools available because it creates a legal obligation for Google to evaluate and act on qualifying requests. Requests are submitted through Google's Right to Be Forgotten request form.
Google evaluates RTBF (Right to Be Forgotten) requests case by case, applying a balancing test between the individual's privacy interests and the public interest in the information. The key factors Google weighs include: whether the subject is a private individual or a public figure (private individuals get stronger privacy protection), whether the information is outdated or no longer relevant (a resolved legal matter, an old arrest, a past financial difficulty), whether the information was accurate when published but is no longer current, and whether the public interest in the information is still served by its continued visibility. Requests are submitted through Google's dedicated privacy request form at google.com/webmastertools/removals.
Historically, Google approves approximately 50-60% of RTBF requests submitted through this process -- a rate that is meaningfully higher for private individuals, for older content, and for content about resolved legal matters or circumstances that have materially changed. Approval rates are lower for public figures, for content about ongoing matters of public concern, and for content involving serious financial or criminal conduct where the public interest argument is strong. When a request is denied, the denial can be appealed to the relevant national data protection authority in the EU -- bodies like the French CNIL, the German BfDI, or the UK ICO have independent authority to review Google's decisions and can compel compliance if they disagree.
Google's Search Console provides an "Outdated Content" removal tool -- separate from the RTBF tool and available to anyone globally, not just EU residents -- that allows requests to de-index pages that have been substantially changed or where Google's cached version no longer matches the live page. This is accessed via Google's outdated content removal tool. This tool operates on a factual basis rather than a privacy or legal basis: it addresses a technical discrepancy between what Google has indexed and what currently exists at a URL. It works in specific circumstances and is one of the fastest de-indexing paths available when those circumstances apply.
The outdated content removal tool is appropriate when: the publisher has substantially edited the article to remove the most damaging content (Google's cached version shows the old text, but the live page now says something different or lacks the damaging detail), the publisher has removed the article entirely but Google still indexes the URL because its crawler hasn't revisited the page, or the article has been deleted and returns a 404 error but still appears in search results. In all of these cases, the tool allows you to flag the discrepancy and request that Google update its index to reflect current reality. Google typically processes these requests within days -- making this the fastest de-indexing path available when the underlying page has already been changed or removed.
Need help navigating the de-indexing process? Our specialists have handled thousands of cases and know which path applies to your situation.
Start Free at RemoveNews.aiIn some jurisdictions, courts can issue orders specifically directing Google to de-index particular URLs. France, Germany, Belgium, and other EU countries have issued such orders in cases involving privacy violations, defamation, and data protection violations. In the United States, court orders in defamation cases have sometimes included injunctions requiring de-indexing as part of a broader injunction against continued publication or dissemination of the defamatory content. Google has compliance processes for valid court orders and will act on them when submitted through Google's legal removal request portal.
This is the most powerful de-indexing path because it bypasses Google's editorial discretion entirely -- a valid court order is a legal obligation, not a request Google evaluates and may decline. However, it is also the most resource-intensive path by a significant margin. Obtaining a court order directing Google to de-index content requires first winning the underlying legal case -- a defamation claim, a privacy violation, a GDPR enforcement action. That requires filing and litigating the underlying claim, which can take years and cost tens of thousands of dollars or more. Legal court orders are the right path when there's an active legal case that has produced a favorable ruling, not as a starting point for de-indexing a live article.
If a publisher adds a noindex meta tag to an article's page, Google will respect it and remove the page from its index within days -- typically within the next time Google's crawler visits the page, which for active news sites is often within 24-72 hours. Similarly, if the publisher adds the article's URL to their robots.txt file, Google will stop crawling that URL, which leads to eventual de-indexing as the old index entry ages out. These publisher-side technical signals require the publisher's cooperation -- they don't remove the article content, but they make the article invisible to Google without requiring the publisher to delete it.
Some publishers are willing to add a noindex tag as a compromise when they decline to fully remove an article. This is worth requesting specifically and explicitly in any correction or removal request -- many people ask only for deletion and never ask for the noindex alternative, which some publishers find easier to grant because the article technically remains on their site (satisfying their editorial records) while becoming invisible in search. When making a removal request that is declined, a follow-up specifically requesting a noindex tag -- framed as a privacy accommodation rather than an editorial retraction -- often produces better results than continuing to push for full removal.
When a publisher has deleted an article -- returning a 404 (not found) or 410 (gone) HTTP response -- Google will eventually de-index it on its own as part of its normal crawling and index maintenance. However, "eventually" can mean weeks or months depending on how frequently Google crawls the publication and how quickly it processes deletions in its index. The Google Search Console URL removal tool allows the page's owner to request faster removal of URLs they control. For third-party pages that have been deleted, the outdated content removal tool described in Path 2 achieves the same result for non-owners.
This path assumes the publisher has already removed the content -- it accelerates the de-indexing that will happen anyway. It is worth pursuing immediately after a publisher confirms deletion, rather than waiting for Google's natural crawl cycle. The outdated content removal tool is available without owning the site, making it accessible to anyone who has confirmed that a third-party URL is returning a 404 error but still appearing in search results.
The right de-indexing path depends on several factors: your geographic location, the current status of the article, what relationship (if any) you have with the publisher, and whether any legal proceedings have taken place. GDPR right to erasure is the right path for EU residents whose content meets the criteria -- outdated, irrelevant, inaccurate, or involving a resolved matter. The outdated content removal tool is right when the article has already been edited or deleted and Google's index hasn't caught up. Legal court orders are appropriate when litigation has produced a favorable ruling that includes a de-indexing directive. Working with a news article removal attorney can help determine the strongest available path.
Publisher-side technical signals -- noindex and robots.txt -- require active cooperation from the publisher but can be pursued in parallel with other approaches. Most non-EU residents who are dealing with a live, unchanged article that has not been the subject of legal proceedings need to first work with the publisher directly to achieve either full removal or a noindex accommodation, because none of the unilateral de-indexing paths apply to live, accurate content published in jurisdictions outside GDPR's reach. In those cases, the path to de-indexing runs through the publisher -- which means a professional editorial removal request is often the essential first step before any de-indexing tool becomes available. Once source removal is secured, remember to also address Wayback Machine copies and review Google's removal policies to understand realistic outcomes at each stage.
Once Google processes a de-indexing request, the article disappears from standard Google search results -- typically within days to a few weeks of the request being approved. The article will not appear for name searches, topic searches, or any other query. However, several things can limit or reverse the effect of de-indexing and should be monitored. First, Google News is a separate index from Google Search, and content may remain in Google News results even after being de-indexed from standard search. Second, Bing, DuckDuckGo, Yahoo, and other search engines maintain their own indexes entirely independently of Google and must be addressed through separate requests to each engine. Third, if the publisher re-links to the article, acquires new external links, removes a noindex tag, or otherwise changes the technical signals pointing to the URL, Google may re-crawl and re-index it without notice.
After de-indexing is confirmed, set a recurring monitoring schedule -- running incognito searches for your name in Google, Bing, and DuckDuckGo on a monthly basis -- to ensure the article does not return. Incognito or private browsing mode bypasses personalization signals and gives you a more accurate picture of what a third party would see when searching your name. If an article reappears after de-indexing, the same removal request pathways are available to you again, and a pattern of re-indexing may strengthen a GDPR argument that the publisher is actively circumventing a legitimate privacy request.
Bing warrants specific attention as a parallel step. Bing is the search engine underlying Siri, Yahoo, MSN, and numerous other products -- meaning de-indexing from Google alone leaves a significant portion of search traffic able to find the article. Bing has its own Bing's content removal tool and offers EU RTBF requests for EU residents through its Bing Webmaster Tools. These should be submitted in parallel with Google requests rather than as an afterthought, because Bing's processing timeline is independent of Google's and may take additional weeks.
Navigating the de-indexing pathways is not inherently difficult for someone who understands the tools and which one applies to their situation. The challenge is that most people confronting a damaging article for the first time don't know which pathway is available to them, submit requests through the wrong tool, and receive automated denials -- not because their request was unmeritorious, but because it was submitted through a tool designed for a different situation. A GDPR request submitted through the outdated content tool will be denied. An outdated content request submitted for a live, unchanged article will be denied. Getting the pathway right is as important as the substance of the request.
RemoveNews.ai provides free editorial removal request generation and editor contact information for publisher-direct outreach -- the first step in the process for most situations involving live articles. For cases where de-indexing tools are the appropriate path, our specialists can evaluate your specific situation, identify which pathways apply, and guide you through the submission process. For the most complex cases involving EU GDPR requests, legal court order submissions, or cases where initial requests have been denied and appeals are appropriate, a consultation with our team provides an assessment of the realistic options available and the sequencing that makes the most sense.
The most common error we see is people attempting multiple tools simultaneously without a clear strategy, which can create a confused record that complicates subsequent approaches. De-indexing is most effective when pursued methodically -- starting with the fastest available pathway, confirming the result, and moving to the next pathway if needed. Our team has handled thousands of these cases and can identify the right starting point for your specific situation quickly, saving both time and the risk of inadvertently closing off better options through premature action.
Tell us about your situation and a removal specialist will personally review it and respond within one business day. No pressure, no obligation.
Before submitting requests through the wrong tool and getting automatic denials, speak with a specialist who can identify the right pathway for your specific situation -- free, no obligation.
A+ BBB · 100% Confidential · No upfront cost