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

Evaluating Severity, Impact, and Effort

Inside this lesson

  • The difference between severity, impact, and effort
  • A simple scoring model you can reuse
  • How traffic and business data change priorities
  • How to explain your ranking to stakeholders

Short answer

Severity is how badly an issue breaks crawling, indexing, or ranking. Impact is how much traffic, revenue, or how many important pages it affects. Effort is the work and risk to fix it. Score each finding on these three, plus confidence, then rank by high impact and severity against low effort to decide what gets fixed first.

Two findings: “Sitewide missing alt text” and “Noindex on 40 location pages.” The crawler marks the first as high priority because it affects more URLs. A real auditor knows the second can wipe out a business’s local visibility. Scoring makes that judgment visible and consistent.

The four factors

Score each finding from 1 (low) to 3 (high):

Factor123
SeverityCosmetic or best practiceWeakens signalsBlocks crawling or indexing
ImpactFew low-value pagesSome important pagesKey templates, traffic, or revenue
ConfidenceHypothesisLikelyConfirmed with Google data
Effort (reverse)Major projectModerateQuick setting or template change

Priority score = Severity + Impact + Confidence + Effort. Highest first.

Use real data for impact

Join Search Console clicks and impressions, and analytics conversions, by URL or template. “Affects 40 pages” means little. “Affects 40 location pages that earned 62% of leads last quarter” settles debates.

Practice: higher or lower priority?

Sort each item into the right group.

  • Noindex on location pages that drive most leads

  • Missing alt text on decorative blog images

  • robots.txt blocks /products/ (confirmed in Search Console)

  • Meta descriptions 5 characters too long on old posts

  • One-line fix for a sitewide canonical bug

Common mistakes

  • Ranking by URL count alone.
  • Ignoring effort, so the roadmap stalls.
  • Not showing the scoring, so stakeholders argue opinions.
1. Which factor measures how badly crawling or indexing is affected?
2. What makes impact convincing?
3. An uncertain issue should get...

Your action

Next, you will separate sitewide issues from isolated ones.

Key terms

Severity
How seriously an issue affects search engines' ability to crawl, index, understand, or rank pages.
Impact
The business and search consequences, based on affected pages, traffic, and revenue.
Effort
Developer time, cost, dependencies, and risk required to fix.
Confidence
How sure you are that the issue is real and that the fix will help.

Questions beginners ask

Is there a standard scoring model?

No single standard. A 1 to 3 or 1 to 5 scale per factor is common. Consistency matters more than the exact scale.

Who estimates effort?

Ideally the developer. Give your own estimate, then confirm in the review meeting.

Should low-severity issues ever come first?

Yes, when they are quick, low risk, and affect high-value pages. Quick wins build momentum.

How do I handle uncertain issues?

Lower the confidence score and recommend a test or investigation step instead of a full fix.

Related lessons

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