Your new website looks ready. The pages are designed, the logo is in place, and everyone wants to share the link. Before you do, check whether a visitor can actually complete the tasks that matter: understand your services, use the site on a phone, and send an enquiry that reaches your team.

This WordPress website launch checklist helps business owners review those essentials with their developer. It covers the handover stage of WordPress website development, when small oversights can create avoidable problems. Work through it on the final domain, because a successful test on a development address does not confirm everything works after launch.

1. Agree on what “ready to launch” means

Start with a short acceptance list. Name the pages that must be finished, the actions visitors should take, and the person responsible for checking each one. A local service business might prioritise service enquiries and phone calls; a store will also need checkout and order processing.

Separate launch blockers from improvements that can wait. A broken enquiry form is a blocker. Replacing an acceptable decorative image can usually wait. Give each remaining issue an owner and a clear description so your launch discussion produces decisions.

2. Read every important page as a customer

Open the homepage, service pages, about page and contact page without using the WordPress editor. Look for missing images, placeholder copy, outdated phone numbers, unsupported claims and buttons that lead nowhere.

Each service page should explain what you offer, who it helps and what the visitor should do next. For example, “Request a laptop repair quote” gives a customer more direction than a vague “Explore” button. Check that your business name and contact details stay consistent across the header, footer and page content.

Ask a colleague who did not build the site to find a service and contact you. Their questions often reveal gaps the project team has stopped noticing.

3. Test mobile navigation and basic accessibility

Use a real phone as well as your desktop browser. Open the menu, follow a service link, read a longer paragraph and complete a form. Check that sticky headers, cookie notices and chat buttons do not cover important controls.

• Text remains readable without pinching to zoom.
• Buttons and links have enough space around them.
• Images and tables fit within the screen.
• Forms have visible labels and understandable error messages.
• Keyboard users can reach links and controls and see which item is selected.

Add useful alt text to meaningful images. Describe what the image contributes instead of repeating a keyword. These practical checks are a starting point, not a complete accessibility audit.

4. Follow each enquiry from submission to inbox

A success message on a form does not prove your team received the enquiry. Submit a clearly labelled test with a real email address, then confirm the message reaches the intended inbox and that replying goes to the correct person.

Try missing required fields and an invalid email address. Make sure errors explain how to fix the problem without wiping out everything the visitor typed. Test notification delivery again after moving to the live domain.

Also check telephone, email and WhatsApp links on a phone. Confirm the destination number, country code and any prefilled message. If a form connects to a CRM, verify the record arrives there too, and agree who handles failed deliveries.

5. Confirm the live domain and HTTPS work

Ask your developer to check the final domain, its preferred www or non-www version, and HTTPS. Open important pages directly, including one reached from an external link. Look for browser security warnings, missing styling and images still loaded from the development site.

If your launch includes hosting or DNS changes, record the existing configuration first. Have the person managing DNS preserve the records used by business email. Website hosting and email delivery may depend on different records, so test incoming and outgoing business email after changes.

6. Check search visibility and page metadata

For a public website you want indexed, review Settings → Reading in WordPress and ensure the option to discourage search engines is cleared. The official WordPress reading settings documentation explains this control. It is not a way to secure a private development site.

Ask your developer to check for other accidental indexing blocks, including page-level SEO settings. Review the title and description for each main page, and confirm the preferred URL points to the live page rather than a staging address.

Open the XML sitemap and submit the appropriate sitemap in Google Search Console. Google explains that sitemaps help URL discovery; they do not guarantee crawling or indexing. Treat launch readiness and search rankings as separate goals.

7. Protect existing links during a redesign

If you are replacing an existing website, list its important URLs before changing the structure. Include service pages, popular articles and downloadable files. Where a URL changes, map it to the closest relevant replacement.

Ask your developer to implement and test appropriate permanent redirects. Do not send every old page to the homepage simply because it is convenient. Update internal links to the new destinations as well. Google’s site migration guidance covers URL mapping, redirects and monitoring; search visibility can fluctuate during a move.

8. Review performance on representative pages

Test more than the homepage. Include a service page, an image-heavy article and any important form. Use a phone on a normal mobile connection, then ask your developer to investigate slow loading, shifting layouts or delayed button responses.

Check whether oversized images, unnecessary scripts or third-party widgets are contributing to the problem. After performance changes, repeat the functional tests. An optimisation that stops the menu or form working needs correcting before launch. Record the test page and conditions so later comparisons are meaningful.

9. Verify backups and business ownership

Confirm you have a recent backup and know who can restore it. WordPress documents that a full recovery needs both files and the database. Ask for a restore test in a separate environment, rather than assuming a successful backup notification proves recovery will work.

The business should control its domain, hosting and essential accounts. Request individual logins with suitable permissions, a record of paid theme or plugin renewals, and a secure handover of access. Agree who installs updates, monitors problems and handles support after launch.

10. Repeat critical checks after going live

Publishing the site is the start of the final check. Test the main visitor journey on the live domain in a logged-out browser. Recheck forms, links and the pages affected by caching or redirects.

Confirm your chosen analytics system records a test visit as expected. If you track enquiries, distinguish successful submissions from button clicks. Keep personal form contents out of analytics events. Record the launch date and known issues, then review errors and customer feedback over the following days.

Frequently asked questions

Can I launch with a few unfinished pages?

Yes, if they are outside the agreed launch scope and visitors do not encounter empty pages or misleading links. Complete the essential service and contact journeys first, and keep unfinished content unpublished.

Is installing an SEO plugin enough?

No. You still need useful content, clear navigation, appropriate page settings and working internal links. An SEO plugin helps manage parts of that work; it does not replace a review of the actual website.

Should I test again after changing hosting?

Yes. Repeat checks on the live domain, especially forms, media, HTTPS and redirects. Confirm email still works if DNS records changed, and keep your recovery plan available until the move is verified.

Who should approve the launch?

Your developer should verify the technical setup, while someone from your business approves the content and customer journey. Name one person who makes the final launch decision and records any accepted outstanding issues.

Plan your WordPress launch with Ishu Technology

Ishu Technology’s WordPress development services include custom themes, plugin and API development, WooCommerce, performance optimisation and migration work. Share your website address, required customer actions and unfinished items so the discussion starts with your actual needs.

Ready to review your project? Contact Ishu Technology with your launch checklist and target date to discuss the next steps.