How to move a static HTML site to WordPress (a non-developer's path)

01Why move an old HTML site to WordPress at all

If you have a site that was hand-built in HTML — maybe a Bootstrap template from years ago, maybe something a freelancer coded once and disappeared — you already know the pain. Changing a phone number means opening a file, finding the right line, and re-uploading. Adding a page means copying another page and editing the guts.

WordPress fixes the thing that actually slows you down: making changes. You log into a dashboard, click a page, type, and hit update. No FTP, no editing tags, no breaking the layout because you missed a closing div.

What you actually gain

• Edit in a browser. Update text, swap images, and add pages without touching code or re-uploading files.
• Themes. Change the entire look from a menu instead of rebuilding the HTML and CSS by hand.
• Plugins. Add contact forms, SEO tools, galleries, bookings, or a store by installing them — no custom coding.
• A blog and growth surface. Static sites rarely have a real blog. WordPress makes publishing routine, which is how most small sites grow their traffic.
• Maintainability. When you hand the site to someone else later, "it's WordPress" is a sentence they understand. "It's hand-coded HTML on FTP" is not.

This is the honest case for the move: you're not chasing a better-looking site, you're chasing a site you can keep up to date without dreading it.

02What you're trading away

Be clear-eyed about the trade, because it's real. A static HTML site has genuine virtues, and you give some of them up when you move to WordPress.

Static sites are tiny and fast. There's no database, no PHP, nothing to query — the server just hands over a file. They're also hard to hack because there's almost nothing to attack, and they rarely break on their own.

WordPress is dynamic. It builds each page from a database every time someone visits, which is slower by default and needs caching to feel fast. It has plugins and core software that need occasional updates, and an unmaintained WordPress site can get hacked in ways a flat HTML file never could.

So you're trading a frozen, low-maintenance site for a living one that needs light upkeep but bends to whatever you want next. For most small businesses that want to actually use their site, that's the right trade. If your HTML site is a perfect five-page brochure that never changes, you may not need this move at all.

03The plan, start to finish

There's no button that sucks in your old HTML and spits out a finished WordPress site. The migration is really a rebuild — but a structured one. Here's the whole shape of it before we go deep on the parts that trip people up.

• Pick hosting and install WordPress. Most hosts install it in one click; many will set it up for you.
• Pick a theme that's close to your current design rather than identical to it.
• Recreate your pages and content inside WordPress — copy text and re-add images page by page.
• Match your URLs to the old ones, or plan the redirects you'll need where they differ.
• Set up redirects so every old .html address points to its new home.
• Add the functional bits — contact forms, an SEO plugin, analytics — that the old static site faked with raw code.
• Test everything on a staging copy, then go live and point your domain at the new site.

Do it in that order and nothing surprises you. The two steps people skip — matching URLs and setting redirects — are the two that protect your Google rankings, so they get their own sections below.

04Matching your old design with a modern theme

The single biggest mistake non-developers make here is trying to rebuild their old site pixel for pixel. Don't. Chasing an exact clone of a hand-coded layout inside a theme is slow, frustrating, and usually ends with a worse site than if you'd just picked a clean, close theme.

Instead, look at your current site and name what actually matters: roughly the layout (one column or two, where the menu sits), your colors, your logo, and the general feel. Then pick a lightweight modern theme that already gets you most of the way there.

How to choose a theme that fits

• Favor lightweight, fast themes so you don't trade your old site's speed for a bloated one. A heavy theme undoes one of WordPress's few weaknesses on purpose.
• Match structure, not pixels. If your old site is a header, a menu, and a content area, almost any clean theme covers that.
• Set your colors and logo in the theme settings, which gets you 80% of "it looks like us" in minutes.
• Prefer themes built on the block editor or a portable builder so you're not locked in if you switch themes again later.

A close-enough theme that you can actually maintain beats a pixel-perfect clone you're afraid to touch. You can always refine the look later — the point right now is getting your content into a system you control.

05Recreating your pages and content

With a theme chosen, the bulk of the work is moving content over. For a small site this is genuinely just copy, paste, and re-add images — tedious but not hard, and no coding involved.

Go page by page. Open the old HTML page in your browser, copy the visible text, and paste it into a new WordPress page using the editor. Recreate headings as headings and lists as lists so the structure stays clean, rather than pasting one giant block of text.

For images, save each one from your old site (or grab the original files if you still have them) and upload them into the WordPress media library, then place them on the page. Don't hotlink to the old server — bring the files across so nothing breaks when you retire the old site.

If your old site has many pages, consider whether all of them still earn their place. A migration is a natural moment to drop dead pages — just remember that any page you drop still needs a redirect if it had traffic or backlinks, which the redirects section covers.

06Preserving your URLs and SEO

This is the part that protects whatever Google traffic the old site has. Your old pages live at addresses like /about.html or /services/web-design.html. WordPress, by default, uses clean URLs like /about/ with no .html. That mismatch is exactly where rankings leak away if you ignore it.

You have two honest options. The simpler one for most people: let WordPress use its clean URLs, then redirect every old .html address to the matching new one. The other option is to configure WordPress to keep the .html endings so the addresses stay identical — possible, but fiddly, and not worth it for most small sites.

Before you change anything, make a URL map

• List every URL on the old site. A free crawler like Screaming Frog will spider the site and hand you the complete list.
• Note which pages actually have traffic or backlinks. Those are the ones that must redirect — check Google Search Console and your analytics.
• Match each old URL to its new WordPress URL. /services/web-design.html maps to /services/web-design/, and so on.
• Set the WordPress permalink structure first, under Settings, Permalinks, so your new URLs are decided before you build the redirects.

Spend the half hour on this map. It's the difference between a migration Google barely notices and one that quietly costs you months of recovery.

07Setting the redirects

A redirect tells browsers and Google that a page has permanently moved to a new address, and it passes the old page's ranking value along. For a static-to-WordPress move, you want a 301 (permanent) redirect from each old .html URL to its new clean URL.

The non-developer way to do this is a redirect plugin — Redirection is the common free one, and most SEO plugins include a redirect manager. You paste in the old URL and the new URL for each page on your map, and the plugin handles the rest. No editing server config files.

• Use 301 (permanent), not 302 (temporary) redirects for moved pages.
• Point each old page to its closest match, never blanket-redirect everything to the homepage — Google treats a mass redirect to the homepage as a soft 404.
• Do the redirects the same day you go live, not next week, so visitors and search engines never hit a dead .html page.
• After launch, watch Google Search Console for 404s and add any redirects you missed.

Redirects feel like the boring chore at the end, but they're the single most valuable hour in the whole migration if the old site has any search traffic worth keeping.

08Images, content, and the functional bits

Static HTML sites often fake the dynamic features a real site needs. Your old contact form was probably a bit of embedded code or a mailto link; your analytics was a script pasted into every page. WordPress does these properly, with plugins instead of hand-pasted snippets.

• Contact forms: a form plugin (WPForms, Contact Form 7, and others) replaces the hand-coded form and actually delivers the messages reliably.
• SEO: install one SEO plugin (Yoast or Rank Math) to manage titles, meta descriptions, and your sitemap — things you previously edited by hand in each file's head.
• Analytics: add your tracking through a plugin or your theme's settings once, instead of pasting a script into every page.
• Images: bring every image into the media library, and consider an image-optimization plugin so the new dynamic site doesn't load slower than the old static one.

Resist installing twenty plugins on day one. Forms, SEO, analytics, caching, and image optimization cover almost every small site. Each extra plugin is something to update and a small chance of conflict, so add them only as you actually need them.

09The non-developer shortcuts

If the technical steps above made you wince, here's the genuinely good news: you don't have to do most of them alone. The hosting industry competes hard on making this easy for non-developers, and you should use that.

Many managed WordPress hosts offer free site setup or migration help as part of the plan. You sign up, tell them about your old site, and their team handles the WordPress install and a lot of the heavy lifting. Hostinger is the one we point readers to for that combination — free setup assistance, one-click WordPress, and built-in staging — but several hosts offer something similar.

Staging deserves a special mention. A staging site is a private copy where you build and test the whole WordPress site before any visitor sees it. You rebuild your pages, set redirects, and check everything on staging, then push it live in one move. That turns a nerve-wracking switchover into a calm one.

Use these shortcuts without guilt. The goal is a maintainable site you own and understand — not proving you can hand-configure a server. Let the host do the setup so you can spend your time on the content that actually represents your business.

10The going-live checklist

Going live is a deliberate step, not an accident. Before you point your domain at the new WordPress site, walk this list on your staging copy so the problems get caught before visitors do.

• Every page exists and its content matches the old site — nothing dropped by accident.
• All images load from the media library, with no broken links back to the old server.
• Your permalink structure is set and final, so URLs won't shift again after launch.
• Redirects are in place for every old .html URL on your map.
• The contact form sends and you actually receive a test message.
• Your SEO plugin has titles, descriptions, and a working sitemap ready to submit.
• The menu and internal links work and point at the new clean URLs, not the old .html ones.
• The site is tested on a phone, since that's where most visitors will see it.
• After going live, submit the new sitemap in Google Search Console and watch for 404s for a couple of weeks.

When that list is green, point your domain at WordPress and you're done. Keep the old static files backed up for a while — cheap insurance in case you spot something you missed.

11FAQ

Can I just import my HTML files into WordPress automatically?

Not cleanly. There are import plugins that attempt it, but they tend to drag in messy markup that's worse to maintain than a fresh rebuild. For a small site, copy-pasting content into clean WordPress pages gives a far better result and isn't much slower.

Will moving to WordPress hurt my Google rankings?

Only if you change URLs without redirecting them, or if the new site is much slower. Keep your URLs mapped and 301-redirected, pick a lightweight theme, and most sites see no lasting drop. Google cares about the address and the content, not whether the page is static or WordPress.

Do I need to know any code?

No. The whole point of WordPress is editing in a browser. The only place code-like work appears is pasting old and new URLs into a redirect plugin, and that's filling in two boxes, not programming.

How long does a small HTML-to-WordPress move take?

A simple five-to-ten-page brochure site is usually a focused weekend: a few hours to set up hosting and a theme, a few more to move content, and an hour on URL mapping and redirects. Bigger sites scale up mostly in the content-moving step.

Should I keep my old HTML site as a backup?

Yes, keep a copy of the old files somewhere safe for a few weeks after launch. It costs nothing and gives you a reference if you discover a page or image you forgot to bring across.

This is general, experience-based guidance from running a theme shop, not financial or professional advice for your specific site. When a site carries real revenue or traffic you can't afford to lose, treat that as the signal to get a professional or your host's migration team involved.