Resource / Launch checklist
WordPress Launch & Handover Checklist
A pre-launch and handover checklist for backups, access, site behavior, SEO, release safety and ongoing ownership.
Use this checklist before launching or handing over a WordPress site. It covers operational details that are easy to miss when attention is focused on the homepage: backups, permissions, forms, redirect behavior, indexability, accessible interaction, monitoring and recovery.
Backups and release safety
- Create a backup of files and the database and verify that restoration is possible.
- Test the release on staging with production-like content and plugin versions.
- Record the theme version, PHP version, WordPress version and important dependencies.
- Keep custom code in version control and define a rollback owner.
Security and access
Remove unnecessary administrator accounts, apply least-privilege roles, enable strong authentication, secure secrets outside source files and confirm HTTPS. Review public endpoints, forms, upload permissions and custom REST fields. Update WordPress and dependencies through a tested process instead of changing everything live without a backup.
Functional review
- Test navigation, footer links, search, archives, single templates and pagination.
- Submit contact and comment forms with valid, invalid and spam-like input.
- Verify email delivery in a real inbox; do not confuse queued mail with delivery.
- Test responsive behavior, keyboard navigation, focus states and reduced-motion preferences.
- Check missing images, broken internal links, 404s and redirect loops.
SEO and analytics
Verify rendered titles and descriptions, canonical URLs, robots directives, XML sitemap inclusion and indexability. Inspect structured data for valid JSON and consistency with visible content. Check that social previews use the intended title, description and image without duplicate tags from the theme and SEO plugin. Configure analytics and Search Console only with the correct account and consent behavior.
Handover package
Document how editors create and update pages, where important settings live, which plugins own critical functionality, who receives form and comment notifications, how deployments happen and how to restore the previous release. Do not include passwords in the handover document; describe the authorized secret-management method instead. Test the guide by asking the receiving owner to complete a routine update and explain recovery steps.
Launch only when open defects are documented, the rollback path is available and named people accept ongoing responsibilities. The Systems Lab Reference Model offers a useful way to document operational controls and recovery.
Release-day decision record
Keep a short release record that names the release owner, reviewer, deployment window, backup location, tested commit or theme version, and rollback decision. Record unresolved issues with their impact and owner instead of hiding them in a general note. A release can proceed with known low-risk issues only when the decision is explicit and a realistic follow-up date is agreed.
Separate checks that can be automated from checks that require human judgement. A link checker can find broken URLs, but it cannot prove that a page gives an accurate answer. A successful form response in the browser does not prove the record was stored securely or that the notification reached the recipient. Test both the visible experience and the resulting record or operational event.
Post-launch observation
After deployment, check the homepage, key landing pages, one archive, one single content page, and every critical conversion path using a normal visitor session. Review server or monitoring logs for fatal errors, repeated redirects, missing assets and form failures. Confirm analytics are firing only as intended and that privacy choices are respected. Revisit the site after caches have expired and after the first routine content edit, since cache invalidation and editor permissions can expose problems that an immediate smoke test misses.
Agree who receives alerts, how urgent issues are escalated, and what constitutes a rollback. Store recovery instructions where the responsible owner can access them without depending on the person who built the site. The handover is complete only when the receiving owner can publish a safe change, find a failure, and explain how to restore the last known-good release.
Need a tailored version?
We can shape a resource, workflow or content system around your team and process.
Get in touch