How to Remove Court Records From Google

Removing court records from Google almost never means deleting the record itself, because most court records are public and cannot be erased on request. What you can usually do is remove or de-index the Google search result that surfaces the record, or clear the underlying record through sealing or expungement so the copies lose their basis. Those are two different problems with two different solutions, and confusing them is the single biggest reason people waste months. This guide walks through both, in order: confirming what Google will actually remove, de-indexing at the source, sealing and expungement, redaction under Federal Rule of Civil Procedure 5.2, the specific aggregator opt-outs, realistic timelines, and the tactics that do not work.

Court records are public, so "delete" is the wrong goal

In the United States, court proceedings and their records are presumptively open to the public. Dockets, filings, judgments, and opinions are accessible so the justice system stays accountable, and that openness is exactly why you generally cannot ask a court or a website to erase a record simply because it is embarrassing. There are genuine exceptions (sealed cases, juvenile matters, expunged records), but the default is access. Reframing the goal helps: for most people the realistic aim is not deleting the record, it is controlling whether it appears when someone searches your name. Once you accept that, the work becomes concrete and winnable instead of a losing fight against the concept of public records.

The record versus the Google result

Picture two separate things. One is the court record, sitting in a court's case-management system or on an official docket site. The other is the Google result: the link, title, and snippet that appears when someone searches you and points to a page displaying that record. De-indexing removes the second without touching the first. The page and the record can still exist, but if the result no longer surfaces in a name search, its practical impact on employers, clients, landlords, and anyone running an informal background check drops dramatically. Most successful court-record cleanup is really about the result, not the record. If you are trying to understand your exposure before you start, a structured reputation audit maps every URL and platform showing the record so you attack them in the right order.

Step 1: Confirm what Google will and will not remove

Start here, because it prevents a common dead end. Google's personal-information removal policy will take down results exposing data that enables real harm: your home address, phone number, or email; Social Security, tax ID, or government ID numbers; bank and credit-card numbers; images of handwritten signatures or IDs; confidential login credentials; and certain medical records. Google also removes doxxing content, meaning personal information published alongside threats or an intent to harass. You can file these through Google's personal information removal request, and the newer Results about you tool helps you find and monitor pages exposing your contact details.

Here is the nuance almost every competing guide glosses over: Google states that when the information appears as part of the public record on a government or official source, it generally will not remove the result. In other words, a result pointing to an official court docket or a government website is usually outside Google's policy removals, and so is content Google considers newsworthy. That is not a reason to give up, it is a reason to aim correctly. Google removals work best when a page exposes redactable personal identifiers (an unredacted Social Security number or birth date in a filing, for example) or when the source is a commercial republisher rather than the court itself. For the record as a whole, the leverage is at the source and in the courts, which is where Steps 2 and 3 come in.

Step 2: De-index or remove at the source

Because Google indexes pages it finds elsewhere, the durable move is to get the hosting website to remove the page or block search engines from indexing it. When a site takes a page down or applies a `noindex` directive (via the robots meta tag or an X-Robots-Tag HTTP header), the result eventually falls out of Google on its own. This is faster and more reliable than fighting Google directly, because you are removing the thing Google is pointing at. The discipline that makes it work is precision: identify the exact URL for each copy, match it to that site's removal or redaction process, and document a specific basis (a sealing order, an expungement, an unredacted identifier, a factual error, a genuine privacy or safety risk) rather than a general objection to being visible. This source-level work is the core of professional court record removal, and it is often the single highest-leverage step.

Sealing and expungement: fixing the record itself

When you can change the underlying record, do it, because it is the most durable fix of all. Expungement erases or destroys a record; sealing restricts public access to it. Both are court processes with eligibility rules that vary sharply by state and by the type of case, and they generally apply to criminal matters rather than civil litigation. The typical path is to confirm eligibility, gather the case documentation, file a petition with the court where the matter occurred, sometimes attend a hearing, and obtain a signed order. Once you have that order, it becomes powerful leverage: you can send it to every site republishing the record, and a platform hosting a now-sealed or expunged case is standing on far weaker ground. Because eligibility is jurisdiction-specific and the paperwork matters, confirm your options with a local attorney before assuming a record can or cannot be cleared. Sealing and expungement are slow, but nothing else produces a cleaner result.

FRCP 5.2 redaction: when sensitive data was never supposed to be public

Sometimes the goal is not removing the whole record but stripping the sensitive data inside it, and this is one of the strongest tools when it applies. In federal cases, Federal Rule of Civil Procedure 5.2 requires that personal identifiers in filings be limited to partial forms: only the last four digits of a Social Security or taxpayer-ID number, only the year of an individual's birth, a minor's initials rather than full name, and only the last four digits of a financial-account number. Many state courts have parallel rules. Critically, in the federal system the responsibility to redact rests on the filer, not the clerk or the court, so unredacted identifiers slip through often. If a filing or a republished copy exposes information that should have been redacted, you have a concrete, actionable basis to ask the source to correct it and to ask Google to remove the exposed identifiers. It is narrower than de-indexing an entire result, but where it applies it is decisive.

The aggregator sites and how to opt out of each

A large part of the visibility problem is not the court's own site but the commercial and non-profit platforms that republish court data and are built to be indexed, so they frequently outrank the original docket for your name. Handle them individually, because each has its own posture. PACER is the federal judiciary's official access system, and because it is an official government source, Google generally will not remove PACER-based results on privacy grounds, which pushes you toward redaction and sealing at the court level. UniCourt accepts a public-records redaction request (you submit your name, email, the record URL, and a reason) and reviews it, generally within about 30 days, blocking approved records from search engines. CourtListener, run by the non-profit Free Law Project, will not remove a public document without a court order, but on a written request it will typically apply a search-engine block within hours using `noindex` directives, so the page stays on its site but drops out of Google over time. Justia and PlainSite each have their own contact or block-from-search request processes. Because these copies proliferate, court-record cleanup usually means working several aggregators in sequence rather than fixing one central source. Where a lawsuit or docket page is the specific problem, a dedicated content removal effort tracks each platform's process to completion.

It is worth being realistic: not every aggregator will act on request, and some republish material that is genuinely public and lawful to display. In those cases the lever shifts back to de-indexing the specific result, clearing the underlying record where you are eligible, and, if neither is possible, suppression.

Google's Refresh Outdated Content tool: the last cleanup step

After a page is removed or de-indexed at the source, the stale Google result can linger for a while, showing a cached link that now leads nowhere. That is what the Refresh Outdated Content tool is for. Once the source page is actually gone (returns a 404 or 410) or the specific words have been removed from the live page, you submit the URL and Google re-crawls it and clears the outdated result faster than waiting for its normal schedule. Use it as the closing move, not the opening one: it only works when the underlying page has genuinely changed, so it comes after Step 2, never instead of it.

Suppression: the realistic path when removal is off the table

When a record is public, lawful, and simply cannot be removed (an active case, a recent judgment, a matter of legitimate public interest), the honest strategy is suppression: publishing and strengthening accurate, authoritative content about you so it ranks above the record and pushes it off the first page, where the vast majority of searchers never look. That means an optimized personal or professional site, well-maintained profiles on platforms search engines trust, credible third-party coverage, and consistent, correct information about who you are. Suppression does not delete anything, and it is not instant, but for records that are here to stay it is often the only thing that meaningfully changes what people see. This is the discipline behind suppressing negative search results, and it pairs naturally with any removal work you have underway.

Timelines: how long each route really takes

Set expectations honestly, because the routes move at very different speeds. A search-engine block from a cooperative aggregator like CourtListener can apply within hours, though the result may take days to weeks to actually disappear from Google. Aggregator redaction requests commonly run up to about 30 to 60 days. Google's own removal requests are typically decided in days to a few weeks, when they qualify at all. Sealing and expungement are the slowest, often months, and depend entirely on your jurisdiction and case type. Suppression is a multi-month effort measured in quarters, not weeks. The practical approach is to run the fast levers (source de-indexing, aggregator opt-outs, outdated-content refresh) immediately while the slower structural fixes (sealing, expungement, suppression) work in the background.

What does NOT work

A few tactics reliably waste time or backfire. Asking Google to remove a result purely because it is embarrassing does not work when the source is an official public record. Contacting a court to "delete" a public civil filing you are not eligible to seal does not work. Paying a site that demands a fee to take down a record you could opt out of for free rewards a bad actor and often fails to remove copies elsewhere. Flooding Google with vague or duplicative requests can slow legitimate ones. Trying to bury a result with thin, spammy, or fake content violates search guidelines and can make things worse. And believing any guarantee of complete erasure is the biggest trap of all, because removal is outcome-dependent and no legitimate provider can promise it. Precision and patience beat volume and shortcuts every time.

When to get professional help

Plenty of people successfully de-index a single aggregator page or file a clean Google request on their own, and this guide is meant to help you do exactly that. Consider bringing in help when the record is republished across many sites, when active litigation or a recent judgment is involved, when sealing or expungement eligibility is unclear, or when the stakes (a job, a licensure, a deal) mean you cannot afford to get the sequence wrong. Reputation Resolutions has handled more than 5,000 engagements across 40-plus countries since 2013, and we will tell you plainly what is realistic in your specific situation before you spend anything. For anyone vetting a person or company where court history is the concern, reputational due diligence surfaces what is actually out there and how removable it is. The bottom line: separate the record from the result, confirm what Google will and will not remove, de-index and redact at the source, clear the underlying record where you are eligible, and suppress what genuinely cannot be removed.