The redirects you must set when a theme change alters your URLs

01When a theme change actually changes your URLs

Start with the reassuring part: changing a WordPress theme does not, on its own, change a single URL. Permalinks are a site setting, not a theme feature. Most theme switches need zero redirects. The trouble starts when a redesign rides along with the theme change and quietly moves your addresses.

A redirect is only needed when the address of a page changes. That never happens because a page looks different — it happens because the path, slug, or structure underneath it changed. Four things cause that during a redesign, and it's worth knowing each one before you start.

Permalink structure changes

If you change the global permalink format under Settings, Permalinks — say from /%postname%/ to /blog/%postname%/, or adding a date prefix — every post URL on the site changes at once. This is the biggest single source of mass URL change during a relaunch, and it's easy to trigger without realizing.

Removed or consolidated pages

A redesign is often a chance to prune. You merge two thin service pages into one, drop an old landing page, or fold a category into another. Each removed address is now a dead end unless you point it somewhere. These are the URLs people forget, because they're deliberately gone.

Builder-specific slugs and demo imports

Some premium themes ship a demo importer that creates its own pages — "Home 2", "Our Services", a sample shop — with their own slugs. If you build the new site on those instead of your existing pages, you can end up with new URLs for content that already lived at a known, indexed address.

Taxonomy and category changes

Renaming a category from /category/news/ to /category/updates/, changing a category base, or restructuring tags all rewrite the archive URLs those terms generate. Taxonomy archives are frequently indexed and linked, so a quiet rename here can drop pages you didn't even think of as "pages."

02Why 301s matter: rankings, link equity, and 404s

Once a URL changes, you have exactly two options for the old address: redirect it, or let it die as a 404. The gap between those two outcomes is most of your organic traffic, so it's worth being precise about what a redirect actually does for you.

A 301 redirect preserves rankings. The old URL accumulated authority over time — from Google's index, from internal links, from external sites linking in. A 301 tells search engines the page permanently moved here, and the large majority of that ranking value transfers to the new URL. No redirect means starting that page's authority from zero.

It also preserves link equity from the rest of the web. Every backlink pointing at an old URL is a vote you already earned and can't easily earn again. Without a redirect, each of those links now lands on a 404, and that earned authority is simply discarded.

And it protects the human experience. A visitor who clicks an old bookmark, a shared link, or a search result for a moved page hits a dead 404 instead of the content they wanted. They leave. A redirect carries them to the right place silently, so the move is invisible to them.

03301 vs 302: use 301 for permanent moves

This distinction trips people up constantly, and choosing wrong quietly costs rankings. A theme-driven URL change is permanent, so the redirect must be permanent too.

A 301 is a permanent redirect. It tells search engines the old URL is gone for good and the new one is its replacement, so they should update the index and pass the ranking value along. For any relaunch where the old address is never coming back, 301 is the correct status.

A 302 is a temporary redirect. It signals "this is a short-term detour, keep the old URL indexed because it'll return." Search engines treat it cautiously and are slower to transfer ranking value. Use it only for genuinely temporary situations — a maintenance page, a short-lived promotion.

The practical risk: many plugins and server configs default to a 302 if you don't specify. Always confirm the redirect you set is a 301. A wall of accidental 302s on a permanent relaunch is a slow, hard-to-diagnose ranking leak.

04How to map old URLs to new ones

Redirects are only as good as the map behind them. The work isn't writing the rules — it's deciding where each old URL should land. Do this on a spreadsheet before you touch a redirect tool.

Step one is a complete inventory of the old URLs. You cannot redirect what you haven't listed. Crawl the live site before you launch the new one so you capture every address as it currently exists, including the ones buried deep in the structure.

Build the source list

• Crawl the old site with a tool like Screaming Frog or Sitebulb to export every indexable URL.
• Pull your XML sitemap as a cross-check — it's the list of URLs you told Google about.
• Export top pages from Google Search Console and your analytics so you know which URLs actually carry traffic and rankings.
• Note which URLs have backlinks using your SEO tool — those are the ones a missed redirect hurts most.

Step two is mapping each old URL to its best new destination. In a two-column sheet, put the old URL on the left and the new URL on the right. Prioritize by what you learned above — pages with traffic, rankings, or backlinks get mapped first and checked most carefully.

For most URLs the match is obvious: the same page at a new path. For removed pages, choose the closest surviving equivalent — the merged service page, the parent category, the most relevant remaining article. The goal is that a visitor lands somewhere that still answers why they clicked.

05The redirect-to-homepage mistake

Here's the single error that does the most damage: pointing every changed or removed URL at the homepage. It feels efficient — one rule, no 404s, done. It is the worst common choice you can make, and it's worth understanding exactly why.

Google treats a redirect to an irrelevant page as a soft 404. When an old article about, say, theme migration redirects to a generic homepage that doesn't cover that topic, search engines often decide the content is effectively gone and drop the ranking value anyway. You get none of the equity transfer a real redirect provides.

It's also a dead end for the visitor. Someone clicked a specific result expecting specific content, and they land on your front page with no signpost to what they wanted. Most of them leave immediately. You technically avoided a 404 and lost the visit just the same.

Map by intent instead. Send each old URL to the page that serves the same need — the closest equivalent, not the front door. The homepage is the right target for exactly one old URL: the old homepage. Everything else deserves a real destination.

This is the same rule we apply to our own acquired domains: never blanket-redirect to a homepage. Inbound links and rankings are earned at the page level, so they have to be preserved at the page level. A lazy redirect throws away the very thing that made the old URL worth keeping.

06Tools and methods to implement redirects

Once the map exists, implementing it is the easy part. There are two broad approaches — a WordPress plugin or server-level rules — and which one you reach for depends on volume and comfort.

Plugin-based redirects

For most sites, a redirect plugin is the simplest path. Redirection (free) and the redirect managers built into Rank Math or Yoast Premium let you add old-to-new rules in the dashboard, default to 301, and log hits. They're easy, reversible, and need no server access.

The tradeoff is a small amount of overhead, since each request is checked against the rule list in PHP. For a few dozen or even a few hundred redirects this is negligible. For tens of thousands, server-level rules are more efficient.

Server-level redirects

• Apache uses Redirect and RedirectMatch rules in an .htaccess file — fast and reliable, but a syntax error can take the site down, so test carefully.
• Nginx uses return 301 or rewrite directives in the server config, applied at restart.
• A CDN or edge layer (such as Cloudflare) can hold redirect rules in front of the origin, which keeps them fast and independent of WordPress.
• Bulk patterns — like sending an entire old /blog/ prefix to a new path — are far cleaner as a single server rule than as thousands of one-by-one plugin entries.

Whichever you choose, a host with one-click staging makes this safe to rehearse — you can load the redirect map on a staging copy, confirm every rule resolves, and only then apply it to production. Cloudways is the host we point readers to for that kind of staging and server-level control.

07Testing redirects and monitoring 404s after launch

Setting a redirect and assuming it works is how chains, loops, and missed URLs survive to launch day. Test before you go live, then watch closely for the first few weeks — the URLs you forgot always surface in the data.

Test before launch

• Re-crawl the old URL list against the new site and confirm each one returns a single 301 to the right destination.
• Check the status code is 301, not 302 — a crawl report or a quick header check will tell you which you actually got.
• Hunt for redirect chains and loops. A URL that 301s to another URL that 301s again wastes equity; collapse each chain so the old URL points straight at the final destination.
• Spot-check your highest-value pages by hand — the ones with the most traffic or backlinks — by visiting the old URL and watching where you land.

Monitor after launch

• Watch the Pages report in Google Search Console for a spike in 404 / "Not found" errors — that's your list of URLs you missed.
• Check your redirect plugin's 404 log, which records real requests hitting dead URLs so you can add the rule.
• Submit the new XML sitemap in Search Console so Google recrawls and reindexes the new addresses faster.
• Keep watching for several weeks. Reindexing is gradual, and some low-traffic URLs only get recrawled — and only reveal a missed redirect — well after launch.

Treat the redirect map as a living document, not a launch-day task you close out. Each 404 that appears is just one more row to add. Done consistently, the traffic dip from a relaunch stays small and short instead of becoming a permanent loss.

08Frequently asked questions

Do I need redirects if I only change the theme?

No. A pure theme switch keeps your permalink structure, slugs, and pages exactly as they were, so no URL changes and no redirect is needed. Redirects only come into play when a redesign alongside the theme change actually moves addresses.

How long should I keep the redirects in place?

Indefinitely. A 301 should be treated as permanent. As long as any link or old bookmark anywhere points at the old URL, the redirect is still doing its job. Removing it later resurrects the 404s you fixed, so there's rarely a reason to delete one.

Will a 301 redirect lose any ranking value?

A correctly mapped 301 passes the large majority of the old page's value to the new URL, and Google has stated permanent redirects don't cause PageRank loss on their own. The real losses come from wrong choices — homepage dumps, 302s, and redirect chains — not from 301s done right.

What about my old XML sitemap and internal links?

Update internal links to point directly at the new URLs rather than relying on redirects to do it for every click — that's faster and cleaner. Generate a fresh XML sitemap of the new URLs and submit it in Search Console; let the old sitemap fall away as Google recrawls.

Can I just use a catch-all redirect to the homepage?

Avoid it. A catch-all to the homepage is the redirect-to-homepage mistake at scale — Google reads it as soft 404s and visitors hit a dead end. Map URLs individually or in sensible patterns to relevant destinations instead.

This is general, experience-based guidance from running a theme shop and managing our own domains — not financial or professional advice for your specific site. When the cost of a botched relaunch is high, rehearse the redirect map on staging first or bring in a second pair of hands.