Skip to content

Limo and chauffeur SEO

Airport Transfer SEO: How I Build Airport Pages for Limo and Chauffeur Companies

By Rehan Javed · Updated · 11 min read

For most limo and chauffeur companies, airport runs are the steady work that pays for everything else. Weddings and proms are seasonal. Corporate accounts come and go. People fly every day of the year, and a lot of them would rather book a car than queue for a taxi after a long flight.

That makes airport searches some of the most valuable a limo website can rank for, and also some of the easiest to get wrong. I've done SEO and marketing for limo and chauffeur services in both the USA and the UK, and the airport pages are often where I find the biggest gap between what the company does and what its website says.

I won't name clients or publish their numbers here. This is the method I use: how I decide which airport pages to build, what goes on them, and how I connect them to the rest of the site and to Google Business Profile.

Why airport searches are different

An airport transfer search is narrow. The person usually knows the airport, the date and roughly where they're going. They are not browsing. They want to know three things quickly: do you cover my airport, what will it cost, and can I trust you to be there when I land?

The wording changes with the market, which is the first thing I check:

  • USA: “car service to LAX”, “limo to JFK”, “black car airport service”, “airport limo near me”.
  • UK: “Heathrow airport transfer”, “chauffeur to Gatwick”, “airport chauffeur service”, “executive car to Manchester Airport”.

A page titled “Airport Limousine Service” on a UK site will struggle, because few UK customers search that way. A US page built around “transfers” has the same problem in reverse. I write each page in the words its own customers use, which sounds obvious, but I regularly see UK operators using American templates and the other way round.

The other difference is trust. A missed airport pickup ruins someone's day, and people know it. So an airport page has to do more than rank. It has to show, in specific detail, that the company does this every week.

Which airport pages to build, and which to skip

I don't start with a keyword tool. I start with the company's booking records: which airports they actually serve, how often, and which runs earn the most. Then I sort every possible page into one of four types.

Page type and when it earns a pageExample
Airport transfers hub
Always. One page that lists every airport you cover
/airport-transfers
Single airport page
Airports you serve regularly and can describe in detail
/airport-transfers/heathrow, /lax-car-service
Route page
Only routes with their own fare, timing or regular demand
/heathrow-to-oxford-chauffeur
Every town to every airport
Skip. Cover these on the airport page instead
“[suburb] to [airport] limo” times a hundred

The example paths are just patterns. The exact URL matters much less than having one clear page per airport, with nothing else on the site competing for the same search.

The line between a useful page and a doorway page

Google's spam policies describe doorway abuse as pages created to rank for specific, similar searches, and give the example of “pages targeted at specific regions or cities that funnel users to one page”. Fifty “limo from [town] to Heathrow” pages with the same text and a different town name fit that description closely.

The test I use is simple: if I deleted the town or airport name, would the page still say anything different from its neighbours? A Heathrow page that explains where the driver waits at each terminal passes. A page that says “We offer luxury transfers from [town] to Heathrow” and nothing else doesn't.

Thin location pages rarely fail on their own. In my experience they make it harder for the good pages on the same site to rank, which is why I'd rather merge twenty weak pages into one strong airport page than keep them. I explain more about why this kind of content struggles after updates in my core update recovery guide.

What goes on an airport page

The best airport pages read like the answers a good dispatcher gives on the phone. Before I write anything, I sit down with the owner or operations manager and go through these questions. Their answers are the page.

  1. Where exactly does the driver meet the passenger? Inside arrivals with a name board, at a set pickup area, or at the kerb? Airports have rules on this, and they differ by airport and sometimes by terminal. I link to the airport's own ground transport page rather than describing rules that might change.
  2. What happens if the flight is late? Whether you track flights, how much free waiting is included, and what happens after that. This is the question customers ask most on the phone, and the one airport pages most often leave out.
  3. Which vehicles, and how much luggage fits? A group of four with golf bags needs a different car from one business traveller. Real luggage limits for your real vehicles, not a manufacturer brochure.
  4. How is the fare worked out? A starting price by vehicle if you have one. If not, explain what changes the price: distance, vehicle, time of day, waiting, parking and tolls. “Contact us for a quote” on its own sends people back to the search results.
  5. How long does the journey take? Typical times from the places you pick up most, with an honest note about peak traffic. One made-up average helps nobody.
  6. How do I book, and how fast will you confirm? A quote form that works on a phone, a tap-to-call number, and a clear promise about response time that the team can keep.

None of this is SEO trickery. It's the information a nervous traveller wants, and it's also what makes each airport page genuinely different from the next one. That difference is what Google's guidance on helpful, people-first content is asking for.

Two things I leave off: stock photos of cars the company doesn't own, and claims nobody can check, like “the best chauffeur service in London”. Real photos of the fleet at the airport, if the company has them, do far more.

Titles, headings and the words on the page

The title should say what the page is and where, in the customer's words. For a UK operator, “Heathrow Airport Transfers by Chauffeur | Brand” works. For a US operator, “LAX Car Service and Airport Limo | Brand” does the same job. What I avoid is the stacked version: “LAX Limo | LAX Car Service | Limo LAX”, which reads as stuffing and is likely to be rewritten by Google anyway.

I use the SERP preview tool to check that titles and descriptions fit before they go live. The description is where I put the reason to click, such as fixed fares or flight tracking, but only if it's true for that company.

Inside the page, the headings follow the questions above: meeting point, waiting time, vehicles, fares, journey times, booking. Someone scanning on a phone at the baggage carousel can jump to the part they need, and Google gets a clear outline of what the page covers.

Linking the airport pages together

An airport page that is only linked from the menu is easy for Google to underrate. I build the links in a simple pattern:

  • Hub to airports: the airport transfers hub links to every airport page with the airport's name as the anchor text.
  • Airports back to the hub: each airport page links back, and to the one or two other airports a customer might compare it with.
  • Airports to fleet and occasion pages: the Heathrow page links to the executive saloon and people carrier pages, and to corporate travel if that's where most airport work comes from.
  • Home page to the hub: a plain sentence on the home page, not just a menu item.
  • Route pages to their airport: where a route page exists, it links up to its airport page, and the airport page links down to it.

The free SEO audit tool shows how many internal links a page has and whether its title and headings match the service. I run it on each airport page before and after a rewrite.

Schema without making things up

Most limo companies don't have a public office. They dispatch from a yard or a garage that customers never visit. That matters for structured data, because the easy mistake is to put an address in the markup that doesn't match Google Business Profile.

On an airport page, I add a Service block: the name of the service (“Heathrow airport transfers”), a short description, the areas served, and the provider pointing to the company's main business block by @id. The business itself is described once, on the home or contact page, following Google's local business guidelines. If the company is a service-area business with a hidden address, the markup leaves the address out too.

I only add FAQPage markup when the questions are actually visible on the page. Google stopped showing FAQ rich results for most sites in 2023, so I add it because it describes the page accurately, not because it will change the listing. The JSON-LD schema generator builds LocalBusiness and FAQ markup with areas served instead of a street address.

How the pages connect to Google Business Profile

For many airport searches, the map results appear above the normal listings, so the website and the profile have to agree with each other.

  • Categories: the primary category should match where most of the revenue comes from. Google's category guidance says to use as few as possible, so I add secondary categories only for work the company really does.
  • Service area: set to the places the company genuinely dispatches to, following Google's service area rules. Listing every county in the state doesn't help and looks implausible.
  • Services list: airport transfers listed as a service, in the same words used on the website.
  • One profile per real location: never a profile per airport. Google's guidelines don't allow profiles for places where the business has no staffed presence, and suspended profiles are hard to recover.

The website's airport pages and the profile support each other. The profile wins the map results for searches near the business. The pages win searches for airports and routes further away, where the map results don't reach.

Using Google Ads to decide what to build next

When a limo company also runs Google Ads, the search terms report is the best keyword research I can get. It shows what people actually typed before they called or asked for a quote. If “car service from Gatwick to Brighton” keeps appearing and converting, that route may be worth its own page.

It also shows what to keep out. Airport searches attract people looking for car rental, shuttle buses, parking and chauffeur jobs. The negative keyword list generator has a limo and chauffeur starter list for exactly this. If you're planning a budget for busy months, the Google Ads budget calculator has a travel preset. There's no limo category in the benchmark data, so treat it as a starting point.

How I measure airport pages

Rankings for one airport phrase don't tell you much. I report on three things:

  1. Indexing and impressions. In Search Console, I filter the Performance report by each airport page and look at which searches it appears for. A new page that gets no impressions after several weeks often has an indexing or internal linking problem, not a content problem. The indexing checker is a quick first test.
  2. Calls and quote requests by page. Tap-to-call clicks and quote forms tracked in GA4 through Google Tag Manager, so I can see which airport pages produce enquiries.
  3. Bookings. The company knows which enquiries became paid rides. Even a simple monthly count of airport bookings from the website tells us more than any ranking report.

Local rankings move at different speeds in different markets, so I don't promise positions. I do expect the pages to be indexed, to show up for the airport searches they were written for, and to start producing enquiries.

Mistakes I find on limo airport pages

  • One “Airport Transfers” page that lists five airports in a sentence and says nothing specific about any of them.
  • Dozens of town-to-airport pages with the same text, which I usually merge into the airport page.
  • No word on what happens when a flight is late.
  • “Call for a quote” with no pricing guidance at all.
  • US wording on a UK site, or the reverse.
  • A quote form that sits on another domain with no tracking, so nobody knows which page produced the booking.
  • Schema with an address the customer can't visit, or FAQ markup for questions that aren't on the page.

Fixing these is rarely glamorous. It's an afternoon with the operations manager, a careful rewrite of a handful of pages, and some deleted ones. That work is the core of what I do for limo and chauffeur companies in the USA and UK, and the technical side is covered in my technical SEO services.

Keep reading

FAQ

Does a limo company need a separate page for each airport?

Only for airports you serve often enough to say something specific about: where the driver meets the passenger, how long you wait if a flight is late, typical journey times and how the fare is worked out. An airport you visit twice a year can be covered on a general airport transfers page.

Should I build a page for every town-to-airport route?

No. Build route pages only where the route has its own facts, such as a regular corporate run or a long-distance transfer with a fixed fare. Pages that only swap the town name are what Google describes as doorway pages, and they tend to drag the rest of the site down.

Should airport pages show prices?

If your pricing allows it, yes. A starting fare by vehicle, or a clear explanation of what changes the price (vehicle, time of day, waiting, tolls or parking), answers the question people ask first. If every quote is custom, say so and explain how quickly you reply.

What schema should an airport transfer page use?

A Service block that names the transfer, the airport and the areas you serve, and points to your business as the provider by @id. Add FAQPage markup only if the questions are visible on the page. Never add an address your customers can't visit.

How long does it take for an airport page to rank?

It depends on the market, the competition and how strong the rest of the site is, so I don't promise positions or dates. What I can measure early is whether the page is indexed, which searches it appears for in Search Console, and whether it produces calls and quote requests.

Want me to look at your airport pages?