← Go back

How Do You Remove Counterfeit Listings from Marketplaces?

Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team

The short answer

Enrol your brand in the marketplace's brand registry first — registry reports act fastest — then report each offending listing separately from your brand account, with the listing ID, the domain evidence behind it, a statement that you have not authorised the seller, and, for counterfeits, whether a test buy was made. Keep every case ID: repeat offenders are escalated by case history.

Run the free brand scan — one domain, no account, no card

What is counterfeit marketplace listings?

Counterfeit marketplace listings are product listings on Amazon, eBay, Etsy-class marketplaces that trade on your brand — often fed by a lookalike store domain. TakedownCoop's marketplace packet is filed via the marketplace's brand registry or report-a-listing flow, from your brand account, and treats every listing as its own reportable item.

What is counterfeit marketplace listings?

Counterfeit marketplace listings are product listings on Amazon, eBay, Etsy-class marketplaces that trade on your brand — often fed by a lookalike store domain. TakedownCoop's marketplace packet is filed via the marketplace's brand registry or report-a-listing flow, from your brand account, and treats every listing as its own reportable item.

Detection starts with the free scan on TakedownCoop's home page. From your one genuine domain, the scanner builds the candidate set an impersonator would plausibly register — typosquats made by deleting, transposing, duplicating or substituting letters, homoglyph lookalikes, affix combinations, and TLD swaps — and tests each candidate against live DNS. That order matters for counterfeit marketplace listings: generation first, evidence second, and nothing is called a hit until DNS or a certificate log says it is real.

How the scan ranks and records it

The results are ranked, not dumped. The scanner's own priority scores put a resolving lookalike with a certificate at 90 and one without at 80, registered-but-dormant names at 50 or 40 depending on whether a certificate exists, and CT-only discoveries at 35 or 30. Certificate Transparency evidence is filtered for relevance — shared certificates carrying unrelated names are not treated as evidence against your brand — and any check that could not be performed is reported as exactly that, never converted into a reassuring claim.

Registry first, listings second, history always

The marketplace checklist is sequenced deliberately. Enrolment comes first because registry reports act fastest; a brand that reports from outside the registry queues behind brands that enrolled. Listing-level granularity comes second: each ASIN or listing ID is reported separately with the evidence block's domain evidence, because marketplaces act on listings, not on sellers in the abstract.

History is the third lever. The checklist's final instruction is to keep case IDs because repeat offenders are escalated by case history — a seller with five prior cases is handled differently from a first-timer, but only if your filings link together. TakedownCoop's case tracking gives those IDs a home: each target is a case, and a reappearing seller re-opens the record instead of starting your evidence from zero.

A worked example, end to end

A fictional leather-goods brand, Tanline Workshop at tanlinewidth.com, finds 14 listings using its product photos, fed by tanline-workshop-outlet.com. It enrols in the marketplace brand registry on day one, then files 14 separate reports, each naming its listing ID, citing the lookalike domain, stating the seller is not authorised, and noting that one test buy was made and photographed. Each report returns a case ID, all 14 are logged against the scan, and when the same seller relists under a new name in week three, the case history is attached to the new filing.

Turning evidence into a filing

Evidence only helps if it arrives in the shape the channel expects. TakedownCoop's packet generator produces one packet per channel — registrar, host, Meta, Google Ads, marketplace, app store — each with that channel's own subject line and filing checklist, built on the same evidence block: genuine brand, lookalike domain, detection method, DNS and CT evidence, and priority. Packets are a Pro feature ($49/mo; Agency $99/mo covers multiple client brands), and they are prepared for the brand owner or their authorised agent to file.

  1. Enrol the brand in the marketplace's brand registry first if not already done — registry reports act fastest
  2. List each offending ASIN/listing ID separately with the evidence block's domain evidence
  3. State you have not authorised the seller and, for counterfeits, whether a test buy was made
  4. Keep case IDs — repeat offenders are escalated by case history
  5. Watch for relists and re-open the case rather than starting over

After you file: tracking the case

The follow-through is where most takedowns quietly die, so the product tracks it as a case. States run from evidence collected through packet built, submitted and provider response, to resolved — and a case can be re-opened as reappeared when monitoring finds the same threat back. Submitted and provider-response states are recorded as holder attestations, honestly labelled, while a verified resolution needs a re-scan showing the target is gone. The recheck after submission is set at seven days.

Where efforts like this usually go wrong

The commonest failure with counterfeit marketplace listings is treating it as a message instead of a case. A report typed from memory, sent from the wrong account, missing its ticket number within the week — each is a small thing, and together they are why impersonators outlast brands that were right about everything. The artefacts exist to remove memory from the loop: the evidence block is generated, not recalled; the checklist is written for the channel, not improvised; the case holds the IDs, not an inbox thread nobody can find in month two.

There is also a sequencing mistake: acting on the loudest artefact instead of the highest-priority one. A furious customer message about a dormant name feels urgent; a quiet scan result showing a live, certified clone is urgent. The priority score exists to arbitrate exactly that conflict — 90 before 40, live before loud — and the teams that follow it spend their filing hours where the money is actually leaving.

Keeping it from coming back

Impersonators rotate, so a one-off filing is a snapshot, not a solution. Monitoring re-scans the domain, and when a known threat reappears the case re-opens and its packet regenerates. Pair that with the verified-genuine page — a public page where customers can confirm they are dealing with the real brand — and the timeline export (JSON and CSV) that processors and insurers ask for, and counterfeit marketplace listings stops depending on whoever happens to notice the fake next.

Frequently asked questions

Why enrol in a brand registry before reporting?

Because registry reports act fastest — that is the first line of the marketplace packet's own checklist.

Can I report all the listings in one submission?

The checklist says to list each offending ASIN or listing ID separately. Marketplaces act on listings, so each gets its own report and case ID.

What does the lookalike domain have to do with a listing?

Listings need traffic, and the lookalike store is usually the traffic source. The packet's subject names it, and the domain evidence travels with the listing report.

Is a test buy required?

No — the checklist asks you to state whether one was made, for counterfeits. State it truthfully either way.

Keep exploring

TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms

Related guides