New: the Sitejar partner program

Integration

Sitejar Slack integration

The Sitejar Slack integration posts a message to a Slack channel when a scan of one of your sites needs attention: the overall score drops by your threshold, a new Confirmed High finding appears, a security header goes missing, or a scan fails. It works through a Slack webhook url you create, so Sitejar installs nothing in Slack and never reads from it.

On Agency Plus.

What the Sitejar Slack integration does

Alerts in Sitejar are rules on a site: when this happens, tell these people. A Slack channel is one more place a rule can tell. Each alert is one line that names the site and what changed, followed by a link to the report, so whoever sees it in Slack can open the scan in one click.

Every message follows the same pattern. These are the four, as they read:

  • Score dropped 7 points on example.com (82 to 75), followed by the report link.
  • 2 new Confirmed High findings on example.com.
  • A security header is missing on example.com.
  • The scan of example.com failed.

Sitejar posts it to Slack as a plain text message. It carries the site, scores and counts, never what was found on the page.

Who Slack alerts are for

Teams that watch a shared Slack channel rather than an inbox. Agencies use it to give each client's sites their own channel, so the people responsible for that client see that client's alerts and nothing else. In-house teams use it to catch a regression the morning after a release, before a customer does.

Adding a channel is for an Owner or Admin of the Sitejar workspace. Choosing it on a site's alert, on the site's Schedule and alerts tab, is open to anyone whose role can manage sites (Owner, Admin or Editor).

Get website scan alerts in Slack

Catch a score drop after a release

A score drop alert compares each completed scan with the site's previous completed scan and posts when the overall score fell by at least the points you set, between 1 and 100. The default is 5.

Hear about new serious problems, not old ones

A new Confirmed High finding alert posts only for findings first seen in that scan, at High or Critical severity and Confirmed confidence. Likely and Needs review findings never alert.

Notice when a security header disappears

A security header alert posts when a scan finds a security header missing that the site had before, or that has gone missing again after a fix.

Know a scan failed without checking

A scan failed alert posts when the scan of the site could not finish, so a broken scheduled scan does not go unnoticed for a week.

How to connect Slack to Sitejar

  1. In Slack, create an incoming webhook for the channel you want alerts in and copy its url. Slack sets incoming webhooks up through an app in your own workspace, and the url starts with https://hooks.slack.com/services/.
  2. In Sitejar, as an Owner or Admin, open Settings, then Alert channels.
  3. Under "Add a channel", choose Slack in "Where", give it a "Name" of up to 80 characters (such as #site-alerts), paste the url into "Webhook url", and choose "Add channel".
  4. Open the site you want alerts for and go to its Schedule and alerts tab.
  5. Choose what to alert on in "Alert me when" (for a score drop, set "By at least (points)"), tick the Slack channel under "Also post to", tick anyone who should also get an email, and choose "Add alert".

A rule can post to up to 10 channels, so one alert can reach both your team's channel and a client's.

What Sitejar sends to Slack, and what it stores

What a Slack alert contains

The site's host, what happened (the old and new score, a count of findings, or that the scan failed), and a link to the report in Sitejar. Never finding evidence, page content, or anyone's email address.

Permissions Sitejar asks for in Slack

None. There is no sign-in to Slack and no scope to grant. The webhook url is the whole credential: whoever holds it can post to that one channel, and that is all Sitejar does with it.

What Sitejar stores

The channel's name, its kind, the url encrypted with AES-256-GCM, and the host to show (hooks.slack.com). The url is never shown again after you add it, never returned to the browser and never logged. Sitejar also keeps when the channel last received an alert and the last error, if any.

Sitejar keeps no personal data from Slack. It only posts, and the only thing it reads back is whether Slack accepted the post.

Removing a channel stops alerts at once, and the url is not kept, so adding it back means pasting it again.

What happens after each scan

When a scan of the site finishes, Sitejar checks every alert rule that covers it and queues one post per rule and channel. A rule fires at most once per scan, so a scan that is looked at twice never posts twice.

Three rules keep alerts worth reading. A site's first scan never fires a finding alert, because everything in it is new. Needs review findings never alert. A site marked "This is a staging site" never sends alerts at all.

If Slack does not answer, or answers with an error, Sitejar tries again, up to five attempts in all. An alert that still has not gone out after 24 hours is dropped rather than posted late, and the channel shows the last error in Settings, Alert channels.

Which plans include Slack alerts

Alert channels (Slack, Microsoft Teams and your own signed webhook url) are on Agency Plus. Email alerts on the same rules are on Business and above. To see everything each plan includes, compare plans on the pricing page.

Slack alert limits

  • Sitejar accepts only a Slack incoming webhook url: https, on hooks.slack.com, under /services/.
  • Up to 10 channels on one alert rule.
  • A channel name of up to 80 characters.
  • Each post waits at most 10 seconds for an answer, follows no redirects, and goes only to a url that resolves to a public address.
  • Up to five delivery attempts, and nothing older than 24 hours is posted.

Troubleshooting Slack alerts

"A Slack incoming webhook url starts with https://hooks.slack.com/services/."

The url you pasted is not one Sitejar accepts for Slack. Copy the webhook url again from Slack, and check it is not a link to the channel itself.

The channel shows "Last attempt: The channel answered 404"

Slack no longer accepts that url, usually because the webhook or the channel was deleted. Create a new webhook in Slack, add it as a channel, choose it on your alerts, and remove the old one.

An alert I expected did not post

Check the rule on the site's Schedule and alerts tab is On and has the channel ticked, that the site is not marked as a staging site, and that the scan was not the site's first. A score drop compares with the previous completed scan, so a failed scan in between does not count.

"Alert channels are not available right now"

Sitejar cannot store channel urls at the moment. Nothing you entered was saved. Try again later.

Slack alerts FAQ

What alerts can Sitejar post to Slack?

Four kinds: the overall score drops by at least the points you choose, a new Confirmed High finding appears, a security header goes missing, and a scan fails. Each is a rule on a site, and each post links to the report.

Does Sitejar read messages from Slack?

No. Sitejar only posts to the webhook url you give it. The only thing it reads back is whether Slack accepted the post.

Can different sites post to different Slack channels?

Yes. Add each channel once in Settings, Alert channels, then choose the right one on each site's alerts. One rule can post to up to 10 channels.

Which plan do I need for Slack alerts?

Alert channels are on Agency Plus. Email alerts on the same rules are on Business and above.

Why did my first scan not send a Slack alert?

A site's first scan never fires a finding alert, because every finding in it is new. A score drop needs a previous completed scan to compare with. Alerts start from the second scan.

Is the webhook url safe in Sitejar?

It is encrypted with AES-256-GCM before it is stored, never shown again after you add it, never sent to the browser and never logged. Only the host is displayed.

Does Sitejar install an app in my Slack workspace?

No. Sitejar never installs anything in Slack and never reads from it. You create the incoming webhook in Slack yourself, and Sitejar only posts to that url.

Last updated . Slack and the Slack logo are trademarks of Slack Technologies, LLC. Sitejar is not affiliated with or endorsed by Slack Technologies, LLC.