ARN Smart Support
Language: English

Monitor WordPress sites

Updated 9 Nov 2026 5 min read
Browse ARN Connect articles

ARN Connect checks every connected WordPress site automatically, keeps the site's inventory with its history and gives every site a health colour with the reasons behind it.

Where to find it: Sites in the sidebar, and the page of each site.

ARN Connect illustration of site health cards with HTTP, TLS, REST and Agent checks and a site inventory

Automatic checks

The checks start with the application and keep running in the background while its window is closed.

CheckInterval
HTTP status, response time, TTFB (time to first byte) and TLS certificate (expiry date and issuer)Every 5 minutes
WordPress REST APIEvery 5 minutes
Signed Agent heartbeatEvery 5 minutes
Full inventory from the AgentEvery 30 minutes, or at once when the Agent reports a plugin, theme, WordPress or fatal error change
For a site added with http://: does https:// work on the same host, and if not, whyEvery 6 hours (local test hosts are skipped)

A failed availability check is confirmed again after 30 seconds before the site is marked offline. Requests that are refused with 401, 403 or 429, or a Cloudflare challenge, count as blocked, not offline.

To check a site at once, click Check now on its page, or tick several sites on the Sites list and click Check now.

Health colours

Every site has a colour, and every colour comes with the reasons that set it. Red overrides everything, then grey, then yellow.

ColourExamples of reasons
Red (Critical)Site offline, including server errors and certificate errors; TLS certificate expired; PHP fatal errors in the last hour; a recent update failed its post-update checks
Grey (Unknown)The Agent has not answered yet, is unreachable, or is no longer paired with this installation
Yellow (Attention required)Availability check blocked; TLS certificate expires within 14 days; REST API blocked or not answering; PHP fatal errors in the last 24 hours; maintenance mode active; paused plugins or themes; WP-Cron overdue; PHP errors displayed to visitors in production; high-risk updates waiting; a performance warning; an interrupted remote action; Site Health critical issues
Green (Healthy)No open problem

Some reasons are notices that do not change the colour, for example Remote changes are disabled on the site.

The Sites list

The Sites list is sorted by severity. It shows each site's availability, Agent state, WordPress and PHP versions, waiting updates, SSL, last local backup, response time and last check. Filter it by colour or client, or search by name, host or client. See Manage your sites for the selection actions.

The site page

The header shows the site's colour, environment, the level of your connection and its client, with Check now, AI summary (when AI is turned on), PDF report, Edit, Disconnect and Delete. Below it, you see how fresh the data is: availability check, Agent heartbeat, last sync and Agent version. The reasons behind the colour follow, each with Share.

TabWhat it shows
OverviewWordPress, PHP, database and server, users, security and SSL, Site Health (from ARN Connect 0.13.0), backups, ARN products, connection, client and critical URLs
Plugins & themesInstalled plugins, themes, must-use plugins and drop-ins with versions and state; activate or deactivate plugins
UpdatesWaiting updates, the update lock and rollback copies
MonitoringAvailability, response time and TTFB charts
ErrorsThe PHP fatal errors the Agent captured
ActionsRead-only actions and changes such as clearing caches or maintenance mode
OperationsEvery operation on this site with its verdict
BackupsBackups of this site and Backup now
TimelineEvery event of this site in order
ConnectionsOnly for the Owner: the installations connected to the site

Site Health (from ARN Connect 0.13.0). The Site Health card on the Overview tab lists the WordPress Site Health tests the Agent ran: first the critical and recommended ones, each with its WordPress title (in the site's language) and its test name, then the passed tests and the tests the Agent does not run, folded under their counts. The Agent runs WordPress's direct tests; tests that need a request from the site to itself or to the internet run only in wp-admin → Tools → Site Health.

Critical URLs. On the Overview tab, use + Add URL to add pages that must keep working, for example the shop or the contact page. They are checked before and after every update, in addition to the homepage and the REST API.

Site inventory

The Agent reports configuration facts, and ARN Connect keeps every change as history instead of overwriting it:

  • WordPress version, Multisite, environment type, debug settings, WP-Cron and REST state;
  • PHP version, limits and extensions; database engine, version and size; web server; disk space where the host allows it;
  • plugins, themes, must-use plugins and drop-ins with versions, active state, automatic update state, requirements and dependencies;
  • WooCommerce template overrides in themes and the available updates;
  • installed backup plugins with their last backup time, and installed ARN products;
  • users as counts per role only, without names or email addresses.

A value the site cannot report is shown as unavailable, with the reason.

Monitoring gaps

When the computer is off or the application is closed, nothing is checked. ARN Connect records these periods as monitoring gaps and shows them in the site's history and in reports. A gap is never counted as time the site was available.

No internet, no false alarms. While the computer has no internet connection, for example while it goes to sleep, just after it wakes up or just after it starts, nothing is checked or recorded. A sleeping laptop therefore does not report its sites as offline. The time counts as a monitoring gap, the automatic checks show that they are waiting for the network, and the checks continue by themselves when the connection is back.

For checks around the clock, keep ARN Connect running on a computer that stays on.

Sites added with http://

A site that still uses http:// can only be added as a local or development site. Its page says that monitoring data travels unencrypted, although requests and answers stay signed. When https:// works on the same host, the SSL column shows that the address can be switched; a broken certificate is named with its reason, such as expired, another host name or self-signed. See Manage your sites for Switch to https.

On this page

Submit a ticket

Create a new support request without needing a portal account.

Priority
Attachments
Only you and our staff see a ticket. Never send passwords or licence codes.

Track a ticket

Use the ticket number and password from your confirmation email.

The number and the password are in your confirmation email.

Sign in

Access your support portal account.

New here?

Create account

Create your support portal account.

Already have an account?

Forgot password?

We email you a link to choose a new password.

Conversation

Was this helpful?
Open full article
↑ ↓ to moveEnter to openEsc to close