Quality assurance · Practical guide

What to test before a website launch

A launch checklist should test what visitors actually do—not just whether a page looks correct on one laptop. Record the expected result and repeat critical journeys after fixes.

1. Test the key journeys

Open every important page directly, follow the main navigation, click primary calls to action and test browser back/forward behaviour. Check for links that point to missing destinations or obsolete .html URLs.

2. Test forms and delivery

Try empty required fields, malformed email addresses, unusually long messages and a valid submission. Confirm what happens after submit, where the data goes and whether any confirmation is honest. A mailto form prepares an email; it does not prove the email was sent.

3. Check mobile and accessibility

Test narrow screens and tablet widths, zoom text, operate menus with a keyboard, check visible focus, labels, contrast and reduced-motion preferences. Ensure no important action depends only on hover.

4. Check SEO and content

Verify a unique title and description, canonical URL, correct heading order, descriptive image alt text, Open Graph metadata, working sitemap and appropriate robots directives. Keep structured data consistent with visible, verified information.

5. Check runtime and security

Review browser console and network errors, image loading, JavaScript failures, HTTPS, exposed secrets, third-party requests and measured performance. Re-test each reported issue after a fix and save evidence for anything still unresolved.

Quick checklist

  • Links and direct loading for every route
  • Form validation and true delivery behaviour
  • Mobile, keyboard and contrast checks
  • Titles, descriptions, canonical and sitemap
  • Console, network and security review
  • Re-test and release notes
Keep it grounded: adapt this checklist to your organisation, technical setup and legal obligations. The right scope depends on the actual use case and requirements.

Discuss a project