Launch walkthrough 1
Walkthrough: a staging site scanned, fixed and rescanned before launch
We scanned a two-page synthetic staging site with Launch Ready's staging rules. The first scan reported 1 Block Launch, 1 Important and 18 Improvement findings, and the verdict was “Critical blocker detected” with a score of 35: a contact form posting to localhost blocked the launch and lorem ipsum sat on the homepage. After fixing the form and the copy, the staging rescan reported 18 Improvement findings and “Ready with warnings” with a score of 91. Scanned as a production site, the same fixed copy was “Critical blocker detected” with a score of 35 again, because its staging noindex tag became a Block Launch finding; with the tag removed the verdict was “Ready with warnings” with a score of 92.
Last reviewed
This is a demonstration on a synthetic site, not a client launch. The site, the bakery and its copy are made up for testing; no customer, client site or customer data is involved.
Scans run on on a local copy of Launch Ready (commit 017a24d), not on the hosted service. Every finding, count, score, verdict and line of output below comes from those runs, saved in the evidence file launch-walkthrough-1-2026-11.json.
The setup
The site is a two-page static bakery website written for testing Launch Ready: a homepage and a contact page with an order form. Three launch mistakes were planted in it on purpose: a noindex robots meta tag on the homepage, a paragraph of lorem ipsum, and a contact form whose action still points at http://localhost:3000.
We served it over HTTPS at https://localhost:4443/ on the same machine, signed up a new account on the local app, added the site as a project with the environment set to staging, and started each scan with the same request the app sends when you start a scan. The workspace was on the Free plan. In a staging scan, a noindex tag is expected and reported as an Improvement, not a blocker.
How this local run differs from a scan on the hosted service:
- LAUNCHGUARD_DISABLE_RENDER=1: pages were read as HTTP HTML; Chromium did not render them, as it does by default. The fixture is static HTML, so the markup the rules read is the same, but the analytics rule grades by rendering: a missing analytics tag is an Improvement on an unrendered page, and Important on a rendered page in a production scan. With rendering on, the two production scans would also have reported no_analytics as Important.
- LAUNCHGUARD_DISABLE_LIGHTHOUSE=1: performance was not measured. Free scans do not measure performance either.
- LAUNCHGUARD_ALLOW_HOSTS=127.0.0.1,localhost: a development allowlist that lets the scanner reach loopback. Hosted Launch Ready refuses localhost and IP addresses.
- The fixture was served at https://localhost:4443/ over HTTPS with a certificate from a local test CA, trusted by the app, the worker and the script through NODE_EXTRA_CA_CERTS.
Before: the first staging scan
- Scan
- Staging scan,
- Readiness
- Critical blocker detected, score 35 out of 100
- Findings
- 1 Block Launch, 1 Important and 18 Improvement findings; 12 checks passed
- Coverage
- 2 of 2 discovered pages checked (page limit 25)
Two findings stood above the rest. The order form posting to localhost was the only Block Launch finding, and the lorem ipsum paragraph on the homepage was Important. The planted noindex tag appeared among the Improvements as noindex_page, because this was a staging scan.
| Severity | Rule and finding | Page | Evidence in the report |
|---|---|---|---|
| Block Launch (critical) | form_action_localhostForm submits to localhost | /contact.html | action="http://localhost:3000/api/contact" |
| Important (high) | lorem_ipsumLorem ipsum placeholder copy | / | …atches before the shop opens. Our story Lorem ipsum dolor sit amet, consectetur adipiscing elit,… |
Improvement findings in the same scan (18)
| Severity | Rule and finding | Page | Evidence in the report |
|---|---|---|---|
| Improvement (medium) | missing_hstsBrowsers are not told to stay on HTTPS (HSTS) | / | No Strict-Transport-Security header on the homepage response. |
| Improvement (medium) | missing_canonicalMissing canonical URL | / | No rel=canonical. |
| Improvement (medium) | missing_canonicalMissing canonical URL | /contact.html | No rel=canonical. |
| Improvement (medium) | missing_ogMissing link-preview metadata (Open Graph) | /contact.html | No og:title / og:description. |
| Improvement (medium) | missing_ogMissing link-preview metadata (Open Graph) | / | No og:title / og:description. |
| Improvement (medium) | missing_twitterMissing X (Twitter) card metadata | /contact.html | No twitter:card / twitter:title. |
| Improvement (medium) | missing_twitterMissing X (Twitter) card metadata | / | No twitter:card / twitter:title. |
| Improvement (medium) | no_analyticsNo analytics detected | / | No known analytics snippets in HTTP HTML (Chromium did not run). |
| Improvement (medium) | missing_llms_txtNo llms.txt file for AI assistants | /llms.txt | /llms.txt answered HTTP 404. |
| Improvement (medium) | missing_cspNo rules on which scripts and embeds may load (CSP) | / | No Content-Security-Policy header or meta tag on the homepage. |
| Improvement (medium) | missing_jsonldNo structured data on the homepage (JSON-LD) | / | No application/ld+json script on the homepage. |
| Improvement (medium) | missing_x_frame_optionsOther sites can show this site inside a frame (clickjacking) | / | No X-Frame-Options header and no frame-ancestors in a Content-Security-Policy header. |
| Improvement (medium) | noindex_pagePage is marked noindex | / | noindex, nofollow |
| Improvement (medium) | cookie_banner_missingPossible compliance issue: no cookie banner or policy detected | / | No cookie-policy copy and no known CMP snippet (OneTrust, Cookiebot, etc.). |
| Improvement (medium) | privacy_policy_missingPossible compliance issue: no privacy policy link found | / | No visible “privacy” link/copy on crawled pages. |
| Improvement (medium) | terms_missingPossible compliance issue: no terms link found | / | No visible terms/legal link. |
| Improvement (medium) | robots_txt_missingrobots.txt is missing | /robots.txt | HTTP 404 |
| Improvement (medium) | sitemap_missingSitemap is missing | /sitemap.xml | HTTP 404 |
Apart from the planted noindex, the Improvements come from how bare the fixture is: no robots.txt, sitemap or llms.txt, no canonical tags, link-preview metadata or structured data, no security headers, no privacy, cookie or terms links, and no analytics. They were not planted, and this walkthrough does not fix them.
What the report says about the planted mistakes
This is the report's own text for each planted mistake: the same title, “Why it matters” and “How to fix” a reader of the report sees.
Rule form_action_localhost
Form submits to localhost
Why it matters: The form action points at a local machine. Real visitors cannot submit it. This is a static markup check — Launch Ready did not send a test submission.
How to fix: Point the action at your production form handler or a live form service.
Rule lorem_ipsum
Lorem ipsum placeholder copy
Why it matters: Dummy Latin copy is still on the page. Clients and customers will notice immediately.
How to fix: Replace placeholder copy with the real launch content.
Rule noindex_page
Page is marked noindex
Why it matters: This page will not appear in search results. Confirm that is intentional.
How to fix: Remove noindex unless the page should stay out of search (thank-you pages, private tools).
Rule production_noindex
Production site is set to noindex
Why it matters: Search engines are told not to index this site. A globally noindexed production launch will not appear in Google.
How to fix: Remove noindex from production templates and HTTP headers before launch. Keep noindex on staging only.
What was fixed
In a copy of the site, the form action was pointed at the site's own handler, /api/contact, and the lorem ipsum paragraph was replaced with a real sentence. The noindex tag stayed, because staging is normally kept out of search. The copy was served at the same address, as a new staging deploy would be.
--- a/original/contact.html
+++ b/fixed/contact.html
@@ -17,12 +17,7 @@
<main>
<h1>Order a celebration loaf</h1>
<p>Tell us the date and the size you need. We reply within one working day.</p>
- <!--
- PLANTED MISTAKE 3: the form still posts to the developer's machine.
- Real visitors cannot submit it.
- Rule: form_action_localhost (critical, "Block Launch", in every environment).
- -->
- <form action="http://localhost:3000/api/contact" method="post">
+ <form action="/api/contact" method="post">
<label for="name">Your name</label>
<input id="name" name="name" type="text" required />
<label for="date">Collection date</label>
--- a/original/index.html
+++ b/fixed/index.html
@@ -24,11 +24,7 @@
<h1>Fresh bread every morning</h1>
<p>Example Bakery bakes sourdough, rye and seeded loaves in small batches before the shop opens.</p>
<h2>Our story</h2>
- <!--
- PLANTED MISTAKE 2: dummy Latin copy that nobody replaced.
- Rule: lorem_ipsum (high on the homepage).
- -->
- <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</p>
+ <p>Example Bakery started as a weekend market stall. The same two bakers still shape every loaf by hand.</p>
<h2>Visit us</h2>
<p>Open Tuesday to Saturday, 7:00 to 14:00. <a href="/contact.html">Send us a message</a> to order a celebration loaf.</p>
</main>After: the staging rescan
- Scan
- Staging scan,
- Readiness
- Ready with warnings, score 91 out of 100
- Findings
- 18 Improvement findings; 14 checks passed
- Coverage
- 2 of 2 discovered pages checked (page limit 25)
The rescan no longer reported form_action_localhost or lorem_ipsum. It reported no new findings, and the 18 Improvements from the first scan were still there, unchanged.
Findings in the staging rescan (18)
| Severity | Rule and finding | Page | Evidence in the report |
|---|---|---|---|
| Improvement (medium) | missing_hstsBrowsers are not told to stay on HTTPS (HSTS) | / | No Strict-Transport-Security header on the homepage response. |
| Improvement (medium) | missing_canonicalMissing canonical URL | / | No rel=canonical. |
| Improvement (medium) | missing_canonicalMissing canonical URL | /contact.html | No rel=canonical. |
| Improvement (medium) | missing_ogMissing link-preview metadata (Open Graph) | /contact.html | No og:title / og:description. |
| Improvement (medium) | missing_ogMissing link-preview metadata (Open Graph) | / | No og:title / og:description. |
| Improvement (medium) | missing_twitterMissing X (Twitter) card metadata | /contact.html | No twitter:card / twitter:title. |
| Improvement (medium) | missing_twitterMissing X (Twitter) card metadata | / | No twitter:card / twitter:title. |
| Improvement (medium) | no_analyticsNo analytics detected | / | No known analytics snippets in HTTP HTML (Chromium did not run). |
| Improvement (medium) | missing_llms_txtNo llms.txt file for AI assistants | /llms.txt | /llms.txt answered HTTP 404. |
| Improvement (medium) | missing_cspNo rules on which scripts and embeds may load (CSP) | / | No Content-Security-Policy header or meta tag on the homepage. |
| Improvement (medium) | missing_jsonldNo structured data on the homepage (JSON-LD) | / | No application/ld+json script on the homepage. |
| Improvement (medium) | missing_x_frame_optionsOther sites can show this site inside a frame (clickjacking) | / | No X-Frame-Options header and no frame-ancestors in a Content-Security-Policy header. |
| Improvement (medium) | noindex_pagePage is marked noindex | / | noindex, nofollow |
| Improvement (medium) | cookie_banner_missingPossible compliance issue: no cookie banner or policy detected | / | No cookie-policy copy and no known CMP snippet (OneTrust, Cookiebot, etc.). |
| Improvement (medium) | privacy_policy_missingPossible compliance issue: no privacy policy link found | / | No visible “privacy” link/copy on crawled pages. |
| Improvement (medium) | terms_missingPossible compliance issue: no terms link found | / | No visible terms/legal link. |
| Improvement (medium) | robots_txt_missingrobots.txt is missing | /robots.txt | HTTP 404 |
| Improvement (medium) | sitemap_missingSitemap is missing | /sitemap.xml | HTTP 404 |
The same copy scanned as production
A staging verdict says nothing about the live site's settings. To show what happens at launch, we changed the project's environment to production and scanned the same fixed copy again, with the staging noindex tag still in place.
- Scan
- Production scan,
- Readiness
- Critical blocker detected, score 35 out of 100
- Findings
- 1 Block Launch and 17 Improvement findings; 14 checks passed
- Coverage
- 2 of 2 discovered pages checked (page limit 25)
| Severity | Rule and finding | Page | Evidence in the report |
|---|---|---|---|
| Block Launch (critical) | production_noindexProduction site is set to noindex | / | Homepage has noindex (meta robots or X-Robots-Tag). |
In production the tag became production_noindex, a Block Launch finding, and noindex_page no longer appeared. We then removed the tag and ran one more production scan.
--- a/fixed/index.html
+++ b/launch/index.html
@@ -5,12 +5,6 @@
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Example Bakery: fresh bread every morning</title>
<meta name="description" content="A synthetic bakery website used to test a pre-launch scan. Not a real business." />
- <!--
- PLANTED MISTAKE 1: the homepage tells search engines not to index it.
- Normal on staging, a launch blocker if it reaches production.
- Rules: production_noindex (production scan), noindex_page (staging or preview scan).
- -->
- <meta name="robots" content="noindex, nofollow" />
</head>
<body>
<header>- Scan
- Production scan,
- Readiness
- Ready with warnings, score 92 out of 100
- Findings
- 17 Improvement findings; 14 checks passed
- Coverage
- 2 of 2 discovered pages checked (page limit 25)
The last scan no longer reported production_noindex. The verdict was Ready with warnings, with 17 Improvement findings still open.
Read this last verdict with the rendering caveat from the setup. Pages were not rendered in this local run, so the missing analytics tag stayed an Improvement. With rendering on, as on the hosted service, a production scan grades a missing analytics tag on a rendered homepage as Important, so this copy would not have reached “Ready with warnings” there without an analytics tag.
Findings still open in the last production scan (17)
| Severity | Rule and finding | Page | Evidence in the report |
|---|---|---|---|
| Improvement (medium) | missing_hstsBrowsers are not told to stay on HTTPS (HSTS) | / | No Strict-Transport-Security header on the homepage response. |
| Improvement (medium) | missing_canonicalMissing canonical URL | / | No rel=canonical. |
| Improvement (medium) | missing_canonicalMissing canonical URL | /contact.html | No rel=canonical. |
| Improvement (medium) | missing_ogMissing link-preview metadata (Open Graph) | /contact.html | No og:title / og:description. |
| Improvement (medium) | missing_ogMissing link-preview metadata (Open Graph) | / | No og:title / og:description. |
| Improvement (medium) | missing_twitterMissing X (Twitter) card metadata | /contact.html | No twitter:card / twitter:title. |
| Improvement (medium) | missing_twitterMissing X (Twitter) card metadata | / | No twitter:card / twitter:title. |
| Improvement (medium) | no_analyticsNo analytics detected | / | No known analytics snippets in HTTP HTML (Chromium did not run). |
| Improvement (medium) | missing_llms_txtNo llms.txt file for AI assistants | /llms.txt | /llms.txt answered HTTP 404. |
| Improvement (medium) | missing_cspNo rules on which scripts and embeds may load (CSP) | / | No Content-Security-Policy header or meta tag on the homepage. |
| Improvement (medium) | missing_jsonldNo structured data on the homepage (JSON-LD) | / | No application/ld+json script on the homepage. |
| Improvement (medium) | missing_x_frame_optionsOther sites can show this site inside a frame (clickjacking) | / | No X-Frame-Options header and no frame-ancestors in a Content-Security-Policy header. |
| Improvement (medium) | cookie_banner_missingPossible compliance issue: no cookie banner or policy detected | / | No cookie-policy copy and no known CMP snippet (OneTrust, Cookiebot, etc.). |
| Improvement (medium) | privacy_policy_missingPossible compliance issue: no privacy policy link found | / | No visible “privacy” link/copy on crawled pages. |
| Improvement (medium) | terms_missingPossible compliance issue: no terms link found | / | No visible terms/legal link. |
| Improvement (medium) | robots_txt_missingrobots.txt is missing | /robots.txt | HTTP 404 |
| Improvement (medium) | sitemap_missingSitemap is missing | /sitemap.xml | HTTP 404 |
What the scans did not check
- The contact form was read, not submitted. The scan saw where its action pointed; whether /api/contact accepts a message and delivers it was not tested.
- No user journeys were run: nothing was clicked through, filled in or bought.
- This is not an accessibility audit, a security test or a legal review. The privacy, cookie and terms findings say a link or banner was not found; whether the site needs them, and what they must say, is for the people responsible.
- Each scan checked the 2 pages its crawl discovered. JavaScript rendering was off in this local run and performance was not measured.
- Launch Ready does not guarantee a bug-free website.
- It does not make the launch decision. People make it, with the report in hand.
How we scan describes what the crawler fetches, renders and stores.
What still needs a person
- Submit the contact form on the live site and confirm the message arrives where the client expects it.
- Decide what to do about the 17 Improvement findings still open in the last scan, including the robots.txt, sitemap, privacy, cookie and terms findings.
- Rescan the production address once DNS points at it, so the verdict is about the live site.
- Make the launch decision with the report in hand. “Ready with warnings” is the scan's verdict, not an approval.
There is no client and no launch in this demonstration, so nobody approved anything. On a real project, this is where the person responsible reviews the last report and records the decision.
How to reproduce it
- Deploy a small site with the three mistakes above to a public staging address. The changes shown on this page are the exact lines involved.
- Add it to Launch Ready as a staging project and run a scan. Fix the form and the copy, then rescan.
- Switch the project to production, or scan the live address, to see how noindex is treated after launch.
The deployment checks guide covers scanning staging before a production promotion. The website launch checklist lists what to check by hand. The planted mistakes each have a page in the launch mistakes library:
- A form still posting to staging: The form's action still points at a staging or local address, so the first enquiries go nowhere useful.
- Placeholder text on a live site: Lorem ipsum, “coming soon” sections or test labels that were meant to be replaced before launch.
- A noindex tag left on: The live site tells search engines not to index it, usually because a staging setting came along.
Check your next client site before handoff
Add the staging or live URL, read the fix list, and send the client a report when it is ready.