Help centre

Add a site by its address. SEOComet looks for robots.txt, sitemaps, ads.txt and app-ads.txt, adds uptime and SSL checks, and runs them all straight away.

Checks run on a schedule and report issues. Most issues open an incident, which alerts you when it opens, gets worse and is resolved.

How often uptime, watched pages, robots.txt, sitemaps, news sitemaps, ads.txt and SSL are checked on each plan.

What critical, warning and info mean, which of them open incidents and send alerts, and why a suggestion never does.

What the robots.txt check looks for: blocked search engines, blocked important paths, watched crawlers, removed Sitemap lines and every change.

How SEOComet reads sitemaps and sitemap indexes, and when it reports a sitemap that’s missing, unreadable, empty, shrinking or stale.

How a news sitemap is checked: how often, when it counts as stopped, articles too old for Google News, missing news tags and the spot-check.

How SEOComet watches ads.txt and app-ads.txt: a file that goes missing, lines that must be present, syntax errors and a diff of every change.

When a page counts as down or slow, and what the page check reads when it answers: noindex, canonical, title, description, H1, blank pages and your text.

SEOComet checks that the other versions of your home page address, with or without www and https, redirect to your home page.

When SEOComet warns about a certificate that’s about to expire, and why an expired, untrusted or mismatched certificate is always critical.

Add a list of pages for uptime and the page check in one go, as paths or full addresses, and what SEOComet does with each line.

A robots.txt, sitemap or ads.txt a site doesn’t have is watched quietly, then checked in full once it appears. app-ads.txt is only checked when it’s there.

Every setting a check has, its default and what changing it does: URL drops, stale sitemaps, slow pages, required text, certificates and more.

How an incident opens, gets worse, reminds you, is muted or marked resolved, and closes on its own once a check no longer finds the issue.

Choose which incidents send alerts for the whole account, then change it for one site or turn that site’s alerts off.

Send alerts by email, to Slack or to a signed webhook, test a channel, and check webhook signatures on your own server.

A daily or weekly email about what happened on your sites, sent in the morning in your time zone. It’s off until you turn it on.

Get alerts when Google starts or finishes a core update, another ranking update or a Search incident, and choose which ones you hear about.

Who can see and change what: Can edit and Can view, all sites or selected sites, the owner, and sites another account shares with you.

Invite someone by email to your account or to one site, what they can do once they accept, how long an invitation lasts and how to resend it.

Stop seeing a site or an account someone shared with you: what you lose, what their account keeps, and how to get access again.

What deleting your profile or an account you own removes, what happens to its sites and subscription, and what to do before you delete.

What each plan includes: sites, watched pages per site, how often checks run, alert channels, people and history, and what happens at a limit.

Move to another plan or billing period, and what happens to sites, checks, people and channels that are over the new plan’s limits.

Why SEOComet couldn’t fetch an address, from timeouts to firewalls, and how to let SEOCometBot through bot protection.

Work through why an alert email didn’t arrive: alert level, muted incidents, the site’s own alerts, unconfirmed addresses and spam folders.