Point a schedule at a page, or at a sitemap and get the whole section. It captures at the hours you choose, in the time zone you choose, without anyone remembering to press a button.
For a page you need the history of: terms, prices, a policy, a statement.
https://example.org/terms
One schedule covers a whole section of a site, and keeps covering it as pages are added.
https://example.org/sitemap.xml
Hours are read in the schedule's own time zone. A run lands at the same wall-clock time every period rather than drifting.
| Cadence | Fires |
|---|---|
| Hourly | Every hour, at the minute you choose. |
| Daily | At each hour you list. 6,12,18 is three a day. |
| Weekly | On the weekdays you pick, at each hour listed. |
| Monthly | On the days of the month you pick, at each hour listed. |
Both sitemap types are read: a urlset of pages, and a
sitemapindex followed one level down. Gzipped sitemaps are
unpacked automatically. Every address is screened before it is fetched.
| Limit | Value | Why |
|---|---|---|
| Pages per run | 20 default, 100 max | Set per schedule when you create it. |
| Sitemap files read | 12 | A huge index costs twelve requests, not hundreds. |
| Sitemap size | 12 MB | Measured after unpacking. |
| Whole traversal | 45 s | A sitemap that will not load does not hold up captures. |
| Captures outstanding | 5 | A run is skipped rather than queued behind itself. |
Scheduled and sitemap captures come with the paid plan, billed only for the storage you keep. Start free, and subscribe when you need them.