# The archive is a growth channel if someone keeps it alive > A plain essay on historical optimization, content decay, pruning, Search Console queues, old posts, and why the archive is not dead weight. - Canonical HTML: https://growth.iangoh.com/blog/the-archive-is-a-growth-channel-if-someone-keeps-it-alive/ - Published: 2026-06-09 - Updated: 2026-06-09T01:05:30.000Z - Categories: content maintenance, SEO, historical optimization - Niches: SaaS, AI products, marketplaces, creator tools, B2B services, startup SEO ## On this page - Old posts often carry the business - Page two is a warm lead - Decay needs a number - A refresh has to answer more of the job - Sometimes growth starts with fewer pages - UGC scale needs a quality gate - Ian's operator take ## Start with these related tactics - [HubSpot old-post lead concentration before new editorial sprint](/growth-ideas/hubspot-old-post-lead-concentration-before-new-editorial-sprint/): Refresh the old posts already producing leads before assigning another brand-new editorial sprint. - [HubSpot page-two republish before new post quota](/growth-ideas/hubspot-page-two-republish-before-new-post-quota/): Republish page-two and page-three posts with refreshed intent coverage before increasing the new-post quota. - [Reddit 30 percent decay report before refresh week](/growth-ideas/reddit-30-percent-decay-report-before-refresh-week/): Build a content-decay report that flags posts down 30% or more before scheduling a refresh week. The archive is where good growth work either compounds or goes stale quietly. Most teams prefer the clean feeling of a new content calendar. New topics, new briefs, new publish dates. The archive is messier. It has old screenshots, old promises, pages that almost rank, pages that used to rank, and URLs nobody wants to be responsible for anymore. ## Old posts often carry the business [HubSpot old-post lead concentration before new editorial sprint](/growth-ideas/hubspot-old-post-lead-concentration-before-new-editorial-sprint/) is the reminder. HubSpot found that old posts carried most of the blog's views and leads. That changes the job. The archive is not a warehouse. It is part of the sales floor. For a founder, the first question is not what should we publish next. It is which existing page already has demand and still leaves money, trust, or clarity on the table. ## Page two is a warm lead [HubSpot page-two republish before new post quota](/growth-ideas/hubspot-page-two-republish-before-new-post-quota/) is a useful habit. If a post sits on page two or three, the market has already given you a signal. The topic has demand. Google can understand the page. The site may be close enough to win with a better answer. That is not a guarantee, but it is a better bet than pretending every new URL starts with equal odds. Warm URLs deserve a queue. ## Decay needs a number [Reddit 30 percent decay report before refresh week](/growth-ideas/reddit-30-percent-decay-report-before-refresh-week/) puts a threshold on the problem. A page down 30 percent in clicks deserves inspection before the team writes another post about the same theme. This is where Search Console is less like a dashboard and more like an operating meeting. Which pages lost clicks? Which lost impressions? Which lost CTR? Which gained impressions but failed to earn the click? Each answer points to a different fix. ## A refresh has to answer more of the job [Reddit 31 percent expansion before cosmetic refresh](/growth-ideas/reddit-31-percent-expansion-before-cosmetic-refresh/) is the anti-theater rule. Changing the year in the title is not maintenance. If the SERP moved on, the page has to move too. Look at the current winners. What do they answer that you skip? What screenshots are newer? What examples are more useful? What objections do they resolve before you even mention them? ## Sometimes growth starts with fewer pages [Seer 14K URL pruning before more indexation](/growth-ideas/seer-14k-url-pruning-before-more-indexation/) is the part that feels strange until you have seen a large site rot. More URLs can mean more confusion. Some pages need an update. Some need a merge. Some need a redirect. Some should leave the index. A smaller, cleaner site can be easier for buyers and crawlers to understand. That is boring work. It also wins more often than founders want to admit. ## UGC scale needs a quality gate [SeoProfy toxic UGC cleanup before migration push](/growth-ideas/seoprofy-toxic-ugc-cleanup-before-migration-push/) matters for marketplaces, creator tools, AI products, and any product where users create public pages. Scale can help search, but only when the public pages are worth indexing. Thin profiles, empty boards, duplicate pages, and spammy states make the product look bigger while making the site weaker. Decide what deserves search visibility before the crawl budget goes there. ## Ian's operator take In consumer platforms and market-entry work, the archive tells you what the market already understood. A founder scaling across MENA, Southeast Asia, creator platforms, or social products should not throw that signal away. Old pages show which language, workflows, and use cases already made sense to real people. The trap is treating maintenance as housekeeping. It is not. Maintenance is where distribution learns from itself. Refresh the pages that almost win. Prune the pages that confuse the story. Keep the archive alive enough that it keeps earning trust. For founders who want an operator-led pass on which archive pages to refresh, merge, prune, or turn into advisory-led landing pages, Ian works through [Ian Goh advisory](https://iangoh.com/advisory). ## Related GrowthDex tactics - [HubSpot old-post lead concentration before new editorial sprint](/growth-ideas/hubspot-old-post-lead-concentration-before-new-editorial-sprint/) - SEO, Conversion, Content Refresh - [HubSpot page-two republish before new post quota](/growth-ideas/hubspot-page-two-republish-before-new-post-quota/) - SEO, Content Refresh, Search Console - [Reddit 30 percent decay report before refresh week](/growth-ideas/reddit-30-percent-decay-report-before-refresh-week/) - SEO, Content Operations, Search Console - [Reddit 31 percent expansion before cosmetic refresh](/growth-ideas/reddit-31-percent-expansion-before-cosmetic-refresh/) - SEO, Content Refresh, Editorial Ops - [Seer 14K URL pruning before more indexation](/growth-ideas/seer-14k-url-pruning-before-more-indexation/) - SEO, Content Pruning, Technical SEO - [SeoProfy toxic UGC cleanup before migration push](/growth-ideas/seoprofy-toxic-ugc-cleanup-before-migration-push/) - SEO, UGC Cleanup, Technical SEO ## Essay chronology - [Newer essay: The Slack app should start helping before the docs tab opens](/blog/the-slack-app-should-start-helping-before-the-docs-tab-opens/) - onboarding, product-led growth, brand trust - [Older essay: The App Store page should qualify the traffic it invites](/blog/the-app-store-page-should-qualify-the-traffic-it-invites/) - App Store, mobile growth, brand trust, paid acquisition ## Keep reading - [The free tool has to do the job before it asks for the lead](/blog/the-free-tool-has-to-do-the-job-before-it-asks-for-the-lead/) - free tools, SEO, product-led growth - [The answer should be easy to quote before you chase the mention](/blog/the-answer-should-be-easy-to-quote-before-you-chase-the-mention/) - AI visibility, SEO, content strategy - [The utility page should finish the job before the pitch](/blog/the-utility-page-should-finish-the-job-before-the-pitch/) - free tools, SEO, product-led growth ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [HubSpot: Historical blog optimization](https://blog.hubspot.com/marketing/historical-blog-seo-conversion-optimization) · [GrowthDex source hub](/sources/hubspot-historical-blog-optimization-blog-hubspot-com/) - [HubSpot Academy: How HubSpot uses blogging to rank #1 on Google](https://blog.hubspot.com/marketing/rank-number-one-google) · [GrowthDex source hub](/sources/hubspot-academy-how-hubspot-uses-blogging-to-rank-1-on-google-blog-hubsp/) - [Reddit r/seogrowth: Content decay refresh process](https://www.reddit.com/r/seogrowth/comments/1raxdex/content_decay_is_killing_our_traffic_how_are_you/) · [GrowthDex source hub](/sources/reddit-r-seogrowth-content-decay-refresh-process-reddit-com/) - [Reddit r/Blogging: 15,000 URL content refresh analysis](https://www.reddit.com/r/Blogging/comments/1qv7cwh/i_analyzed_15000_urls_heres_what_actually_worked/) · [GrowthDex source hub](/sources/reddit-r-blogging-15-000-url-content-refresh-analysis-reddit-com/) - [Seer Interactive: Content pruning case study](https://www.seerinteractive.com/insights/content-pruning-case-study) · [GrowthDex source hub](/sources/seer-interactive-content-pruning-case-study-seerinteractive-com/) - [SeoProfy: xTiles SaaS SEO cleanup case study](https://seoprofy.com/case-studies/xtiles/) · [GrowthDex source hub](/sources/seoprofy-xtiles-saas-seo-cleanup-case-study-seoprofy-com/) ## Editing notes - Kept the essay focused on archive maintenance as a growth system, not generic content advice. - Used concrete operating moves: page-two queues, 30 percent decay checks, expansion, pruning, and UGC cleanup. - Used Ian's growth background as context for market-entry and platform archives without inventing personal anecdotes. - Removed ranking guarantees and avoided inflated SEO language. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.