Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Backups & maintenance · Guide

How to Monitor Uptime, Errors and Changes on WordPress

Short answer

To monitor a WordPress site, turn on Jetpack Downtime monitoring or add the site to UptimeRobot for uptime alerts, check Tools > Site Health each week, and read wp-content/debug.log after errors appear. Add a change log or activity log plugin so you can see who changed what. Together, these four checks catch downtime, errors, and unwanted changes early.

Key takeaways

  • Jetpack checks your home page every 5 minutes and is free with no paid plan needed.
  • UptimeRobot Free covers 50 monitors with 5-minute checks as of November 2026.
  • Site Health lives at Tools > Site Health and flags critical and recommended fixes.
  • The WordPress error log lives at wp-content/debug.log when logging is turned on.
  • A downtime alert alone does not prove the cause, so check the log before you act.

What does monitoring a WordPress site cover?

Monitoring a WordPress site means watching uptime, errors, and changes so problems reach you before visitors report them.

Most sites need four checks. Uptime checks ask if the home page loads. Error checks ask if PHP or WordPress wrote a fatal error.

Site Health checks ask if the setup still meets WordPress needs. Change checks ask if a file, plugin, or setting changed without a clear reason.

You do not need all four on day one. Start with uptime alerts, then add Site Health and the error log. Add change tracking once the first three run on a set routine.

SignalToolHow often
UptimeJetpack Monitor or UptimeRobotEvery 5 minutes, automatic
Site HealthTools > Site HealthWeekly
PHP errorswp-content/debug.logAfter each alert
ChangesActivity log pluginWeekly

How do you set up uptime monitoring with Jetpack?

Turn on Jetpack Downtime monitoring at Jetpack → Protect → Settings, and it checks your home page every 5 minutes.

First, install and activate the Jetpack plugin, then connect it to a WordPress.com account. Jetpack's own support page says downtime monitoring needs a working Jetpack connection, and it is a free feature that does not require a Jetpack plan as of November 2026.

  1. Go to Jetpack → Protect in WP Admin and click the Settings tab.
  2. In the Downtime monitoring card, turn on “Enable downtime monitoring”.
  3. Turn on “Email me when my site goes down and comes back up” if you want both alerts.
  4. Check that the address shown matches your WordPress.com account address.

On Jetpack versions before 16.4, the same setting sits at Jetpack → Settings → Security. If the standalone Jetpack Protect plugin is active, the Protect page does not show, and the older path applies instead.

The Protect page Overview tab shows your uptime for the last 40 days, day by day. Hover over a day to see if the site was up or how long it was down. That 40-day view helps you spot a pattern, such as daily drops at the same hour.

How do you monitor uptime with UptimeRobot instead?

Create a free UptimeRobot account, add your home page URL as an HTTP monitor, and pick email as the alert channel.

UptimeRobot's pricing page lists a Free plan at $0 per month with 50 monitors and a 5-minute check interval as of November 2026. No credit card is needed for that plan. Paid plans start with Solo, which lists 60-second checks.

  1. Sign up at UptimeRobot and open the dashboard.
  2. Click Add New Monitor and choose HTTP(s) as the monitor type.
  3. Enter a friendly name and your full home page URL.
  4. Leave the interval at 5 minutes on the Free plan.
  5. Add your email under alert contacts and save the monitor.

UptimeRobot checks from outside WordPress, so it still works when a plugin breaks your site. Jetpack does the same job from its own servers. Pick one as your main alert source, and use the other only if you want a second view.

If your site sits behind Cloudflare, note that a cached copy can hide a dead origin server. Jetpack's support page warns that its monitor may see the cached copy and miss downtime at the origin as of November 2026.

How do you check Site Health each week?

Open Tools > Site Health, read the critical items first, then work through the recommended items one by one.

WordPress added Site Health in version 5.2, and the WordPress.org documentation places it at Tools > Site Health. The Status tab groups findings as critical, recommended, or good, with a short fix note under each item.

Start with anything marked critical. Common critical items are an old PHP version, a failed loopback request, or a plugin that needs an update. Fix one item, then reload the page to confirm it clears.

Next, open the Info tab and expand Server. Note the PHP version and the WordPress version.

WordPress.org recommends PHP 8.3 or greater as of November 2026, with MariaDB 10.11 or MySQL 8.4 or greater. If your host still runs PHP 7.4, ask for an upgrade, because that version has reached end of life.

Use the “Copy site info to clipboard” button before you ask a host or plugin maker for help. That copy gives them the versions and server facts they need, and it beats a screenshot. For more on host needs, see the guide to WordPress hosting requirements.

How do you read the WordPress error log?

Turn on logging in wp-config.php, reload the broken page once, then open wp-content/debug.log and read the newest fatal error lines first.

WordPress logging needs three lines in wp-config.php, placed before the line that says “That's all, stop editing!” The developer handbook at Debugging in WordPress gives this exact set:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

WP_DEBUG turns debug mode on. WP_DEBUG_LOG writes errors to wp-content/debug.log.

WP_DEBUG_DISPLAY set to false keeps errors off your public pages, so visitors do not see raw messages. The handbook says these tools are meant for local and staging installs, not for long use on a live site.

Read each line from left to right. The date comes first, then the error type, then the message.

The file path and line number come last. A line that says “PHP Fatal error” breaks a page.

A warning is a note to keep. Notices and deprecated notes can wait unless they flood the file.

The folder name after plugins/ or themes/ in the path names the plugin or theme at fault. Copy that one line, with the date and the path, when you ask for support. Turn logging off when you finish, by setting WP_DEBUG back to false.

How do you track file and content changes?

Use an activity log plugin that records logins, plugin changes, post edits, and setting changes with a date and a user name.

WordPress core does not keep a full change history on its own. Jetpack keeps an activity log for Jetpack-connected sites, and many security plugins add their own log. Pick one log and check it on the same day each week.

Look for four kinds of entries. New admin users you did not create need a fast check.

Plugin installs or deletions you did not plan need a question to the person who made them. Theme file edits outside a planned update need a review. Settings changes to the site URL or admin email need a check right away.

If a change has no clear author, change the passwords for every admin account and review the active plugins list. A change with no author is a sign to look at the error log and the Site Health screen in the same session.

Keep the log for at least a few weeks. A short log helps you link a change to a problem that shows up days later, such as a form that stopped sending mail after a plugin update.

How do you read a downtime alert and act on it?

Open the site in a private browser window first, then read the alert status code before you change anything.

Jetpack marks a site down only after checks fail, and its support page explains the checks as of November 2026. It pings the home page every 5 minutes with an HTTP HEAD request.

A code of 400 or more, more than three redirects, or no reply within 20 seconds marks the site as tentatively down. Three more servers in other places then check it, and only if all three fail does Jetpack send the alert.

The alert email carries a reference number with a status word at the end. Jetpack lists these meanings: “server” means a 5xx reply, often a fatal error from a theme or plugin.

“blocked” means a 403 reply. “client” means another 4xx reply.

“intermittent” means the request timed out after 10 seconds. “redirection” means a redirect loop or too many redirects.

Follow this order when an alert arrives. First, load the home page yourself. Second, check the error log for a fatal error at the same time.

Third, check your host status page for a known outage. Fourth, turn on logging if it is off, and note the time of the alert.

If the site loads fine for you, the alert may be a false positive. Jetpack notes that a slow home page can trigger one, since a load over 20 seconds counts as down.

A host that blocks the Jetpack user agent can also trigger one, so ask your host to allow jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com).

You can test that user agent with curl, as Jetpack's support page shows. A 200 reply means the monitor can reach the site. Replace the example domain with your own domain before you run it.

curl -IA "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)" https://example.com

How often should you check each signal?

Check uptime alerts as they arrive, Site Health weekly, the error log after each problem, and the change log weekly.

Uptime alerts need a same-day look, even if the site is back up when you open it. A short outage that repeats each day points to a server limit or a scheduled task, and you will miss the pattern if you ignore single alerts.

Site Health needs a weekly slot of about 10 minutes. Open it after updates, not before them, so you see the result of the change. After a WordPress, theme, or plugin update, reload the front page and the admin, then open Site Health.

The error log needs a look after each alert, each white screen, and each failed update. If the log is empty after a real error, logging may be off, or the host log may hold the entry instead. Ask your host where its PHP error log lives.

The change log needs a weekly look on the same day as Site Health. Pairing the two checks keeps the routine short, and it links a change to a problem while both are still fresh. For context on how much downtime costs in lost visits, see website downtime statistics.

What mistakes should you avoid?

Do not rely on one check, do not leave debug logging on for months, and do not ignore single alerts.

The most common mistake is watching uptime only. A site can return a 200 code while the checkout, the contact form, or the search page is broken. Open a key page yourself after each update, not just the home page.

A second mistake is leaving WP_DEBUG_LOG on with no end date. The log file grows, and the handbook warns that the file can be read by others if it sits in a public folder. Turn it off when the problem is fixed, and delete the old log file.

A third mistake is muting alerts after one false positive. Fix the cause instead, such as a slow home page or a blocked user agent, then watch the next week of alerts. If alerts stop, the fix worked.

A fourth mistake is restoring a backup before you know the cause. A restore can hide the error for a day, then the same plugin update breaks the site again.

Read the log first, then decide if a restore is the right fix. If you need that step, follow the guide to restore a backup with UpdraftPlus.

If alerts keep coming and the log names no plugin, ask your host. Give them the alert times, the status word from the email, and the copied Site Health info. That set lets support check server limits instead of guessing.

Frequently asked questions

Is Jetpack Monitor free?

Yes. Jetpack's support page says Downtime monitoring is a free feature and does not require a Jetpack plan as of November 2026. You still need the Jetpack plugin installed and connected to a WordPress.com account before you can turn it on.

How often does Jetpack check my site?

Jetpack checks your home page every 5 minutes with an HTTP HEAD request. If a check fails, three more servers in other locations check the site before Jetpack marks it down and sends an alert, which helps cut false alarms.

Why did I get a downtime alert when my site loads fine?

The most common causes are a slow home page, too many redirects, or a host that blocks the Jetpack monitor. Jetpack treats a load over 20 seconds as down, and a redirect loop also triggers an alert, so check speed and redirects first.

Should I leave WP_DEBUG on all the time?

No. Turn it on only while you chase a problem, then turn it off. The WordPress developer handbook says these tools are meant for local and staging installs, and a debug log left in a public folder can expose error details.

What is the difference between uptime monitoring and Site Health?

Uptime monitoring asks if the site loads right now and alerts you when it does not. Site Health asks if the setup is sound, such as the PHP version, updates, and server checks, and it lists fixes before a small issue becomes downtime.

Sources

  1. Monitor your site's uptime and downtime Jetpack
  2. Plans and Pricing UptimeRobot
  3. Site Health: keep your website healthy WordPress.org
  4. Debugging in WordPress WordPress Developer Resources
  5. Requirements WordPress.org
  6. WordPress Hosting - Push Environments Kinsta

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test