Ninety days is about the shortest window in which your SaaS content program can show real AI-citation traction. It's also about as far ahead as most teams can plan before what actually happens drifts away from the plan.
Two separate findings point at that number, one about when citations start and one about how fresh cited pages are, and a quarterly cadence catches both. I'll show you each in the next section.
The template assumes a small SaaS team publishing 25-40 posts a quarter. It gives you an explicit mix, a refresh habit most editorial calendars skip, and enough flex to catch news without breaking your topic clusters. It won't choose your strategy for you, since that comes down to which clusters you commit to. Once you've made that call, the calendar is how the strategy ships.
Why 90 days is the right window
It comes down to two data points. The first is when citations start. Averi ran a controlled sprint on its own content and tracked the moment AI engines began citing it:
| Averi's 12-piece sprint | Result |
|---|---|
| What they shipped | 1 pillar page (3,000-4,000 words), 6 new cluster spokes, 5 refreshes of posts ranking 5-15 |
| First citations | Piece 11 |
| Full traction | Piece 14: cited in 4 of 10 prompt variants across ChatGPT, Perplexity, Claude and Gemini |
| Time it took | 8-12 weeks |
That fits inside a quarter with time left for cleanup. A calendar of 25-40 posts clears the threshold with margin.
The second is freshness. Ahrefs looked at 16.975 million AI citations across seven platforms and compared how old the cited pages were:
| Pages | Median age |
|---|---|
| Cited by ChatGPT | 958 days |
| Cited by AI engines overall | 1,064 days |
| Cited by Perplexity | 1,166 days |
| Cited by Google AI Overviews | 1,432 days |
| Ranking in organic search | 1,432 days |
So AI-cited pages run 25.7% fresher than what ranks organically. ChatGPT rewards the freshest content, while AI Overviews sits at nearly the same age as the organic results. A quarterly refresh keeps you inside ChatGPT's window, and you won't waste effort refreshing pages AI Overviews would happily quote from three years ago.
Where most teams go wrong is rhythm. They plan once a year, execute every week and measure every month, while the signals AI engines send back move faster than any of that. Ryan Law's Day-1 Head of Content playbook gets at the shift underneath:
if i was starting my FIRST DAY as a new Head of Content, here's what i would do: - build a new blog using a static site generator, host with GitHub, deploy with Netlify or Cloudflare Pages. for an existing blog like WordPress, set up an MCP connector. the goal is a fully
Ryan Law@thinking_slowJun 8, 2026He described a static site, a CMS connected over MCP, and Gong, Intercom and Slack piped into the calendar. That kind of content operation lets you run the calendar as a real system instead of a spreadsheet. If your tooling can't tell you which posts got cited last week, your plan is a guess.
The post mix across 90 days
Say your team ships 30 posts in the quarter. This is the mix that fits both Averi's inflection window and the Ahrefs freshness curve:
| Piece type | Posts | Share of calendar | What it's for |
|---|---|---|---|
| Pillar hubs | 2-3 | 6-10% | 2,000-3,500-word buyer's guides that anchor topic clusters; one at week 1, one at week 5, one at week 9 if you have the resources |
| Cluster spokes | 15-20 | 50-60% | Listicles, comparisons, alternatives-of, use-case pages, statistics roundups; 1-2 a week |
| Refreshes | 6-10 | 20-30% | Pages ranking 11-30, or pages AI cited last quarter that slipped this quarter; 1-2 a week alongside new content |
| News reactions | 2-4 | 5-15% | Flex slots, filled only when a real news window opens |
| Guest experts or interviews | 1-2 | 3-5% | Featured content with an outside voice |
Every spoke links back to the pillar it supports. Keep the news slots empty until something real happens, like a product launch, an algorithm update or category news. Guest pieces compound more slowly than pillar content, but they add EEAT signal.
Semrush makes the case for a tagging habit most calendars skip:
Map TOFU, MOFU, and BOFU content types, define target keywords and personas and track KPIs and stage-specific success metrics with our free content funnel planner template 👇 https://t.co/hSNaz2fTFR. https://t.co/cVtzPdTqEr
Semrush@semrushJul 8, 2026
Tag every planned piece by funnel stage (TOFU, MOFU or BOFU), and lock in the target keywords and personas before anything gets a date. The tag is what exposes an imbalance. Three months of TOFU listicles with no MOFU comparisons means your citations pile up in the awareness layer, and nothing converts.
You're getting AI traffic. But do you know where it comes from?
RankControl credits every visit to the assistant that sent it: ChatGPT, Perplexity, Claude, Gemini, Copilot, or Grok. Full source attribution, next to your Google traffic.
The weekly cadence
A quarter gives you 12-13 working weeks. Here's a rhythm your team can hold without burning out, seen at three zoom levels:
| When | What ships |
|---|---|
| Every Monday | New spoke #1 |
| Every Tuesday | Refresh #1 |
| Every Wednesday | New spoke #2 |
| Every Thursday | Reactive/flex slot, or refresh #2 if there's no news |
| Every Friday | Interlinking audit and measurement checkpoint |
| Week 1 of each month | Pillar publish |
| Weeks 2-4 | Spokes and refreshes on that pillar's cluster |
| End of each month | Cluster review, keyword-gap analysis, adjust next month's plan |
| Month 1 of the quarter | Category-defining content (what is X, how does X compare) |
| Month 2 | Use-case and mid-funnel content (X for Y persona, X for Y outcome) |
| Month 3 | Comparison, decision and refresh push (X vs Y, X alternatives, refresh top performers) |
Thursday is your flex day. Keep about 20% of each week open for reactive content, because the engines pick up new pages quickly. Google AI Mode indexes new content within 24 hours. Perplexity takes 12-24 hours, and ChatGPT crawls new pages about 8x more often than Google does in the first five days.
The month-by-month progression is our own view, and no study backs it. It does match how AI engines seem to build coverage, though: category first, then use case, then decision.
Refresh discipline: the piece most calendars skip
When people argue for refreshes, they point to HubSpot's historical-optimization program, and these numbers are why:
| HubSpot's historical optimization | Result |
|---|---|
| Monthly blog views from posts published in prior months | 76% |
| Blog-generated leads from posts published in prior months | 92% |
| Their fix | Refresh 2-3 posts per week |
| Monthly organic views on updated posts | 106% average lift |
| Monthly leads | More than doubled |
Old posts were doing most of the work, and that month's new content wasn't. Budget 20-30% of your production hours for refreshes, and run them by these rules:
| Rule | How |
|---|---|
| Prioritize pages ranking 11-30 | Skip the top 10 (already performing) and the bottom (needs a rewrite); the middle is where a small update turns into a big rank shift |
| Change substantive things | Update stats older than 12 months, add a section on where the topic has moved, fix broken outbound links, add fresh named entities, rewrite the opening 100 words if the answer wasn't front-loaded |
| Never change the URL | Preserve link equity; update dateModified in schema and add a visible "Last updated" line |
| Batch by cluster | All comparisons in cluster A one week, all listicles in cluster B the next, fixing cross-links as you go |
| Track refresh ROI | Measure citation and traffic lift 30 and 60 days after each refresh; that tells you which cluster deserves refresh budget next quarter |
Refreshing quarterly beats refreshing once a year by roughly 42%, according to an Animalz benchmark. And once decay starts, content loses about 1.21% a week. Every refresh you skip leaves compound gains on the table.
Team velocity and realistic cadence
The biggest calendar mistake I see is a team promising more volume than it can actually produce. Size your plan to the team you have:
| Team | New posts a week | Refreshes a week | Per quarter | Watch out for |
|---|---|---|---|---|
| Solo operator | 1-2 | 1 | 20-30 posts in 90 days | Aggressive but sustainable if you protect the time |
| Pod (2-6 people) | 3-5 | 1-2 | 45-75 posts | The baseline for a serious SaaS content program |
| Program team with AI assistance | 4+ | 2-3 | 75-100+ | Needs disciplined quality gates or output degrades fast |
| Sweet spot for most teams | 2-5 | 1-2 | Publishing multiple times a week correlates with reporting "strong results" |
Orbit Media's 2025 blogger survey gives you a baseline for the work behind each post:
| Orbit Media survey, 808 respondents | Result |
|---|---|
| Average time to produce a post | About 3.5 hours; deeper research pieces take 6-10 |
| Average post length | 1,333 words |
| Bloggers publishing weekly or more | Only 39% |
Now do the arithmetic for your own team. With 20 hours of writing capacity a week, planning eight pieces a week guarantees burnout by month two.
An r/digital_marketing thread shows what an aspirational calendar looks like up close:
the marketing team's content calendar has 94 pieces planned for Q3. asked how many were published in Q2. the answer was 31 out of 88 planned. nobody adjusted the Q3 plan.
sat in the quarterly planning meeting. the content team presented an ambitious Q3 calendar. 94 pieces across blog, social, email, and video. asked a simple question: how many of the Q2 planned pieces actually got published? silence. then th...
| The team in that thread | Pieces |
|---|---|
| Planned for Q2 | 88 |
| Shipped in Q2 | 31, a 35% completion rate |
| Planned for Q3 | 94 |
Nobody in the room adjusted for capacity. The post's diagnosis was that "the calendar exists to signal ambition, not predict output." Teams count pieces published instead of the share of planned pieces published, so the gap between plan and execution stays invisible quarter after quarter. Don't let that happen to you. Build the new plan on the capacity you actually realized last quarter, and leave the aspirational number out of it.
We'll show you exactly where your brand stands in AI search.
No commitment. $0 due today, cancel anytime. See how ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode talk about your brand today.
Measurement checkpoints
Measurement is what turns your calendar from a spreadsheet into a system. You need four checkpoints:
| Checkpoint | What you look at |
|---|---|
| Weekly | Citation share on the top 30 buyer prompts; which of last week's posts got cited on which prompts; which existing pages lost citation share |
| Monthly | Cluster review: which clusters are producing citations and which have stalled; adjust next month's plan to what's earning share |
| Day 60 (end of month 2) | Mid-quarter check: if Averi's 12-piece inflection hasn't shown up, something in the mix is off, so diagnose it before day 90 |
| Day 90 (end of quarter) | Full retrospective: which posts made the top 5 citations for their target prompts, which clusters compounded, which failed; plan Q2 with a corrected mix |
Our AI visibility tracking covers the weekly part, with citation checks across six engines and a trend view for the monthly and quarterly reviews. You can sample by hand, but practitioner data has roughly 40-60% of citations churning every 30 days. That volatility makes weekly manual work brutal by month two.
A thread on r/seogrowth landed on a similar order of work:
If you had to start SEO from zero today, what would be your first 90-day plan?
I've seen a lot of conflicting advice about SEO in 2026. If you had a brand-new website and no authority, how would you spend your first 90 days to get traction?
The top-scored reply said your first weeks shouldn't touch keywords at all. You build a real knowledge base of the business first, with offers, features, transcripts and internal docs, before a single URL gets planned, because the calendar is only as good as what feeds it. Another commenter split the quarter into a 30-day audit, 30 days of intent-mapped content and a 30-day double-down, which lines up with the month-by-month progression above.
The traps
Four failure modes sink these calendars. Here they are, most frequent first.
Over-planning leads the list. When every slot is filled, you miss every news window, so reserve 20% of each week as flex.
Next is a plan with no refreshes in it at all. HubSpot's numbers above are the warning, so put 20-30% of your production hours into refreshes.
The third is having no measurement checkpoints. Teams review lagging indicators like traffic and rankings monthly, and by the time they see a drop, the window to correct it has closed. Block Friday citation-share reviews into your calendar.
Burnout from the weekly cadence comes last. Running a team above 85% capacity for several weeks produces attrition and measurable quality drops, and most experts who commit to consistent publishing burn out within six months. Plan against the capacity you really have.
What to ship this week
If you're starting the calendar next Monday, this week is setup:
| Step | What to do |
|---|---|
| Audit last quarter's output | Work out the percentage of planned pieces that actually shipped, and plan the new quarter against that realized capacity |
| Define topic clusters | Pick 2-3 for the quarter |
| Pick buyer prompts | Choose 30 to track citation share on, and sample them now for a baseline |
| Draft the pillar for Cluster 1 | 2,000-3,500 words, published Monday of week 1 |
| Schedule the 90 slots | 2-3 pillars, 15-20 spokes, 6-10 refreshes, 2-4 flex slots |
| Set weekly Friday reviews | Citation share, coverage gaps, adjustments |
Our content engine handles format scheduling and pillar-to-spoke links as one system, and it flags its own articles when rankings or citations slip. For how each post should be built to earn citations once it ships, our anatomy of a high-citation article covers the per-post gates in detail.
Ninety days is long enough to learn whether your content strategy earns AI citations. It's also long enough for a mediocre calendar to burn out a good team, and this template is built to survive both. Plan against the capacity you really have, refresh on schedule, and measure every week.
Know exactly what AI says about your competitors.
RankControl's Recon Agent monitors competitor citations across ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode. See where they show up and you don't.
