WebGee Docsالتوثيق
Performance & Caching

Site Quality Monitoring

Turn on uptime and health monitoring for a domain from cPanel — what it scans, how often, and what the free allowance covers.

Site Quality Monitoring watches a domain for downtime and scans it for problems that affect how visitors and search engines see it. Applies to shared, reseller and Premium hosting on cPanel.

It is off until you create a project. Nothing is monitored by default.

What the included allowance covers

The Site Quality Monitoring introduction, listing the included allowance

Included
Monitored domains1
Uptime scansEvery hour
Full health and performance scansWeekly
Manual crawlUp to 20 pages

The hourly uptime check is the part worth having. It tells you your site went down before a customer does, which is the single most useful thing monitoring provides.

The weekly full scan looks for the common issues that quietly cost you traffic — broken links, missing metadata, slow pages, mixed content.

One domain is included. If you host several sites, monitor the one that matters commercially, and rely on the weekly scan plus your own checks for the rest.

Turn it on

The Create Project form, with the monitored domain, notification address and consent checkbox

  1. In cPanel, select Site Quality Monitoring in the left-hand menu.
  2. Choose the Monitored domain.
  3. Enter the Email Address that should receive notifications.
  4. Tick the consent box.
  5. Select Create Project.

Use an address you actually read, and preferably one not hosted on the account being monitored. A downtime alert delivered to a mailbox on the server that is down does not reach you.

After it is running

The first full scan takes a little time; uptime checks begin straight away.

Treat the results as a list to triage rather than a score to maximise. Fix what affects visitors — broken links, slow pages, mixed content — before anything that only affects the number.

What it does not do

It monitors from outside, so it sees what a visitor sees. It cannot tell you why a page is slow.

For that, use the server-side tools:

If monitoring reports intermittent downtime, the cause is often resource limits rather than an outage — see Resolve the 503 resource limit error.

On this page