Loading…
Skip to main content

Ignore rules

Ignore rules hide specific findings from your dashboard views so you can focus on actionable regressions. They are scoped to your account, one monitored site, one check type, and optionally a single URL.

On this page

When to ignore vs fix

Ignore rules are for findings you have reviewed and deliberately accept—not for hiding problems you plan to fix later.

Prefer ignore when… Prefer fix when…
The check is a false positive for your stack (for example a third-party script you cannot change). The issue affects SEO, crawlability, or accessibility and you control the page.
One legacy URL is intentionally different and you only want to silence that page. The same check fires on many URLs—you likely need a template or site-wide fix.
You track the exception elsewhere and still want deploy diffs for everything else. CI or your team uses raw finding counts to gate releases—fix or configure checks instead of hiding signal.

Ignoring never changes what was stored on a completed crawl. It only changes how your signed-in dashboard summarizes runs for that site.

Rule scope: site + check + optional URL

Each ignore rule has three parts:

  • Site — The monitored sitemap you selected on the dashboard. Rules do not carry over to other sites on your account.
  • Check — The finding type (for example MissingMetaDescription). See the SEO checks reference for what each check means.
  • URL — Optional. When set, the rule applies only to that page. When omitted, the rule applies to all pages for that check on the site.

You must be signed in with GitHub to create or remove rules. Anonymous try-a-scan reports do not offer ignore controls.

Per-URL vs all-pages rules

Open a completed run from run history, scroll to the Findings card, and use the Ignore dropdown on a finding group or individual row.

Option Effect
On this page only Suppresses that check for one URL. Other pages with the same check still appear. Available from the row action menu when a finding lists a specific page.
On all pages Suppresses every occurrence of that check on the site—present and future runs in your dashboard views. Available from the issue-group header or any row menu.

After you add a rule, click ignore rule(s) in the findings header to expand the list of active rules for the current site.

“Suppressed” badge in finding groups

When ignore rules hide findings, the report still shows that something was filtered out:

  • The findings header may show a gray suppressed badge with the total count hidden across all issue types.
  • Each issue group can show its own suppressed badge next to the error/warning/info counts.
  • If every occurrence of a check is ignored, the group badge reads Ignored and the check name is dimmed.
  • Expand the group to see suppressed rows: faded table lines with an Ignored badge on each page, so you can confirm what was hidden and undo per row.

Suppressed rows are visible in the report for transparency; they are excluded from headline counts and top-issue ranking.

Undo ignore

Remove a rule when you want findings to surface again:

  • Issue group fully ignored — Click Undo ignore on the group header (removes the all-pages rule for that check).
  • Single suppressed row — Click Undo on that row to remove the most specific matching rule (per-URL or all-pages).
  • Active ignore rules panel — Expand ignore rule(s) and click Remove next to any listed rule.

Changes apply immediately on the dashboard. The next time you open a run, counts and listings reflect the updated rule set.

Effect on dashboard counts and top issues

Ignore rules adjust how the dashboard summarizes the selected site. Suppressed findings are excluded from:

  • Overview cards — Error, warning, and info totals on the latest run card.
  • Trend chart — Historical error and warning points when run detail is available.
  • Top issues — Ranked issue types from the latest complete run; fully ignored checks drop off the list.
  • Run history — Per-run severity counts in the history table (for runs whose page detail has been loaded).
  • Findings table — Visible occurrence counts and severity badges; suppressed items move to the faded rows described above.

Per-URL rules need page-level data for precise counts. When detail is not loaded yet, the dashboard may approximate using all-pages rules only until history rows are preloaded. See Reading your report for how overview and top issues fit together.

Effect on deploy diffs

The deploy diff card compares this run to a baseline using the full stored crawl—ignore rules do not filter deploy diff output. New vs baseline and resolved lists, diff chips, and CI-facing regression counts still include ignored checks unless you fix them on the site.

That split is intentional: ignore rules quiet known noise in your personal triage views, while deploy diffs and CI keep showing what actually changed between runs.

For baseline selection and how new vs resolved findings work, see Baselines and diffs. Pipeline gating is covered in CI and GitHub Actions.

Next steps