How to Plan a Website Redesign: A Step-by-Step Guide
A practical, step-by-step plan for a website redesign, from setting goals and auditing your current site to testing, launch and what to do afterward.
How to Redesign a Website · Last reviewed October 19, 2026 · 5 min read
A website redesign can feel like a big, shapeless project. There's design to think about, words to write, photos to gather, technical decisions to make and a launch date that keeps drifting. Without a plan, it's easy to spend weeks debating colors and fonts and then discover that nobody has written the service pages.
The good news is that most redesigns follow the same basic sequence. Working through it in order keeps decisions grounded in what your business needs and keeps surprises small. The steps below apply whether you do the work yourself or hire a freelancer or an agency.
Treat this as a checklist you can adapt. A five-page site for a local shop can move through these steps quickly, while a larger site with an online store or many services will need more time at each stage.
Step 1: Set Goals and Get to Know Your Audience
Start with why. What should the new site do better than the old one? Good goals are specific enough to check later. Look more modern is hard to measure; make it easy to book an appointment from a phone is not.
Write down two or three goals and the evidence you'll use to judge them, such as contact form submissions, calls from the site or online orders. If your current site has analytics, record today's numbers so you have a baseline to compare against after launch.
Next, list the main types of people who visit and what each is trying to do. Imagine a dental practice: new patients want to know which insurance is accepted and how to book, existing patients want hours and directions, and job seekers want to see openings. Each group needs a clear path. The people who answer your phone and email are a great resource here, because the questions customers ask most often show what the website should answer up front.
Step 2: Audit the Current Site
Before you change anything, take stock of what you have. A useful audit covers:
- Content: every page, what it's about and whether it's still accurate
- Performance: how quickly key pages load on mobile, using a free tool such as PageSpeed Insights
- Search: which pages bring in visitors from search engines, which Google Search Console can show you if your site is verified there
- Technical: the platform, plugins, hosting, domain registration and who holds the logins
- Accessibility: quick checks for readable contrast, image descriptions and keyboard use
Pay special attention to the list of existing page addresses, or URLs. If any of them will change on the new site, you'll need to set up redirects so old links, bookmarks and search results still lead somewhere useful. Google's site-move guidance recommends mapping every old URL to its new one before launch.
Step 3: Map the New Structure
In planning terms, a sitemap is simply a list or diagram of the pages the new site will have and how they connect. (Search engines also use a technical file called an XML sitemap, which is a different thing.) Group related pages together, keep the main menu short, and use plain names that match the words your customers use rather than internal jargon.
Google's SEO Starter Guide recommends descriptive URLs and grouping topically similar pages together. That kind of tidy structure helps visitors find their way and helps search engines understand how your site is organized.
Step 4: Plan and Write the Content
Content is often the step that holds up a launch, so start it early, ideally while the design is still taking shape. Decide which existing pages will be kept, updated, merged or removed, and who will write anything new. Gather photos, testimonials you have permission to use, and details such as prices, service areas and frequently asked questions.
Writing first also improves the design. It's far easier to design a page around real headlines and paragraphs than around placeholder text that gets replaced at the last minute.
Step 5: Design for Real Screens
Design usually moves from rough to polished: simple page layouts, often called wireframes, come first, followed by full visual designs. Ask to see the mobile version of each key page, not just the desktop view, since many visitors will arrive on a phone. Check that text contrasts clearly with its background, buttons are easy to tap, and the most important action on each page, such as calling or booking, stands out.
Step 6: Build, Test and Launch
During the build, the new site should live at a private staging address, a working copy that the public can't see yet. Before launch, test it thoroughly:
- Click every link and menu item.
- Submit every form and confirm the messages arrive where they should.
- Try the site on several phones and browsers.
- Move through key pages using only the keyboard, with Tab and Shift+Tab.
- Check that every page has a clear, unique title and description.
- Confirm that redirects from old URLs land on the right new pages.
- Make sure any setting that hid the staging site from search engines is removed on the live site.
Choose a launch time when someone can watch for problems. That usually means avoiding the start of a holiday weekend or the busiest stretch of your season.
Step 7: Look After the Site After Launch
Launch is a milestone, not the finish line. In the first few weeks, watch for broken links, form problems and error reports in Google Search Console. Google notes that some changes show up in search within hours while others can take months, and suggests waiting a few weeks before judging the effect of your work.
After that, compare results against the goals and baseline numbers from Step 1. Keep a running list of small improvements, and schedule a regular review so the new site doesn't slowly drift out of date the way the old one did.
Key takeaways
- Set specific, measurable goals before discussing colors or layouts.
- Audit content, speed, search traffic and existing URLs before changing anything.
- Start writing content early, because it commonly causes delays.
- Test forms, links, mobile layouts, keyboard use and redirects before launch.
- Measure results against your original goals in the weeks after launch.
Sources
Spotted something out of date? Let us know.