Web
A launch check confirms that nothing which worked before has been lost: URLs resolve or redirect, content depth is preserved, tracking still fires, and the site is crawlable, accessible and fast on real devices.
In order
Every existing URL should have a decided destination: kept, redirected once to the closest equivalent, or deliberately retired. Check for chains and loops, and confirm that pages which earned search visibility have kept their content rather than being trimmed to fit a new template.
Fetch key templates as a crawler and confirm the main content is in the HTML, there is exactly one H1, structured data validates, canonicals are self-referencing, and no staging noindex or robots block survived. This is the single highest-value pre-launch pass.
Analytics loading on every template, conversion events firing on the real form rather than a test one, Search Console verified for the live property, and the previous data still available for comparison.
A staging noindex left in place, and analytics or conversion tracking that was never re-verified on the live site. Both are silent: the site looks correct while being invisible or unmeasurable.
Closely for two weeks, then weekly for a quarter. Indexing and ranking effects lag the change, so a problem introduced at launch often becomes visible well after everyone has moved on.
A launch check confirms that nothing which worked before has been lost: URLs resolve or redirect, content depth is preserved, tracking still fires, and the site is crawlable, accessible and fast on real devices.
You have read what we think. If you want to know what it means for your case specifically, describe it and we will tell you which parts of website launch checklist actually apply — and which do not.
