Manual launch QA and automated checks
A manual launch checklist or Launch Ready?
A hand-run launch checklist, a Lighthouse run on a few pages and developer spot checks cover what the person running them remembers to check, on the pages they open. Launch Ready runs the same automated checks across the pages it crawls on a staging or live site, on every launch, and produces a report the client can read. Keep a checklist for the items that need a person, such as submitting forms and approving content, and let the scan take over the repetitive, rule-checkable ones.
Last reviewed
Manual checklist and Launch Ready at a glance
| Question | Manual checklist | Launch Ready |
|---|---|---|
| What it is built for | A person checking a site against a list before go-live. Lighthouse is built to audit a page: give it a URL and it runs a series of audits for performance, accessibility, SEO and more. (Source: Lighthouse overview (Chrome for Developers)) | Automated pre-launch website QA for agencies: it crawls a staging or live site, applies fixed rules and produces a prioritised fix list and a readiness report. |
| How issues are found | People tick the list and open pages to spot-check them, so coverage depends on who runs it and which pages they open. Lighthouse audits each URL or user-flow step it is given; a run does not crawl the site. (Source: Lighthouse overview (Chrome for Developers), Lighthouse user flows (GoogleChrome/lighthouse docs)) | The scanner finds them. It crawls the site and applies the same rules on every scan, across technical reliability, SEO and indexability, analytics, placeholder content, form markup, performance, and accessibility and compliance signals. |
| Who uses it | The agency's own team: the developer who built the site, a project manager, or whoever owns the launch. | The agency's developer, technical lead or delivery manager, before the client sees the site. |
| What the client receives | Whatever the team writes up: a ticked spreadsheet, an email, or a Lighthouse report for each audited page. (Source: Lighthouse overview (Chrome for Developers)) | A readiness report the client can read, as a share link or PDF: findings with evidence, what ran clean and what was not measured. The Agency plan adds your logo, colours and a client portal. |
| Where it fits in the delivery week | When someone has time, usually close to launch. Lighthouse runs in Chrome DevTools, from the command line, as a Node module or through PageSpeed Insights. (Source: Lighthouse overview (Chrome for Developers)) | Before the client review: scan staging, fix, scan again. Then once more before go-live, and the report goes out with the handoff. |
Choose a manual checklist and Lighthouse when…
- Forms have to be submitted and the message confirmed in the right inbox or CRM.
- Checkout, payment or a logged-in area has to be tested from start to finish.
- Copy, legal text or design needs the client's sign-off, or the site has to be reviewed by eye on real phones, tablets and browsers.
- Launch-day steps, such as the DNS switch and the redirect map from the old site, need someone to carry them out.
- You need detailed lab diagnostics for one page. A Lighthouse report scores the page, and each audit links to why it matters and how to fix it. (Source: Lighthouse overview (Chrome for Developers))
- You want to test a page under predefined network and device conditions, for example to debug performance. (Source: About PageSpeed Insights, Lab and field data differences (web.dev))
- You want to measure a multi-step interaction with a scripted Lighthouse user flow. The default mode analyses a single page load and lists form submissions as outside its scope. (Source: Lighthouse user flows (GoogleChrome/lighthouse docs))
Choose Launch Ready when…
- The same checks should run on every launch, not only the ones someone remembers on the day.
- The repetitive checks should cover each crawled page, not only the pages someone opened: noindex tags, broken links, titles, placeholder text, tracking tags and form markup.
- You want a record of what was checked, what was found and what was not measured, to send the client with the handoff.
- You want to scan again after the fixes instead of repeating the list by hand.
How we scan · See an example report · Agency website QA guide · Website launch checklist
Using both
Start from our free website launch checklist. Each of its 72 items is marked Scan check, Partly checked or Manual.
Run Launch Ready on staging for the Scan check items, fix what it reports and scan again. Then work through the Partly checked and Manual items by hand. A checklist is still needed for these: the scan reads form markup but does not submit a form, and it does not judge whether the copy is approved or the design looks right on a phone.
Keep Lighthouse for page-level diagnostics. Launch Ready runs Lighthouse on the homepage and a small sample of other pages, on plans that include Lighthouse, not on every page, so run Lighthouse yourself on other key pages when performance matters. (Source: Lighthouse overview (Chrome for Developers))
What Launch Ready does not do
- It replaces the repetitive, rule-checkable part of a launch checklist, not the part that needs a person.
- It does not guarantee a bug-free website.
- It does not submit forms or run functional tests. Form checks read the form markup; they do not confirm that a message arrives.
- It is not a full accessibility audit, legal review or security test. Its accessibility and compliance checks are automated signals.
- Evidence on a finding is the affected URL and what the rule found. The report shows one homepage screenshot, not a screenshot for each finding.
- It does not make the launch decision. People make it, with the report in hand.
Sources
Statements about Lighthouse come from these official pages. Features and plans change; check the current page before you decide.
Scan your next client site before the review
Add the staging or live URL, read the fix list, and send the client a report when it is ready.