- Scope
- Programmatic SEO · Technical · Content
- Sources
- Google SERP · Search Console
High-value demand with nowhere to land.
The business had strong service pages and a solid brand, but its most valuable searches were phrased as journeys: an origin, a destination and a vehicle class. A single generic page about airport transfers cannot rank for hundreds of those, and it certainly cannot answer them well.
Meanwhile the results for those routes were being answered by aggregators and directories, which meant a customer with a high-value booking in mind was meeting a comparison site instead of an operator.
Google SERP verification on tracked route queries during the engagement.
Four workstreams, one engine.
Each stream existed to make the others measurable. Nothing here was run in isolation.
Mapping demand as journeys
We built the page set from how customers actually search, not from how the business is organised internally.
- Origin and destination pairs mined from real query data
- Routes prioritised by booking value, not search volume
- Vehicle class and occasion modifiers mapped per route
- Seasonal and event-driven demand identified
A template that answers the journey
Each route page had to be genuinely useful, not a find-and-replace of city names.
- Distance, duration and typical pricing context per route
- Vehicle options appropriate to the journey length
- Route-specific FAQs answering real pre-booking questions
- Service and FAQ structured data on every route page
Links that make new routes rank faster
The internal structure was designed so each new page inherits authority.
- Hub pages by region and airport, spoking into individual routes
- Related-route linking between complementary journeys
- Clean, readable URLs per route
- Sitemap segmentation so new routes are discovered quickly
Built to be quoted
Long-distance transfer questions are exactly the kind AI answers summarise.
- Content structured for extraction, with direct answers up front
- Entity consistency across routes and service pages
- Coverage of the comparison questions buyers ask before booking
- Position tracked in both classic results and answer panels
Route pages that rank, and answer.
The route engine now ranks in position one for targeted long-distance transfer queries, ahead of the aggregators and directories that previously intercepted that demand. Because each page answers a specific journey rather than a generic service, the traffic it earns is far closer to the point of booking.
The same structure that earns the classic ranking also makes the pages quotable. Route questions are exactly the sort of query that AI answers summarise, and pages that state distance, duration and vehicle guidance plainly are the ones that get cited.
Ranking positions verified in live Google results during the engagement. Position data varies by location and personalisation; the screenshot shows the query as returned at time of capture.
Match the page to the phrasing of the demand
Customers do not search for "airport transfers", they search for a journey. Route-level pages exist because that is how the money is actually looked up.
Programmatic wins where intent is combinatorial
Origin, destination and vehicle class create thousands of legitimate pages, provided each one is genuinely useful.
Aggregators are beatable on specificity
A directory can list a route. An operator can answer it. Depth is the advantage that structure alone cannot buy.
Answer-ready content is a by-product of clarity
Stating the distance, duration and price context up front helps buyers and makes the page easy for an AI answer to quote.