Using Intercrawl
Audits and alerts
The daily check of your installed site, and the messages Intercrawl sends when something changes.
Audits
Once your site is verified, Intercrawl audits it every day: it finds up to 100 of your pages the way the free scan does, and requests each one as a visitor and as each crawler, through your install. The dashboard shows the results, and for each crawler view whether it was served by Intercrawl (from its cache or a fresh render) or by your own server.
Audit requests are signed, so your install recognises them and answers them exactly as it would answer that crawler. They are never counted as crawler visits.
You can also run an audit yourself from the dashboard: at most once every 60 minutes, and 3 times a day (UTC) per site.
Alerts
After each audit, Intercrawl can tell you about:
- pages that newly differ for a crawler,
- an install that stopped serving (crawlers were served by Intercrawl before and are now served only by your own server),
- pages that match again,
- a daily digest.
Choose the events and channels per site on the Alerts page:
| Channel | Where it goes |
|---|---|
Your account's own address, from alerts@intercrawl.com | |
| Slack | A Slack incoming webhook URL (https://hooks.slack.com/services/...) |
| Webhook | Any public https address of yours, as a signed JSON POST |
Each channel has Send test alert, so you can see a message arrive before an audit sends one.
Verifying webhook messages
Every webhook request carries X-Intercrawl-Signature: t=<unix seconds>,v1=<signature>, where the signature is the hex HMAC-SHA256 of <t>.<request body> with your endpoint's secret (shown on the Alerts page, starting with whsec_). Compute it on your side, compare, and reject a request whose t is more than a few minutes old. X-Intercrawl-Event is audit.completed (or test), and X-Intercrawl-Delivery identifies the delivery. Webhooks are not redirected.