How to Convert HTML to WordPress: 4 Ways, and Which One Fits
Maybe it is a site someone hand-coded years ago, an HTML template you bought, or an export from Claude Design, Lovable, Bolt or v0. It looks right, but every change means editing code, and there is no blog, no easy forms and no SEO tools. WordPress solves all of that, once the site is in it.
There is no button that turns HTML into WordPress one to one. Every way of doing it is a rebuild of some kind, and they differ in what you get at the end: real WordPress pages your team can edit, or HTML pasted into WordPress. This guide walks through the four ways, what each one costs in time and skills, and how to move without losing your Google rankings.
Key takeaways
- No converter does it one to one. Every way is a rebuild; the question is how much of the work you do yourself.
- Choose by the result, not the method. Editable WordPress pages are worth more than a fast import of raw HTML.
- Keep your addresses. Every old .html page needs a 301 redirect to its new page, or rankings drop.
- An AI agent can now do the rebuild. Our own 8-page site went from an HTML export to native Gutenberg blocks in less than 2 hours.
Hand this to your AI first: fabrement.com/AGENTS.md. One link, and your agent knows what Fabrement can do on your site and how to connect to it.
Before you start
- Know what you have. The files (HTML, CSS, JavaScript and images, ideally as one zip), or only the address of the live site.
- List every page address now. You need the list for the redirects at the end.
- Know what stays behind. Logins, databases and server-side scripts are app logic, not pages; no way of converting carries them over.
- Prepare WordPress. A fresh install with HTTPS is easiest. If the HTML site is live, build on a separate address or a staging copy and switch when the new site is ready.
Which way should you use?
| Skills | Time for a small site | Editing afterwards | Design | |
|---|---|---|---|---|
| 1. By hand, as a theme | PHP, HTML and CSS | Days | Mostly through code | Exact |
| 2. Import plugin | None | Fast | Raw HTML in the editor | Often broken by CSS conflicts |
| 3. Page builder | The builder’s interface | Days | Visually, inside the builder | Close, rebuilt by hand |
| 4. AI agent with Fabrement | None; you describe it in words | Our 8 pages: under 2 hours | Native blocks with fields | Close, checked against the original |
If you would rather not do it yourself, a developer can take any of these routes for you, or our team can convert the site for you. The rest of this guide shows each one, so you know what you are asking for.
1. By hand, as a WordPress theme
This is the classic developer route: the HTML becomes the theme’s templates, and WordPress fills them with content.
- Create a theme folder in
wp-content/themeswith astyle.cssthat starts with a theme header (at leastTheme Name:) and anindex.php. - Cut the repeated parts out of your HTML: the top of the page into
header.php, the bottom intofooter.php, and load them withget_header()andget_footer(). Keepwp_head()andwp_footer()in them, or plugins stop working. - Load your CSS and JavaScript from
functions.phpwithwp_enqueue_style()andwp_enqueue_script()instead of hard-coded tags. - Replace the static navigation with
wp_nav_menu(), and the page text with the WordPress loop, so the content comes from the editor. - Create the pages in WordPress and paste the content in.
What you get: the exact design, and a theme you own. The catch: anything that is not plain text, like a pricing table or a hero with a button, stays in the template code unless you also build editable fields for it. For the owner, most changes still go through a developer.
2. With an import plugin
Import plugins read your HTML files and create a WordPress page for each one, with the HTML inside. It is the fastest way in, and it works well for one thing: archives with many simple text pages, such as old articles.
The catch: the pages keep their raw HTML, which is hard to edit in the block editor, and the layout depends on the old CSS, which your WordPress theme does not load, while the theme’s own styles clash with the old markup. Expect the text to arrive and the design to break.
3. Rebuild it with a page builder
You install a page builder plugin and recreate each section by hand, dragging in columns, headings, images and buttons until the page looks like the original.
What you get: pages you can edit visually, without code. The catch: rebuilding by hand takes days, the result is only as close as your patience, and the site now depends on the builder: its scripts load on every page, its pro features usually need a yearly licence, and moving away later means rebuilding again.
4. Let an AI agent rebuild it as native blocks
An AI agent connected to your WordPress site can do what a developer does in way 1, but it builds each section as a native Gutenberg block with editable fields instead of a fixed template. With Fabrement, a free plugin, the agent you already use (Claude, ChatGPT, Codex or Cursor) reads your HTML as the design source and rebuilds the whole site on your WordPress. Nothing is pasted in as raw HTML. See how HTML becomes Gutenberg blocks with Fabrement.
Step 1: Install WordPress and Fabrement
You need WordPress 6.9 or newer with HTTPS, PHP 8.0 or newer, and Fabrement installed and signed in. A fresh install is easiest, because the agent can then build without working around old content.
Step 2: Connect your agent
Open Fabrement → MCP Connection in wp-admin and connect the agent you use. Step by step: Claude, ChatGPT, Codex or Cursor. For a whole site, a client that handles a zip and a long session works best, such as Claude Code.
Step 3: Give it the files and the request
Attach the zip in a new session and send the request. This is the one we use, with the names replaced by placeholders:
The attached zip is a static website (HTML + CSS + JS, [number] pages).
Turn it into a real WordPress site using the Fabrement MCP server [your server name].
Rebuild every section as a native Fabrement block with editable fields, on a design system built from the site's colours and fonts. Build the header, footer and menus, all pages, a working contact form, and a post type for any repeating content such as [projects or team members].
Keep every page address. For each old .html address, create a 301 redirect to its new page.
Save new pages as drafts. Check every page on desktop and mobile against the original and fix the differences. When done, give a short report: what you built, the decisions you made, and what couldn't be carried over and why.
If you only have the live address, give that instead of the zip: the agent reads the pages and copies the images into your media library. This works when the pages are plain HTML. Sites that build their pages in the browser with JavaScript, such as Wix sites, are harder to read; for those, see how to move from Wix to WordPress. Have a Figma design instead of HTML? The same agent can convert Figma to WordPress too.
Step 4: Read the report, then review
Start with the list of what could not be carried over: it tells you exactly where to look. Then open each page on desktop and mobile. Ask for changes in the same chat, for example “make the hero shorter on mobile”, or edit text and images yourself in the block editor. When you are happy, publish.
What you get: the same design on native blocks, one design system for the whole site, real fields your team can edit, forms rebuilt with Contact Form 7, and repeated content as post types with their own archive. The catch: a long build needs enough usage on your AI plan, and the result still needs a person to review it. Our 8-page build ran about an hour on its own; a bigger site takes longer.
A Claude Design export, step by step
Move an HTML website to WordPress without losing rankings
Whichever way you choose, the move itself decides whether your Google traffic survives. Search engines know your pages by their addresses, so the goal is that every old address still leads somewhere sensible.
- Keep addresses where you can.
/about/can stay/about/. - Redirect every .html address. WordPress pages have no
.htmlending, so/about.htmlneeds a 301 redirect to/about/. With Fabrement the agent creates these redirects itself, with no redirect plugin. - Carry over titles and descriptions for every page, for example with Yoast SEO.
- After the switch, submit the new sitemap in Google Search Console and check the Pages report for 404 errors after a week.
After the move: run the site with your AI agent
Once the site is in WordPress, the same MCP connection keeps working. You run the site by asking your AI agent in plain language: new pages from the blocks you already have, texts and images, menus, forms, SEO titles and descriptions, redirects, and translations with WPML. New pages wait as drafts, and every block change can be rolled back. The team can still edit the same blocks in the WordPress editor whenever they prefer.
Fabrement: the workplace for your AI agent
A free plugin for WordPress 6.9 or newer. Connect your AI agent over MCP, and do all of this on your site from its chat.
What does not come over
Whatever made the HTML site behave like an app: logins, user accounts, databases, search and server-side scripts. These are not converted by any of the four ways. In WordPress they become plugins or custom features, and they are a separate project from moving the pages. Contact forms are the exception: every way above can rebuild them, with Contact Form 7 or a similar plugin.
Frequently asked questions
How long does it take to convert HTML to WordPress?
Can I keep my exact design?
Will I lose my Google rankings?
Can I convert a site from its live address only?
Do I need to know how to code?
What does it cost?
Can I turn an HTML template into a WordPress theme?
Sources
- WordPress Theme Handbook (theme files, style.css header, enqueuing scripts)
- Google Search Central: site moves with URL changes (301 redirects, sitemaps)
- Fabrement steps from our own AGENTS.md and the plugin’s MCP Connection screen; the build in the video is our own agency site, recorded on 21 October 2026.
Checked on 10 November 2026, with Fabrement 1.7.0. If a step has changed, tell us and we will correct it.