Skip to content
Black Friday 50% off + 15,000 credits Ends Nov 30 Ends Nov 30 see the deal
Black Friday15,000 free credits + 50% offends Nov 30

How to Convert HTML to WordPress (3 Ways, Step by Step)

Moving a static HTML site to WordPress is three jobs: getting the content in, matching the design, and keeping your URLs so you don't lose search traffic. Here is each way to do it: by hand, with an importer plugin, or with an AI agent.

Updated WPOSAI + WordPress How-TosContent & Delivery Workflows
In this article
  1. 01The short answer
  2. 02Before you start
  3. 03Way 1: rebuild it by hand
  4. 04Way 2: import the pages with a plugin
  5. 05Way 3: let an AI agent rebuild it
  6. 06Keep your URLs and rankings
  7. 07Forms, scripts and other things that break
  8. 08Where WPOS fits
Key takeaways
  • Install WordPress first, ideally on a staging copy, and keep the old site live until you switch.
  • Rebuilding by hand in a theme or page builder gives you pages your team can edit.
  • HTML Import 2 imports a folder of pages and images, but it hasn't been updated since 2017.
  • An AI agent such as WPOS can rebuild each page in the builder you use: Gutenberg, Elementor or Divi.
  • Redirect every old .html URL to its new page with a 301, and keep each page's title and description.
  • Submit the new sitemap in Search Console and watch for 404 errors after launch.

The short answer

Install WordPress, rebuild or import each page, then redirect every old .html address to its new WordPress URL. Pick the way that fits the site:

  • By hand: best for small sites, or when you want a fresh design in a theme or page builder.
  • With an importer plugin: HTML Import 2 brings in a whole folder of pages, but it hasn’t been updated since 2017.
  • With an AI agent: WPOS rebuilds each page in Gutenberg, Elementor or Divi, so the pages stay editable.

WPOS is our product. The plugin details below were checked in the WordPress.org plugin directory on 7 November 2026.

Before you start

  1. Get WordPress running. Install it on your host, or build on a staging copy first so the old site stays live until you switch.
  2. Copy the old site. Download every HTML file, image, stylesheet and script, and make a list of every page address, from the files or by crawling the live site.
  3. Save the SEO details. For each page, note the title tag, meta description and main heading, and export the pages that get traffic from Google Search Console.
  4. List what isn’t content. Contact forms, analytics tags, maps, booking widgets and any JavaScript all need a new home in WordPress.
  5. Decide how exact the copy must be. Rebuilding in a theme or builder gives you pages anyone can edit; keeping the original HTML keeps the exact look but is edited as code.

Way 1: rebuild it by hand

For a site of up to a few dozen pages, rebuilding is usually cleaner than importing, because you end up with pages your team can edit.

  1. Pick a theme, or a page builder such as Elementor or Divi, that can match the layout. In a block theme, set the colors and fonts in the Site Editor’s Styles first, so every page picks them up.
  2. Create each page, paste the text from the old HTML, and rebuild the sections with blocks or builder widgets. Our landing page guide walks through both.
  3. Upload the images to the Media Library and add alt text, rather than linking to the old image files.
  4. Rebuild the menu in the Site Editor (block themes) or under Appearance → Menus (classic themes).
  5. For a section that is hard to rebuild, paste its original markup into a Custom HTML block (in Elementor, the HTML widget; in Divi, the Code module) and add its CSS under Additional CSS.

Developers can turn the HTML template itself into a theme. A classic theme needs at least a style.css with a header comment and an index.php. Split the shared markup into header.php and footer.php, and keep the wp_head() and wp_footer() calls, or plugins and analytics won’t load. A block theme needs a style.css too, plus HTML templates such as templates/index.html, and usually a theme.json file for the colors and fonts. The style.css header looks like this:

/*
Theme Name: Old Site
Author: Your Agency
Version: 1.0
*/

If the new design means switching an existing WordPress theme, see how to change your WordPress theme without breaking the site.

Way 2: import the pages with a plugin

HTML Import 2 is the best-known importer. It reads a folder of static HTML files that you upload to your web server, and creates a page or post for each one:

  • You tell it which HTML element holds the content, such as <div id="content">, so the old header and footer are left out.
  • It keeps the folder structure as parent and child pages.
  • It can import linked images and documents into the Media Library.
  • When it finishes, it lists redirect rules from each old file to its new address.

The catch: on 7 November 2026 it had 5,000+ active installs but no update since November 2017, and it was last tested with WordPress 4.6. Run it on a staging copy, check every page afterwards, and remove it when you’re done. Its redirect rules are written for Apache’s .htaccess file; on Nginx hosts, add the redirects with a plugin or in your host’s dashboard instead.

An importer brings in the text and images, not the design: the pages take on your WordPress theme’s look, so plan time to fix the layouts.

Way 3: let an AI agent rebuild it

An AI agent can do the rebuild for you, page by page, in the builder the site already uses. With WPOS:

  1. Install the WPOS plugin on your WordPress site, or start in a WPOS sandbox: a WordPress site WPOS spins up with no hosting to set up.
  2. Give the agent the old site’s address while it is still online.
  3. Ask for the rebuild in plain language:

“Rebuild the five pages of our old HTML site at example.com in Gutenberg. Keep the copy word for word, upload the images to the Media Library with alt text, use the site’s colors and fonts, and add a 301 redirect from each .html address to its new page.”

WPOS works in the builder the site already uses (Gutenberg, Elementor or Divi), so every page stays editable there. It copies the images into the Media Library first and checks its own work before it reports done. When a page has to match the original exactly, it can assemble it from the original HTML and CSS instead of redrawing it. A site built in a sandbox moves to your real host with a migration key.

Keep your URLs and rankings

Search engines have your old addresses indexed, such as /about.html. WordPress uses addresses like /about/, so every old URL needs a 301 redirect to its new page, or the traffic it earned is lost.

  1. Map every old URL to its new one in a spreadsheet, starting with the pages that get traffic.
  2. Add the 301 redirects with a plugin such as Redirection, in your host’s dashboard, or with your SEO tool.
  3. Copy each page’s title tag and meta description into your SEO plugin.
  4. Keep the headings and wording of pages that rank well; small edits are fine.
  5. After launch, submit the new sitemap (WordPress serves one at /wp-sitemap.xml, or use your SEO plugin’s) in Google Search Console, and watch its Pages report for 404 errors for a few weeks.

For a bigger move, our WordPress site migration checklist covers the rest.

Forms, scripts and other things that break

  • Forms: static sites often post to a third-party form service. Rebuild the form with a WordPress form plugin and send a test entry before launch.
  • Analytics: add Google Analytics or Tag Manager once for the whole site, instead of pasting the code into every page.
  • Relative links: paths such as ../images/logo.png break in WordPress. Point them at the files in the Media Library.
  • Scripts: sliders and widgets that relied on old JavaScript libraries usually need a block or plugin instead.
  • Site icon and robots.txt: add your favicon as the WordPress site icon, and check that robots.txt still lets search engines crawl the site.

Where WPOS fits

A migration is a good first job to hand WPOS. Its agent works inside wp-admin on the sites you already run, on any host, in the builder each site already uses (Gutenberg, Elementor or Divi), and it checks its own work before it reports done.

WPOS is our product, so weigh this section accordingly; you can try it free for 30 days with 5,000 credits, a live site plus a staging sandbox, and no card.

Frequently Asked Questions

Partly. An importer plugin such as HTML Import 2 can turn a folder of HTML files into pages, but it brings in the content, not the design, and it hasn't been updated since November 2017. An AI agent such as WPOS can rebuild the pages and the design in your page builder, and you review the result before it goes live.

Usually not, if you add a 301 redirect from every old URL to its new page, keep each page's title and meta description, and submit the new sitemap in Search Console. Expect some movement for a few weeks while Google recrawls the site.

Posts can, if you end the permalink structure in .html under Settings → Permalinks, but pages normally get addresses like /about/. It is simpler to add a 301 redirect from each old .html address to its new page, which keeps the visitors and the search traffic.

Yes. Use the Custom HTML block in the block editor, the HTML widget in Elementor or the Code module in Divi. The markup stays exactly as it is, but you edit it as code, and its CSS has to be added separately.

It depends more on the number of pages and how exact the copy must be than on anything else. Rebuilding by hand suits a small site; an importer or an AI agent saves the most time on sites with dozens of pages. Either way, leave time for the redirect map and a check of every page.

HTML Import 2 is free on WordPress.org, but it was last updated in November 2017, so test it on a staging copy first. Rebuilding by hand costs only your time, and WPOS has a 30-day free trial.

Black Fridayends Nov 30

Start free with 15,000 credits.

Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.

Claim 15,000 credits