Skip to content
Start free trial

Website health monitoring

Find broken pages on every scan

On every scan Rookflare checks the status code, redirects, JavaScript errors, images and search settings of each page. A failure opens an issue with the request, the error and a screenshot.

Start monitoring See pricing
Sample Issues page: five issues across client websites, led by a critical server error 500 on the Northwind Shop checkout. The open detail shows a JavaScript error on the Northwind Shop homepage with its HTTP status, final address, JavaScript error, latest screenshot and page checks.

Checks

What a scan looks at besides the screenshot

Technical failures do not wait for a review. They open an issue at once, with one alert for each issue at or above the severity you chose.

Status codes

Server errors and redirects

Each page request is logged with its status code and response time. Redirects are followed, and a page that starts redirecting somewhere else opens an issue.

  • Any 4xx or 5xx response opens an issue
  • The issue shows where the page ends up now and before
  • GET https://northwind-shop.example/ 200 142 ms
  • GET https://northwind-shop.example/tents/ 200 168 ms
  • GET https://northwind-shop.example/sale/summer 301 → /tents/
  • GET https://northwind-shop.example/tents/kestrel-2p/ 200 189 ms
  • GET https://northwind-shop.example/checkout/ 500 1.2 s

Issue opened for https://northwind-shop.example/checkout/

JavaScript

Errors thrown while the page loads

Uncaught errors and console errors are recorded with their message and grouped across the pages of a website.

  • One issue per error, listing every page that shows it
  • Uncaught errors are medium, console errors low
Console · https://northwind-shop.example/checkout/ × 14

✕ Uncaught TypeError: Cannot read properties

of undefined (reading 'total')

Failed to load resource: the server

responded with a status of 500

Images

Images that fail to load

Every image request is checked. A failed image is listed with the page and the image address.

  • Listed per page with the address that failed

https://northwind-shop.example/tents/: tent-ridgeline.webp returned 404

Search settings

Noindex, title and canonical

A noindex robots tag or a missing title is flagged on every scan, and a changed title or canonical address is compared with the previous scan, so an accidental noindex shows up on the next scan.

  • Title and canonical changes open low or medium issues
https://northwind-shop.example/tents/ · head Flagged

title: Tents & shelters · Northwind Shop

robots: index, follow

robots: noindex

canonical: https://northwind-shop.example/tents/

Uptime

Whether key pages answer between scans

On Growth and Agency, Rookflare also requests your key URLs as often as every minute and alerts you when one is down and when it is back up.

  • Down only after repeated failures and a confirmation check
  • Warnings for expiring SSL certificates and slow responses
https://northwind-shop.example/checkout/ Up for 12 days · 184 ms Up
Last 30 days 99.95% uptime
1 outage · 22 min Checked every minute

After deploy

Scan right after you deploy

On Growth and Agency, your CI or host calls one URL with a secret token when a deploy finishes, and Rookflare scans the website straight away instead of waiting for the next scheduled scan.

  • Ready snippets for GitHub Actions, Vercel, Netlify, WordPress and cURL
  • Repeated calls for the same deploy start only one scan

Demo: someone copies the GitHub Actions step, the next deploy calls the deploy hook and Rookflare starts a scan of the website right away.

Scan after deploy

Your CI or host calls one URL with a secret token after each deploy. Repeated calls for the same deploy start only one scan.

Growth and Agency plans
Endpoint
https://app.rookflare.example/api/webhooks/deploy
Token
pgd_••••••••••••3f9a
Last used
Yesterday 17:40 Just now
Scan after deploy started Deploy 4f1a9c2 from GitHub Actions · just now

Add the token as the ROOKFLARE_DEPLOY_TOKEN repository secret, then add this step after your deploy step.

- name: Scan with Rookflare after deploy if: success() run: | curl -fsS -X POST "https://app.rookflare.example/api/webhooks/deploy" \ -H "Authorization: Bearer ${{ secrets.ROOKFLARE_DEPLOY_TOKEN }}" \ -H "Content-Type: application/json" \ -d '{"ref": "${{ github.sha }}"}'

Sample endpoint and placeholder token

FAQ

Questions

Something missing here? Send us a message

Do I need to install a script on my website?

No. Rookflare visits your pages from the outside, the way a visitor would. You add a website, verify that you control the domain, and choose the pages to monitor.

How often are pages scanned?

Starter scans once a day, Growth every 12 hours and Agency every 6 hours. Scan frequency is fixed per plan; you can choose a longer interval, but not a shorter one.

How is uptime checked and when do you alert?

Rookflare requests each uptime URL on a schedule: every 5 minutes on Growth and every minute on Agency. A page counts as down only after 3 failed checks in a row and a failed confirmation check, so one slow response does not wake anyone. After a failed check, the next checks follow about a minute apart, so an outage is confirmed about 2 minutes after the first failed check on both plans. You get one email or Slack alert when it goes down and another when it is back up, with how long it was down.

What happens when a page looks different?

Rookflare opens an issue that needs review, with the changed areas outlined. Someone on your team approves the new screenshot as the baseline or marks the change as expected. If the change is a mistake, fix the page and the issue resolves when it matches the baseline again. Technical failures such as a 500 response open an issue straight away.

Which technical checks run on every scan?

By default, each scan records the status code and load time of the page, follows redirects and flags a new redirect target, lists JavaScript errors thrown while the page loads, checks that images load, flags a noindex robots tag or a missing title, and compares the title and canonical address with the previous scan.

Will I get the same alert twice?

No. You get one alert when an issue opens. If the next scan finds the same failure, the issue is updated and no new alert is sent, unless the problem gets worse.

Do uptime checks warn about anything besides downtime?

Yes, about two things that are not outages yet: an SSL certificate that expires within 14 days, and a page that answers much slower than it usually does. Both show up as warnings, so you can fix them before visitors notice.

Can Rookflare scan right after I deploy?

Yes, on Growth and Agency. Create a deploy hook in the website settings and call its URL with the secret token when a deploy finishes. The dashboard gives ready snippets for GitHub Actions, Vercel, Netlify, WordPress and cURL. Rookflare then scans the website straight away instead of waiting for the next scheduled scan, and repeated calls for the same deploy start only one scan.

Start monitoring your website

Add your address, pick the pages and approve the first scan as your baseline.

Start monitoring Talk to us

Plans start at €19 per month. Prices are provisional.