One Page for a Recurring Series

A retreat you run three times a year has a problem a one-off event does not: its page keeps expiring. Every time you set the next date, you create a new event with a new address, and whatever recognition the last page earned — the links pointing to it, the search results it climbed into, the people who bookmarked it — gets thrown away and has to be rebuilt from nothing. You did this work last time. You will do it again next time, from zero, unless something changes. A series page fixes this by giving the retreat, course, or class itself one lasting address, with the individual dates living inside it rather than replacing it each time. The offering stays put. Only the dates underneath it change.

A series page describes the offering once: what it is, who leads it, and what someone can expect to experience, whether that is a weekend retreat, a recurring course, or a regular class. Every upcoming date is listed beneath that single description rather than each date carrying its own separate write-up. This matches how someone actually arrives at the page. A person following a link a friend shared, or a page a search turned up, wants to understand what they are looking at before they decide when to show up for it. Reading the description first and picking a date second is the natural order; a page built solely around one date reverses that, putting a booking decision in front of someone who has not yet been told what they would be booking.

Search engines and ordinary word of mouth both reward pages that have been around and accumulated attention — links from other sites, people returning to it, a history of being found. A page that has existed for two years and gathered links in that time is worth considerably more, in practical terms, than one created last week with none of that behind it. Running every occurrence of a retreat at its own address means each occurrence starts from zero; the recognition the last date's page built up stays with that now-expired page and does nothing for the next one. Consolidating every occurrence under one series address means the opposite happens: each time the retreat runs, whatever attention that occurrence brings adds to the same page's standing instead of competing against it. Two years and a dozen occurrences in, the series page carries the weight of all of them. A page rebuilt each time never gets the chance to carry any of it.

Because the series page is not tied to any single occurrence, a sold-out or finished date does not end the page's usefulness the way it would if the date were the whole page. The description of the offering stays exactly where it was; only the list beneath it changes, dropping the date that has passed and showing whatever comes next. This matters for the person who bookmarked the page two years ago and finally comes back to it, or who arrives too late for anything currently listed. Instead of landing on a page that reads as finished, with nothing left to do but leave, they land on the same lasting page and see what is coming afterward. A dead-feeling page with no path forward is exactly what a series page is built to avoid — it gives someone who missed this round somewhere to stay connected rather than a dead end.

The series page is not a replacement for the individual date pages — both exist at once. Each occurrence of the retreat keeps its own page, which is where someone lands if they arrive at a specific date directly, say from a ticket confirmation or a listing for that particular weekend. The series page sits above all of them: it is the one lasting address that describes the offering itself and lists every date, individual pages included, so people arrive at the level that matches what they are actually looking for — the retreat in general, or this one occurrence of it.