Travel and tourism
MICE
Business travel and organised gatherings.
MICE buying starts with a shortlist somebody else compiled. A sponsor weighing an event, an exhibitor weighing a stand, an HR head weighing a reward budget, an organiser weighing a hall: all of them ask an assistant first and get four or five names back with reasons attached. What decides those names is a handful of numbers, and the numbers are the one thing this sector keeps to itself.
Where the answer is being lost
Every decision here turns on a number, and yours are behind a form.
The facts that settle a MICE booking are almost all gated. A rate card sent on request, a technical sheet emailed after a call, a floor plan saved as an image, a post-show report circulated only to the companies who already booked. An engine cannot fill in a form or read a picture, so it substitutes. Attendance comes from a listing nobody has updated in years, cost per head from an agency working in dollars, the sector breakdown from a blog about a different show. The buyer ends up holding a number you never published and measuring you against it. That comparison is finished before anyone writes to you.
How we win this
The programme for mice
Publish the operating numbers
The questions in this sector are arithmetic. How many seats in theatre layout, what a stand costs per square metre, what a five-day trip runs per head, which sectors walked the floor last year. answer-pages carry those numbers in plain text with the conditions attached. Engines quote figures they can attribute. They skip pages that promise scale without stating it.
Build for the calendar
Demand here arrives in short windows and disappears again. Sponsors commit long before a programme is public. An exhibitor's budget closes before the show is announced. Pages written a fortnight before the event are read by nobody, because engines answer from what has been indexed and cited for a while. We work backwards from the booking date, not the event date.
Stay one entity across editions
An annual show is only as strong as the identity an engine can pin it to. Publish each edition on a fresh page under a slightly different name and you have handed the model a run of unrelated one-off events, none of them with any history. Venues have the mirror problem: a building and the five halls inside it are one entity with children, not five addresses. schema states those relationships and listings holds the same organiser, name and edition dates across the registries, so the record adds up to one thing that has been running for years.
Match, do not multiply
A hall holds what it holds and a show has a fixed number of stands. Volume is not the goal and we do not sell it. We write the qualifying facts into the answer, the size, the sector, the date, the budget band, so the organiser who calls has already checked that you fit. Fewer enquiries, further along.
The mix that carries it
Content
Answer and comparison pages
Cost, process, eligibility and comparison pages built for direct extraction, not for a reader who scrolls.
Foundation
Entity and schema engineering
Structured data and entity definition so engines know exactly what you are, where you operate, and what you are credible in.
Authority
Directories and profile consistency
Every listing, registry and profile saying the same thing, so the entity resolves to one business instead of three.
Content
GEO blogs and authority content
The definitive written answer to the questions your buyers put to an engine, structured so it can be lifted and attributed.
Content
Video and YouTube
Video run as a primary AI source, for the dense, entity-rich transcripts models read and quote.
Authority
Original data and benchmarks
Proprietary numbers, surveys and benchmarks — the most-cited asset class there is, because nobody else has them.
The constraint we work inside
There is no advertising regulator in this sector, but there is a hard ceiling: a venue has a fixed number of dates, a show has a fixed floor, and demand concentrates into a few weeks each year. Content can bring the enquiries in earlier in the cycle. It cannot make the calendar longer.
Specialisations
4 total
The pitch is different for each one, because the buyer, the trigger and the rules on what may be published are different for each one. Open the one that is yours.
Nobody looks up a conference by name unless they went to the last one. They ask for the subject, and the event that has put its subject in writing is the one that comes back.
The question deciding this today
“Which industry conferences in India cover supply chain technology”
- Who they sell to
- Organisations running professional gatherings with a programme
- Who signs
- Event director, association head, or marketing lead
- What starts it
- Annual event cycle, industry theme, sponsor commitments, venue booking
- Cost of staying invisible
- Delegates who never learned the event existed
"Which industry conferences in India cover supply chain technology" is a question about subject matter, and an engine has to judge it from what it can read. A registration form, a speaker grid and a PDF agenda give it nothing to work with. What it does hold is whatever was written about the last edition, usually by other people and usually in the week it happened. So the theme it associates with you is last year's theme, and the chair it names may have moved on since. The delegate spending three days of study leave and the sponsor deciding where the logo goes both work from that record, and neither of them writes in to check it.
What we would run
- 01Answer and comparison pages
An edition page per year that states the tracks, who each track is for, the delegate fee, the sponsor tiers and what a stand or a speaking slot includes. Written as text, not as a downloadable brochure.
This is exactly the comparison a delegate and a sponsor run against the other events that month, and a download is invisible to the thing making the comparison.
- 02Entity and schema engineering
Event structured data for every edition and every session: dates, venue, location, tracks, named speakers and their affiliations, tied to one persistent entity for the conference itself rather than a new page each year.
Engines answer date and location questions from structured fields. A conference that changes URL every year reads as a new, unproven event each time.
- 03GEO blogs and authority content
The programme turned into written argument: what the supply chain technology track actually covers, why the agenda changed this year, what last year's sessions concluded. One piece per theme, published under the chair's name.
A delegate searching a subject, not an event name, reaches the theme before the brand. The chair's byline is what makes the answer worth citing.
- 04Video and YouTube
Session recordings and keynote clips published with full transcripts and speaker names, one page per talk, indexed against the track it belonged to and the year it was recorded.
Last year's transcripts are the only evidence of what the event is actually about, and they are what an engine reads when someone weighs attending the next one.
- 05Directories and profile consistency
Consistent entries across event registries, industry calendars and association directories, with the same dates, venue, edition number and organiser name in each, refreshed the day the dates are fixed.
These calendars are where an engine looks first for what is on and when. A wrong date in one of them outranks the right date on your own site.
What we would not recommend
- Instagram. A programme is a grid of sessions, times and named speakers. There is no version of that worth posting, and nobody would keep it if there were. The channel earns its keep thanking sponsors afterwards, which is the one job we are not here for.
- X. Live-posting during the three days reaches the room, not the person deciding nine months out whether to register.
- Quora. The only question there we could answer is whether our own conference is worth attending. An organiser answering that is not a source anyone weighs, and the model discounts it for the same reason a reader would.
What a lead looks like
A programme manager at a logistics firm who found the supply chain track before he found the event. He has read the session write-ups and the delegate fee, and wants to know whether the Tuesday sessions are worth the trip and whether his vendor can sponsor a track.
What we measure
- Inclusion when the subject is asked
- Dates and speakers correct everywhere
- Delegate enquiries citing the agenda
- Sponsor enquiries before the budget closes
What changes
A corporate admin writes asking whether the 1,800-seat hall is free in the second week of February, having already read the seating matrix. A packaging firm's marketing head asks for stand rates in a specific zone because the visitor breakdown told him his buyers walk it. An HR head asks what a fifty-person programme costs at two destinations, not what incentive travel is. They arrive with the brief written and the budget known.
Start here
See who gets named in mice today
We put your buyers' real questions to the live models and come back with the businesses they name, the sources behind those answers, and the gap between that list and yours.