Skip to content
SEOComet

Everything SEOComet watches, and how it tells you

Add a site and SEOComet sets up its checks for you: robots.txt, the sitemaps robots.txt lists, ads.txt, app-ads.txt, uptime for the home page and, for https sites, the SSL certificate. Problems become incidents, and alert rules send them where your team will see them.

Checks

Each monitor checks one address on its own schedule and keeps its history. Run any of them by hand with Run now.

The checks SEOComet runs and their default intervals
robots.txt New blocks on the whole site, on important paths or on watched crawlers, removed Sitemap lines, and every change, with a diff. Default: every hour
Sitemaps Missing or unreadable sitemaps, failed child sitemaps, empty files, URL counts that drop and lastmod dates that stop moving. Default: every 6 hours
ads.txt and app-ads.txt Files that disappear, expected seller lines that go missing, records that don’t parse, and every change, with a diff. Default: every hour
Uptime Downtime and wrong status codes after a run of failed checks, slow responses, and redirects that land somewhere new. Default: every 5 minutes
SSL certificate Certificates that are about to expire, have expired, don’t cover the host name or aren’t trusted. Default: every 12 hours

Intervals can be shortened to your plan’s minimum: every hour on Free, every 5 minutes on Pro and every minute on Agency. Pause a single monitor or a whole site when you need quiet, and tag monitors to group them in alert rules.

Incidents

When a check finds a problem, SEOComet opens an incident for it, marked critical, warning or info. One incident covers the problem for as long as it lasts, however many checks see it.

  • Open, acknowledged, resolved

    Acknowledge an incident to tell the team you’re on it; reminders stop for that incident. It resolves on its own when a later check no longer finds the problem.

  • Escalation

    If an open problem gets worse, say a sitemap drop that goes from warning to critical, the incident escalates and rules can alert on that separately.

  • Changes close themselves

    A change, such as an edited robots.txt or a new redirect, is reported once. Its incident closes on the next check rather than waiting for a fix that isn’t needed.

  • Pausing is quiet

    Pausing a monitor or a site closes its incidents without sending a “resolved” alert.

Mock-up of the SEOComet Incidents list: a critical robots.txt block, a warning about a sitemap that lost 41% of its URLs, an expiring certificate, an ads.txt change and a resolved downtime incident.

Alert rules and channels

A rule says which incidents to send and where. Every workspace starts with one, “Warnings and critical”, which sends anything at warning or above to every channel you add.

Mock-up of a SEOComet alert rule: when severity is at least warning, the check type is robots.txt or sitemap and the monitor tags include shop, send opened, escalated, resolved and still-open reminders to a Slack channel and a signed webhook, with a 60 minute cooldown and reminders every 4 hours.
Mock-up of a SEOComet alert in Slack: "New issue: robots.txt on Shop", saying robots.txt now blocks every crawler from the whole site, with the changed lines and a View incident button.

Conditions

Match on severity, check type, issue, site, monitor or monitor tags, with “all of” and “any of” groups. Before you save, see which incidents from the last 7 days the rule would have matched.

Events

Send when an incident opens, escalates or resolves, and optionally a reminder every few hours while it stays open and nobody has acknowledged it. A cooldown spaces out repeats.

Slack

Through an incoming webhook. Messages carry the severity, site, check, the issue, up to 10 changed lines and a link to the incident. Text from your files is escaped, so it can’t ping @channel.

Signed webhooks

A JSON POST with X-SEOComet-Signature, an HMAC-SHA256 of the timestamp and body. Retries keep the same X-SEOComet-Delivery id, so your server can drop repeats.

Email

To workspace members and other addresses you add. Addresses outside the workspace confirm before they get alerts.

Retries

A delivery that fails is tried 5 more times, after 1 min, 5 min, 15 min, 1 h and 4 h. Each channel page lists what was sent and whether it arrived, and Send test shows you a sample.

Workspaces and the activity log

Keep each client or project in its own workspace, with its own plan, members and alert setup. Switch between them from the palette.

  • Roles

    Each workspace has one owner, who controls its plan and billing. Invite others as admins, members or viewers.

  • Activity log

    Every change to sites, monitors, members, incidents, alert rules, channels and the plan, with who made it and what changed. Filter by person, type, site and date. Kept for 30 days on Free, 90 days on Pro and 90 days on Agency.

  • Check history

    Kept for 7 days on Free, 90 days on Pro and 90 days on Agency.

Mock-up of the SEOComet Activity log: who acknowledged an incident, changed an alert rule, added a Slack channel and changed a check interval, and when the plan changed.

Command palette and shortcuts

Everything is a few keys away. The palette searches every site and monitor in the workspace and runs the common actions.

Mock-up of the SEOComet command palette, searching for "shop" and listing a matching site, two monitors and commands such as Add a site and Invite someone.
Search or run a command (Ctrl K on Windows and Linux)
⌘K
Search this page
/
Go to Overview
GO
Go to Sites
GS
Go to Monitors
GM
Go to Activity
GA
Show every keyboard shortcut
?

Add your first site free

The Free plan covers 1 site with 6 monitors and email alerts. No card needed.

Get started free See pricing Open dashboard