squirrelscan
GitHub

Emails we send

Every automatic email a squirrelscan account can receive, what triggers it, and how to turn it off

squirrelscan sends a small number of automatic emails. This page lists every one of them, what makes it arrive, and where the off switch is.

Most of them are per website and ride a single toggle. A few are account level and arrive whatever that toggle says, because they report something that affects your credits or a service switching itself off.

On top of that, Settings → Email has four account-wide switches: product news, tips and onboarding, scheduled audit digests, and account alerts. They belong to you rather than to a website or an organization, and they follow your account if your email address changes.

Per-website emails

These follow the website’s Email notifications toggle. Turn it off and none of them arrive for that site.

They go to your account address unless the website has its own. Set one in the Alert email field under Website → Settings → Alerts, for example to send a client’s site reports straight to the client. Audit complete, audit failed and the digest then go to that address instead. Clear the field and save to send them to your account address again. Account-level emails never use this address.

Audit complete

Arrives when an audit of the website finishes and its report reaches the cloud. That covers dashboard runs, scheduled runs, and CLI, API and GitHub audits that publish their report. It carries the health score and the error, warning and passing counts. The button opens the dashboard rather than that specific report, so you pick the run from the website’s audit history.

A scheduled run normally sends the digest instead, so you get one email about a run, not two.

How to stop it: turn off Settings → Alerts for that website (the email’s Alert settings for this website link opens it), or Account alerts in Settings → Email for every website (linked from the email’s footer, and the email’s one-click unsubscribe does the same).

Audit failed

Arrives when an audit run for the website ends in failure, with the reason and whether the run was scheduled. Failed audits are refunded automatically, so a failure never costs credits.

The reason names the cause the crawl hit, and the email carries the next step for that cause. See failed audits for every reason and what to do about it.

How to stop it: the same Settings → Alerts toggle, or Account alerts in Settings → Email, which the email’s footer links to. Its one-click unsubscribe switches off Account alerts too.

Scheduled-audit digest

Arrives after a scheduled audit completes, including the runs where nothing changed. It has three variants, and the subject line tells you which one you have before you open it.

VariantSent whenWhat is in it
What changedThe comparison found movementNew, fixed and worse counts, the leading new and worsened findings, and the score change
Nothing changedThe comparison ran and found nothingThe health score and the same three counts, all at zero
First auditThere is no earlier audit to compare againstThat run’s own error and warning counts and pages crawled, with no claim about change

Every variant carries the health score, a link to the full report, and a link that pauses the schedule without a login.

Two cases send the ordinary audit email instead. A scheduled run that fails sends the failure email, and a run whose comparison cannot be built falls back to the completion email rather than guessing at what changed.

How to stop it: the pause link in the email, the Settings → Alerts toggle, setting the website’s schedule to Disabled, or Scheduled audit digests in Settings → Email, which the email’s one-click unsubscribe switches off for you. With digests switched off there, a scheduled run sends no completion email in their place: the audits keep running and their results stay in the dashboard.

On the Pro and Team plans. Arrives after a scheduled audit of the website finds a link that the previous scheduled audit checked and found fine, and that is now dead: internal links, and external links while external link checking is on. A link the checker could not verify, such as one behind a bot wall, a rate-limited one, or a first failure still waiting for its confirming check, never counts. One email per run names up to 10 of the links and links to the report for the rest.

It has its own Broken link alerts switch under Website → Settings → Alerts, on by default, separate from external link checking and from the schedule. It also rides the website’s Email notifications toggle, and it compares scheduled audits only: a website with no recurring audits gets none, and its first scheduled audit has nothing to compare against, so alerts start from the second.

How to stop it: turn off Broken link alerts for that website, the Email notifications toggle, or Account alerts in Settings → Email for every website.

Account-level emails

These are not gated on any per-website toggle.

Recurring audits paused

Sent when a website’s schedule stops on its own. There are two reasons, and the email says which:

  • Three scheduled runs in a row failed. The usual causes are an unreachable site, a firewall or WAF blocking our crawler, or a URL that has moved. Those failed runs were refunded, so the pause costs you nothing.
  • The account balance fell too low to pay for even a one-page audit (the 50-credit base plus 2 for the page). The run was skipped without a charge, and the schedule paused rather than skipping again every cycle. A balance that covers some pages but not the site’s whole page limit still runs, with the page limit lowered to what the balance covers.

It goes to your account address, because a recurring service that spends credits switching itself off is account news. The email is throttled to roughly one per organization in any rolling 24 hours: if several sites pause around the same time, the rest still pause and still appear in the dashboard bell without each sending mail.

How to stop it: switch off Account alerts in Settings → Email, which the email’s footer links to, or use its one-click unsubscribe. It also only arrives when a schedule pauses itself, so turning the website’s schedule off means it never fires. The per-website Settings → Alerts toggle does not suppress it.

Low credits

Sent when a charge takes the organization’s balance down across the low-balance threshold, with the remaining balance, roughly how many more audits it buys, and a link to billing. It fires on the crossing, not on the level, so it does not repeat while the balance stays low. The next one is earned only once credits are added again, whether by a top-up, a monthly grant, a refund or an adjustment. Refunds carry one extra guard: a balance that crosses the line again within an hour of a refund records the warning in the dashboard bell but sends no email, so a failed charge that is refunded and retried cannot mail you twice about the same money.

It goes to one billing contact: the owner where there is one, otherwise another member who can bill, and failing both the person who created the organization.

How to stop it: switch off Account alerts in Settings → Email. Handing off the billing role also moves it to someone else, unless you created the organization, in which case you stay the fallback recipient.

Welcome

One email from Nik about an hour after you sign up. Replies go to a real inbox and open a support thread, so answering it reaches a person.

How to stop it: switch off Tips and onboarding in Settings → Email before it comes due. Replying reaches a person but does not unsubscribe you on its own.

Support ticket confirmation and replies

Opening a ticket from support sends a confirmation with your ticket reference. Every reply from us arrives by email too, and you can answer by replying rather than returning to the dashboard.

How to stop it: these are answers to something you asked, so they have no toggle. They stop when the conversation does.

How often emails can arrive

Notification emails that also write a dashboard bell entry, which is audit complete, audit failed and the digest, are rate limited per account and per email type: at most one an hour, and at most five in any rolling 24 hours. Over the limit the email is dropped, but the notification still appears in the dashboard bell, in list_notifications over MCP, and on any webhooks that carry it. Nothing is lost, it just does not land in your inbox.

The low-credit warning and the pause notice are not on that counter. Each has its own limit instead: once per low-balance crossing, and roughly once per organization in any rolling 24 hours.

Several notification types never email at all and are in-app only, including issue comments, agent fix runs, and the scheduler’s skip notices.

Email settings and unsubscribing

Settings → Email in the dashboard has four switches, all on until you change them:

SwitchWhat it covers
Product newsAnnouncements and new features
Tips and onboardingThe welcome email and other getting-started emails
Scheduled audit digestsThe digest after each scheduled audit
Account alertsAudit complete, audit failed, recurring audits paused, low credits, and credits added to your organization

Billing emails, sign-in and security emails, and replies to your support requests are not on the list. They arrive whatever the switches say.

Every product news email carries an unsubscribe link, which switches off Product news and nothing else. The link asks you to confirm first, because mail scanners open every link in an email and must not unsubscribe anyone by doing so. If you subscribed to updates without an account, the link takes your address off the mailing list instead.

Digest and alert emails carry a one-click unsubscribe as well, the Unsubscribe button your mail app shows next to the sender. It switches off only the switch that email belongs to: Scheduled audit digests for a digest, Account alerts for audit complete, audit failed, recurring audits paused, low credits and credits added. Product news and the other switches stay as they are, and you can turn it back on in Settings → Email. The audit and paused-schedule emails also link to Settings → Email from their footer.

The one-click unsubscribe is only on mail sent to your account’s own address. Mail that goes to a website’s own alert address follows that website’s Settings → Alerts toggle instead, so turn it off there.

A hard bounce or a spam complaint stops all email to an address, whatever the switches say, and Settings → Email shows when that has happened. Once the mailbox works again, contact support and we will switch it back on.

An unsubscribe from an announcement before October 2026 also switched off tips and digests, so Settings → Email shows those off too. Switch any of them back on there.

Type to search…

↑↓ navigate↵ openesc close