ChecklistLab

Website Launch

Website QA Checklist

Use this QA checklist to catch the ordinary mistakes that make a finished website feel unfinished to visitors and clients.

Use when: Use it after design and content are mostly final, before the launch owner signs off.

Start with: Open every page.

Then review: Website Launch Checklist.

What this website QA checklist covers

Use this section to confirm the checklist fits the work before you start. If it does, move through the steps in order and log anything that needs an owner.

  • Page-by-page review
  • Responsive layout
  • Forms and links
  • Content accuracy
  • Accessibility basics
  • Browser checks

Who should use it

This checklist is written for people who need to ship practical work, review client deliverables, or maintain a site without adding process for its own sake.

  • Designers handing off sites
  • Developers preparing production deploys
  • Agencies standardizing client QA
  • Business owners reviewing a new website

Content and design QA checks

Use it after design and content are mostly final, before the launch owner signs off.

  • Create a list of all live pages and key states.
  • Gather final copy, images, legal links, and contact details.
  • Decide which browsers and device sizes matter most.
  • Make sure someone owns fixing each issue found.

Website QA checklist: step by step

Work from top to bottom. Skip a step only when someone has already checked it and there is a clear owner for the result.

  1. Step 1

    Open every page

    Check layout, copy, images, buttons, and section order on every required page.

  2. Step 2

    Test mobile first

    Review the site at phone width before desktop because mobile issues are often launch blockers.

  3. Step 3

    Click every navigation item

    Confirm header, footer, cards, breadcrumbs, and related links lead to the right pages.

  4. Step 4

    Submit all forms

    Test success states, error states, required fields, notifications, and tracking events.

  5. Step 5

    Proofread visible copy

    Check spelling, outdated references, draft-only text, repeated sections, and inconsistent capitalization.

  6. Step 6

    Review visual consistency

    Look for mismatched spacing, awkward line breaks, oversized text, and inconsistent card styles.

  7. Step 7

    Check accessibility basics

    Verify heading order, focus states, keyboard navigation, image alt text, and color contrast.

  8. Step 8

    Test performance basics

    Compress heavy images, remove unused scripts, and check that the page feels fast on mobile.

  9. Step 9

    Log issues clearly

    Record the URL, device, browser, issue, severity, screenshot, and owner for each fix.

Common QA mistakes

These are the issues that usually create rework, client friction, or avoidable launch cleanup.

  • Only reviewing the homepage.
  • Testing forms with unrealistic data.
  • Ignoring footer links.
  • Checking desktop but not mobile.
  • Reporting vague issues like “looks weird” without a screenshot or URL.

Download this QA checklist

Use this page as the working version. Print it, save it as a PDF, or copy the steps into your project workspace. If you need the next related check, open Website Launch Checklist.

Website QA FAQ

Who should do website QA?

Ideally someone who did not build the page should perform the final review because they are more likely to notice unclear flows and missing details.

Should QA happen in staging or production?

Run full QA in staging, then repeat critical checks in production after launch.

What is a launch-blocking QA issue?

Anything that breaks conversion, damages trust, blocks access, exposes private information, or prevents search engines from crawling important pages.