HANDMADE DESIGN / WEB DEVELOPMENT GUIDE
Website Redesign Checklist: Protect SEO and Improve the Customer Journey
A redesign should solve a business problem, not simply replace the colors and fonts. The launch can change navigation, content, code, page speed and URLs at the same time. Without a plan, teams may accidentally remove valuable pages or break the contact paths customers use.
This checklist is designed for small and medium-sized businesses preparing a site refresh or full rebuild.
Before design starts
Define the goal. Decide whether the project aims to increase enquiries, improve conversion, simplify content maintenance, support a new offer or solve technical problems. Choose a small set of measurements you can compare before and after launch.
Inventory existing URLs. Export the sitemap, crawl the current site and collect page-level data from Google Search Console. Include important URLs discovered in external link reports, analytics and server logs. Do not assume the current menu contains every valuable page.
Save a baseline. Record search clicks, impressions, top landing pages, enquiry submissions, conversion tracking, page speed and index coverage. A redesign without a baseline makes improvement hard to prove.
Understand the audience. Talk to customers and review the questions sales teams answer repeatedly. A design should make those answers easier to find.
Information architecture and content
Map old pages to new destinations. Each page should either keep its URL, move to a relevant equivalent or be removed with a real 404/410. Do not redirect hundreds of unrelated pages to the homepage.
Protect high-value material. A guide with relevant incoming links may deserve an updated page at the same URL even when it does not appear prominently in the new navigation.
Plan service pages individually. If you sell website development, Shopify, SEO and ads, explain each service separately rather than expecting one generic page to rank for everything.
Write before polishing. Make sure page headings, services and calls to action are clear. Design around real text and real content lengths.
Design and development
Design mobile behavior intentionally. Test navigation, forms, headings and sticky components at narrow widths. Do not rely on a desktop mockup as the mobile specification.
Keep accessibility in scope. Use semantic HTML, labels, keyboard access and visible focus states. Test the primary task from start to finish.
Track performance from the start. Limit image weight and optional JavaScript. Heavy animation or third-party widgets can undermine a polished experience.
Check important links. Menus, footer links, calls to action, legal pages and social profiles should all lead somewhere useful.
Pre-launch SEO checklist
- Every important page has a unique, descriptive title and H1.
- Canonical URLs use the correct domain and HTTPS.
- No accidental site-wide
noindexorDisallow: /remains. - Sitemaps contain only current, intended canonical URLs.
- Internal links use final destinations rather than redirect chains.
- Old URLs redirect to relevant new equivalents when content moved.
- Removed pages return real 404/410 statuses where appropriate.
- Translated pages use correctly paired
hreflangannotations. - Forms, analytics and conversion tracking are tested.
- The live site works for keyboard and mobile users.
On launch day
Deploy pages and redirects together. Check a sample of the most valuable URLs with a command-line HTTP request and a browser. Confirm that each redirect finishes at a page returning HTTP 200, with no redirect loop and no chain through several intermediate URLs.
Submit the new sitemap to Search Console. Inspect the homepage, major service pages and a few previously linked guides. Keep an eye on unexpected 404 spikes, indexing changes and missing conversions.
After launch: the first month
Track search and enquiry performance in weekly windows rather than panicking over a single day. Some fluctuation after a major change is normal. Fix technical blockers first: broken forms, server errors, misconfigured canonicals and redirects. Then review content gaps and opportunities for improvements.
Google recommends keeping permanent redirects in place for at least a year after a site move; in many cases it is best to keep useful redirects indefinitely. If you own referring links, update them to the final URL as well.
When do you need a complete rebuild?
A full rebuild may be justified when your platform blocks necessary improvements, core page templates are difficult to maintain or the structure no longer fits the business. If the foundation is sound, an incremental redesign can be cheaper and less risky.
For a deeper technical review, use our technical SEO audit checklist. If you want help planning and shipping a redesign, explore website design and development or contact our team.
