April 12, 2026
8 min read
Table of Contents
By Kokil Thapa | Last reviewed: April 2026
You can write the best content and build the most relevant backlinks — but if Google cannot crawl, index, and render your pages correctly, none of it matters. Technical SEO is the infrastructure layer that makes everything else work. After auditing hundreds of Nepal-based websites, I consistently find the same technical issues: broken sitemaps, orphan pages, duplicate content, slow servers, and missing schema markup. As a web developer in Nepal and SEO specialist, I am sharing the exact technical SEO audit checklist I use on every client project in 2026 AD (2083 BS).
Quick answer: A technical SEO audit examines how well search engines can crawl, index, and render your website. It covers site architecture, crawlability, page speed, mobile responsiveness, schema markup, HTTPS security, and indexing issues — the foundation that determines whether your content can rank.
What Is a Technical SEO Audit?
Technical SEO is everything that happens between your server and the search engine crawler. Unlike on-page SEO (content, keywords) or off-page SEO (backlinks), technical SEO focuses on the infrastructure: how your site is structured, how fast it loads, whether pages are accessible, and whether search engines can understand your content.
A technical audit identifies and prioritizes issues that prevent your site from ranking at its full potential. Here is the complete checklist organized by priority.
Crawlability and Indexing Audit
1. Robots.txt Analysis
Your robots.txt file (at yoursite.com/robots.txt) tells search engines which pages to crawl and which to skip. Common issues on Nepal websites:
- Blocking important pages — accidentally blocking CSS, JavaScript, or image directories prevents Google from rendering your pages correctly
- Missing robots.txt — without it, Google crawls everything including admin pages and duplicate parameter URLs
- Blocking the entire site —
Disallow: /blocks all crawling. This happens more often than you would think during development-to-production migrations.
What to check:
# Correct robots.txt example User-agent: * Disallow: /admin/ Disallow: /api/ Disallow: /storage/ Allow: / Sitemap: https://yoursite.com/sitemap.xml2. XML Sitemap Audit
Your XML sitemap tells Google which pages exist and when they were last updated. Audit these points:
- Sitemap exists and is accessible — check
yoursite.com/sitemap.xml - Submitted to Google Search Console — go to Indexing → Sitemaps and verify status
- No errors — all URLs in the sitemap should return 200 status codes, not 404 or 301
- Includes all important pages — blog posts, services, portfolio items, tool pages
- Excludes non-indexable pages — admin pages, search result pages, parameter URLs should not be in the sitemap
- lastmod dates are accurate — Google uses these to prioritize crawling updated content
3. Index Coverage Analysis
In Google Search Console, check the Indexing → Pages report for:
- Indexed pages — does the count match the number of pages you expect to be indexed?
- "Not indexed" reasons — Google lists specific reasons: "Crawled - currently not indexed," "Discovered - currently not indexed," "Excluded by noindex tag," etc.
- Duplicate content — "Duplicate without user-selected canonical" means Google found copies of your pages
- Soft 404s — pages that return 200 status but Google considers them error pages (thin content)
4. Canonical Tag Audit
Every indexable page should have a self-referencing canonical tag:
<link rel="canonical" href="https://yoursite.com/blog/your-article" />Common canonical issues:
- HTTP and HTTPS versions both accessible without canonical
- www and non-www duplicates
- Trailing slash inconsistencies (
/blog/vs/blog) - Parameter URLs creating duplicates (
/products?sort=price)
Site Architecture Audit
5. URL Structure
Clean, logical URLs help both users and search engines navigate your site:
- Use hyphens to separate words, never underscores or spaces
- Keep URLs under 75 characters
- Include primary keywords in the URL slug
- Maintain a flat hierarchy — every important page should be reachable within 3 clicks from the homepage
- Avoid dynamic parameters for user-facing URLs (
?id=123is worse than/blog/article-name)
6. Internal Linking Structure
Internal links distribute page authority and help Google discover new content. Audit for:
- Orphan pages — pages with no internal links pointing to them (Google may never find them)
- Deep pages — important pages buried 4+ clicks from homepage
- Link distribution — are your most important pages receiving the most internal links?
- Broken internal links — links pointing to 404 pages waste crawl budget and user trust
- Anchor text variety — using descriptive, keyword-rich anchor text instead of "click here"
Learn the detailed on-page SEO checklist for internal linking best practices.
7. Redirect Audit
Redirects are necessary when URLs change, but they cause problems when mismanaged:
- Redirect chains — A → B → C → D. Each hop adds latency. Maximum one redirect between any two pages.
- Redirect loops — A → B → A creates an infinite loop. Usually caused by misconfigured server rules.
- 302 vs 301 — use 301 (permanent) for moved content. 302 (temporary) does not pass full link equity.
- Mixed content redirects — HTTP to HTTPS redirects should be clean single-hop 301s
Page Speed and Performance Audit
8. Core Web Vitals
Google uses Core Web Vitals as a ranking signal. Test every important page:
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | < 2.5s | 2.5–4.0s | > 4.0s |
| INP (Interaction to Next Paint) | < 200ms | 200–500ms | > 500ms |
| CLS (Cumulative Layout Shift) | < 0.1 | 0.1–0.25 | > 0.25 |
Testing tools:
- Google PageSpeed Insights — lab and field data combined
- Chrome DevTools Lighthouse — detailed technical breakdown
- Google Search Console Core Web Vitals report — real user data for your entire site
- WebPageTest.org — advanced waterfall analysis
Nepal websites face unique speed challenges: shared hosting with high TTFB, unoptimized images on slow connections, and third-party scripts (chat widgets, analytics) blocking rendering. Read the detailed guide on how website speed impacts SEO in Nepal.
9. Server Performance
- TTFB (Time to First Byte) — should be under 200ms. Many Nepal-hosted sites exceed 2 seconds.
- Uptime — 99.9% minimum. Use monitoring tools like UptimeRobot to track.
- SSL/TLS — valid certificate, no mixed content warnings, HTTP/2 enabled
- Compression — GZIP or Brotli enabled for HTML, CSS, JavaScript
- Caching headers — static assets should have far-future cache expiry (1 year for versioned assets)
Consider professional speed optimization services if your site consistently fails Core Web Vitals.
Mobile and Rendering Audit
10. Mobile-First Indexing
Google indexes the mobile version of your site first. Ensure:
- All content visible on desktop is also visible on mobile (no hidden content)
- Structured data is present on the mobile version
- Images and videos are accessible on mobile
- No mobile-specific blocked resources in robots.txt
- Tap targets are at least 48px apart
- No interstitials or popups blocking content on mobile
11. JavaScript Rendering
If your site uses JavaScript frameworks (React, Vue, Angular), verify Google can render the content:
- Use Google Search Console's URL Inspection tool → "Test Live URL" → view rendered page
- Compare the rendered HTML with your source HTML — are dynamic elements visible?
- Check for JavaScript errors that prevent rendering
- Consider server-side rendering (SSR) for critical content pages
Security and HTTPS Audit
12. HTTPS Implementation
- All pages load over HTTPS — no HTTP pages remaining
- HTTP to HTTPS redirect is a single 301 hop
- No mixed content (HTTP resources loaded on HTTPS pages)
- SSL certificate is valid and not expiring soon
- HSTS (HTTP Strict Transport Security) header is set
13. Security Headers
Security headers protect users and signal site quality:
X-Content-Type-Options: nosniffX-Frame-Options: SAMEORIGINContent-Security-Policy— defines allowed sources for scripts, styles, imagesReferrer-Policy: strict-origin-when-cross-origin
Structured Data (Schema Markup) Audit
14. Schema Implementation
Validate schema markup on every page type:
| Page Type | Required Schema | Benefits |
|---|---|---|
| Homepage | Organization, WebSite, SearchAction | Sitelinks search box, brand panel |
| Blog posts | Article, FAQPage, BreadcrumbList | Rich results, FAQ dropdowns |
| Service pages | Service, LocalBusiness | Service-related rich results |
| Contact page | LocalBusiness, ContactPoint | Business info in search results |
| Product pages | Product, Review, AggregateRating | Star ratings, price in search results |
Validate using Google's Rich Results Test. Errors in schema markup can prevent rich results and trigger manual actions.
Technical SEO Audit Checklist (Quick Reference)
| # | Check | Tool | Status |
|---|---|---|---|
| 1 | Robots.txt is correct and not blocking important content | Browser / GSC | ☐ |
| 2 | XML sitemap submitted and error-free | GSC | ☐ |
| 3 | All important pages are indexed | GSC Coverage | ☐ |
| 4 | Canonical tags present and correct | Screaming Frog | ☐ |
| 5 | No orphan pages | Screaming Frog | ☐ |
| 6 | No broken internal links (404s) | Screaming Frog / Ahrefs | ☐ |
| 7 | No redirect chains or loops | Screaming Frog | ☐ |
| 8 | Core Web Vitals passing (LCP, INP, CLS) | PageSpeed Insights | ☐ |
| 9 | TTFB under 200ms | WebPageTest | ☐ |
| 10 | Mobile responsive with no issues | Mobile-Friendly Test | ☐ |
| 11 | HTTPS with no mixed content | Browser DevTools | ☐ |
| 12 | Schema markup validated | Rich Results Test | ☐ |
| 13 | No duplicate content issues | GSC / Screaming Frog | ☐ |
| 14 | Hreflang tags (if multilingual) | Screaming Frog | ☐ |
Free Tools for Technical SEO Audits
- Google Search Console — indexing issues, Core Web Vitals, mobile usability, manual actions
- Screaming Frog SEO Spider (free up to 500 URLs) — crawl your site for broken links, redirects, duplicates, missing meta tags
- Google PageSpeed Insights — performance scores with specific optimization recommendations
- Ahrefs Webmaster Tools (free) — site audit, backlink analysis, keyword tracking
- Chrome DevTools — Lighthouse audit, network waterfall, rendering analysis
- Rich Results Test — validate structured data markup
- Mobile-Friendly Test — verify mobile rendering
Run a technical SEO audit quarterly — or after any major site update, migration, or redesign. Technical debt accumulates silently and can erase months of content and link building effort. Combine this technical audit with the local SEO optimization guide for Nepal businesses targeting local search results.
Frequently Asked Questions
A technical SEO audit examines how well search engines can crawl, index, and render your website pages.
Run a technical SEO audit quarterly or after any major site update, migration, or redesign.
Both are essential. Technical SEO is the foundation that allows content to rank in search engines.
Slow server response time is the most common issue on Nepal websites. Many Nepal-hosted sites have Time to First Byte exceeding 2 seconds due to shared hosting on distant servers. This directly impacts Core Web Vitals scores and search rankings. Choose hosting with servers in Singapore or Mumbai for faster Nepal access.
Use Google Search Console's URL Inspection tool to test individual pages. Check the Indexing then Pages report for crawl errors and indexing issues. Verify your robots.txt file is not blocking important content. Submit your XML sitemap and monitor its status for errors in the Sitemaps section.
Core Web Vitals are three Google metrics measuring user experience. LCP or Largest Contentful Paint should be under 2.5 seconds for loading speed. INP or Interaction to Next Paint should be under 200 milliseconds for interactivity. CLS or Cumulative Layout Shift should be under 0.1 for visual stability.
A canonical tag tells Google which version of a page is the master copy when duplicates exist. Every indexable page needs a self-referencing canonical tag. Without canonicals, Google may index HTTP and HTTPS versions, www and non-www duplicates, or parameter variations separately, diluting your page's ranking power.
Use Screaming Frog SEO Spider to crawl your site and identify all pages returning 404 errors. It is free for up to 500 URLs. Either fix the broken pages by creating content at those URLs, or set up 301 redirects from broken URLs to relevant live pages. Also check Google Search Console for crawl errors.
Your robots.txt should allow crawling of all public content pages and block admin areas, API endpoints, and private directories. Always include your sitemap URL. Never block CSS, JavaScript, or image files as Google needs these to render your pages correctly. Test changes using Google Search Console's robots.txt tester.
Use Google's Rich Results Test to validate schema markup on any page. Enter your URL and the tool shows which schema types are detected, any errors or warnings, and whether the page is eligible for rich results. Fix all errors before expecting rich results to appear in search. Revalidate after any changes.
Redirect chains occur when multiple redirects happen in sequence like page A redirects to B which redirects to C. They are caused by accumulated URL changes over time without updating old redirects. Fix them by updating all redirects to point directly to the final destination URL in a single hop.
Yes, every Nepal website should have an XML sitemap submitted to Google Search Console. It tells Google which pages exist and when they were last updated. Include all important public pages and exclude admin pages, search results, and parameter URLs. Update the sitemap automatically whenever content changes.
Mobile-first indexing means Google primarily crawls and indexes the mobile version of your website. If your mobile version has less content, missing structured data, or blocked resources compared to desktop, your rankings will suffer. Ensure all content and technical elements are identical on both mobile and desktop versions.
Switch to hosting with servers in Singapore or Mumbai for faster Nepal access. Enable server-side caching, use a CDN like Cloudflare free tier, enable GZIP or Brotli compression, and optimize database queries. Upgrade from shared hosting to VPS if your current TTFB exceeds 500 milliseconds consistently.
Yes, free tools cover most technical SEO audit needs. Google Search Console provides indexing, crawling, and Core Web Vitals data. Screaming Frog is free for up to 500 URLs. Google PageSpeed Insights tests speed. Chrome DevTools Lighthouse runs full audits. Ahrefs Webmaster Tools provides free site audit capabilities.
-thumb.webp)
