Gallery
Seven views from the finished site. Click to see a larger one.
The challenge
One Tribe takes groups to more than 48 countries, but the site lived on a locked platform where the content team could change almost nothing. To add a new departure date, in practice a new page was created — still visible in the old URLs japanas-ekspedicija-3, -6, -8: the same trip split into separate records.
That had two consequences. First, no trip had a stable number — not for the customer in a conversation, not for the team internally, not on the invoice. Second, the marketing team could not work with SEO: the platform did not let them manage titles, descriptions, keywords or body copy the way modern search requires.
The old site was not bad — it already had filters and trip cards. The problem was that the catalogue grew faster than the platform could carry it, and each new date added to the chaos.
Before and after
Pirms
Pēc
What we did
Every trip now gets a number automatically, the moment it is created. The number is visible on the trip page, in the enquiry form and in the list, and you can search the catalogue by it. The customer says the number in a conversation — the team knows at once which departure it is.
Brauciena nr. ONET-0049Catalogue search accepts a trip name, a country or an ONET number. Alongside that — destination, month, difficulty and duration, extra filters for price and trip language, and badges for “Last places”, “Flights included”, “New dates”, “Early booking”. The result count is visible immediately, and the list can be sorted.
People search differently: one browses pictures, another compares dates and prices. So the catalogue has grid, compact and list views — the same data set, three ways to read it.
We moved all the content to WordPress and built a custom theme and admin panel specifically for trips: dates, prices and discounts, difficulty, group size, remaining places, included services and galleries. The content team now adds a trip without a developer.
Titles, descriptions, URLs and body copy are in the team’s hands. Each trip is one record with its own dates — not ten nearly identical pages competing with each other in search.
Opening filters, card states, gallery transitions, the map and view switching — every action responds at once and clearly. The goal was not effects, but the feeling that the site reacts: browsing trips becomes pleasant, not merely possible.
On mobile, filters, cards and the enquiry are designed separately, not squeezed from the desktop version. On desktop we use the wider screen — more comparison in one view, a side panel with price and enquiry that stays visible as you scroll.
The One Tribe compass mark lives throughout the interface — in icons, badges, map markers and small accents. The site looks like One Tribe, not a template with a logo stuck on.
The result
The site is not publicly live yet, so we deliberately do not show traffic or conversion figures here. We will add them once the first full season cycle has run.
“Klients bija patiesi pārsteigts par gala rezultātu.”
How a project starts
No long intro. Usually one conversation is enough to understand scope and timing.
Enquiries, sales, speed or automation. A short note is enough.
Goal, audience and what you already have. Usually one conversation.
Scope, timing and the next step — before we write code.
You’ve been added to the newsletter. No spam — just useful updates.
Closes in 15 s
Ja jums ir mājaslapa, lai saprastu, kas strādā un kas nestrādā, labākais pirmais solis ir CRO audits. Bez prezentācijas — tikai konkrēti secinājumi.
Saņemt bezmaksas audituBez surogātpasta. Bez aģentūras prezentācijas. Secinājumi 2 darba dienu laikā.
