Many companies consider a website redesign to be a creative undertaking and simply hand it off from a technical standpoint once it is ready to go live. This is the wrong approach. The second you start shifting around pages, altering copy, or updating your URL structure, you are beginning to make choices that will impact your search rankings, and if those choices are not being influenced by data, you can erase years of organic progress in a single weekend launch. Websites that go through a complete redesign and relaunch without a solid redirect strategy and a migration plan can count on losing 20 to 40% of their organic traffic immediately (HubSpot).
The solution is not to wait the design process and slowly design the site over a year, but rather, to do the SEO work at the same time as the design work.
Start With a Full SEO Audit Before Touching Anything
Before you even start sketching out a new site map, you need to prep your baseline data. Pull up Google Search Console and export your top pages based on impressions and clicks. Then, use Google Analytics 4 (or your preferred conversion tracking platform) to sort your top pages driving conversions, not just traffic. These are your most valuable pages, the pages that rank in organic search, the pages that attract and earn backlinks, and the pages that convert customers.
Why is this important? Redesigns typically incorporate page reduction or outright name/URL/section changes, and you don’t want to accidentally delete something that makes you a good chunk of your organic revenue because you didn’t even know it existed in the background.
Write down everything. Current URL structure, meta titles and descriptions, current word count on important pages, and your backlink profile. The backlink profile is perhaps the most critical here because external sources linking to your old URLs are passing you link juice, or authority. If your URLs change and those links are not redirected correctly, you’re losing that authority.
Plan Your Information Architecture Before Your Visual Design
The biggest source of SEO problems in a rebuild is information architecture, how pages are grouped, labeled, and linked. Reducing those links is a good way to create a cleaner, more focused, responsive design, which is why so many talented designers inadvertently tank your search traffic. Fewer menu items mean fewer clicks, less waste, and no room for your blog no one reads. It’s beautiful logic but for the way Google and a lot of your users find and move through your site.
The only high-level rule of IA is that no high-value page should be more than 3 clicks from the homepage. If a category page gets buried four or five levels deep in the site beneath the homepage, about, services, and the new research section, its crawl priority drops and its ranking tends to follow.
Use a spreadsheet. List every page you’ve got, include where it roughly falls in the current structure and how Google rates it, then where it will fit in this new world order, and what happens to old pages if you’re combining a few, splitting one of them into further detail, or killing some off.
This is where any hope of a successful rebuild lives or dies and where input from someone who understands web design perth and how aesthetics and technical SEO strategy intersect is vital. Go forth and collaborate. Make wireframes together.
Build and Test on a Staging Environment Properly
Each and every redesign, without exception, must happen on a staging server that’s invisible to search engines. If Google indexes your staging site, you’ll have duplicate content. If your new URLs haven’t been set up right and Google’s already found them, they’re in the index. And if you’ve left more of your old URLs lying around than just those that were intended to carry forward, you’ve got junk in the index. If you’re rebranding or reskinning for a new year but not updating much content, the premature indexation issue will be even worse. You’ll have old content indexed as new content.
For public staging environments take your pick from password walls or no crawlers allowed in robots. If it’s password protected, good. If not, you’ll also need disallow: / in your robots.txt file to keep that old index off the pre-launch site. Don’t kid yourself that a few meta noindex tags in your source will keep it invisible, doesn’t work that way, they’ve got to stay on the outside of those shiny locked gates.
This is also the best time to test Core Web Vitals. Lighthouse and PageSpeed Insights can grade projects on how close they come to hitting Google’s metrics on load time, interactivity, and cumulative layout shift. A redesign that introduces heavy unoptimized images, render-blocking JavaScript, or layout instability can hurt your scores even if the page itself looks polished. Run performance tests during development, not as an afterthought before launch.
Mobile-first responsiveness is non-negotiable here. Google indexes the mobile version of a site first. If the new design works beautifully on desktop but the mobile version has text that’s too small, buttons that are too close together, or images that don’t scale properly, that’s what Google will evaluate.
Build Your 301 Redirect Map Before Launch Day
A redirect map is a spreadsheet that maps every old URL with the new URL it should redirect to. This is the most important technical document in any redesign project, but it’s often created too late or isn’t detailed enough.
Every URL that is changing, because the page is being renamed, reorganized, or consolidated into another page, requires a 301 redirect. That includes old blog posts, old product or service pages, old category pages, and any URLs that have backlinks. A 301 informs search engines that the page has permanently moved and tells them to pass the ranking authority to the new location.
You don’t want redirect chains. If page A redirects to page B, which redirects to page C, you’re losing signal at each hop. Every redirect in the chain should point directly to the final destination URL wherever possible.
And you don’t want redirect loops, which means page A redirects to page B, which redirects back to page A. These will cause crawl errors and may render pages inaccessible.
Protect Your On-Page SEO During the Content Migration
It’s often very tempting when you’re investing in a redesign to just, redesign everything. New layout, new content, new messaging. But you shouldn’t. The page is ranking in search engines and that will almost certainly be largely down to its content and also its structure, the H1 tag, the body copy, the internal links, the meta title and description.
Stick to minimum viable changes at launch. Get the new design live with existing content still on as many stable, high performing URLs as possible. Then, once everything’s settled down and you’ve been able to see rankings stabilize, you can begin making content improvements. This doesn’t mean the content can’t evolve. It means you don’t want to find out whether a rewritten page is as ‘good’ as it was. Probably it’s not going to be, and you don’t want to be making all these other changes at the same time and end up in a chaotic situation where you’re not sure how different things have affected things.
The Launch Checklist: What to do in the First 48 Hours
Once your new site is live you want to be sure Google is able to find everything it needs. That means taking a few steps to open the floodgates to fresh crawls.
Spend a few minutes in the first few days checking these basics to make sure Google can start assessing all your hard work. First, make sure no pages are unintentionally blocked with a ‘noindex’ meta tag that carried over from staging. Then update the robots.txt rule which blocks crawlers on staging.
Finally, if you haven’t already, update XML sitemaps for the new structure and submit them to Google Search Console to accelerate the crawl. Most clients will see traffic changes one week post-launch once Google is able to index the new site properly.
Monitor For at Least Six Weeks After Launch
Rankings don’t stabilize instantly after a redesign. Google takes time to re-crawl and re-evaluate a restructured site, and there’s typically a period of fluctuation that can look alarming if you’re not expecting it.
Watch Google Search Console’s Index Page Status report daily for the first two weeks. You’re tracking whether your key pages are being indexed, whether new 404 errors are appearing, and whether your crawl coverage is growing or shrinking. If pages that should be indexed aren’t appearing, check whether they’re being blocked or whether the internal linking to those pages is weak.
GA4 will show you traffic trends, but give it at least four to six weeks before drawing firm conclusions. A two-week drop that then recovers is normal. A persistent decline after six weeks, particularly on pages that didn’t change structurally, needs investigation, check the redirect chain, the canonical tags, and the on-page content to identify what’s different.
Treat the Redesign as a Migration Project, Not a Relaunch Event
A redesign goes wrong when it’s conceptualized as a fun, creative project, and SEO is slapped on at the end to make sure everything’s okay. By the time the SEO ‘re-review’ happens, everything site structure-wise is locked in, and nobody’s prepared to deal with the technical fallout of the pretty (but heavy) new site. No budget, no timeline left.
The sites that navigate a redesign without an iceberg of lost traffic are the ones that start with an SEO audit. They’re the ones where SEO considerations drive design trade-offs all the way along. And they’re the ones who take the new site live, not as they release the breath held for the swan dive, but as they would if they were setting out on a test flight. The real work begins. It’s the continual monitoring and tweak work that catches problems early, before they mask up and become a real nightmare to shift.
