Children's Activity Centres: Agent Comparison Shopping for Parents

Parents are busy. When they need to find swimming lessons for a six-year-old on Saturday mornings, or a holiday camp for a ten-year-old during half term, or gymnastics classes that fit around school pickup, they increasingly ask an AI agent to compare the options. The agent's job is to find centres within a reasonable distance, check which ones offer the right activity for the right age group at the right time, and present the shortlist.

How well an agent can do this depends almost entirely on how a centre presents its information online, across activities like swimming, gymnastics, dance, martial arts, and multi-activity holiday camps.

Two Common Approaches

Centres tend to fall into two groups based on how they publish their timetable and pricing.

The PDF-first approach: Timetable data is available only as a downloadable PDF, typically a branded document with coloured tables showing class schedules. Some PDFs are scanned images of printed timetables, not even searchable text PDFs. Age ranges are mentioned in the PDF or in prose on the website ("Our Little Splashers class is for children aged 4 to 6"). Pricing is either absent from the website ("Contact us for pricing") or displayed as a simple text list without structure. These centres usually have no structured data markup.

The structured-HTML approach: Timetable data is presented in HTML on the website, either as properly structured tables or as filterable lists. Age ranges are clearly marked per class. Pricing is visible and associated with specific classes or membership tiers. Some go further and add JSON-LD structured data.

Give an agent a realistic query such as "Find Saturday morning swimming lessons for a 6-year-old in Bristol, under £50 per month" and the difference is stark. Against PDF-first sites, agents typically cannot return a usable result at all. Even where a PDF happens to contain searchable text, what an agent extracts tends to be partial and full of formatting errors. Against structured-HTML sites, agents reliably return matching classes, the only common failure being a site whose timetable HTML uses custom class names with no semantic structure, or buries the age range in a tooltip.

What the Best Setups Have in Common

The centres that agents handle well tend to share a couple of patterns.

A structured timetable table. The class schedule is an HTML table with columns for day, time, class name, age range, level, and price per term. Each class row is a tr element with proper td cells. The age range is formatted consistently, "Ages 4-6" in every row. The table has a thead with th elements and is filterable by day and age group using URL query parameters (/classes?day=saturday&age=6). Often there is also Schema.org Course markup on each class, including name, description, provider, time, day, and price.

A structured card layout with a data feed. Some centres use a card-based layout instead, but each card is an article element with structured content: class name in an h3, age range in a data attribute and as visible text, schedule as a time element, price in a span with clear labelling, and available spaces as a badge with text content (not just a colour). The strongest examples also publish a JSON feed at a path like /classes.json that returns all class data in a machine-readable format.

A useful pattern here: centres built or rebuilt with accessibility in mind tend to be agent-friendly too, even when they never set out to optimise for AI agents specifically.

Why It Matters for Referrals

When a centre's data is structured, agents send parents to it with specific, accurate information about class times, ages, and prices, so visitors arrive already knowing what they want and are more likely to enquire or start a booking. When the data is locked in a PDF, the best an agent can do is say "this centre might offer what you are looking for" without specifics, if it surfaces the centre at all. Some centres now see a meaningful share of new term enrolments coming from parents who mention they were recommended by an AI assistant, and that channel only exists for centres whose information agents can read.

What Centres with PDFs Are Missing

The PDF timetable is the default in children's activity businesses. It makes sense from an operations perspective: print the timetable, hand it out at reception, upload it to the website. One document, multiple uses.

But PDFs are a closed door for agents. Even searchable text PDFs require downloading and parsing, which most agents do not do reliably. Scanned image PDFs are completely opaque. And because PDF content is not linked to the rest of the website's data, agents cannot cross-reference class times with pricing or availability.

The fix is not complicated. A centre's timetable data already exists in some form, usually a spreadsheet or booking system. Publishing that data as an HTML page with proper table markup and basic structured data is a small piece of work. For centres using booking platforms like BookWhen or Bookeo, the platforms already generate HTML class listings; the centre just needs to link to them prominently and ensure the HTML is properly structured.

Practical Steps for Activity Centres

If you run a children's activity centre, here is what to do, in priority order.

First, get your timetable into HTML on your website. A basic table with day, time, class name, age range, and price is sufficient. Make sure it uses real table elements, not divs styled to look like a table. You can run an audit to check how agents see your current setup.

Second, make age ranges machine-readable. Use a consistent format ("Ages 4-6") and put the values in data attributes as well as visible text. Agents need to filter by age, and this is the single most common filter criterion parents specify.

Third, add pricing to the timetable page. "Contact us for pricing" makes your centre invisible to agents that are comparison shopping. Even an approximate range ("£40-£55 per term") is better than nothing. Parents who use agents to compare options need to see price alongside schedule and age.

Fourth, if you have the technical capacity, add Schema.org Course or Event markup to your classes. This gives agents a fast, structured data path that is more reliable than HTML parsing.

The centres that make their data accessible to agents now will have a growing advantage as more parents adopt AI assistants for family logistics. The ones relying on PDF timetables will find themselves recommended less and less often, losing enrolments to competitors whose information agents can actually read.