How often checks run
How often uptime, watched pages, robots.txt, sitemaps, news sitemaps, ads.txt and SSL are checked on each plan.
Updated
Your plan sets how often each kind of check runs. It’s the same on every site in the account, and there’s no setting to change. Every plan checks robots.txt, sitemaps, ads.txt, app-ads.txt, the homepage and SSL. Plans differ in sites, watched pages and how often checks run.
Speeds per plan
| Check | Free | Pro | Business |
|---|---|---|---|
| Homepage uptime | every 5 minutes | every minute | every minute |
| Watched pages | every hour | every 30 minutes | every 15 minutes |
| robots.txt | every hour | every 5 minutes | every 5 minutes |
| Sitemaps | every hour | every hour | every 30 minutes |
| Google News sitemaps | every hour | every 15 minutes | every 10 minutes |
| ads.txt | every hour | every hour | every hour |
| app-ads.txt | every hour | every hour | every hour |
| SSL certificate | every day | every day | every day |
A sitemap with Google News tags is read on the news sitemap row, because a news sitemap goes stale in hours. As soon as a check finds the tags, the sitemap moves onto that interval. See Google News sitemaps.
If you change plan, every check on every site moves to the new plan’s speeds at once: a shorter interval brings the next check forward, and a longer one never pushes back a check that was already due sooner. See Plans and limits.
Run now
Run now on a check’s page queues that check straight away, outside its schedule. You can also select several checks on the Checks page and run them together. To run every check on a site, choose Check all now on the site’s page, or Check everything now in the site’s row menu on the Sites list. Select several sites there and choose Check now to run them all. The result shows in the check’s History when it finishes, usually within seconds.
- You need Can edit on the site to run its checks.
- A paused check doesn’t run. Resume it first.
- If the check is already queued or running, nothing extra is queued.
- Running a check by hand doesn’t move its next scheduled run.
There are limits a minute, so a busy account can’t flood the queue: 10 run requests a person (running a selection counts as one), and 30 checks across the whole account. When you hit one, wait a minute and try again.
When the next check runs
A check’s next run is one interval after its last scheduled run. Say a check runs every hour and last ran on schedule at 10:00: its next check is at 11:00. Running it by hand at 10:20 doesn’t change that.
The next check time shows in the Next check column on the Checks page and in Next checks on the Overview. A paused check shows Paused instead, and has no next check until you resume it.
Overdue and Due now
Due now means the check’s time has come and it’s waiting in the queue. That usually takes seconds, so you rarely see it for long.
Overdue means the check should have run by now and hasn’t: its last run is a little more than twice its interval ago. Instead of a next check time, it shows when it was due, such as “Was due 2 h ago”. Hover over the badge to see when it last ran and how often it should.
An overdue check is almost always a delay on SEOComet’s side, not a problem with your site. Nothing about your site changes while a check waits, and it runs as soon as the queue catches up. If SEOComet’s scheduler stops, every page shows a banner that says “Checks are delayed. We’re looking into it.” until the scheduler is running again.
If a check stays overdue and there’s no banner, email us at the address below.