How a DMCA counter-notice works

What a counter-notice is

A counter-notification is the formal reply to a takedown notice under the US DMCA. It asserts that the material was removed as a result of mistake or misidentification, and it asks the service provider to restore it. It is the statutory route back — the mechanism that stops notice-and-takedown from being a one-way door.

It only becomes relevant once something has already been removed, so it sits at the end of a longer sequence — how the takedown process runs covers the steps that come before it, and what a copyright infringement notice establishes covers why an allegation on its own settles nothing.

It is worth being precise about what gets restored. If the notice went to your host and content was taken down, a successful counter-notice can put the content back. If the request went to Google and a URL was delisted from Search, what is restored is the search listing — the page itself was never removed. See how Search removal works.

What it has to contain

A counter-notification is generally expected to include:

• Your physical or electronic signature.
• Identification of the material removed and the location where it appeared before removal.
• A statement, under penalty of perjury, that you have a good-faith belief the material was removed as a result of mistake or misidentification.
• Your name, address and telephone number.
• A statement consenting to the jurisdiction of a specified federal district court, and that you will accept service of process from the party who filed the notice.

That last element is the one people skim past. You are agreeing in advance to be sued in a named court, and giving the claimant your contact details to do it with. If you are outside the US, you are typically consenting to a US court.

What happens after you file

1. The provider reviews it for the required elements. Incomplete filings are rejected.
2. Your details are forwarded to the claimant, including the contact information in your filing.
3. A statutory waiting period runs. Under the US framework this is typically described as roughly 10 to 14 business days.
4. If the claimant does not file a court action seeking to restrain the activity, the provider may restore the material.
5. If the claimant does sue, restoration does not happen and you are now in litigation.
6. The counter-notice may be published, in transparency data and in the Lumen archive.

Counter-notice, appeal, and simply asking

These are not the same instrument, and the informal ones are usually tried first. A platform appeal is an internal review under that platform's own policy: no sworn statement, no jurisdiction clause, and no fixed statutory clock. A retraction request asks the claimant to withdraw, which is the only route that ends the matter without a process at all. A counter-notification is the statutory mechanism described on this page, and it is the one with legal consequences attached. Where a platform offers an appeal, exhausting it before filing anything sworn is usually the cheaper order.

When a counter-notice makes sense

Reasonable grounds include:

• You own the material outright and can evidence it — originals, drafts, publication dates.
• You hold a licence covering the use, and can produce it.
• The notice named the wrong URLs, or swept your page into a bulk list by mistake.
• The material is in the public domain.
• The use is defensible as fair use — though this is a legal judgement, not a checkbox, and it is where advice matters most.

Weak grounds, which regularly get people into trouble:

• "I credited the source." Attribution is not a licence.
• "It was already on the internet." Publication is not permission.
• "I only used part of it." Partial use can still infringe.
• "I did not know." Knowledge is not the test.
• "A user uploaded it, not me." Relevant to your safe-harbour position, but not a basis for swearing the removal was a mistake.

Cheaper things to try first

A formal counter-notice is rarely the first move. Options that carry less risk:

• Contact the reporting organisation. For a bulk-list mistake, a short factual email identifying the URL often resolves it faster than any process.
• Approach the copyright owner. The vendor who filed may have no authority to withdraw; the owner does.
• Fix and republish. If the material genuinely is not yours, replacing it and publishing at a new URL is usually quicker and cheaper than a dispute.
• Licence it. Sometimes the rights holder would rather sell you a licence than fight.
• Do nothing. A legitimate option for a low-value URL. Not every removal is worth a legal process.

If the notice was abusive

The US framework includes a provision on misrepresentation — knowingly materially misrepresenting that material is infringing can expose the sender to liability for damages. In practice such claims are difficult and expensive to pursue, so treat it as context rather than a plan. If you suspect a pattern of abusive filings against you, the useful first step is evidence: the dates, the senders, the URLs. See false and abusive takedowns.

The official routes

For Google, start with the legal troubleshooter, which routes you to the right form, or go directly to the counter-notice form. Background is in Google's legal help centre. For content removed by a host or platform, use that provider's own process — the details vary.

Before any of it, establish exactly what is on the public record about your domain: which requests exist, who filed them, which URLs they named and what status each carries. A response drafted without that is a response drafted from someone else's summary — and if the request concerned Google Search, the removal message you saw is only one entry in it.

Check what has been filed against your domain

This page is informational and is not legal advice.

FAQs

Keep reading

Last reviewed 2026-08-26.