How to write a takedown notice that does not bounce

A takedown notice should make the reviewer's next action obvious. It should not ask them to investigate from scratch, guess what policy applies, or work out whether the person complaining has authority to complain.

Most bounced notices have the same problems: missing URL, unclear ownership, no screenshot, wrong category, no explanation of harm, or a report sent to a provider that cannot remove the target.

Start with the exact target

Never start with "there is a fake site." Start with the exact URL, handle, app listing, marketplace listing or domain.

If there are multiple targets, list them cleanly. Group related URLs by platform or provider. If the target is a redirect, include the visible URL and the final landing URL. If it only appears in a certain region or device, say that.

The best first line is concrete:

"This Instagram account is impersonating our CEO and directing customers to a fake investment group."

That sentence tells the reviewer what it is, who is harmed, and why it matters.

Match the claim to the channel

Different channels expect different proof.

For copyright, show the original work and the copied work. For trademark, show the mark and the confusing use. For impersonation, show the real identity and the fake identity side by side. For phishing, show credential or payment collection. For malware, show the download path and indicators.

A single bad page can support several claims, but the notice should lead with the claim the recipient can act on fastest.

If a fake store uses your logo and collects card details, the host may move faster on fraud and phishing than on a trademark-only complaint. If a marketplace listing uses your product photos, the marketplace may need IP evidence and seller information. If the issue is a whole lookalike domain, a registrar abuse report may be the escalation path.

Attach proof of standing

Standing means: why are you the right person to ask for removal?

Useful proof includes:

• Official website or verified social profile.
• Trademark registration or brand record.
• Company domain email.
• Business registration.
• Original source files, publication timestamps or product pages.
• Authorization letter for agencies or employees filing on behalf of a brand.

Do not assume the reviewer knows your brand. A famous brand still needs a clean proof trail because abuse queues are built for speed and auditability.

Keep evidence readable

Evidence should be easy to open and understand. Use screenshots with visible URLs or handles. Name files clearly. Avoid dumping a folder of unrelated images with no explanation.

A strong evidence pack often has:

1. Screenshot of the fake page or account.
2. Screenshot of the real page or account.
3. Screenshot of the harmful action: login form, payment request, scam message or counterfeit listing.
4. Technical evidence when relevant: DNS, hosting, app package name, redirect chain or form endpoint.
5. Ownership or authorization proof.

That mirrors the evidence pack platforms need, but compressed into the exact claim you are filing today.

Close with a specific request

Do not end with "please handle this." Say what you want:

• Remove the page.
• Disable the profile.
• Suspend the domain.
• Delist the app.
• Remove the counterfeit listing.
• Disable the redirect URL.

Then provide a reply contact that can answer follow-up questions. Many cases stall simply because the provider asks for one more proof item and nobody sees the email.

Reuse structure, not stale wording

Templates help, but copied templates can hurt when they include irrelevant claims or outdated legal phrasing. Keep the structure consistent and change the body to match the case.

A good takedown notice is short, specific and provable. Exact target, matching claim, readable evidence, proof of standing, clear request. That is the difference between a report that bounces and a report that can move straight into review.