Itinerary pages are some of the hardest pages we see in travel design. They have to hold days, cities, maps, hotels, excursions and prices, and then squeeze all of it onto a phone screen that someone is scrolling on a train. Most of them try to show everything at once and end up showing nothing clearly.
So we picked a worked example and thought it through properly. Here's how we'd approach an itinerary page for a river trip along the Rhine, with a few nights on land before or after the cruise, designed mobile first.
Start with the device. Ofcom's research into UK online habits found that most of the time adults spend online is now on a smartphone. Whatever the itinerary looks like on a big monitor, the phone version is the one that has to work.
Then think about the geography. A Rhine itinerary isn't one destination. The river's catchment spans nine countries and is home to around 60 million people, according to the International Commission that works to protect it. A single week might start in Switzerland, pass through France and Germany and finish in the Netherlands.
That's the core design problem. Multiple cities, multiple days, two very different types of stay and a price that changes depending on what you add. On a screen about the width of your hand.
This is a UX piece first and foremost: how travel sites can show multi-day, multi-city itineraries on a small screen, from the day-by-day layout to maps and pricing. The river trip is simply the worked example.
A good reference point is the way Celebrity River Cruises presents its cruise and land package. Its before-and-after city stays let guests add nights in Budapest, Prague, Amsterdam or Lausanne around a sailing, with hotels, daily breakfast, ship transfers and a daily tour from its Discovery Collection included. The land portion is presented as part of the trip rather than an afterthought, which is exactly the mental model an itinerary page should support. Viking and AmaWaterways also sell pre- and post-cruise extensions, so the pattern is familiar to anyone shopping the category.
From a design point of view, that changes the shape of the page. The itinerary isn't "a week on a ship". It's "a couple of nights in a city, a week on the river, maybe a few more nights somewhere else".
Here's the structure we'd sketch first.
Before any detail, give people the whole trip in one glance. Start city, end city, number of nights on land and on the river, and the month. On mobile, this works best as a compact horizontal strip that sits just below the hero image.
If a visitor only reads one thing, it should be this.
This is the heart of the page. Each day becomes a collapsible row with a short title, the place name and one line about the highlight. Tap to expand for detail.
The GOV.UK Design System has a step-by-step navigation pattern built on the same idea. It presents an end-to-end journey in logical steps, lists them in the order people need them and lets users expand each one. A holiday isn't a government form, but the logic transfers neatly.
We'd visually separate the land days from the river days. A different icon or background tint tells people instantly where they'll be sleeping.
Maps are where most itinerary pages go wrong on mobile. A full interactive map often traps the scroll, so the user tries to move down the page and ends up panning across Germany instead.
We'd use a static, simplified route map by default, with numbered stops that match the timeline. A clear "Open interactive map" button can launch the full version for people who want it.
Each before or after stay deserves its own card. City name, hotel tier, what's included and one striking image. Keep the cards consistent so people can compare them quickly.
Pricing needs to be honest and readable. Show the starting price per person, say clearly what it includes and make the effect of adding a land stay obvious. Hidden extras discovered at checkout are the fastest way to lose trust.
On mobile, a slim bar at the bottom of the screen with the price and a "Check dates" button keeps the main action within reach without hijacking the page.
Itinerary pages are dense, and that density creates accessibility problems. Tiny map pins, cramped day toggles and small text links are hard to hit with a thumb.
The WCAG 2.2 guidance on target size sets a minimum of 24 by 24 CSS pixels for interactive targets, with some exceptions. On a page full of toggles and pins, designing to that minimum, or larger, makes a real difference to how usable it feels.
A few other details we'd sweat:
Times in local time zones, labelled clearly.
Readable place names, not just port codes.
Image weight, so a page full of castles doesn't crawl on mobile data.
A printable or saveable version, because people love to share itineraries with family.
Before polishing anything, we'd put a rough prototype in front of real users and ask a few simple questions. Can they tell where they'll be on day four? Can they find out what the land stay costs? Can they get back to the timeline after opening the map?
If the answers are quick and confident, the structure works. If people hesitate, the layout needs another pass before anyone touches the visual design.
A Rhine itinerary is a lovely thing to design for, full of castles, vineyards and old towns. But the beauty only lands if the structure is clear. Summarise the trip first, let people expand the detail day by day, treat land stays as part of the journey and keep the price honest.
Get those right on a phone, and the desktop version will almost take care of itself.
I'm Tom, a Web Developer at Shape - when I'm not making slick Craft CMS or Shopify websites, I'm usually feeding my sourdough starter or baking a loaf.