A website launch checklist should verify production URLs, indexability, redirects, metadata, forms, analytics, accessibility, performance, ownership and rollback before promotion.

Treat launch as a controlled production change. Verify the real domain and integrations, preserve important old paths and assign people to monitor forms, indexing and errors after release.

The two failures that actually happen

Launch problems are rarely exotic. Almost all of them fall into two categories: a temporary setting left in place, and something that was only ever tested on a preview URL. Both are invisible from the browser and both are entirely preventable by checking on the real domain before announcing anything.

  • A noindex rule from staging carried into production.
  • A form that worked in preview and silently fails live.
  • Neither is visible by looking at the site.

Verify production infrastructure

Confirm domain records, TLS, canonical host, redirects, headers, environment settings and rollback information. Preview success does not prove production configuration. Test on the address the public will use, not on the staging URL that behaved correctly yesterday.

  • One canonical host, with the other variant redirecting to it.
  • A valid certificate and a known renewal date.
  • A documented way back if something goes wrong.

Review search controls

Check titles, descriptions, canonicals, robots directives, sitemap entries, structured data and internal links on the final URLs. Test old-to-new redirect mappings directly. The staging noindex left switched on is the most common and most damaging launch error, and it can go unnoticed for weeks.

  • Remove temporary noindex rules.
  • Keep one canonical host.
  • Submit or confirm the production sitemap.
  • Walk the redirect list address by address, not by sampling.

Test conversion and measurement

Complete forms, booking and contact journeys using controlled data. Confirm delivery, success and failure states, analytics events and consent behavior where applicable. Send a real submission and confirm it arrives in the inbox that a person actually reads, not merely that the success message appears.

  • A genuine submission through every form.
  • Confirmation that it reached a monitored destination.
  • Analytics recording page views on the live domain.
  • Behaviour when a required field is left empty.

Run human quality assurance

Review representative pages on mobile and desktop, navigate by keyboard, inspect content and media, and check performance with production assets. Record known limitations and owners. Automated checks miss the things people notice first: a broken image, an untranslated label, a heading that wraps awkwardly on a phone.

  • Every template opened on a real phone.
  • The whole page navigable by keyboard with visible focus.
  • Content proofread on the live site, not in a document.

The first week matters more than launch day

Most launch damage is done not by the release itself but by the days afterwards, when nobody is watching. A short monitoring period catches problems while they are still cheap, and before search engines have fully processed the change.

  • Watch indexing reports for pages disappearing.
  • Check that enquiries are still arriving at the usual rate.
  • Look for 404 errors appearing in reports.
  • Keep the previous site available until the new one is confirmed.

Practical decision checklist

  • Verify domain, TLS and canonical host on the live address.
  • Remove staging noindex rules.
  • Walk the full redirect list.
  • Send a real submission through every form.
  • Review accessibility and responsive layouts on a phone.
  • Assign post-launch monitoring and rollback.

Frequently asked questions

When should a sitemap be submitted?

After the production sitemap contains the intended canonical indexable URLs and the site is ready for search engines to process.

How long should launch monitoring continue?

Monitor closely through the initial processing period and continue recurring checks for forms, indexing, performance and content changes.

Should the old website be deleted immediately?

Retain appropriate backups and rollback information until the new production site, data and redirects have been verified.

What is the most common launch mistake?

A noindex directive left over from staging. It is invisible to visitors, it stops the site being indexed, and it is frequently discovered only weeks later when traffic fails to appear.

When is the best time to launch?

Early in a working day with people available to respond, rather than late on a Friday. Most launch problems are quick to fix if somebody is watching when they surface.