How to Set Up a WordPress Staging Site and Push Changes Live Safely
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
The WordPress Site Health screen can look alarming. Learn what its warnings mean, fix the risky ones first, and decide which recommendations can wait.
WordPress Site Health is the screen that tells you, in orange and red, that something about your site “should be improved”. Most owners open it once, feel a small wave of panic, and then either ignore it forever or click every fix they can find. Both reactions are a mistake. This guide explains what the Site Health screen actually checks, which warnings can put your site at risk, and which ones are only advice.
Go to Tools → Site Health. The Status tab groups results into critical issues, recommended improvements and passed tests, and the Info tab lists technical details about your site. Fix the risky items first: an outdated PHP version, plugins waiting to be updated, background updates not working, and debug messages shown to visitors. Then look at connection problems (loopback requests, reaching WordPress.org), and finally housekeeping such as unused themes and plugins. Treat the rest as advice you can judge for your own site.
How this guide was prepared: the explanations follow the WordPress documentation listed under Sources, read on October 21, 2026. Messages differ between WordPress versions and hosts, and we did not test every possible warning. Our suggested order of fixing is our own recommendation, based on risk.
wp-config.php) can break something. See Is your WordPress backup really safe?
| What Site Health says | What it means | How urgent |
|---|---|---|
| Your site is running an outdated version of PHP | An old PHP version is slower and gets fewer security fixes | High: Step 2 |
| You have plugins waiting to be updated | Plugins have deep access to your site, so old versions are a risk | High: Step 3 |
| Background updates are not working as expected | WordPress may not install security updates by itself | High: Step 3 and 5 |
| WP_DEBUG_DISPLAY or WP_DEBUG_LOG is enabled | Errors may show on the front end or be written to a readable file | High: Step 4 |
| Your site could not complete a loopback request | Scheduled events and editors may not work reliably | Medium: Step 5 |
| Inactive plugins or themes, or no HTTPS | Unused code to remove, or a connection to secure | Medium: Step 6 |
The WordPress documentation explains that Site Health has two tabs. Status shows critical information about your configuration, grouped by severity: critical issues, recommended improvements and passed tests. Info is a detailed view of your WordPress version, theme, plugins, database, server and more, and it has an export feature that copies the information to the clipboard. Use that export when you ask a developer or host for help, but check it for private details first. The Info tab also shows whether your site is discouraging search engines, which is worth a glance if you care about traffic.
The documentation says newer PHP versions are made with performance in mind, and flags an outdated PHP as a security matter. WordPress.org’s requirements page recommends PHP 8.3 or greater, and its PHP update guide explains how to check your version: Tools → Site Health → Info → Server. Your host decides which versions are available, and many let you change it in the control panel. Back up first, switch on staging or a low-traffic moment, change the version and test the front end, forms and checkout. If a plugin breaks, update or replace that plugin rather than staying on an old PHP forever.
Site Health lists plugins waiting for updates because, as the documentation puts it, plugins have deep access to your site. Update them with a method that lets you recover, as in how to update WordPress plugins safely. If it says background updates are not working, WordPress may be unable to install automatic security updates, which can come from file permissions, a blocked connection or a hosting restriction. Our guide to WordPress auto updates explains what is automatic by default and what you can switch on.
The documentation warns that debug information may contain sensitive details. If WP_DEBUG_DISPLAY is on, errors can appear on your pages. If WP_DEBUG_LOG is on, errors are written to a file that may be available to others. On a live site, turn display off and keep logging off unless you are actively investigating, then delete the log. These settings live in wp-config.php, so back it up before editing. If you only need logs for a short time, see WordPress critical error for a safe approach.
The documentation explains that loopback requests are used to run scheduled events and by the built-in theme and plugin editors to verify code. A failure often comes from a security plugin, a firewall, basic authentication on a staging site or a hosting limit. It also notes that an active PHP session can interfere with REST API and loopback requests, and that an inability to reach api.wordpress.org means your site cannot check for or install updates. To test, deactivate security plugins on staging and retest. See WordPress REST API error if the editor is also failing.
The Info tab lists inactive themes and plugins, and the documentation recommends removing inactive themes you do not plan to use. The same logic applies to plugins you no longer need: every installed plugin is something to keep updated. Delete only after a backup and after checking that nothing depends on the plugin. If Site Health says your site does not use HTTPS, ask your host to enable a certificate, then update your site address in Settings → General.
The documentation describes recommended improvements as items that are not critical but should be modified for better security and performance. Some will not apply to you, and some depend on your host, for example a persistent object cache or optional PHP extensions. Do not install a plugin just to turn a line green. Ask: does this affect my security, my speed or my ability to update? If not, note it and move on. A perfect score is not the goal; a site you can safely update and restore is.
Not always, but treat it as a to-do for this week. The documentation describes critical issues as potential security vulnerabilities or serious performance issues.
No. Aim for no critical issues and a clear reason for each recommendation you skip.
Usually a firewall, security plugin, hosting rule or login wall is blocking the site from calling itself.
Review it first. It lists versions, paths and plugin names, which you may not want to publish.
Related guide: Contact Form 7 Not Sending Email? Sender, SMTP, SPF and Spam Fixes
Related guide: WordPress Mixed Content Warnings After Installing SSL: Fix “Not Secure”
Sort the warnings into risky and optional, and fix the risky ones one at a time. If WordPress Site Health still shows a problem you cannot explain, send the exact message and the Info export (after checking it) to your host or developer. If you would like a person to look, wpallsolution offers independent plugin support and website security help. We cannot promise a fix without seeing your setup.
Last reviewed: October 21, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation or Automattic.
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Most break-ins start at the login screen. Use this practical checklist for passwords, two-step login, admin accounts, attempt limits and HTTPS.
Care plans give agencies steady work after launch. See how white label WordPress maintenance works, what to include and what to agree…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout