The situation
An established Nepali trekking operator running guided departures on the main Everest, Annapurna and Manaslu routes, plus a smaller programme of less-travelled itineraries. Physical office in Thamel, an experienced guiding team, and a genuine safety and logistics record.
Their commercial problem was dependence. Almost all bookings arrived through international aggregator platforms and agent relationships, both of which took a substantial share of the margin and, more importantly, owned the customer relationship. Direct bookings through their own website were a rounding error, despite the site having existed for years and describing every trek they ran.
The diagnosis
The site was not broken. It was invisible for a specific and fixable set of reasons.
Trek pages competed with each other
Several near-identical pages existed for variations of the same trek — different durations, different starting points, an older page and a newer one that had never been consolidated. Search engines had multiple candidates for the same query and no clear signal about which to rank, so none of them ranked well. This is the most common technical pattern in trekking sites and it is almost always the result of pages being added over years without anyone removing or consolidating the old ones.
The content answered the wrong question
Existing trek pages were essentially itineraries: day one, day two, day three, altitude, teahouse. That is what you need after you have chosen an operator. What people search before choosing is different — whether they are fit enough, what the altitude sickness risk actually is, which season is genuinely better and why, what the permit process involves, what the realistic total cost is including the things that are not in the headline price, and what happens if somebody has to descend early.
Source markets were treated as one audience
The site addressed “international trekkers” as a single group. In practice the source markets behave differently: search vocabulary differs, the booking lead time differs, the questions asked differ, and what counts as a reassuring credential differs. A single generic page cannot serve all of them well.
Seasonality was not reflected anywhere
The research window for an autumn trek opens months earlier than the season itself, and from time zones where the business is asleep. Content was being published according to internal convenience rather than against that cycle, which meant the right page frequently arrived after the decision had been made.
Local search was unclaimed
The Thamel office had an incomplete Google Business Profile. Walk-in and same-day booking traffic in that neighbourhood is real and it is decided almost entirely on profile completeness, photographs and recent reviews.
What was delivered
Consolidation before creation
The first substantive work was subtractive. Duplicate and near-duplicate trek pages were merged into one authoritative page per trek, with redirects mapped from every retired URL so that whatever the old pages had accumulated was preserved rather than discarded. Nothing new was written until this was done.
Trek hubs built around the pre-booking decision
Each major trek became a hub covering the questions that get asked before an operator is chosen: fitness and preparation, altitude and acclimatisation, season comparison with honest trade-offs, permits and paperwork, realistic total cost including what is excluded, and what the operator does when something goes wrong. The itinerary remained, but as one component rather than the whole page.
Source-market differentiation
Keyword and content work separated by source market rather than pooled, with vocabulary, lead time and question set handled distinctly, and the technical signals set correctly so that search engines could tell which content was intended for whom.
Safety and credential content as a ranking and conversion asset
Guide qualifications, insurance arrangements, group sizes, evacuation procedure and emergency protocol written out plainly. Most competitor sites assert that they are safe; very few explain what that means operationally. This content did double duty — it answered real searches, and it was the material that turned a researcher into an enquiry.
Seasonal scheduling
A content calendar built against the research window rather than the trekking season, so that pages were indexed and established before the demand arrived.
Local and measurement
Google Business Profile completed for the Thamel office with current photographs and a review workflow. Search Console and Analytics set up under the client's ownership, with a named metric agreed in writing before implementation — direct booking enquiries from organic search, not sessions.
What actually mattered
The consolidation. It was the least visible work in the engagement and the thing that made everything after it possible. Three pages competing for the same trek is a self-inflicted problem, and no amount of new content resolves it — new pages simply join the pile.
The second was writing honestly about difficulty and risk. Publishing that a trek is genuinely hard, that a specific season has real drawbacks, and that some people should not attempt a particular route felt commercially counterintuitive to the client at the start. It attracted better-qualified enquiries, from people who had read the difficult parts and were contacting anyway, and it distinguished the operator in a category where nearly every competitor is uniformly reassuring.
What I would do differently
I treated the aggregator dependency as background context rather than as part of the brief. In hindsight the engagement should have explicitly addressed the transition — what a direct booking path needs to look like, what happens to pricing when the platform margin is removed, and how the business handles enquiries arriving in a different form. Search visibility that produces enquiries a business is not set up to convert is a partial job.
I would also start the source-market separation earlier. It was sequenced after the trek hubs, which meant the first versions of those hubs had to be revised once the market distinctions were properly understood. Doing the research first would have avoided rewriting.
Whether this applies to you
If you run treks and have several pages describing variations of the same route, you have the duplication problem in this case study, and it is worth checking before commissioning any new content. If your trek pages are essentially itineraries, you are answering the post-decision question and missing the pre-decision searches where the choice is actually made.
If your dependence on aggregators is the real commercial problem, be clear that organic visibility is one part of solving it and not the whole of it. The direct booking path has to exist and work.
More on the vertical: trekking agency SEO services, the full trekking agency SEO guide, and hotel and tourism SEO.