Case 11 of 17
Travel · Taxi & Yatras · 2026

Shiva Tour and Travel

In one line

A taxi and temple-yatra operator beside Kangra Airport, rebuilt from a mockup that invented its own reviews — and a build that stops them coming back.

Client
Shiva Tour and Travel
Location
Gaggal, Kangra
Sector
Travel · Taxi & Yatras
Year
2026
Stack
Astro 7 · About 1 KB of JS
Scope
58 pages: 20 packages, 21 taxi routes, a temples guide
Shiva Tour and Travel — homepage hero, desktop
01 — Grid slot

The brief

Manish Kumar runs a Swift Dzire and an Innova Crysta from beside Kangra Airport at Gaggal: airport and station pickups, temple yatras and Himachal tours. The design mockup looked good, and it was full of numbers nobody had given.

02 — Setup

The build

  1. 0120 packages, 21 taxi routes, a guide to 14 temples with a distance chart, and 5 posts
  2. 02Fake stats, reviews and urgency badges banned by the build
  3. 03One prices file feeds cards, FAQs, schema and llms.txt
  4. 0463 places linked to the right Wikipedia and Wikidata entries
03 — Telemetry

The result

CH.01 58 Pages in its sitemap, Nov 2026
CH.02 63 Places verified on Wikidata
CH.03 95–100 Lighthouse mobile, 9 page types

What clients say about working with me

04 — Debrief

The notes

  1. 01

    Banned

    What the mockup made up, the build refuses

    Every invented stat, review and badge was removed, and the post-build check now fails if any of them reappears: the mockup's numbers and names, urgency badges, “police-verified”, GST-invoice wording, review markup, a broken “₹null”, or any React runtime shipped by accident. The mockup's own page URLs 301 to their real pages. A design that ships with a fake 4.9★ isn't a draft; it's a claim the business would have to answer for.

  2. 02

    Prices

    One prices file

    A single file holds the taxi fares and the date they were last updated. It drives the price cards, the fare FAQs, the Offer schema (valid for a year from that date), the price range in the business's structured data, llms.txt, and the “fares updated” line, so a fare changes in one place. Fares include fuel, tolls, parking and state entry tax and are the same in both directions, so the return trip is answered as a question on the same page instead of a near-duplicate reverse page. Package prices were taken down on 12 October and replaced with a WhatsApp quote card.

  3. 03

    Temples

    Historic Temples, not Devi Darshan

    The temple trips are labelled “Historic Temples” across the site, while the words people search, like Devi Darshan, stay in the copy where they belong. One guide page covering 14 temples, and a temple distance chart, answer the planning questions. Temple distances were re-measured through OSRM between the temples' own map points, 85 pairs averaged over both directions, and some of the old figures turned out to be about 5 km too high. Distances always carry a “≈”, and drive times are padded for hill roads.

  4. 04

    Photos

    No stranger's car

    Until the owner's car photos arrived, the two cars were drawn, not photographed. The component's own comment explains why: “A stranger's car in a stock photo would be a small lie on the one thing customers check.” Two of the owner's photos were left out: one with a well-known guest, who'd need to agree first, and one showing two Innovas against a stated one-Innova fleet. Temple photos are public domain, so no credit is needed anywhere. Where no such photo exists of a temple, the trip shows a nearby scene rather than a different temple.

  5. 05

    Entities

    The right Wikipedia page, or none

    Search engines and AI assistants match a page to the places it talks about. So 63 places mentioned on the site are tied to their Wikipedia and Wikidata entries, checked one by one. Places without a clean entry are left unlinked, because, in the data file's own words, “no link beats a wrong one.” The build fails on any sameAs link that isn't Wikipedia or Wikidata.

  6. 06

    Answer engines

    Written to be quoted

    Every web page carries speakable markup, and the build fails without it. There's an llms.txt index with fares, an llms-full.txt that the build checks contains every taxi, package and blog page, and an RSS feed. Every blog post is linked from every footer, and every page needs at least three inbound links and must sit within three clicks of home.

  7. 07

    Speed

    Tap to load the map

    On 11 October Lighthouse on mobile scored 95–100 for performance across nine page types. The contact page reached 99 once the Google Map became tap-to-load: the embed had been costing about three seconds of first paint on phones. The site ships roughly 1 KB of inline JavaScript, for the menu and the route tabs.

  8. 08

    The lesson

    A mockup is a picture of a website, and pictures fill empty space with confident numbers. Each one has to be traced to the owner or deleted, and then the build has to stop it coming back. See also Baglamukhi Travels, another Kangra operator built around the six-temple yatra.

05 — Onboard

Gallery

Shiva Tour and Travel — the tour packages page
On mobile
Shiva Tour and Travel homepage on a phone
Shiva Tour and Travel — the tour packages page on a phone
06 — Before you ask

Questions I get.

Shiva Tour and Travel is a taxi and tour operator run by Manish Kumar near Kangra Airport at Gaggal, Himachal Pradesh, with a Swift Dzire and an Innova Crysta. It offers airport and station pickups, outstation taxis, historic temple yatras and Himachal tour packages. Divyansh Sood built its website in Astro in 2026.

Next project → P12
Sach Pass
Travel · Stays & road status · 2026
Sach Pass website