SEO · Web
Tripianto
Itinerary-led architecture for an operator competing on custom trips rather than fixed departures.
Work / Nile River Trips
Nile River Trips had the boats, the itineraries and the departures. What it didn't have was a way for a traveller to find any of it in search — the inventory lived in a downloadable PDF that Google could never index. We turned it into landing pages.
The challenge
A traveller planning a Nile cruise doesn't search for "Nile cruise". They search for "4-night Nile cruise from Luxor", or "deluxe dahabiya Aswan to Luxor" — itinerary length, boat category and departure port, in that order. Those are the decisions they're actually making.
Nile River Trips answered all of those questions — but only inside a downloadable PDF and a single catch-all page. None of it was an indexable page, so none of it could rank. The moment a traveller asked a specific question, the site had no specific page to meet it with.
The brief was: how do you make a cruise fleet searchable the way people actually shop for one? Everything followed from treating each real variable — length, category, port — as its own landing page rather than a row in a document.
The approach
The build
The work wasn't writing more copy — it was converting a static inventory into a structure search engines could read. Each cruise became a landing page generated from the same fields the operator already tracked: length, category, port. Nobody rebuilds these by hand every season.
On top of that sits a schema and entity graph that connects boats to ports to itineraries, so the site can be cited in an AI answer and not just listed in blue links. For a category as specific as Nile cruises, being named in the answer is the whole game.
The result is a fleet that's findable at the exact grain travellers search — by nights, by boat, by port. A downloadable PDF asks the traveller to do the sorting. A system of pages does the sorting for them, and gets indexed while it's at it.
Results
↑ Placeholder metrics — replace with figures from Search Console and analytics before publishing. Never publish a number you can't screenshot.
More work
SEO · Web
Itinerary-led architecture for an operator competing on custom trips rather than fixed departures.
Web design · Build
Rebuilt as a booking engine rather than a brochure: licences above the fold, two paths off the hero, multi-currency pricing and destination-first architecture.
Your turn
Is your inventory searchable the way people actually shop for it — or locked in a PDF? Send us the URL and we'll answer it in writing — free, and yours to keep.