A website redesign affects more than colours and layouts. It can change navigation, URLs, content, tracking, forms and how search engines discover key pages. A structured checklist helps the team improve the experience while protecting useful assets and reducing avoidable launch problems.
Set goals and inventory the site
Define why redesign is needed: clearer offers, better mobile usability, updated content, simpler navigation or a new business model. Choose a few measures that could show whether the work helped. Without goals, teams may spend time on visual details while the main problem remains.
Inventory URLs, forms, downloads, images, tracking events and external links. Use analytics and Search Console where available to identify pages that attract relevant traffic or enquiries. Keep business, policy and contact information accurate.
Plan content and URL changes carefully
Map each important old URL to the most relevant new URL if the structure changes. Keep working URLs where feasible. If a page is removed, redirect users to a genuinely relevant replacement rather than sending every old URL to the homepage. Update internal links.
Do not delete content just because it is old. Decide whether each page should be retained, improved, consolidated or removed based on purpose, accuracy, relevance and performance. Avoid replacing a useful article with thin copy merely to simplify the design.
Review mobile usability and accessibility
Test navigation, headings, buttons, forms, phone links, tables, images and accordions on real mobile devices or reliable emulation. Ensure the primary action remains clear and pop-ups do not obscure important content.
Use readable fonts, sufficient contrast, clear focus states, descriptive labels and keyboard-accessible controls. Add useful alt text to informative images and do not place essential text only inside graphics. Make form errors explain how to fix the problem.
Protect technical SEO and measurement
Ensure important pages can be crawled, titles and headings are descriptive, canonical URLs are correct and internal links point to live pages. Update the sitemap to preferred URLs after launch. If URLs change, prepare a redirect map and monitor errors.
Validate analytics and conversion tracking in staging and production. Test forms, call events, consent handling where applicable and CRM connections. Google’s canonical URL guidance explains how redirects, canonical annotations and sitemap signals can help consolidate duplicate versions; implement them accurately.
Run staged QA and launch
Before launch, check broken links, missing images, spelling, metadata, redirects, forms, responsive layouts, performance and access controls. Confirm who can edit the site and how to roll back a serious problem. Test representative templates, not just the homepage.
After launch, crawl the site, test key conversions and monitor indexing, traffic, enquiries and errors. Keep a change log so the team can distinguish redesign effects from unrelated fluctuations.
Treat launch as the beginning of maintenance
After launch, review search queries, customer feedback and page performance. Fix defects, update confusing content and investigate technical problems rather than waiting indefinitely for search engines to process changes.
Assign an owner for accuracy, technical updates and measurement. A maintained website is more sustainable than rebuilding every few years because no one owns ongoing improvements.
Create a pre-launch inventory and redirect map
Before changing design or URLs, export a list of important current pages, their status, canonical URL, organic traffic or links where available, forms, analytics events and internal links. For each changed URL, decide whether to keep it, improve it, consolidate it with a relevant page or redirect it to the closest equivalent destination.
Avoid sending every old URL to the homepage. A redirect should help users and search engines find the relevant replacement. Update internal links and sitemaps after launch, test redirect chains and keep a record of the mapping so the team can troubleshoot unexpected traffic changes.
Use a staged launch rather than a single visual check
Before release, test representative page templates, mobile layouts, keyboard accessibility, form submission, error messages, analytics, consent behaviour, metadata, indexability and broken links. Verify that staging restrictions are removed only for the intended production pages and that important pages remain crawlable.
After launch, monitor server errors, indexing, organic landing pages, conversions and user feedback. Compare with a meaningful baseline while allowing for seasonality and normal fluctuations. Fix technical regressions first; then use the new structure to improve content, navigation and calls to action.
- Back up current content and URLs
- Test redirects and enquiry flows
- Keep a change log and post-launch owner
Put it into practice
- Inventory URLs, forms, tracking events and pages with existing search value.
- Map every changed URL to a relevant destination and test redirects.
- Test mobile, accessibility, forms, analytics and crawlability before launch.
- After launch, monitor indexing, errors, enquiries and unexpected traffic changes.
Frequently asked questions
Will a redesign hurt SEO?
It can if content, URLs, redirects, internal links or indexability are mishandled. A planned redesign can improve clarity and usability; monitor it carefully.
Should all URLs change?
No. Keep useful, stable URLs where feasible. Map changed URLs to relevant destinations and implement redirects.
What should we check immediately after launch?
Test key pages and forms, confirm analytics, inspect redirects and broken links, verify indexability and review enquiry data for unexpected problems.
Next step
Hakaru Infotech supports web development and digital growth work. Discuss your redesign goals before finalising the scope.
Explore Hakaru Infotech services | Discuss your requirements
