Use Update Monitored URL and Remove Page fixes

Apply supported URL-management actions directly from incident evidence.

Last checked 20 August 2026

Some incidents provide actions that correct TechDash monitoring configuration. They do not edit the live website, CMS, robots.txt, sitemap, redirects, or server configuration.

Update Monitored URL

Update Monitored URL appears in the dialog footer only when all of these conditions are true:

  • The incident is the built-in Monitored URL returns a redirect check.
  • The incident is tied to an existing monitored-page record.
  • TechDash can parse the first-hop redirect destination.
  • The destination belongs to the same saved website hostname.
  • The normalized destination path differs from the current monitored path.

External-host redirects are not eligible because a monitored path cannot be moved to another saved website through this action.

Update the path

  1. Open the redirect incident.
  2. Review Before and After and confirm the destination is intentional.
  3. Confirm that the destination is the page you want TechDash to monitor from now on.
  4. Select Update Monitored URL.

TechDash checks connectivity, replaces the current monitored path with the destination path, clears the old page check state, records the original redirect incident as resolved, and immediately runs a page check for the updated monitored page.

If the updated page check no longer has the redirect incident, TechDash shows Monitored URL updated. This incident is closed. If the same check still fails at the new path, the refreshed incident remains open and TechDash shows The monitored URL was updated, but the check still fails.

The update can fail when the page no longer exists in monitoring, the destination cannot be read, another monitored page already uses that path, the redirect points back to the current path, or the computer is offline.

Use this action only for an intentional redirect whose destination has replaced the old URL. If the redirect is accidental, correct the live redirect and use Check & Verify instead.

Remove Page

Remove Page appears beside affected URLs for supported list-style incidents. The supported set includes duplicate title or H1, link architecture, canonical target, robots.txt blocking, sitemap membership, hreflang, page-retirement, WebMCP cohort, and several Search Console list findings.

The action can appear beside a displayed URL even when that value is not itself a saved monitored page. TechDash validates it when you confirm.

Remove the monitored page

  1. Open the grouped incident.
  2. Find the affected URL that should no longer be monitored.
  3. Select Remove Page beside that URL.
  4. Read the confirmation: the URL will be removed from monitoring and TechDash will stop checking it.
  5. Select Remove Page again to confirm, or Cancel.

TechDash normalizes the displayed URL against the current website, finds a matching monitored path, removes its saved check runs and local page HTML, deletes the monitored-page record, and then verifies the original incident.

If the grouped incident no longer exists, TechDash shows Page removed from monitoring. This incident is closed. If other affected rows remain, it shows Page removed from monitoring. and refreshes the incident. If no matching page exists, it shows That page is no longer being monitored.

Choose the safe action

Use Update Monitored URL when an intentional same-website redirect means monitoring should move from the old path to its destination. It preserves the monitored-page record and its settings while resetting check state for the new path.

Use Remove Page only when a listed URL should leave the monitored set entirely. Suitable cases include an intentionally retired page or a URL that was added by mistake.

Do not remove a page solely to make a valid production issue disappear. If the page should remain monitored:

  • Fix the website and select Check & Verify.
  • Select Mark Resolved if you accept the exact current finding.
  • Use Ignore This only when the check is irrelevant at the chosen scope.

Effects on future monitoring

Updating a monitored URL causes future scheduled checks to use the new path. Removing a page stops its page checks and removes its saved per-page check history and stored HTML. Either action can also change later sitewide findings because the monitored portfolio has changed.

Neither action changes external systems. If you need to fix a redirect, sitemap, robots.txt rule, canonical, or Search Console state, make that change at its source.

Related articles