Checklist · 22 November 2026 · 6 min read
WordPress Website Testing Checklist: 62 Checks to Run Before a Client Sees It
A free WordPress website testing checklist: 62 checks we run before a client sees a site, from forms and phones to speed, SEO, accessibility and security.
By Nagz Studio
The first time a client opens their new site, they don't look at the code. They look for their phone number, try the contact form, open it on their phone and scroll to the bottom. If any of those is broken, that's the moment they remember, however good the rest is.
So we test the site the way the client and their customers will use it, before they ever see it. Below is our free checklist: 62 checks, grouped by area. Copy it into your project tool and tick it off for each site.
1. Content
- No placeholder text anywhere: search the database for "lorem", "ipsum", "sample" and "example.com".
- No placeholder images, stock watermarks or images you don't have the rights to.
- Phone numbers, email addresses and the street address match what the client gave you, and are the same on every page.
- Phone numbers are tap-to-call links (
tel:) and email addresses open a new message (mailto:). - The copyright year and business name in the footer are right.
- Spelling and grammar are checked on every page, including the 404 page and form messages.
- The "Hello world!" post, "Sample Page" and demo content from the theme are deleted.
Searching the database is quicker than reading every page. With WP-CLI: wp db search "lorem".
2. Forms
Forms are where launches go wrong most quietly: the form says "Thank you" and the email never arrives.
- Every form submits, on desktop and on a phone.
- The email arrives, in the inbox, at the address the client actually reads.
- The "from" address and subject make sense to the person receiving it.
- Required fields, email validation and error messages work and read clearly.
- The success message or thank-you page appears.
- Spam protection is on (a honeypot, Akismet, reCAPTCHA or Turnstile).
- If the form saves entries, they appear in the admin.
- Auto-replies to the visitor, if there are any, are worded by the client, not by you.
If emails don't arrive or go to spam, send them through a proper mail service with an SMTP plugin, and add that service to the domain's SPF and DKIM records.
3. Devices and browsers
- Test at real widths: a small phone (360px), a large phone (430px), a tablet (768px), a laptop (1280px) and a wide screen (1920px).
- Nothing scrolls sideways at phone width.
- The menu opens, closes and works with a thumb.
- Buttons and links are big enough to tap.
- Test in Chrome, Safari, Firefox and Edge, and on a real iPhone. Safari on iOS is where most layout surprises live.
- Videos, sliders and embeds (maps, booking widgets) load on mobile.
Your browser's device toolbar is a good start, but test on one real phone too. Fixed headers, address bars and touch behave differently on the device.
4. Speed
- Run the homepage and one inner page through PageSpeed Insights, and read the mobile result.
- Images are sized for where they're shown and compressed (WebP or AVIF where possible).
- The first image on the page isn't lazy-loaded; images further down are.
- No plugin is loading scripts on pages that don't use it.
- Page caching is on, from the host or a plugin, not both.
A slow page on a phone is usually one big image, one heavy plugin or too many fonts. Look at what PageSpeed lists under "Opportunities" before reaching for an optimisation plugin.
5. Search basics
- Every page has its own title and meta description.
- Every page has one H1.
- Images have alt text that describes them.
- An XML sitemap exists and lists the real pages.
- Each page has a canonical URL pointing at itself.
- The social sharing preview (Open Graph title, description and image) looks right when the link is pasted into WhatsApp or LinkedIn.
- Old URLs redirect (301) to their new pages if this replaces a site.
- On staging: search engines are blocked. On production: they're allowed. Settings → Reading, and robots.txt. Write this one in capitals in your checklist.
6. Accessibility
- You can reach and use every link, button, menu and form field with the keyboard alone (Tab, Shift+Tab, Enter, Esc).
- The focus outline is visible.
- Text has enough contrast against its background, including text over images.
- Every form field has a label, not just placeholder text.
- The page language is set (
lang="en"or the right language). - Headings go in order (H2 after H1, H3 inside an H2 section).
- Run Lighthouse's accessibility audit and fix what it finds. It doesn't catch everything, but it catches the common things.
7. Security and HTTPS
- Every page loads over HTTPS, and http:// redirects to https://.
- No mixed content: no images, scripts or fonts loaded over http://.
- www and non-www both lead to the same address.
- Security headers are set (at least X-Content-Type-Options, a Referrer-Policy and frame protection).
- The uploads folder doesn't list its files when you open
/wp-content/uploads/in a browser. -
readme.htmlis removed, and the WordPress version isn't printed in the page source. - XML-RPC is off unless something needs it.
-
WP_DEBUGis off, and no PHP errors or warnings appear on any page. - Admin accounts have strong passwords and two-factor authentication. No user is called "admin".
8. The admin the client will use
This is the part most testing skips, and it's the part the client lives in after launch.
- Log in with the client's role, not as an administrator, and do the jobs they'll do: edit a page, add a post, change an image, update opening hours.
- Custom fields have clear labels and instructions.
- The client can't accidentally break the layout, delete a template or change settings they shouldn't.
- The dashboard isn't full of plugin upsells and notices.
- The client has their own account, with their own email address. You're not sharing yours.
9. Before you hand it over
- Everything is updated: WordPress, the theme, every plugin.
- Unused plugins and themes are deleted.
- A full backup is taken, and stored somewhere other than the server.
- The 404 page looks like the rest of the site and helps people find their way.
- A site icon (favicon) is set.
- Analytics is recording, and Search Console is ready to be set up on the live domain.
- You've written down the logins, the plugin licences and who renews what.
Once the site is live, carry on with what to set up in week one after launch: Search Console, email delivery, off-site backups and uptime monitoring.
Test it once from the outside
Many of the checks above, such as HTTPS, mixed content, security headers, the uploads folder, readme.html, the WordPress version, XML-RPC, PHP errors, titles, descriptions, H1s, alt text, the sitemap, the canonical, the social preview, the 404 page and speed, can be tested on a live site without logging in.
That's what our free WordPress launch check does. It runs real tests and shows the evidence and a fix for each result, so you can paste the report into the handover or fix the failures before the client sees them.
For agencies and freelancers who run this on every project, WPShipReady builds it into the delivery itself: Claude Code takes the project from the client's brief to a QA report made from real tests, not a ticked list.
Which test on this list has caught the most problems on your sites?
More from the blog
- Tutorial · 6 minHow to Build a WordPress Website With Claude Code, Step by StepWPShipReady
- Opinion · 6 minFree Tools as Marketing: What We Learned Building Them for ShareMyInvite and DocxToWPShareMyInvite
- Build story · 6 minHow We Built ShareMyInvite: A Wedding Invitation SaaS With Next.js, Supabase and Dodo PaymentsShareMyInvite