Refresh your old blog into a funnel or start over?

Refresh an old blog before you think about replacing it. Start with an inventory: tag every post by funnel stage, note which posts already earn search clicks or links, and give each one a decision: update, rewrite, merge and redirect, redirect to a close match, or retire. Posts that already earn traffic keep their URLs. What often needs starting over is the structure, not the archive. A new hub can sit on top of the old posts and absorb the best of them.

The case for a fresh build is strongest when the old posts don't match the services you sell, when nearly all of them answer TOFU (top of funnel) questions and nothing leads to a MOFU (middle of funnel) comparison or a BOFU (bottom of funnel) decision page, or when the facts in them are too stale to fix one at a time. Even then, deleting the archive throws away whatever it has earned. This guide covers the inventory, the five decisions, what Google's documentation says about redirects and canonicals, and how to protect the pages that already work.

Start with an inventory, not a decision

The urge to start fresh usually comes from looking at the blog as a whole. Decisions are easier one post at a time. Export every post URL from your CMS or sitemap into a spreadsheet and add these columns:

Stage tagging is the first step of the method in our TOFU, MOFU, BOFU content strategy. Most sites we inventory skew heavily to TOFU. An ABA therapy center's 21 legacy posts were 14 TOFU, 5 MOFU and 2 BOFU: plenty of explanation, very little help choosing or acting. That shape is a gap to fill, not a reason to delete the 14. Turning the inventory into a list of missing pages is covered in the funnel content gap analysis.

Five decisions for each old post

Every row in the inventory ends with one of five decisions. This table is a decision aid, not a Google rule.

Two habits keep these decisions honest. First, decide by reader and money page, not by traffic alone. A post with steady visits about a service you dropped is still a candidate for a redirect. Second, read the money page before rewriting. If the service page already answers the post's question, improving that page may beat keeping a rival article, as explained in how to map every article to a money page.

Don't make cuts or additions in bulk just to look new. Google's people-first guidance lists, as a warning sign, adding or removing a lot of content mainly to make a site seem fresh, and answers its own question: "(No, it won't)".

Protect the pages that already earn traffic

Some old posts carry real value: search clicks, links from other sites, or leads. Find them before anything changes. Sort the Performance report's Pages tab by clicks, check which pages other sites link to, and check GA4 for landing pages with key events. Mark those rows as protected.

1. Keep the URL. Rewrite on the same address. The links pointing at it keep working, and nothing has to be redirected.
2. Keep answering the queries that find it. Filter the Performance report to that one page and open the Queries tab. A rewrite that drops the answer people search for can cost the page its visits.
3. Add, don't replace. Add the next-stage link, the money-page link and a short direct answer near the top. Leave the parts that work.
4. If the URL must change, redirect it. Google says "we recommend that you use HTTP permanent redirects if possible, such as 301 and 308," and "Don't worry about link credit. 301 and other permanent redirects don't cause a loss in PageRank."

Moving old posts into a new folder, such as /guide/, is a URL path change, which Google's site-move guide covers. Its steps start with a map: "Prepare a URL mapping from the current URLs to their corresponding new format." It also warns: "Expect temporary fluctuation in site ranking during the move." If you are redesigning the site at the same time, Google advises: "Plan your changes to your site one after the other, not everything at the same time." Our guide on protecting visibility during a redesign or migration covers the wider project.

Redirect, canonical or 404?

Each tool does a different job. Pick by what should happen to the old page.

Three redirect mistakes come up in refresh projects:

• Everything to the home page. Google: "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site. This can confuse users and might be treated as a soft 404 error." A soft 404, in Google's description, is a page that shows a user-friendly "not found" message without returning a 404 status code.
• Chains. When a post has already moved once, point the old address straight to the final page. Google advises "redirecting to the final destination directly" and, where that isn't possible, keeping chains short.
• Removing redirects too soon. Google's site-move guide says "Keep the redirects for as long as possible, generally at least 1 year," and adds that, for users, you should "consider keeping redirects indefinitely."

A retired page that returns 404 is not a failure. Search Console's Page indexing help lists "a 404 for a page that you've removed and have no replacement for" among the right reasons for a URL not to be indexed.

When a new hub beats retrofitting

Retrofitting means adding stage labels, next links and money-page links to the posts you have. A new hub means building a pillar page with a planned reading order, writing the missing stages, and then folding in the old posts that fit. The second is more work, and it is the better choice when the old blog can't support a reading order.

A new hub doesn't require new URLs for old posts. A hub can link to pages anywhere on the site, so the posts you keep can stay where they are and appear in the hub in their place in the reading order. For a church bookkeeping firm, we added 27 new guides to an existing hub. That is an example of structure, not a result. Our post on updating old blogs covers the editing side of the posts you keep.

How to retrofit a post you keep

1. Write a direct answer to the post's question near the top.
2. Check every fact against a first-party source. Note anything that will change on a known date, as described in keeping a content guide current.
3. Add a "next" link that hands the reader to the next stage: TOFU to a MOFU comparison, MOFU to a BOFU page or the service page.
4. Link the money page with descriptive anchor text.
5. Answer the follow-up questions readers actually ask. Write FAQs for readers: Google stopped showing FAQ rich results for all sites on May 7, 2026.
6. Change the visible "Last updated" date only if the content changed in substance. Google lists "changing the date of pages to make them seem fresh when the content has not substantially changed" as a warning sign.
7. Update the sitemap's lastmod for that URL at the same time.

A hypothetical example

Here is how the decisions might fall for a hypothetical plumbing company with a 60-post blog. The numbers are round and invented for illustration.

Hypothetical example: 60 posts become 33 kept pages, plus whatever new MOFU and BOFU pages the gap analysis calls for.

After the changes go live

Update internal links so they point at final URLs, not at redirects. Submit the updated sitemap. In Search Console's Page indexing report, redirected URLs show as "Page with redirect"; Google's help says such a URL "will not be indexed," which is expected. The full launch sequence, including sitemaps and IndexNow, is in the funnel guide launch checklist.

Conclusion

Refreshing an old blog is mostly careful bookkeeping: an inventory, one decision per post, permanent redirects where URLs change, and a hub built where the old structure can't carry a reading order. Starting over from nothing discards the posts that already earn clicks and links. If you want help sorting an archive into a funnel, inventory and content refreshes are part of our content marketing services. More guides are in our GEO and AEO Guide.

Frequently asked questions