Publish scope
Confirm which pages, languages, forms and work examples belong in the first live release.
Launch guide
What should be checked before a website goes live.
Launch work is not only making the page look finished. The site should be crawlable, fast, mobile-safe, form-safe and clear enough for the first real visitors.
Plan a launchLaunch handoff
A good launch leaves clear ownership behind.
Before the site is handed off, separate what is ready to publish, what needs follow-up and who owns the lead path after the site is live.
Lead path
Check who receives inquiries, what context is sent and what details should be handled after launch.
Measurement
Make sure key clicks, forms and thank-you paths can be checked after launch.
Next owner
Mark what remains to improve next: SEO, content, credibility, speed, or follow-up pages.
Page paths
Final URLs should be clean, predictable and linked from navigation, footer, sitemap, or relevant internal pages.
Search preview
Page titles, descriptions, social previews, language links and visible page copy should match what the page is actually about.
Mobile and speed
The opening section should load quickly, avoid layout shifts and keep buttons, forms and menus usable on small screens.
Forms and thank-you flow
Forms should submit to the right destination, include page context, block simple spam and redirect to a useful thank-you page.
Indexing files
Robots.txt, sitemap.xml, security.txt, humans.txt and llms.txt should be present when the site is ready for crawlers.
Post-launch check
After launch, verify the live domain, HTTPS, language paths, 404 page, form delivery and the most important search pages.
FAQ
Questions worth answering before the build.
Should launch wait for perfect design?
No. Launch should wait for a clear, working, trustworthy version. Visual polish can continue after the basics are stable.
What is the most urgent launch risk?
Broken forms, blocked indexing, bad mobile layout, missing HTTPS and pages that are not linked anywhere.
Can this guide be reused for every new page?
Yes. Each new service, city, resource, or offer page should pass the same basic launch checks.
What needs owner approval?
Production deploys, domain settings, analytics account access, billing, secrets and private inbox confirmations require owner approval or action.
Related resources
What comes next
Related pages that turn this into a plan.
Website review
Put the launch package back into a critical review path
Review vs launch guideSee whether diagnosis or final launch QA comes first
Brief vs launch guideSee whether direction or QA is the missing step before launch
Work examplesDecide which examples must appear before launch
Website briefClarify what is needed before launch is finalized
Trust checklistCheck which examples should be included
Approved project materialSend real screenshots, copy, results and permissions before a work example is published.
SitemapCheck link coverage before launch
Contact
Want to turn this into a site plan?
Send the business type, current site if there is one and deadline. We will reply with a clear direction.