A website redesign should change what visitors can do, not only how the site looks. It is also one of the easiest ways to lose search traffic, break forms, and confuse returning customers if it is rushed. Most of the damage is preventable with a checklist and a clear owner for each item.
This checklist covers the four stages of a redesign: before you start, while you plan and build, on launch day, and in the weeks after.
Before you start: decide what the redesign must change
- Write down the problem. Is the site not producing enquiries, hard to edit, slow, off-brand, or failing to explain new offers? A redesign without a named problem becomes a cosmetic project. If lead flow is the issue, read why websites do not generate leads first.
- Set measurable goals. For example, more qualified enquiries, faster pages, or fewer support questions. Agree how each will be measured.
- Record a baseline. Export current traffic, top landing pages, conversion rates, rankings, and Search Console data. You cannot prove improvement without a “before”.
- Identify your best pages. Find the pages that bring the most organic traffic, links, and enquiries. These need the most care during the move.
- Talk to sales and support. They know which questions buyers ask and where the current site lets them down.
- Decide who decides. Name one owner for approvals. Redesigns run long when feedback comes from a committee.
Plan: structure, content, and URLs
- Inventory every page. List all current URLs with their traffic, purpose, and a decision: keep, merge, rewrite, or remove.
- Design the new structure. Map pages to visitor jobs, with a page for each service and audience that matters. Our guide to website architecture explains how.
- Keep URLs where you can. Unchanged URLs carry their rankings with them. Change them only when there is a clear benefit.
- Build a redirect map. Every old URL that changes or disappears needs a permanent (301) redirect to the most relevant new page, not to the homepage.
- Plan content early. Decide who writes, edits, and approves each page. Late content is the most common cause of delay.
- Protect what ranks. When rewriting high-traffic pages, keep the topics and questions they answer. Improve them, but do not strip them out.
- Choose the CMS deliberately. Pick a system your team can publish in after launch. See our CMS comparison.
Build: design, performance, and tracking
- Design templates, not one-off pages. A small set of reusable page types keeps the site consistent and cheaper to grow.
- Design for phones first. Much of your traffic is likely to be mobile. Test key journeys at phone width early.
- Build for speed. Compress images, limit third-party scripts, and avoid heavy page builders where they are not needed. See website speed and conversion.
- Get the SEO basics right. Unique titles and meta descriptions, one clear H1 per page, logical headings, descriptive alt text, structured data where relevant, and internal links between related pages.
- Make it accessible. Sufficient colour contrast, keyboard navigation, form labels, and meaningful link text help every visitor and reduce legal risk.
- Set up tracking. Install analytics, define conversions for forms and calls, and connect Search Console. Respect consent requirements in the markets you serve.
- Keep the staging site private. Block search engines from the development site so it does not get indexed as a duplicate.
Before launch: test everything that matters
- Test every form end to end. Submit each one, confirm the email or CRM record arrives, and check the confirmation page and message.
- Test redirects. Check a sample of old URLs, especially your top pages, and confirm each lands on the right new page with a 301 status.
- Check links. Run a crawl for broken internal links and missing images.
- Test on real devices and browsers. iPhone, Android, and the main desktop browsers.
- Proofread. Names, phone numbers, prices, legal pages, and placeholder text left behind by templates.
- Check performance. Measure key templates with a speed testing tool and fix the worst issues.
- Prepare a rollback plan. Know how to restore the old site quickly if something critical breaks.
Launch day
- Remove indexing blocks. The most common launch mistake is leaving the staging “discourage search engines” setting or a noindex tag on the live site.
- Switch on redirects and confirm they are working on the live domain.
- Check HTTPS and that all versions of the domain (with and without www) redirect to one preferred version.
- Submit the new sitemap in Google Search Console.
- Confirm analytics and conversions are recording on the live site.
- Clear caches on the server and CDN so visitors see the new version.
- Launch early in the week. Avoid launching before a weekend or holiday when the team is unavailable to fix issues.
After launch: monitor and improve
- Watch Search Console daily for the first weeks. Look for crawl errors, 404s, and pages dropping out of the index. Fix missing redirects as they appear.
- Compare against your baseline. Traffic and rankings can fluctuate briefly after a migration. Sustained drops on specific pages usually point to a missing redirect or removed content.
- Review conversions. Check that enquiries arrive at the expected rate and from the expected pages.
- Collect feedback. Ask sales, support, and a few customers what is clearer and what is not.
- Keep improving. A redesign is a new starting point. Use real visitor behaviour to decide what to refine next. Our note on website conversion optimisation covers how.
Common redesign mistakes
- Starting with visuals before agreeing the problem and goals.
- Deleting or merging pages that brought organic traffic without redirects.
- Redirecting every old URL to the homepage.
- Leaving the site blocked from search engines after launch.
- Forgetting to reconnect forms, analytics, or third-party integrations.
- Launching without a baseline, so nobody can tell whether the redesign worked.
For the final pre-launch checks in more detail, see our website launch checklist.
How Sovassa runs a redesign
We start with what the site must change and the data you already have: the pages that bring traffic, the ones that bring enquiries, and the questions buyers ask. Structure, content, and a full redirect map are agreed before design. Build includes technical SEO, performance, accessibility, and tracking, and we stay on after launch to monitor Search Console and fix what real traffic reveals. Read more about our web development and UI/UX design work, or ask us to scope your redesign.
Frequently asked questions
Will a redesign hurt my SEO?
It does not have to. Rankings usually drop after a redesign because URLs changed without redirects, valuable content was removed, or the site was blocked from indexing. A careful migration plan protects existing traffic and often improves it.
How often should a business redesign its website?
There is no fixed schedule. Redesign when the site no longer explains your offer, cannot be edited easily, performs poorly, or no longer reflects the business. Between redesigns, continuous improvement is usually better value than a full rebuild.
Should we change our URLs during a redesign?
Only when there is a clear benefit, such as a confusing structure. Every changed URL needs a permanent redirect to its closest new equivalent.
How long does a website redesign take?
It depends on the number of page types, the amount of new content, and integrations. Content readiness and decision speed have the biggest effect on the schedule.
