90-Day Content Calendar Template
Most content calendars are a spreadsheet of headlines and dates. This is the 90-day map that ties topic clusters, internal links, refresh cycles, and distribution into one structure.
Why this matters
- 1Calendars with topic clusters compound across the 90 days. Calendars with one-off posts don't.
- 2Refresh windows baked into the calendar prevent the most common decay pattern (top-performing posts going stale).
- 3Distribution slots assigned upfront beat trying to retroactively promote published pieces.
- 4An AI agent can drive a clustered calendar autonomously. It cannot drive a list of disconnected headline ideas.
The template, step by step
- 01
Lock 3-5 pillar topics for the quarter
Pillar topics are the umbrella themes you'll own this quarter. Pick topics where you have a real opinion and authority. Bad pillars: 'marketing.' Good pillars: 'AI SEO for SMBs', 'agentic operations for hospice', 'topic clusters in 2026'.
- 02
Map 8-12 spokes per pillar
Spokes are specific questions your audience asks about the pillar. Mine from People Also Ask, Reddit threads, support tickets, sales objections. Each spoke is a separate post. 8 to 12 spokes per pillar gives the pillar enough internal-link weight.
- 03
Assign one spoke per week per pillar
If you have 3 pillars and 12 weeks, you ship 1 spoke from each pillar per week. That's 3 posts per week. Adjust to your capacity. Don't ship all 12 spokes of one pillar before moving to the next; the cluster needs all 3 pillars progressing.
- 04
Bake in refresh windows at week 4, 8, 12
Every 4 weeks, refresh the top 2 spokes by traffic. Add new data, update stats, fix dead links, expand the FAQ. Refreshes signal freshness to Google and AI engines, often more valuable than a new post.
- 05
Schedule the pillar page last
Pillar pages get written in week 11 or 12, after most spokes are live. The pillar synthesizes what you've learned writing the spokes. Don't write the pillar first; the outline always changes.
- 06
Assign distribution slots
Every post gets 3 distribution touchpoints: LinkedIn (day of publish), newsletter (day +3), Twitter/X thread (day +7). Mark these slots on the calendar. Most content underperforms because distribution is an afterthought.
PILLAR 1: ____________ Spoke 1 (Week 1): ____________ Spoke 2 (Week 2): ____________ Spoke 3 (Week 3): ____________ Spoke 4 (Week 4): ____________ [Refresh top 2 spokes this week] Spoke 5 (Week 5): ____________ Spoke 6 (Week 6): ____________ Spoke 7 (Week 7): ____________ Spoke 8 (Week 8): ____________ [Refresh top 2 spokes this week] Spoke 9 (Week 9): ____________ Spoke 10 (Week 10): ___________ Pillar page (Week 11): ___________ Spoke 11 (Week 12): ___________ [Refresh top 3 spokes this week] PILLAR 2: ____________ (same structure) PILLAR 3: ____________ (same structure) DISTRIBUTION (per piece): Day 0: LinkedIn post + cross-post to X Day 3: Newsletter feature Day 7: X thread (5-7 tweets) Day 14: LinkedIn comment thread on a related industry post Day 30: First refresh review (top performers only)
Common mistakes
- Skipping pillar mapping. Without pillars, the calendar is a list of headlines that don't compound.
- Picking 8 pillars instead of 3. Spread too thin to build cluster authority.
- Treating distribution as a separate exercise. Bake into the calendar upfront.
- Not scheduling refresh windows. Top posts decay; refresh recaptures the traffic.
- Writing the pillar first. You don't know what it should say until you've written 8 spokes.
Let PostWyse run this template on autopilot.
Wyse drafts every input, every personalization, every follow-up in your brand voice. You approve before anything goes live.
Questions
Can I run this calendar with a one-person content team?
Yes, especially with PostWyse handling drafts. A solo content lead ships 2-3 pieces per week with PostWyse and reviews 3-5 hours per week. Without AI, 1 piece per week is realistic.
How is this different from a Notion content calendar?
Notion calendars are usually a flat list of dated headlines. This template structures around clusters and refresh windows so the calendar compounds for SEO and AIO. The format works in Notion, Airtable, or anywhere else.
What if my industry is too small for 3 pillars?
Cut to 2 pillars with 10-12 spokes each. Don't go below 2; you need at least 2 clusters to demonstrate topical breadth to AI engines.
How long until I see results?
Volume lift immediate. SEO traffic: 90-120 days. Compounding cluster effect: month 4-5. AI engine citations: usually month 3-6 after cluster is dense enough.
Should I publish on a fixed day each week?
Yes. Consistency signals reliability to search engines and to subscribers. Tuesday and Thursday are best for B2B; Wednesday for B2C. Pick a day and stick.
Blog Cluster Plan Template
Topic cluster strategy: one pillar page plus eight to twelve spokes. The structure Google and AI engines both reward.
AI SEO Brief Template
The brief structure that gets an AI to write a 1,500-word SEO post that actually ranks. Eight inputs, three deliverables.