Incidents you can trust.
Two consecutive failures plus a second location agreeing means an alert is a real outage, not a blip on one network path.
- Confirmation from a second location
- Downtime duration on recovery
- Incident history
Uptime monitoring that alerts you before customers notice
Check your site from outside on a schedule, confirm a failure before it becomes an incident and see uptime, response time and certificate expiry in one place.
TL;DR
Too long; didn't readShow summaryHide summary
How does uptime monitoring work?
Uptime monitoring requests your site on a fixed interval and records whether it responds correctly. BigRank checks the status code, optionally a keyword, the response time and the SSL certificate, and opens an incident only after a failure is confirmed.
- How often is my site checked?
- Every 10 minutes on Pro, every 5 minutes on Max and every minute on Ultra.
- How are false alarms avoided?
- An incident opens after 2 consecutive failures and confirmation from a second check location.
- Will I know before my SSL certificate expires?
- The monitor tracks SSL certificate expiry as part of its checks.
- How am I alerted?
- By email, in the app, and as a signed webhook to n8n, Zapier or your own code.
How uptime checks work
Every check uses the same expected status, optional keyword and timeout, at your plan's interval. An incident opens only after two consecutive failures and confirmation from a second location, so an alert means a real outage.
Check intervals
Checks run at your plan's interval: 10, 5 or 1 minute.
- Every 10 minutes on Pro
- Every 5 minutes on Max
- Every minute on Ultra
Status and keyword checks
Set the expected status code and, optionally, a keyword that must appear on the page, along with a timeout.
- HTTP and HTTPS URLs
- Error pages served with a 200
- Response time on every check
Second-location confirmation
A failure is confirmed from a second check location before an incident is opened.
- Two failures in a row first
- No alert from one network blip
- Confirmed before any email
Incidents
Incidents open after 2 consecutive failures, close on recovery and record how long the downtime lasted.
- Downtime duration per incident
- Current status on the Overview
- Shown in report uptime sections
SSL expiry
The certificate expiry date is tracked as part of each check.
- Expiry date per monitored site
- Checked with no extra setup
- Stored with each check result
Response time
A response-time chart and the average response time show slowdowns before they become outages.
- Response time on every check
- Kept in a time-series store
- Old data downsampled automatically
Alerts
Email and signed webhook alerts for site down and recovered events, plus the in-app notification center.
- In-app notification center
- Signed webhooks for n8n and Zapier
- Planned: Slack and Telegram
Status page
Planned: a public page where your visitors can check whether the site is up.
- Planned: one page per project
- Planned: on a custom subdomain
- Planned: no login needed to view
Checks that look at content.
A page can return 200 and still be broken. Add a keyword check to catch an error page that looks healthy.
- Expected status code
- Optional keyword-present check
- Configurable timeout
Uptime in the context of the whole site.
The Overview shows current status, 30-day uptime, average response time and a response-time sparkline next to your crawl and search data.
- 30-day uptime percentage
- Last check time
- Response-time sparkline
SEO MCP
Ask your AI assistant about Uptime Monitoring.
Ask your assistant whether every monitor is up, what the 30-day uptime is, or how fast the last check responded.
From setup to peace of mind
An uptime alert is only useful if you trust it. Tune the check once, let confirmed incidents reach you by email, and use the history to spot problems that keep coming back.
Add the monitor
It starts automatically when you finish project onboarding.
Tune the check
Set the expected status, a keyword and a timeout.
Get alerts
Get email alerts when the site goes down and when it recovers.
Review incidents
Use incident history and response times to find recurring problems.
When teams monitor uptime
Uptime monitoring earns its place whenever availability is at risk or has to be proven: busy launch weeks, hosting moves, certificates close to expiry and client agreements.
Launch weeks
Watch availability while traffic is at its peak.
Hosting changes
Compare response times before and after moving providers.
Certificate hygiene
Keep an eye on SSL certificate expiry alongside availability.
Client SLAs
Show clients their 30-day uptime and incident history.
Down, slow or rated poorly: what are you checking?
Start with Uptime Monitoring when the question is whether visitors can reach the site at all, then turn to PageSpeed Monitoring for slow loads and to Core Web Vitals for how pages feel once they arrive.
Uptime Monitoring
Know within minutes when the site stops responding, with each failure confirmed from a second location before anyone gets an alert.
PageSpeed Monitoring
When the site is up but slow: see each key URL's daily Lighthouse score and the opportunities that would speed it up.
Core Web Vitals
When pages load but feel sluggish: find out whether loading, layout stability and responsiveness are rated Good for real visitors.
Keep going
Look beyond up or down
A site can respond and still struggle. Follow its daily speed score, check which status codes bots receive, and include uptime in the reports you send to clients.
Uptime Monitoring FAQ
Answers about automatic setup, what each check covers besides the status code, incident history, alert channels, the planned status page and uptime in client reports.
Does the monitor start automatically?
Yes. The uptime monitor starts when you finish project onboarding.
What is checked besides the status code?
Optionally a keyword on the page, plus the response time and the SSL certificate.
How long is incident history kept?
Incidents are kept as a history with their downtime duration. Older check data is downsampled automatically to keep it compact.
Can I get alerts in Slack?
Through a webhook: send alerts to n8n or Zapier and post them to Slack from there. Direct Slack and Telegram channels come later.
Is there a public status page?
Not yet. A public status page for each project, on a custom subdomain, is planned.
Can uptime go into a client report?
Yes. Uptime is one of the sections you can choose for a white-label PDF report.
SEO that fits your budget
Plans start at $19/month with a 7-day free trial. Every plan includes the site audit, Search Console insights and white-label reports.