# Plausible one blog archive with 301 from older content section

> Collapse split content archives into one obvious home and 301 the older section there before you keep publishing more pages.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/plausible-one-blog-archive-with-301-from-older-content-section/
- Source: [plausible.io](https://plausible.io/blog/open-source-saas)
- GrowthDex source hub: [Plausible Analytics: How we built a $1M ARR open source SaaS](/sources/plausible-analytics-how-we-built-a-1m-arr-open-source-saas-plausible-io/)
- Last checked: 2026-06-07T03:15:30.000Z
- Rarity: uncommon
- Budget: low
- Channels: SEO, Website, Content
- Stages: site architecture, redirects, content archive, technical seo


## Why this can grow

A split archive wastes more than navigation. It splits authority, confuses internal links, and makes content feel like several side projects instead of one growing body of work. Plausible explicitly called out a cleanup where it had two content sections, 'journal' and 'blog', then redirected the journal to the blog while improving site structure. That move matters because it concentrates link equity and teaches both users and crawlers where the living archive sits. When a product later publishes comparison pages, support docs, and milestone essays, the cleaner hierarchy compounds instead of fighting itself.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where plausible one blog archive with 301 from older content section can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and Website channel.
3. Use the evidence from plausible.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Plausible said it used to have separate 'journal' and 'blog' sections, then redirected the journal to the blog as part of a site-structure cleanup.

## Adjacent tactics in the same lane

- [Plausible category-fight post against the incumbent](/growth-ideas/plausible-category-fight-post-against-the-incumbent/) - same source, 2 shared channels
- [Keyword-cannibalization redirect cleanup](/growth-ideas/keyword-cannibalization-redirect-cleanup/) - 3 shared channels, 2 shared stages
- [Plausible build-in-public updates across owned and community channels](/growth-ideas/plausible-build-in-public-updates-across-owned-and-community-channels/) - same source, 1 shared channel
- [Same-workspace 301 map after help-center migration](/growth-ideas/same-workspace-301-map-after-help-center-migration/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The category fight should clean up the whole site](/blog/the-category-fight-should-clean-up-the-whole-site/) - SEO, brand trust, operator-led distribution

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.