A new website can look perfect in a design preview and still fail the moment a customer tries to use it. The contact form may never reach your inbox. A button might lead nowhere. Your staging site’s search visibility setting might still be active. Or an old service page may disappear without a redirect.
A proper launch is a short series of real-world tests, not just a final look at the homepage. Use this checklist before making your WordPress site public. If you are redesigning an existing site, pay particular attention to the URL and redirect checks.
1. Read every important page as a customer
Start with the homepage, core service pages, About page, and Contact page. Can someone understand what you offer, who you help, and what to do next within a few seconds? Replace placeholder copy, check pricing and service details, and confirm that business hours, email addresses, and phone numbers are correct.
Do not stop at proofreading. Ask someone unfamiliar with your business to find a service and send an inquiry. Watch where they hesitate.
2. Check every button and link
Click your header menu, footer menu, service cards, blog links, and every call to action. A button labeled “Get a Quote” should open the quote form or contact page—not jump to the top of the current page. Check links in a private browser window so your WordPress login does not hide access problems.
Make a list of any # placeholder links and replace them with real destinations before launch.
3. Send a test through every form
Fill out each contact, quote, booking, and newsletter form as a visitor would. Test both valid and incomplete submissions. Confirm that the success message appears, the notification reaches the correct inbox, and any autoresponder says the right thing. If a form stores entries in WordPress, check that the submission is recorded there too.
Also test on a phone. Fields that appear fine on desktop can be hard to use on a small screen.
4. Test the mobile experience on a real device
Open the homepage, a long service page, a blog post, and the contact page on your phone. Check the menu, text size, button spacing, forms, image crops, and sticky elements. Look for sideways scrolling or content hidden behind a fixed header.
A responsive editor preview is useful, but it is not a substitute for tapping through the actual site.
5. Confirm the site uses HTTPS
Open the live domain with and without www, and with http://. Each version should lead to your intended HTTPS address. Check that images, fonts, and embedded content load securely. A browser warning on your contact or checkout page can stop a visitor from continuing.
6. Check your homepage and WordPress settings
Under Settings → Reading, confirm the correct homepage and posts page are selected. Review the site title, tagline, timezone, and administrator email under Settings → General. If you have not launched yet, choose a clear URL structure under Settings → Permalinks. Changing URLs later needs extra care because existing links may need redirects.
7. Remove staging restrictions before asking Google to find the site
A staging site may be hidden from search engines on purpose. Before launch, review Settings → Reading → Search engine visibility, any SEO plugin indexing settings, and any password protection or noindex rule applied to public pages. Then check the live version rather than assuming the staging settings transferred correctly.
Turning indexing on does not guarantee that Google will list every page. It simply removes one common obstacle.
8. Review titles, descriptions, and social previews
Give each main page a specific title and a useful meta description. The homepage should explain your main service; individual service pages should describe their own service. Check the featured image and social sharing preview for pages you expect people to share.
Avoid publishing many pages with the same title and description. If you need help planning page topics, see our guide to internal linking for service-based WordPress sites.
9. Inspect the sitemap and connect Search Console
Open your XML sitemap and check that your important public pages appear while private or test content does not. Verify the live domain in Google Search Console and submit the sitemap there. Google says a sitemap is a discovery hint, not a promise that each URL will be indexed.
After launch, use Search Console’s URL Inspection and indexing reports to catch problems that were not obvious during testing.
10. Map old URLs to new ones if you are redesigning
If an existing page changes address, set a permanent redirect from the old URL to the closest relevant new page. Do not send every old URL to the homepage. Check your most visited pages, service URLs, and pages with backlinks first. Preserve a URL when there is no good reason to change it.
For a larger rebuild, read our website redesign guide and keep a simple spreadsheet of old URL, new URL, and redirect status.
11. Test speed on the pages that matter
Check the homepage, your main service page, and at least one contact or landing page with PageSpeed Insights. Pay attention to what actually slows the page: large hero images, unnecessary scripts, slow server response, or elements that move while loading. Test on mobile as well as desktop.
A single score is not the whole story. Fix the reported issues, then test the same pages again. If your site uses Elementor, our Core Web Vitals guide explains common LCP and CLS problems.
12. Check images and accessibility basics
Make sure each important image is sharp at its displayed size without being unnecessarily large. Add helpful alternative text to informative images. Check that headings follow a clear order, form fields have understandable labels, and text is readable against its background. Try navigating menus and forms with a keyboard.
Accessibility needs more than a single automated score, but these checks catch common barriers before launch.
13. Finish the privacy and trust pages
Review your Privacy Policy, Terms, and any refund or cancellation information that applies to your business. Make sure they reflect the tools and processes you actually use, especially forms, analytics, payments, and email marketing. Link to the relevant pages from your footer and forms where appropriate.
If your business has a physical location or professional credentials, check that those details are accurate too.
14. Set up backups, updates, and basic security
Before launch, confirm you have a working backup and know how to restore it. Update WordPress, your theme, and plugins, then test again. Remove unused plugins and unused accounts. Give each person only the access they need, use strong passwords, and enable extra login protection where practical.
A launch is the beginning of maintenance, not the end. See what is covered by our WordPress maintenance and support service.
15. Confirm analytics and define a useful conversion
Check that your analytics tool records visits on the live domain. Then decide which actions matter: form submissions, phone clicks, bookings, purchases, or another real inquiry. Test those actions so you know the measurement works.
Do not judge the new site only by traffic. A site that brings the right visitors to a working inquiry path is more useful than one with a large visit count and broken forms.
A quick final test before publishing
Open the website in a private window on desktop and mobile. Start on the homepage and try to complete the same task a customer would: understand the offer, choose a service, and contact or book with the business. Then check the notification, the recorded submission, and the thank-you page. Fix anything that blocks that path before launch.
After the site goes live, repeat the test on the public domain and review Search Console and form submissions over the next few days. Small issues are easier to catch when the launch is still fresh.
Frequently asked questions
How long does a WordPress website launch check take?
It depends on the size and features of the site. A five-page brochure website can often be reviewed in a focused session, while an online store or booking website needs more detailed transaction and workflow testing. Reserve time to fix what you find and test it again.
Do I need to submit every page to Google?
You can submit your sitemap through Search Console and use URL Inspection for important pages. Google decides when to crawl and index pages; sitemap submission does not guarantee inclusion.
What should I test first if I have limited time?
Test the main inquiry path: homepage, primary service page, contact or booking form, mobile navigation, and the resulting notification. Then check indexing settings and redirects before you announce the launch.
Should I launch if a few small issues remain?
Fix issues that prevent visitors from finding information, trusting the site, contacting you, or completing a purchase. Minor visual refinements can be scheduled after launch, provided you have a clear owner and date for them.
Ready to launch with confidence?
At Elementor Team, we design and build WordPress websites with the full customer journey in mind—from the first page view to the inquiry. If you want a second set of eyes on a new site or a complete build, tell us about your project and we’ll help you identify what needs attention before launch.