How to test a website redesign before launch
A well-organised checklist helps you find navigation, content, performance and SEO issues before the new version goes live.

A redesign can look good and still hide problems that only appear after launch. Broken links, failed forms or differences between mobile and desktop can affect the experience and the website’s results.
Testing is easier when it is divided into categories and focused on the pages that matter most.
Test forms and actions
Submit forms with valid data and check the message shown afterwards. Also test missing fields, invalid email addresses and situations where a service does not respond.
Check that data reaches the correct destination and that the user receives a clear confirmation.
Compare mobile and desktop layouts
Open important pages on different screen sizes. Check the menu, images, headings, spacing, buttons and tables. Content should not overflow the screen or require unnecessary zooming.
Test landscape orientation too when a page includes tables, galleries or wide components.
Check performance and images
Measure key pages before and after the redesign. Optimise images, check main content rendering and watch for new scripts that delay interaction.
Keep images in modern formats and avoid loading resources that are not used on the current page.
Protect the SEO structure
Compare titles, descriptions, headings, URLs, canonical tags and internal links. Check the sitemap, robots.txt and language versions when the website is multilingual.
For changed URLs, confirm the 301 redirects and make sure pages are not all sent to one unrelated destination.
Run a final pre-launch check
Create a list of service, contact, project, article and other pages that bring traffic or enquiries. Repeat the check after publishing because the live environment may have different settings.
Keep a backup version and note what changed so that any issue can be traced more easily.
Monitor the first days after launch
After publishing, check crawl errors, forms, traffic to important pages and user behaviour. Fix problems that affect access or primary actions quickly.
A methodically tested redesign gives you a safer launch and a better foundation for future improvements.
This article was prepared with the assistance of AI tools and editorially reviewed before publication.


