WordPress Website Launch Checklist: What to Check Before You Go Live
The site looks finished. The client has signed off the design, the content is in, and someone is about to point the domain at it.
What goes wrong next is almost never the design. It is a setting left over from building the site: a search-engine block that was right on staging, a page that was renamed after the menu was built, a plugin printing warnings onto the homepage. Each takes a minute to fix and is easy to miss, because the site looks fine to the person who built it.
This is the checklist we use, in the order worth working through it.
Before you start: a backup and a way back
Take a full backup, files and database, before you change anything for launch. Launch day means DNS changes, a search-and-replace of the site URL, and plugin settings flipped from staging to live. If one of those goes badly, a backup turns a bad afternoon into a ten-minute restore.
Download a copy off the server too. A backup stored only on the same hosting account is gone if the account has a problem.
1. Search engines are allowed in
This is the classic launch-day mistake, and it can cost weeks.
- Settings → Reading → "Discourage search engines from indexing this site" must be unticked on the live site. It is meant for staging, and it is easy to carry over.
- No noindex on your important pages. SEO plugins can set noindex per page or per post type. Check the homepage and a few key pages in your SEO plugin's settings.
- robots.txt doesn't block everything. Open yoursite.com/robots.txt. A line saying
Disallow: /underUser-agent: *tells every search engine to stay out of the whole site.
A site can look perfect, rank for nothing, and nobody notices for a month, because nothing on the page itself looks wrong. Check these three on launch day, then again a week later.
2. One address for the whole site
Visitors and search engines should end up at exactly one version of every page.
- http:// redirects to https://. Type the http address into the browser and confirm it lands on https.
- www and non-www. Pick one. The other should redirect to it with a 301. If both serve the full site, search engines see two copies and split the signals between them.
- Settings → General. The WordPress Address and Site Address should both match the version you picked.
- Short redirect chains. One hop from any variant to the final address. Chains of three or four redirects slow the first visit and are usually leftovers from old setups.
- Canonical links point at the live site. A staging URL in the canonical tag tells Google the real page lives somewhere else. This usually comes from a migration that missed a setting.
3. Every link works, and missing pages say so
- Click through the menu, the footer and the homepage. Pages renamed in the final week are the usual cause of broken links, because the menu still points at the old address.
- A missing page returns a real 404. Visit an address that doesn't exist. You should see your theme's 404 page, and the server should answer with status 404, not 200. A "soft 404" lets error pages into search results.
- Old URLs redirect. If the site replaces an older one, map the old addresses to the new pages with 301 redirects before launch, not after the traffic drops.
4. The basics search engines read
- A page title on every page, around 30 to 60 characters, with what the page is about first and the brand name after it.
- A meta description of 120 to 160 characters. Without one, Google writes its own snippet from the page.
- One main heading (H1) per page, saying what the page is about. Sections below it use H2 and H3.
- An XML sitemap. WordPress makes one at /wp-sitemap.xml by itself, and SEO plugins make their own, usually at /sitemap_index.xml. Make sure one is on, add a
Sitemap:line to robots.txt, and submit it in Google Search Console. - Structured data. SEO plugins add Organization and WebSite schema when you fill in your business details. It helps search engines, and AI tools, understand who the site belongs to.
- Social sharing previews. A title, a description and an image for Open Graph, so a link shared on WhatsApp, LinkedIn or Facebook shows a proper card instead of a bare URL.
- A site icon. Appearance → Customize → Site Identity, or the Site Editor's site icon.
5. HTTPS is complete
- The certificate is valid and renewing. Most hosts include a free certificate that renews itself. Check the expiry date anyway, and that auto-renewal is on.
- No mixed content. An https page that loads an image or script over http:// gets warnings or blocked files. It usually comes from content copied from the old site. A search-and-replace of the old http address fixes it.
6. Speed on a phone, measured
Run your homepage through Google's PageSpeed Insights, on mobile first. It runs Lighthouse and shows the timings behind the score: when the largest content appears (LCP), how much the layout shifts (CLS), and how long the page is blocked from responding.
- Turn on page caching, through your host or a caching plugin. It is usually the single biggest change.
- Compress and size images. Large images uploaded straight from a camera or a design tool are the most common reason a WordPress page is slow.
- Question every plugin that loads on the homepage. Each one can add its own scripts and styles to every page.
One measurement on one day is a direction, not a verdict. Once the site has enough visitors, the real-visitor data in Search Console's Core Web Vitals report is the better long-term measure.
7. Nothing embarrassing on show
- No PHP warnings on the page. If debug display is on, a plugin's warning prints straight onto the page for every visitor to see. In wp-config.php, keep
WP_DEBUG_DISPLAYset to false on the live site and log errors instead. - No leftover test content. Sample pages, "Hello world!", placeholder text, test products and test form entries.
- The uploads folder can't be browsed. Visit yoursite.com/wp-content/uploads/. If you see a list of files, directory listing is on. Turn it off at the server, or ask your host.
8. Basic security from the outside
These are the things anyone can see without logging in:
- User accounts in the REST API. By default, /wp-json/wp/v2/users lists author accounts with their username slugs, which are often the login names. That is half of what a password-guessing script needs. Security plugins can restrict it to logged-in users.
- XML-RPC. If you don't use the WordPress mobile app, Jetpack or a service that needs it, turn xmlrpc.php off. It is a common target for password guessing.
- readme.html and the version number. WordPress's readme.html and the generator tag tell anyone which version you run. Not a hole by themselves, but no reason to advertise it. Keeping WordPress updated matters more.
- Security headers. Four basic headers (Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options or a frame-ancestors policy, and Referrer-Policy) can be added at the server, the CDN or with a plugin. Add them one at a time and test the site after each.
- Strong passwords and two-factor login for every administrator, and no account called "admin".
9. Forms send, and email arrives
No automated check can tell you this one. Send a real message through every form on the site and confirm it arrives where it should, including the auto-reply if there is one.
WordPress sends email through the server by default, and much of it lands in spam or never arrives. An SMTP plugin connected to a proper sending service fixes most lost-email problems. Test with an address outside your own domain.
10. Accessibility basics
- Alt text on images. Describe the image in the Media Library, or leave alt text empty for purely decorative images.
- The page language is set (Settings → General), so screen readers use the right voice.
- Text has enough contrast against its background, and links look like links.
- The site works with a keyboard. Tab through the homepage: you should always see where you are, and the menu should open and close.
Automated checks catch some of this. A minute with the keyboard catches more.
11. After launch: tell Google and start measuring
- Add the site to Google Search Console, verify it, and submit the sitemap.
- Check analytics is recording real visits on the live domain, not the staging one.
- Look at Search Console again after a week: pages indexed, pages excluded and why, and any crawl errors.
- Keep a backup schedule running from day one.
The checklist in one table
| Check | Where to look |
|---|---|
| Search engines allowed | Settings → Reading, SEO plugin, robots.txt |
| One address for the site | http, www and non-www all land on one https address |
| Canonical points at the live site | Page source or SEO plugin |
| No broken links | Menu, footer, homepage |
| Real 404 page | Visit a made-up address |
| Titles, descriptions, one H1 | SEO plugin, page source |
| XML sitemap submitted | /wp-sitemap.xml or /sitemap_index.xml, Search Console |
| HTTPS complete | Certificate expiry, no http:// files |
| Speed on a phone | PageSpeed Insights, mobile |
| No PHP errors or test content | Homepage, wp-config.php |
| Uploads folder not browsable | /wp-content/uploads/ |
| User list, XML-RPC, headers | /wp-json/wp/v2/users, xmlrpc.php, response headers |
| Forms deliver | Send a real message |
| Accessibility basics | Alt text, language, contrast, keyboard |
| Search Console and analytics | After launch |
Check most of this in a minute
We built a free tool that runs most of these checks on a live site at once: search settings, redirects, broken links, the 404 page, titles and the sitemap, HTTPS and mixed content, Google's speed test on a phone and a desktop, security headers, and the WordPress settings anyone can see from outside. Each result shows the evidence it found and how to fix it.
It can't send your forms or press Tab through your menu, so steps 9 and 10 stay with you.
Run the free WordPress launch check
Enter your site address and get a report in about a minute: launch blockers, things to fix, and the evidence behind each result. No sign-up.
Check your siteLaunching a site built from Word documents? Back up and check your disk space before a bulk import first.
Related Articles
Best WordPress Plugins for Bloggers in 2026: 12 Free Picks
The 12 free WordPress plugins a blog needs in 2026, one per job: writing, SEO, spam, backups, speed, images, email and analytics, with the catch for each.
How to Let AI Post to WordPress Without Giving It the Keys
Connecting an AI agent to WordPress can mean handing it the power to publish, edit and delete. Here is what to check before you connect one, and why a drafts-only connection is the safer start.
Before You Bulk-Import Word Documents: Back Up and Check Your Disk Space
A bulk import puts hundreds of posts and thousands of image files on your site in one afternoon. Two checks to do first: a full backup, and how much room the import has.
Import your first Word document in under 60 seconds
Start free. Import a Word document without copy-pasting or rebuilding its formatting. No account, no credit card. Straight from WordPress.org.