A website redesign is a different project from a first-time website build, and it carries risks a new build doesn't have. You have existing search rankings that can be lost if redirects aren't handled correctly. You have existing content that needs to be migrated, audited, or retired. You have an existing audience with expectations about how your site works. And you have a live business that can't afford downtime or broken functionality during the transition.
If you've decided a redesign is the right move whether your current site feels dated, no longer represents your business, performs poorly, or simply hasn't been touched in years, this checklist covers everything that needs to be planned before development starts. Treat it as a working document. Going through it properly is the difference between a redesign that improves your results and one that quietly loses ground you'd already won.
Before Anything Else: Audit What You Have
A redesign should start with an honest assessment of your current site, not assumptions about what's wrong with it, but actual data.
Pull your analytics
Before redesigning anything, look at what's actually happening on your current site. Which pages get the most traffic? Where do visitors drop off? What are your highest-converting pages, and what do they have in common? A redesign that doesn't account for what's currently working risks losing it.
Identify your highest-ranking pages
Run a search for your domain and note which pages currently rank well in Google. These pages have accumulated authority over time, backlinks, age, relevance signals. A redesign needs to preserve that authority, not start from zero by replacing well-ranking URLs without a redirect plan.
Audit your existing content
Go through your current site page by page. For each page, decide: keep as is, keep but update, merge with another page, or retire entirely. This audit prevents two common redesign mistakes carrying forward outdated or low-value content out of habit, and accidentally dropping content that was quietly performing well.
Run a technical and performance check
Check your current site against Core Web Vitals, as covered in our post on how website speed affects sales and SEO. Note specific issues: slow load times, broken links, mobile usability problems. These give you a concrete baseline to measure improvement against after the redesign.
Document your current functionality
List every feature your current site has forms, integrations, login systems, calculators, booking tools, anything custom. It's easy to overlook functionality that's been quietly working in the background for years until it's missing from the new site and someone notices it's gone.
Define Why You're Redesigning
A redesign without a clear goal tends to become a redesign driven by aesthetic preference alone "it looks dated" which is a legitimate starting point but not sufficient on its own to guide the many decisions a redesign involves.
Be specific about what's driving this project. Common, legitimate reasons include: the current site no longer reflects the brand or positioning of the business, the site performs poorly on mobile or fails Core Web Vitals, the current platform is difficult or impossible to update, conversion rates have declined or never met expectations, the business has grown or changed and the site doesn't reflect new offerings, or the site was built cheaply early on and needs to be rebuilt to a professional standard.
Each of these reasons points toward different priorities for the redesign. A performance-driven redesign prioritizes technical rebuild work that might not be visually dramatic. A positioning-driven redesign prioritizes messaging and design. A platform-driven redesign prioritizes the underlying CMS and architecture decision, covered in our post on WordPress vs custom development. Knowing which of these is primary keeps the project focused on what actually needs to change.
Set Goals and Success Metrics
Just as with a first-time build, a redesign needs measurable goals but for a redesign, you have something a new build doesn't: a baseline to improve against.
Use your analytics audit to set specific, comparative goals. Examples: improve homepage-to-contact-form conversion rate from its current baseline by a defined percentage, reduce average page load time from its current measurement to under 2.5 seconds, increase organic traffic to key category pages by a defined amount within six months of launch, or reduce bounce rate on the highest-traffic landing pages.
These goals do two things. They give the redesign project a clear definition of success beyond "looks better," and they give you a way to evaluate whether the redesign actually worked once it's live, which is the only way to know if the investment paid off.
Plan Your URL Structure and Redirects
This is the single most consequential technical decision in a redesign, and the one most commonly underestimated.
Decide whether URLs are changing
If your redesign keeps the same URL structure and page paths, just a new design and content your SEO risk from the redesign itself is minimal. If URLs are changing a new site structure, a new CMS with different default URL patterns, or pages being merged or split every changed URL needs a redirect plan.
Map old URLs to new URLs
For every page on your current site, document where it will live on the new site or explicitly note that it's being retired and where its traffic should be redirected instead (typically to the most relevant equivalent page, or a parent category page if no direct equivalent exists).
Plan 301 redirects for every changed URL
A 301 redirect tells search engines and visitors that a page has permanently moved, passing along the ranking value the old URL had accumulated. Without these redirects, a redesign that changes URLs can cause a significant, sometimes severe drop in organic search traffic, because search engines effectively see the old, ranking pages as gone and the new pages as having no history.
Test redirects before and after launch
Before launch, verify the redirect map is complete. After launch, monitor for 404 errors using Google Search Console any old URL that wasn't accounted for in the redirect map will show up here, and can be fixed retroactively, but catching it before launch is far better than after.
This single area URL planning and redirects is responsible for more redesign-related SEO disasters than any other factor. If your development partner doesn't raise this proactively, raise it yourself.
Plan Your Content
Decide what content is being reused, rewritten, or newly created
Your content audit from earlier gives you the starting point. For content being reused, confirm it's been reviewed for accuracy and current relevance. For content being rewritten, plan who's doing that work and by when. For new content new pages, new sections treat this the same way you would in a first-time build: identify responsibilities and deadlines clearly, since content readiness is the most common cause of redesign timeline slippage, as covered in our web development timeline guide.
Plan for SEO continuity in rewritten content
If a page currently ranks well for specific search terms, a rewrite needs to preserve and ideally improve its relevance to those terms. Rewriting a high-performing page without checking what made it perform is a common way redesigns accidentally lose organic traffic on pages that previously worked.
Update outdated information across the board
A redesign is a natural point to update anything that's drifted out of date, old pricing, discontinued products or services, outdated team information, old testimonials, outdated copyright years and legal pages.
Plan Your Design Direction
Gather your current brand assets
Logo files, brand colors, fonts, and any existing brand guidelines. If your brand has evolved since the current site was built and for older sites, it likely has this as the point to formalize that evolution into the new design.
Identify what's working visually and what isn't
Be specific about which parts of your current site's design and structure are working for your business and which aren't. "Everything needs to change" is rarely true and rarely helpful. Most redesigns improve significantly by addressing the genuinely weak elements while retaining what was actually fine.
Gather design references
As with a first-time build, identify sites whose design you admire and articulate specifically why layout, imagery, typography, navigation patterns.
Plan for consistency across the full site, not just key pages
A common redesign failure is a beautifully designed homepage and a handful of key pages, with dozens of interior pages still following old templates or inconsistent ad-hoc designs. Plan for the redesign to cover your full site structure, not just its most visible pages.
Plan Your Functionality and Integrations
Re-evaluate every piece of existing functionality.
Using the functionality audit from earlier, decide for each item: keep as is, improve, replace, or retire. A redesign is a natural opportunity to fix functionality that's never worked well, but it's also where functionality silently disappears if it isn't explicitly carried into the project plan.
Review your integrations
CRM connections, email marketing integrations, analytics setup, payment gateways, booking systems each of these needs to be re-established in the new site, and this is a good opportunity to check whether each integration is still necessary or could be improved.
Consider what's changed since the current site was built
If your current site predates significant changes to your business, new products, new services, new operational processes, the redesign is the opportunity to build functionality that reflects how your business actually operates now, not how it operated when the site was last built.
Plan the Technical Foundation
Decide on platform
If your current platform is the source of ongoing problems, difficult to update, poor performance, limited functionality, a redesign is the appropriate point to change platforms. If your current platform works well and the issues are primarily design and content, staying on the same platform with a rebuild may be the more efficient path. Our post on WordPress vs custom development covers this decision in detail.
Plan for performance from the start
A redesign is an opportunity to address performance issues baked into the current site's foundation hosting, caching, image handling rather than carrying them forward into a new design.
Plan your hosting and infrastructure
If your current hosting is outdated, underpowered, or poorly configured, a redesign is a natural point to migrate to better infrastructure as part of the same project.
Plan the Launch and Transition
Plan for a staging environment
The new site should be built and tested in a staging environment, a private, non-public copy before going live, so the live site continues operating normally throughout development.
Plan your launch window
Choose a launch time that minimizes business disruption avoiding your busiest sales periods if possible, and allowing time immediately after launch for monitoring and quick fixes.
Plan post-launch monitoring
In the days following launch, monitor analytics for unexpected drops in traffic, check Google Search Console for crawl errors and 404s, and verify that key conversion paths forms, checkout, and key calls to action are working correctly under live conditions.
Communicate the change if relevant
If your redesign significantly changes how customers interact with your site, a new login system, a changed checkout process, a restructured navigation, consider whether existing customers need any communication about the change.
The Complete Checklist
Audit current analytics, rankings, content, technical performance, and functionality. Define the specific reasons for the redesign and the priorities that follow from them. Set measurable goals against your current baseline. Map every existing URL to its new location and plan 301 redirects for anything that changes. Decide what content is reused, rewritten, or newly created and check rewritten content for SEO continuity. Update outdated information throughout the site. Gather brand assets and design references, and identify what to keep versus change. Plan for design consistency across the entire site structure, not just key pages. Audit and plan every piece of existing functionality and integration. Decide on platform and plan the technical foundation with performance built in from the start. Build and test in a staging environment. Plan your launch window and post-launch monitoring.
How WRTeam Approaches Redesign Projects
A redesign engagement with WRTeam starts with the audit work covered above analytics, rankings, content, and technical performance because this audit shapes everything that follows. The process from there follows the same brief-to-launch structure covered in our post on how WRTeam builds websites, with the redirect planning, content migration, and staged testing specific to redesigns built into the process rather than treated as afterthoughts.
If you're ready to move on a redesign, the starting point is a conversation that begins with your current site, what's working, what isn't, and what the data says before any decisions are made about what the new site should look like.
The Summary: A Redesign Is a Migration, Not Just a New Design
The visual outcome of a redesign is what's most visible, but the work that protects your business through the transition redirects, content continuity, functionality preservation, performance is what determines whether the redesign is a clean improvement or a project that quietly costs you ground you'd already gained.
Work through this checklist before development starts. It takes real time, but every item on it is here because skipping it has caused a real redesign to go wrong for a real business at some point. Getting it right the first time is considerably easier than recovering from it afterward.
