About the Content Seasonality Planner
Seasonal content is won or lost before the season starts. A guide to Thanksgiving recipes published the week of Thanksgiving is competing with pages that have been ranking since September; a sunscreen comparison that goes live in July has missed the climb that began in April. This planner tells you when interest in a topic rises, when it peaks and the date your piece needs to be live to catch it.
Each topic is measured by its Wikipedia article’s real monthly reads — every month since July 2015, human readers only, straight from the Wikimedia Foundation’s public pageview statistics. From that the page computes a seasonal index for each calendar month by classical decomposition: each month’s reads are divided by a centred twelve-month moving average, which strips out the long-term trend, and the ratios are averaged across all the years. The above-average run around the peak becomes your season, and your lead time counts back from its first month.
Two limits, stated plainly. Wikipedia reading is a proxy for search interest, not Google data; the two track each other closely for most topics, but not perfectly. And the trend figure includes Wikipedia’s own drift in readership, which the report shows alongside so you can tell a fading topic from a fading platform. The seasonal maths was checked against the statsmodels reference implementation of the same decomposition.
1.00 is an average month for that topic. Shaded months run above average; the outlined cell is the peak.
Articles Wikipedia itself rates as most similar, ranked by how many people read them in the last 30 days. Add any to the calendar (up to 10 topics).
A publish-by reminder for every seasonal topic as an .ics file for Google Calendar, Outlook or Apple Calendar, plus a CSV of the whole plan for your content tracker.
Days in the last three years when reads jumped to at least three times the previous four weeks’ median. Some are fixed dates (the holiday itself); the rest are news, the bursts a season cannot predict. A spike tells you when, not why: check the news for that date.
Writing for another market? Compare the season in another language’s Wikipedia — Southern Hemisphere readers flip summer topics, and holidays move between countries.
How to Use the Content Seasonality Planner
Type a topic and pick the Wikipedia article that best matches it — “Sunscreen”, “Tax returns in the United States”, “Easter”. Choosing an exact article matters, because the planner reads that article’s real readership; a vague match measures the wrong thing. Add up to three topics to compare them, set the lead time your site needs, and run it. The hero card gives the date your first topic needs to be live; the calendar table gives every topic’s season, peak and publish-by date.
Why Publish Before the Peak, Not At It
A new page does not rank the day it goes live. It has to be discovered, crawled, indexed and then earn its position, and for anything competitive that takes weeks. Meanwhile interest in a seasonal topic does not jump on the peak day; it climbs for a month or two beforehand, and the early searchers are often the most valuable ones — planners, buyers, people with time to read. A page published at the peak catches the tail of the season at best. That is why the publish-by date here counts back from the start of the above-average season, then subtracts your lead time on top.
How the Seasonal Index Is Calculated
The method is classical multiplicative decomposition, the same one statisticians use for retail sales and unemployment figures. For every month, the reads are divided by a centred twelve-month moving average — the average of the surrounding year, weighted so the window is centred exactly on that month. That ratio removes the long-term trend, leaving how unusual the month was. The ratios for each calendar month are then averaged across all the years and scaled so the twelve indices average exactly 1.0.
- Above 1.5 at the peak: strongly seasonal. Timing decides most of the traffic the piece will ever get.
- 1.2 to 1.5: seasonal. A well-timed publish or refresh is worth planning.
- Below 1.2: steady. No month is reliably special; publish when ready and keep the page current.
Reading the Trend Without Being Fooled by It
The five-year trend is a straight-line fit to the logarithm of the seasonally adjusted reads, so it reads as a steady percentage change per year. One caution: English Wikipedia’s overall readership has itself been drifting as search engines answer more questions directly on the results page. The report shows the whole of Wikipedia’s trend next to your topic’s, so a topic falling at the platform’s own rate is holding its share, while one falling much faster is genuinely losing interest.
Building an Editorial Calendar From the Results
- Work backwards from publish-by. Subtract your own drafting, editing and approval time to get the date the brief needs to be written.
- Refresh, don’t just publish. If you already have a page on the topic, update it shortly before the season starts; a refreshed page that already ranks recovers far faster than a new one can climb.
- Stagger your seasonal pieces. Topics with overlapping seasons compete for the same writing time. The calendar table sorted by publish-by date is the order to write them in.
- Fill the troughs with steady topics. The months where your seasonal topics are quiet are the time to write evergreen material.
Once you know when to publish, shape the piece with the Content Brief Builder, check it against the search intent with the SEO Content Analyzer, and test its title in the Headline Analyzer. Browse every Writing & Content tool for more.
Frequently Asked Questions
Why use Wikipedia data instead of Google Trends?
Because it is real, published, absolute and stable. Wikimedia releases the exact number of times every article is read each day, back to July 2015, and the figures never get rescaled after the fact. Google Trends shows a relative 0–100 score that is re-normalised for every query and sampled, so the same search can give different numbers on different days. Wikipedia readers are not Google searchers, but the two move together closely for most topics — people search for a thing and then read about it — which makes Wikipedia a good, honest proxy for when interest rises and falls.
What does a seasonal index of 2.5 mean?
That the month typically gets two and a half times the reads of an average month for that topic, after the long-term trend has been taken out. An index of 1.0 is an ordinary month, 0.6 is a quiet one. Indices are averaged over every year of data, so one freak year — a news story, a viral moment — is diluted rather than mistaken for the pattern.
How far ahead of the peak should I publish?
Far enough for a search engine to find, index and start ranking the page before readers begin looking — and readers begin looking well before the peak. That is why the publish-by date counts back from the start of the above-average season, not from the peak itself. Six weeks suits an established site with steady crawling; a new site or a competitive topic needs three months or more. Updating an existing page that already ranks can be done much closer to the season.
Why does a topic show no seasonal window?
Because no month reliably beats the average by much. When the strongest month is less than 20% above an average one, the topic is steady: interest is spread across the year, and timing a publish date around it would be false precision. Publish when the piece is ready and update it on a regular cycle instead.
Can a news event distort the result?
One event cannot distort it much, which is the point of averaging ten years of ratios. A celebrity death or a viral story creates a spike in one month of one year; the seasonal index for that month is the average over all years, so a single burst moves it only a little. Subscribers can see the daily spikes with their dates, which separates the predictable season from the unpredictable bursts.