Chauffeur SEO in the age of ChatGPT: how AI assistants pick which operator to recommend

A fleet owner in Manchester asked me last month why ChatGPT recommended two competitors and not him when he typed "reliable chauffeur company near Manchester Airport" into it himself. His site outranks both of them for half a dozen Google searches I checked. That gap is the actual subject of this article. Google ranking and being the operator an AI assistant names out loud are related but not the same job, and most operator sites are set up to do neither well.

I manage SEO across 185+ Search Console properties, and over the last year I have started pulling AI Overview appearances and running the same prompts through ChatGPT and Perplexity for a sample of those accounts every week. The pattern is consistent enough now to write down plainly, caveats included.

How these systems actually assemble an answer

None of ChatGPT, Perplexity or Google's AI Overviews are calling around chauffeur companies to ask about availability. They are retrieving a small number of web pages that already rank or already match the query closely, reading them, and stitching a summary out of sentences that were easy to lift whole. Perplexity shows its sources openly as numbered citations. AI Overviews link out below the summary. ChatGPT with browsing does the same when it searches live; without browsing, it is drawing on whatever it absorbed during training, which for a small local operator is often close to nothing.

The practical consequence is that a page gets used as a source for the same reason it gets clicked in ordinary Google results: it answers the specific thing being asked, in a form that is cheap to extract. "Cheap to extract" is doing a lot of work in that sentence, and it is the difference between the two competitors who got named and the Manchester operator who didn't. All three ranked. Only two were quotable.

What makes a page quotable

A quotable sentence states one fact plainly, with no hedge and no adjective doing the work a number should do. "A transfer from Manchester Airport Terminal 2 to the city centre takes 25 to 40 minutes depending on traffic on the M56, and costs £55 in a saloon or £75 in an executive MPV" is a sentence an assistant can lift and attribute. "We offer competitive rates and a fast, professional airport transfer service" contains nothing to lift, because there is no fact in it. It's a paragraph the assistant has to skip past on the way to a competitor's page that actually said a number.

• Published prices by vehicle class, or a clear formula (per mile, per hour, minimum fare) if fixed prices genuinely don't work for your business
• Journey times stated as a range with the reason for the range named — traffic, terminal, time of day
• Waiting-time policy on delayed flights, in minutes, with what happens after the free period ends
• Licensing and insurance facts: PHV licence, operator number, passenger insurance limit
• Cancellation window stated in hours, not "reasonable notice"
• Vehicle capacity stated with luggage loaded, not the brochure figure

FAQ blocks, JSON-LD schema and llms.txt

FAQ blocks help for a plain reason: a question-and-answer pair is already in the shape an assistant wants to output, so it needs almost no rewriting to reuse. "Do you charge for waiting at the airport?" followed by a two-sentence answer with a number in it is close to a direct lift. I put one on every route and policy page now, five to seven questions, written from what the office actually gets asked on the phone rather than invented for the sake of having a section.

FAQPage JSON-LD schema, LocalBusiness schema with your address, phone, price range and service area, and Product or Offer markup on price pages don't guarantee a citation, but they remove ambiguity for anything parsing the page, human or otherwise. I would not spend more than an afternoon on schema for a small operator site — get LocalBusiness and FAQPage correctly implemented and move on to writing the pages that need it.

llms.txt is the newer, more speculative one: a plain-text file at your site root listing your key pages and a short description of each, aimed at AI crawlers the way robots.txt is aimed at search crawlers. Adoption among the assistants is inconsistent as of this year, and I would not delay anything else to build it. It costs perhaps twenty minutes once your pages exist, so I add it, but I have not seen it move a citation on its own in any account I manage.

Third-party mentions are the biggest lever you're not pulling

Here is the part operators find least intuitive. When I trace citations back for chauffeur-related AI answers, a large share are not the operator's own website at all. They are a Reddit thread in r/london or r/AskNYC where someone asked for a recommendation and got three names in the replies, a Tripadvisor or Quora answer, a local newspaper's "best of" listing, or a chamber of commerce directory. Assistants weight these highly because they read as independent opinion rather than a company describing itself, which is exactly the bias you'd want if you were trying to avoid recommending whoever wrote the most persuasive marketing copy.

This means the fastest way to get named by ChatGPT is often not a new page on your own site. It's your name appearing, accurately and with context, in the places assistants already trust: a considered answer on a Reddit thread about airport transfers in your city, a listing in the right local business directory, a mention in a wedding blog or a corporate relocation guide for your area, a review response on Trustpilot or Google that names your service specifically. BabyLoveGrowth's Reddit and Quora agents exist for exactly this gap — placing genuine, disclosed brand mentions in threads that AI assistants already treat as citable, rather than only writing pages that hope to be found.

How to test whether you're being recommended

Don't guess. Open ChatGPT, Perplexity and Google on a phone with location services on, and run the same handful of prompts across every city you operate in: "best chauffeur service in [city]", "reliable airport transfer from [airport] to [city]", "chauffeur company with fixed prices in [city]". Note whether you're named, whether a competitor is named instead, and where the assistant says it got the information, when it says at all.

Do this weekly rather than once. Answers from these systems move around noticeably between weeks, sometimes for no reason I can find beyond a model update. I track it properly rather than manually now, using a tool that checks a set list of prompts daily across ChatGPT, Claude and Gemini and logs whether a brand is mentioned — BabyLoveGrowth's Grow plan tracks 10 prompts a day this way, and Scale tracks 50, which matters once you're running this across more than two or three cities.

What I'd do this month

1. Run the prompt test above across every city and airport you serve, and write down what's being said today as a baseline.
2. Rewrite your top three pages — usually a price page and your two busiest routes — to replace vague marketing sentences with plain, quotable facts and numbers.
3. Add a five-to-seven-question FAQ block to those same pages, sourced from what your office is actually asked.
4. Implement LocalBusiness and FAQPage JSON-LD if you haven't already; it's an afternoon of work, not a project.
5. Spend an hour finding one live Reddit or Quora thread where someone is asking for a recommendation in your city and answer it properly, with disclosure that you run the business.
6. Claim or check your listing on one relevant local directory and your Google Business Profile, covered in full in the Google Business Profile guide for operators.

Where this fits with everything else

None of this replaces ordinary SEO; it sits on top of it. The six page types I'd build for Google ranking are the same six page types that get quoted by an assistant, covered in full in the hub article on why chauffeur sites go unseen, and the route pages specifically are where I've seen the clearest AI citations, detailed in how to rank for every route you actually drive. If you're weighing whether to do this work in-house, through an agency, or with a tool that automates the research and publishing, I've compared the real costs in agency retainer versus AI content tool.

The short version is the same one I gave the Manchester operator on the phone. His site was fine. It just never said anything an assistant could repeat with confidence. Fix that, and the same specificity that gets a route page ranked in Google starts turning up, word for word sometimes, in an answer he never saw being written.