Web design · Build
Egypt Day Trips
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.
Work / Misk Tours
Misk Tours ranked fine on Google. But the traveller's first question increasingly gets answered by an AI — ChatGPT, Perplexity, Google's AI Overview — and those don't read a site the way a search crawler does. We rebuilt Misk Tours and added an entity and schema layer so the brand is legible to the machine that now writes the answer.
The challenge
Search is splitting in two. There's the ten blue links, and there's the answer an AI writes before the traveller ever sees a link. Misk Tours was built for the first and invisible to the second.
An answer engine doesn't reward the page that's prettiest or even the one that ranks first. It cites the sources it can understand — brands whose identity, offering and credentials are stated as structured facts a machine can lift with confidence, not prose it has to guess at.
The brief was: when a traveller asks an AI to plan a trip to Egypt, what makes it name Misk Tours? Answering that meant treating the site as data first and a brochure second.
The approach
The build
Strategy, design, build and the entity work came from the same team. That matters here more than usual: an entity layer that contradicts the copy, or schema that describes a page that no longer exists, actively harms trust — and that only stays consistent when one team owns all of it.
The entity and schema graph was decided before a single screen was designed — organisation identity, tour data and FAQ markup mapped first, because structure determines what an answer engine can ever lift. The rebuild was then designed around it, conversion-first, so the human who arrives after the citation meets a site that closes.
The mechanism is simple: an answer engine cites what it can understand and corroborate. You don't win the citation by shouting louder. You win it by being the source that's easiest for the machine to trust — and then not wasting the click when it comes.
Results
↑ Placeholder metrics — replace with figures from Search Console, analytics and answer-engine checks before publishing. Never publish a number you can't screenshot.
More work
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.
Web design · SEO
Tailor-made positioning made obvious in the first screen, with an enquiry flow built for high-value custom trips.
SEO · Nile cruises
Cruise inventory made searchable: itinerary length, boat category and departure port as real landing pages instead of a downloadable PDF.
Your turn
When a traveller asks an AI to plan a trip to Egypt, does it name you? Send us the URL and we'll tell you what an answer engine can and can't read about you today — free, and yours to keep.