Downtime, slow pages and expiring certificates, next to your SEO files
SEOComet checks your home page every 5 minutes by default, and any other page you add, for downtime, slow responses and new redirects. It reads your SSL certificate every 12 hours and warns you well before it expires.
Uptime
A failed check alone doesn’t page anyone. SEOComet counts failures in a row and opens an incident once the streak reaches your threshold, 2 to start with, so one dropped connection stays quiet.
| Issue | Severity | What it means |
|---|---|---|
Site down uptime.down | Critical | The address failed, or answered with the wrong status, on as many checks in a row as your alert threshold (2 to start with). |
Slow responses uptime.slow | Warning | The address took longer than your limit (5,000 ms to start with) to answer, on as many checks in a row as your alert threshold. |
Redirect changed uptime.redirect_changed | Info | The address now ends up somewhere different after its redirects, for example after a move to https or to a new domain. |
- Expected status
- 200 by default. Set a 3xx to check a redirect itself; SEOComet then compares the first response.
- Slow after
- 5,000 ms by default, anywhere from 100 to 9,000 ms.
- Alert after
- 2 failed checks in a row by default, from 1 to 10.
- Interval
- Every 5 minutes by default; as often as every hour on Free, every 5 minutes on Pro and every minute on Agency.
Each check follows up to 5 redirects and records the chain, which is how a new destination is spotted. Requests give up after 10 seconds. You can watch any address on the site’s own host and port.
SSL certificates
Every https site gets an SSL monitor when you add it. The check opens a TLS connection, reads the certificate and closes it, so it sends no HTTP request at all.
| Issue | Severity | What it means |
|---|---|---|
Certificate not trusted ssl.invalid | Critical | Browsers won't trust the certificate: it has expired, doesn't cover this host name, or its chain isn't trusted. |
Certificate expiring ssl.expiring | WarningCritical Warning under 21 days, critical under 7 | The certificate expires soon. Once it does, browsers show a security warning and most visitors leave. Both limits can be changed. |
A warning opens when the certificate has fewer than 21 days left, and it becomes critical under 7. Both limits can be changed per monitor. An expired certificate, one that doesn’t cover the host name, or one whose chain isn’t trusted is critical straight away.
Each check records the issuer, the names the certificate covers and its expiry date, so you can tell whether automatic renewal is still doing its job.
Add your first site free
The Free plan covers 1 site with 6 monitors and email alerts. No card needed.