freecourses.digital
Lesson progress: 0 of 3 activities done
All lessons in Technical SEO Auditing Lesson 1.3 of 84

Module 1: Introduction to Technical SEO Auditing

  1. 1.1What Is a Technical SEO Audit?
  2. 1.2Technical SEO Audit vs. General SEO Audit
  3. 1.3When Should You Audit a Website?
  4. 1.4Types of Technical SEO Issues
  5. 1.5Defining Audit Scope and Objectives

Module 2: Website Crawling and URL Discovery

  1. 2.1How SEO Crawlers Discover URLs
  2. 2.2Configuring a Website Crawl
  3. 2.3Crawl Scope, Limits, and Exclusions
  4. 2.4Internal Links and Crawl Depth
  5. 2.5Orphan Pages and URL Discovery
  6. 2.6Crawl Data vs. Search Engine Data
  7. 2.7Identifying Crawl Coverage Gaps

Module 3: HTTP Status Codes and Redirect Auditing

  1. 3.1Understanding HTTP Status Codes
  2. 3.2Finding 4xx Errors and Broken Links
  3. 3.3Identifying 5xx Server Errors
  4. 3.4Redirect Chains and Redirect Loops
  5. 3.5Internal Links to Redirected URLs
  6. 3.6301 vs. 302 Redirects
  7. 3.7Auditing 404 Pages and Soft 404s

Module 4: Crawlability and Indexability Auditing

  1. 4.1Crawling vs. Indexing
  2. 4.2Robots.txt Audit
  3. 4.3Meta Robots and X-Robots-Tag
  4. 4.4Noindex and Canonical Conflicts
  5. 4.5XML Sitemap Validation
  6. 4.6Canonical URL Auditing
  7. 4.7Identifying Indexability Conflicts
  8. 4.8Comparing Crawl Data with Google Search Console

Module 5: URL Structure and Duplicate Content Issues

  1. 5.1URL Structure and Normalization
  2. 5.2Duplicate URLs and Duplicate Pages
  3. 5.3HTTP vs. HTTPS and Hostname Variations
  4. 5.4Trailing Slashes and URL Parameters
  5. 5.5Pagination and Faceted Navigation
  6. 5.6Canonicalization Strategies
  7. 5.7Internal Linking to Preferred URLs

Module 6: Technical On-Page Auditing

  1. 6.1Missing and Duplicate Title Tags
  2. 6.2Missing and Duplicate Meta Descriptions
  3. 6.3Missing, Duplicate, and Multiple H1 Headings
  4. 6.4Heading Hierarchy and HTML Structure
  5. 6.5Missing Image Alt Attributes
  6. 6.6Internal Link and Anchor Text Issues
  7. 6.7Empty, Thin, and Near-Duplicate Pages
  8. 6.8Auditing HTML Metadata at Scale

Module 7: Website Performance and Core Web Vitals

  1. 7.1Core Web Vitals: LCP, INP, and CLS
  2. 7.2Lab Data vs. Field Data
  3. 7.3Identifying Slow Pages
  4. 7.4Image and Resource Optimization Opportunities
  5. 7.5JavaScript and CSS Performance
  6. 7.6Mobile Usability and Responsive Rendering
  7. 7.7Prioritizing Performance Fixes

Module 8: JavaScript SEO and Rendering

  1. 8.1How Search Engines Process JavaScript
  2. 8.2HTML Source vs. Rendered HTML
  3. 8.3Client-Side vs. Server-Side Rendering
  4. 8.4JavaScript-Generated Content and Links
  5. 8.5Rendering Failures and Missing Content
  6. 8.6Lazy Loading and Crawl Accessibility
  7. 8.7Diagnosing JavaScript SEO Problems

Module 9: Structured Data and Schema Auditing

  1. 9.1Structured Data and Schema.org Basics
  2. 9.2JSON-LD and Structured Data Formats
  3. 9.3Finding Structured Data Across a Website
  4. 9.4Detecting Invalid or Incomplete Markup
  5. 9.5Schema Validation and Rich Result Eligibility
  6. 9.6Conflicting or Duplicate Structured Data
  7. 9.7Prioritizing Schema Fixes

Module 10: Analyzing Audit Data and Prioritizing Issues

  1. 10.1Reading Crawl Reports and Exports
  2. 10.2Grouping URLs by Issue Type
  3. 10.3Identifying Root Causes vs. Symptoms
  4. 10.4Evaluating Severity, Impact, and Effort
  5. 10.5Separating Sitewide and Isolated Issues
  6. 10.6Identifying False Positives
  7. 10.7Building an Actionable Issue Register

Module 11: Technical SEO Audit Reporting

  1. 11.1Structuring a Technical SEO Audit Report
  2. 11.2Documenting Evidence and Affected URLs
  3. 11.3Writing Developer-Ready Recommendations
  4. 11.4Mapping Issues to Business and Search Impact
  5. 11.5Creating a Prioritized Remediation Roadmap
  6. 11.6Presenting Findings to Stakeholders
  7. 11.7Tracking Fixes and Ownership

Module 12: Fix Verification and Technical QA

  1. 12.1Re-Crawling After Fixes
  2. 12.2Comparing Before-and-After Crawl Results
  3. 12.3Verifying Redirects, Canonicals, and Indexability
  4. 12.4Detecting Regressions and Newly Introduced Issues
  5. 12.5Testing Website Changes Before Deployment
  6. 12.6Confirming Fixes with Search Console and Other Evidence
  7. 12.7Closing Audit Findings and Recording Results

When Should You Audit a Website?

Your roadmap for this lesson

  • The events that should trigger an immediate technical audit
  • How often to run full audits and lighter monthly checks
  • Warning signs in Google Search Console that something broke
  • How to build a simple audit calendar

Short answer

Audit a website before launch, after a redesign or migration, after major CMS or plugin changes, and whenever organic traffic or indexed pages drop suddenly. Outside those triggers, run a full technical SEO audit once or twice a year and lighter monthly checks in Google Search Console to catch problems early.

A Naga City clinic launched its new website on a Monday. By Friday, its appointment pages had disappeared from Google. The cause: the developer forgot to remove the “discourage search engines” setting from the staging site. One checkbox, five days of lost bookings.

Most technical SEO disasters happen right after a change. That is why the best time to audit is tied to events, not just the calendar.

Trigger 1: Before a website launches

A pre-launch audit on the staging site catches problems before Google sees them. Check that:

  • Robots.txt and meta robots tags will allow indexing on the live site.
  • Important pages return a 200 status code.
  • Title tags, canonicals, and the XML sitemap use the live domain, not the staging URL.

Trigger 2: Redesigns and migrations

Changing your domain, moving to HTTPS, switching platforms, or restructuring URLs are the riskiest moments for SEO. Old URLs must redirect with 301s to the matching new URLs. Audit before the migration (to record a baseline crawl) and after it (to compare). You will learn before-and-after crawl comparison in Module 12.

Trigger 3: Sudden drops in traffic or indexed pages

If organic clicks fall sharply in Google Search Console, or the number of indexed pages drops in the Pages report, run a focused audit. Start with one question: what changed on the site around that date? Plugin updates, theme changes, new cookie banners, and CDN settings are common culprits.

Trigger 4: Major CMS, plugin, or server changes

A new SEO plugin can rewrite canonical tags. A new hosting provider can produce 5xx server errors under load. A JavaScript framework upgrade can change what Googlebot renders. Any of these deserves a quick crawl.

The regular schedule

For sites without big changes, use this rhythm:

  • Monthly (15 minutes): Review Search Console’s Pages, Core Web Vitals, and Manual Actions reports.
  • Quarterly (larger sites): Run a scheduled crawl and compare it with the last one.
  • Yearly: A full technical SEO audit covering every module in this course.

Practice: audit now or wait?

Sort each item into the right group.

  • Moving the site from HTTP to HTTPS next week

  • Traffic is stable, last full audit was 4 months ago

  • Indexed pages fell from 900 to 300 in two weeks

  • Wrote two new blog posts this month

  • Switched from one page builder theme to another

  • Changed hosting provider yesterday

Common mistakes

  • Auditing only after traffic drops. By then, Google may have dropped pages for weeks.
  • No baseline crawl before a migration. Without it, you cannot prove what changed.
  • Blaming algorithm updates first. Check your own changes before blaming Google.
  • Running audits but no monthly checks. Small problems grow between yearly audits.
1. When should you first crawl a site that is about to migrate?
2. Indexed pages dropped sharply. What is the best first question?
3. What is a sensible audit rhythm for a small business site?

Your action

Next, you will learn the main types of technical SEO issues, so you know what you are looking for when you crawl.

Key terms

Site migration
Any large change to a site's URLs, domain, platform, or structure, such as moving from HTTP to HTTPS or from WordPress to Shopify.
Pre-launch audit
A technical check on a staging site before it goes live, to catch blocked pages, broken redirects, and missing tags.
Traffic drop diagnosis
An audit focused on finding why organic clicks or impressions fell, by comparing dates of site changes with search data.
Staging site
A private copy of a website used for testing changes before they reach the live site.

Questions beginners ask

How often should a small business website be audited?

A full technical audit once a year is enough for most small sites, plus a 15-minute monthly check of Search Console's Pages and Core Web Vitals reports.

Should I audit after a Google algorithm update?

Only if your traffic changed. Algorithm updates usually affect content and quality signals, so check technical health first to rule it out, then move to content.

What is the most common cause of a sudden traffic drop?

Recent site changes. Redesigns, migrations, and plugin updates often add noindex tags, break redirects, or block resources. Always check what changed on your site before blaming Google.

Do large sites need more frequent audits?

Yes. Ecommerce and news sites change daily, so they often run automated weekly crawls and a deep audit each quarter.

Related lessons

Want someone to handle SEO for your business while you learn? The team at Remar Digital can help.