Technical SEO Audit: A Step-by-Step Tutorial Anyone Can Follow
A technical SEO audit is the process of examining your website's infrastructure to identify issues that prevent search engines from properly crawling, indexing, and ranking your pages. Many website owners in Nepal skip this step entirely, focusing only on content and keywords while their sites have fundamental technical problems that no amount of content can overcome. Slow page speeds, broken links, missing meta tags, crawl errors, and mobile usability issues silently destroy your rankings. This tutorial walks you through a complete technical SEO audit using mostly free tools, with clear instructions that anyone can follow regardless of technical background. By the end, you will have a prioritized list of fixes that can immediately improve your site's search performance.
What Tools Do You Need for a Technical SEO Audit?
You need Google Search Console (free), Google PageSpeed Insights (free), Screaming Frog SEO Spider (free for up to 500 URLs), and a mobile-friendly testing tool to conduct a comprehensive audit. These free tools cover 90% of what premium tools offer.
Essential Free Tools
| Tool | What It Checks | Cost | Setup Time |
|---|---|---|---|
| Google Search Console | Indexation, crawl errors, search performance | Free | 10 minutes |
| Google PageSpeed Insights | Page speed, Core Web Vitals | Free | No setup |
| Screaming Frog SEO Spider | Full site crawl, broken links, meta tags | Free (500 URLs) | 5 minutes |
| Google Mobile-Friendly Test | Mobile usability | Free | No setup |
| Google Rich Results Test | Schema/structured data validation | Free | No setup |
| Chrome DevTools | Network performance, rendering | Free (built into Chrome) | No setup |
Optional Premium Tools
| Tool | Additional Value | Cost |
|---|---|---|
| Ahrefs Site Audit | Comprehensive audit with prioritized issues | $99+/month |
| SEMrush Site Audit | Detailed crawl with health score | $119+/month |
| Screaming Frog (paid) | Unlimited URL crawling | $259/year |
| GTmetrix | Detailed performance analysis | Free tier available |
Setting Up Google Search Console
If you have not set up Search Console yet, do this first:
- Go to search.google.com/search-console
- Add your property (enter your website URL)
- Verify ownership (HTML tag method is easiest)
- Wait 24-48 hours for data to populate
Search Console is the single most important SEO tool. It shows you exactly how Google sees your website.
How Do You Check Crawlability and Indexation?
Check crawlability by reviewing your robots.txt file, XML sitemap, and Google Search Console's index coverage report to ensure Google can find and index all important pages on your site. Crawl issues are the most critical technical SEO problems because if Google cannot crawl your pages, nothing else matters.
Step 1: Check robots.txt
Your robots.txt file tells search engines which pages they can and cannot crawl. Access it by typing your domain followed by /robots.txt:
https://yourwebsite.com/robots.txt
What to look for:
# Good robots.txt
User-agent: *
Allow: /
Disallow: /admin/
Disallow: /wp-admin/
Disallow: /cart/
Sitemap: https://yourwebsite.com/sitemap.xml
# Bad robots.txt (blocks everything!)
User-agent: *
Disallow: /
Common mistakes:
- Accidentally blocking important pages or entire directories
- Blocking CSS or JavaScript files (prevents Google from rendering your pages)
- Not including sitemap location
- Having no robots.txt at all (not critical but not ideal)
Step 2: Check XML Sitemap
Your sitemap helps Google discover all your important pages. Check it at:
https://yourwebsite.com/sitemap.xml
Sitemap audit checklist:
- Does the sitemap exist?
- Is it submitted in Google Search Console?
- Does it include all important pages?
- Does it exclude pages you do not want indexed (admin, thank-you pages)?
- Are the URLs in the sitemap returning 200 status codes (not 404 or redirects)?
- Is the sitemap under the 50,000 URL / 50MB limit?
Step 3: Check Index Coverage in Search Console
Navigate to Search Console > Pages (formerly Index Coverage):
| Status | What It Means | Action |
|---|---|---|
| Valid | Page is indexed | Good, no action needed |
| Valid with warnings | Indexed but has issues | Review and fix warnings |
| Excluded | Not indexed (intentionally or not) | Check if important pages are excluded |
| Error | Cannot be indexed | Fix immediately |
Critical errors to fix immediately:
- "Submitted URL has crawl issue" – Google cannot access the page
- "Submitted URL returns 404" – Page does not exist
- "Server error (5xx)" – Server is failing
- "Redirect error" – Redirect chains or loops
Step 4: Use Site Search to Check Indexation
In Google, search:
site:yourwebsite.com
This shows all pages Google has indexed. Compare this count to the number of pages you expect to be indexed. Major discrepancies indicate problems.
How Do You Audit Page Speed and Core Web Vitals?
Use Google PageSpeed Insights to test each key page, focusing on three Core Web Vitals metrics: LCP (largest content load time under 2.5 seconds), INP (interaction response under 200 milliseconds), and CLS (visual stability score under 0.1). Page speed directly impacts both rankings and user experience.
Running a Page Speed Test
Go to pagespeed.web.dev and enter your URL. Test at minimum:
- Homepage
- A key product or service page
- A blog post
- Contact page
Understanding Core Web Vitals
| Metric | What It Measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed of main content | < 2.5s | 2.5-4.0s | > 4.0s |
| INP (Interaction to Next Paint) | Response to user interactions | < 200ms | 200-500ms | > 500ms |
| CLS (Cumulative Layout Shift) | Visual stability | < 0.1 | 0.1-0.25 | > 0.25 |
Common Speed Issues and Fixes
Issue 1: Large Images
The most common speed problem, especially for Nepali websites:
Before: hero-image.jpg (2.5 MB, 4000x3000 pixels)
After: hero-image.webp (150 KB, 1200x800 pixels)
Fix:
1. Resize images to the maximum display size needed
2. Convert to WebP format (80% smaller than JPEG)
3. Use lazy loading for images below the fold
4. Add width and height attributes to prevent layout shift
<!-- Optimized image implementation -->
<img
src="hero-image.webp"
alt="Swift Academy training session in Pokhara"
width="1200"
height="800"
loading="lazy"
decoding="async"
/>
Issue 2: Render-Blocking Resources
<!-- Bad: Blocks rendering -->
<link rel="stylesheet" href="large-library.css">
<script src="analytics.js"></script>
<!-- Better: Non-blocking loading -->
<link rel="stylesheet" href="critical.css">
<link rel="preload" href="large-library.css" as="style" onload="this.rel='stylesheet'">
<script src="analytics.js" defer></script>
Issue 3: No Browser Caching
# Add to .htaccess for Apache servers
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/webp "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"
</IfModule>
Issue 4: No Content Delivery Network (CDN)
For Nepali websites serving local audiences, a CDN may seem unnecessary. However, even for local sites, a free CDN like Cloudflare improves speed through caching and optimization.
Speed Optimization Priority List
| Fix | Impact | Difficulty | Time |
|---|---|---|---|
| Optimize images | High | Easy | 1-2 hours |
| Enable compression (gzip) | High | Easy | 30 minutes |
| Add browser caching | Medium | Easy | 30 minutes |
| Defer non-critical JS/CSS | High | Medium | 1-2 hours |
| Use a CDN | Medium | Easy | 1 hour |
| Minimize CSS/JS | Medium | Medium | 1-2 hours |
| Optimize fonts | Low-Medium | Easy | 30 minutes |
How Do You Audit Mobile-Friendliness?
Test your site using Google's Mobile-Friendly Test tool and manually browse every key page on a mobile phone, checking for text readability without zooming, tap targets that are not too small or too close, and content that does not overflow the screen. Over 70% of web traffic in Nepal comes from mobile devices.
Google's Mobile-Friendly Test
Go to search.google.com/test/mobile-friendly and enter your URL. The tool will flag specific issues.
Manual Mobile Audit Checklist
Open your website on a smartphone and check each item:
Text and Readability:
- Text is readable without zooming
- Font size is at least 16px for body text
- Line spacing is comfortable (1.5-1.8)
- Paragraphs are short (2-3 sentences for mobile)
Navigation:
- Menu is accessible and functional on mobile
- Hamburger menu opens and closes properly
- Navigation links are large enough to tap easily
- Search function works on mobile
Tap Targets:
- Buttons are at least 48×48 pixels
- Links have adequate spacing (not touching each other)
- Form inputs are easy to tap and type into
- Phone numbers are clickable (tel: links)
Content Display:
- Images scale properly (not overflowing)
- Tables are scrollable or responsive
- Videos are responsive
- No horizontal scrolling required
- Pop-ups are mobile-friendly or disabled on mobile
Performance on Mobile:
- Pages load within 3 seconds on 4G
- Interactive elements respond quickly
- No content layout shifts during loading
Common Mobile Issues for Nepali Websites
Many Nepali websites were designed desktop-first without proper mobile optimization:
| Issue | Impact | Fix |
|---|---|---|
| Non-responsive design | Critical | Use CSS media queries or responsive framework |
| Tiny text on mobile | High | Set base font size to 16px minimum |
| Unoptimized images | High | Serve appropriately sized images for mobile |
| Flash content | Critical | Remove Flash, use HTML5 |
| Intrusive pop-ups | High | Disable or minimize pop-ups on mobile |
| Fixed-width tables | Medium | Make tables scrollable or responsive |
How Do You Audit On-Page SEO Elements?
Crawl your site with Screaming Frog to systematically check every page's title tag, meta description, heading structure, image alt text, and URL structure for issues like missing tags, duplicates, or length violations. Screaming Frog automates what would take hours to check manually.
Running a Screaming Frog Crawl
- Download Screaming Frog (free version crawls up to 500 URLs)
- Enter your website URL and click "Start"
- Wait for the crawl to complete
- Review each tab for issues
Title Tag Audit
Filter the "Page Titles" tab for issues:
| Issue | What to Look For | Fix |
|---|---|---|
| Missing title | Pages with no title tag | Add unique, keyword-rich title |
| Duplicate titles | Multiple pages with same title | Make each page's title unique |
| Too long | Over 60 characters | Shorten to under 60 characters |
| Too short | Under 30 characters | Add more descriptive text |
| Missing keyword | Target keyword not in title | Include primary keyword naturally |
<!-- Good title tag examples -->
<title>Flutter Course in Pokhara | Swift Academy Nepal</title>
<title>Best Django Training Pokhara - Learn Python Django</title>
<!-- Bad title tags -->
<title>Home</title> <!-- Too vague -->
<title>Welcome to Our Website - The Best Website for All Your Needs</title> <!-- Too long, no keywords -->
Meta Description Audit
| Issue | Criteria | Fix |
|---|---|---|
| Missing | No meta description | Write 150-160 character description |
| Duplicate | Same description on multiple pages | Make each unique |
| Too long | Over 160 characters | Trim to 150-160 characters |
| Too short | Under 70 characters | Expand with compelling description |
| No call-to-action | Description does not encourage click | Add action-oriented text |
Heading Structure Audit
Every page should have:
- Exactly one H1 tag containing the primary keyword
- Logical H2-H6 hierarchy (no skipping levels)
- No empty heading tags
- No duplicate H1 tags on the same page
<!-- Correct heading structure -->
<h1>Flutter Development Course in Pokhara</h1>
<h2>What You Will Learn</h2>
<h3>Dart Programming Fundamentals</h3>
<h3>Flutter Widget Architecture</h3>
<h2>Course Schedule and Pricing</h2>
<h2>Student Success Stories</h2>
<!-- Incorrect: Skipping levels, multiple H1s -->
<h1>Our Courses</h1>
<h1>Flutter Course</h1> <!-- Second H1 - wrong -->
<h4>Details</h4> <!-- Skipped H2 and H3 - wrong -->
Image Alt Text Audit
Screaming Frog's "Images" tab shows images missing alt text:
<!-- Good alt text -->
<img src="classroom.jpg" alt="Students learning Flutter development at Swift Academy Pokhara">
<!-- Bad alt text -->
<img src="classroom.jpg" alt=""> <!-- Empty -->
<img src="classroom.jpg" alt="image"> <!-- Non-descriptive -->
<img src="classroom.jpg"> <!-- Missing entirely -->
How Do You Check for Broken Links and Redirect Issues?
Use Screaming Frog to identify all 404 (broken) links, redirect chains (3+ hops), and redirect loops on your site, then fix them by updating link targets, implementing proper 301 redirects, or removing dead links. Broken links waste crawl budget and harm user experience.
Finding Broken Links
In Screaming Frog, filter "Response Codes" tab by:
- 4xx errors: Pages that do not exist (404 Not Found)
- 5xx errors: Server errors
- 3xx redirects: Pages that redirect (check for chains)
Fixing Common Issues
404 Errors (Broken Links):
- If the page moved, create a 301 redirect to the new URL
- If the page was deleted intentionally, update all internal links pointing to it
- If it is an external link, either update to a working URL or remove it
Redirect Chains:
Bad: Page A → Page B → Page C → Page D (3 redirects)
Good: Page A → Page D (direct redirect)
Every redirect in a chain adds load time and wastes crawl budget. Fix chains by pointing all redirects directly to the final destination.
Redirect Loops:
Broken: Page A → Page B → Page A (infinite loop)
Fix: Remove one redirect so there is a clear destination
Redirect Implementation
# .htaccess (Apache)
Redirect 301 /old-page/ https://yourwebsite.com/new-page/
# For WordPress, use a plugin like Redirection
# For Nginx
server {
rewrite ^/old-page/$ /new-page/ permanent;
}
Internal Link Audit
While checking broken links, also audit your internal linking:
- Are important pages linked from the homepage?
- Do related pages link to each other?
- Are there orphan pages (no internal links pointing to them)?
- Is anchor text descriptive and relevant?
How Do You Audit Structured Data and Schema Markup?
Test your structured data using Google's Rich Results Test, verify that your schema types match your content type (LocalBusiness, Article, FAQ, Product), and ensure all required properties are present without errors. Schema markup helps Google display rich results for your pages.
What Schema Types Your Site Should Have
| Page Type | Recommended Schema | Benefit |
|---|---|---|
| Homepage | Organization, LocalBusiness | Business info in search |
| Blog posts | Article, FAQPage | Rich snippets, FAQ display |
| Product pages | Product | Price, availability in search |
| Course pages | Course | Course info in search |
| Contact page | LocalBusiness | Address, phone in search |
| FAQ page | FAQPage | Expandable FAQ in search |
Testing Your Schema
- Go to search.google.com/test/rich-results
- Enter your page URL
- Review results for errors and warnings
Implementing Basic Schema
<!-- LocalBusiness schema for a Pokhara training institute -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "EducationalOrganization",
"name": "Swift Academy",
"description": "IT training institute in Pokhara offering courses in Flutter, Next.js, Django, Laravel, Digital Marketing, SEO, and Generative AI",
"url": "https://swiftacademy.com.np",
"address": {
"@type": "PostalAddress",
"addressLocality": "Pokhara",
"addressRegion": "Gandaki",
"addressCountry": "NP"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "28.2096",
"longitude": "83.9856"
},
"sameAs": [
"https://facebook.com/swiftacademy",
"https://instagram.com/swiftacademy"
]
}
</script>
<!-- FAQ schema for blog posts -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does the Flutter course take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The Flutter course at Swift Academy takes 3 months with classes held 5 days per week."
}
}
]
}
</script>
What Reddit and SEO Communities Recommend for Technical Audits
Community insights from r/SEO, r/TechSEO, and professional SEO forums:
-
"Do the basics first. 80% of technical SEO improvements come from fixing page speed, broken links, and missing meta tags. You do not need expensive tools for that" – Consistent advice from experienced SEOs.
-
"Google Search Console is the most underused free tool. Most site owners set it up and never check it. Make it a weekly habit" – Regular Search Console monitoring catches issues early.
-
"Screaming Frog free version is enough for most Nepali websites. If your site has fewer than 500 pages, you do not need the paid version" – Practical advice for smaller sites.
-
"Do not fix everything at once. Prioritize by impact: crawlability issues first, then speed, then on-page elements. Otherwise you get overwhelmed and fix nothing" – Prioritization is key.
-
"Run an audit quarterly. Technical issues creep in as you add content, change designs, and update plugins. One-time audits are not enough" – Regular auditing prevents issue accumulation.
Practical Takeaway: Your Technical SEO Audit Checklist
Use this checklist for your next audit. Address issues in priority order:
Priority 1: Crawlability (Fix First)
- robots.txt is not blocking important pages
- XML sitemap exists and is submitted to Search Console
- No critical crawl errors in Search Console
- Important pages are indexed (check with site: search)
Priority 2: Page Speed
- All key pages score 50+ on PageSpeed Insights (aim for 80+)
- Core Web Vitals pass (LCP < 2.5s, INP < 200ms, CLS < 0.1)
- Images are optimized (WebP format, compressed, lazy loaded)
- Browser caching is enabled
Priority 3: Mobile Usability
- All pages pass Google Mobile-Friendly Test
- Text is readable without zooming
- Tap targets are adequately sized and spaced
- No horizontal scrolling required
Priority 4: On-Page Elements
- Every page has a unique title tag (under 60 characters)
- Every page has a unique meta description (150-160 characters)
- Every page has exactly one H1 tag
- All images have descriptive alt text
- URLs are clean and descriptive
Priority 5: Links and Redirects
- No broken internal links (404s)
- No redirect chains or loops
- Important pages have internal links pointing to them
- All redirects are 301 (permanent), not 302
Priority 6: Structured Data
- Schema markup is present on key pages
- Rich Results Test shows no errors
- LocalBusiness schema on homepage (for local businesses)
- Article schema on blog posts
Frequently Asked Questions
How often should I run a technical SEO audit?
Run a comprehensive audit quarterly (every 3 months). Between full audits, check Google Search Console weekly for new crawl errors or indexation issues. After major website changes (redesign, migration, new CMS), run an immediate audit. Regular monitoring prevents small issues from becoming major problems.
Can I do a technical SEO audit without any technical knowledge?
Yes. This tutorial is designed for non-technical users. Google Search Console and PageSpeed Insights require no technical skills, just follow the interface. Screaming Frog may feel technical initially but becomes intuitive quickly. For implementing fixes, you may need a web developer's help, but identifying the issues is something anyone can do.
How much does a professional technical SEO audit cost in Nepal?
Professional SEO audits in Nepal range from NPR 10,000-50,000 for small websites to NPR 50,000-200,000 for large e-commerce or enterprise sites. Many digital marketing agencies in Pokhara and Kathmandu offer audit services. Learning to do it yourself using this tutorial saves money and gives you ongoing capability.
What is the most impactful technical SEO fix?
Page speed optimization typically delivers the most immediate and measurable impact. Specifically, image optimization (converting to WebP, compressing, lazy loading) often improves page speed scores by 20-40 points and directly reduces bounce rates. It is also one of the easiest fixes to implement.
Does fixing technical SEO issues guarantee higher rankings?
Fixing technical issues removes barriers to ranking but does not guarantee top positions. Think of technical SEO as the foundation: you cannot rank well with a broken foundation, but the foundation alone is not enough. You also need quality content, relevant keywords, and backlinks. Technical SEO ensures your other efforts are not wasted.
Learn Technical SEO at Swift Academy
Swift Academy in Pokhara offers hands-on SEO Training that includes comprehensive technical SEO auditing. Learn to use professional tools, identify and fix issues, and optimize websites for search engines. Our course covers both the theory and practical application of SEO for Nepal's market.
Explore our SEO Training course and master the technical skills that set professional SEOs apart.
Related Articles
- SEO Career in Nepal 2026: Salary, Skills, and Growth Opportunities
- Content Marketing for Nepali Startups: How to Get Customers Without Spending on Ads
- Social Media Marketing Strategy for Small Businesses in Pokhara: A Local Guide
Suggested Images
- Hero Image: Screenshot-style graphic showing a technical SEO audit dashboard with checkmarks and warning indicators — "technical-seo-audit-dashboard.png"
- Checklist Infographic: Visual checklist of the 6-priority audit framework with icons and status indicators — "technical-seo-audit-checklist-infographic.png"
- Speed Comparison: Before-and-after PageSpeed Insights scores showing the impact of optimization — "page-speed-before-after-optimization.png"
