freecourses.digital
Lesson progress: 0 of 3 activities done
All lessons in Technical SEO Auditing Lesson 2.7 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

Identifying Crawl Coverage Gaps

Covered here

  • What a crawl coverage gap is
  • The two directions of gaps: missing from the crawl and missing from Google
  • How to build a URL comparison table
  • How to sort gaps by cause before reporting

Short answer

A crawl coverage gap is any difference between the URLs your crawler found and the URLs that exist or matter. You find gaps by comparing the crawl against XML sitemaps, Search Console, analytics landing pages, and server logs, then sorting missing URLs into orphans, blocked pages, rendering problems, and scope errors.

Before you report a single issue, check that your crawl actually covered the site. An audit built on a crawl that missed the whole blog folder gives the client wrong answers. This lesson closes Module 2 by checking crawl completeness.

Two directions of gaps

Gap A: URLs that exist but your crawl missed. Found in the sitemap, Search Console, analytics, or logs, but not in the link crawl. Causes include orphans, JavaScript-only links, robots.txt blocks, and your own crawl limits.

Gap B: URLs your crawl found but Google does not use. Crawled as indexable, yet not indexed or with no impressions. Causes include duplicates, thin content, weak linking, or Google not having crawled them yet.

Build a URL comparison table

Create a spreadsheet with one row per URL and one column per source:

URLIn crawlIn sitemapIn Search ConsoleIn analyticsStatus code
/rooms/deluxe/YesYesYesYes200
/packages/whale-sharks/NoYesYesYes200
/blog/?page=40YesNoNoNo200

Every “No” on a URL that should rank is a gap to explain.

Sort gaps by cause

Group every gap into one cause before reporting:

  • Orphan: live, no internal links (Lesson 2.5)
  • Blocked: robots.txt or firewall stops crawling (Module 4)
  • Rendering: links exist only after JavaScript (Module 8)
  • Scope error: your exclusion or limit skipped it (Lesson 2.3)
  • Not chosen by Google: crawled but excluded from the index (Module 4 and 5)

Fix your own scope errors first, recrawl, then report the rest. Grouping also shows root causes: 400 missing URLs in one folder usually means one problem.

Practice: what caused this gap?

Sort each item into the right group.

  • Product in sitemap, live, no internal links

  • Whole /blog/ folder missing, crawl stopped at the 500 URL limit

  • Category links built with onclick, not crawled

  • Folder disallowed in robots.txt

  • Your regex excluded every URL containing 'event'

  • Old campaign page with visits in analytics, unlinked

Common mistakes

  • Reporting your own scope errors as site problems. Always check settings first.
  • Treating every gap as an issue. Redirects and removed URLs belong outside the sitemap and index.
  • Skipping this check entirely. Every later module depends on complete crawl data.
1. A whole folder is missing and the crawl hit its URL limit. What is the gap?
2. What should you do before reporting coverage gaps?
3. A redirected URL is not in the sitemap. Is that a problem?

Your action

You have finished Module 2. In Module 3, you will audit HTTP status codes and redirects across your crawl.

Key terms

Crawl coverage gap
A URL present in one data source but missing from another, which signals a discovery, crawling, or indexing problem.
URL comparison table
A spreadsheet listing every known URL with a column for each source, showing where it appears and where it does not.
Scope error
A gap caused by your own crawl settings, such as an exclusion rule or a URL limit.
Discovered, currently not indexed
A Search Console status meaning Google knows the URL but has not crawled it yet.

Questions beginners ask

What is the most common cause of coverage gaps?

On small sites, orphan pages and sitemap problems. On large sites, crawl limits, JavaScript-only links, and parameter rules.

Should every URL be in every source?

No. Redirected, noindexed, and removed URLs should not be in the sitemap or index. A gap only matters when a URL that should rank is missing somewhere.

How do I check if my own settings caused a gap?

Look at your exclusion rules, URL limit, and robots.txt setting. If the missing URL matches any of them, it is a scope error, not a site problem.

Is this the same as the comparison in Module 4?

This lesson checks discovery coverage. Module 4 compares indexing signals in depth, such as noindex, canonicals, and Google's chosen canonical.

Related lessons

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