Website · THE NO-PANIC PLAN
Launch a new website with a verifiable checklist
A launch checklist is useful when each item points to a real route, owner and verification result. This workflow combines user-facing QA with crawlability and sitemap preparation, while keeping robots.txt separate from privacy and access control. Nirmion Robots.txt Generator and Sitemap Generator help prepare specific files from URLs and paths you supply; they do not inspect the deployed site or guarantee that a search engine will index a page.
MISSION Coordinate a website release by checking essential user journeys, accessibility, crawler rules, canonical sitemap URLs, production cutover and post-launch monitoring.
Prepare the launch checklistTHE REAL-WORLD BIT
What happens outside this browser tab?
Define the production boundary and rollback owner; test critical journeys, accessibility and performance; review crawler access rules; generate a sitemap from only canonical public pages; then cut over and verify real routes, redirects, errors and search-console status.
YOUR CHECKLIST, WITH FEWER DRAMATIC SIGHES
One step at a time.
Follow the order below. If a step names a Nirmion tool, its link is right there with it.
- 01
Set the launch boundary and protect the rollback path
Name the production hostname, launch owner, release window, critical user tasks and a person authorized to roll back. Confirm the production build is the one reviewed on staging, staging and private preview pages cannot be crawled or accessed by the public, and a tested backup or prior deployment can be restored. Keep a route list of pages that should be public, canonical and indexable, plus any intentionally private or retired paths. Do not rely on robots.txt as access control. Agree how the team will monitor errors after cutover and who can pause the launch if checkout, sign-in, contact or other essential flows fail. This plan makes launch decisions observable rather than treating a successful deploy command as proof the site is ready. (Source 1)
- 02
Review real pages for usability, accessibility and performance
Test representative templates and critical journeys on mobile and desktop, using keyboard-only navigation and a screen reader where available. Check headings, labels, focus order, contrast, image text alternatives, form errors, confirmation messages, links, 404 behavior and language. Submit test data through each important form and confirm the expected destination without exposing real customer information. Measure page experience with both controlled checks and, after launch, field data; web.dev describes loading, interactivity and visual stability as separate dimensions, so one fast lab score is not the whole review. Use W3C's WCAG 2.2 Quick Reference to select relevant success criteria and techniques, while avoiding a claim of conformance from a checklist alone. Fix blockers or record an owner and accepted launch decision for each remaining issue. (Sources 3, 4)
- 03
Set crawler rules without confusing crawling and privacy
Decide which public paths search crawlers may request and which should stay out of the public site. Nirmion Robots.txt Generator (tool 283) can build crawler directives from reviewed paths and an optional same-origin sitemap reference; compare the output with the actual production routes before deploying it. Google states that robots.txt is not a way to hide a page from search or protect private information, and blocked URLs may still be indexed if linked elsewhere. Use authentication or an appropriate noindex mechanism for private or excluded pages, and ensure CSS, JavaScript and other resources needed to render public pages are not accidentally blocked. Check that the production file is reachable at the site's root and that staging restrictions will not be copied onto production. (Source 1)
- 04
Create a sitemap from canonical pages that should be discoverable
Build the final list from production-ready pages that return successfully, have a self-consistent canonical URL and are intended for search discovery. Exclude staging links, redirects, duplicate parameter variants, noindex pages, error pages and private routes. Nirmion Sitemap Generator (tool 284) creates XML from up to 500 supplied same-origin URLs; it does not crawl the website, so you must supply and review the list. Confirm absolute URLs use the correct HTTPS host and match canonical tags, then publish the sitemap at an appropriate location and submit it through Google Search Console if Google discovery is desired. Google explains that sitemap submission can help discovery but does not guarantee indexing or a ranking. Large sites should use their CMS or sitemap index rather than truncating a list to the tool limit. (Source 2)
- 05
Cut over, verify key routes and watch the first real traffic
After DNS or hosting cutover, open the production site from a clean browser session and verify HTTPS, certificate validity, canonical host redirects, representative page loads, forms, authentication boundaries, robots.txt and sitemap. Check that old URLs either resolve to the intended new page or return the correct status, and that no staging or private content became public. Review deployment logs, analytics, Search Console sitemap status and field performance after real users arrive; web.dev notes that field experience and lab measurements differ. Keep the rollback option available until critical journeys and error rates are acceptable, and assign owners to unresolved accessibility, content or performance issues. Re-run the route and crawler checks after significant changes, because launch verification describes the observed build and date rather than a permanent guarantee. (Sources 1, 2, 3, 4)
THE HELPER CREW
Tools for the fiddly bits.
These are the currently published Nirmion tools matched to this guide. Open a tool page for its accepted inputs and limits.
RECEIPTS, PLEASE
Sources & review notes
Each source is linked to the steps it supports. Open it to check its scope and current guidance.
Source checked 2026-10-08