“Manchester airport taxi” is one of the most contested phrases in UK taxi search. Around 3,600 searches a month. A dozen firms within striking distance of the top three. Most of them have been trying to rank for years and have no idea why one of their competitors keeps edging them out.
We did not build the firm’s site that currently sits in the top three. We are not going to name them. They are a 22-vehicle operator on the south-east side of the city. What we are going to do is pull their page apart at the technical level: the exact JSON-LD structured data they use, how they word their title tag, and the review velocity they have held for two years. You can copy this pattern for your own airport page.
What You Can See Vs What Google Sees
Passengers see a page with fares, a booking form, a phone number, and a photo of a saloon at terminal drop-off. Google sees three things on top of that.
- A block of JSON-LD structured data in the head
- A clean URL path and a title tag structured for the query
- A steady stream of fresh Google reviews mentioning the airport by name
Those three signals are doing most of the work. Let us go through each.
The Schema Markup, In Full
Here is roughly what the JSON-LD block on the ranking page looks like, with names and numbers changed. This is the pattern, not the firm’s literal markup.
{
"@context": "https://schema.org",
"@type": "TaxiService",
"name": "Manchester Airport Taxi Transfers",
"provider": {
"@type": "LocalBusiness",
"name": "Example Manchester Cabs",
"telephone": "+44 161 000 0000",
"address": {
"@type": "PostalAddress",
"streetAddress": "1 Example Street",
"addressLocality": "Stockport",
"postalCode": "SK1 1AA",
"addressCountry": "GB"
},
"priceRange": "££",
"openingHours": "Mo-Su 00:00-23:59",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.9",
"reviewCount": "1,847"
}
},
"areaServed": [
{ "@type": "Airport", "name": "Manchester Airport", "iataCode": "MAN" },
{ "@type": "City", "name": "Stockport" },
{ "@type": "City", "name": "Cheadle" }
],
"serviceArea": {
"@type": "GeoCircle",
"geoMidpoint": {
"@type": "GeoCoordinates",
"latitude": "53.3537",
"longitude": "-2.2750"
},
"geoRadius": "20000"
},
"offers": {
"@type": "Offer",
"priceCurrency": "GBP",
"price": "22",
"description": "Fixed fare from Stockport to Manchester Airport, saloon vehicle"
}
}Every line in there is doing work. Here is what each part signals to Google.
- “@type”: “TaxiService” tells Google this page is about a specific service. The TaxiService type on schema.org is an underused signal. Most firms use LocalBusiness on its own, which is a weaker match for an airport transfer query.
- “provider” with LocalBusiness nested inside ties the service to the firm. Address, phone, opening hours. This is what gets matched against Google Business Profile. Details must match GBP exactly. A different phone number or address format is a red flag.
- “aggregateRating” is the line that produces the star snippet in the results. The rating and review count should mirror the firm’s public Google reviews. Making them up is a policy breach that gets ranking pulled.
- “areaServed” with an Airport object is the airport-specific signal. Note the IATA code (MAN). That is the explicit handshake that says “this page is about Manchester Airport”.
- “serviceArea” as a GeoCircle tells Google how far out the firm travels. A 20km radius around Stockport covers the realistic pickup zone.
- “offers” with a price and a description gives Google a concrete fare to match against “cheap manchester airport taxi” or “manchester airport taxi stockport” type queries.
If you want the full spec on how Google reads this, developers.google.com has the local business guidance. The short version: structured data does not win you the ranking on its own, but it makes everything else you do count more.
The FAQPage Schema That Captures People Also Ask
On the same page, further down in the HTML, there is a second block of JSON-LD for FAQPage. Four questions. Short, plain answers. Something like:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How much is a taxi from Stockport to Manchester Airport?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A fixed fare saloon from Stockport town centre to Manchester Airport is £22. Estate and 6-seater MPV are £26 and £36."
}
},
{
"@type": "Question",
"name": "Where will my driver meet me at Manchester Airport?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Meet and greet is available in the short-stay car park at Terminal 1, 2, and 3. Your driver will text you the parking bay number 15 minutes before arrival."
}
}
]
}FAQ schema does two things. It lets Google put the questions directly into the People Also Ask box on the results page, which is free real estate above the fold. It also means your page answers the silent question a passenger has before they book, which lifts conversion.
The Title Tag Formula
Every airport page in the top three of Google in the UK follows the same shape. Keyword first, benefit second, trust signal third, brand last.
[Airport] Taxi | [Fixed Fare or 24/7] | [Star Rating or Years in Trade] | [Firm Name]
Three examples using the formula:
- “Manchester Airport Taxi | Fixed Fares From £22 | 4.9 Stars | Example Cabs”
- “Manchester Airport Taxi Transfers | 24/7 | Meet & Greet | Example Cabs”
- “Taxi to Manchester Airport | £22 Saloon From Stockport | Example Cabs”
Keep the whole string under 60 characters where you can. If you hit 70 characters, Google will truncate in the results with an ellipsis and your click-through drops. Measure in pixels rather than characters if you are being thorough, but 60 is a safe rule of thumb.
Reviews Velocity: The Unglamorous Ranking Factor
The firm we are looking at has held a top-three position for roughly two years. Their Google Business Profile receives, on average, two to three reviews a week. Never fewer than two. Occasionally five or six in a busy week.
That cadence is not random. Our working rule for airport pages in competitive cities is:
- Under 1 new review per week: you will slide down the map pack within six months
- 1 to 2 reviews per week: you can hold a top 5 map pack position
- 2+ reviews per week: you can hold a top 3 map pack position long-term
- 4+ reviews per week: you will move up if you are not already top 3
Velocity matters more than raw count. A firm with 400 reviews added at one a week is a stronger signal than a firm with 1,200 reviews that stopped receiving them two years ago. Google is reading the timestamps.
The mechanic the firm uses to get that cadence is old-school. After every airport drop-off, the driver sends a follow-up SMS. “Thanks for riding with us. If you have 30 seconds, a Google review helps a small firm beat the apps.” One link in the text. No mention of star rating. Conversion is around 6 to 8 percent, which is plenty for two to three reviews a week on an airport-heavy fleet.
Review Text: What To Hope For
Reviews matter more if they mention the airport by name. “Great taxi, very friendly” is worth less than “driver was early for my 5am Manchester Airport transfer from Didsbury, fare was the quoted £28”. The second one tells Google the firm operates to Manchester Airport from Didsbury at 5am for £28. That is a tiny cluster of keywords and specifics the firm did not have to write themselves.
The SMS the firm sends includes a gentle nudge: “A short mention of your journey helps other passengers.” It works. Most reviews on their profile mention Manchester Airport, a town name, and sometimes a fare or a time. That is gold.
Core Web Vitals, Because They Matter Too
We measured the page on a throttled 4G connection. Largest Contentful Paint at 2.1 seconds. Cumulative Layout Shift 0.05. Interaction to Next Paint 180 milliseconds. All three comfortably inside the web.dev Core Web Vitals thresholds. None of those numbers are world-class. They are just good enough to not be a drag.
If your airport page takes five seconds to load the hero image on a 4G phone, you will rank below pages that load in two seconds even if your content is better. Speed is a ranking signal and a conversion signal. Passengers bounce before the fare table ever loads.
What To Copy For Your Airport Page
You do not need a developer to implement most of this. Here is the order of operations we use when we are building an airport page for a firm.
- Publish the page at /airport-taxi/ or /[airport-name]-taxi/. One page per airport.
- Write a title tag that follows the keyword-benefit-trust-brand formula. Keep it under 60 characters.
- Write the first paragraph to include the airport name, the firm name, a journey time, a fare, and a tap-to-call number.
- Add a fixed fare table with 6 to 12 rows of common pickup postcodes.
- Add a 4-question FAQ section with FAQPage schema.
- Add TaxiService + LocalBusiness schema, including areaServed with an Airport object and IATA code.
- Set up an SMS follow-up to every airport fare asking for a review mentioning the airport name.
- Link to the page from every location page on your site, using “[airport] taxi” as the anchor text.
The firm we are teardown-ing did exactly those eight things in the right order. Two years later, they are still in the top three.
Where This Fits In A Proper Build
An airport page is a single chapter in a bigger book. Our Essential build at £799 includes one airport page with schema and a fare table. Our Fleet build at £1,499 includes a full airport hub plus unlimited location pages that link back to it. Full breakdown on the pricing page and service specifics under services, with the local SEO side covered at local SEO. Live airport pages we have built sit in the portfolio, and the wider structural argument is in our guide on taxi website design. If you want a deeper SEO read, the local SEO post covers citations and GBP.
Your Move This Week
Three things, maybe 30 minutes of work.
- Open your airport page in an incognito tab and view source. Search the source for “TaxiService” and “FAQPage”. If neither is there, your page is running on copy alone. That is fixable without a rebuild. A Care Pro plan at £129 a month includes this as part of monthly work.
- Count your Google reviews over the last 30 days. Fewer than eight and you are losing velocity. Draft the two-line SMS text your drivers will send after every airport fare, and try it on next weekend’s runs. Two to three reviews a week is the target.
- Book a free booking funnel audit. We will pull apart your airport page the same way we pulled apart the Manchester one. One-page PDF back, three biggest changes, no pitch. Request your audit here.
Ranking for your airport phrase is not a mystery. It is a structured data block, a clean URL, a fare table, and two reviews a week for two years. Start the reviews this week and the rest is mostly paperwork.