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

Verifying Redirects, Canonicals, and Indexability

Covered here

  • Why these three fix types need extra checks
  • How to verify a redirect map
  • How to verify canonicals and indexability signals together
  • How to confirm sitemaps match the fixes

Short answer

Verify redirects by list-crawling every old URL and confirming each returns one 301 hop to the mapped 200 destination. Verify canonicals by checking raw and rendered tags point to the preferred indexable URL. Verify indexability by confirming meta robots, X-Robots-Tag, robots.txt, and sitemaps all match the intended state for each page group.

A Legazpi online store migrated to a new platform. The developer confirmed “all redirects are working.” A list crawl showed 40% of old product URLs redirected to the homepage instead of their matching products. “Working” and “correct” are not the same thing.

Verifying redirects

  1. List-crawl all old URLs from the redirect map, following redirects.
  2. Export address, status, final address, number of hops.
  3. Compare final address with the planned destination.
  4. Flag:
    • Wrong destination (especially the homepage)
    • More than one hop
    • 302 instead of 301
    • Final URL not returning 200

Verifying canonicals

For affected templates, confirm:

  • Canonical points to the preferred, 200, indexable URL
  • Raw and rendered canonicals match
  • Only one canonical tag per page
  • Correct protocol, host, and trailing slash

Verifying indexability

For each page group, check all signals against its intended state (Lesson 4.7):

SignalIndex group should show
Status200
Meta robots and X-Robots-Tagindex or none
robots.txtAllowed
CanonicalSelf-referencing
XML sitemapListed

Practice: pass or fail?

Sort each item into the right group.

  • Old product URL → 301 → matching new product (200)

  • Old product URL → 301 → homepage

  • Canonical self-referencing in raw and rendered HTML

  • Noindex removed, but page still disallowed in robots.txt

  • Sitemap still lists the old redirected URLs

Common mistakes

  • Checking only status codes, not destinations.
  • Verifying canonicals in raw HTML only.
  • Forgetting the sitemap after redirect changes.
1. How do you verify a redirect map?
2. Old URLs redirecting to the homepage is...
3. Indexable pages should be...

Your action

Next, you will detect regressions and newly introduced issues.

Key terms

Redirect map
A table of old URLs and their intended new destinations, used to build and verify redirects.
Destination match
Whether the final URL after redirects equals the planned destination in the map.
Signal check
A combined check that canonicals, robots directives, and sitemaps agree for a URL.
Intended state
The agreed indexing decision for a page group: index, consolidate, hide, or remove.

Questions beginners ask

Why are these fixes high risk?

A wrong redirect, canonical, or noindex can remove pages from Google. Errors here affect many URLs at once.

How do I verify a redirect map quickly?

List-crawl the old URLs with redirects followed, export the final URL, and compare it to the planned destination column.

Should I check rendered canonicals?

Yes, on JavaScript sites. Raw and rendered canonicals must match.

Do sitemaps need updating after redirects?

Yes. Sitemaps should list only final 200 URLs, never redirected ones.

Related lessons

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