Website QA checklist: what to test before launch
Launch-day bugs are rarely exotic. They are a contact form that emails nobody, a hero image that is three megabytes, a page that still says “Lorem ipsum” under the fold, or a menu that cannot be closed on a phone. A checklist will not catch everything, but it reliably catches the boring things, and the boring things are most of what goes wrong.
This is the list we would run on any marketing site or web app before it goes live. Work through it on the real staging environment, not on a local build, and write each problem down the moment you find it. There is advice on reporting at the end.
1. Content and copy
- No placeholder text, sample images or “TODO” left anywhere, including in alt text and meta descriptions.
- Spelling and grammar checked on every page, including buttons, error messages and emails.
- Names, prices, addresses, phone numbers and dates are correct and consistent across pages.
- Legal pages exist and are linked: privacy policy, terms, cookie notice where required.
- The copyright year and company details in the footer are right.
- Empty states, error pages and the 404 page have real copy.
2. Links and navigation
- Every link in the navigation, footer and body goes where it says. Run a link checker to find 404s.
- No links point at staging, localhost or a preview domain.
- External links open where you intend, and links to files (PDFs) work.
- Redirects from old URLs are in place if this replaces an existing site.
- The logo returns to the home page.
3. Forms
Forms are where launches quietly fail, because they look fine until someone submits one.
- Submit every form for real and confirm the submission arrives where it should: inbox, CRM, database.
- Required fields are enforced, and the error messages say how to fix the problem.
- Validation accepts real-world input: long names, plus signs in emails, international phone numbers.
- The success state is clear and the form cannot be double-submitted.
- Spam protection is on and does not block real people.
- Confirmation emails send, render properly, and come from the right address.
4. Layout and responsive design
- Check every page template at phone, tablet and desktop widths, plus one very wide screen.
- Nothing overflows horizontally on a phone. A sideways scroll usually means one element is too wide.
- Tap targets are large enough and not crowded together.
- The mobile menu opens, closes and can be used with one thumb.
- Images are sharp, correctly cropped and not stretched.
- Sticky headers, cookie banners and chat widgets do not cover content or buttons.
5. Browsers and devices
- Test in current Chrome, Safari, Firefox and Edge at a minimum.
- Test on at least one real iPhone and one real Android phone. Emulators miss touch and keyboard behaviour.
- Check that fonts load, and that the fallback font is acceptable if they do not.
- Note the exact browser and version of anything that fails; it is the first thing a developer will ask.
6. Accessibility basics
- Every page can be used with the keyboard alone, and the focus outline is visible.
- Images that carry meaning have alt text; decorative ones have empty alt text.
- Text has enough contrast against its background, in light and dark themes if you have both.
- Form fields have labels, not just placeholder text.
- Each page has one h1 and headings in a sensible order.
- Animations respect the reduced-motion setting.
Automated checkers find a useful share of accessibility problems, but not all of them. Tab through the main journey yourself at least once.
7. Performance
- Run a performance audit (Lighthouse or similar) on the home page and the heaviest template.
- Images are compressed and served at sensible sizes; nothing huge loads above the fold.
- The page does not jump around as it loads (layout shift).
- Third-party scripts are only the ones you need, and none of them block the page from rendering.
- Test once on a throttled mobile connection, not only on office wifi.
8. SEO and sharing
- Every page has a unique title and meta description.
- Canonical URLs point at the production domain.
- The robots settings that hid staging from search engines are removed on production.
- A sitemap exists and is submitted.
- Share cards (Open Graph images) render when a link is pasted into a chat app.
- The favicon and app icons show up.
9. Analytics, tracking and consent
- Analytics records page views on production, and staging traffic is excluded.
- Conversion events (sign-ups, purchases, form submissions) fire once each.
- The cookie banner, where required, actually blocks non-essential cookies until consent.
10. Security and the unglamorous parts
- HTTPS everywhere, with no mixed-content warnings.
- Staging passwords, debug flags and test API keys are not on production.
- Error pages do not show stack traces.
- Backups and uptime monitoring are set up before launch, not after the first outage.
How to report what you find
A checklist produces a list of problems, and a list of problems only helps if each one can be fixed without a follow-up conversation. For each issue, capture:
- the page URL,
- the exact element, described so it cannot be confused with another,
- what you did, what you expected and what happened,
- the browser, operating system and screen size,
- a screenshot, and a recording if the bug needs several steps.
The guide to writing bug reports goes through each of these in detail, and the free bug report template turns them into Markdown you can paste into your tracker.
If several people are testing, it pays to collect findings on the page itself instead of in a spreadsheet. With Jot on the staging site, a tester clicks the broken element and types one sentence; the screenshot, URL, selector and browser details are attached automatically, and each finding can be filed into GitHub, Linear, Jira or Trello from the dashboard (see integrations). It also means clients and non-technical reviewers can join the QA pass without learning a template; the client feedback guide covers that side.
Keep the checklist alive
Every launch teaches you one new thing that should have been on the list. Add it. A checklist that grows from real misses is worth more than any generic list, including this one. Start here, then make it yours.