Choose a page check frequency

Choose a page interval based on detection needs and local crawl load.

Last checked 21 August 2026

Choose the slowest interval that still detects an important problem soon enough for you to act. TechDash offers four page intervals:

  • Every 15 minutes: high-risk pages where a short detection window is worth the additional local crawl load
  • Hourly: important pages that change often or support time-sensitive campaigns and releases
  • Daily: normal monitoring for important pages, and the standard default for new pages
  • Weekly: stable or lower-priority pages where slower detection is acceptable

A practical starting point

Start most pages at Daily. Move only a small, deliberate set to Hourly or Every 15 minutes, such as:

  • A checkout, lead form, or other critical conversion page
  • A frequently deployed homepage or campaign landing page
  • A page with a history of accidental redirects, noindex directives, or broken templates
  • A page being watched closely during a release

Use Weekly for stable reference pages and representative template samples where a seven-day detection window is acceptable. Frequency does not change which enabled checks run. It changes when the page next becomes due.

Understand the resource cost

Page checks use this computer's browser, network, CPU, memory, and local storage. The approximate scheduled demand per enabled page is:

  • Every 15 minutes: 96 checks per day
  • Hourly: 24 checks per day
  • Daily: 1 check per day
  • Weekly: about 1 check every 7 days

Multiplying a fast interval across hundreds or thousands of URLs can create a backlog and keep the computer busy. For example, 100 pages at Every 15 minutes represent about 9,600 scheduled page checks per day before other site work. Monitor the URLs that matter and use representative pages for shared templates.

Open Queue Status to see waiting and active page work, worker counts, backlogs, and website pressure. If waiting work keeps growing, reduce the number of monitored pages, slow some intervals, or adjust Concurrent Crawls within the hardware limit.

How timing actually works

An interval is a due-time target measured from the page's last completed check. It is not a promise to start at an exact wall-clock time.

TechDash normally sweeps for due pages once a minute. It orders due work and admits only as many pages as available worker slots allow. A crawl then waits in the page-check queue if all workers are busy. Slow sites, large pages, and a large due set can move execution past the nominal interval.

While the computer is on battery power or the screen is locked, TechDash uses twice the configured interval when deciding whether a page is due. A Daily page is therefore due after about two days if the stretched condition remains in effect. The saved frequency itself does not change.

Offline status and captive Wi-Fi sign-in stop due pages from being admitted. Due work is reconsidered on later scheduler sweeps after connectivity returns. Paused websites, disabled pages, portfolio-wide pause, and an unusable license also prevent normal scheduled admission.

Set or change the frequency

To change one page:

  1. Open Websites and select the website.
  2. In Monitored Pages, select the page path.
  3. Under Interval, select Every 15 minutes, Hourly, Daily, or Weekly.

The selection saves immediately. It does not run the page immediately. Select Run now if you also need an immediate check.

To set all current pages on a website to one interval, edit the website's Check frequency and select Save changes. This replaces every page-specific interval on that website.

Schedules this setting does not change

Page frequency does not alter separate schedules for robots.txt, sitemap, llms.txt, favicon, SSL, domain, DNS, Google Search Console, or brand assets. Those jobs use their own schedules and queues.

If checks run later than expected

Check Queue Status, page Enabled state, website pause state, tray-wide monitoring state, internet connectivity, license status, battery power, and screen lock. If the queue is persistently backlogged, a faster interval is not producing faster detection and should be reduced.

If a page remains stale beyond its applicable interval after those conditions are cleared and a manual request also fails to complete, open Help & Support. Include the TechDash version, operating system, hostname and path, saved interval, last-check text, power and lock state, request time with time zone, and screenshots of the row and Queue Status.

Related articles