How Do You Convert HTML to WordPress Without Losing Rankings?

To convert HTML to WordPress you have three real options (and two half-options covered in the table): turn the HTML into a WordPress theme by splitting it into header.php, footer.php, index.php and style.css; rebuild the pages inside WordPress with the block editor or a builder, keeping the design but not the code; or pay a conversion service to do either. For almost every small business site the second option is the right one, because the point of moving to WordPress is to edit pages without touching code, and a hand-converted theme leaves you exactly where you were. The first option is below in full for anyone who needs the pixel-identical result, then the rebuild method, then the part every guide skips: keeping the URLs and rankings the old site had.

Which way to convert HTML to WordPress should you use?

Method 1: convert the HTML into a WordPress theme

1. Create a theme folder in wp-content/themes/yourtheme/ with two required files: style.css (with the theme header comment at the top: Theme Name, Author, Version) and index.php.
2. Split the HTML. Everything from <!DOCTYPE> to the end of the navigation goes into header.php; the footer and closing tags into footer.php; the page body into index.php.
3. Add the WordPress hooks. <?php wp_head(); ?> before </head>, <?php wp_footer(); ?> before </body>, and <?php get_header(); ?> and get_footer() at the top and bottom of index.php.
4. Fix asset paths. Replace css/style.css and image paths with <?php echo get_template_directory_uri(); ?>/css/style.css; better, enqueue styles and scripts in functions.php with wp_enqueue_style.
5. Replace the static content with the Loop so pages come from the database: <?php while ( have_posts() ) : the_post(); the_content(); endwhile; ?>.
6. Make the menu dynamic with register_nav_menus in functions.php and wp_nav_menu() in header.php.
7. Add page.php and single.php for pages and posts, copied from index.php; the WordPress template file reference lists the full hierarchy.
8. Activate the theme under Appearance, Themes, create the pages, paste in the content, and test.

This produces a site that looks identical, with the design still living in template files. It is the right method for a developer who will keep maintaining the theme; for an owner who wants to edit the home page hero without opening header.php, it solves nothing.

Method 2: rebuild the pages in WordPress

1. Install WordPress on hosting (do you need hosting for WordPress covers the choice) on a staging subdomain, so the HTML site stays live throughout.
2. Pick a lean block theme (Twenty Twenty-Five, Ollie, or a blank theme for a builder) and set the fonts, colours and logo in the Site Editor to match the old site.
3. Recreate each page with blocks: cover, columns, headings, images, buttons. Paste text, upload images at the right sizes, and keep headings in the same hierarchy as the HTML.
4. Recreate the menu, footer and forms. Contact forms become a form plugin; any custom JavaScript becomes a plugin or a Custom HTML block.
5. Match the URLs (next section), then point the domain at the new host.

Two to three days for a typical brochure site, and at the end the owner can edit every page. Most “HTML to WordPress” projects I take on are this method, often combined with the design cleanup the old site needed anyway; custom design versus a theme explains when the rebuild is also the moment to redesign.

How do you keep the URLs and rankings?

Static HTML sites have URLs like /services.html or /about-us.htm; WordPress uses /services/. Every old URL with any traffic or links needs a 301 redirect to its new address, or the site starts over in Google.

1. Export the old URL list: Search Console, Pages report, plus a crawl with Screaming Frog or the sitemap.
2. Map each to a new WordPress slug. Where possible keep the slug identical minus the extension: /services.html to /services/.
3. Add redirects with the Redirection plugin or in .htaccess: Redirect 301 /services.html /services/. A regex rule handles the pattern in one line: RedirectMatch 301 ^/(.*)\.html$ /$1/.
4. Keep the title tags and meta descriptions from the old pages (copy them into Yoast or Rank Math), and keep the H1s.
5. Submit the new sitemap in Search Console and watch the Pages report for two weeks.

The redirect step is the same one that protects rankings in a WordPress domain change, and skipping it is the single most common reason a conversion “lost all our traffic”.

What gets lost or changed in a conversion?

• Speed. A static HTML page is the fastest thing on the web; WordPress adds PHP and a database. Caching, a lean theme and a decent host keep the difference small; the speed optimisation checklist covers it.
• Custom scripts. Sliders, calculators and animations built into the HTML need re-implementing as blocks, plugins or Custom HTML blocks.
• Forms. PHP mail scripts do not carry over; use a form plugin.
• Maintenance. The static site needed none; WordPress needs regular updates. That is the trade for editability and plugins.

Should you convert at all?

Convert when the site needs a blog, a shop, forms with logic, member areas, or an owner who edits pages. Keep the HTML site if it is five pages that change once a year and someone can edit them; a static site is fast, secure and free to run. If the reason for converting is really “the site looks dated”, the honest fix is a redesign on whichever platform fits, and the platform comparison is where to start that decision rather than with a conversion.

Frequently asked questions