Website Redesign SEO: How to Redesign Without Losing Your Rankings
By Kristian Kreaktive Published
Website redesign SEO, learned moving my own site to a new domain: the redirect map, launch-day traps and what to watch after launch.
In short
A redesign doesn’t hurt your SEO. Changing page addresses, page content and links without a plan does. Before launch, list every page that gets found on Google, send each old address to its closest new page with a permanent (301) redirect in a single hop, and keep the words that rank in the new titles. After launch, check Search Console every week for the first few months and keep the redirects for good. I used these redirect rules when I moved my own site to a new domain in October 2026.

On this page
A website redesign doesn’t hurt your SEO. The damage comes from what tends to happen during one: page addresses change, pages that rank get rewritten around different words, old pages vanish, and nobody tells Google where anything went. Website redesign SEO is the plan that stops that from happening.
I’m Kristian, founder of KREAKTIVE (formerly Digital Marketing Services). On October 6, 2026 I did the riskiest version of this on my own business: I moved the whole site from digitalmarketingservices.pro to kreaktive.design. New domain, new name, every single page address changed at once. This guide covers that process, including the traps I found along the way.
Written by Kristian Kreaktive, founder of KREAKTIVE (formerly Digital Marketing Services) in Colorado Springs. 17 years in digital marketing, 15 of them running my own agency. The domain move in this guide is my own business website, moved from digitalmarketingservices.pro to kreaktive.design on October 6, 2026. I describe the steps, not the traffic figures.
Redesign, refresh or migration: know which one you’re doing
People use “redesign” for three very different projects. The SEO risk is very different too, so name yours before anything else.
| Project | What changes | SEO risk |
|---|---|---|
| Refresh | Colors, photos, fonts, some copy. Same pages, same addresses. | Low. Check you didn’t delete text that ranks. |
| Redesign | Page structure, navigation, platform, some addresses. | Medium to high. Every changed address needs a redirect. |
| Domain migration | The domain itself. Every address changes. | High. Redirects, Change of Address, profiles, email and forms. |
If your problems are a dated look and old photos, a refresh is often enough, and it barely touches SEO. If the site is slow, hard to update or built on a platform you’ve outgrown, you’re in redesign territory. I wrote about the platform side in how to choose a web designer.
One smaller kind of migration sits between the rows: moving to https, or between www and non-www on the same domain. Every address still changes, so you still need permanent redirects. But Google says not to use its Change of Address tool for it.
When a redesign has almost nothing to lose
Most redesign SEO guides skip this point. The risk depends on what you have today. A site that gets found on Google has something to protect. A site that doesn’t has very little.
Bristlin Construction, a Wisconsin metal roofing and sheet metal contractor, came to me with a site that took more than 5 seconds to load and had zero keywords ranking on Google. Customers found them through the owner’s network and word of mouth. There were no rankings to protect, so I could rethink the structure from scratch instead of tiptoeing around old pages. I did the strategy and design, eSEO Space did the WordPress build and technical SEO, and two months after launch the site had 70+ ranking keywords. The full story is in the Bristlin Construction case study.
My own move was the opposite. KREAKTIVE’s old domain had pages in Google, links from other sites and directory listings. That’s the situation where a careless redesign costs real money, and where every step below matters.
Before you plan anything, find out which group you’re in. The inventory in the first step tells you.
1. Take an inventory of what Google already likes
Before anyone opens a design tool, write down every page that brings you visitors from Google. This list is what you’re protecting.
Open Google Search Console, go to the Performance report and set the date range to cover the last year. Switch to the Pages tab and export it. Every page with clicks or impressions goes on your list. Then add three more sources:
- Every page address on the site, from your sitemap or a crawler like Screaming Frog (the free version covers 500 addresses).
- Pages other websites link to, from the Links report in Search Console.
- Old addresses that already redirect, from your current redirect rules or plugin. People forget these, and they matter more than you’d think (more on that in the third step).
For each page that gets found on Google, note the words it gets found for. Search Console shows those queries when you click into a page. If a page ranks for “metal roof repair,” the new version needs those words in its title and main heading. Rewrite a ranking page around a different phrase and you can lose the traffic it was bringing in.
Before my move, I also saved a copy of everything I was about to change: the server’s redirect file and the settings of both domains in Cloudflare. With that copy saved, I could put the old redirect file and Cloudflare settings back if launch day went badly. On a client redesign, the equivalent is a full backup of the old site that you keep until the new one has settled.
2. Build the redirect map
The redirect map is a spreadsheet with two columns: the old address and the new address it goes to. Every page from your inventory needs a row. This map is the single most important SEO document in a redesign. Skip it and you lose rankings, links and visitors in one go.
Three rules for the map:
Page to page, never everything to the homepage. Someone who clicked an old link to your gutter page wants gutters. Send each old page to the closest match on the new site. On my domain move this was easy, because I kept the same paths: /blog/anything/ on the old domain goes to /blog/anything/ on the new one, query strings included.
Use permanent (301) redirects. Google’s redirect guide explains the difference: with a permanent redirect, Google shows the new page in search results, while with a temporary (302) redirect it keeps showing the old one. Check which kind your platform or redirect plugin creates before you trust it.
One hop. Each redirect should land on the final page directly. Google’s site move guide asks you to redirect to the final destination directly. Chains build up quietly, and I found them on my own site.
When the addresses change too
Keeping the same paths is the easy case. Most redesigns change them, and that’s where the map takes real work.
Match by what the page is about, not by how the address looks. Take each old page from your inventory, look at the search words you noted for it, and find the new page that answers the same need. If two old pages become one new page, both rows point to that page. If you can’t find a match for a page that gets found on Google, the new site is probably missing a page you should keep.
When a whole group of addresses changes the same way, you don’t need one row per page. Say every blog address moves from a news folder to a blog folder, so /news/metal-roofs/ becomes /blog/metal-roofs/. Google’s site move guide says you can handle common patterns like that with rewriting rules on your server. Write the rule, then still test the pages from your inventory one by one.
This site went through that before the domain move. It used to run on WordPress, and when I rebuilt it on Astro, the old WordPress post and page addresses got redirects to their new pages. Those WordPress redirects were still in place at the time of the domain move, and they had to be rewritten in the move.
3. Hunt down the redirects you forgot you had
My move got messy here. A site that’s been around for a while carries redirects from earlier changes. Mine had older redirects from when it ran on WordPress, sending old WordPress post and page addresses to their Astro pages on the old domain.
Once the old domain itself started redirecting to the new one, every one of those old WordPress links would have taken two hops: first to the old domain’s newer page, then over to kreaktive.design. So I rewrote those redirects to point directly at the final page on kreaktive.design, and placed them before the general “send everything to the new domain” rule. Old links now reach their final page in one hop.
I found two more traps the same way:
- A rule pointing the other way. Before the move, kreaktive.design had been set to forward visitors to the old domain. Leave that in place and add the new redirect, and the two domains send visitors back and forth forever. I removed that rule as part of the move.
- An extra hop on plain http. My host forces https on every visit, which added a step for old http links. I changed the setup so those land on the new domain in one step too.
None of this shows up if you only test the homepage. Test old addresses from your inventory, including the oldest links you can find. Google’s site move guide suggests command line tools or scripts to test large numbers of addresses. Two ways to do it on a small business site:
- A list in a crawler. Screaming Frog lets you upload a list of URLs to audit in a site migration, and it reports temporary and permanent redirects, redirect chains and loops. Paste in every old address from your inventory.
- A single address in a terminal. Run
curl -sILfollowed by an old address. It shows the headers from every page it passes through, so you can read each status code and count the steps. One 301 followed by the live page (a 200) is what you want. A 301 that leads to another 301 is a chain, and a 302 or a 404 needs fixing.
4. Fix the internal links (and use the chance to find broken ones)
Redirects are for visitors arriving from outside. Your own site should link straight to its new addresses. Google’s site move guide asks for the same thing: update internal links from the old addresses to the new ones, give every new page a canonical tag that points to itself, and submit a sitemap with only the new addresses.
When I audited my links during the move, I found problems that had nothing to do with the new domain. Some city pages had “View all articles” links pointing at tag pages that return a “410 Gone” error. Some business-type pages linked to location addresses that returned “Not found (404)“.
So I added an automated test to the site’s build. It fails the build on dead internal links, on links to addresses that redirect, and on redirecting addresses in the sitemap. You don’t need a custom test for a small site, but you do need a crawl of the new site before launch, looking for any link that returns an error or a redirect.
5. Launch day, including the parts that aren’t SEO
By the day the new site goes live, the SEO work is mostly done. The usual launch-day breakage is something nobody thinks of as SEO, and it can cost you more than a ranking drop: a contact form that quietly stops working.
Launch day needs six things:
- Put the redirects live with the new site, at the same moment. Every hour the new site runs without them is an hour of dead links.
- The old domain’s security certificate keeps renewing. Old links use https, so the old domain has to keep serving secure connections for the redirect to work. I kept the certificate’s renewal requests out of the redirect, so they still reach the old domain’s server.
- The cache gets cleared on both domains. Cloudflare sits in front of my site and saves copies of pages. After every update, the Cloudflare copies for both domains (kreaktive.design and digitalmarketingservices.pro) get cleared, or visitors would keep seeing old pages.
- The contact form. My form’s spam check only accepts submissions from domains on its allowed list. If the new domain isn’t on that list, every submission fails while the page looks fine. Check this one by sending a real test message.
- Email didn’t move on day one. The site kept sending from the old address until the new mailbox was set up, a few days later. Moving the website and email on the same day doubles what can go wrong.
- The old name stays visible to machines. My business information for Google (structured data) lists the old name as an alternate name, and the About page explains the name change. That gives Google and AI tools what they need to connect the old business to the new one.
For a domain change, add one more: Google’s Change of Address tool in Search Console. You need to be an owner of both the old and new domain in Search Console, and Google says to use the tool after you’ve moved and redirected the site. I submitted it for my move. Google’s Change of Address help page says it keeps forwarding signals for 180 days. A redesign that keeps the same domain doesn’t need it.
After launch I updated my Clutch profile and directory listings to the new domain, so the links people actually click don’t depend on a redirect.
The pre-launch checklist
This is the list I’d want any designer to go through before a redesign goes live. If yours can’t answer one of these, wait.
- Every page with Google clicks or impressions in the last year is in the redirect map.
- Every redirect is permanent (301) and lands on its final page in one hop.
- Old redirects from earlier changes point to the new final pages.
- No rule sends traffic in the opposite direction.
- Pages that rank keep their main words in the title and main heading.
- No ranking page was deleted without a redirect to its closest match.
- Internal links use the new addresses, and a crawl finds no errors or redirects.
- Every page’s canonical tag points to itself on the new site.
- The sitemap lists only new, working addresses.
- The new site isn’t blocking Google. Staging sites often carry a “noindex” tag or a robots.txt block, and it sometimes ships with the launch.
- Analytics and Search Console are set up for the new site.
- Contact forms send a real test message.
- Phone numbers, click-to-call buttons and booking links work on mobile.
- Domain change only: Change of Address submitted, and the old domain renews automatically.
If the redesign also changes your platform, add a speed check. A rebuild is the cheapest moment to fix a slow site, and the Astro vs WordPress performance post covers that side of the platform choice.
The first months after launch
Expect some movement. Google’s site move guide says a medium-sized site can take a few weeks or more before the new addresses show up, and that rankings can fluctuate while Google recrawls. A dip in the first weeks is normal, but one that keeps growing needs a look.
My own move went like this. Indexing moved quickly: within four weeks of the switch, Google had indexed almost every blog post under the new domain. Rankings were slower. Weeks after the switch, Search Console still showed some searches landing on the old domain, and my pages on the new domain sat lower on average while Google moved things over. Don’t change the domain redirects to chase a split like that. It’s part of the move, and changing things mid-move only gives Google more to reprocess.
What to check every week after launch
Search Console’s Page indexing report for new “Not found (404)” errors, the Performance report for pages that lost clicks compared to the same weeks before launch, and the contact form and phone calls. Leads matter more than rankings, so if calls hold steady, a small ranking dip can wait.
When to worry instead of wait:
- An important page shows “Not found (404)” in Search Console. Its redirect is missing or broken.
- A page that used to rank has dropped out of the index completely, not just down a few spots.
- An old address returns a page instead of a redirect, or a temporary (302) redirect.
- Leads drop at the same time as traffic. Check the form first.
Keep the redirects. Google says to keep them as long as possible, generally at least a year, and I treat mine as permanent: the redirect rule on my server carries a note that says “Never remove: old backlinks and bookmarks depend on it forever.” Old links on other sites and old bookmarks keep sending people for years.
Plan the redesign around what’s already working
The biggest redesign SEO mistake is starting from the design instead of from the inventory. Start with what Google already sends you, protect it with a redirect map, and the new design gets to build on years of work instead of starting from zero.
If a redesign is on your list for next year, my website cost breakdown covers what to budget, and the technical SEO guide for business owners explains the moving parts in plain English. And if you’d like me to rebuild your site with the redirect map done properly, here’s how I handle website redesigns, or get in touch. If you’re in Colorado Springs, my page on web design in Colorado Springs has the local details.
Frequently Asked Questions
Not by itself. Rankings drop when page addresses change without redirects, when pages that rank get rewritten around different words, or when pages disappear. Keep the addresses where you can, redirect the ones that change, and a redesign can keep or improve what you have.
Usually a few weeks, sometimes longer. Google’s site-move guide says a medium-sized site can take a few weeks or more before the new addresses show up, and rankings can move around while it recrawls. If pages are still missing after a month, look for broken redirects or removed content.
A 301. Google shows the new page in search results for a permanent (301) redirect. For a temporary (302) redirect, it keeps showing the old page.
Forever, if you can. Google says to keep them as long as possible, generally at least a year. Old links on other websites and in people’s bookmarks keep sending visitors for years, and each one lands on a dead page the day the redirects come down.
No. Someone who clicked an old link to your roofing page wants roofing, not your homepage. Send each old page to the closest new page. Only point a page at the homepage when nothing on the new site matches it.
Only when the domain changes. Google’s tool is for moves from one domain or subdomain to another. A redesign that keeps your domain doesn’t need it, even if page addresses change, and Google says not to use it for a switch from http to https.
Test the old addresses, not just the homepage. Upload your list of old addresses to a crawler like Screaming Frog, which reports redirect chains and loops, or run curl -sIL on a single address in a terminal to see every step and its status code. One 301 followed by the live page is what you want.






