You just paid someone to build you a website. It looks good on your phone. Your logo is crisp, the colors match your brand, and your nephew who “knows computers” said it looks professional. Six months later, it’s nowhere on Google.

This happens to Nepal businesses constantly, and it’s rarely a design problem. It’s a technical one — and the frustrating part is that most owners never find out, because nobody explains technical SEO in a way that doesn’t require a computer science degree.

This guide is that explanation. No jargon for its own sake. Just what technical SEO actually is, a health check you can run yourself in ten minutes with zero coding knowledge, and the exact list to hand your developer or agency so this stops being invisible to you.

What Technical SEO Actually Means

Every other kind of SEO assumes Google can already see your website properly. Technical SEO is the layer underneath that assumption — whether Google’s crawler can actually reach your pages, read them correctly, and load them fast enough to bother trying.

Think of it like a building inspection versus interior design. On-page SEO is choosing good furniture and paint. Technical SEO is whether the foundation is solid, the wiring works, and the front door actually opens. You can have the best furniture in the country — it doesn’t matter if nobody can get through the door.

This is also the part of SEO you’re least equipped to judge just by looking at your own site, because a technically broken website can still look completely fine to you and your customers. The problems live in code you never see.

The 10-Minute Technical Health Check Anyone Can Run

You don’t need to hire anyone to get a first read on your site’s technical health. These are free tools, and none of them require touching code.

1. Google PageSpeed Insights. Go to pagespeed.web.dev, paste your homepage URL, and run it. You’ll get a score out of 100 for both mobile and desktop, plus specific flagged issues. Anything consistently below 50 on mobile is a real problem, not a nitpick — since I moved this site to Astro, bimalrp.com scores 91 on mobile Performance and 100 on SEO, and that gap is the difference between a site Google is happy to rank and one it’s actively working against.

2. Google Search Console. If you haven’t set this up, do it today — it’s free and it’s the single most honest source of data about how Google actually sees your site. Under “Pages,” it tells you exactly how many of your pages are indexed versus excluded, and why.

3. The Mobile-Friendly check. Search Console’s “Mobile Usability” report flags specific pages with tap targets too close together, text too small to read, or content wider than the screen. In Nepal, mobile is where the overwhelming majority of your traffic already lives, so this isn’t optional polish.

4. Look at your own robots.txt. Type your domain followed by /robots.txt into your browser. If it’s blank or missing, that’s usually fine. If it contains a line like Disallow: /, your entire site is telling Google not to crawl it — a single misplaced line can take your whole business invisible.

5. Check your sitemap exists. Try yourdomain.com/sitemap.xml. If it 404s, search engines are relying purely on finding your pages through links, which is slower and less reliable.

If two or more of these come back bad, you have a technical SEO problem worth fixing before you spend another rupee on content or ads.

The Nepal-Specific Problem: Cheap Hosting and Bloated WordPress

Most technical SEO guides are written for a generic global audience. Here’s the part that’s specific to what I actually see running WP Tracer and consulting across Nepal’s market.

Shared hosting with no caching. A huge share of Nepal business websites sit on the cheapest shared hosting plan available, with no page caching layer. Every visitor triggers a fresh database query. This alone can double or triple load time, and it compounds badly the moment you get a traffic spike — like the exact moment a Dashain campaign starts working.

Plugin bloat. WordPress makes it dangerously easy to install a plugin for every small feature — a slider here, a popup there, three different SEO plugins because nobody removed the old ones. Each one adds its own scripts and stylesheets that your page has to load, whether or not the visitor ever uses that feature.

Unoptimized images straight from a phone camera. A 4MB photo uploaded directly, displayed at a fraction of its actual size, is one of the single most common speed problems I see on Nepal business sites. Compress before you upload, or use a plugin that does it automatically — this alone fixes a meaningful share of speed complaints.

No HTTPS, or HTTPS done inconsistently. Google has treated HTTPS as a baseline trust signal for years now, and an inconsistent setup — some pages loading over HTTP, mixed content warnings, or a certificate that’s expired — actively damages both rankings and visitor trust. Browsers now show an explicit “Not Secure” warning for HTTP pages, which is its own conversion killer.

Core Web Vitals, in Plain Language

Google measures three specific things about how your page feels to actually use, grouped under “Core Web Vitals.” You don’t need the technical definitions, just what each one means for a real visitor:

How fast the main content appears. If someone taps your link and stares at a blank or half-loaded screen for several seconds, this is failing — and on Nepal’s mobile data speeds, this is where a lot of sites lose people before they ever see anything.

How fast the page responds when tapped. A visitor taps “Add to Cart” and nothing happens for a second or two, so they tap again, and now they’ve added it twice, or given up. This usually comes from too much JavaScript loading and running before the page is actually interactive.

Whether the layout jumps around while loading. You go to tap a button, an ad or image loads above it and shifts everything down, and you accidentally tap the wrong thing. This is one of the more annoying, and more fixable, technical issues — it usually just means images and ad slots need a reserved size set in advance.

All three are measurable, reportable, and something a competent developer can genuinely fix — they’re not vague “make it feel faster” requests.

What to Ask Your Developer or Agency

If you’re not building the site yourself, here’s exactly what to put in front of whoever is — as an explicit requirement, not an assumption they’ll figure it out on their own.

  • A caching layer configured from launch, not added later as an afterthought
  • Images compressed and served in modern formats (WebP), not raw camera or phone uploads
  • An auto-generating XML sitemap, submitted to Search Console
  • A correctly configured robots.txt, checked before launch, not after
  • HTTPS enforced site-wide, with automatic redirects from HTTP
  • One canonical version of every URL — pick either www or non-www, and redirect the other, so Google never sees the same page as two different URLs
  • A Core Web Vitals check on the actual staging site before it goes live, not as a post-launch surprise
  • Clean redirects for any old URLs, so nothing 404s when you migrate or restructure

I moved bimalrp.com off WordPress specifically because every one of these had to be deliberately built rather than toggled in a plugin settings panel — I’ve written about that trade-off in more depth here if you’re weighing the same decision for your own business.

When to DIY and When to Bring in a Specialist

The health check above, a good caching plugin (WP Rocket or LiteSpeed Cache if you’re on WordPress), and image compression are genuinely within reach for a non-technical owner with an afternoon to spend.

Structural problems — a site architecture that confuses crawlers, JavaScript-heavy pages Google can’t read properly, a botched migration, or Core Web Vitals that won’t move no matter what plugin you install — are where it’s worth paying for a proper technical audit rather than guessing. The cost of staying invisible to Google usually outweighs the cost of the audit within the first month of it actually working.

Frequently Asked Questions

What is technical SEO, in one sentence?

Technical SEO is making sure search engines can actually crawl, read, and quickly load your website — the infrastructure layer underneath your content and keywords, without which nothing else you do for SEO can fully work.

Can I do technical SEO myself without hiring a developer?

The basics — running a PageSpeed check, setting up Search Console, compressing images, installing a caching plugin — are genuinely doable yourself. Structural fixes involving site architecture, crawlability, or a broken migration are worth bringing in a specialist for.

How is technical SEO different from on-page SEO?

Technical SEO is about whether Google can access and load your site properly. On-page SEO is about how well each individual page communicates what it’s about — titles, headings, content quality. See the full on-page SEO checklist for that layer in detail.

Does website speed actually affect Google rankings in Nepal?

Yes, directly through Core Web Vitals as a ranking signal, and indirectly through user behavior — a slow site loses visitors before they ever see your content, which shows up as poor engagement signals regardless of ranking position.

Why is my website not showing up on Google at all?

The most common causes are a robots.txt file accidentally blocking crawlers, a missing or broken sitemap, a site too new to be indexed yet, or a technical error preventing Google from rendering the page properly. Check Search Console’s “Pages” report first — it tells you the specific reason.

Is shared hosting bad for SEO?

Not automatically, but cheap shared hosting with no caching and slow server response time is one of the most common technical SEO problems I see on Nepal business websites. If your PageSpeed score is consistently poor, hosting is one of the first things worth investigating.

How often should I run a technical SEO check?

At minimum, after any major change — a redesign, a migration, a new plugin — and as a routine check every few months even without changes, since plugin updates and content growth can quietly introduce new issues over time.

Getting the technical foundation right is the unglamorous work that makes everything else you do for SEO actually count.

Talk to Bimal About Your SEO Strategy →

Related reading: