A catalogue organised the way travellers browse.

Jakada Tours Egypt had a deep catalogue of tours, but it was organised for the operator, not the traveller. Someone who knew they had five days and a fixed budget couldn't get to the handful of tours that fit — they had to read through everything.

Underneath that, the individual tours weren't structured to be found. Each departure was part of a general listing rather than a page in its own right, so there was nothing for Google to index and rank against the specific searches travellers actually type.

The brief was to rebuild the catalogue around how people browse — by city, by length, by budget — and make every single tour a page that could stand on its own in search.

The catalogue's structure was mapped first: how cities, lengths and budgets relate, and what a single tour page needs to carry. That decision comes before design because it's what determines how Google reads the site — and it's the part that's expensive to change later.

Built with dedicated tour post types rather than a page builder, so every departure carries proper structured data, a clean URL and a consistent booking path without anyone rebuilding it by hand. Performance was treated as a build requirement, not a phase at the end.

The result is a catalogue where the traveller reaches the right tour in the way they were already thinking, and where every tour can be found on its own. That's the whole mechanism. A catalogue earns bookings by matching how people browse — not by making them read the whole thing.