How to Fix Broken Links on Your Blog (Step-by-Step)
Broken links have a way of hiding in plain sight until a reader finds one at the worst possible moment. Just like what we had in our own site before, if you've got an aging blog archive, a few affiliate posts, and a backlog of old roundups that still get clicks, how to fix broken links stops being a tidy SEO task and becomes basic site maintenance.
The good news is that you don't need to guess your way through it, we'll help you out on this one. There's a sensible order to finding the damage, deciding what matters, and choosing the right repair, and it's a lot less painful once you stop treating every dead URL like the same problem. Keep reading, because the fix is usually simpler than the mess.
Table of Contents
- What Broken Links Are and Why Bloggers Should Care
- Finding Every Broken Link on Your Blog
- Prioritising Which Broken Links to Fix First
- The Four Ways to Actually Repair a Broken Link
- Testing and Validating Your Fixes
- Setting Up Ongoing Monitoring and Prevention
What Broken Links Are and Why Bloggers Should Care
Open an old post and click a link that used to work. If it now lands on a 404 page not found, a soft 404, a dead external reference, or a redirect that has gone stale, you have a broken link on your hands. On blogs, that usually shows up in affiliate links, old roundup posts, articles that moved during a redesign, and citations that vanished after another site updated its content. A moved page should usually go to a 301 redirect, and old URLs should point to the closest current version instead of being left to fail with 404 errors.
For bloggers, the fallout shows up in three places. Broken links waste crawl budget, so search engines spend time on dead ends instead of finding fresh or updated content. They also break reader trust, because nobody enjoys clicking a recipe source, travel tip, or product mention and landing on a dead page. They make an archive look neglected too, which is a bad look when your site is supposed to feel useful and current rather than like a digital attic.
Practical rule: if a link is broken on a page that matters, the fix should preserve the reader's path, not just silence an error report.
Across the blogs we've analysed, broken links tend to pile up in the same places, older posts, affiliate-heavy articles, and pages that were updated once and then forgotten. I have seen the same pattern on my own sites too. A four-year-old affiliate link can keep getting clicks while leading nowhere useful, and that is steady revenue leakage, not a dramatic disaster, which is exactly why it gets ignored for too long.
The job is to sort the problems by impact, fix the links that still matter, and leave the harmless leftovers alone when that makes more sense. A broken link audit is part cleanup, part triage, and part judgment call. A good SEO audit helps you spot the pages worth attention first, which is why a framework like Blog Health's guide to SEO auditing is a useful companion if you want the bigger picture.
Finding Every Broken Link on Your Blog
A broken-link audit works best as a layered workflow. Start with Google Search Console for crawl data, then run a dedicated crawler to catch the links Google has not surfaced recently, then spot-check the pages where traffic and revenue matter most. Search Console's indexing reports can surface Not found (404) URLs, which gives you a clean free starting point.
Start with Search Console, then crawl
A crawler like Screaming Frog is the next step because it finds internal links that Search Console can miss, especially on pages Google has not revisited in a while. The practical move is to export the broken URL, source page, anchor text, link type, and status into one spreadsheet, then sort by impact instead of staring at a long error dump. Sitebulb's approach of drilling into the Incoming Links/Inlinks tab is useful here too, because it shows exactly where the link lives before you touch anything.
A lot of bloggers stop after the first crawl export and wonder why the list feels noisy. That is normal. Search Console tells you what Google saw, while a crawler shows what is sitting on your site right now, and those two views often disagree after years of edits, theme changes, and content updates.
Don't let affiliate and redirect links fool you
Generic tools get slippery here. Affiliate links often run through tracking URLs, temporary redirects, and advertiser systems, so a checker may flag them as broken when they are working as intended. A naive report does not know the difference between a dead destination and a legitimate redirect chain, which is why bloggers with affiliate-heavy archives need a human eye on the results.
Manual spot-checks still matter because some of the links that hurt most are also the ones generic tools misread. If a broken-link report says an affiliate redirect is failing, click it yourself and confirm whether the final destination loads, whether the path is just ugly, or whether the advertiser has pulled the page. That distinction saves a lot of false cleanup.
Use a blogger-friendly scan when you're short on time
When the audit list is bigger than your patience, a blogger-focused scan can help you get to the trouble faster. The point is not to replace Search Console or a crawler, it is to cut down the amount of cross-checking you have to do when your site has years of old posts. Blog-specific workflows are useful because they are built around the mess most independent bloggers have, not the tidy setup generic SEO tools seem to assume.
If you want a stronger foundation for the rest of your audit habits, it helps to understand the wider process first, which is why a basic SEO audit framework is worth reading alongside this workflow.
Prioritising Which Broken Links to Fix First
Not every broken link deserves the same level of panic. Across the blogs we've scanned, the highest-value fixes usually sit on pages that still get traffic, still pass internal link equity, or still support an active cluster of posts. A dead link buried in a post nobody reads is annoying, but a dead link on a strong article with dozens of internal links is where the damage tends to live.
Score by impact, not by volume
The simplest way to keep this practical is to score each broken link against four factors, page traffic, internal link equity, link type, and whether the page belongs to a cluster you're actively building. Page traffic matters because a broken link on a high-traffic post affects more readers. Internal link equity matters because a broken internal link can interrupt the path you've already built through your site.
Here's a quick way to rank what gets fixed first.
| Factor | Low Priority (1) | Medium Priority (2) | High Priority (3) |
|---|---|---|---|
| Page traffic from GA4 | Low or stale traffic | Some regular traffic | High-traffic page |
| Internal link equity | Few or no inlinks | Several inlinks | Many inlinks or hub page |
| Link type | Low-value external link | Standard external link | Internal, affiliate, or revenue-linked URL |
| Cluster importance | Standalone post | Adjacent to a topic group | Part of an active topical cluster |
A score that lands at the top of that grid should be fixed immediately. A middling score is usually batch-worthy, and a low score can wait until your regular maintenance round. That approach lines up with the way strong content structure works, which is why it helps to think in terms of topical authority and supporting posts instead of one lonely URL at a time.
Useful exception: some 404s are fine to leave alone if they are not soft 404s, not linked from important pages, and not tied to conversion or affiliate value. Dead doesn't automatically mean urgent.
Use business value, not just technical neatness
A broken link on a post that still brings in readers, income, or strategic internal clicks deserves attention before a dead end tucked into a low-traffic archive post. If you're staring at a long export, ask one blunt question, “Would anyone miss this if it stayed broken for another month?” If the answer is no, batch it. If the answer is yes, move it up the list.
A concrete example helps. If an old recipe post gets steady traffic, has several links from newer posts, and contains a broken affiliate link, fix that first, because it affects readers, internal flow, and revenue in one go. If a five-year-old seasonal roundup has one broken external citation and almost no traffic, it can wait until your next clean-up pass.
The Four Ways to Actually Repair a Broken Link
Once you know what matters, the repair itself is usually one of four moves. The trick is matching the fix to the problem instead of slapping a redirect on everything and calling it done. That's how people end up with messy redirect chains and a false sense of progress.
Update the link when the destination still exists
If the page still exists at a new address, or the URL was mistyped in the first place, update the link directly in the editor. This is the cleanest fix because it sends readers straight to the right place without extra hops. Conductor and Acquia both point out that typos, moved pages, and outdated URLs are common causes, and the best fix is often just replacing the bad destination with the correct one (Conductor's broken link guide).
Redirect when the old page has a real replacement
Use a 301 redirect when the original page is gone but a relevant live page exists at a new URL. The redirect should point to the closest topical equivalent, not the homepage, because dumping everything on the homepage usually feels lazy and confuses readers. Guidance from Sitebulb and Acquia both support redirecting to a relevant page rather than leaving people on a dead end (Sitebulb's broken link guide).
Replace the destination when the source disappeared
For broken external references, swap in an alternative source if one exists. If you're dealing with a citation that vanished entirely, the Wayback Machine is a useful fallback for finding an archived version or confirming what the original page said before you choose a replacement (MLA guidance on disappearing sources).
Remove the link when it adds nothing useful
If the destination is permanently gone and you don't have a credible replacement, remove the link. That's especially reasonable when the link isn't essential to the article's value. A dead link is not sacred just because it used to be there.
| Situation | Best Fix | Why It Works |
|---|---|---|
| URL typo or wrong slug | Update the link | Preserves the original path with no extra redirect |
| Page moved or merged | 301 redirect | Keeps readers and value moving to the nearest relevant page |
| External source disappeared | Replace the source | Keeps the citation useful and current |
| No replacement exists | Remove the link | Stops sending readers into a dead end |
One small but important habit, avoid redirect chains. If a URL already redirects once, don't send it through another layer unless you have to. Every extra hop makes the fix clunkier than it needs to be.
For your own site structure, it's worth keeping the larger internal linking system in mind too, since fixing one dead URL is often a good moment to strengthen the whole post: internal linking strategy for bloggers.
Testing and Validating Your Fixes
A repair is only done after you verify it in the wild. I've seen plenty of bloggers save a change in the CMS, then miss that the old URL still points to a dead path, or that a redirect is looping in the background. A quick check now saves you from cleaning up the same link twice later.
Check the source, then the destination
Open the source page in an incognito window and click the repaired link. That shows you what a real reader sees, not what your logged-in browser cache wants to claim is happening. Then load the destination URL directly and confirm it resolves cleanly, ideally with a 200 status, not another redirect chain.
If the fix involved a 301, make sure it lands on the page you intended. A redirect that technically works but drops people onto the wrong article is still a bad fix.
A failed validation usually looks simple. The link clicks, but the browser lands on a 404 page, or the old URL keeps bouncing through two redirects before it reaches the target. I treat that as a bad repair, even if the final page eventually loads, because readers still pay the friction cost.
Use Search Console to confirm reprocessing
After you've repaired the important URLs, run them through Google Search Console's URL Inspection tool and request re-indexing where it makes sense. That does not guarantee instant updates, but it does push the process along. It also gives you a fast way to spot whether Google is still seeing the old problem.
If a redirect fails, check for CMS-level conflict first. Redirect plugins can fight with manual .htaccess rules, auto-redirect features can override your hand-built rules, and some plugins strip query parameters that your affiliate or tracking URL needed.
That is the point where validation gets annoying, because the problem is often not the link itself, it is the machinery around it. A combined view of technical health and traffic helps here, and a combined view of technical health and mobile experience can matter too, which is covered in our guide to optimizing your website for mobile. It also helps to check whether the fix sits on a page that gets visits before you spend another hour chasing a stubborn redirect.
Setting Up Ongoing Monitoring and Prevention
Broken-link cleanup works best when it's routine, not heroic. For active blogs, a monthly scan is realistic. For slower publishers, quarterly is usually enough, as long as you also check after any redesign, migration, or big content update.
Use a small monthly checklist
Monthly broken-link checklist
Run a full crawl. Catch new 4xx and 404 URLs before they stack up.
Export new 404s from Search Console. Compare them with last month's list so you're not chasing duplicates.
Check affiliate redirects manually. These are the ones generic tools misread most often.
Review posts updated in the last 30 days. Fresh edits are where new mistakes usually sneak in.
That routine keeps the work small. It also stops you from becoming the person who says, “I'll get to the technical stuff someday,” which is how broken links breed in the first place.
Prevent new problems while you publish
Use relative paths for your own internal links where possible, because they're easier to manage when you change slugs or move content around. Keep a redirect map before any site move, especially if you're merging posts or switching themes. And treat plugin and theme updates as a reason to recheck outbound links, because a small change can break a lot of URLs faster than you'd expect.
If you want to keep this habit tied to the broader health of your site, it helps to think of maintenance as an ongoing category, not an occasional panic session. That's the same mindset behind a good blog maintenance routine.
The bloggers who stay on top of broken links aren't necessarily the most technical. They're just the ones who check consistently, fix the links that matter first, and don't let the archive drift into slow decay.
If you'd rather not spend your evenings cross-referencing Search Console, crawlers, affiliate links, and old posts one by one, Blog Health App brings the broken-link picture into the same view as your traffic and site health. Visit Blog Health to see how it helps independent bloggers spot the links worth fixing first, before they turn into another weekend lost to cleanup.
