Skip to content

Marked as Ignore

Marked as Ignore is where your dismissed findings live. When a finding is a known non-issue for your site — an intentional noindex, a deliberate canonical, a genuine false positive — you ignore it, and it drops out of your active Issues list and stops affecting the headline counts. It isn’t deleted, though. This view is the record of everything you’ve suppressed, so you can audit those decisions and un-ignore anything that should be active again.

Ignoring is what keeps your active Issues list honest. A finding you’ve already reviewed and accepted is noise on every future crawl, and noise is how real problems get missed. Suppressing known non-issues keeps the list focused on decisions you actually need to make.

The risk runs the other way too. A finding you ignored last quarter assumed the site behaved a certain way — but sites change. If a template later starts emitting that noindex somewhere it shouldn’t, your ignore can hide the regression, because the finding never returns to the active list. That’s why this view exists and why you should review it periodically: an ignore is a standing decision, and standing decisions need re-checking.

Ignoring and reviewing happen in two places:

  • Ignore from the Issues view. When you’re looking at a finding you’ve decided is a non-issue, mark it as ignored there. It leaves your active list immediately and stops counting against your score.
  • Review and restore here. This view lists everything you’ve suppressed. Open it to see what’s been dismissed, confirm each one is still a legitimate non-issue, and un-ignore anything that should return to active tracking. A restored finding rejoins the Issues list and counts again on the next crawl.

A good cadence is to scan this list after any significant deploy or template change — exactly the moments when a previously safe assumption can quietly stop being true.