After the fact might be too late for this, but there are defensive programming techniques you can use to make a cloner's job a bit tougher. In some industries, this is more important than others.
> Obfuscate and compress your frontend code - It's harder to clone a big pile of random code that's not pretty.
> Put subtle watermarks in your site images - Makes their job harder and very easy to slip up.
> Use absolute rather than relative links so your own URLs appear everywhere in the site - It's easy for them to slip up and miss one.
> Use some of that obfuscated JS and frontend code to check what URL you're at and consider your options for redirecting, popping up a warning message, or rewriting the URLs in the body - it's a nightmare to try and figure out what a pile of crazy compressed JS actually does.
> Have your site rely on your own API in some fashion - hard for them to clone if they have to rely on you for the data.
> Put some hidden messages in your source code that might slide by a casual cloning job, but might be enough to verify ownership of the original code.
> Obfuscate and compress your frontend code - It's harder to clone a big pile of random code that's not pretty.
> Put subtle watermarks in your site images - Makes their job harder and very easy to slip up.
> Use absolute rather than relative links so your own URLs appear everywhere in the site - It's easy for them to slip up and miss one.
> Use some of that obfuscated JS and frontend code to check what URL you're at and consider your options for redirecting, popping up a warning message, or rewriting the URLs in the body - it's a nightmare to try and figure out what a pile of crazy compressed JS actually does.
> Have your site rely on your own API in some fashion - hard for them to clone if they have to rely on you for the data.
> Put some hidden messages in your source code that might slide by a casual cloning job, but might be enough to verify ownership of the original code.