When an old Blogger post is deleted, people may still visit its URL from search results, bookmarks, or other websites. If you have a genuinely relevant replacement article, a redirect can take those visitors to the useful new page instead of leaving them at a dead link.
But not every deleted post should redirect to the homepage. This guide explains how to redirect a deleted Blogger post, when a permanent redirect makes sense, and how to verify that it works without creating confusing chains.
Decide whether a redirect is appropriate
First ask what the old page was about and whether the new page really satisfies the same need. For example, if you removed an outdated tutorial on connecting a Blogger domain and replaced it with a clearer version of the same process, a permanent redirect may be appropriate.
If the old page explained an unrelated product that no longer exists, sending everyone to a generic “How to Start a Blog” page is unlikely to help. A genuine 404 may be more honest than an irrelevant redirect.
Step 1: Record the old and new URLs
Copy the exact path of the deleted or retired article, such as /2023/09/old-tutorial.html. Also copy the path of the relevant published replacement, such as /2026/10/updated-tutorial.html.
Check that the destination is already published and loads correctly. Do not point visitors to a draft or a guessed future permalink.
Step 2: Open Blogger's Custom redirects setting
- Sign in to Blogger and select the blog.
- Open Settings and find Errors and redirects.
- Choose Custom redirects.
- Add the old path as the source and the published replacement path as the destination, following the current Blogger dialog.
- Use the permanent option when the content has moved for good; save the rule.
The official Blogger settings guide lists the Custom redirects feature. Depending on interface version, fields may be labeled “From,” “To,” and “Permanent.” Review their actual values before saving.
Step 3: Choose permanent versus temporary correctly
A permanent redirect communicates that the resource has moved for good. A temporary redirect is for a situation that you expect to reverse. Do not choose one merely because you think it has “more SEO power.” Use the status that reflects the actual move.
Google's redirect guidance explains how redirects are used in site moves and URL changes. The reader's experience should determine whether a redirect is appropriate in the first place.
Step 4: Test the exact old URL
Open the original address in a private browser window. Confirm that it reaches the intended published replacement and not a different article, a login page, or another 404.
Check the HTTPS version and any custom-domain variants that matter for your site. If you changed your domain as well as the post path, test the complete route from the older address.
Step 5: Update internal links
Search your own published articles and navigation for links that still point to the retired post. Replace those links with the new URL when the context remains relevant. A redirect helps visitors using old links, but your site should not keep sending readers through unnecessary extra hops.
Do not add a random list of unrelated links to the replacement post. The best internal link explains why the reader might want the destination.
When not to redirect
- There is no genuinely similar replacement.
- The destination is unpublished, blocked, or broken.
- The old post addressed a unique question that the new page does not answer.
- A rule would send multiple unrelated articles to one generic page.
If the old content was removed for safety, legal, or accuracy reasons, evaluate whether any new page should replace it. The safe answer can be to return a proper not-found response while keeping the site's navigation useful.
Common redirect errors in Blogger
The old URL still returns a 404
Double-check the source path, spelling, leading slash, and the saved rule. Test a specific URL rather than the homepage. Allow the Blogger interface to show whether the rule was saved.
The redirect goes to the wrong page
Check the destination path and any older rule affecting the same source. Update only the incorrect mapping. Do not create a loop that sends the new page back to the old page.
The new page has a different topic
Choose a better replacement or remove the redirect. Relevance matters more than preventing every possible 404.
Google still shows the old URL
Search indexing takes time to process URL changes. Check the live redirect, update internal links, and monitor Search Console instead of repeatedly changing a working rule.
Frequently asked questions
Will a redirect restore all traffic from a deleted post?
No guarantee. A relevant redirect can help readers reach replacement content, but search visibility depends on many factors.
Can I redirect a deleted Blogger post to my homepage?
Technically possible in some cases, but generally not useful when the homepage does not answer the old article's question. Prefer a closely related page.
Should I delete the original post before testing?
Not without a reason. If the task is content improvement, preserving the existing URL and updating the existing article may be less disruptive than deleting it.
Does Blogger support custom redirects?
Yes. The Settings area includes Custom redirects, subject to the platform's available options and limits.
A sensible redirect policy
Keep a small log with old URL, destination, reason, and date. Redirect only when the replacement is real and relevant, then test it and update internal links. A thoughtful mapping helps readers more than a blanket “send everything home” rule.