Pre-launch QA for web agencies
Agency website QA: a buyer's guide
Catch launch mistakes before your clients do. Launch Ready gives a small agency the same final check on every client launch: a scan of the staging or live site, a prioritized fix list with evidence, and a report you can hand to the client.
It works alongside your delivery stack. “Fix this” sends findings to your issue tracker or your AI coding tool, the GitHub Action can fail a build on a Block Launch finding, and your team still owns the fixes and the launch decision.
Last reviewed
A repeatable workflow for each client launch
1. Organize sites by client and launch
Keep each website as a project, associate it with a client, and use environment and tags to distinguish production, staging, and preview work.
2. Run QA at the agreed checkpoint
Start a scan before the release review, or let the pipeline do it: Pro and Agency can add a CI gate token and GitHub Action that scans one project and fails the build on a Block Launch finding. Scheduled daily or weekly scans are discrete runs, not uptime monitoring.
3. Triage blockers with evidence
Review readiness, severity, affected pages, and captured evidence. Start with critical launch risks, then check what was not measured before drawing conclusions.
4. Send the fixes where your team works
“Fix this” on one issue or a selection opens a pre-filled GitHub or Linear issue, gives Jira and Asana text to paste, or writes a prompt for your AI coding tool. Owners, due dates and status stay in your tracker. Short on hands? “We fix it” sends us the issues and the report link, and nothing changes on the site without your go-ahead.
5. Review exceptions and rescan
Pro and Agency include rule tuning to document an accepted exception or adjust a finding; scan again to see the current result. Keep the reason and client approval in your normal delivery record too.
6. Hand over a client-ready report
Share the findings, remaining blockers, exceptions, and unmeasured checks. Agency adds your logo and colours, a client portal login, and a monthly branded PDF per client.
Portfolio view
See which client site needs attention first
This preview uses the current portfolio heat-map component and its real readiness ordering. Every name is fictional: the first tile uses the AV-12 synthetic report, and the second is explicitly unscanned, with no invented score or findings.
Heat map
Worst first: 1 blocked.
- Pre-launch websiteFictional client35Blocked
- Next launchFictional client—Never scanned
The heat map is an Agency feature. This illustrative portfolio is not customer data or a claim that every plan includes the portfolio view.
Report evidence
Show the client what was found and what was not checked
The report below is a live rendering of the synthetic AV-12 fixture using the current scoring, finding, and badge components. It is fictional; no site was scanned, and no customer data or share link is used.
launch-ready-example.example
Critical blocker detectedScore and readiness are calculated from the fixture findings with the production scoring rules.
1 critical, 1 high, and 1 medium findings.
- Block Launch
Homepage returns noindex
<meta name="robots" content="noindex, nofollow">
- Important
Contact form submits to a staging URL
<form action="https://forms.staging.example/lead">
- Improvement
Images without alt text
4 image elements on this page have empty or missing alt attributes.
The full report shows page coverage, category coverage, Not measured states, exceptions, and plan requirements.
Open the full synthetic reportAlternatives
Replace fragmented review artifacts, not your whole delivery stack
Spreadsheets and screenshots are useful for human context and bespoke checks. They become harder to keep aligned across many sites and repeat scans. Launch Ready adds repeatable automated findings and coverage; your team still decides what to fix and where to track it.
| Approach | Useful for | Trade-off / boundary |
|---|---|---|
| Spreadsheet checklist | Client-specific manual checks, sign-off steps, and context outside automated scans. | The agency must keep status, evidence, and repeat checks consistent across sites. |
| Screenshot bundle | Visual context for a reviewer or a point-in-time design decision. | A still image is not a crawl, does not establish page coverage, and can lose the URL or review context when separated from the checklist. |
| Launch Ready | Repeatable scan findings, page-level evidence, coverage, client reports, and fix requests sent to your tracker or AI tool. | Automated checks can miss inaccessible or dynamic behavior; they do not submit forms or change your code. A build fails only where you add the GitHub Action to the pipeline. |
| Your issue tracker | Owners, implementation work, due dates, and delivery status. | Keep it as the source of truth. Fix this opens or creates the issue there; Launch Ready does not sync its status back. |
Plan fit
Match the plan to the agency workflow
This comparison reflects current code entitlements, not a verification of production overrides. In-app share links are available on every plan. API/MCP share-link creation and the deploy hook are Agency-only; a deploy hook starts a scan but does not judge its completed results or block a release. To fail a build on a Block Launch finding, use the CI gate token and GitHub Action on Pro or Agency.
| Capability | Free | Pro | Agency |
|---|---|---|---|
| In-app share links | Available | Available | Available |
| Report branding | Launch Ready branding | Neutral, unbranded report | Your agency logo and colours |
| Full scan categories | Core checks | Included | Included |
| Scheduled scans and monitoring | Not included | Daily or weekly scans; alerts depend on configured delivery | Daily or weekly scans; alerts depend on configured delivery |
| Portfolio heat map | Not included | Not included | Included |
| Fix this: AI prompt and tracker issue | Not included | GitHub, Linear, Jira, Asana and AI prompt | GitHub, Linear, Jira, Asana and AI prompt |
| “We fix it” request | Available | Available | Available |
| CI gate token and GitHub Action | Not included | One project per token | One project per token |
| Client portal login | Not included | Not included | Included |
| API/MCP scan and read access | Included | Included | Included |
| API/MCP share creation and deploy hook | Not included | Not included | Included |
Plan limits come from current code entitlements and may be configured differently in production. Check pricing for current commercial terms. API/MCP scan and read access is on every plan; Free scans are limited to one site. In-app sharing is available on every plan.
Limitations
What to keep in the client handover
- Coverage depends on reachable pages, scan limits, captured markup, and rendering; read the report's coverage and Not measured states.
- Static form checks do not submit forms or confirm that leads are delivered. Test important workflows manually.
- Automated accessibility and compliance signals are not specialist audits, legal advice, or proof of conformance.
- A scan informs the release decision; your team makes it. The GitHub Action fails a build only on Block Launch findings, and only where you add it.
- Use the tracker for owners, accepted client exceptions, and due dates. Issues created with Fix this do not sync their status back to the report.
- Confirm every finding against the client site and record what was manually reviewed before handover.
For implementation detail, see how we scan, the API reference, and pricing. Launch Ready is a QA aid; the agency remains responsible for technical fixes, client approval, and release decisions.