Type “luton airport taxi” into Google and Google returns a mix of aggregator sites, a couple of national airport transfer firms, and two or three local operators. The local operators in the top three are never the firms with an /airports/ page. They are firms with a dedicated /luton-airport-taxi/ page, sat alongside separate pages for every other airport they serve.
This is the single structural decision that determines whether you rank for airport phrases or not. Most firms get it wrong the first time. A few rebuild. Most carry on losing direct bookings to aggregators. Here is the case, in plain English, for one airport per page.
The One-Page Trap
The pattern on most UK taxi websites is a single page, sitting at something like /airports/ or /airport-transfers/. The page lists every airport the firm serves. Luton, Heathrow, Stansted, Gatwick, Birmingham, East Midlands. A paragraph for each. One hero image of a plane. One booking form at the bottom.
The owner feels like they are being efficient. One page covers the lot. The reality is Google sees a page that is about six different airports, which means it is really about none of them. It will not rank for “luton airport taxi” because there are pages out there 100 percent dedicated to Luton. It will not rank for “heathrow airport taxi” for the same reason. It will rank, weakly, for “airport taxi [town]” if you are lucky.
What Google Is Actually Looking For
Google’s ranking system is, in simplified terms, trying to match the query to the most specific page that answers it. “Luton airport taxi” is a specific query. It wants a specific page. If your page is split six ways, yours is not the specific page.
Google’s own search starter guide at developers.google.com is pretty blunt on this. “Organize your site so each page covers a single topic.” The topic, in this case, is “Luton Airport taxi transfers from [your town]”. That is a topic. “Airports” is not.
The Cannibalisation Trap
Here is where it gets worse. Some firms, having read that location pages work, add a /luton-airport-taxi/ page. But they keep the old /airports/ page as well, because they do not want to break internal links. Now Google has two pages from the same domain that both mention “luton airport taxi”. Which one is the canonical page? Google has to guess.
When it guesses, it usually splits the ranking signal between the two. Neither page ranks as well as one would. That is keyword cannibalisation. The fix is to either delete the old page and 301-redirect it to the new one, or strip all airport content off the hub page so it becomes a plain directory of links.
- If you have one /airports/ page and nothing else: build individual pages and redirect the hub
- If you have individual pages plus a hub: redirect the hub to the most important individual page, or make the hub link-only
- If you have individual pages and no hub at all: add a hub that simply lists them with short descriptions
The Right Structure, Laid Out
Here is the structure we put in place for a 20-vehicle firm in Bedfordshire serving the usual mix of southern airports. Their URLs now look like this.
- /airports/ (hub page, 400 words, lists and links to each airport page)
- /luton-airport-taxi/ (1,000 words, fare table, FAQ, schema)
- /heathrow-airport-taxi/ (1,000 words, fare table, FAQ, schema)
- /stansted-airport-taxi/ (1,000 words, fare table, FAQ, schema)
- /gatwick-airport-taxi/ (1,000 words, fare table, FAQ, schema)
- /birmingham-airport-taxi/ (1,000 words, fare table, FAQ, schema)
- /east-midlands-airport-taxi/ (1,000 words, fare table, FAQ, schema)
Six airport pages plus a hub. Every page has the same structure, different data. The hub is the index. The airport pages are the books.
Word Count: What To Aim For
A common question is how long the airport page should be. Longer is not automatically better. Too short and you do not give Google enough signal. Too long and you pad, which hurts both rankings and conversion.
Here is the rule we use for UK airport pages, by competitiveness of the phrase.
| Phrase Volume | Example | Page Target |
|---|---|---|
| Under 500/mo | “[small regional airport] taxi” | 800 words |
| 500 to 2,000/mo | “luton airport taxi”, “bristol airport taxi” | 1,000 to 1,200 words |
| 2,000 to 5,000/mo | “manchester airport taxi” | 1,200 to 1,500 words |
| 5,000+/mo | “heathrow airport taxi” | 1,500 to 2,000 words |
Those word counts include the fare table, the FAQ, and the review block. They are not padded prose. Every section should be doing a specific job: matching intent, answering a question, providing a fare, or showing proof.
Each Airport Page: The Required Blocks
Every airport page on the site should contain the same eight blocks, in roughly the same order. Consistency helps Google pattern-match. It also stops you reinventing the wheel for every airport.
- H1 with the airport name. “Luton Airport Taxi Transfers” or similar. One H1 per page.
- First paragraph with the airport, the firm, a journey time, and one fare. 60 to 80 words.
- Fixed fare table. 8 to 12 rows of pickup postcodes against vehicle types.
- Meet and greet explanation. Where the driver waits, what happens if the flight is delayed, whether the firm checks flight status. 120 to 150 words.
- Vehicle options. Saloon, estate, MPV, exec. 2 sentences each. Prices where they vary.
- Reviews block. Three recent reviews that mention the airport by name.
- FAQ section. Four questions with plain answers. FAQPage schema attached.
- Call to action. Phone number and booking form link. Schema block at the bottom.
Once you have written one airport page to this template, the rest are a day’s work each. Same structure, different numbers.
The Interlinking Pattern
Publishing six airport pages and walking away does not work. Google needs to see that the pages are part of a coherent site, connected to each other and to supporting content. Here is the interlinking we build by default.
- The hub /airports/ page links to every airport page with the anchor text “[airport] taxi”
- Each airport page has a sidebar or a footer box linking to the other airport pages (“We also run to Heathrow, Stansted, Gatwick…”)
- Every location page (/luton-taxi/, /dunstable-taxi/, /leighton-buzzard-taxi/) links to the relevant airport pages with anchor text like “Luton Airport taxi from Dunstable”
- The homepage links to the top two airports by revenue, with keyword-rich anchor text
- Blog posts about airport topics (what is meet-and-greet, early-morning flight advice) link back to the relevant airport pages in-content
The anchor text is the piece most firms get wrong. “Click here” and “read more” are wasted. Every link that points to /luton-airport-taxi/ should contain the words “Luton Airport taxi” somewhere in the anchor. That is how Google confirms the destination is about that topic.
The Location Page Assist
Here is a detail most firms miss. Your airport pages rank better when your town location pages exist and link in. If you have a /dunstable-taxi/ page and on it you mention “Luton Airport taxi from Dunstable, fixed fare £18”, that is a vote from a topically relevant page on your own site. Ten town pages voting for your Luton Airport page is more weight than ten random links from the homepage.
Town pages are cheap to produce and they feed the airport pages. Our 800-word rule for town pages makes them quick to roll out. Our local SEO post covers the town page template in more detail.
The 301 Redirect Step Most Firms Skip
When you move from one /airports/ page to six separate airport pages, you need to handle the old URL. Options, in order of how we usually do it:
- Redirect the old /airports/ URL to the new hub page, also at /airports/ but now short and link-heavy
- If the old URL was something different (/airport-transfers/, /uk-airports/), 301 redirect it to the new /airports/
- Update any internal links in menus, footer, and blog posts to point to the relevant new airport page
- Submit the updated sitemap in Google Search Console so Google picks up the new URLs
Without the redirect, you lose the authority the old URL had built up. With the redirect, that authority flows to the new hub and, via internal links, to the airport pages.
A Realistic Timeline
Here is what we see when a firm moves from a single airports page to six individual ones, with the schema, reviews, and interlinking in place.
- Week 1 to 4: pages are indexed, initial rankings show up low on page two or three
- Month 2 to 3: rankings climb to page one for the less competitive airport phrases
- Month 4 to 6: top five map pack positions emerge for lower-competition airports, top ten blue link positions for bigger airports
- Month 6 to 12: top three positions for the airports with the strongest internal link support and review velocity
The timeline depends on review velocity and how much content the site had before. A firm with weak domain authority will take longer. A firm with existing town pages and a steady review stream can see top three on the less competitive airports inside three months.
Where This Fits In The Build And The SEO Service
Our Essential build at £799 includes up to three location or airport pages. The Fleet build at £1,499 covers unlimited location and airport pages, which is usually the right fit for any firm with more than three airports on their ranking list. The monthly local SEO service starts at £49 a month for smaller firms and covers the roll-out of additional airport and town pages, the review strategy, and the monthly ranking report. Full pricing is on the pricing page, service detail under services, and our live airport work is in the portfolio. The wider structural argument is in our main guide on taxi website design.
Your Move This Week
Three quick checks, roughly 15 minutes each.
- List every airport your firm actively serves. Count them. That is the number of dedicated airport pages you should have. If you have one /airports/ page trying to cover six airports, you already know the fix.
- Search “[your town] to Luton airport taxi” in Google. Or whichever airport you care about most. If you are not on page one, note who is. Open their page and note the URL structure, the fare table, and the FAQ. That is the gap you are trying to close.
- Book a free booking funnel audit. We will map your current airport structure, flag the cannibalisation, and send a one-page plan for the right number of pages and redirects. No pitch attached. Request your audit here.
One airport per page is boring advice. It is also the single decision that separates the firms ranking for airport phrases from the ones that are not. Do the boring work.