There you are, trying to help a parent find something to do this Saturday. They find your toddler class, open the page, and still cannot tell whether the class is happening this week. The poster says “Saturdays this fall,” the calendar is tucked inside a widget, and the latest reminder has already disappeared into a social feed.
I have made the same kind of mistake. I treated the first date of a weekly event as if it described the whole schedule. It did not. A real class can be well-loved and still be effectively invisible when its important facts are hard to read or trapped somewhere software cannot reliably use.
1. Can someone answer the question in two seconds?
For a recurring event, the useful question is not “did this class ever happen?” It is “is it on this week, and can we get there?” Put the answer in one ordinary line on a dependable page.
Toddler Tumble — Saturdays this fall! (see flyer)
Toddler Tumble (ages 2–3) · Every Saturday, 10:00–10:45am · Sep 6 – Dec 13 · No class Nov 29 · $15 drop-in · Register: <page>
“Saturdays this fall” sounds friendly, but it makes a parent hunt for the first date, the last date, and any holiday exceptions. It also leaves a search result, assistant, or local calendar unable to confirm a specific Saturday. The second line gives the audience, recurrence, hours, date range, exception, price, and next action in one readable place.
You do not need to write like a database. You do need to write the facts so a busy person can copy them, check them, and make a decision without opening six tabs.
2. Can a visitor tell whether the place is open?
Places need the same treatment. If someone is deciding where to take the kids after lunch, say plainly whether they can come today. Here are three short lines that do the job:
Open daily 9–5
Weekends only, 10–4, through Oct 31
Closed for a private event Sat Oct 12
That clarity matters more than it may seem. A parent with a short break between errands is not going to investigate an ambiguous opening time. If the answer takes too much work, they may choose somewhere else that is easier to trust. The lost visit is not caused by a lack of enthusiasm for your event; it is caused by uncertainty arriving at the wrong moment.
3. Where should the details live?
Keep the embedded calendar widget if it is useful for your visitors. Keep the social post if it helps with reminders and last-minute energy. But put the essential details in ordinary page text too: the title, date or recurrence, start and end time, audience, location, price, and registration link.
An embedded calendar can look perfectly clear in a browser while leaving the actual details difficult for search engines, AI answers, and listing tools to read. An Instagram story can reach regular followers and still be a poor permanent home for a seasonal class. Give every class or series one stable page URL, then let the widget and social post point back to it.
This also gives you one place to correct an exception. If there is no class on a holiday, update the dependable page. Do not make a parent compare an old flyer with a newer comment and hope they spotted the difference.
4. What makes the same facts portable?
Explicit dates and times are the best starting point. For a series, include the recurring day, the overall start and end dates, and every cancellation you already know about. A stable URL means the answer can be found again next week, not only while one announcement is circulating.
If you have help maintaining the site, add schema.org Event or Course markup with startDate and endDate or an eventSchedule. You can also publish a public ICS calendar feed. These are ways to carry the same clear facts into other places; they are not substitutes for writing the facts for people first.
Why this matters if you run something local
Clear event facts give a family a fair chance to find a class, market, camp, or festival that is still on. They also give any local guide the information it needs to show the right event at the right time. That is a small publishing habit with a very human payoff: fewer guesses, fewer disappointed arrivals, and more chances for the people looking for you to actually get there.
The ten-minute fix
- Put the event's dates, start and end time, audience, location, price, and registration link in plain text on its page.
- For a series, state the recurring day, overall start and end dates, and every cancellation or holiday exception.
- State whether a place is open, limited-hours, or closed, with dates where needed.
- Give the class or series a stable URL instead of replacing it with each seasonal announcement.
- Add
EventorCoursemarkup, or link a public ICS calendar feed.
