Redirects for Deleted Posts: What to Send Where
When you remove a post that has traffic or links, set a 301 redirect from its old URL to the most relevant live page. If there is no relevant page, let the old URL return a not-found or gone response instead of redirecting to the home page.
A redirect is a signpost: it tells browsers and crawlers that a page moved, and where. Used well, it keeps visitors and most of a page’s signals. Used carelessly, it creates confusing loops and error-like behavior.
What a 301 redirect does
A 301 is a permanent redirect. When someone requests the old URL, the server responds with a message that the page has moved permanently and gives the new address. The browser then loads the new page.
Search engines treat a 301 as a signal to replace the old URL with the new one in their index, and to pass along much of the old page’s signals. It takes time for them to process, so the change is not immediate.
A 302 is a temporary redirect, meant for short-term moves. For deleted or merged posts, use the permanent type, since the move is not meant to be reversed.
When to redirect
Redirect in these situations:
- You merged two posts, and the loser’s URL should lead to the winner.
- You replaced a post with a new version at a different URL.
- You changed your URL structure.
- You deleted a post that has links or visitors, and a closely related page exists.
In each case the aim is the same: send the visitor to the page that now best answers what they were looking for.
Where to point the redirect
Choose the closest match in topic and intent. A redirect from a post on “choosing a keyword tool” should go to a page on keyword tools or keyword research, not to an unrelated category.
If the old topic has no close match on your site, do not force one. Redirecting many unrelated pages to your home page can be treated by search engines like an error page, and it frustrates visitors who expected the original content.
When in doubt, ask yourself: would a visitor who clicked the old link be glad to land here? If yes, redirect. If no, don’t.
When there is no good target
If the content is gone and no related page exists, let the URL return a 404 (not found) or 410 (gone) response. A 410 states explicitly that the page was removed on purpose, and search engines may drop it from the index sooner. Either is acceptable.
Show a helpful error page that links to your main sections or a search box, so visitors can find something else.
How to set one up
On most platforms, there are three routes. Many SEO plugins include a redirect manager, where you enter the old and new URLs. Some hosts offer a redirect tool in their control panel. Advanced users can add rules in the server configuration.
After setting a redirect, test it. Visit the old URL in a private window and confirm that it lands on the right page. Use an online redirect checker to confirm that it returns a 301 status.
Keep a list of your redirects in a spreadsheet, with the date, old URL, new URL, and reason. When you review your site later, you will know what each rule does.
Avoid common mistakes
Redirect chains. If A redirects to B, and B redirects to C, update A to point to C directly. Chains slow things down and can lose signals.
Redirect loops. If A redirects to B and B redirects back to A, the page fails to load. Test every new rule.
Redirecting everything to the home page. As noted, this is rarely helpful.
Forgetting internal links. After setting a redirect, update your own links to point straight at the new URL.
Removing the redirect too soon. Keep redirects in place for a long time, ideally permanently, since external links to the old URL may remain.
Check Search Console afterward
Look at the page indexing report for errors such as “not found” or “redirect error” on URLs you changed. Also check that the new URL appears in the Performance report in the weeks after the change.
If clicks dip briefly, that can be normal while search engines reprocess the change. If they stay down, check that the redirect target truly matches the old content.
Redirects and speed
Each redirect adds a small delay, since the browser must make another request. A single redirect is fine. This is why long chains are worth cleaning up. When you review your redirect list each year, point old rules straight at the final destination, and remove rules for URLs that no longer receive any visits or links, if you are sure that is safe.
Handling a changed URL structure
If you change your site’s address pattern, such as removing dates from post URLs, set up pattern-based redirects instead of one per post. Many platforms support this with a single rule. Test a sample of old URLs afterward to make sure each lands on the matching new page.
Document the reason
Next to each redirect, note why it exists. A year from now, you will want to know whether a rule can be changed safely, and a one-line reason makes that decision simple.
What to do next
Make a list of every post you have deleted or merged. For each, visit the old URL and see what happens. Add a 301 for any that show an error page but have a relevant target, and note any chains or loops.
Then update internal links so they point directly to the final URLs, and save your redirect list in a spreadsheet for future reference.