Before redesigning a website, benchmark your current SEO performance, audit your existing content and URLs, document your conversion paths, and plan redirects — all before a single new page goes live. Skipping this groundwork is the single most common cause of a redesign that quietly tanks traffic and rankings for months afterward. The checklist below covers each item and why it matters.
Goals
Define clearly what the redesign needs to achieve — better conversion rates, improved brand perception, easier content management, faster load times — since design decisions should trace back to these goals rather than aesthetic preference alone. Without a clear goal, redesign decisions default to subjective taste, and it becomes very difficult afterward to judge whether the project actually succeeded, since success was never concretely defined in the first place.
Analytics
Pull baseline data before you start: traffic by page, conversion rates, top-performing content, and user behaviour patterns. Without this baseline, you won't be able to tell whether the redesign actually improved anything — a common and entirely avoidable regret is redesigning a site, waiting several months, and then having no reliable way to compare before-and-after performance because nothing was properly documented beforehand.
SEO benchmarks
Document current rankings, organic traffic, and backlink profile for your most important pages. This is essential for measuring post-launch impact and for the redirect mapping work that follows. Pages currently ranking well deserve particular attention during planning, since they represent existing value that a poorly executed redesign can easily and unnecessarily erode.
Existing URLs
Inventory every indexed URL on your current site. Every one of these needs a clear plan — either preserved, redirected to an equivalent new page, or deliberately retired — before launch. Skipping this step and simply letting old URLs 404 after launch is one of the most common and most damaging redesign mistakes, since it discards search equity that took time to build and hands a worse experience to anyone still holding a bookmark or old link.
Budgeting time, not just money
Beyond the financial budget, it's worth honestly budgeting the time required from your own team — reviewing content, approving designs, providing feedback within a reasonable turnaround, and testing the finished site before launch. Redesign timelines slip most often not because of the agency or developer's pace, but because internal stakeholders take longer than expected to review and approve each stage, which is worth planning for explicitly rather than assuming everyone will have immediate bandwidth throughout the project.
Content
Audit existing content for what's actually performing (keep and migrate), what's outdated (update), and what's no longer relevant (retire). A redesign is a natural opportunity to clean up content debt, but only if it's done deliberately — content quietly dropped during a redesign without a deliberate decision to retire it is a common, avoidable source of lost traffic.
UX
Review current user behaviour data to understand what's working in the existing design before changing it — a common redesign mistake is fixing things that weren't actually broken while introducing new friction elsewhere. Heatmaps, scroll depth, and session recordings from the existing site are a genuinely useful input here, since they show what visitors actually do rather than what the team assumes they do.
Conversion paths
Map every current path to conversion (contact forms, calls, bookings) and ensure the new design preserves or improves each one — a beautiful redesign that accidentally buries the contact form is a net loss regardless of how much better the site looks visually. It's worth testing every conversion path on the new site personally, end to end, before launch rather than assuming it works because it looks right in the design mockups.
Technical performance
Benchmark current site speed and core web vitals, and set performance targets for the new build — this is often overlooked in favour of visual design but has a direct, measurable impact on both rankings and conversion. A visually striking redesign that loads noticeably slower than the site it replaced can quietly undo much of the intended improvement, since both users and search engines respond negatively to slower load times regardless of how the site looks once it finishes loading.
Tracking
Confirm your analytics, conversion tracking, and any ad platform pixels are correctly configured on the new site before launch, and validate they're capturing data accurately in the days immediately following. It's surprisingly common for tracking codes to be missed or misconfigured during a rebuild, which can leave a business flying blind on performance for weeks before anyone notices the data looks wrong.
Redirects
Build a complete 301 redirect map from every old URL to its new equivalent before launch — this is the single most impactful technical step for protecting existing SEO value through a redesign. A redirect map built carelessly (redirecting everything to the homepage, for instance, rather than to genuinely equivalent new pages) provides only partial protection and can still cost meaningful rankings and traffic. For a deeper look at when a full rebuild (versus a lighter redesign) is actually warranted, see our guide on website redesign vs rebuild.
Launch checklist
- [ ] Baseline analytics and SEO performance documented
- [ ] Complete inventory of existing URLs
- [ ] Content audited and migration plan set
- [ ] Conversion paths mapped and preserved in new design
- [ ] Performance targets set and tested pre-launch
- [ ] Tracking and pixels configured and validated
- [ ] Complete 301 redirect map built and tested
- [ ] XML sitemap updated and resubmitted
- [ ] Post-launch monitoring plan in place for the first 30 days
Choosing between a like-for-like refresh and a bigger rebuild
Not every redesign needs to touch every item on this checklist with equal intensity. A lighter visual refresh that keeps the same platform, URL structure, and content largely intact carries much lower risk and needs a lighter-touch version of this process, while a full platform migration or significant restructuring of the site's information architecture demands the full checklist treatment, particularly around redirects and content migration. Being honest about which category your project actually falls into, before planning begins, helps avoid both under-preparing for a genuinely complex migration and over-engineering the process for what's really a modest visual update.
Staging and testing before go-live
Before the new site goes fully live, test it thoroughly in a staging environment that mirrors production as closely as possible — every major page, every form, every redirect, and every tracking pixel, ideally reviewed by more than one person since a single reviewer tends to miss the same issues a fresh set of eyes would catch. It's also worth testing on a genuine range of devices and browsers rather than only the one the design team happens to use daily, since a rendering issue that's invisible on a designer's laptop can be immediately obvious to a visitor on an older phone or a less common browser.
The first 30 days after launch
The work isn't finished at launch — the weeks immediately after are when problems, if they exist, tend to surface. Monitor rankings, traffic, and conversion rates daily for the first couple of weeks rather than waiting for a monthly report, since catching a redirect error or a tracking gap within days is far easier to fix cleanly than discovering it a month later after damage has compounded. A brief dip in the days immediately following launch, as search engines re-crawl and re-index changed pages, is normal; a sustained decline beyond a few weeks is the signal that something in the migration needs attention.
This checklist underpins every project we run through our AI website redesign service, and pairs well with a fresh AI SEO audit once the new site is live to catch anything that shifted during the rebuild.
Communicating the change to existing customers and users
If your site has a meaningful base of returning visitors or logged-in users, it's worth planning how the change will be communicated rather than letting them discover it unannounced. A brief heads-up (an email, a banner on the old site in the days before launch) reduces confusion and support enquiries from people who return expecting the familiar layout and instead find something entirely different with no explanation of what changed or why.
Who should own the redesign process
Even when an outside agency is doing the design and build work, it helps to have someone internal accountable for the checklist above — pulling the analytics baseline, coordinating the content audit, and signing off that redirects and tracking are genuinely working before launch. Redesign projects without a clear internal owner tend to have gaps precisely in the unglamorous groundwork items (redirect mapping, tracking validation) that don't show up in a visual mockup review but matter enormously for protecting the site's existing performance through the transition.
FAQs
What should I check before redesigning a website? Baseline analytics and SEO performance, a full inventory of existing URLs, content quality, conversion paths, technical performance, and a complete redirect plan.
Can a redesign hurt SEO? Yes, if URLs change without proper redirects, content is lost without a migration plan, or technical performance regresses — all preventable with careful planning before launch.
How often should a business redesign its website? Most businesses benefit from a full redesign every three to five years, with smaller ongoing improvements in between rather than waiting for everything to feel outdated at once.
Planning a redesign and want to avoid the common pitfalls? Talk to our team about a redesign planning session.
