

Strictly confidentialGEO · Revenue Leak Audit
Annapurna View Hotel
The rarest view in Pokhara is already yours. But AI ranks the site for Nepali New Year, not hotel stays, so "hotel in Sarangkot" is answered with a competitor.
AI visibility score
Google authority score
Inside this audit
| Client | Annapurna View Hotel, Sarangkot, Pokhara | Document No. | ELG-AVH-1911 |
| Scope | Crawl → Schema → Bookings | Issued | 19 Nov 2026 |
| Data | Semrush crawl of 78 pages on 19 Nov 2026. Search data is desktop, worldwide, as of 18 Nov 2026. | ||

Where annapurnaview.com stands today
SEO & GEO Revenue Leak Audit
annapurnaview.com has a sound technical foundation, but its SEO growth is held back by broken links, duplicate metadata and a weak, off-topic backlink profile. The Semrush crawl of 78 pages on 19 Nov 2026 found 2,059 issues: 66 errors, 410 warnings and 1,583 notices.
The three priorities
Scorecard, out of 100
Technical SEO is largely healthy. No server errors (5xx), no pages blocked from indexing, a working robots.txt, XML sitemap and 404 page, and no mixed-content, multiple-canonical or frame problems.
The 66 errors come from three causes. 40 resources returning 4xx, 9 duplicate titles and 17 duplicate meta descriptions.
Link hygiene is the biggest warning. 362 broken links make up 88% of the 410 warnings.
Visibility is thin and not hotel-focused. The site gets about 1.9K organic visits a month from 353 keywords, and its top ranking keywords are about Nepali New Year, not Pokhara hotel stays.
Authority is low for the link volume. Authority Score is 10 despite 2.2K referring domains and 4.2K backlinks, which points to links that are many but not relevant or strong.

Site Health Audit
SEO & GEO Revenue Leak Audit
Issues by severity
Issues by type
Scorecard by area
No server errors. The foundation is solid. Organic traffic 1,900 visits / month · up 8.6%


Technical SEO health
SEO & GEO Revenue Leak Audit
Checks by result
The technical base is healthy. Search engines can crawl and index the site, and the core setup is correct. What remains is cleanup (dead URLs, broken links, heavy pages) and three checks that the audit did not run.
The three untested items should be checked in Google Search Console and PageSpeed Insights, because the crawl returned no data for them.
Server errors (5xx)
The server is stable; Google is not hitting failures
Pages restricted from indexing
No page is accidentally blocked by noindex or robots rules
robots.txt
Crawlers get clear instructions
XML sitemap
Helps Google discover all 78 pages
404 page
Dead URLs return a proper 404 rather than a soft error
HTTPS mixed content
Secure pages load only secure resources
Multiple canonical URLs
No conflicting canonical signals
Pages with frames
Content is not hidden inside frames
Too long URLs
URLs are short and readable
Resources with 4xx status
Wasted crawl budget and lost link value
Too big pages
Slow loading hurts rankings and bookings, especially on mobile
Dynamic URLs
One parameter URL may create duplicate versions of a page
Mobile friendly
Most hotel searches are on mobile; this must be verified
W3C HTML and CSS errors
Low impact, but worth a quick validation

Issues, SEO impact and what to do
SEO & GEO Revenue Leak Audit
Issues are ordered by priority. Fix the High items first; they cover all 66 errors plus the largest warning. Bars use a log scale so small counts stay visible.
| Priority | Issue | Count | Why it costs you | What to do |
|---|---|---|---|---|
| High | Resources with 4xx statusError | 40 | Googlebot wastes crawl budget on dead URLs, users land on error pages, and any backlinks pointing to them pass no value | Export the 4xx list. Add a 301 redirect to the closest live page for each, or restore the page if it should exist. Remove the URLs from the sitemap |
| High | Broken linksWarning | 362 | Broken internal links break crawl paths and dilute link equity; broken external links lower content quality and trust | Fix or remove each link. Update internal links to the final URL. Replace dead external links with working sources, and re-crawl monthly |
| High | Duplicate meta descriptionsError | 17 | Weakens click-through rate from search results and blurs what each page is about | Write a unique 140 to 155 character description per page with the room type, Pokhara location and a call to action |
| High | Duplicate titlesError | 9 | Pages compete against each other for the same query and Google may pick the wrong page to rank | Give each page a unique title with its own primary keyword, for example the page topic plus Annapurna View Hotel, Pokhara |
| Medium | Too long titlesWarning | 36 | Titles over about 60 characters are cut off in results, hiding the keyword and brand | Shorten to 50 to 60 characters and put the main keyword first |
| Medium | Too big pagesWarning | 10 | Heavy pages load slowly, which hurts Core Web Vitals, mobile rankings and booking conversions | Compress and convert images to WebP, enable lazy loading, minify CSS and JS, and turn on caching and a CDN |
| Medium | Empty meta descriptionWarning | 1 | Google writes its own snippet, which may not sell the page | Add a custom description to that page |
| Low | Pages with excessive linksNotice | 42 | Spreads link value thinly and can make pages harder to crawl and use | Cut footer and menu link clutter; keep links that help users and bookings |
| Low | Dofollow external linksNotice | 1,369 | A high count passes authority away from the site; unreviewed outbound links can point to poor sites | Review them, keep trusted sources, and add rel nofollow or sponsored to ads, partners and unvetted links |
| Low | Dynamic URLsWarning | 1 | Parameter URLs can create duplicate versions of the same page | Use a clean URL, or add a canonical tag pointing to the main version |
| Check | Mobile, W3C HTML and CSSCheck | Not tested | Mobile usability is a ranking factor, and markup errors can break rendering | Run Search Console Mobile Usability and PageSpeed Insights, then validate with the W3C validator |

On-page SEO: titles and descriptions
SEO & GEO Revenue Leak Audit
63 title and description flags across 78 pages (up to 81% of the site), counting 9 duplicate titles, 36 too long titles, 17 duplicate descriptions and 1 empty description. Pages can have more than one problem, so the true share is lower.
Title and description flags
Bar length is out of all 78 pages crawled.
Up to 63 of 78 pages carry a title or description flag
One square per page. A page can carry more than one flag, so the real share is lower.
| Passing | Failing | Action | |
|---|---|---|---|
| Title tags | No empty titles | 9 duplicate, 36 too long | Rewrite to 50 to 60 characters, unique per page |
| Meta descriptions | None too long | 17 duplicate, 1 empty | Write unique 140 to 155 character descriptions |
Suggested patterns for a hotel site, using the homepage title Annapurna View Hotel, Hotel in Sarangkot, Pokhara as the brand anchor:
Suggested title length, characters (Google shows about 60)
Also confirm each page has one H1, descriptive image alt text, and hotel schema markup (Hotel, LocalBusiness and FAQ) so results can show ratings, price and location.

How many people find you on Google
SEO & GEO Revenue Leak Audit
The site earns about 1.9K organic visits a month (+8.6%) from 353 organic keywords (-0.3%), with no paid traffic. Semrush data is for desktop, worldwide, as of 18 Nov 2026.


Traffic trend, last 2 years
Read from the chart, so approximate. Organic traffic ran between 1K and 2.8K through 2025 and early 2026, spiked to about 5.5K in early July 2026, then fell back to roughly 1.8K. Branded traffic is about 1.2K, so around two thirds of current organic visits come from people who already know the hotel. The July spike did not hold, so it should be treated as a one-off rather than growth.

Where the site ranks, and what it should rank for
SEO & GEO Revenue Leak Audit
Top organic keywords (UK) · position on Google, dot size = searches a month
The site ranks on page 1 or 2 for festival searches that rarely convert into room bookings. The commercial opportunity is in searches such as hotel in Sarangkot, Pokhara hotels with mountain view and Annapurna view hotel Pokhara, none of which appear in the top keywords.
Hotel searches with no ranking
All five are informational, and none is a hotel-booking search.
Searches a month (grey) against the visits the site gets (black)
Recommendations
- Build dedicated landing pages for hotel in Sarangkot, Pokhara hotel with Annapurna view, and sunrise-view stays.
- Keep the Nepali New Year content but add a booking link and a festival-stay offer, so that traffic has a path to conversion.
- Create a trekking-stay page to catch annapurna trek nepal (480 searches, position 36) with an acclimatisation and pre-trek hotel angle.
- Track hotel-intent keywords weekly in Semrush Position Tracking for Nepal, India, UK and US.

Many links, little trust
SEO & GEO Revenue Leak Audit
Volume versus trust
Authority Score, out of 100
Diagnosis
The site has 4.2K backlinks from 2.2K referring domains, yet its Authority Score is only 10. A profile that large with that score usually means many low-quality or unrelated links, so the number of links is not the problem; their relevance and strength are. The first step is to review the profile, not to add more links.
Step 1: audit the existing profile (week 1 to 2)
- Export all 2.2K referring domains from Semrush Backlink Audit and flag spammy, adult, gambling, hacked or foreign-language directory links.
- Check the Toxicity Score and remove what can be removed by contacting the site owner; use the Google disavow file only for clear spam that cannot be removed.
- Find backlinks pointing to the 40 dead URLs and redirect those URLs, which recovers link value at no cost.
Step 2: build relevant backlinks (ongoing)
Relevant means travel, hospitality, Nepal, Pokhara and Himalayan trekking. A few links from these sources are worth more than hundreds of generic directory links.
Hotel and booking listings
Examples to pursueGoogle Business Profile, TripAdvisor, Booking.com, Agoda, Expedia, with a link back to the official site
Why it is relevantTrusted hospitality signals and direct booking traffic
TargetClaim and complete all, keep name, address and phone identical
Trekking and tour operators
Examples to pursueOperators running Annapurna, Poon Hill and Pokhara itineraries
Why it is relevantTheir guests need a hotel before and after treks
TargetPartner pages with a link to your stay package
Own content assets
Examples to pursueSarangkot sunrise guide, Pokhara in 3 days, best time to see Annapurna
Why it is relevantContent that others cite and link to
Target1 new guide a month

Already mentioned, but not for hotel stays
SEO & GEO Revenue Leak Audit
Needs work
Cited pages overlap across platforms, so they do not add up to the 35 total.
Times AI named the site, by platform
ChatGPT
Gemini“Hotel in Sarangkot with mountain view”
PerplexityNot cited“Pokhara hotels with Annapurna view”
ChatGPTCompetitors named“Best place to stay for Sarangkot sunrise”
GeminiNot cited“Is Annapurna View Hotel good?”
ChatGPTFoundWhen guests ask about you by name, AI knows you. When they ask for a hotel, it names someone else.
Recommendations
Add FAQ sections and FAQ schema to room, location and package pages (check-in times, distance to Sarangkot sunrise point, airport transfer, best season).
Write short, direct answers near the top of key guides, so AI tools can quote them.
Keep name, address, phone, amenities and prices consistent across the site, Google Business Profile, TripAdvisor and booking sites.
Earn mentions on trusted travel sources, which AI tools draw on; this supports the backlink plan above.

The moment that matters
SEO & GEO Revenue Leak Audit
The moment that matters
A traveller planning Pokhara opens their phone and asks "best hotel in Sarangkot with a mountain view?"
If Annapurna View is named among the recommended options, the booking is close to won, because the guest is already deciding where to watch the Annapurna sunrise. Today the hotel's real advantage, a hilltop Sarangkot position with panoramic Annapurna and Machapuchare views, is not understood by AI. The site carries no structured hotel signals and its visibility is built on festival content, not stays.
These are not technical problems. They are revenue problems. Fixed, they let Annapurna View own "hotel in Sarangkot" and "Pokhara hotel with Annapurna view" instead of ranking on page one for a Nepali New Year search that never books a room.

The Pokhara Opportunity
Pokhara is where the Annapurna trade sleeps, and the booking decision is made on a phone.
International visitors entered Nepal in 2025. Pokhara is the gateway to the Annapurna region, and most overnight before or after a trek.
Per-night rate for a premium mountain-view room. Strong value for a private Sarangkot sunrise over the Annapurnas.
Peak months for clear mountain views and trekking demand, exactly when sunrise-stay searches spike.
Most visitors searching for a Pokhara hotel decide within hours, not weeks, which makes the AI recommendation extremely valuable at the point of intent. India, Nepal's largest source market, has rapidly growing ChatGPT usage, so AI referrals are becoming decisive for inbound demand.

What makes it different
This gives AI a unique, hard-to-copy story: a named ridge, a named sunrise point, a named mountain. Those are strong entity signals for engines looking for a real place. Right now that story reads as ordinary prose, so the machine recommends whichever Pokhara hotel it can read.

How AI-influenced demand becomes booked rooms
SEO & GEO Revenue Leak Audit
Annual AI-influenced funnel
Read the funnel top to bottom. The share captured is set conservatively, because today the hotel is cited for the wrong searches, but a hilltop sunrise property converts hotel-intent inquiries at a healthy rate once the engines can read it.
Estimated annual upside
≈ NPR 1,60,00,000Including restaurant and bar spend, direct-booking commission saved versus OTAs, repeat stays, and the search visibility AI recommendations create.
Direct AI bookings
NPR 1,10,40,000552 bookings × NPR 20,000 average booking value (about two mountain-view nights).
| AI-influenced decisions a year | 20,000 |
| Recommended by AI | 15% |
| Become inquiries | 40% |
| Inquiries that book | 46% |
| Average booking value | NPR 20,000 |

The work, month by month
SEO & GEO Revenue Leak Audit
Each month has a plain-language goal and the exact engineering behind it. The order matters: fix the foundations, make the hotel machine-readable, publish the pages that book rooms, then build the trust that gets you recommended.
Every broken page and duplicate fixed, and today's numbers locked so every gain is provable.
Google and AI learn the facts: what you are, where you are, what rooms cost and how guests rate you.
New pages built for the searches that actually turn into stays.
Remove the junk links dragging trust down and recover the value of the good ones.
Get trusted travel sites and real guests talking about you, the signals AI relies on.
Show exactly which bookings came from AI and search, then hand everything over.

The work in detail, months 1 to 3
SEO & GEO Revenue Leak Audit
Clean-up & baseline
Every broken page and duplicate fixed, and today's numbers locked so every gain is provable.
Technical work
- Full crawl export; 301 redirect map for all 40 4xx URLs to the closest live page; dead URLs removed from the XML sitemap
- Fix or remove all 362 broken links; internal links repointed to final 200-status URLs
- Rewrite 9 duplicate and 36 over-long titles (50-60 chars, keyword first) and 17 duplicate and 1 empty meta descriptions (140-155 chars)
- Parameter URL consolidated with
rel="canonical"; one<h1>per page robots.txtpolicy for GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot, Google-Extended; publish/llms.txt- Baselines: Search Console, GA4, Semrush Position Tracking (Nepal, India, UK, US), AI citation share per engine
Make the hotel machine-readable
Google and AI learn the facts: what you are, where you are, what rooms cost and how guests rate you.
Technical work
- JSON-LD
@graph:Hotelwithgeo,address,amenityFeature,checkinTime,priceRange,starRating HotelRoom+Offerper room type;FAQPage,BreadcrumbList,AggregateRatingfrom verified reviewsOrganization.sameAslinking Google Business Profile, TripAdvisor, Booking.com, Agoda- Validated in Google Rich Results Test and Schema.org validator before release
- Images to WebP/AVIF with
srcset,loading="lazy", fixed dimensions; minify CSS/JS, defer non-critical scripts, CDN + caching on the 10 heavy pages - Core Web Vitals on mobile: LCP < 2.5s, INP < 200ms, CLS < 0.1
Pages that book rooms
Break-evenNew pages built for the searches that actually turn into stays.
Technical work
- New landing pages:
/hotel-in-sarangkot,/pokhara-hotel-annapurna-view,/sarangkot-sunrise-stay,/pre-trek-stay-pokhara - Answer-first structure: a 40-50 word definition up top, then a facts table (rooms, rates, distance to sunrise point, airport transfer time) inside the first 150 words
- FAQ blocks with
FAQPagemarkup; descriptive alt text on every room and view photo - Nepali New Year pages get a festival-stay offer and booking link, so existing traffic has a path to a room
- IndexNow pings for Bing (the index ChatGPT search draws on);
lastmodkept accurate in the sitemap

The work in detail, months 4 to 6
SEO & GEO Revenue Leak Audit
Clean up who links to you
Remove the junk links dragging trust down and recover the value of the good ones.
Technical work
- Export all 2,200 referring domains; score toxicity; request removals; submit a
disavow.txtfor unremovable spam - Recover links pointing at the 40 dead URLs through the Month 1 redirects
- Identical name, address and phone across Google Business Profile, TripAdvisor, Booking.com, Agoda and Expedia
- Google Business Profile: Hotel category, amenities, room photos, Q&A and booking link
Earn recommendations
Get trusted travel sites and real guests talking about you, the signals AI relies on.
Technical work
- Partner pages with Annapurna and Poon Hill trek operators linking to a pre/post-trek stay package
- One linkable guide a month: Sarangkot sunrise guide, Pokhara in 3 days, best time to see Annapurna
- Post-checkout review request flow (Google + TripAdvisor) feeding
AggregateRating dateModifiedand visible "last updated" dates on room and package pages
Prove it & hand over
Show exactly which bookings came from AI and search, then hand everything over.
Technical work
- GA4 custom channel group "AI referrals" matching chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, claude.ai
- Booking-engine conversion events tied to traffic source
- Full re-crawl and AI prompt panel re-run against the Month 1 baseline
- Handover: redirect map, schema files, page templates, tracking setup and a maintenance checklist

Targets by month 6
SEO & GEO Revenue Leak Audit
Today against the month 6 target
Sample · Hotel structured data
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Hotel",
"name": "Annapurna View Hotel",
"address": {
"addressLocality": "Sarangkot, Pokhara",
"addressCountry": "NP"
},
"geo": { "@type": "GeoCoordinates" },
"amenityFeature": [ "Mountain view", "Sunrise terrace", "Airport transfer" ],
"checkinTime": "14:00",
"priceRange": "NPR 6,500 – 14,000"
}
</script>
The Investment
SEO & GEO Revenue Leak Audit

Monthly retainer
NPR 35,000/ monthexcluding VAT · 6-month engagement: NPR 2,10,000 · + VAT as applicable 13%
Six months of work against one year of estimated upside
≈ 76× the six-month fee, if the estimate holds. The upside is an estimate, not a guarantee.
When the work pays for itself
The plan marks break-even in month 3, when the new booking pages go live.
What the fee covers

Executive Recommendation
SEO & GEO Revenue Leak Audit
Annapurna View already owns the rarest asset in Pokhara: a hilltop Sarangkot position with a panoramic Annapurna sunrise. The next phase of growth is not inventing a story. It is making the machines able to read the one you already have, so it stops losing "hotel in Sarangkot" to rivals.
By clearing the technical faults, adding hotel schema, and engineering the content for hotel-intent retrieval across a focused 6-month engagement at NPR 35,000 / month (excl. VAT), Annapurna View can redirect its existing AI trust from festivals onto bookings, recovering the about NPR 1.6 Crore now walking to competitors, and building an asset that compounds after the work ends.
The diagnostic work is done: the leaks are located and the fixes are sequenced to the month. The next step is small: a 30-minute walkthrough of this audit, your questions answered page by page, before any commitment.
What happens next
Before any commitment
A 30-minute walkthrough.
We go through the audit page by page, answer every question, and show you the first fix on your own site.
Book the walkthrough →eliteleadgrow.com/book-strategy-callThe audit at a glance
×
ELG-AVH-1911 · 19 Nov 2026 · Prepared exclusively for Annapurna View Hotel. Prepared exclusively for the owners and management of Annapurna View Hotel, Sarangkot, Pokhara. Contains commercially sensitive findings and proprietary EliteLeadGrow methodology. Do not copy, forward, print or distribute outside Annapurna View Hotel without written consent. Each copy is individually numbered and its circulation logged.