Broken Links, Redirects, and HTTP Status Codes

What common status codes tell you

Repair the visitor journey

Begin with the page containing the link and the task that link promises. A broken link to a pricing page, form, or download can interrupt a real decision. An obsolete link in an old article may be lower priority, but it still needs an honest destination. The repair should preserve the meaning of the link, not merely remove a red indicator.

Google documents different handling for redirects, client errors, and server errors. A 200 response alone does not establish indexing eligibility when the content behaves like an error. Likewise, a 404 on an intentionally removed URL is not automatically a sitewide fault. Judge the response against what should exist at that particular address.

Confirm the source and the full response path

1. Copy the exact link from the source page. Watch for wrong capitalization, an old hostname, an accidental space, a bad extension, or a missing path segment.
2. Request it without your administrator session and record the status of each redirect hop, including protocol and hostname changes.
3. Read the final page. Check that its heading and content fulfill the link promise, rather than landing on a homepage, login form, or generic search page.
4. Repeat a transient failure once in a normal browser and compare monitoring evidence. A single timeout does not establish a permanent outage.
5. Find other incoming links and sitemap references to the same URL so the correction covers the actual source of repeated requests.

Choose the correct repair

1. Fix a simple source typo at the link itself. Do not add a permanent redirect just to preserve an accidental internal spelling.
2. If the content moved permanently, redirect the old URL directly to the closest equivalent destination. Update owned internal links to that final URL.
3. If the move is temporary, keep an appropriate temporary response and record when to review it. Do not turn every temporary campaign into permanent routing.
4. If no useful replacement exists, return a genuine 404 or 410 and remove misleading incoming links. Provide helpful navigation on the error page.
5. Resolve loops and unnecessary chains by aligning the active redirect layers. Check CDN, server, CMS, and extension rules before adding another rule.
6. For 5xx failures, preserve the timestamp and affected request, then investigate authorized logs and hosting diagnostics. Avoid treating a content edit as a cure for an upstream failure.

Migration examples

These paths are illustrative. Create a migration table with old URL, intended replacement, reason, observed status, and owner. Test valuable old URLs individually; bulk rules can silently send unrelated pages to the same destination.

PASS
/old-guide/ -> 301 -> /guides/new-equivalent/ -> 200
Owned internal links point directly to /guides/new-equivalent/

FAIL
/old-guide/ -> /previous-path/ -> /another-path/ -> homepage
Final page does not answer the original request

Joomla and WordPress checks

Joomla

Check the published article, category, route-owning menu item, alias, and access level. A missing category route can break many working articles at once. Review existing Redirect component entries and any server or extension rules before editing. Preserve an established component menu item when diagnosing an article link; matching aliases do not make them interchangeable.

WordPress

Check the post status and preferred permalink, then review the existing redirect owner. A stale link, renamed post, and rewrite failure are different causes. Do not repeatedly resave sitewide permalink settings or install overlapping redirect plugins without diagnosing the failure. Check whether a page builder or cache still contains the old destination.

Verify beyond the destination status

Open each repaired link from its actual source page. Test ordinary GET requests, because a HEAD response can differ on some systems. Confirm the final URL, useful content, canonical, and any language or query handling. A form or download link also needs functional testing appropriate to its task.

Test representative URLs that should remain unchanged, especially after a pattern-based redirect edit. Check for unexpected changes to assets, administrator paths, or scanner endpoints. Update the sitemap and internal links according to the canonical plan. Then rescan comparable pages and preserve the before-and-after evidence.

Primary references

Use these first-party references for the technical definitions and platform behavior discussed in this guide.

• Google Search Central: HTTP status codes
• Google Search Central: Redirects
• MDN: HTTP response status codes