Website launch QA automation for every go-live
Launches go wrong in predictable ways: old URLs without redirects, noindex left on, forms that do not send, contrast failures, a missing SSL redirect. We build a launch QA workflow that runs these checks on staging and again on the live site, compares the old sitemap with the new redirects, runs Lighthouse and axe accessibility checks and produces a report for the developer to sign off. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.
The problem
Why website launches still miss items on the checklist
Most web agencies have a launch checklist, and most launches still miss something on it, because it is run by hand at the end of a long project. The classic losses are redirects from the old site and a leftover noindex tag, which can quietly undo years of search traffic.
Accessibility is growing in importance and harder to check by hand. Automated engines such as axe-core find on average 57% of WCAG issues, which makes them a strong first pass, but people must still test keyboard use, screen readers and content clarity.
What we build
What our website launch QA automation includes
Old-to-new redirect check
Every URL from the old sitemap and top landing pages tested against the new site for a working redirect.
Indexing and meta checks
Noindex, canonical, robots.txt, titles, descriptions and Open Graph tags checked page by page.
Lighthouse on key templates
Lighthouse CI runs on the main templates with thresholds you set, on staging and live.
Automated accessibility pass
axe-core checks on every template, with results grouped for a person to verify.
Forms, SSL and security headers
Test submissions on every form, HTTPS redirects, certificate validity and headers.
Sign-off report
One report per launch with pass, fail and manual-check items for the developer to sign.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
QA triggered
The project manager marks the site ready, or a deploy to staging triggers the run.
-
02
Automated
Checks run
Redirects, meta, Lighthouse, accessibility, forms and SSL are checked.
-
03
Automated
Report built
Results are grouped into pass, fail and manual checks with links to each issue.
-
04
Project manager review
Developer fixes
Developers fix failures and complete the manual accessibility checks.
-
05
Project lead or agency owner decides
Launch decision
A developer approves the launch; the project lead confirms with the client.
How it behaves
How launch QA behaves
What the client sees
- A launch that keeps old links working
- A site that loads fast and works with a keyboard
- A QA report they can file
What developers see
- One report with pass, fail and manual items
- Links to each failing page and element
- The same checks on every launch
What the automation does
- Crawls staging and live sites
- Runs Lighthouse and axe-core
- Tests forms, redirects and SSL
Edge cases and fallbacks
- Old site already offline
- Old URLs are taken from Search Console exports or archives you provide.
- Staging behind a password
- The runner uses a test account or IP allowlist you set.
- Third-party widget fails accessibility
- Reported separately so the client can raise it with that vendor.
- Runner or CI outage
- The manual checklist remains as fallback and the run is repeated before go-live.
Architecture
Pre-launch QA for a website at a glance.
- Input
- Logic and services
- Output
- People
How it flows
- 1 The old sitemap and the staging site are given to the QA runner.
- 2 Redirects, meta tags, forms, SSL and headers are checked across all pages.
- 3 Lighthouse and axe-core run on key templates and results are grouped into a report.
- 4 Developers fix failures, complete manual checks and approve the launch.
Project planner
How the project runs, phase by phase.
Pre-launch QA, accessibility & migration checks project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Current launch checklist, hosting and deploy process, thresholds and report format.
-
02
Design
2 to 3 days
Check list per site type, thresholds, manual items and sign-off flow.
-
03
Build
1 to 2 weeks
Redirect mapper, crawlers, Lighthouse CI, axe runs, form tests and report.
-
04
Pilot launch
About 1 week
Run on a real launch beside your manual checklist and compare.
-
05
Launch
1 to 2 days
Make it part of every launch and train developers on the report.
-
06
Support
Ongoing
New checks as standards and browsers change.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Checklist, thresholds and report format.
$200 – $400
-
Build
Redirect mapper, crawls, Lighthouse CI, axe and form tests.
$550 – $1,350
-
Integrations
CI, hosting and Slack.
$150 – $400
-
Testing and pilot launch
Real launch beside the manual checklist.
$50 – $200
-
Launch and training
Developer walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CI minutes, hosting and n8n are billed to you directly. Manual accessibility audits are quoted separately if you need them.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- CI minutes: Your CI provider's plan; checks run in minutes per launch.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: ADA web rule for public bodies
The Department of Justice rule sets WCAG 2.1 Level AA for state and local government web content, with compliance dates of April 26, 2027 for entities of 50,000 or more people and April 26, 2028 for smaller ones.
Source: www.ada.govEU: European Accessibility Act scope
The European Accessibility Act covers services including e-commerce and banking, so client shops selling in the EU need accessible sites.
Source: commission.europa.euAutomated checks are a first pass
axe-core finds on average 57% of WCAG issues automatically, so the report always includes manual checks for a person.
Source: github.comFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Pre-launch QA, accessibility & migration checks questions, answered.
Automated checks that run before and after launch: links, redirects, meta tags, speed, accessibility, forms and SSL, collected into one report. Developers still fix issues and approve the launch.
Yes. The redirect check compares the old sitemap and top landing pages with the new site, which is the part of a website migration SEO checklist that loses the most traffic when missed.
axe-core for the automated pass and Lighthouse for a quick score, followed by manual checks for keyboard, screen reader and content clarity. Automated tools find only part of the issues.
Yes. Lighthouse CI and the checks can run in GitHub Actions or your CI on each deploy to staging, so regressions show up before launch day.
No. Passing automated checks is a strong start, not a compliance certificate. Legal compliance depends on the site and jurisdiction, and you confirm with your client's counsel where it matters.
Issues caught before launch, redirects missing at launch, post-launch hotfixes and Search Console errors in the first weeks.
Free 20-minute call
Want this for your web developer?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for web developers
All servicesCRM automation for web design agencies: enquiry to proposal
Capture every website enquiry in one CRM pipeline, turn vague requests into a structured brief with a quick audit of the current site, track proposals and hand signed projects straight to delivery.
From $1,000 · About 4 weeks Details
Website content collection & client chasing
Collect copy, images, bios, product data and logins against the approved sitemap, with scheduled, friendly reminders and a clear view of what is blocking the build.
From $1,000 · About 3 to 4 weeks Details
Staging feedback & change request workflow
Gather staging feedback from Marker.io, BugHerd, email and chat into one list, sort bugs from content edits and new requests, and draft change requests for anything outside scope.
From $1,000 · About 3 to 4 weeks Details