Resource · Checklist

Website launch checklist

Use it in the final two weeks, with one named owner per section. Unless an item says otherwise, tick it on a staging URL serving the production build.

Free, no sign-up. Updated .

Content

  • No dummy copy left: search the build for lorem and get zero results.
  • Names, prices, dates and company details checked against sources by someone other than the writer.
  • Each page has one h1 and no skipped heading levels (HeadingsMap).
  • Informative images have alt text describing them; decorative ones have alt="".
  • A made-up URL returns 404 (curl -I) and the custom 404 page, linking back into the site.
  • Crawl staging (Screaming Frog or Sitebulb): no two indexable pages share a <title> or meta description.
  • Canonicals point to each page's own production URL, not staging.
  • Production sends no noindex (meta tag or X-Robots-Tag header) and no password prompt.
  • Campaign landing pages carry noindex and stay out of the sitemap.
  • sitemap.xml lists only indexable canonical URLs, and robots.txt links to it.
  • robots.txt blocks no CSS, JavaScript or page you want crawled.
  • Structured data passes Google's Rich Results Test on each template using it.
  • LinkedIn's Post Inspector shows the right title and image for a page URL.

Speed

  • Lighthouse per template, mid-range Android profile: LCP (Largest Contentful Paint) ≤ 2.5 s and CLS (Cumulative Layout Shift) ≤ 0.1, the web.dev “good” thresholds.
  • With the Web Vitals extension on, the main interactions keep INP (Interaction to Next Paint) ≤ 200 ms.
  • Each <img> has width and height, and none downloads at over twice its displayed width (Network panel).
  • Fonts are subset, the body face preloaded, and the fallback metric-adjusted so the swap causes no visible shift.
  • The Performance panel shows LCP before WebGL and other heavy scripts load.
  • Responses are compressed (content-encoding: br or gzip), and hashed assets get a long cache-control.
  • Each third-party script has a named owner and a reason; remove the rest.

Accessibility

  • Tab through each template: every control is reachable, works with Enter or Space, and shows focus.
  • The first Tab shows a skip link to the main content.
  • axe DevTools reports no WCAG 2.2 AA contrast failures on any template.
  • Empty form submissions show errors beside the fields, announced by screen readers.
  • Screen reader pass done with VoiceOver (iOS) and NVDA (Windows).
  • At 200% zoom and a 320 px viewport, nothing is cut off or scrolls sideways.
  • With reduced motion on, animated pages pass the motion accessibility checklist.
  • Analytics loads only on production, office IPs filtered out.
  • Each tracked event (form sent, primary call to action, download) shows in the real-time report.
  • With consent declined, the Network panel shows no analytics or advertising requests.
  • Search Console verified for the production domain, sitemap submitted.

Forms

  • Each form submitted on production lands where it should (inbox, CRM or spreadsheet).
  • Notification emails reach the inbox, not spam, with SPF and DKIM passing.
  • After sending, visitors are told what happens next.
  • Spam protection is on, and a genuine test still gets through.

Redirects and domains

  • Each old URL with traffic or backlinks redirects (301 or 308) to its closest new page; test the map in a crawler's list mode.
  • No redirect takes more than one hop, and none loops.
  • http:// redirects to https://, and the non-preferred host (www or bare domain) to the preferred one.
  • The TLS certificate is valid and auto-renews.
  • DNS TTLs were lowered a day or more before the switch.
  • Privacy and cookie policies name the services in use, including whoever receives form data.
  • Company details, terms or an imprint published where your market requires.
  • Licences for fonts, images and any video, music or code are on file.

Launch day and after

  • On launch day, redirects, forms and analytics events re-tested on the live domain.
  • An uptime monitor checks the home page and form endpoint, alerting a named person.
  • JavaScript errors go to a reporting tool (Sentry or similar) someone reads.
  • Weekly for the first month: 404 log and Search Console's Pages report reviewed, missing redirects added.
  • Once Search Console has field data, its Core Web Vitals report checked against lab results.
  • A rollback to the previous deploy, or a backup restore, tried once.

For the speed items’ reasoning, read A performance budget for motion-heavy websites.

Want a second pair of eyes on it?

Start a project and we will tell you plainly where the risks are.