Copy any website to WordPress, as pages you can actually edit

The usual advice for this is bad. "Paste the HTML into a Custom HTML block" gives you an unmaintainable slab nobody can edit. "Use an iframe" is not a copy, it is a window onto somebody else's server. "Rebuild it by hand from a screenshot" is honest work but it is a week.

What you actually want is the page arriving in WordPress as blocks — sections you can click into, headings you can retype, images in the media library — with the page's own CSS carried alongside so it still looks like the thing you copied.

How the conversion works

CopyAnySite captures the rendered page in your browser, then converts it on the way out:

1. Sectioning. The rendered DOM is split at the structural seams a designer would recognise — header, hero, feature rows, testimonial band, footer — rather than at arbitrary depth. Each becomes one block.
2. Blocks, not soup. Each section is emitted as a sitegrab/section block: real Gutenberg markup with the section's own scoped styles attached, so the editor shows it as one manipulable unit.
3. Styles extracted, not inlined everywhere. The computed CSS the page actually uses is written out as a stylesheet the companion plugin enqueues, so you are not editing a page where every element carries a 400-character style attribute.
4. Assets localised. Images, SVG, fonts and background images are embedded or imported rather than hotlinked. This matters more than it sounds: hotlinked assets vanish the day the source site adds referrer protection, and it was a real bug we shipped a fix for — a WordPress export that left 192 remote image references now leaves none.
5. Import. A small companion plugin exposes a REST endpoint (wp-json/sitegrab/v1); the extension posts the converted page straight into your site as a draft. Nothing is published until you publish it.

What comes across, and what does not

Comes across: layout and spacing, typography including webfonts, colours and gradients, images and inline SVG, pseudo-element decoration, the settled state of scroll animations, section structure, and alt text.

Does not: the source site's plugins, its forms' destinations, dynamic queries (a "latest posts" grid arrives as the posts that were on screen), anything driven by the visitor's session, and the source theme's own admin options. A copied page is a static design in your CMS, not a working clone of their installation.

That boundary is deliberate. If you want an editable page you can rewrite, you get it. If you wanted their backend, no tool can give you that.

The honest workflow

1. Open the page you own or have permission to reuse. Capture it.
2. Export → WordPress. Install the companion plugin on the target site, paste the site URL and an application password, import as a draft.
3. In the editor, replace the words and images with yours. This is the step people skip and it is the one that matters — see is it legal to copy a website for why.
4. Check the page with the source site unreachable (open it in a private window with the source domain blocked). If something breaks, an asset is still remote.

Full walkthrough with screenshots: convert a website to WordPress.

Why not a page-builder import?

Elementor, Divi and friends each have their own serialised format, and an importer that targets one of them ties your copy to that builder forever. Gutenberg is core WordPress — block markup is just HTML comments around standard HTML, so a page imported as blocks stays readable and editable even if you later switch themes or drop the plugin. If your site is built on a page builder, the blocks still render; you edit them as blocks rather than in the builder's canvas.

FAQ

Can I copy any website into WordPress?

You can convert any page your browser can render into editable WordPress blocks. You cannot import the source site's plugins, database or backend behaviour, and you should only republish content you have the right to use.

Does the copied page stay editable in Gutenberg?

Yes — each section arrives as a block you can select, reorder and retype into, with the page's extracted CSS enqueued separately rather than baked into every element.

Will the images be hosted on my site or the original one?

On yours. Images, SVG, fonts and CSS background images are localised during export; nothing is left hotlinked, which is what keeps the page working after the source site changes.

Do I need a plugin on my WordPress site?

Yes, a small companion plugin: it registers the section block, enqueues the extracted CSS and exposes the REST endpoint the extension imports through. It does not phone home.

Can I copy a whole site into WordPress, not one page?

Yes, by crawling: the extension can capture a set of pages in one run and export each as its own draft. Expect to tidy navigation and forms afterwards, since those depend on the destination site's structure.

Keep reading

Clone any website — what a clone can and cannot include

Clone" promises more than any tool delivers. Here is the part of a website that genuinely clones, the part that never will, and how to tell which you need.

A Chrome extension that copies any website — how it works, and why in-browser wins

Why a browser extension copies pages that URL-based tools cannot, what CopyAnySite's MV3 extension actually does with the page, and what permissions it needs.

Copy any website's design — the layout, type and palette, not the content

How to extract a site's real design decisions — type scale, spacing rhythm, palette, grid, motion — and reuse them legitimately instead of copying the page itself.

Copy any website free — the options, and where each one breaks

Five genuinely free ways to copy any website, what each keeps, where each falls apart, and the measured fidelity of every one with the original server offline.