A website launch includes more than making a page public. The agency should confirm that content is approved, key workflows function, access is understood, and someone is ready to respond if a problem appears. A checklist gives the client, agency, and production partner a shared view of what is complete and what still needs a decision.
Confirm scope and approval
Review the agreed deliverables and acceptance criteria. Confirm that the client or authorized decision maker has approved the design and content. Verify that open issues are either resolved, accepted with a plan, or clearly documented as post-launch work. Do not treat silence as approval unless the project agreement defines it that way.
Check that the production environment uses the approved source files and final copy. Remove placeholder text, test content, temporary passwords, and internal notes. Confirm that any third-party assets or plugins are licensed for the intended use.
Test the visitor experience
Review all important pages at desktop and mobile widths. Test navigation, buttons, internal links, contact forms, search, account access, checkout, booking, or other workflows included in the project. Confirm that form submissions reach the intended inbox or system and that confirmation messages are clear.
Check headings, image alternatives, form labels, and keyboard navigation according to the accessibility requirements for the project. Review page titles and descriptions for accuracy. Google’s guidance emphasizes that pages should be accessible to crawling and use content that helps people understand the site; these practices do not guarantee a ranking.
Verify technical and search settings
Confirm the intended canonical domain, HTTPS, redirect behavior, and analytics configuration. Make sure public pages are not accidentally blocked by a noindex setting, password protection, or a robots directive. If a sitemap is generated, inspect it for the intended public URLs. Google notes that sitemap submission can help communicate pages but is not required and does not guarantee indexing.
If the site is replacing an existing one, compare old and new URLs and implement agreed redirects. Check internal links and update any references to a staging domain. Avoid leaving duplicate staging pages publicly accessible when they are not intended for indexing.
Confirm access and recovery
Document who controls the domain registrar, DNS, hosting, WordPress administrator accounts, and key integrations. Confirm that the client has access to the accounts it owns and that unnecessary temporary accounts will be removed. Ensure a backup exists before launch and determine how to restore it if deployment creates a serious problem.
Agree on a rollback decision owner and contact method. If a critical workflow fails, the team should know who can pause the launch, restore the previous version, or contact the host. Record the time of launch and the person responsible for monitoring the result.
Close the handoff
Provide the client with concise documentation: how to edit routine content, where to request changes, who handles hosting and updates, and what support is included. State any known limitations or deferred items. If the partner completed the build behind the agency brand, the agency remains responsible for its client communication and final delivery commitments as defined by its agreement.
Coordinate the final release
Agree who has authority to approve publication and who can roll back a release. Before launch, confirm that the approved copy, images, forms, redirects, and contact destinations are present in the release candidate. Make a brief record of the current site state and any changes planned, especially when the site receives orders, bookings, or ongoing submissions. After release, check the public pages and the main conversion paths, then tell the client what was verified and what remains scheduled. If a problem appears, use the agreed escalation path instead of making untracked changes. A launch checklist is useful only when named people own each item and can report completion.
Related resources
Explore the topic hub and these related guides:
For work involving WordPress, the official WordPress documentation is a useful reference for maintenance responsibilities and recovery planning.