Most website redesigns fail for reasons that have nothing to do with design. The new site looks better, launches a month late, and then the phone gets quieter: rankings slip because old URLs were never redirected, the contact form stops reaching the right inbox, and nobody can say whether the new site performs better than the old one because nobody measured the old one. This website redesign checklist is the list we work through before we write a line of code or open a design file. Twenty-one items, grouped by phase, in roughly the order they matter.
If you're still deciding whether you need a rebuild at all, start with the five signs a business has outgrown its website. If you've already decided, keep reading.
Phase 1: Decide what the redesign is for (items 1–5)
1. Write down the business reason in one sentence
"It looks dated" is a symptom, not a reason. A useful reason sounds like: "We get traffic but almost no quote requests," or "We added two services and the site still describes the business we were three years ago." That sentence becomes the test every later decision has to pass.
2. Pick the two or three numbers that define success
Usually some mix of qualified form submissions, phone calls, booked appointments, and organic traffic to service pages. Pick them now, because you'll need a baseline for each before launch.
3. Capture a baseline from the current site
Export at least the last twelve months from your analytics and Google Search Console: top landing pages, top queries, conversions by page, and pages with backlinks. Without this, "the new site is working" is an opinion.
4. Name the decision-maker and the approvers
Redesigns stall in review cycles. Decide who signs off on copy, who signs off on design, and who has final say when they disagree. One final voice, not a committee.
5. Separate must-haves from nice-to-haves
List every feature request, then mark each one as launch-critical or post-launch. Online booking might be launch-critical; a resource library probably isn't. This is the single biggest lever on timeline and scope.
Phase 2: Protect what already works (items 6–11)
6. Crawl and inventory every existing URL
Use a crawler or your CMS export to list every live page, including old blog posts and PDFs. Pages you've forgotten about are often the ones still pulling search traffic.
7. Build a redirect map before design starts
Every old URL either keeps its address or gets a permanent (301) redirect to the most relevant new page. Not the homepage — the closest matching page. Google's own documentation on moving a site with URL changes walks through why mapping old to new matters.
8. Keep the pages that rank, even if you rewrite them
If a service page ranks well, improve it in place rather than merging it into something new. Keep its core topic, its URL where possible, and the content that earned the ranking.
9. Document every form, integration and notification
Where does each form send its data? Which email addresses get notified? Is anything feeding a CRM, a booking tool, or a spreadsheet someone checks every morning? Write it all down. Lost integrations are the most common silent failure after launch.
10. Inventory tracking and tags
Analytics, Search Console verification, ad conversion tags, call tracking numbers. List them and decide which carry over. If you're in healthcare, this is also when you confirm no third-party tracking ends up on pages where patients log in or submit health information.
11. Confirm who owns the domain, DNS and hosting accounts
We regularly meet owners whose domain is registered under a former employee's or former agency's account. Sort out access before launch week, not during it.
Phase 3: Content and conversion (items 12–16)
12. Write the copy before you design the pages
Designing around lorem ipsum produces pages that look finished and say nothing. Draft real headlines, service descriptions and calls to action first, then design around them.
13. Give every service its own page
One "Services" page listing everything you do can't rank for, or convert on, any single service. Each core service gets a page that explains who it's for, what's included, how the process works, and what to do next.
14. Make the next step obvious on every page
Each page should have one primary action: request a quote, book a call, schedule a visit. Secondary links are fine; competing primary buttons are not. Our guide to websites that generate leads goes deeper on this.
15. Shorten your forms
Ask only for what you need to respond well. Every extra required field is a reason to leave. You can collect the rest on the first call.
16. Put real trust signals where decisions happen
Licenses, certifications, years in business, real project photos, genuine reviews with permission to use them. Place them next to the call to action, not buried on an About page. Don't invent or embellish any of them.
Phase 4: Build, launch and verify (items 17–21)
17. Design for phones first
For most local service businesses, a large share of visitors arrive on a phone. Click-to-call, readable text without zooming, and forms that work with a thumb are baseline requirements, not extras.
18. Set a performance budget
Decide up front what the site is allowed to load: image sizes, scripts, third-party widgets. Every chat widget and tracking script you add costs speed. It's easier to say no during the build than to claw speed back later.
19. Build accessibility in, not on
Proper heading structure, alt text, color contrast, labeled form fields, and keyboard navigation. Retrofitting accessibility after launch costs more than doing it during the build.
20. Run a pre-launch QA pass
Test every form submission end to end, every redirect in the map, every phone link, and every page on at least one iPhone and one Android device. Check that the staging site was blocking search engines and that the live site isn't.
21. Watch the first 30 days closely
Check Search Console for crawl errors and 404s weekly, compare conversions against your baseline, and fix broken redirects as you find them. Launch is the midpoint of a redesign, not the end.
Mistakes that make a website redesign checklist necessary
Almost every painful rebuild we've been asked to rescue traces back to one of these:
- Treating launch as the finish line. Nobody is assigned to watch traffic, forms and rankings afterward.
- Letting the platform drive the plan. Choosing a theme or builder first, then bending the business to fit it.
- Redesigning and re-platforming and rebranding at once without extra time for each. Any one of those is a project; all three is a program.
- Skipping the redirect map. The fastest way to lose rankings you spent years earning.
- No owner for content. The build waits weeks for copy that was "almost done."
How to use this checklist with whoever builds your site
Hand this list to any developer or agency you're considering and ask how they handle each phase. Pay particular attention to items 3, 7, 9 and 21; those separate a team that builds websites from a team that protects a business through a rebuild. Our post on how to choose a web design company in Salt Lake City has more questions worth asking.
When we run a website build, the redirect map, integration inventory and post-launch monitoring are part of the scope, not add-ons. Cost depends on scope, which is why we quote each build individually.
FAQ
How long does a website redesign take?
It depends on page count, how much content needs writing, and integrations. A focused small-business site moves much faster than a rebuild that also changes platforms and adds booking or a CRM. The content step is the most common cause of delay.
Will a redesign hurt my Google rankings?
It can if URLs change without redirects or ranking content gets cut. With a complete redirect map and preserved content on pages that already rank, most of that risk is manageable. Nobody can honestly guarantee rankings after a rebuild.
Should I redesign or just refresh the current site?
If the structure, platform and integrations work and the problem is mostly visual or copy, a refresh may be enough. If you can't add pages easily, the site is slow on phones, or forms aren't connected to how you work, a rebuild usually makes more sense.
What should I prepare before talking to a developer?
Your one-sentence business reason, your success metrics, a baseline export from analytics and Search Console, your list of must-have features, and login access to your domain and hosting.
Do I need to rewrite all my content?
Not necessarily. Keep and improve pages that rank and convert. Rewrite pages that are thin, outdated or describe services you no longer offer.
A website redesign checklist only helps if someone owns it from kickoff through the first month after launch. If you want a team that does, see how we approach website builds, or request a quote with your goals and current site, and we'll tell you honestly whether you need a rebuild or a refresh.