Content Operations and Maintenance

Broken Link Remediation Sheet

Investigate failed or redirected references and choose a verified replacement, direct destination, archived citation, contextual rewrite, removal, or escalation.

Free editable Markdown · Content operations teams, SEO specialists, and editors · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Link and failure record

Issue ID, finder, and check date: [Enter]
Source canonical URL and locale: [Enter]
Anchor text and location: [Enter]
Surrounding claim or reader task: [Describe]
Destination URL: [Enter]
Link purpose: [Evidence / Credit / Navigation / Task / Download / Other]
Discovery method: [Crawler / Reader report / Manual / Other]
Observed result: [Status, redirect, content mismatch, fragment, access]
Reproduction notes: [Browser/device/time]

Candidate assessment

Failure class: [Persistent / Temporary / Redirect / Soft error / Wrong content / Other]
Original source owner: [Enter]
Canonical/current location checked: [Enter]
Candidate replacement: [Enter or None]
Exact claim/task support: [Explain]
Authority, date, scope, and limitations: [Assess]
Archive, rights, privacy, and accessibility: [Assess]
Reason candidates were rejected: [List]

Repair and verification

Action: [Update / Direct link / Rewrite / Remove / Restore / Redirect / Escalate]
New anchor/destination or wording: [Enter]
Content and technical owners: [Enter]
Priority and reader impact: [Enter]
Affected components/pages/locales: [List]
Deployment reference/date: [Enter]
Rendered link and destination verified: [Enter]
Re-crawl result: [Enter]
Systemic follow-up and review date: [Enter]

How to use this template

Capture the source context, anchor, destination, link purpose, locale, and discovery evidence.
Reproduce and classify the failure instead of assuming every tool-reported URL is broken.
Evaluate canonical, archived, or alternative sources for exact support, authority, scope, and safety.
Choose the editorial and technical repair with owners, priority, and any downstream impact.
Verify the rendered result, record deployment, re-crawl the scope, and escalate recurring patterns.

Verify the failure and the link’s job

Record the source page, exact anchor text, surrounding claim or task, destination, link type, locale, discovery tool, and check date. Test the destination in a normal browser and, where authorized, inspect response behavior. Distinguish a persistent failure from a temporary outage, blocked crawler, authentication wall, malformed URL, certificate issue, redirect chain, soft error, wrong fragment, or working page that no longer supports the reference. Decide what the link was meant to do: substantiate a claim, credit a creator, help complete a task, provide a download, explain terminology, or move through the site. Remediation must preserve that purpose or explicitly revise the source content.

Choose a replacement by evidence, not URL similarity

Look first for the current canonical location from the same authoritative owner, then for a suitable primary or high-quality alternative source. Verify title, author or institution, publication and update date, exact claim support, scope, accessibility, language, permissions, and stability. An archived copy can help document history, but consider rights, privacy, accessibility, and whether the old material should still guide present action. Do not link to a search result, an unrelated homepage, or a page that mentions the topic without supporting the sentence. If no trustworthy destination exists, rewrite or remove the unsupported claim, add a transparent limitation, or escalate for new evidence rather than substituting a convenient link.

Implement the smallest complete repair

Select update destination, link directly past an internal redirect, change anchor text, replace the source, remove the link, restore a missing internal page, add a redirect, or revise the paragraph. For internal URLs, inspect canonical rules, redirect ownership, navigation, backlinks, locale equivalents, and sitemap effects before changing many sources. Assign content and technical owners separately when both are needed. After implementation, test the rendered link, destination, fragment, download, focus behavior, and nearby meaning on relevant devices and locales. Record the deployed version and re-crawl the affected scope. Repeated failures from one source, component, or migration should create a systemic action rather than hundreds of isolated edits.

See the fields in context

Fictional example: retired accessibility guidance URL

The source page, organization, and URLs are invented.

Purpose: A link supports instructions for writing descriptive link text.
Failure: The old path redirects to a broad homepage that does not contain the cited guidance.
Replacement: The same fictional standards owner publishes a current, scoped guidance page.
Repair: Update the destination and anchor, then verify the sentence still matches the new source.
Follow-up: Search the component library for the retired domain path and assign one grouped repair.

Frequently asked questions

Should every redirect be replaced?

Not automatically. Prioritize long chains, wrong destinations, unstable external redirects, and internal links where a direct canonical URL improves reliability.

Is an archived page always an acceptable replacement?

No. Check whether historical content remains accurate and lawful to reference, and whether readers need current instructions instead.

What if no source supports the claim anymore?

Revise, remove, qualify, or investigate the claim. A working but irrelevant link does not restore evidence.

How should temporary outages be handled?

Record repeated checks and consequence. Monitor low-risk failures; use containment or an alternative source when the missing destination blocks an important task.