404 Recovery Decision Sheet Template

404 Recovery Decision Sheet (fill-in)

When to use: One row per broken URL: who links to it, what replaces it, the restore, redirect or retain decision and the QA result.

404 recovery decision sheet

Start with URLs that have links or past traffic. A 404 nobody links to can usually stay a 404.

Decision rules

• Restore when the page was removed by mistake or still answers real demand.
• Redirect (301) when a page now covers the same need. Same product moved, same guide merged.
• Retain as 404 or 410 when nothing replaces it. Remove the internal links pointing to it.
• Soft 404 (a 200 that says not found): change it to a real 404 or 410, or give it real content.

Completion check: every row has one decision and a reason, redirects retested at one hop to a 200, internal links to retained 404s removed, and the custom 404 page still returns a 404 status.

Find Broken Internal & Outbound Links

When to use: Run a full crawl to surface every internal and outbound link that returns an error.

Crawl your whole site

Point a crawler at [Root Domain] and let it follow every internal link. Export all URLs that return 4xx or 5xx status codes, plus their source pages so you know where each broken link lives.

Don't ignore outbound links. External pages disappear constantly, so filter the crawl for outbound links returning 404, 403, or timeouts.

A page full of dead outbound links signals low maintenance to visitors and crawlers alike.

Layer in other sources

• Check Search Console & the Pages report for crawled URLs flagged Not found (404).
• Pull server log lines where bots hit 404 responses.
• Review analytics for pages whose title or path reads like an error.

Build one master sheet: [Broken URL], [Source Page], [Status Code], and link type (internal vs outbound). This list feeds every fix decision that follows.

Diagnose 404 vs Soft-404 vs Other Status Codes

When to use: Classify each error correctly before fixing, since the status code dictates the right action.

Read the actual status code

Request each [Broken URL] and record the real HTTP response, not just what the page looks like. A genuine missing page should return 404 (or 410 if permanently gone): that is normal and not a penalty.

Spot soft-404s

A soft-404 is a page that says "not found" or shows thin or empty content while still returning a 200 OK. Search engines flag these because the status lies about the content.

Find them by comparing the visible message to the header status.

Bucket everything

• 404 / 410: page is gone: decide restore, redirect, or leave.
• Soft-404 (200): fix the status or the content.
• 301 / 302 chains: consolidate to a single hop.
• 403 / 5xx: access or server faults, not true not-found. Persistent 5xx errors eventually drop pages from the index, so fix these first.

Tag each row in your sheet with one bucket so the fix stage is mechanical, not guesswork.

Fix Decision: Restore / 301 / 410 / Leave

When to use: Choose the correct fix per URL instead of blanket-redirecting everything to the homepage.

Work down the decision tree

For each [Broken URL], pick exactly one action based on intent and value.

1. Restore if the page was removed by mistake or still has real demand: republish it at the original path.
2. 301 redirect to the closest relevant page when a clear replacement exists. A product moved to a new URL should point to the new product, not the homepage.
3. 404 or 410 when the page is genuinely gone and nothing replaces it. Google treats all 4xx codes except 429 the same way, so pick the one your team uses consistently. A clean 404 is perfectly acceptable.

Avoid the soft-404 trap

Redirecting an unrelated dead URL to the homepage or a generic hub can be treated as a soft-404, and Google advises against it. Only 301 to a page that truly satisfies the same intent; otherwise serve 404 or 410.

Log each choice in [Action Taken].

Custom 404 Page Best Practices

When to use: Build a 404 page that helps lost visitors recover without misleading crawlers.

Return a real 404 status

The single most important rule: a custom 404 page must still return an actual 404 HTTP status. A friendly design that returns 200 OK becomes a soft-404 and confuses search engines.

Verify the header, not just the visuals.

Help the visitor recover

• State clearly that the page wasn't found, in plain language.
• Include a search box so users can find what they wanted.
• Link to your homepage, top categories, and popular content.
• Keep header, footer, and navigation consistent with the rest of the site.

Polish the experience

Match your brand tone, add a short helpful message, and offer a contact link for users who hit a dead end. Avoid auto-redirecting away from the 404: let people read it and choose.

Test it by visiting [Domain]/[Random Nonexistent Path] and confirming both the helpful layout and the correct 404 status appear together.

Reclaim External Broken Backlinks

When to use: Recover link equity from external sites still pointing at your dead URLs.

Find who links to your dead pages

In a backlink tool, list your broken pages that have external backlinks. These are dead URLs on your domain that other sites still link to, and every one of those links is leaking equity into a 404.

Reclaim the equity

For each dead URL with backlinks, add a 301 redirect to the closest relevant live page. A permanent redirect is a strong signal for Google to process the new URL instead.

If no relevant page exists, consider restoring content worth the inbound links.

Then chase outreach

• Identify high-value linking domains pointing at [Dead URL].
• Email the site owner with the corrected [New URL] and ask them to update the link.
• Track replies and updated links in a follow-up column.

Redirects capture equity automatically; outreach gives you a clean, direct link. Prioritize the URLs with the strongest referring domains first.

Monitor & Prevent

When to use: Set up ongoing checks so new broken links and 404s are caught early.

Schedule recurring crawls

Run a scheduled crawl of [Root Domain] on a fixed cadence, weekly or monthly depending on how often you publish. Compare each run against the last to catch newly broken internal and outbound links before users do.

Watch your reporting

• Review the Search Console Pages report for fresh Not found (404) entries.
• Monitor server logs for spikes in 404 responses from real users.
• Set an alert on 404 hits in analytics for high-traffic sections.

Prevent breakage at the source

1. Before deleting or moving a page, plan its 301 to the closest relevant URL.
2. Keep a redirect map and audit it for chains and loops.
3. Use a link checker in your publishing workflow to catch typos and dead outbound links pre-publish.

Log every recurring check in [Review Date] so monitoring stays a habit, not a one-off cleanup.

Worked Example (fictional software company)

When to use: A filled-in sheet for an invented invoicing app that deleted old help pages during a docs move.

Worked example: Tallyfin help center

Example only. The company, people, URLs and figures are invented to show what a usable, filled-in version looks like.

Why only two redirects

Five broken URLs, five different answers. Two had a real equivalent. One deserved to come back. Two were fine as errors.

Redirecting everything to the help home would have hidden the one page people were still looking for.

Next step

Use the Backlink Analyzer to see which dead URLs still have referring domains, and confirm every new rule with the Redirect Checker. Run a website audit to catch broken internal links and soft 404s.

For dead pages with strong links you can't restore, our link building team can handle the outreach to update them.