Clone a website you own, or use it as a reference?

Suppose your old campaign page is still live, but the agency that built it never handed over editable files. A reconstruction can recover the visible layout as a new HTML draft. You can inspect the result, change the copy, and replace the old assets. This is a sensible use of cloning because the page and its content are yours to work with.

It is not source-code recovery. The public page cannot tell the builder how the original CMS was configured, where a form submitted, which analytics events fired, or what happened after login. List those functions before you start so the draft does not quietly become your launch plan.

A site you admire may solve a design problem you also have: explaining a technical product, showing how a service works, or placing proof before a pricing decision. In that case, study the choice rather than asking for a close replica. Write down its section order, image balance, proof placement, and how often it repeats the main action. Then explain which decisions serve your own buyer.

Use your company's content source for the facts, claims, screenshots, and identity. A reference site's customer quote is not an empty slot to fill with an invented one. If you cannot support a section with real material, change the section or leave it out.

For a redesign, make a two-column note before generating anything. In one column, record what you are taking from the reference: perhaps a narrow hero, a three-step product explanation, and a customer-proof block after the demo. In the other, record what must come from your business: the offer, buyer, product images, named customers, results, and call to action. This small separation prevents the reference from becoming the source of your claims.

For a clone of your own page, the note is different. Record the original URL, who controls it, which images and fonts you may reuse, and the behavior you need to rebuild outside the visible page. That gives you a review list for the draft rather than a vague request to 'make it the same.'

Open the draft at phone and desktop widths and compare all sections and real content, not the first screen alone. Follow every navigation link and call to action. Test forms with a safe address, check keyboard focus, and read the page without images. If the old site had multiple routes, one cloned page does not recreate them automatically.

Finally, ask whether you can change a headline, replace an image, and adjust a section without starting over. The value of an editable clone is control over the next revision. If the page looks close but cannot be maintained, you have moved the dependency rather than removed it.