Website launch checklist
WordPress launch checklist for agencies
A WordPress build carries settings from staging that nobody sees on the page: the box that discourages search engines, the site addresses, the administration email and the accounts created during the build. Check these twelve settings in the WordPress admin before handoff. Use the full website launch checklist for everything that is not specific to WordPress.
Last reviewed
← Full website launch checklist
Search visibility and addresses
Search engines are no longer discouraged
Manual
In Settings > Reading, uncheck “Discourage search engines from indexing this site” under Search Engine Visibility, then click Save Changes.
Why it matters: While it is checked, WordPress adds a noindex, nofollow robots meta tag to the <head> of themes that call wp_head.
Site addresses show the live domain
Manual
In Settings > General, check that WordPress Address (URL) and Site Address (URL) use the live domain. If WP_SITEURL or WP_HOME is defined in wp-config.php, the field shows that value and cannot be changed in the admin.
Why it matters: The Site Address is the address people type in their browser to reach the site.
References to the staging domain are replaced
Manual
After the move, search for the old domain and replace it in the wp_posts table, the scope the migration guide gives for a search and replace. Never change the GUID column.
Why it matters: The guide warns that references to the old domain name or location will remain in the database, and that a search and replace on the entire database can cause issues with data serialization.
Source: WordPress Advanced Administration Handbook: Migrating WordPress
The permalink structure is final
Manual
In Settings > Permalinks, choose the structure under Common settings, such as Post name, and click Save Changes.
Why it matters: Permalinks are the permanent URLs of posts, pages and archives, and WordPress says each post URL should be permanent and never change.
Accounts and email
The administration email reaches the client
Manual
In Settings > General, set Administration Email Address to an address the client's organization can access, then click the confirmation link WordPress sends to it.
Why it matters: It may receive comment moderation, recovery mode and fatal error notices, and WordPress asks sites set up by a developer or agency to check it.
Open registration is off unless needed
Manual
In Settings > General, leave Membership: Anyone can register unchecked unless the site needs public sign-ups, and check New User Default Role.
Why it matters: When the box is checked, anyone can register an account, and new users get the default role.
Build accounts are removed
Manual
In Users, delete the accounts created for the build that the client does not need. When asked about their content, choose Attribute all posts and links to and pick a remaining user.
Why it matters: Choosing Delete all posts and links instead deletes the content attributed to those users.
Content and comments
Test posts are deleted
Manual
In Posts, move the test posts written during the build to the Trash, including the post a new installation starts with.
Why it matters: WordPress's first-steps guide ends with a reminder: don't forget to delete your test posts.
Source: WordPress documentation: First steps with WordPress (Block Editor)
Comment settings match the client's plan
Manual
In Settings > Discussion, decide whether “Allow people to post comments on new articles” stays checked, and review Before a comment appears and Email me whenever.
Why it matters: These defaults apply to new articles and can be overridden on individual articles, so set them before content goes in.
A privacy policy page is published
Manual
In Settings > Privacy, select the page and click Use This Page, or click Create New Page, edit the template and publish it.
Why it matters: WordPress shows the page on the login and registration pages; linking it from every page of the site is up to the site.
Debug mode and site health
Debug mode is off on the live site
Manual
In wp-config.php on the live server, check that WP_DEBUG is not set to true.
Why it matters: WordPress does not recommend WP_DEBUG or the other debug tools on live sites; use them in a local development or staging environment.
Source: WordPress Advanced Administration Handbook: Debugging in WordPress
Site Health shows no critical issues
Manual
On the live site, open Tools > Site Health, resolve the Critical issues in the Status tab, and read the Info tab.
Why it matters: The Status tab flags problems such as errors displayed to visitors; the Info tab shows the site URL, permalink structure and whether search engines are discouraged.
What a Launch Ready scan covers on WordPress
A Launch Ready scan reads the published pages of a WordPress site with the same rules as any other site (see How we scan). A Launch Ready scan does not log in to the WordPress admin and does not read platform settings. So every item above is Manual. Where a setting leaves a result on the published pages, the scan sees the result, not the setting:
- With the search engine setting still checked, the noindex robots meta tag WordPress adds is on the published pages, and the scan reports it. See A noindex tag left on.
- Links and canonical tags that still point at localhost are reported, and on a project set to Production, so are those that point at a host that looks like staging, such as a staging. subdomain. See Staging and localhost links left in.
- On paid plans, when the crawled pages show a WordPress site, an advisory check that does not change the score flags the Hello world! post or the Sample Page that a new installation creates while it is still published.
- On paid plans, when the crawled pages show a WordPress site, an advisory check that does not change the score flags PHP error messages printed on crawled pages and a /wp-content/debug.log file anyone can download.
- The same advisory WordPress checks also flag the default tagline WordPress used before version 6.1, a public user list at /wp-json/wp/v2/users, a reachable /xmlrpc.php and a browsable /wp-content/uploads/ folder. For these, the scan requests /wp-json/wp/v2/users, /xmlrpc.php, /wp-content/debug.log and /wp-content/uploads/ on the scanned site, with GET only, following no redirect and reading only the start of each response: at most 128 KB of the user list and a few kilobytes of the others. Of the user list it keeps only the number of users.
Everything else
The items above cover WordPress settings only. For everything else, use the free 72-item website launch checklist.
Related launch mistakes
Check your next client site before handoff
Add the staging or live URL, read the fix list, and send the client a report when it is ready.