What it does
It supports an explicit saved live baseline, a public staging URL, important URL mapping, saved check results, a launch decision, and a bounded post-launch review.
Pulse Hub add-on
Launch QA Add-on
Launch QA keeps a saved public-staging launch review in one place so an authorised workspace website operator can prepare for a relaunch and review saved results.
Where it appears
An authorised workspace website operator activates it in Pulse Hub, manages projects from the dedicated Launch QA page, and sees a compact saved project-status area in Website Detail.
Safe use
Opening Hub, Website Detail, this guide, or a project does not start a scan, queue a check, contact a provider, or change saved data. Baseline capture, project changes, and public checks are separate authorized actions.
Protected staging boundary
An authorised operator can choose approved Protected Basic Auth staging access without seeing or sharing a secret. A separate controlled browser-journey foundation remains unavailable until its dedicated secure browser egress is deployed. Other sign-in methods, forms, checkout or payment tests, Google services, and browser journeys are not included.
Saved results
After an authorised operator queues a public run, Launch QA can save clear results for page titles, descriptions, headings, canonical and robots settings, structured-data presence, public sitemap availability, HTTPS behaviour, and a bounded markup-only inventory of links, images, CTA labels, and forms. The inventory does not fetch, click, or submit those items. Across same-host images, stylesheet/script/favicon assets, and saved-approved normal link targets, no more than two supplemental safe checks run in total: images are considered first, then assets, then approved links. Button-only, external, unsupported, malformed, and unapproved targets remain not checked. Launch QA must remain entitled and active while work is queued or runs; if it is deactivated or unavailable, no public check is made. It records Passed, Failed, Warning, Partial, and Not checked honestly; unavailable or deferred checks are not presented as completed. A separately labelled existing saved Pulse evidence row may link a bounded relevant saved finding; it is not a new Launch QA check.
Client-safe visibility
Project controls stay restricted to authorised workspace website operators. A client can receive only an explicitly prepared safe summary through their authenticated workspace access when it was opted in; private staging details, raw evidence, and internal notes are not included. Anonymous or public sharing is not available.