Monitoring and alerts

Hear about it before the client does.

A noindex tag shipped on Friday, a certificate that expires next week, a homepage that went down at 3 a.m. Semhack watches every site you audit and tells you when something important changes.
fernhillcoffee.comExample
UpChecked every 5 min

99.97% uptime, last 30 days

SSL certificate

41 days left

Alerts start 14 days before it expires.

  • Site down or back up fernhillcoffee.com is back up after 14 minutes.Oct 19
  • Audit score dropped /shop/cold-brew went from 91 to 79.Oct 22
  • Page became noindex /wholesale now has a noindex tag.Oct 24

Uptime and SSL

Starts on its own after a site’s first audit.

  • Homepage uptime

    Checked every 5 minutes by default; you can choose up to every 60 minutes, or pause it. A site counts as down after two failed checks in a row, and as back up on the next success.

  • History that lasts

    Uptime for the last 24 hours, 7 days and 30 days, every incident with its duration, and hourly and daily summaries kept long after the raw checks.

  • SSL certificates

    Read once a day. You’re warned 14, 7, 3 and 1 days before a certificate expires, and straight away if it isn’t trusted.

Scheduled re-audits

The same audit, every day or every week.

Each monitored page is re-audited on its schedule and compared with its previous audit. That’s how Semhack notices a page that turned noindex, a robots.txt rule that now blocks Google, or a score that fell after a release. How many pages you can monitor depends on your plan.
  • The homepage is added automatically; add the pages that matter most
  • Daily or weekly per page, spread through the day
  • “Run now” whenever you’ve just shipped a fix

Alert rules

10 rules, all on by default
  • Site down or back up

    The homepage failed two checks in a row, and when it recovers.

  • SSL certificate expiring

    Fewer than 14 days left, or the certificate isn’t trusted.

  • Audit score dropped

    A monitored page scores 5 or more points below its previous audit.

  • Important check started failing

    A high-importance check passed last time and fails now.

  • robots.txt blocks Google

    robots.txt now stops Googlebot from crawling a monitored page.

  • Page became noindex

    A monitored page now tells search engines not to index it.

  • Search Console clicks drop

    A new traffic drop in a client’s Search Console data.

  • Mentions in comments

    Someone @mentions a member in a comment on an action. Only that member is told.

  • Overdue actions

    Monday reminder to each member about actions assigned to them that are past their due date.

  • Tracked keyword moved

    A tracked keyword’s Search Console average position moved 3 or more places week over week, or it lost all impressions.

Core Web Vitals

Speed over time, for the pages you monitor.

  • On the same schedule

    Monitored pages also get a PageSpeed Insights test on a phone and a desktop, daily or weekly like their re-audits, so you can see LCP, INP, CLS and the Lighthouse score change over time.

  • A history per site

    Each monitored site has a Core Web Vitals view with one point per test day and Google’s good and poor thresholds drawn in.

Alerts

Signal, not noise.

  • Where alerts go

    To the bell in the app and to each member’s email, and if you set one up, to Slack or your own webhook. Every member chooses whether they want alert emails and the weekly digest.

  • Switch rules off

    Any of the rules can be turned off for the whole workspace if it doesn’t matter for your clients.

  • No floods

    The same alert stays quiet for a while after it fires, emails are bundled and capped per hour (critical ones first), and a page’s first audit never alerts.

  • Monday digest

    One email on Monday morning: uptime, downtime and certificate days left per site, score changes, new issues and the week’s top actions.

  • Search Console too

    When a new traffic drop appears in a client’s Search Console data, or a tracked keyword moves, it arrives as an alert like any other.

  • Straight to the problem

    Each alert links to the report, the monitored site or the action it’s about.

Honest limits

What it doesn’t do

  • Uptime is checked from our server, on the homepage only. It isn’t a multi-region probe network or a public status page.
  • Scheduled re-audits use the same HTML-only audit as the rest of Semhack: they don’t run JavaScript.
  • Alerts come in the app, by email, and to Slack or webhooks if you add them. There are no SMS or phone calls.
  • Scheduled Core Web Vitals tests run only when PageSpeed Insights API access is set up on our side, and cover a few monitored pages per workspace each hour.

Audit a site once. Semhack keeps watching.

Monitoring starts on its own after a website’s first audit, on every plan.