Open an incident and review its evidence

Select any part of an incident card to open the detail dialog. The dialog combines the latest failing evidence with check-specific explanation and actions. Review it before changing the website or suppressing the finding.

Start with identity and scope

At the top, TechDash shows:

• The exact check name
• Its Advisory, Warning, or Critical badge
• A short description of what the check detects

Next, identify where the finding applies. A normal page incident shows Incident URL. Specialized incidents can instead show Checked URL, Destination pages, Search Console queries or appearances, or several cards and rows. Site-level findings may use the website origin and have no individual monitored-page path.

Use the external-link icon beside a URL when you need to inspect the live address. The live page may already differ from the saved evidence because TechDash displays the latest completed check it has stored.

Read the evidence format

Evidence is chosen by check type:

• A current-state check can show Best Practice and Current.
• A threshold check can show Best Practice and Current Amount.
• A change check generally shows Before and After.
• Rendered-versus-server comparisons use Server Side Rendered HTML and Client Side Rendered HTML.
• Listed findings show cards, URL lists, or tables instead of a generic comparison.

Changed text may be highlighted. Long or multiline code can be scrolled within its evidence block. Missing evidence is shown as Not recorded when a field is part of the layout but has no stored value.

Some raw values are intentionally transformed for readability. TechDash can format JSON, HTML-like snippets, status labels, counts, analytics identifiers, and check-specific evidence. The dialog represents the monitored signal, not necessarily a byte-for-byte copy of the original response.

Read How to fix

When product guidance is available, the dialog shows How to fix. This text can include the affected website, URL, before value, after value, or field name. For redirect-waste and image-redirect incidents, the section can also include a source-and-destination table.

Guidance is an investigation path, not proof that the website is wrong. Confirm whether the change was intentional and whether the shown URL is still part of the desired monitored set.

Choose an action

The footer can include:

• Ignore This, with the scopes available for this incident
• Share, for supported incident sharing
• Mark Resolved, to accept the current observed failing value
• Check & Verify, to run the work relevant to the incident immediately
• Update Monitored URL, only for an eligible monitored-page redirect

Supported list-style findings can also place Remove Page beside affected monitored URLs. That action appears in the evidence area, not the main footer.

Buttons are disabled while an action is running. TechDash reports whether verification passed, still failed, or could not run. Do not close an unresolved incident merely to tidy the list. Use the action that matches your decision:

• Fixed the underlying condition: Check & Verify
• Intentionally accept this exact current value: Mark Resolved
• Check is irrelevant at a defined scope: Ignore This
• Monitoring the wrong redirecting path: Update Monitored URL
• A listed URL should no longer be monitored: Remove Page

Investigate the cause

Compare the detected check time with recent deployments, CMS edits, redirects, template changes, DNS or certificate work, and Search Console updates. For grouped incidents, inspect every row before assuming a single cause. A shared template or generator can affect many URLs, but grouped evidence can also contain unrelated page-level problems.

Related articles

• Read before-and-after content, HTML, and JSON differences
• Review incidents that affect multiple URLs
• Recheck an incident with Check & Verify