Skip to content
Get Ranked On TopIllustrative case studySignal plan

A fictional business. The figures are a modelled scenario, not a client result.

Glasmoor Rail Tours · Heritage rail holiday operator · Perth

How a heritage rail tour operator re-routed 2,140 broken URLs and won back “Highland rail holidays”

+19% organic bookings after every URL broke

11 months · UK & Ireland · Signal plan · Redirect mapping · Log-file analysis · Canonicals & parameters · Structured data

Arrivals board · month 11

Organic tour bookings a month (vs. pre-migration)
+19%
Legacy URLs re-routed, one hop each
2,140
Ranking for “Highland rail holidays”
#41 → #2
Old tour URLs returning 404
1,780 → 0

01The challenge

The night the line went dead.

A booking-engine migration changed every tour URL without a single redirect. Overnight, Glasmoor fell from #3 to #41 for “Highland rail holidays”.

Glasmoor runs 40 escorted rail holidays out of Perth: the West Highland Line, the Kyle Line, the Far North Line and steam specials over the Glenfinnan Viaduct. For twelve years its tour pages had gathered rankings, press links and forum recommendations. Then a new booking engine went live on a Tuesday night. Every tour moved to a new address, nobody wrote a single redirect, and by Friday every page Google knew returned a 404.

Organic sessions, week by week
W1W2W3W4W5W6W7W8SWITCH-OVER

-67%

of organic sessions gone in one week

#3 → #41

Position for “highland rail holidays”

02The inspection

What the signal box register showed.

  1. Entry 1 of 4

    Dead URLs

    1,780

    Of 2,140 legacy URLs that were indexed or linked, 1,780 now returned 404: all 40 tour pages, 1,120 departure-date pages and 620 itinerary-day pages. The other 360 bounced to the home page, which Google treats as soft 404s.

  2. Entry 2 of 4

    Lost links

    640

    Backlinks from 212 domains, among them newspaper travel sections, rail-enthusiast forums and tourism boards, now landed on dead pages. Twelve years of earned authority was pointing at nothing.

  3. Entry 3 of 4

    Old chains

    312

    Redirects left over from a 2019 redesign were still live. Mapped naively, each one would have become a three-hop chain: the 2019 URL to the old URL to the new one.

  4. Entry 4 of 4

    Parameter sprawl

    9,600

    Crawlable booking-engine URLs built from ?dep=, ?pax= and session parameters took 58% of Googlebot's requests, while 31 of the 40 new tour pages had not been crawled at all.

Where Googlebot spent its requests

Week after the switch-over
Month 11
  • Booking parameters
  • Dead and redirected URLs
  • Tour pages

03The working timetable

Four levers, pulled in order.

Built on our Signal plan: the technical engagement for sites where crawling, redirects and architecture decide the outcome.

  1. Lever 1

    Redirect mapping

    Every legacy URL, gathered from server logs, old XML sitemaps, web archives and backlink indexes, matched to its nearest new page: tour to tour, departure date to the tour's dates tab, itinerary day to its anchor. 2,140 one-hop 301s, and not one blanket redirect to the home page.

  2. Lever 2

    Log-file analysis

    Daily log ingestion showed how fast Googlebot found each batch of 301s, which old URLs it kept requesting and which new tour pages it had never seen, so a stalled recrawl showed up in hours, not weeks.

  3. Lever 3

    Canonicals & parameters

    Departure, passenger and session parameters canonicalised to the clean tour URL, stripped from internal links and kept out of the crawl where they only produced calendar states.

  4. Lever 4

    Structured data

    TouristTrip and Offer markup on every tour page, with departure dates, durations and prices taken from the booking engine, so the new URLs could earn back their rich results.

04Set the route

Pull the levers in the right order. Get it wrong and the train comes off.

In a signal box, the interlocking stops a signalman clearing a signal before the points are set. A migration needs the same discipline. These five levers re-route one old tour URL to its new page: pull them in order, or try one out of turn to see what breaks.

404/301·301·30112345
Old URLNew page

Each lever is released by the one before it, as in a real interlocking.

0 of 5 levers pulled

0 of 5 levers pulled

Route not set: the old URL returns 404. Pull lever 1 to begin.

Request trace

  1. 404/tours/highland-explorer.html

Dead end: page and links lost

0 redirect hops

05Month by month

11 months, station by station.

  1. 1

    Month 1

    Emergency triage

    The 40 tour pages and the 120 most-linked departure pages redirected within 72 hours, from a map built on the old sitemap and the booking export.

  2. 2

    Months 2–3

    The full map

    All 2,140 legacy URLs inventoried and matched, 312 old chains flattened, and every rule tested on staging against a crawl of the old site before two releases.

  3. 3

    Months 4–5

    Clean crawl

    Booking parameters canonicalised and taken out of internal links; templates fixed so that every link points at the final URL, not at a redirect.

  4. 4

    Months 6–8

    Recrawl and markup

    TouristTrip and Offer markup live, fresh XML sitemaps, and daily log checks until Googlebot was spending most of its visits on tour pages.

  5. 5

    Months 9–11

    Running ahead

    With authority consolidated on the new URLs, route pages for each line and a rebuilt departures calendar took the site past its old traffic.

06Arrivals

Back on the main line, and running ahead of the old timetable.

Organic tour bookings a month (vs. pre-migration)

+19%

62 → 74 organic bookings a month

Legacy URLs re-routed, one hop each

2,140

Every one a single hop; none to the home page

Ranking for “Highland rail holidays”

#41 → #2

#3 before the migration

Old tour URLs returning 404

1,780 → 0

plus 360 soft 404s cleared

Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.

Organic sessions by monthPre-migration level
08,00016,00024,000Pre-migration levelSWITCH-OVER · 6,10021,300BeforeM1M3M5M7M9M11

Rankings before the switch-over, the week after, and now

QueryBeforeWeek afterMonth 11
highland rail holidays#3#41#2
west highland line tour#2#27#1
scottish rail tours#5#38#3
kyle line rail tour#4#33#2
rail holidays from perth#1#19#1
escorted rail holidays uk#9#64#6
jacobite steam train tour#12#58#7

Queries as searched on google.co.uk. Organic bookings a month: 62 before the migration, 18 at the low point, 74 by month 11.

Planning a migration? Set the route first.

Moving to a new booking engine, CMS or domain? Start with the Signal plan, or tell us what you are moving and when.

All case studies