A Seasonal Page That Ranks Without New Photography

Seasonal traffic does not need a new shoot. It needs dates, a table, and an answer to the question the season creates.

Last updated: October 30, 2026

The question lands every autumn, usually with a deadline attached: do we book a photographer before the peak-season page goes up? Almost never, and the order is backwards anyway. A seasonal page gets found because it names a specific set of weeks and answers the question those weeks create. Photos help once someone's already on the page. They don't help it exist.

Key Takeaways

• Dates first, images later. A page built on a local calendar and a rate table does its work before a single new photo exists.
• One season, one question. A page that tries to cover the whole year has to hedge every sentence, and hedged sentences don't get found.
• The table is the page. Four columns of weeks, local events, minimum stay and rate band carry more weight than three paragraphs of scene-setting.
• Internal links keep it reachable in the off months. A page nobody links to is a page nobody finds in June.
• Refresh, don't rebuild. Four edits a season keeps the same URL working year after year.

Start from the calendar, not the camera

A season is a local fact. Summer in a lake town with a six-week school break isn't the same thing as August in a city that empties out and refills in September. Build the page on the generic version and it reads like every other page about the same three months, which is roughly how much traffic it gets.

The local version has a source, and the source is published. School terms are gazetted. Festivals confirm dates a year out. Trade fairs book their halls even earlier. So spend the first hour with the calendar open, not the photo library.

The second hour belongs to your own record. Which weeks actually sold last year? Not the ones you assumed would — the ones that did. Occupancy, ADR and RevPAR on the reports page answer that at month level, and the pairing tells you more than any single figure. High occupancy with a holding ADR is demand. High occupancy with a sagging ADR is a discount that worked, and that's a different season asking for a different page.

Then narrow it down. Four to eight consecutive weeks is a page. Twelve months is a brochure, and brochures don't get found for anything specific.

Tables that carry the page

A seasonal page earns its place with a table, and the table wants four columns at most: the week, what's on locally, the minimum stay you'll hold, and the rate band you're pricing into.

Four, because a fifth is where pages start guessing. A weather column is a forecast dressed up as a fact. An events column is a fact with a published date behind it, and that kind of fact holds up in front of a reader who lives down the road.

The rate column is where most pages go soft. A single "from" figure is a promise you'll break inside a fortnight, and a broken promise on a page is worse than no page at all. The rate you can defend is the one you can still see in the system in week three: what each connected channel is quoting for the same dates, and whether those nights are open. localsbnb.com keeps four channel prices beside one calendar, so the table on the page and the rates in the account don't drift apart while the season runs.

Then write the answer. One question, inside the first hundred words, in a sentence that would still be true if the reader printed it and took it with them. "Is the lake walkable from here in February" is a question. "Experience the magic of winter" is a mood, and moods don't get quoted back to you by anyone.

The minimum stay column is the one most hosts copy from last year and never touch again. A three-night minimum made sense in the week the fair was on. It made no sense in the quiet week after it, when a two-night booking beat an empty Tuesday. Rebuilding that column from your own calendar takes ten minutes, and it's usually the difference between a page that describes the season and a page that sells it.

One more test before you publish. Read the headline and ask whether a stranger could tell which four weeks it's about. If the answer is no, the page is a season page for the whole world, which means it's for nobody.

Internal links that keep it alive

A seasonal page has a short life unless something keeps pointing at it. Three links do most of the work.

The first comes from the listing page, in a line that names the season. The second comes from the other seasonal pages you already run, in a single sentence at the bottom about what the next one covers. The third comes from whatever page answers the practical questions — parking, arrival, pets — because that's the page most people land on first.

Anchor text matters more than hosts expect. "Click here" tells a reader nothing and a search engine less. "Peak-season rates for the first three weeks of July" tells both exactly what's behind the link, and it costs nothing to write.

There's a fourth thing that isn't a link at all: the same page, kept alive. Holding the URL is the whole trick. A new address each season restarts the page from zero, and a page that restarted five times never accumulated anything worth keeping.

The links also tell you when the page has stopped earning its place. If nothing on your site points to last winter's page by the following June, that's not a linking problem. It's a sign the page was written about the weather instead of about a week that people were actually searching for.

Updating it every season

Four edits, once a year, and the page stays current.

Change the dates in the headline and the opening line. Swap the rows in the table. Re-check the minimum stay, because the number you'll accept in a shoulder week has probably moved since you last looked. Then re-date the "last updated" line, because a page still saying August reads as abandoned even when every figure in it is right.

Leave the rest alone. The structure earned whatever it earned. Rewriting the introduction each year is how a page loses the one thing that made it work: a reader arriving at the same answer in the same place.

Keep a two-line log of what changed — season, rates, minimum stay. Next year you'll want to know what you were charging in the same week, and the page itself won't tell you once it's been overwritten.

Sometimes the season moves on you. A festival shifts a week, a school break gets extended, a conference changes venue. When that happens, edit the table and the dates and leave the argument alone. Why these weeks matter here is the part that took the work, and it's usually still right.

FAQ

Do I need new photos at all?

No. Photos improve conversion once someone's on the page, and a seasonal page's first job is to be found and to answer a question. Reuse the four best images you already have, cropped to the season, and put the budget into the table instead. If the page earns bookings two seasons running, that's when the shoot pays for itself.

How long should a seasonal page be?

Long enough to answer the question, and not much longer. One table, one clear answer above the fold, and enough detail to survive a reader who knows the area. Length isn't what makes a page useful to a search engine. Specificity is, and specificity runs out fast once you're describing the same four weeks a fifth way.

Can I run one page for every season?

You can, and it usually underperforms. A single page covering the whole year has to hedge every sentence, and hedged sentences answer nothing. Separate pages for peak, shoulder and the local event that fills a fortnight will each say something definite — and each one gets to keep its own URL.

A season page is a small piece of work done at the right time of year, and most hosts overbuild it. Start with the calendar you already have open, and the table will follow. When you want the channel rates that fill the rate column sitting next to the calendar they belong to, localsbnb.com is where the two meet.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Nothing here guarantees search placement, indexing or traffic, and seasonal dates vary by place and year. Confirm local holidays and event dates with the competent authority or the organiser before you publish them.