Checklist

Website launch checklist

A practical pre-launch checklist covering content, accessibility, performance, security, SEO and AI readiness, with the free tools to check each item.

Published

Short answer

Before launching a website, check that every page works on real devices and browsers, meets WCAG 2.2 AA for accessibility, loads quickly (Core Web Vitals in the "good" range), is served over HTTPS with sensible security headers, can be crawled and indexed, and has working forms, analytics and error pages. Print this checklist and work through it with the site's owner.

Key takeaways

  • Test real journeys on real devices, not just pages in one browser.
  • Run an automated accessibility check, then test key journeys with a keyboard.
  • Measure performance against the Core Web Vitals thresholds.
  • Confirm HTTPS, security headers and that no test credentials or debug pages are live.
  • Check search and AI readiness basics - titles, descriptions, sitemap and structured data.

Definitions

WCAG (Web Content Accessibility Guidelines)
WCAG is the W3C's international standard for making web content accessible to people with disabilities. WCAG 2.2 is the current version, with success criteria at three levels, A, AA and AAA; most laws and policies expect level AA.
Core Web Vitals
Core Web Vitals are Google's three metrics for real-world page experience - Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability) - each with a "good" threshold measured at the 75th percentile of visits.
Accessibility testing
Accessibility testing checks whether people with disabilities can perceive, understand, navigate and use a website or app, usually by measuring it against WCAG with a mix of automated tools and manual checks.

How to use this checklist

Work through it with the site’s owner a few days before launch. Tick each item in your browser, or save the page as PDF and print it. Where a tool is suggested, a free one is enough.

Content and functionality

  • Every page has real content: no placeholder text or images left in
  • All links work, including in the header, footer and emails
  • Every form submits, sends to the right place and shows a clear confirmation
  • Form errors explain what went wrong and how to fix it
  • Key journeys work end to end: sign-up, checkout, contact
  • The site works in current Chrome, Firefox, Safari and Edge
  • Key journeys work on at least one real phone and one tablet
  • The 404 page is helpful and links back into the site

Accessibility (WCAG 2.2 AA)

  • An automated check (axe-core, WAVE or Lighthouse) shows no errors on key templates
  • Text has sufficient colour contrast
  • Every meaningful image has alternative text that describes it
  • Every form field has a visible label
  • You can reach and use everything with a keyboard alone, in a sensible order, with a visible focus indicator
  • Headings are in a logical order and the page language is set
  • Key journeys work with a screen reader
  • Content still works when zoomed to 200%

Performance

  • Largest Contentful Paint is 2.5 seconds or less on a mid-range phone
  • Interaction to Next Paint is 200 milliseconds or less
  • Cumulative Layout Shift is 0.1 or less
  • Images are compressed and sized for the screen they are shown on
  • Caching and compression are switched on

Security

  • The whole site is served over HTTPS, and HTTP redirects to HTTPS
  • Security headers are set, such as Strict-Transport-Security and Content-Security-Policy
  • No test accounts, debug pages or staging links are reachable
  • Admin areas need strong authentication
  • Dependencies and plugins are up to date
  • Backups are working and you have tested a restore

Search and AI readiness

  • Every page has a unique title and meta description
  • Canonical tags point to the right URLs
  • An XML sitemap is published and robots rules allow the pages you want found
  • Structured data is valid for the page types you use, such as Organization, Article or Product
  • Important answers appear in plain text near the top of the page, not only in images or scripts
  • Redirects are in place from any old URLs
  • Privacy notice and cookie consent are in place and work
  • Analytics records visits and key events
  • An accessibility statement is published, if your sector requires one

After launch

  • Check the live site again: forms, analytics, redirects
  • Submit the sitemap to search engines
  • Set up monitoring for uptime and errors
  • Record any bugs found with clear steps to reproduce, screenshots and the device and browser used

Tools in this guide

  • Lighthouse

    Google

    Google's open-source auditing tool for performance, accessibility, SEO and best practices, built into Chrome DevTools.

    Performance tools, Accessibility tools, SEO audit tools. Open source. Last reviewed .

    Profile
  • axe-core

    Deque Systems

    Open-source accessibility rules engine that checks web pages against WCAG 2.0, 2.1 and 2.2 and plugs into existing automated test suites.

    Accessibility tools. Open source. Last reviewed .

    Profile
  • WAVE

    WebAIM

    WebAIM's accessibility evaluation tool, which shows errors, alerts and structure directly on the page to support human review.

    Accessibility tools. Freemium. Last reviewed .

    Profile
  • Playwright

    Microsoft

    Microsoft's open-source framework for end-to-end testing and browser automation across Chromium, Firefox and WebKit.

    Testing tools. Open source. Last reviewed .

    Profile
  • HolstrOur product

    RedevIO Ltd

    Scotland-built test recording tool that helps testers capture evidence and write clearer, reproducible bug reports.

    Testing tools. Free trial. Last reviewed .

    Not scored

Frequently asked questions

How long before launch should I start testing?

As early as possible. Run automated checks from the first build, and leave at least a few days before launch for a full pass through this checklist, so there is time to fix what you find.

What is the most commonly missed launch check?

Accessibility. Low-contrast text, missing alternative text and unlabelled form fields are among the most common failures on the web and are quick to catch with free tools.

Do I need to test on mobile?

Yes. Test key journeys on at least one real phone, not only in a desktop browser's mobile view.

Sources

  1. How the Core Web Vitals thresholds were defined (web.dev)
  2. WCAG 2 Overview (W3C WAI)
  3. The WebAIM Million 2026