A website redesign can improve your message, mobile experience and enquiries. It can also lose useful search traffic if pages disappear, links break or the new site launches with the wrong settings. A better-looking homepage is little comfort if customers can no longer find your services.
This website redesign SEO checklist covers what to save, test and monitor before, during and after launch. It is written for small-business owners planning a rebuild with a designer or developer. No checklist can guarantee unchanged rankings, but a clear plan helps you catch avoidable mistakes.
The short checklist: protect these five things first
- Your useful pages: identify which URLs already earn search visits, links and enquiries.
- Your content: carry forward the information that helps customers choose you.
- Your URLs: keep working addresses where possible and plan redirects for necessary changes.
- Your launch settings: make sure the public site can be accessed and indexed.
- Your enquiries: test forms, booking links and tracking before declaring the job finished.
Already know you need help with the rebuild? Explore our website redesign service. If you are still deciding whether a refresh is enough, start with when to redesign your website.
Before the redesign: record what already works
1. Save a baseline for traffic and enquiries
Before anyone touches the site, save the last three months of Search Console page and query data. Note the country and search type you used so later comparisons are meaningful. For a seasonal business, also keep a comparable period from the previous year if you have it.
Record which pages lead to qualified calls, form submissions and bookings in your analytics. Search visibility and business results answer different questions: a page with modest traffic may still bring your best enquiries. Write down what the redesign should improve, such as clearer service information or an easier booking process.
2. Make a page-by-page content inventory
- List the current URLs, titles, main headings and important internal links. Include useful downloads and images if their addresses will change.
- Mark pages with search clicks, customer enquiries or links from other websites. Review these before cutting anything.
- Give each page a decision: keep, improve, combine or remove. Record who approves the content and who checks it on the new site.
Do not strip a useful service page down to a vague slogan because the mock-up looks cleaner. Keep the details customers need: who the service is for, what is included, where you work, proof and the next step. Our small-business website guide explains how those pieces fit together.
3. Agree which URLs stay and which must change
Keeping a useful URL is often the simplest choice. A new layout does not require a new address for every page. When a URL must change, put its old address and most relevant replacement in a redirect map before development begins.
For example, if a separate installation page moves into a new services section, visitors using its old link should arrive at the new installation page. Sending every retired service to the homepage leaves people hunting for the information they wanted.
A moved page needs a relevant destination. A genuinely removed page with no suitable replacement can return a proper 404 or 410 response; it does not need an unrelated redirect just to make an error report look tidy. Ask your developer to document that decision.
4. Plan the handover and recovery route
Agree who owns the launch checklist, who can change hosting and domain settings, and who checks the site afterwards. Save a complete backup and establish how it would be restored. Confirm access to WordPress, hosting, Search Console and analytics before launch day. Nobody wants to discover the only login belongs to someone who left two years ago.
During the build: carry the useful work forward
5. Keep the development site private
Build and review the replacement on a staging site so customers can continue using the existing website. Password protection is one way to restrict staging access. Your developer should explain how staging is kept out of search and which restrictions must be removed from the public site at launch.
Keep a clear distinction between staging and live settings. A temporary noindex instruction tells search engines not to index a page. Google explains how noindex works; it should not accidentally carry over to public pages that need to appear in search.
6. Preserve meaning, then improve the copy
Use your inventory to carry over the important service information, helpful headings, testimonials and relevant page titles. Improve thin or confusing copy, but make each change intentional. Replacing a detailed page with a large photo and “Let’s make things happen” is not much help to a customer comparing services.
Give each page a clear job. Your redesign service page should explain the service; this checklist should help someone plan a safer launch. Separate purposes make the site easier to navigate and reduce repetitive content.
7. Rebuild links and test the customer journey
- Update navigation and contextual links to the intended live URLs. Check that buttons do not point to the staging domain.
- Check images, downloads and any links you reuse from the old site.
- Test important pages on desktop and a phone: readable text, working menus, usable forms and clear contact options.
- Check that the new templates still show the right titles, headings and business details.
If budget is shaping the scope, use our Halifax website pricing guide to compare build costs and ongoing expenses. Agree whether content migration, redirect setup and post-launch checks are included in your quote.
At launch: check the public site, not just the preview
8. Test redirects from the old addresses
For permanent moves, ask your developer to use permanent server-side redirects, usually 301 or 308. Test old links directly and check that they reach the right final page without unnecessary chains. A redirect that lands somewhere unrelated is not a useful result.
Google’s site-move guidance recommends keeping redirects for at least a year, and longer where practical. Updating your own internal links to the final addresses also avoids sending visitors through extra steps.
9. Check indexing, canonical URLs and the sitemap
- Open the important public pages without a staging password and check that they load normally.
- Remove staging-only noindex instructions or crawl restrictions from pages that should be public and searchable.
- Check canonical URLs: they should identify the intended public page, not a staging copy or an old address.
- Check the XML sitemap contains the intended live URLs and submit the updated sitemap in Search Console.
- Use URL Inspection to investigate priority pages that appear blocked or missing.
These checks matter even when the domain stays the same. The Google canonical URL guide explains how canonical signals help identify the preferred version of a page.
10. Submit a real test enquiry
Send a clearly labelled test through each important form and confirm it arrives in the right inbox. Test phone links and booking links on a mobile device. Check the confirmation message, any follow-up email and the analytics event for a successful enquiry. A thank-you screen is not proof that the email was delivered.
11. Check the live experience and keep a launch record
Review the homepage, priority service pages and contact route on a phone and desktop. Look for missing images, clipped text, slow-loading sections and broken menus. Record the launch date and any changed URLs so later reporting has context. Keep a short list of problems, with a named person responsible for each fix.
After launch: watch pages and enquiries, not just rankings
12. Compare the pages that mattered before
Check important pages and enquiries immediately after launch, then review performance regularly over the following weeks. Use the same Search Console filters as your baseline. Compare clicks, impressions and queries for individual pages, alongside actual leads. Avoid judging the whole redesign by one day of data or a sitewide average.
If traffic falls, first check for missing pages, failed redirects, accidental noindex settings, server errors and lost content. Then look at which pages, queries, countries or devices changed. Google’s guide to investigating search traffic drops is a useful reference. A dip needs investigation; it does not automatically mean the redesign failed.
13. Keep ownership after the launch party
Assign responsibility for updates, backups, forms and content accuracy. Our WordPress maintenance plans cover ongoing website care; make sure any support agreement spells out what is included.
Keep the redirect map, access details and launch checks with your website records. The next person maintaining the site should be able to understand what changed without playing digital archaeology.
Do you need a full redesign or a smaller refresh?
Unclear services, difficult mobile layouts, broken contact paths and a platform you struggle to maintain are all worth investigating. Some problems need a rebuild; others need better copy, a repaired form or a more focused service page.
For that decision, use our guide to when a website redesign makes sense or review six signs your Halifax website may be costing you clients. This checklist becomes your handover and launch plan once the scope is agreed.
Website redesign and SEO: frequently asked questions
Will a website redesign hurt my SEO?
It can if useful pages disappear, important content is removed or the replacement site cannot be indexed. Planning and testing reduce avoidable problems, but nobody can promise identical rankings after a substantial change. Keep a baseline and check what happens after launch.
Can I redesign my website without changing its URLs?
Yes. A new WordPress theme, layout or clearer copy does not automatically require new page addresses. Preserve useful URLs where possible. Still check content, internal links, canonical URLs and indexing settings after the new design goes live.
Do I need Search Console’s Change of Address tool?
Not for a visual redesign or changes to page paths on the same domain. Google’s Change of Address tool is for moves between domains or subdomains. If you are changing the domain too, include that move in the migration plan rather than treating it as a design detail.
How long does SEO take to settle after a redesign?
There is no dependable fixed deadline for every website. The scale of the changes and how quickly pages are recrawled affect the process. Fix technical errors promptly and monitor the affected pages over time. A broken redirect will not improve simply because you wait another month.
Should my redesign quote include SEO checks?
Ask for a written scope covering the content inventory, URL decisions, redirect testing, public indexing settings and post-launch checks. “SEO included” is too vague on its own. Ongoing content work and a continuing SEO campaign are separate commitments unless your agreement includes them.
Planning a redesign? Start with what is worth keeping.
Bring the current site, the problems you want to solve and the pages that already earn enquiries. We can talk through what needs improving and what the rebuild should preserve. Explore our website redesign service, see examples of our work, or ask Paul about your redesign.
