A website launch is a business handover, not just a successful upload. The public pages, contact routes, domain configuration and operating responsibilities must work together. Use a release checklist with clear evidence and owners so unresolved issues can be assessed before customers encounter them.

This guide covers production readiness, enquiry routes, search configuration and operational handover. Discuss the relevant requirements through ITZ’s Website Development service.

Content and navigation

Confirm service descriptions, business details, image permissions and approved page titles. Check internal links, navigation and important user journeys on supported screen sizes.

Review approved service descriptions, branch details, images and permissions against the actual release. Test representative journeys from entry page to enquiry rather than clicking only the main navigation. Include long content, translated pages and empty or error states. Content approval and functional approval should both be recorded; one cannot stand in for the other.

Technical configuration

Verify HTTPS, domain routing and the production environment. Where URLs change, check the redirect plan and canonical addresses. Confirm that required assets and integrations are available after deployment.

Verify the production domain, HTTPS, routing and public assets after deployment. Keep preview access and indexability settings distinct from production. If URLs change, test a sample redirect map and important old entry points. Confirm that external services use the correct production accounts without exposing credentials in page source or a public release note.

Plan Your Website Launch Review to discuss production readiness, enquiry routes, search configuration and operational handover.

Search and measurement

Review robots directives, sitemap URLs and the indexability of intended public pages. Configure and validate agreed analytics events where applicable, without treating an event as evidence of a completed sale.

Check intended indexability, canonicals and sitemap destinations. Google's sitemap guidance explains that a sitemap helps discovery but does not guarantee crawling or indexing. If analytics is part of the agreed scope, validate the relevant events under approved conditions. Do not report installed tags as evidence of received leads or improved search performance.

Operational handover

Confirm account access, backups, renewal responsibilities and the route for reporting faults. Record known limitations and assign ownership for post-launch checks and ongoing content updates.

Hand over account access, renewals, backups, content ownership and fault reporting. Name the person who can make a rollback decision and record known limitations. A short post-launch review should revisit production journeys and provider notifications. No checklist proves a system can never fail; it makes the release decision and response responsibilities clearer.

A practical example

Illustrative example: a site deploys successfully but retains a preview noindex setting and sends enquiries to an old inbox. Both can be missed if approval stops at the hosting build result. A public-page check and an authorised delivery review address different parts of launch readiness.

Your review checklist

  • Approve content and test representative customer journeys.
  • Verify production routing, HTTPS and external integrations.
  • Review indexability, canonicals and sitemap destinations.
  • Document access, rollback and post-launch operating owners.

Frequently asked questions

Does a successful deployment complete the launch process?

It confirms delivery to the hosting environment. The public website still needs checks for accessibility, key functions, routing and operational readiness.

References and further reading

Related services and guides

Discuss the next step

Plan Your Website Launch Review. Use the form below to discuss production readiness, enquiry routes, search configuration and operational handover. Share the relevant goals and existing arrangements; do not include passwords, private records or access tokens.

Plan Your Website Launch Review ↗

Reviewed and expanded on 15 October 2026. Examples are illustrative; the appropriate approach depends on your business requirements and existing systems.