A WordPress launch checklist should verify the website people will actually use. Review the core visitor journeys, not just the homepage’s appearance.
Use this checklist on a staging site where possible, then repeat the public-facing checks after launch. Assign an owner to every unresolved item.
Content and identity
- Confirm the business name and contact details.
- Remove sample posts, placeholder text, and unused demonstration sections.
- Check that every service or product claim is accurate.
- Review About and Contact content.
- Complete the policy information relevant to the site’s actual activities.
- Verify that photos and other assets may be used.
An unfinished sentence hidden near the footer is still part of the public website. Read entire pages.
Navigation and links
- Follow each main menu item.
- Check footer links.
- Confirm that important pages are reachable through a sensible route.
- Remove links to unpublished resources.
- Test buttons against their labels.
- Check the site on a narrow screen.
Do not assume a page appears in the menu simply because it is published.
Forms and customer journeys
- Submit each important form with valid test information.
- Test missing or invalid required fields.
- Confirm that the destination receives the submission.
- Check the confirmation message.
- Verify ownership of incoming enquiries.
- Remove test records when appropriate.
For a shop or booking system, use the platform’s supported test process to check the entire transaction and exception paths.
Access and recovery
- Confirm business ownership of domain and hosting access.
- Review administrator accounts.
- Confirm backup scope and retention.
- Identify who can restore the site.
- Record the recovery procedure and support route.
- Check that a tested recovery copy exists where required.
WordPress’s advanced backup guidance provides background on protecting site files and data.
Search and page information
- Review titles and descriptions for important pages.
- Check intended public indexing settings.
- Inspect the actual sitemap.
- Confirm that private or staging material has appropriate access protection.
- Verify important URLs after launch.
Search visibility settings are not a substitute for protecting confidential content.
Usability and accessibility
- Test keyboard access to important controls.
- Check form labels and readable error messages.
- Review meaningful image alternatives.
- Inspect text at increased zoom.
- Check that overlays do not block the main task.
A launch review does not establish complete accessibility conformance, but it can identify barriers that need attention.
Decide whether the site is ready
Classify unresolved issues by consequence. A non-working enquiry form can block the site’s purpose; a minor spacing inconsistency may not.
Record the issue, owner, decision, and target date. Avoid marking everything complete merely to meet a planned launch time.
After launch, repeat the main journeys from the public URL. Confirm that the live configuration, content, and integrations match what you tested. Keep the checklist as a record of the review, then turn recurring checks into a maintenance routine.
