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

Tracking Fixes and Ownership

In this lesson

  • Why audits fail after delivery
  • How to assign clear ownership
  • Which statuses to track
  • How to report progress simply

Short answer

Track fixes by giving every finding one named owner, a status such as open, in progress, deployed, verified, or won't fix, a due date, and a link to its development ticket. Review the register in short regular check-ins, report progress by priority level, and only mark items verified after re-crawl and Google data confirm the fix.

Many audits end the same way: a great report, a good meeting, then silence. Six months later, the same issues appear in the next audit. Tracking is what turns findings into results.

One owner per finding

Each row in the register gets one named person, not “dev team” or “marketing.” That person may delegate, but they answer for progress.

Five statuses

StatusMeaning
OpenNot started
In progressWork has begun, ticket linked
DeployedChange is live
VerifiedConfirmed by re-crawl and Google data, no regressions
Won’t fixTeam decided not to act, reason recorded

Keep deployed and verified separate. Many “fixed” items are live but not actually working.

Check-ins and reports

  • Check-ins: 15 minutes every one or two weeks. Review Now and Next items only.
  • Progress report: counts by status and priority, blocked items, and one or two early results.

Example: “Now phase: 3 of 3 verified. Next phase: 4 of 6 deployed, 2 blocked by theme update. Location pages back in the index, impressions up 38% in 3 weeks.”

Practice: which status?

Sort each item into the right group.

  • Redirect rules live, not yet recrawled

  • Recrawl confirms canonicals correct, no new errors

  • Owner decided to keep old blog URLs, reason logged

  • Noindex removed and URL Inspection shows indexed

  • Image dimensions added in template yesterday

Common mistakes

  • Team ownership with no name.
  • Marking deployed as done.
  • Stopping check-ins after the first wins.
1. What is the difference between deployed and verified?
2. Who should own a finding?
3. What should a 'won't fix' include?

Your action

You have finished Module 11. In Module 12, the final module, you will verify fixes and run technical QA.

Key terms

Owner
The one named person responsible for getting a fix done.
Deployed vs. verified
Deployed means the change is live. Verified means you have confirmed it works and caused no new issues.
Won't fix
A status for findings the team decides not to address, with the reason recorded.
Progress report
A short update showing fixes completed, in progress, and blocked, by priority.

Questions beginners ask

Can a team be the owner?

Name one person, even within a team. Shared ownership often means no ownership.

How often should we check in?

Every one or two weeks during the Now and Next phases, then monthly.

What if a fix is blocked?

Record the blocker and who can unblock it. Escalate high-priority blocked items in the progress report.

Is 'won't fix' a failure?

No. It is a documented business decision. Record the reason so it can be revisited.

Related lessons

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