# Site Quality Monitoring
Source: https://docs.webgee.com/en/performance/site-quality-monitoring







**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 [#what-the-included-allowance-covers]

<img alt="The Site Quality Monitoring introduction, listing the included allowance" src="__img0" />

|                                   | Included       |
| --------------------------------- | -------------- |
| Monitored domains                 | 1              |
| Uptime scans                      | Every hour     |
| Full health and performance scans | Weekly         |
| Manual crawl                      | Up 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.

<Callout type="info">
  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.
</Callout>

## Turn it on [#turn-it-on]

<img alt="The Create Project form, with the monitored domain, notification address and consent checkbox" src="__img1" />

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 [#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 [#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:

* [Diagnose a slow website with PHP X-Ray](/en/performance/diagnose-slow-site-php-xray)
* [Understanding resource limits](/en/performance/understanding-cloudlinux-and-lve-limits-enhancing-server-stability-and-performan)

If monitoring reports intermittent downtime, the cause is often resource limits
rather than an outage — see
[Resolve the 503 resource limit error](/en/performance/understanding-and-resolving-the-503-error-resource-limit-reached).

## Related [#related]

* [Diagnose a slow website with PHP X-Ray](/en/performance/diagnose-slow-site-php-xray)
* [Mixed content errors](/en/security-ssl/what-are-mixed-content-errors-and-how-do-i-resolve-them)