HTML to WordPress: How to Move a Page or Site
To convert HTML to WordPress, install WordPress on your hosting, choose a theme close to your design, recreate each page in the block editor by copying your content across, and set up redirects so old URLs lead to the new pages. For pages that need the exact original look, turn the HTML into a custom theme or block templates.
Searches for "HTML to WordPress" usually come from one of two people. One has a single HTML page, often from an AI assistant, that has grown into something they want to manage properly. The other has an older hand-coded site and is tired of editing files. The route is similar for both, and it is more manageable than it looks.
Before you start: decide what you are keeping
Make a short list:
- Pages and their addresses. Every URL that exists now, especially ones people link to or that bring visitors from search.
- Content. Text, images, downloads.
- Design. Is the exact look essential, or is "close and clean" fine?
- Features. Forms, embedded videos, scripts, tracking codes.
This list decides your route and stops you discovering a missing page a month after launch.
Three routes, from simple to exact
Route 1: rebuild with a theme
Pick a WordPress theme whose layout is close to your current design, then recreate each page in the block editor. Copy the text, re-upload the images, adjust colours and fonts in the theme settings.
Good for: most single pages and small sites. Effort: low to medium. Result: a clean, maintainable WordPress site that looks like your old one, not identical.
Route 2: paste HTML into blocks
WordPress has a Custom HTML block. You can paste sections of your original HTML into it and they render as they did. Styles may need to move into the theme's custom CSS.
Good for: a few special sections, such as a pricing table or a calculator, inside an otherwise normal WordPress page. Watch out: a page made only of HTML blocks is hard to edit later, which defeats the purpose of moving.
Route 3: turn the HTML into a theme
Your HTML and CSS become the templates of a custom theme. In modern block themes, that means template files and patterns built from your markup, so new pages automatically get your design.
Good for: sites where the exact look matters, or where many pages share the same layout. Effort: high, usually developer work.
Step by step for Route 1
- Get hosting and install WordPress. Most hosts install it in one click. Use your own domain, or a temporary address if the old site is still live there.
- Choose a theme close to your design. Block themes make later changes easier.
- Set permalinks under Settings, Permalinks to "Post name", so addresses look like
/about/. - Recreate pages. For each page on your list, create a WordPress page with the same address. Copy text across, re-upload images and set alt text.
- Set the home page under Settings, Reading.
- Rebuild menus under Appearance.
- Recreate forms with a form plugin, and check they send where they should.
- Add an SEO plugin to handle titles, descriptions and the sitemap.
- Set redirects for any address that changed (see below).
- Switch the domain to the new site and test every page on your list.
Keep your addresses, or redirect them
If your old page lived at /pricing.html and the new one lives at /pricing/, people following old links and search engines will hit a dead end unless you redirect. A 301 redirect tells browsers and search engines the page has moved permanently. You can set them with a redirect plugin or in your server configuration.
Google's guidance on site moves with URL changes explains how to do this without losing search visibility. If your original page lived on a free host's address, such as a pad, you cannot redirect it, but you can update the links you shared.
Moving a page from HTMLpad
If your page is on HTMLpad, open the pad's edit view, copy the full HTML or download it as a file, and use it as your source for any of the routes above. The content, structure and styles are all there. Keep the pad online until the new site is live, so the link you shared keeps working in the meantime.
Automated migration
Copying pages by hand is fine for a handful. For a larger site, or one stuck on a platform such as Wix, Squarespace or Framer, automated migration tools can extract the content and rebuild it in WordPress. Whichever you use, check that the result is a standard WordPress install in your name, with your content exportable, and keep the manual routes above for anything the tool misses.
Whatever tool you use, check the result page by page against your list. Automated tools get you most of the way; the last details always need a human eye.
After the move
- Test on a phone as well as a computer.
- Submit the new sitemap in Google Search Console.
- Watch for errors in Search Console for a few weeks, especially "not found" pages that need a redirect.
- Keep a copy of the old HTML for reference.
For the background on why sites outgrow HTML in the first place, read when a single HTML page isn't enough. The WordPress project's own documentation on getting started is a solid companion for the setup steps.
Frequently asked questions
Can I convert HTML to WordPress automatically?
Partly. Automated migration tools can import content and structure, especially from common platforms. Exact designs and custom features usually need manual work afterwards, so plan to review every page.
Will my HTML design work in WordPress?
Yes, with work. You can rebuild it with a similar theme, paste sections into Custom HTML blocks, or turn the HTML and CSS into a custom theme for an exact match.
Do I lose SEO when moving to WordPress?
Not if you keep the same addresses or redirect old ones with 301 redirects, keep your content, and submit the new sitemap. Changing URLs without redirects is the most common way to lose traffic in a move.
How long does it take to move an HTML site to WordPress?
A single page can be rebuilt in an hour or two. A small site of five to ten pages takes a day or two. A custom theme that matches the design exactly takes longer and usually needs a developer.