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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Plausible Analytics: How we built a $1M ARR open source SaaS · Browse Plausible Analytics: How we built a $1M ARR open source SaaS tactics
Plausible said the content and site-structure push helped carry the company from $400 MRR to $10,000 MRR over the next nine months.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when SEO, Website, Content is relevant to site architecture, redirects, content archive and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to SEO and Website, using evidence from Plausible Analytics: How we built a $1M ARR open source SaaS as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.
SOURCE HUB
More tactics from Plausible Analytics: How we built a $1M ARR open source SaaS
Explore related GrowthDex examples and evidence connected to Plausible Analytics: How we built a $1M ARR open source SaaS.
Open Plausible Analytics: How we built a $1M ARR open source SaaS source hub