OVERVIEW · SITE HEALTH

Watch your site from GitHub Actions
— with no SaaS subscription

Three small workflows cover the whole job: daily checks of uptime, SSL certificates, security headers and compliance basics; smoke tests after every deploy; and automatic validation of bug reports from visitors. All free, all running inside your own repository.

The three parts of the stack

1. Daily monitoring: uptime, SSL, headers and compliance →

A cron workflow that runs every morning and verifies the site responds, the SSL certificate isn't expiring soon, security headers are intact, and GDPR basics are still in place. Replaces monitoring SaaS at $10–15/month.

2. Smoke tests after every deploy →

“The deploy succeeded” and “the site works” are two different questions. Two workflow steps check both after every release — uptime and a compliance scan — so a deleted privacy policy or broken redirect is caught immediately.

3. Bug reports straight from visitors →

Let visitors report bugs with a tiny on-page script, then let CI validate each report before it goes anywhere. Bugs become structured data in your repo instead of an inbox nobody reads.

Get started in ten minutes

  1. Start with daily monitoring — most value for the least work.
  2. Add smoke tests once you deploy more often than about once a week.
  3. Add the bug-report form if you have real visitors who might hit problems.

Try the compliance part right now

No repository needed to see what the scanner finds on your live site — free, no signup, results in about a minute.

Scan your site for free →