Managing Findings and Suppressions

Critical

A likely blocker or high-impact problem requiring prompt attention.

Major

A meaningful problem that can hurt usability, trust, or conversion.

Minor

A real but lower-impact issue that should be handled during normal cleanup.

Severity helps you triage, but always review the description and evidence in the context of the page's purpose.

Choose Mark as Fixedafter the underlying website issue has been corrected. This changes the current finding's status but does not create a suppression rule. If the problem is still present, a later scan can report it again.

Choose Dismisswhen the finding is not actionable or should not be reported again in the selected scope. Scout requires a short reason and creates a rule for future findings with the same type and device and a similar description. Page-level rules can also use the finding's approximate position.

Page

Hide matching findings only on the current page.

Site

Hide matching findings across pages in the current site.

Account

Hide matching findings across all of your Scout sites.

Use the narrowest scope that solves the problem. Page is the safest default. Site and account scopes are useful only when the same accepted pattern genuinely repeats.

Scout previews how many currently reported findings appear to match the proposed rule at every scope. Read that estimate before saving. Site- or account-wide suppression of a Critical or security finding also requires an explicit confirmation checkbox.

Expand the Suppressed findings or Suppressed link findings section in scan history. Choose Unsuppress to disable the matching suppression rule, restore that finding to the reported state immediately, and allow future matching findings to appear again.

Site settings list page- and site-scoped rules for that site. You can review their scope, hit count, reason, and status, then pause, resume, or delete them. Pausing a rule affects future matching; it does not automatically rewrite earlier scan history.