Key takeaways
- **Website Redesign Checklist:** Use this guide to decide what to fix first, what can wait, and how the work should support a site that is easier to use, manage, and convert from.
A safe website redesign follows a fixed order: inventory every URL, map redirects one to one, preserve on-page SEO, stage the new build, and run launch checks before you point DNS. Skip the inventory and redirect steps and you can lose 20 to 40 percent of organic traffic in the first month.
Most redesigns fail on the same thing. The design looks better, but URLs changed, redirects were guessed, and the pages that earned rankings got merged or deleted without a plan. This checklist keeps traffic intact while the site gets rebuilt. For scope and pricing context, see our website redesign services overview.
1. Inventory every URL before you touch design
You cannot protect what you have not counted. Start by pulling a complete list of live URLs from three sources and reconciling them:
- XML sitemap and CMS export for the pages you know about
- A crawl (Screaming Frog or similar) for pages linked internally
- Google Search Console and analytics for pages that earn clicks and impressions
A 60-page marketing site often has 180 to 300 real URLs once you count blog posts, tag pages, PDFs, and old landing pages. Export the full set to a spreadsheet with columns for URL, current title, primary keyword, monthly clicks, and backlinks. This becomes the master document for the entire project.
Flag the top 20 pages by organic traffic and the top 20 by referring domains. These two lists are the pages you protect at all costs. Everything else has room for consolidation.
2. Decide keep, merge, redirect, or retire
Go through the inventory and assign every URL one of four dispositions:
- Keep: the URL stays the same, content gets refreshed in place
- Merge: two or more thin pages combine into one stronger page
- Redirect: the URL changes, so it needs a 301 to the new location
- Retire: the page is dead weight with no traffic and no links, safe to remove
Retiring pages is fine when they have zero clicks and zero backlinks over 12 months. Retiring a page that still earns 200 clicks a month is how traffic disappears. When in doubt, redirect rather than delete. A 301 to the closest relevant page preserves most of the link value.
3. Map redirects one to one
This is the step that saves or sinks the project. Every URL marked merge, redirect, or retire needs a destination. Build a redirect map with two columns: old URL and new URL.
Rules that hold rankings:
- Point each old URL to the single most relevant new page, not a blanket redirect to the homepage
- Use 301 (permanent), not 302 (temporary), so link equity passes
- Avoid redirect chains. Old A to new B, never old A to old B to new C
- Keep the map in the master spreadsheet so QA can test every row after launch
For a 250-URL site, expect 40 to 90 redirects. Homepage-only redirects for changed URLs are the most common cause of a post-launch traffic drop, because Google treats a mass redirect to the homepage as a soft 404.
4. Preserve on-page SEO signals
The pages you keep should carry their ranking signals into the new design. Before content moves, record for each priority page:
- Title tag and meta description
- H1 and heading structure
- Body copy and internal links
- Image alt text and file names
- Structured data (schema) already in place
Rebuild the new page with the same or stronger signals. If the old page ranked for a term, the new page needs that term in the title and H1. A cleaner design with 60 percent less copy often ranks worse, because thin content competes poorly. Keep the word count on money pages unless the old copy was genuinely padded.
5. Build and review on a staging URL
The new site should live on a password-protected staging environment, blocked from search engines with a noindex tag or robots rule. Two failure modes to avoid:
- Staging gets indexed, creating duplicate content that competes with the live site
- Staging robots.txt with a sitewide disallow gets pushed to production, deindexing the whole site on launch day
Review staging against the master inventory. Confirm every keep page exists, every priority keyword is present, and internal links point to new URLs rather than old ones.
6. Redesign launch checklist
Run this table the day before and the day of launch. Do not point DNS until every pre-launch row passes.
| Phase | Check | Why it matters |
|---|---|---|
| Pre-launch | Redirect map tested row by row | Confirms no 404s on old URLs |
| Pre-launch | Remove staging noindex and disallow | Prevents deindexing the new site |
| Pre-launch | Analytics and tag manager installed | No gap in tracking data |
| Pre-launch | XML sitemap regenerated | Search engines find new URLs fast |
| Pre-launch | Forms and CTAs submit correctly | Protects lead flow on day one |
| Launch | 301 redirects live and returning 301 | Passes link equity to new pages |
| Launch | Robots.txt allows crawling | Lets Google index the new site |
| Launch | Submit new sitemap in Search Console | Speeds recrawl of changed URLs |
| Post-launch | Crawl the live site for 404s and chains | Catches broken redirects early |
| Post-launch | Monitor Search Console coverage 30 days | Spots indexing problems while fixable |
7. Monitor for 30 to 60 days
Launch is not the finish line. For the first 30 days, check Search Console coverage weekly for spikes in 404s or excluded pages. Compare organic clicks week over week against the same period before launch. A 10 to 15 percent dip in the first two weeks is normal as Google recrawls. A 30 percent-plus drop that holds past week three means a redirect or indexing problem to fix now.
Keep the master spreadsheet open through this window. Most post-launch fixes trace back to a row that was missed: a redirect that resolved to a 404, a priority page that lost its title tag, a page that got retired when it should have been redirected.
Preparing your team and content before you start
Most redesign trouble starts before a single page is built, so prepare the groundwork first. Agree on who makes decisions and how fast feedback will come back, because a redesign stalls fastest on slow approvals. Gather your content, brand assets, and analytics in one place so no phase waits on a missing file. Decide the one or two outcomes the redesign must improve, and write them down so success is measurable rather than a matter of taste. And set a realistic window that accounts for design rounds and testing rather than a date picked to feel fast. A redesign that walks in with these settled moves far more smoothly than one that assembles them while the clock runs.
What to check in the first weeks after launch
Launch is the middle of the project, not the end, because real traffic reveals what testing missed. In the first days, confirm every redirect resolves, forms deliver, analytics are recording, and key pages load correctly on real phones. Over the following weeks, watch your search rankings and traffic for pages that dropped, since a missed redirect or a changed URL is the usual cause and the fix is cheap if caught early. Compare conversion on the important templates against where they were before, so a prettier site that converts worse does not go unnoticed. Watching closely for a month turns a risky relaunch into a controlled one, and catches the small problems while they are still small.
Related terms
You may see this topic described with related searches like website redesign plan, website redesign process, website redesign steps, and website redesign strategy. Those phrases are useful when they clarify what the reader needs next, but they should still point back to one clear plan.
Frequently asked questions
How long does a website redesign take?
A standard 40 to 80 page business site runs 8 to 14 weeks from kickoff to launch. Inventory and redirect mapping take 1 to 2 weeks, design 3 to 5 weeks, build 3 to 5 weeks, and QA plus launch 1 to 2 weeks. For budget by scope, see our website redesign cost guide.
Will a redesign hurt my SEO?
It can, but it does not have to. Traffic loss comes from changed URLs without redirects, thinner content, and deindexing accidents. Follow the inventory, redirect, and preservation steps here and most sites hold rankings within 10 percent through launch.
Do I need to redirect old URLs if the design changes but URLs stay the same?
No. If URLs are identical, no redirects are needed. Redirects only matter when a URL changes, merges, or retires. Keeping URLs stable is the single easiest way to reduce redesign SEO risk.
How do I know if I even need a full redesign?
Look at load speed, mobile usability, conversion rate, and how dated the design feels to visitors. A refresh sometimes beats a rebuild. Our guide on when to redesign your website walks through the signs.
Who should own the redirect map?
One named person, usually the developer or SEO lead, owns the map end to end. Shared ownership is how rows get missed. That person builds the map during inventory, keeps it in the master spreadsheet, tests every row at launch, and rechecks it against Search Console during the monitoring window. A single owner means a single source of truth.
Can I redesign in stages instead of all at once?
Yes, and for large sites it often lowers risk. Rebuild one section at a time, such as the blog, then the product pages, redirecting and monitoring each before moving on. A staged rollout limits how much traffic is exposed to any single mistake. The trade-off is a longer overall timeline and a period where old and new designs coexist.
Can I use AI to redesign my website?
Usually, yes, if the work supports a real business goal and someone checks the result after it goes live. If it does not help people find, trust, or convert through the site, it is probably not worth doing.
How do I improve my website performance?
Start with the pages that affect revenue, then test speed, layout stability, mobile usability, images, scripts, forms, and tracking. Fix the issues users actually feel first, then confirm the changes in PageSpeed, analytics, and real conversion data.
How much would it cost to revamp a website?
A website redesign is priced around template count, custom functionality, content migration, integrations, and SEO protection. A simple marketing site may be a smaller project, while a redesign that changes URLs, content, and conversion paths needs discovery, design, development, launch QA, and post-launch monitoring.
Get help with your redesign
A redesign that protects rankings is mostly discipline: count the URLs, map the redirects, preserve the signals, and check every row before DNS flips. If you want a partner to run the inventory and launch process, our website redesign services team handles the full plan from crawl to post-launch monitoring.