A deleted Blogger post needs a permanent redirect only when readers have a clear new destination. If the post is gone and no similar page exists, the old URL should return a real 404 or 410 response. Google recommends that choice because it tells search engines the content no longer exists. A custom 404 message can still help the reader find their way around the blog.
The decision starts with one question: does another page genuinely replace the deleted post?
If the answer is yes, send the reader to that replacement. If the answer is no, keep the old URL as a missing page and give the reader useful links. Sending every old post to the homepage creates a poor match between the URL requested and the page shown. It can also produce a soft 404 when a page says that content is missing while the server returns a successful 200 status.
Start with the reader’s original intent
An old URL can keep receiving visits from bookmarks, search results, links in other articles, social posts, or a browser history. The visitor expected a specific subject. The useful response depends on whether that subject still exists somewhere on the blog.
A replacement should cover the same need, not merely share a broad category. A deleted tutorial about changing a Blogger setting may have a newer tutorial that covers the same setting. That newer tutorial is a sensible destination. A general archive page is not automatically a replacement.
Google Search Central draws the same line: use a 301 permanent redirect when a page has moved or has a clear replacement. When the content is unavailable and no similar replacement exists, return 404 or 410. Read the guidance in Google Search Central’s documentation on soft 404 errors.
The choice is about the old page itself. A redirect should answer the reason someone followed that URL. A custom missing-page message should acknowledge that the page has gone, then offer routes back into the site.
The practical choice
| Situation at the deleted URL | Best response | What the reader sees |
|---|---|---|
| The post moved to a new URL | Permanent redirect | The replacement post opens automatically |
| A newer post covers the same subject | Permanent redirect | The newer, closely related post opens automatically |
| The post is gone and no similar post exists | 404 or 410, with a useful 404 page | A clear missing-page message with navigation |
| The old URL points to a temporary site problem | Fix the problem and keep the page available | The original content returns |
A 301 tells browsers and search engines that the address has moved permanently. Google says it helps users continue browsing without interruption and identifies the new location for search engines.
A 404 means “not found.” A 410 means “gone.” Google treats both as signals that the page does not exist and should not be indexed. The difference matters less to a reader than the message on the page. The reader needs a plain explanation and a route to a useful part of the blog.
Do not treat a deleted URL as a spare traffic source. A redirect to an unrelated post or to the homepage can leave a visitor confused. Google’s guidance focuses on a page that has moved or has a clear replacement. That is a narrower test than “another page exists on the site.”
When a custom 404 message fits the situation
Use a custom 404 message when the deleted post has no close successor. The message appears after the visitor reaches a missing URL, so its job is simple: explain that the page cannot be found and point to useful next steps.
Google recommends several ingredients for a useful custom 404 page. Tell visitors clearly that the page cannot be found. Use friendly language. Keep the look and navigation consistent with the rest of the site. Link to the homepage and consider links to popular posts. A way to report a broken link can also help site owners find outdated references.
For a Blogger blog, keep the message brief. Readers arrived through a broken or old address; a long explanation adds little. A short message can say that the post is no longer available, offer a link to the homepage, and direct the reader toward a relevant archive or category page when one exists.
The custom message does not turn every missing page into a valid page. Google warns about soft 404 errors, where a URL displays a message saying the page is unavailable while the server sends HTTP 200, the normal success response. Search systems can exclude such pages after detecting the mismatch. A useful error page needs the matching error status.
Blogger’s settings page says that its Custom 404 setting lets you enter a message shown on the blog’s 404 page in place of the generic message. That documentation describes the setting. It does not establish which HTTP status a particular blog returns after a change. Check the old URL after saving the setting.
Set the custom 404 message in Blogger
Blogger lists its error controls under Settings, in the “Errors and redirects” section. Its Blogger Help settings guide describes both Custom 404 and Custom redirects.
Open the blog’s Settings area and find “Errors and redirects.” Choose “Custom 404,” then enter the message you want visitors to see. The message replaces Blogger’s generic page-not-found wording.
Write for someone who expected a real page. “This post is no longer available” is clearer than a vague apology. Give the visitor one or two relevant routes. The homepage is useful for a general return path. A topic page helps only when it matches the missing post’s subject.
Keep the promise modest. Do not say that a replacement exists unless you actually link or redirect to one. Do not write that the post will return unless you plan to restore it.
The visual design remains part of the reader experience. Google advises matching the rest of the site’s look and navigation. Blogger’s custom-message field handles the message itself; the surrounding page behavior depends on the blog’s setup. Review the published result through an old URL, not only through the settings screen.
Set a permanent custom redirect when a replacement exists
Blogger also lists “Custom redirects” in the same Settings section. Its help page says to add redirects for URLs that point to pages on the blog. Enter the deleted address in the “From” field and the destination in the “To” field. When the original article was deleted, Blogger’s documentation says to select “Permanent.”
Use the exact old path that readers and search engines request. Then choose the new path with care. The destination should answer the old visitor’s likely question.
Imagine a fictional example. A blog deletes a post called “How to change comment settings in Blogger” because a later post rewrites the instructions for the current interface. The later post addresses the same task. A permanent redirect from the retired URL to the updated guide makes sense.
Now change the example. The deleted post reviewed a discontinued tool, and the blog has no replacement review or alternative guide. A permanent redirect to the homepage would not meet the reader’s expectation. A useful 404 page fits that case better.
A third fictional example shows why similarity matters. A deleted post explains how to export a Blogger backup. A general post about writing better headlines does not replace it, even though both posts belong to the same blog. The old backup URL should not redirect there.
Check the old URL after saving
Do not assume a saved setting produced the intended result. Test the original URL after you create either a custom message or a redirect.
For a permanent redirect, confirm that the old address reaches the chosen replacement and that the destination is relevant. Google recommends using the URL Inspection tool to verify that a moved page returns the correct code.
For a missing page, confirm that the visitor sees the custom message, can use the site navigation, and receives a real 404 or 410 response. Google says custom 404 pages exist for users and should return a 404 status so search engines do not index them as normal content.
Also check for redirect chains. Google warns that long redirect chains hurt crawling. Keep the path direct: old deleted URL to replacement page. If the replacement itself redirects elsewhere, update the old redirect when possible so readers do not take unnecessary hops.
The original URL deserves a second look after later edits. A replacement can be deleted, renamed, or moved again. A redirect that once made sense may later point to another missing page or a loosely related destination.
A simple rule for future deletions
Before deleting a Blogger post, identify whether a clear replacement already exists. If it does, set a permanent custom redirect to that page. If it does not, use a useful custom 404 message and verify that the URL returns an actual missing-page status.
That rule keeps the reader’s task in view. A close replacement sends them straight to the information they wanted. A missing-page message tells the truth and gives them a practical way to continue.
Does the replacement answer the same question as the deleted post? Can a visitor who lands on the old URL quickly find a relevant next page?
