claude skills / Claude Code Web Skills / prelaunch-checks / en français

Prelaunch checks.

Launch day always breaks the same things. We look for them before, with evidence.

See what it produces
  • Claude Code
  • Playwright
  • Lighthouse
  • axe
  • Google Search Console
  • Bing Webmaster Tools
3possible verdicts: go, go with conditions, no-go
1failed blocker is enough for a no-go verdict
2passes: on staging, then on the real domain right after launch

orders of magnitude, depending on your volume

the problem

What gets in the way today.

  • 01The site goes live with the staging noindex still on and drops out of Google within days.
  • 02Old addresses return a 404 error, and years of links and traffic go with them.
  • 03The contact form sends requests to the developer's inbox, not yours.

input, output

You give this. You get this.

What you give Claude: the staging site, the domain, the pages, the old URLs and the launch plan

Site: Brightwater Physio, redesign with URL changes (WordPress to Next.js)
Preview: preview.example.com | Production: www.example.com
Pages: 9 templates, 22 top pages
Old URLs: 186, from the old sitemap and Search Console
Forms: booking request (must reach the clinic inbox), calendar booking
Legal: EU, consent required before analytics
Launch: 20 November, 14:00, the developer deploys

$ claude "Run the prelaunch checks on preview.example.com and tell me if we can go live tomorrow."

Prelaunch check, report extractexample

Prelaunch check: Brightwater Physio (preview.example.com to www.example.com)

Launch type: redesign with URL changes | Pages: 9 templates, 22 top pages | Date: 2026-11-19 | Browser: Chromium through Playwright

VERDICT: NO-GO

Two blockers fail: the booking form sends test data to a developer's inbox, and 11 old service URLs return 404. Both are fixable in a day. Re-run the blocker checks, then launch.

BLOCKERS

B1 Production robots.txt | PASS | allows all, sitemap line points to www

B3 Canonicals | FAIL, fixed during check | blog template pointed to preview.example.com

B4 Forms | FAIL | booking request arrives at a developer's address (test entry "TEST launch check 1")

B6 Old URLs | FAIL | 186 tested, 171 pass, 11 return 404, 4 redirect to the home page

B9 Consent and analytics | PASS | refusing consent blocks analytics requests

B10 Secrets | PASS | only the public analytics ID found in the client bundle

MAJOR

1 Display | at 390 px the cookie banner covers "Book now" on first visit

2 Accessibility | treatment filter chips not reachable with the keyboard

4 Performance | home LCP 3.8 s on mobile, hero photo 1.9 MB

LAUNCH DAY

1. Fix B4 and B6, re-run the blocker checks. Developer, 20 Nov morning.

2. Clinic manager approves the launch in writing.

3. Domain switch at 14:00, a quiet time for bookings.

4. Within one hour: redirect file on production, one real booking, analytics real-time, robots.txt and sitemap.

5. Rollback: point the domain back to the old host, about 5 minutes with a low TTL set the day before.

NOT CHECKED

Screen reader pass, field Core Web Vitals (about 28 days after launch).

the method

What Claude does, in order.

  1. step 1Run the blockers

    robots.txt, noindex, canonicals, forms end to end, old URLs, HTTPS, legal pages, consent, keys in the code, 404 page: any failure is flagged right away.

  2. step 2Display and accessibility

    Every template at 1440, 768 and 390 pixels with screenshots, an automated scan, then keyboard navigation, focus, contrast and alt text checked by hand.

  3. step 3Speed and redirects

    Mobile Lighthouse on every template, compared with the old site. Every old URL is requested, with its final status and destination recorded.

  4. step 4Verdict and launch day

    Go, go with conditions or no-go, then the launch sequence, the rollback plan and the checks to repeat on the real domain within the first hour.

demo in French / click, try it

Your turn.

An interactive demo of the skill. It is in French, the pack works in any language: ask Claude to answer in English.

2 blockers, NO-GO

constat

The test request "TEST launch check 1" arrives in a developer's inbox, not the clinic's.

correction

Set the recipient variable on the production environment, submit a new test, confirm arrival.

the film / 44 seconds, with sound

The pack film.

the pack film

In 8 seconds.

the guardrails

What the skill never does.

  • Everything is checked in a real browser, not by reading the code. Anything that could not run is listed as such.
  • Evidence for every result: a screenshot, a status code, a measured value or a test submission ID.
  • One failed blocker means a no-go verdict, whatever happens elsewhere.
  • Test data only, and no deployment or DNS change without your approval.

Questions

Does the skill check every page of a large site?

It checks every template and the pages that matter most for traffic and revenue, and it says so clearly in the report.

How is it different from the landing-page-builder skill?

The builder checks the page it has just built. Prelaunch checks reviews a whole site before a launch, a redesign or a migration, old URLs included.

What happens after go-live?

Within the first hour, the critical checks are repeated on the real domain. Then the sitemap is submitted and errors are monitored for two weeks.

What if no browser is available?

Claude does not pretend. The visual and interaction checks move to the "Not checked" section, with the reason.

the pack

In the pack: Claude Code Web Skills.