Review and remove ignored-check rules

Understand ignored-check scopes and restore a suppressed check from the Ignored Checks list.

Last checked 21 August 2026

Ignoring a check suppresses matching findings from open Incidents and every notification channel at the scope you chose. Monitoring and result collection continue. Use the Ignored Checks card when you want to review those rules or show a check again.

Review ignored rules

  1. Open Notifications from the sidebar.
  2. Scroll to Ignored Checks.
  3. Review the check name, website group, and scope detail.

The card groups website-specific rules under the website name. Global rules appear first under All websites. Each row shows the check name and one of these scope details:

  • A path such as /pricing means the rule applies to that exact monitored URL on that website.
  • This website means the check is ignored across that website.
  • All websites means the same check is ignored throughout the portfolio.

If there are no rules, the card shows No ignored checks.

Understand matching

An ignore rule matches the check ID as well as its scope. Ignoring one check does not suppress every incident for the URL or website.

  • URL scope matches the same check, website, and path.
  • Website scope matches the same check on that website, regardless of path.
  • Global scope matches the same check on every website.

Sitewide incidents do not have a URL path. Their Ignore This menu offers website and global scope only. Page incidents also offer URL scope.

You create these rules from an incident's Ignore This menu using the exact options Ignore check for this URL, Ignore check for this website, or Ignore check on all websites.

Choose the narrowest scope that matches your intention. For example, ignore a title-length check for one intentionally unusual landing page at URL scope rather than hiding that check across every client website.

Remove a rule

  1. Find the rule you no longer want.
  2. Select Remove rule.
  3. Wait for the confirmation Ignore rule removed.

The row disappears from Ignored Checks. If another copy of the same check exists at a broader scope, that broader rule can continue to suppress it. Review the entire list when a check remains hidden.

Removing a rule does not run a check or create a synthetic result. It removes the filter and refreshes derived incident data. If TechDash already stores a current failing result that matches the removed rule, the incident may reappear immediately without another crawl. This is the stored current failure becoming visible, not a new failure.

Use Check & Verify from the incident when available, or Run now for the monitored page, to collect fresh evidence. If the check passes, the expected result is Good and the incident closes. If it still fails, the incident remains with updated evidence.

Notification transition rules still apply. Removing a rule does not itself send a desktop, Slack, Microsoft Teams, or Discord alert. An already stored failure becoming visible is not necessarily a new failure notification. Future new failures, qualifying severity escalations, and eligible recoveries follow the normal channel settings.

Understand severity and Health Score

Good means the check passed. Good does not open an incident or lower Health Score. An open Advisory identifies a lower-impact concern, Warning identifies a meaningful risk to areas such as visitors, crawling, indexing, reporting, or renewals, and Critical identifies the highest likely impact, such as serious access or certificate problems.

Current open incidents influence Health Score by severity: Advisory has weight 1, Warning weight 4, and Critical weight 10. An ignored finding is excluded from the open set, so adding or removing a rule can change Health Score without changing the underlying website. Removing a rule can lower the score as soon as a stored failure becomes visible. The Health Report may briefly show cached data.

Built-in Warning and Critical incidents can notify; built-in Advisory incidents do not. Custom Checks follow their own Notify option. Delivery also requires the global channel configuration and the affected page's channel toggle under Notify. If the newly visible incident later passes, Notify when a check recovers controls whether eligible channels receive a recovery.

If the check does not return

Confirm:

  • The monitored page and website are enabled.
  • The relevant check is enabled for that page.
  • No website or global ignore rule for the same check remains.
  • The latest stored result still meets the incident criteria.

A problem that has a stored failing result can reappear until you rerun the check. Use fresh evidence to determine whether the problem is still present.

If no incident returns but you need current evidence, run Check & Verify or Run now. A fresh Good result confirms the check currently passes. A fresh failure restores the incident with current evidence.

If Remove rule reports That ignore rule is no longer set., another app action or refresh already removed it. Reload Notifications and review Ignored Checks.

Ignore rules differ from Mark Resolved. An ignore suppresses matching current and future findings by scope. A manual resolution records the observed issue state and can reopen when the observed value changes.

Related articles