Review incidents that affect multiple URLs

Read card or table evidence for sitewide and cross-page findings.

Last checked 21 August 2026

Some checks evaluate relationships across a website or return several affected items in one result. TechDash groups those items into one incident identified by website, site-level path, and check. The incident count therefore does not always equal the number of affected URLs.

Recognize grouped evidence

The detail dialog chooses a layout that fits the check.

Grouped URL lists

Duplicate title and duplicate H1 incidents can show a card for each duplicated value, followed by every page that uses it. Other checks can show a simpler Pages list. Examples include orphan monitored pages, inbound-link loss, sitemap membership, robots.txt blocking, and possible page retirement.

Result cards

Some rows need several fields:

  • Canonical findings can show Checked URL, On-page Canonical URL, and Google Selected Canonical URL.
  • Invalid hreflang targets can show Checked URL, Invalid hreflang target, and Why.
  • Reciprocity gaps show Checked URL, hreflang, and Alternate URL (no return tag).
  • Duplicate hreflang language evidence shows the checked page and separate cards with URLs with this code.

These cards keep each source URL associated with its own target and reason.

Tables

High-value anchor-text changes use a Destination pages table with the destination, previous wording, and current wording. Redirect-waste and image-redirect findings use a source-and-destination table under How to fix.

Non-URL lists

Some grouped Search Console incidents list Query, Queries, Search appearance, or Search appearances rather than page URLs. These values are affected dimensions, not monitored pages.

Investigate shared causes

Start by looking for a common source:

  1. Check whether affected URLs share a page template or content type.
  2. Review recent CMS, navigation, canonical, hreflang, robots.txt, or sitemap changes.
  3. Check whether the same target URL or status appears repeatedly.
  4. Separate intentionally retired or redirected pages from unexpected failures.
  5. Open representative live URLs, then sample the remaining rows.

A shared template, menu, deployment, or generator can explain many rows, but do not assume one cause solely because TechDash grouped the result. A single incident can contain distinct underlying problems found during the same sitewide evaluation.

Treat the affected-row count as evidence of reach, not severity by itself. One broken template can affect an important customer journey or a large section of search-visible content. Open the evidence and consider traffic, conversions, crawling, and indexability before deciding priority. The grouped incident contributes once to Health Score at its assigned Advisory, Warning, or Critical level, even when it lists many URLs.

Understand Check & Verify

For an incident assembled from results across the website, Check & Verify recalculates the finding from the page data TechDash currently has. It does not automatically crawl every affected page first. If that saved page data is stale, run or wait for the needed page checks before verifying the grouped result.

Other site-resource incidents rerun the relevant resource check. Google Search Console grouped incidents rerun the corresponding Search Analytics or URL Inspection work, subject to the connected service and its limits. If verification is delayed or incomplete, review Understand URL Inspection quotas and Fix delayed or missing Search Console data.

If the result still contains any qualifying rows, the incident remains open and the dialog reports The check still fails. Fixing one row does not close a grouped incident while other rows continue to fail.

Remove an obsolete monitored page

Supported list-style incidents can show Remove Page beside affected URLs. This is available more broadly than robots.txt or sitemap incidents. It can appear for supported duplicate, link, canonical, hreflang, portfolio, and other listed findings.

Only use Remove Page when that URL should no longer be in Monitored Pages. TechDash removes the monitored-page record, then verifies the incident. It does not delete the live page or change the website source.

Some displayed URLs are targets or external values rather than saved monitored pages. If TechDash cannot find a matching monitored path, it reports That page is no longer being monitored.

Close the grouped issue correctly

After correcting a shared source, allow affected page checks to complete when necessary, then select Check & Verify. Use Mark Resolved only when you accept the entire current grouped observed value. If the grouped evidence later changes, the resolution no longer matches and the incident can reappear.

Related articles