What to Do After You Find a Clone of Your Store

Finding the clone is the easy part, honestly — if you’re still confirming one actually exists, start with the signals first. Once you’re sure, what happens in the next hour counts for more than what happens over the next week, because a cloner who suspects you’ve noticed will often pull the page down fast, and your evidence goes with it.

Document everything first

Get proof before you report anything, anywhere. Once a cloner suspects a report is coming, pages can disappear within minutes, and most platforms won’t act on a claim they can’t verify themselves.

• Screenshot the whole page, URL bar included, and the checkout flow too if you can get through it without actually buying.
• Save the page source, not just a screenshot of it. That’s your clearest proof the content was copied rather than independently written.
• Look up the domain’s registrar through WHOIS, and note the hosting provider if it’s visible.
• Screenshot the ad too, if that’s how you found it, along with the platform running it. Ad creative usually comes down faster than the page it links to.
• Write down the date and time. Later on, being able to say exactly when you noticed this can matter more than you’d expect.

Report it, in the right order

If there’s an ad involved, start there. Facebook, TikTok, and Google all run intellectual property complaint processes, and they usually move faster than a hosting takedown, since cutting off the ad spend is in their interest too. This step alone can choke off most of the clone’s traffic before the page itself ever comes down.

Next, file a DMCA takedown with the host, not the registrar. A WHOIS lookup or a look at DNS records usually points you to hosting information. Most hosts have a standard process for this and will act on a claim that’s actually documented, which is what your screenshots and saved source are for.

Only go to the registrar if the host doesn’t respond. Registrars move slower and are more reluctant to act, since pulling a domain is a much bigger step than pulling content. Treat it as your backup, not your first move.

If the clone is actually taking payments, get the payment processor involved. At that point it’s not really a copyright question anymore, it’s fraud, and processors like Stripe, PayPal, or Shopify Payments tend to act on that faster than a standard IP complaint. If you can tell which processor they’re using, this is often the quickest way to actually stop money moving.

A lawyer is worth it once the losses justify it, not before. One clone caught early usually doesn’t need one. A cloner who keeps coming back, or one hitting a campaign that actually matters to your business, is a different situation. A cease-and-desist on real letterhead tends to land harder than an individual complaint.

What not to do

Skip emailing the cloner directly. It rarely gets you anything besides confirming you’ve noticed, which just speeds up their move to a new domain before your reports even land. Don’t try anything that looks like unauthorized access to their site or hosting account either. Whatever it might feel like in the moment, it’s not worth the legal risk. And don’t assume one takedown fixes anything long-term. Someone who copied your page once can do it again within days, on a domain you haven’t found yet.

Set expectations correctly

A successful takedown gets rid of that one clone. The person running it is probably still out there, and there’s a decent chance they’re back on a new domain within the week. Think of each takedown as closing a single incident. If the same thing keeps happening, that’s a pattern worth dealing with directly, not just another report to file — our brand protection checklist covers what that looks like.

Reporting works, but it’s always a step behind. You find the clone, then spend real time getting it taken down while it’s still costing you sales. PageShield catches the clone the moment it goes live and redirects that traffic straight back to your store, before you’d even notice through analytics. If clones keep coming back for you, pageshield.io is the part that handles it automatically.