A website redesign checklist matters because most redesign damage is entirely avoidable: lost search rankings, broken links, and missing pages almost always come from skipping a preparation step, not from the new design itself. This checklist covers 25 steps across five stages, from planning through the weeks after launch, so nothing important gets missed.
The single biggest cause of a redesign losing traffic is changing page URLs without redirecting the old ones. Keep that one fact in mind through every stage below, and most of the serious risk disappears.
This website redesign checklist applies whether you are moving from an old WordPress theme to a new one, switching platforms entirely, or rebuilding a site from scratch on new infrastructure. The specific tools change; the underlying risks and the order you address them in do not.
Document the old site before touching anything
Export a full list of your current URLs, their rankings, and your analytics baseline before starting. You cannot measure what a redesign changed if you do not know what you started with.
Before you start: 5 steps
- Write down specific goals for the redesign: what should visitors do differently afterward, and what problem is the current site actually causing?
- Export your current analytics baseline: traffic, top pages, conversion rate, and bounce rate, so you have a clear before-and-after comparison.
- Export a full list of every indexed URL on the current site, along with its current search rankings for its main keywords.
- Audit existing content to decide what to keep, rewrite, merge, or retire, rather than assuming every page carries over automatically.
- Set a realistic budget and timeline, referencing our website cost guide if you are still scoping the project.
Preserve your SEO: 6 steps
- Plan a 301 redirect for every URL that will change, mapping old paths to their new equivalents before launch, not after.
- Keep the highest-performing page titles and meta descriptions where they were already working well, rather than rewriting everything by default.
- Preserve your existing internal linking structure where it made sense, especially links pointing at your best-ranking pages.
- Keep your XML sitemap and robots.txt configuration in mind from the design stage, not as an afterthought at launch.
- Note any backlinks pointing at pages that will change URL, so you know exactly which redirects matter most for retained authority.
- Keep your existing analytics and Search Console properties connected through the transition rather than starting fresh ones.
Design and content: 4 steps
- Build and review the new design on a staging copy, never directly on the live domain.
- Check the new design against Core Web Vitals early, since retrofitting performance after launch is far harder than designing for it from the start.
- Confirm every form, calculator, or interactive element on the old site has an equivalent on the new one, or a documented decision to drop it.
- Test the new design on real mobile devices, not just a browser’s resize tool, before considering it finished.
Technical pre-launch checks: 6 steps
- Test every form on the staging site, including confirmation emails, to make sure submissions actually arrive.
- Click through every internal link to confirm nothing points at a broken or placeholder page.
- Confirm SSL is correctly configured on the new domain or subdomain before launch, not scrambled into place afterward.
- Check that noindex tags used on the staging site are removed before it becomes the live site.
- Run the new site through PageSpeed Insights and fix obvious performance issues before, not after, launch.
- Take a full backup of the current live site immediately before switching anything over.
Launch day: 4 steps
- Switch DNS or push the new site live during low-traffic hours to minimise disruption if something needs a quick fix.
- Submit the new XML sitemap to Search Console immediately after launch.
- Monitor uptime and error rates closely for the first few hours, not just the first few minutes.
- Spot-check your redirect map on a sample of old URLs to confirm they land on the correct new pages, not just anywhere on the site.
The weeks after launch matter as much as launch day
Check Search Console’s Coverage report daily for the first two weeks for a spike in 404 errors, which usually means a redirect was missed. Compare traffic and rankings against your pre-launch baseline weekly rather than daily, since search engines take time to fully re-crawl and re-rank a changed site, and short-term dips are common even on a well-executed redesign.
Keep the old site’s backup accessible for at least a month after launch. If a redirect mapping mistake surfaces two weeks in, having the original content and URL structure on hand makes it far faster to fix than trying to reconstruct what the old page said from memory or a cached search result.
Who should own each part of the checklist
A redesign usually spans several people: a designer for layout and branding, a developer for the build and technical checks, and someone responsible for content and SEO continuity. Assign the redirect mapping and Search Console monitoring specifically to one person by name, since “someone will handle it” is how that step gets missed. On smaller projects, one person may cover all three roles, but the responsibility should still be explicit rather than assumed.
Common mistakes that cause the most damage
| Mistake | Consequence |
|---|---|
| Changing URLs with no redirects | Lost search rankings and broken external links |
| Leaving staging noindex tags on the live site | New site never gets indexed at all |
| No pre-launch backup of the old site | No fallback if the new site has a serious problem |
| Skipping mobile testing on real devices | Broken layouts visitors report after launch, not before |
Want a redesign done without the risk?
We build WordPress sites from $450 and React/Next.js/Node applications from $1,200, and we handle redirects and SEO preservation as standard. Book a free 15-minute call or contact us.
Website redesign checklist: quick answers
How long should a website redesign checklist take to work through?
Planning and SEO preparation typically take a week or two for a small business site, running in parallel with design work rather than after it. Rushing the redirect mapping step specifically is the most common cause of problems after launch.
Will a website redesign hurt my SEO?
Not if the checklist above is followed properly, especially the redirect mapping. Most SEO damage from a redesign comes from avoidable mistakes, not from redesigning itself, so a careful process protects rankings through the transition.
Do I need a website redesign checklist for a small site too?
Yes, the size of the site does not remove the risk. A five-page site with changed URLs and no redirects loses exactly the same kind of traffic and rankings as a large one, just at a smaller scale.
What is the single most important item on a website redesign checklist?
Mapping every old URL to its new equivalent with a 301 redirect. Almost every serious redesign problem traces back to this step being skipped or done incompletely.
