Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Publishing Into a Peak Is Publishing Too Late
When demand arrives, the results page has already been settled by pages that were live months earlier. A page published in the first week of the season is being discovered and assessed while its competitors are accumulating clicks. The work is not harder, it is just scheduled wrongly.
The mechanism is the ordinary one. A new page has to be discovered, crawled, indexed, and then given enough exposure for the system to form a view of whether it satisfies the query. None of that is instant, and on a competitive seasonal term the pages you are competing with have been through that process already, some of them several years running.
Practical guidance clusters around having the page live and indexed three to six months before the peak, with the longer end for high-competition retail events. Treat that as a planning shape rather than a precise rule: the underlying requirement is that the page has been assessed before the traffic arrives, and how long that takes depends on your site.
Find Your Cycles, Not the Global Ones
Sixteen months of your own Search Console data will show you your market's shape, which frequently differs from the global pattern for the same words. Export impressions by query and by month, and look for what repeats.
The distinction matters more than it sounds. A home services business may find demand peaks weeks before the weather event people associate it with, because the searches are anticipatory. A B2B business may find its cycle tracks budget quarters rather than anything seasonal in the ordinary sense. A global trend line for the same keyword shows you an average of markets you do not serve.
Use Google Trends as confirmation rather than as the primary source. It is good for establishing that a pattern is real and repeating across years, and for spotting the rough shape of a cycle in a market where you have no data yet. It is not a substitute for your own impressions data once you have sixteen months of it.
One Permanent URL, Refreshed Annually
Publish seasonal content at a URL containing no year, and update that page every cycle. A new page each year restarts from nothing and divides references across a series of near-identical documents, which is the slow way to guarantee none of them ever gets strong.
| Approach | What happens over three years | Verdict |
|---|---|---|
| New URL with the year in it, annually | Three competing pages, references split, each starting cold | Avoid |
| One evergreen URL, content refreshed | One page compounding, assessed and known before each cycle | Default choice |
| Dated pages redirected to the newest | Workable, with redirect chains accumulating over time | Acceptable if you inherited it |
| Page unpublished out of season | Discovery restarts each year, worst of all options | Never |
Leave the page live year-round. Taking it down out of season means the URL has to be rediscovered and reassessed every cycle, throwing away exactly the head start the strategy is built on. If the content would be confusing off-season, change the framing rather than removing the page: an out-of-season visitor is a future customer and a crawler visit you want to keep.
The Annual Refresh, and What It Should Change
A refresh is a factual update, not a rewrite. Dates, prices, availability, anything that expired, and anything last year taught you about what people actually asked. Changing the publication date without changing the content is not a refresh and does not fool anything.
- Schedule it against the cycle, not the calendar.
If the peak is in December and you want to be live by August, the refresh belongs in July. Put it in whatever system holds your work with a real date, because this is the step that silently does not happen.
- Read last year's queries first.
Filter Search Console to the page and to last year's season. The queries it received are a list of what people actually wanted, which is a better brief than anything you will imagine in July.
- Update the facts that expire.
Prices, dates, deadlines, product availability, and any reference to the current year in the body text. These are also the claims a reader checks first, so being wrong here costs more than being incomplete elsewhere.
- Refresh internal links pointing at it.
Seasonal pages get orphaned between cycles as newer content takes navigation slots. Restoring the links before the season is part of the refresh, not a separate task, per internal linking.
- Update the modified date honestly.
Because the content genuinely changed. Sites that bump dates on unchanged pages are doing something visible and pointless, and it undermines the dates on the pages you did update.
Reporting Around Seasonality Without Lying
Traffic falling after a peak is the season ending, not a failure. Compare year over year, not month over month, and say which comparison you are using. Most alarming SEO reports are seasonality presented without that context.
The inverse error is just as common and more flattering: reporting a rise into a peak as the result of work done that quarter. If demand triples every autumn, a September increase is not evidence that the content programme is working, and claiming it is will make the January report impossible to explain.
Two habits fix both. Always show the same period last year alongside the current one, and annotate your reporting with the seasonal shape so that anyone reading it knows what to expect before they see the number. That belongs in the structure described in the SEO reporting framework, and it is the same reasoning that makes an uncontrolled before-and-after unreliable in SEO split testing.
Questions People Ask About Seasonal SEO
- How far in advance should seasonal content be published?
Months, not weeks. Common practical guidance is to have the page live and indexed three to six months before the demand peak, with longer lead times for high-competition retail events. The reason is mechanical: the page needs to be discovered, assessed, and given a chance to accumulate signals before the traffic arrives, and none of that happens instantly.
- Should I create a new page each year or reuse the same URL?
Reuse the same URL and update it, in almost every case. A new URL each year restarts from zero and splits any accumulated references across several near-identical pages. Keep one evergreen URL without a year in it, refresh the content and dates annually, and let the page compound instead of resetting.
- How do I find my seasonal patterns?
Your own Search Console data over sixteen months is the most reliable source, because it reflects your market rather than a global average. Export impressions by query and by month and look for the repeating shapes. Google Trends is useful for confirming the pattern is real and industry-wide rather than something specific to one year.
- What if the peak has already passed?
Publish anyway and treat it as next year's asset. A page live now has months to be assessed before the next cycle, which is precisely the position you want. Rushing something out during the peak is the worst option: it competes with pages that have been established for months and it will not be ready next year either.
- Does traffic dropping after a peak mean something is wrong?
Usually not, and confusing seasonality with decline is one of the most common reporting errors. Compare against the same period last year rather than against last month. If year-over-year is flat or up while month-over-month is down, the season ended and nothing broke.
