Readable by search and AI
Readable, with your real prices.
A booking widget on its own is invisible to search engines and AI assistants. Every hub and campaign gets its own page they can read.
The problem
People ask search engines and AI assistants what is on this weekend, and a booking widget gives them nothing to read.
What we built
Pre-built public pages carrying your events, dates and the exact prices the shop charges.
What is actually in it.
Pages they can read
Every hub and campaign has its own public page.
- Pre-built with your events, dates and prices written into it
- Structured data for events, series, sessions, venue and address
- Map position, organiser, images, every price and availability
- Prices shown to search engines are exactly what the shop charges
- In stock is only claimed when there is comfortable stock
- The next 90 days of dates are covered
Found and shared properly
Canonical addresses, sitemaps and a plain-text catalogue.
- Every campaign page has its own canonical address
- Social sharing previews per page
- An automatic sitemap of every hub and campaign page
- An llms.txt file giving AI tools a plain-text catalogue
- Test and staging pages are hidden from search engines
- Each campaign gets a shareable link that opens on that tab
Fast, and hard to knock over
Pre-built and served from a global delivery network.
- Load fast and stay up under heavy traffic
- Each page carries its own data, so the shop appears without waiting
- Pages refresh every few minutes and straight after any change
- If one hub has a problem, the others keep working
- Ticket, wallet, waiver and voucher processing runs in parallel
- Which means tickets arrive faster
A page per campaign
Pre-built, with your dates and prices in it.
Your real prices
Exactly what the shop charges, nothing aspirational.
Ninety days of dates
Covered, so the next season is already visible.
A sitemap, automatically
Every hub and campaign page, kept current.
A catalogue for AI tools
A plain-text llms.txt of what is on sale.
Fast, and resilient
Served from a global network, refreshed often.
Readable by search and AI questions
Why is a booking widget not enough?
A widget holds your dates and prices inside JavaScript, which is invisible to search engines and AI assistants. Every hub and campaign also gets its own public page, pre-built with that information written into it.
Are the prices on those pages real?
Yes. The prices shown are exactly the prices the shop charges, and availability is only claimed as in stock when there is comfortable stock.
How far ahead do the dates go?
The next 90 days.
Do we have to maintain a sitemap?
No. Each operator gets an automatic sitemap of every hub and campaign page, and test and staging pages are hidden from search engines.
What happens if one page has a problem?
The others keep working. Pages are pre-built and served from a global delivery network, and each carries its own data.
See it running for your venue.
Every demo is built around your venue. We base it on your own website, events and prices, so you can see exactly what changes for your guests and your team.
Request a demo
An honest conversation with the people who built it.