Blog Redirects and 410 Gone: Fix 404s Without Losing SEO
Most 404s on a blog are noise, but a few cost you readers and rankings. Here is when to use 301, 302 or 410, how to find the 404s worth fixing, and how to avoid chains.
Use a 301 redirect when a blog post has moved for good, a 302 when the move is temporary, and 410 Gone when a page was removed on purpose and has no replacement. Fix only the 404s with evidence that readers hit them, and always redirect in a single hop.
Every blog accumulates broken URLs. Posts get renamed, old series get retired, a migration changes the URL structure. Each broken link is a reader who lands on an error and a bit of search value that goes nowhere. The fix is not to redirect everything, though. It is to use the right status code for each case and to fix the 404s that actually matter.
301, 302 and 410: which one when
- 301 Moved Permanently: the post now lives at a new address for good. Search engines move rankings and links to the new URL. This is the default for renames and migrations.
- 302 Found: the move is temporary, for example during maintenance. Search engines keep the original URL indexed.
- 410 Gone: the page was removed on purpose and there is no replacement. It tells search engines the removal is deliberate.
- 404 Not Found: the server simply has nothing at that address, with no statement about whether it ever did.
Google eventually drops both 404 and 410 pages from its index, and has said a 410 can be processed slightly sooner. The bigger practical difference is clarity: a 410 says you meant it.
Which 404s are worth fixing
On a public blog, most 404s are not readers at all. They are scanners probing for files that never existed, which is a job for an IP firewall, not for redirects. The 404s worth your time have evidence behind them:
- Something links to them: another page on your site, an external article, or an old social post.
- They look like a real post: a typo, an old slug after a rename, or a different capitalisation.
- Search Console reports them as URLs it tried to crawl.
When not to redirect
Do not send a removed post to your homepage or an unrelated page. Search engines tend to treat that as a soft 404, and a reader who wanted a specific article lands somewhere that does not answer them. If there is a close replacement, redirect to it. If there is not, 410 is the honest answer. And keep redirects in place for as long as old links might still be followed, which for a popular post can mean years, because deleting a rule brings the broken link straight back.
Avoid chains and loops
A chain is a redirect that lands on another redirect. Each extra hop slows readers down and wastes crawl budget, and a loop never resolves at all. Point every rule at the final URL, and update your own internal links to the destination rather than relying on the redirect. That is one of the habits in our self-hosted blog SEO checklist.
Redirect what readers are looking for, retire what you removed on purpose, and let the scanners hit a wall.
How Inkwell handles redirects
- Automatic redirects: renaming a post and running an import both write redirect rules for you, which is how the importer in our WordPress migration guide keeps old permalinks working.
- 301, 302 or 410: since v1.0.4 a rule can move a URL or retire it with 410 Gone, which serves a "no longer available" page that points readers to current content.
- Admin > Redirects (since v1.0.5) lists, creates, edits and removes rules, and turns the 404 log into a worklist. A 404 is ranked first when another page links to it or it closely matches a real slug, with one click to 301 it to the suggested post or 410 it. Scanner noise is collapsed out of the way.
- No chains by construction: rules that would loop, point at a URL that redirects again, or target a retired URL are refused, with the real destination named.
- Link Audit scans every published post and page for internal links that dead-end, point at a retired URL, or take an avoidable redirect hop.
Redirect rules are Admin-only and every change is audited. Setup details are in the documentation.
Frequently asked questions
What is the difference between a 404 and a 410?
A 404 means the server has nothing at that address, without saying why. A 410 Gone means the page was removed on purpose. Search engines drop both from their index eventually, and Google has said a 410 can be processed slightly sooner.
Should I redirect every 404 on my blog?
No. Most 404s on a public blog come from scanners probing for files that never existed. Redirect only the ones with evidence that readers reach them: an inbound link, a close match to a real post, or a Search Console report.
Do redirect chains hurt SEO?
They waste crawl budget and slow readers down, and long chains may not be followed to the end. Point every redirect directly at the final URL and update internal links so they skip the redirect entirely.
Does Inkwell have a redirect manager?
Yes. Inkwell writes redirects automatically for post renames and imports, supports 301, 302 and 410 Gone rules, and since v1.0.5 has an Admin Redirects screen with a ranked 404 worklist that refuses rules creating loops or chains.
Ready to host your own blog?
Inkwell is free, open-source, and self-hosted — your content, your server, your rules. Deploy in minutes on .NET 10.