Choose which pages to monitor

Build a focused monitored set that balances coverage and local crawl load.

Last checked 26 August 2026

Monitor URLs where an unnoticed change could affect traffic, revenue, leads, crawling, indexation, or user journeys. TechDash does not need every URL on a large website to provide useful change detection.

Start with business-critical pages

Build the first set from:

  • The homepage and major organic landing pages
  • Important category, product, service, pricing, contact, and conversion pages
  • Pages tied to current campaigns, releases, or high-value searches
  • URLs with important canonicals, hreflang, structured data, analytics, or custom requirements
  • Pages that have broken or changed unexpectedly before

The source URL entered when the website was created is added as its first monitored path. If that source URL included a path or query, TechDash uses that path rather than automatically using /.

Add representative template coverage

When many pages share a template, monitor representative examples instead of every variation. Include:

  • One or more examples from each important page type
  • Templates with different optional modules or layouts
  • Paginated, filtered, localized, or JavaScript-heavy variants when they behave differently
  • A small sample of old or rarely changed content if regressions there still matter

Representative coverage helps detect template-level changes without multiplying local browser work unnecessarily.

Consider cross-page findings

Some TechDash checks compare the monitored set, including duplicate titles, orphan signals, inbound-link changes, canonical and hreflang targets, and possible page retirement. Their conclusions describe the URLs TechDash monitors and the links observed during those checks. They are not a complete crawl of every URL on the public website unless you have chosen to monitor every URL.

Include enough connected, important pages for cross-page comparisons to be meaningful. Avoid describing a small sample as complete site coverage.

Choose an initial schedule

Start most pages at Daily. Use Hourly or Every 15 minutes only for a small set where rapid detection justifies the load. Use Weekly for stable, lower-priority examples.

Every page run uses local browser, network, CPU, memory, and storage resources. Thousands of URLs at fast intervals can keep queues backlogged and make the computer feel busy. The configured interval is a due-time target, not a guaranteed exact start time. Worker capacity, offline status, captive Wi-Fi, pause state, battery power, and screen lock can delay execution.

Open Queue Status after building the set. If waiting page work grows rather than clearing, reduce coverage, slow frequencies, or adjust Concurrent Crawls within the available hardware limit.

Ways to add pages

Use Sources after adding a website

After Add website, Sources collects candidate URLs from Search Console, Bulk URL Import, and links found on checked pages. Review Suggested Pages, then Add selected or Add all. This is the first-run path only. See Use Sources after adding a website.

Add one URL

In Monitored Pages, enter one complete HTTP or HTTPS URL with the exact website hostname, then select Add page.

Bulk-add a prepared list

Select Bulk Add, paste one absolute same-host URL per line, and review accepted and rejected results. This is useful for exports from analytics, a CMS, or another crawl tool.

Import from Google Search Console

After connecting the website to a matching Search Console property, select Import from GSC. Choose how many top pages to import. TechDash uses pages ranked by clicks over the last 28 days and skips paths already monitored or on another host. This is useful for traffic-led prioritization, but it may omit new pages and strategically important URLs with little search traffic.

Review the set over time

Revisit Monitored Pages after launches, migrations, product changes, and content pruning:

  1. Filter for old campaigns or retired sections.
  2. Remove pages that no longer need monitoring, or turn Enabled off for a temporary pause.
  3. Add new high-value URLs and new template examples.
  4. Check whether fast frequencies are still justified.
  5. Review Queue Status for sustained pressure.

Removing a monitored page excludes it from future page scheduling and portfolio comparisons. Disabling it preserves the page and settings while keeping it out of normal scheduled checks.

If important pages are missing checks

Confirm the page is listed and Enabled, its website is not paused, portfolio-wide monitoring is running, and the license is usable. Check connectivity and Queue Status. Battery power and a locked screen stretch due timing to twice the saved interval; they do not alter the saved setting.

If an enabled high-value page remains stale while comparable pages on the same website continue checking and no queue backlog is present, open Help & Support. Include the TechDash version, operating system, hostname and path, interval, last-check text, page and website states, request time with time zone, and screenshots of the page row and Queue Status.

Related articles