Beta mumus is in public beta: free while we test it with real teams. Found something odd? Tell us.

Website launch checklist - the QA tests to run before going live

Most launch problems are small and avoidable: a broken form, a missing redirect, a page that still says "noindex". Run through this checklist on the staging website and again on the live website right after launch.

Content

  • All placeholder text and images replaced; no "Lorem ipsum" anywhere
  • Spelling and grammar checked, especially headings, buttons and prices
  • Contact details, company details and legal pages complete and correct
  • Images have meaningful alternative text and reasonable file sizes
  • Dates, prices and currencies formatted for the audience

Functionality

  • Every link works, including the navigation, footer and buttons
  • Forms send, show a confirmation and arrive where they should
  • Search, filters and logins work with real data
  • Checkout or booking flows tested end to end, including payment in test mode
  • The 404 page exists and helps people find their way back

Browsers and devices

  • Current versions of Chrome, Edge, Firefox and Safari
  • At least one Android phone and one iPhone, in portrait and landscape
  • Narrow and very wide windows, and 200 % zoom
  • No console errors on the main pages

Performance

  • Main pages load quickly on a mobile connection
  • Images are compressed and sized for the layout
  • Caching and compression are enabled on the server

SEO

  • Every page has a unique title and meta description
  • The robots meta tag and robots.txt allow indexing on the live website (and only there)
  • An XML sitemap exists and is submitted to search engines
  • Old addresses redirect permanently (301) to their new pages
  • Canonical links point to the live addresses, not to staging
  • Social sharing images and titles look right

Accessibility

  • Everything works with the keyboard alone, with a visible focus
  • Text has enough contrast against its background
  • Form fields have labels and errors are explained in text
  • Headings are in a logical order

Privacy, legal and security

  • Imprint, privacy policy and terms published and linked in the footer
  • Cookie consent works and no optional cookies are set before consent
  • HTTPS everywhere, with a valid certificate and HTTP redirected to HTTPS
  • Admin areas protected, default accounts removed, backups configured

After launch

  • Repeat the functionality and SEO checks on the live website
  • Watch error logs and form submissions for the first days
  • Keep collecting feedback from the team and the client in one place

Running the checklist as a team

Split the checklist between people and devices, and have everyone report findings in the same place, with the page, a screenshot and the device. With a visual bug reporting tool such as mumus, testers click on each problem on the staging website and the findings appear on a board, where they can be fixed and retested before launch.

Frequently asked questions

What should I test before launching a website?

Content (no placeholders, correct legal pages), functionality (links, forms, checkout), browsers and devices, performance, SEO (titles, indexing, sitemap, redirects), accessibility (keyboard, contrast, labels), privacy and security (cookie consent, HTTPS, protected admin).

Which browsers should a website be tested in?

At least current versions of Chrome, Edge, Firefox and Safari on desktop, plus one Android phone and one iPhone. Test narrow and wide windows and 200 % zoom as well.

More questions in the help centre

Turn website feedback into tasks your team can fix.