Travel and tourism

Transport

Getting travellers there and around.

Air, sea, rail and road sell the same object: a seat with a set of rules attached. Buyers no longer research those rules. They ask once and take what comes back. Baggage, inclusions, licences, cabin grades, deposits. Every one of those has a correct answer, and in most cases the operator who owns it has never written it down anywhere a machine can read.

Where the answer is being lost

Your fare rules are explained by people who never sold a seat.

Your reservations desk already knows the shape of this. Callers arrive having been told something wrong: that the fare covers a checked bag when the basic fare does not, that the deposit is taken in cash, that the season runs a month longer than it does. Those cost a few minutes each to correct. The expensive ones are the calls that never come, from people who read a confident wrong answer, concluded the trip did not work, and quietly went and did something else. Neither group ever reaches the page where you set the position out properly, because that page was written for someone who had already found you.

How we win this

The programme for transport

01

Start from what the engine already gets wrong

Most sectors worry about being left out of an answer. Transport has the opposite problem. Ask a model what a fare covers or who is allowed to drive and it will answer, confidently, from whatever it holds. diagnostic puts your own rule questions to live models and comes back with the statements they currently make about your baggage allowance, your deposit, your inclusions and your permits, including the ones that were true two seasons ago or belong to a competitor. answer-pages and blogs then set the correct position down, one rule at a time. Engines quote a specific policy. They paraphrase a general one.

02

Get the operating detail out of the widget

Nearly everything a buyer needs here is locked inside something a model cannot open. The timetable lives in a booking engine. The fare rules are in a PDF. Cabin grades sit behind a date picker, branches behind a store finder that needs a click. schema and technical turn routes, sailing dates, grades, vehicle classes and counter records into structured text on your own domain, which is the only form of them anything can lift into an answer.

03

Show the inside of the thing

The rest of travel can be photographed from outside. What transport sells is an interior nobody may enter until they have paid: a cabin, a berth, a boot, a bathroom at the end of a corridor. video is the honest way to settle that, and the transcript is worth as much as the footage, because it names the fittings the follow-up questions are about. Whether there is a socket by the bed. Whether two large cases fit. Whether the shower is over the toilet.

04

Decide whose copy of your facts wins

An aggregator holds a version of your schedule, your branch list, your cabin grades, and publishes it somewhere readable. Engines use it because they can. We do not try to take the fare comparison back; that belongs to the platforms and will stay there. The work is making your own record the better one and keeping it current through listings and monitoring, so that when a counter changes terminal or a route is suspended, the answer moves with it instead of repeating last year.

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.

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.

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.

Foundation

Technical fixes

Crawlability, render, speed and the machine-readability faults that keep an engine from reading you at all.

Content

Video and YouTube

Video run as a primary AI source, for the dense, entity-rich transcripts models read and quote.

Authority

Directories and profile consistency

Every listing, registry and profile saying the same thing, so the entity resolves to one business instead of three.

Authority

Reviews and testimonials

Structured, retrievable proof from customers, which is what engines lean on when a category has no objective data.

The constraint we work inside

We do not publish live fares, seat availability or price comparisons. Prices move daily, an advertised fare has to show the full amount payable, and a number that goes stale costs more trust than silence. What we publish is what a fare covers, who is eligible, and what a change costs.

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.

A traveller with a Pune departure and four days in Singapore asks which carriers go non-stop, and the answer comes back from a platform that will also take the booking.

The question deciding this today

Which airlines fly direct from Pune to Singapore

Who they sell to
Passengers buying scheduled air services
Who signs
The traveller, or a corporate travel manager
What starts it
Trip booking, fare movement, route launch, schedule disruption
Cost of staying invisible
Fares compared on a platform that owns the customer

Ask "Which airlines fly direct from Pune to Singapore" and you will probably be named, because a schedule is a public fact and everybody holds a copy of yours. Being named is not the win. The answer arrives with a booking route attached and it is rarely yours, and then comes the second question, about the bag, the date change, the infant travelling on a lap. That one is assembled from an aggregator's help centre, because your own fare rules sit inside a booking widget and a PDF. Your in-house team runs the app, the campaigns and the loyalty programme. Nobody owns the plain-text rule layer, so the platform answers on your behalf and keeps the passenger.

What we would run

  1. 01Technical fixes

    Route and schedule content made fetchable without a browser: static city-pair pages behind the booking widget, baggage and fare-rule tables in HTML rather than PDF, sitemap coverage for every pair you actually operate.

    An engine answering a route question can only use text it can fetch. If the timetable exists only inside the booking engine, the aggregator's copy of it becomes the source.

  2. 02Entity and schema engineering

    The carrier and each route defined as entities: origin, destination, non-stop status, operating days, terminal, aircraft. Baggage allowance, change fees and no-show rules marked up as structured data.

    Travellers and corporate travel managers ask policy questions in absolutes. Structured facts survive being lifted whole into an answer. A PDF and a fare grid do not.

  3. 03Answer and comparison pages

    One page per rule, not per campaign: cabin and check-in baggage by fare family, what a change costs before and after departure, unaccompanied minors, pets in hold, excess charges, and a plain non-stop or one-stop statement per city pair.

    These are the questions asked after the fare is chosen, at the moment the traveller decides whether to book on your site or on the platform.

  4. 04AI Presence tracking

    City-pair tracking of which routes an engine names you on, which it skips, and which aggregator holds the citation in your place, refreshed as schedules and route launches change.

    A route launch is the one moment when the answer is still unwritten. Tracking shows the weeks in which a new pair is genuinely winnable.

What we would not recommend

  • Instagram. Your in-house team already runs that account, and to a standard we would not improve on. Its work is holding the brand together through delays and launches, which was never meant to reach a passenger asking who flies a route non-stop.
  • Reddit. The airline conversation there is about one flight on one day, so answering means adjudicating a disruption in public. That belongs to customer relations and carries its own legal exposure. It is not a booking answer.
  • Reviews and testimonials. Airline review surfaces belong to the aggregators and skew towards disruption. Gathering more of them does not change what an engine quotes about a route.

What a lead looks like

A corporate travel manager at a Pune manufacturer who has already read your baggage and change-fee rules and knows the route runs non-stop, writing to ask what a corporate account looks like and whether a fare family can be held for the year. Not a fare enquiry. A contract conversation.

What we measure

  • Which city pairs the answer names you on, and which it hands to a platform
  • Fare rules readable without opening the booking widget
  • Baggage and change answers attributed to the carrier
  • Corporate desks opening with account terms, not fares

What changes

Enquiries arrive with the homework done. A first-time cruise buyer asks whether the balcony grade is worth it on a five-night sailing, rather than what a cruise fare is. A traveller checks whether the cheapest fare family allows a date change, before she books the hotel around it. An office administrator in Bengaluru who has read the deposit and damage policy asks what a month of chauffeured hire costs on account. Fewer of these conversations die on a policy question, and more of them begin at the point of choosing.

Start here

See who gets named in transport 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.