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

Identifying Root Causes vs. Symptoms

This lesson covers

  • The difference between a symptom and a root cause
  • How to use the five whys in an audit
  • Where root causes usually hide
  • How to write findings around causes

Short answer

A symptom is what the crawl or Search Console shows, like 500 broken links. A root cause is why it happens, like a footer template linking to a deleted page. Trace causes by asking why repeatedly, inspecting the template or setting behind each group, and checking change history. Fixing causes stops the same issues from returning.

A Naga clinic fixed 200 broken links in January. By April there were 260 again. The links were fixed, but the cause was not: the doctor directory deleted profiles when doctors left, and every profile was linked from service pages.

Symptom vs. cause

SymptomRoot cause
1,200 duplicate titlesProduct title template uses only the category name
404 spike in Search ConsoleMigration launched without a redirect map
Pages dropped from indexSEO plugin update set noindex on a post type
Recurring broken linksDirectory deletes pages instead of redirecting

The five whys

Why are service pages full of broken links? Because they link to deleted doctor profiles. Why are profiles deleted? Because the directory removes them when a doctor leaves. Why does that break links? Because service pages link to profiles manually. Why is there no redirect? Because the CMS has no rule for removed profiles. Root cause: no process or rule for retired profiles.

Where causes hide

  • Templates and theme files
  • Plugin and app settings
  • Server and CDN rules
  • CMS workflows and editor habits
  • Releases and migrations (check change history and Search Console dates)

Practice: symptom or root cause?

Sort each item into the right group.

  • 300 pages excluded by noindex

  • Theme setting applies noindex to all 'page' templates

  • Duplicate meta descriptions on products

  • No redirect rule when products are deleted

  • Spike in 404 errors

Common mistakes

  • Reporting symptoms as findings without causes.
  • Stopping at the first why.
  • Ignoring process causes, so problems return.
1. How do you know you found a root cause?
2. Which is a root cause?
3. Which source helps date when an issue began?

Your action

Next, you will evaluate severity, impact, and effort.

Key terms

Symptom
The observable effect of a problem, such as errors, drops, or warnings.
Root cause
The underlying reason the symptom exists, usually a template, setting, process, or code rule.
Five whys
A method of asking 'why' repeatedly until you reach the underlying cause.
Change history
Records of releases, plugin updates, and settings changes that help date when issues began.

Questions beginners ask

How do I know I found the root cause?

When fixing it would remove the whole group of symptoms and stop new ones from appearing.

Can one root cause create several findings?

Yes. A migration without redirect mapping can cause 404s, lost rankings, and broken backlinks at once. Report it as one cause with linked symptoms.

What if I cannot see the code?

Describe the pattern and evidence clearly, and ask the developer to confirm the source. Hypotheses are fine when labeled as such.

Are process problems root causes?

Often. 'Editors can publish pages without titles' is a process cause that needs a CMS validation fix.

Related lessons

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