You can write the best content in Nepal and still not rank if Google can't crawl your pages, can't tell which version is the real one, or watches visitors leave because the page took eight seconds to appear. Technical SEO is the plumbing that stops that happening. This is the checklist I run on every site I audit, ordered from "breaks everything" to "nice to have".
Why technical SEO hits harder in Nepal
Two local facts shape everything below. First, most traffic is mobile, StatCounter puts phones at roughly 57 to 62% of web traffic in Nepal. Second, mobile speeds are unusually inconsistent: Ookla removed Nepal from its global mobile speed ranking in 2024 because results across networks varied too much to compare. Fixed broadband is a different story (Ookla's early-2026 index put Nepal's fixed speeds around 84 Mbps), so a site can feel instant on office fibre and painfully slow for the customer on mobile data in Butwal. Test on the slow connection.
- 1Can Google crawl and index the site?
- 2Is there exactly one version of each page?
- 3Core Web Vitals: speed Google measures
- 4Mobile-first, for real
- 5Structured data
- 6Site structure and internal links
- 7Multilingual sites: English and Nepali
1. Can Google crawl and index the site?
- Open yoursite.com/robots.txt and make sure it isn't blocking important folders, I regularly find sites blocking their own CSS and JavaScript, which stops Google rendering the page properly.
- Search site:yourdomain.com.np on Google for a rough count of indexed pages, then check the real numbers in Google Search Console → Pages.
- Look for accidental noindex tags, often left behind from a staging site by a developer.
- Submit an XML sitemap in Search Console that lists only live, canonical pages, no redirects, no 404s, no test pages.
- Fix broken internal links and redirect chains; each hop wastes crawl time and slows users down.
2. Is there exactly one version of each page?
To Google, http:// and https://, www and non-www, and /about and /about/ can all be different URLs. If all of them load, your ranking signals are split between duplicates. Pick one version and 301-redirect everything else to it.
- Force HTTPS everywhere and renew the SSL certificate before it expires, an expired certificate scares visitors away with a browser warning.
- Choose www or non-www and redirect the other.
- Be consistent about trailing slashes, and make sure your canonical tags, sitemap and internal links all use the same final URL (not one that redirects).
- Add a canonical tag to every page pointing at its own preferred URL.
3. Core Web Vitals: speed that Google measures
Google measures real-user experience with three Core Web Vitals, judged at the 75th percentile of visits, meaning three out of four visitors need a good experience, not just you on your fast laptop.
| Metric | What it measures | Good | Common culprit on Nepali sites |
|---|---|---|---|
| LCP, Largest Contentful Paint | How fast the main content appears | ≤ 2.5 s | Huge uncompressed hero images and sliders |
| INP, Interaction to Next Paint | How quickly the page responds to taps | ≤ 200 ms | Heavy page builders, chat widgets and too many plugins |
| CLS, Cumulative Layout Shift | How much the layout jumps while loading | ≤ 0.1 | Images and ads without set dimensions |
INP replaced the older First Input Delay metric in 2024, so if you read an older guide that talks about FID, that advice is out of date.
- Images first: resize to the size they're shown at, compress, and serve WebP or AVIF. This alone often halves load time.
- Lazy-load images below the fold, but never the main image at the top.
- Cut third-party scripts. Every chat widget, tracking pixel and social embed costs time on slow connections. Keep what you actually use.
- Use a CDN and caching so visitors aren't downloading everything from one distant server.
- Check field data (from real users) in Search Console's Core Web Vitals report, not just a one-off lab test.
4. Mobile-first, for real
Google now crawls and evaluates sites using the smartphone version. If your mobile layout hides content, cuts sections or loads a stripped-down page, that's the version that ranks.
- Same content and headings on mobile as on desktop.
- Tap targets (buttons, links) large enough and not crammed together.
- No pop-ups that cover the content as soon as the page opens.
- Text readable without zooming.
5. Structured data
Structured data (schema markup) is a small block of code that tells search engines exactly what a page is about, a business, a product, an article, a FAQ. It doesn't guarantee rich results, but it removes guesswork.
- LocalBusiness (or a more specific type like Dentist or TravelAgency) with your name, address, phone and opening hours.
- Product with price and availability for online shops, useful for stores taking eSewa, Khalti or card payments.
- Article and BreadcrumbList for blogs and deeper pages.
- Validate everything with Google's Rich Results Test before going live.
6. Site structure and internal links
- Every important page reachable within three clicks of the homepage.
- Clean, readable URLs: /services/dental-implants/ rather than /page?id=4821.
- Descriptive link text ("see our implant prices") instead of "click here".
- One clear H1 per page, followed by a logical H2/H3 outline.
- Services
- Each service page
- Blog
- Each post
- About
- Contact
7. Multilingual sites: English and Nepali
If you publish both English and Nepali versions of pages, give each language its own URL (for example /en/ and /ne/), link them with hreflang tags, and never auto-redirect visitors based on their location, let them choose. Machine-translated Nepali that nobody has read is worse than no Nepali page at all.
What I actually find on real audits
Most problems are not exotic. They are small mistakes that a template repeats on every page:
- NP Movers (Perth): a template bug repeated the destination in the H1 of all 30 route pages ("Perth to Geraldton Geraldton"), and suburb pages repeated the same alt text six times. Neither showed up unless someone looked at the page source. Full story in the NP Movers case study.
- Lunera (Kathmandu, owned by my sister): all 53 product listings had Merchant schema errors, and every category page carried 44 Product items it should not have had. See the Lunera case study.
- Awesome Mate Removals (Perth): six duplicate AggregateRating blocks on each page were stopping review stars from showing in search. See the Awesome Mate Removals case study.
In each case the fix was made once, in the template, and checked in Search Console afterwards.
Five-minute crawl check
- Open Search Console, then Page indexing, and list the reasons pages are not indexed.
- Run URL Inspection on your three most important pages and read the indexing and canonical result.
- Open robots.txt and check that CSS, JavaScript and your key folders are not blocked, including by any CDN or firewall.
- View the source of one page per template and read the H1, title, alt text and structured data for repeated words.
- Test the page on a phone using mobile data, not office broadband.
Three habits that waste time
- Worrying about crawl budget on a small site. Google says it matters for very large, frequently updated sites, roughly one million pages changing weekly or ten thousand changing daily, or many URLs stuck in Discovered, currently not indexed.
- Fixing heading order for ranking. Heading order does not matter to Google Search. It matters for screen readers, so fix it as an accessibility task.
- Adding llms.txt as an AI fix. Google Search ignores it. See the llms.txt post.
For a real example of a template fault, see how a template bug hid on 30 pages, and for AI crawler settings see the robots.txt guide for AI bots.
The quick checklist
| Check | Tool |
|---|---|
| Pages indexed, no accidental noindex | Search Console → Pages |
| robots.txt not blocking CSS/JS | yoursite.com/robots.txt |
| One version of each URL, HTTPS forced | Browser + redirect checker |
| Sitemap lists only live canonical URLs | Search Console → Sitemaps |
| LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1 | PageSpeed Insights / CWV report |
| Mobile layout complete and usable | Your own phone, on mobile data |
| Structured data valid | Rich Results Test |
| No broken internal links | Any site crawler |
If this list looks long, start at the top, crawling and indexing problems undo everything else. Or let me run the whole audit for you: technical SEO services.
