Himalayan Brothers Hotels
Five family-run hotels from Dharamshala to Spiti, rebuilt from an old site that had given one hotel another's coordinates and every room of one hotel the description of another's.
- Client
- Himalayan Brothers Hotels
- Location
- Dharamshala, Spiti & Chamba
- Sector
- Hospitality · Hotel group
- Year
- 2026
- Stack
- Astro 7 · TypeScript
- Scope
- Five-hotel group site, rebuilt from an audit
The brief
Two brothers who started out as mountain guides run five hotels across Dharamshala, Spiti and Chamba. Their old site had to be replaced without losing a single URL, a single real review, or the brand searches that brought nearly every click.
The build
- 01Five hotels and 20 room types in one typed data file
- 02One booking form: WhatsApp for three hotels, the booking engine for two
- 03Every old URL kept, old room pages redirected to anchors
- 04No rating or review on the page that can't be traced
The result
The notes
- 01
The audit
What the old site was actually saying
A scripted crawl of the old Next.js site read every page the way a search engine does, page data and JavaScript included. It found Samdupling standing at Buddha House's coordinates in the structured data, every hotel sharing one
@id, and every Buddha House room described with Quartz's text./attractionswas in the sitemap and returned a 404;/faqwas in the menu, missing from the sitemap, and canonicalised to the About page. Property pages had two H1s and the home page none. The meta keywords read “titla, meta, nextjs”. Diwan's Tripadvisor button opened Quartz's listing, white text sat on orange at 2.6:1, and the post about Tibetan culture in Dharamshala was illustrated with the Potala Palace in Lhasa. None of it showed on a quick look. All of it was there to read. - 02
Recovery
The content was all there, in the JavaScript
The old site rendered in the browser, so a first pass that read only server HTML found almost nothing and concluded half the rooms were unpublished. The second pass read each page's data and its own JavaScript chunk, and recovered about 150 original photographs, the original logo files, full room data for all five hotels, every group and property FAQ, and 25 named guest reviews. Every hotel fact on the new site comes from there or from the family.
- 03
One file
One data file, four outputs
Hotels, their 20 room types (floor area, beds, occupancy, amenities), FAQs and reviews live in typed data. The same file renders the pages, the
HotelandHotelRoomstructured data,llms.txt, and a Markdown copy of every page served for AI tools. They can't disagree, because there is only one of them. Anything still unconfirmed carries aneedsClientReviewflag, andnpm run content:reportlists every flag for the owners in one place. - 04
Booking
One form, two kinds of booking
Quartz and Spiti Villa run booking engines; Buddha House, Samdupling and Diwan confirm stays on WhatsApp. Guests shouldn't have to know that. One form asks for the hotel, the room, the dates and the guests, then opens the right engine for two hotels and a pre-written WhatsApp message for the other three. Without JavaScript it still submits. There are no links out to online travel agencies.
- 05
Reviews
Only reviews you can find
The old home page had a strip of MakeMyTrip, Goibibo and Google ratings with quotes that couldn't be traced to any listing, so it went. Of the 25 named guest reviews on the old site, 6 couldn't be found on Google and were removed. The ratings that remain are each hotel's Google and Tripadvisor figures with the date they were checked: 2,285 Google reviews across the group. There is no review markup, because Google treats a business marking up reviews of itself as self-serving.
- 06
URLs
Every old address still lands somewhere
Hotel pages kept their exact old URLs, down to
/dharamshala-hotels-buddha-house-himalayan-brothers. The old per-room pages, ten of them still indexed, now 308 to#room-…anchors on their hotel's page. The retired Spiti URL points at Spiti Villa, the misspelt footer link to the cancellation policy works, and the bare domain goes towwwin one hop, so the canonical finally agrees with the address the site is served from. - 07
Search Console
What the launch-day numbers said
On the day the new site went live, the old one's last 28 days stood at 164 clicks and 4,980 impressions at an average position of 4.7, and nearly every click came from someone searching a hotel's name: “quartz himalayan brothers” alone brought 45 in three months. So hotel titles lead with the full name again, and “The Quartz Guest House”, which draws about a thousand impressions a month, became Quartz's alternate name, flagged for the owners to confirm. The most useful line in the export: Buddha House, the priority property, had 0 clicks from 242 impressions at position 2 for its own full name. That's a snippet problem, not a ranking one, and its new title is written for it. These figures are the baseline to measure against, not a result.
- 08
Performance
The bug that hid the LCP
At launch, Lighthouse on mobile scored 98–100 for performance on all 12 pages tested and 100 for accessibility, best practices and SEO, with LCP between 1.7 and 2.3 seconds and layout shift under 0.01. Desktop scored 100, the Buddha House page ships about 3.4 KB of JavaScript gzipped, and axe found zero violations across 19 pages at phone and desktop widths. One of those numbers was briefly impossible to get: the carousel's smooth scrolling stopped Chrome recording an LCP at all, so there was nothing to measure until it was fixed. Inlining all the CSS was tested too, and dropped: once pages were compressed it gained nothing.
- 09
Sister site
The travel desk next door
The same family runs tours and taxis from Buddha House at himalayanbrothers.com. That site was built afterwards on this one's design system, and its structured data points at these hotels' own IDs, so search engines see one family business rather than two strangers. Read the Himalayan Brothers travel case study → A third site, sachpass.com, is run from Diwan Sachpass at Bairagarh and lists every stay on the road over the pass.
- 10
The lesson
An old site can look finished and be wrong in a dozen places nobody reads. Read it the way a crawler does before redesigning anything, because the redesign will faithfully carry every mistake you didn't look for. More on what a hotel site needs in hotel and homestay websites for direct bookings.
Gallery




Questions I get.
Himalayan Brothers Hotels is a family-run group of five hotels in Himachal Pradesh: Buddha House and Quartz near the Norbulingka Institute in Dharamshala, Samdupling in Mohli, Spiti Villa near Kaza in Spiti, and Diwan Sachpass near Sach Pass in Chamba. Divyansh Sood rebuilt the group's website in Astro in 2026.
One booking form covers all five hotels. For Quartz and Spiti Villa it opens their booking engines; for Buddha House, Samdupling and Diwan it opens WhatsApp with the stay already written out. It still works without JavaScript.
Every hotel page kept its exact old URL. Old per-room pages redirect permanently to anchors on their hotel's page, retired slugs point to their current pages, and the bare domain redirects to www in a single hop.
Because Google treats review markup that a business publishes about itself as self-serving and won't show stars for it. The site shows each hotel's Google and Tripadvisor rating to people, with the date it was checked, but adds no review markup. Unverifiable ratings and six untraceable reviews from the old site were removed.
At launch Lighthouse scored 98–100 for mobile performance on all 12 pages tested and 100 for accessibility, best practices and SEO, with LCP between 1.7 and 2.3 seconds. Desktop scored 100, and axe found no accessibility violations across 19 pages.
Yes. It is the same family's travel desk, run from Hotel Buddha House, and it was built on this site's design system. Its structured data references these hotels' own identifiers so the two sites read as one business.
