>
When a court enters a sealing order, it binds the clerk of court to restrict access to the official docket. What it does not do is reach the internet. News sites that covered the proceedings before the seal, PACER aggregators like CourtListener and Justia that mirrored documents the moment they were filed, and legal databases that indexed case materials as a matter of routine -- none of them are parties to the court's order, and none are automatically obligated to comply with it. The gap between a sealing order and search engine reality is the subject of this guide.
A sealing order binds the court clerk -- it does not bind Google, CourtListener, Justia, Law360, or news organizations. Each third party must be addressed through its own channel, legal or editorial.
PACER court documents accessed and mirrored before sealing are permanently indexed unless specifically addressed. The moment a document was downloaded from the federal court filing system, it became a copy outside the court's direct control.
A motion to compel de-indexing, filed in the same court that issued the sealing order, is the strongest legal tool available. Several federal district courts have granted these orders when the sealing rationale was sufficiently compelling.
News articles based on pre-sealing court filings have First Amendment protection but can still be updated or removed through editorial channels. Resolution of the underlying matter significantly improves the prospects for editorial removal.
A sealing order is an instruction from a judge to the clerk of court. It directs the clerk to restrict access to specified case materials within the court's own docket system. In federal courts operating under PACER and the Case Management/Electronic Case Files system (CM-ECF), sealing typically means reclassifying the relevant documents as restricted so that members of the public logging into PACER can no longer view them. Access is then limited to the parties, their counsel, and court staff.
The scope of a sealing order is precisely as broad as the court defines it. An order sealing a single exhibit applies only to that exhibit. An order sealing an entire case docket restricts access to all filings in that docket. In either case, the obligation runs to the court's own systems and personnel. The clerk must comply. Court IT staff must implement the restriction. Judges and their staff must treat the sealed materials accordingly.
The sealing order does not name CourtListener. It does not name Justia. It does not name Law360, Reuters Legal, or the local newspaper that covered the filing. These entities were not parties to the case. They are not bound by an order entered in proceedings to which they are strangers. This is not a loophole -- it is a fundamental feature of how court orders work. Orders bind parties and those acting in concert with parties. Third-party publishers who obtained information through legal means before the seal was entered have their own First Amendment and legal rights that a sealing order alone does not extinguish.
This distinction creates the practical problem that brings most people to this page. A court enters a sealing order, the petitioner assumes the matter is resolved, and six months later they search their name in Google and find a CourtListener page with their sealed complaint indexed and cached in full.
To understand why sealed records persist online, it helps to understand the mechanics of how court documents enter the public internet in the first place. Federal court filings in cases that begin as public proceedings are immediately accessible through PACER the moment they are docketed. Any member of the public with a PACER account -- which requires only registration and a credit card -- can download any document in a public case at the time of filing.
PACER aggregators operate automated systems that monitor new filings continuously. CourtListener, operated by the Free Law Project, runs scrapers against PACER that download newly filed documents within hours or even minutes of filing. Justia operates similarly. These systems were designed precisely to democratize access to federal court records, and they are extraordinarily efficient at it. By the time a party files a motion to seal -- let alone by the time the court rules on it -- the underlying documents may already have been downloaded, indexed, and made searchable through multiple aggregator platforms.
Legal press coverage adds a second layer. Law360, Bloomberg Law, Reuters Legal, and local reporters who monitor court dockets routinely access newly filed complaints, particularly in high-profile cases or cases involving recognizable parties. An article written based on a complaint filed before sealing quotes from the document and describes its allegations. That article is then indexed by Google, often within hours of publication, and begins to accumulate inbound links that strengthen its search ranking over time.
Background check and people search sites represent a third vector. Sites that aggregate public records from court dockets often do so through bulk data purchases or automated scraping. Once case data enters these aggregators' databases, it propagates across dozens of derivative sites, each of which may index independently and appear in Google results for the subject's name.
The Public Access to Court Electronic Records system was established under the E-Government Act of 2002 with a clear mandate: make federal court records accessible to the public. PACER has achieved that goal comprehensively. Tens of millions of documents are available through the system, and the downstream ecosystem of aggregators, legal databases, and research tools built on top of PACER has made federal court records more searchable than at any prior point in history.
The consequence of this success is that documents that are publicly filed, even briefly, leave a trace that survives sealing. When CourtListener's scrapers download a complaint at 2:00 AM on a Tuesday, and the court grants a motion to seal at 10:00 AM the same day, CourtListener has a copy of that complaint in its database. The court's sealing order does not reach CourtListener's servers. CourtListener is not a federal agency. It is a nonprofit organization in California operating a legal research platform.
The temporal gap between filing and sealing is often where the problem originates. A complaint filed in a rush to meet a statute of limitations deadline may be online for days or weeks before the party realizes it contains sensitive information and moves to seal. Even a same-day motion to seal typically requires a judicial ruling, which introduces additional time during which the document is publicly accessible and potentially being copied.
Some courts have developed procedures for filing documents under temporary seal pending a motion to seal, which narrows this window. But these procedures are not uniform across all federal districts, and state courts vary even more widely in their handling of sealed filings. Many state court systems lack the same aggregator infrastructure as the federal system, but where state court records have been incorporated into third-party databases, the same problem applies.
The motion to compel de-indexing is an underused but powerful tool. Filed in the same court that issued the sealing order, it directs court IT administrators to request removal from Google and from PACER mirror services. Several federal district courts have granted these orders when the sealing rationale was sufficiently compelling -- typically involving trade secrets, minor victims, or national security. The motion should specifically name the third-party platforms hosting the content and include documentation of their indexing of the sealed materials.
Several distinct legal mechanisms are available to parties whose sealed court records remain publicly accessible. They differ in strength, speed, and scope, and the right approach depends on which platforms are hosting the content and what the underlying sealing order says.
Motion to compel de-indexing is the most powerful tool available and is filed in the originating court. This motion asks the court to issue an order specifically directing named third parties -- Google, CourtListener, Justia, or other identified platforms -- to remove or de-index the sealed content. The legal basis is the court's inherent authority to enforce its own orders and to protect the purposes served by the sealing order. Courts that have granted these motions have typically required the moving party to demonstrate that the sealing rationale remains compelling, that the third parties were on notice of the sealing order, and that the content they are hosting is materially identical to the sealed court materials.
Google's Legal Removal Request tool accepts submissions from parties seeking removal of content from Google Search based on legal orders. Attaching a certified copy of the sealing order and identifying the specific URLs containing the sealed content gives Google the documentation it needs to evaluate the request. Google does not automatically comply -- it makes its own determination about whether the sealing order provides a sufficient legal basis -- but it has removed content in response to valid sealing orders, particularly where the content is directly reproduced from sealed documents rather than independently reported.
Publisher demand letters directed at CourtListener, Justia, Law360, and news organizations put those entities on formal legal notice of the sealing order and demand removal of the specific content. A demand letter accompanied by a certified copy of the seal order and a specific identification of the URLs at issue is the appropriate first step before considering litigation. CourtListener and Justia, as nonprofit organizations committed to public access to public records, have shown willingness to remove content when presented with valid sealing orders, because sealed records are no longer public records by legal definition.
For understanding how Google's content removal process works in detail, including what legal bases Google recognizes and how to structure a removal request, that resource covers the mechanics of the process from initial submission through appeal.
If the sealed record involved allegations that were later proven false or resulted in dismissal with prejudice, this is not just a sealing issue -- it is grounds for a much stronger editorial and legal removal campaign. Do not treat it solely as a sealing compliance question. A false allegation that was sealed and then dismissed carries different legal arguments for removal than a legitimately sensitive matter that was simply sealed for protection. Dismissal with prejudice, in particular, opens additional arguments about the news value of perpetuating coverage of allegations that were adjudicated as without merit.
For many individuals and companies, the most damaging content in Google is not the CourtListener page hosting the sealed document -- it is the news article that summarized, quoted, and analyzed the filing before the seal was entered. This content presents a distinct set of challenges because it involves journalism rather than direct document hosting.
News coverage of court proceedings published before a sealing order was entered is generally protected by the First Amendment. The article accurately described a public court filing at the time it was written. The reporter had a right to access the filing, a right to report on its contents, and a right to publish. A subsequent sealing order does not retroactively make that coverage unlawful, and it does not create a legal obligation on the publication to remove it.
That said, editorial channels remain open. Most publications have processes for considering corrections, updates, and in some cases removal of articles where circumstances have materially changed. The resolution of the underlying case matters significantly here. A publication that ran a prominent article about allegations at the time of filing is more likely to consider an update or removal request when the outcome of those allegations is known -- particularly if the outcome was favorable to the subject and the original coverage was prominent enough to warrant follow-up.
The editorial approach requires different framing than a legal demand. Publications respond better to factual arguments about the current accuracy of their coverage than to legal threats they know are unlikely to succeed. A request that explains how the matter was resolved, why continued indexing of the original coverage creates a misleading picture of events, and what a fair editorial response would look like has better prospects than a cease-and-desist letter asserting rights the publication's counsel will likely dispute.
For matters involving government press releases and online removal, which often accompany court proceedings, that resource addresses the specific challenge of government-originated content that cites or summarizes court filings.
CourtListener and Justia are operated by nonprofit legal organizations committed to public access to court records. They generally respond to legal requests backed by a valid sealing order more cooperatively than commercial sites, because their mission is access to public records -- and sealed records are definitionally not public records. A well-drafted demand letter citing the sealing order and specifying the exact URLs involved is often sufficient to initiate a removal review. Escalating to motion practice before attempting this direct approach leaves significant value on the table.
Sealed court records still showing in Google? We work with attorneys and reputation specialists to coordinate the legal and editorial removal process.
Get a Confidential AssessmentThe following steps reflect best practice for individuals and organizations whose sealed court records remain visible in Google search results. They are ordered by priority and should generally be executed in sequence, with legal counsel involved from the first step onward.
For context on how this process compares to the parallel situation involving expunged records that still appear online, that article covers the expungement-specific legal framework and where it differs from sealing in terms of available removal arguments.
| Source | Bound by Seal Order | Typical Removal Path | Legal Strength | Timeline |
|---|---|---|---|---|
| PACER / CM-ECF docket | Yes (at source) | Motion to compel + court IT | Highest | 4-12 weeks |
| CourtListener / Justia | No | DMCA or legal demand | Moderate | 2-8 weeks |
| Law360 / legal press | No | Editorial + legal basis | Moderate | 4-16 weeks |
| Local newspaper | No | Editorial request | Lower | 4-12 weeks |
| Google search result | No | Legal removal tool + seal order | Moderate-high | 6-16 weeks |
| Background check sites | No | Opt-out + demand letter | Moderate | 2-6 weeks |
A sealing order is the beginning of the process, not the end. Our team works with attorneys and reputation specialists to coordinate the legal demands, platform requests, and editorial outreach needed to close the gap between court reality and search engine reality.
Free assessment. Confidential. No obligation.