Enable or disable checks for one page

Skip irrelevant optional checks for one URL while keeping page monitoring active.

Last checked 21 August 2026

Disable an optional built-in check when it is not relevant to one URL. The page remains monitored, and its enabled checks continue to run at the saved interval.

Change the optional check set

  1. Open Websites and select the website.
  2. In Monitored Pages, find the URL. Use Filter pages if necessary.
  3. Select the page path to expand its controls.
  4. Under Optional checks, clear a checked item to disable it.
  5. Select an unchecked item to enable it again.

Each change saves immediately for that page. There is no separate Save button. The list shows the shipped page checks that can be controlled here by their current product documentation names.

Expected result

On future page runs, TechDash omits disabled evaluators for that URL. Other enabled checks still run normally. The page keeps its interval, Enabled state, notification settings, latest results, and history.

Changing the check set does not queue a run. Select Run now if you want a fresh check immediately. Otherwise, the new selection takes effect when the page next runs through normal scheduling.

Disabling a built-in check does not delete an existing incident, erase a prior result, or mark an issue resolved. Review the incident separately. Re-enabling a check allows it to evaluate again on a future run.

Availability checks cannot be disabled

The Optional checks list excludes the HTTP error and redirect gate checks. These availability checks always run when the page runs.

Gate checks establish whether TechDash received a usable response and whether later evaluation should proceed. If availability prevents useful analysis, later checks may be skipped or produce only the results appropriate to the response.

Some enabled checks also skip responses they cannot meaningfully evaluate. HTML-specific checks do not treat an XML sitemap, robots.txt response, or another non-HTML body as a normal HTML document. A small group of response-level checks can still run safely on non-HTML content.

Built-in checks and custom checks are separate

These controls apply only to built-in page evaluators. They do not enable, disable, edit, or delete:

  • A custom check scoped to this page
  • A sitewide custom check
  • Website-level site-resource, DNS, SSL, domain, Search Console, or finalize checks

Manage custom checks from the website's Custom Checks card. To stop every scheduled page run for this URL, use Enabled: Off instead.

When to disable an optional check

Disable a check only when its expectation is genuinely inappropriate for this page. Examples include a deliberate noindex utility page, a non-HTML resource, or a template that intentionally omits an element.

Avoid disabling a check simply because it currently reports a real problem. That hides future evaluation for the page and can make regressions harder to spot. If the finding is expected but you still want the check to run, use the incident's ignore workflow where appropriate.

Scheduling and offline behavior

Optional-check changes do not affect when the page is due or how much queue capacity is available. Enabled pages are considered by the scheduler according to their interval. Battery power or a locked screen stretches due timing to twice the configured interval. Offline or captive Wi-Fi prevents due work from being admitted until connectivity returns.

A manual Run now checks connectivity and license state, then queues the page without waiting for its interval. The page must still be Enabled and its website unpaused when the worker starts, or the worker skips the crawl. A completed run uses the currently enabled built-in checks for that page.

Troubleshooting

A check is not listed: It may be an always-on availability gate, a sitewide/finalize check, a site-resource or lookup check, a Search Console check, or a planned rather than shipped check.

The checkbox changed but old evidence remains: The control affects future evaluation. It does not rewrite historical results or incidents.

No checks run at all: Confirm that Enabled is On, the website and portfolio are not paused, the license is usable, and the computer is online. Check Queue Status for waiting work.

A custom check still runs: Manage it in Custom Checks. The built-in Optional checks list does not control custom rules.

If an optional-check selection does not persist after a full restart, or a disabled check produces a new result on a later completed run, open Help & Support. Include the TechDash version, operating system, hostname and path, exact check name, selected state before and after restart, run completion time with time zone, and a screenshot of Optional checks and Latest results.

Related articles