WEBSITESfor Normal People2026

Part III: Before You Go Live (now the domain)10

Chapter 10Launch

Going live on your domain

2 min read, 2 cheat sheets

Finish line's right there.

Up to now your site has lived on a free Cloudflare address, something like your-site.your-name.workers.dev. That's your staging site. Show it to people, get feedback, change things. When you're happy, put it on the real domain.

The launch prompt

PromptCheat sheet 0138 lines
Launch this site on [DOMAIN] using the deployment route already validated
on staging and recorded in this project's CLAUDE.md.

For the default cf route, use the pinned cf version and reviewed
cloudflare.config.ts. If I approved a framework deployment exception in
Path B, keep its recorded build, dry-run and deployment commands and
configuration. Do not run cf init, cf dev, cf build or cf deploy against
that unmigrated project, or migrate it without separate approval.

Keep cf for account tasks, inspecting command help/schema rather than
guessing API fields. Keep the workers.dev address working as a separate
staging Worker.

1. Attach [DOMAIN] and www.[DOMAIN] to the production Worker as custom domains.
   Pick one as the main address ([DOMAIN] without www, unless I say otherwise)
   and redirect the other to it.
2. Make sure HTTPS is forced everywhere.
3. Then run a full launch check on the live domain and fix anything that fails:
   - Every page loads, no broken links, no 404s from the navigation or footer
   - Every page has a unique title and meta description, one H1, and a
     proper Open Graph image for link previews
   - sitemap.xml and robots.txt are correct for the live domain, and staging is
     set to noindex so Google doesn't index it twice
   - Favicon and app icons exist
   - Images are properly sized and lazy loaded
   - Mobile layout works at 375px wide, no horizontal scrolling
   - Keyboard navigation and colour contrast pass basic accessibility checks
   - Lighthouse scores for performance, accessibility, best practices and SEO,
     on mobile. Fix anything under 90.
   - Contact form sends, email arrives, spam protection works
   - Analytics fires on the live domain: test consent acceptance, rejection,
     footer opt-out and GPC, trigger the form event, and verify receipt
     in GA4. Staging must still send no production analytics
   - Structured data (schema.org LocalBusiness or Organization) with my real
     business name, address, phone and hours: [DETAILS]
4. If Search Console is set up, submit the live sitemap.

Report what you fixed and the final Lighthouse scores.
Watch itThe launch prompt, then the live domain.

Personal details are covered or swapped for examples. Press play, it's silent and loops.

If your domain's DNS isn't on Cloudflare yet

Your registrar may need you to sign in and change nameservers. Go back to chapter 7, change the nameservers to the two the agent gave you, and ask the agent to tell you when the domain is Active. Then run the prompt.

Moving from an old site

If you're replacing a site that's been around a while, it has pages Google already knows about. Kill those URLs without redirects and you throw away whatever search ranking they had.

Add this to the launch prompt:

PromptCheat sheet 024 lines
Before launching, this domain currently hosts my old site. Crawl it (and its
sitemap if it has one), list every URL, and set up 301 redirects from each old
URL to the closest matching page on the new site. Nothing that used to exist
should 404.

On a phone, swipe left and right to turn pages.