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

Separating Sitewide and Isolated Issues

Covered here

  • What makes an issue sitewide, template-wide, or isolated
  • How to test which kind an issue is
  • Why the difference changes the fix and the owner
  • How to spot small patterns that will grow

Short answer

Sitewide issues affect every or nearly every page, usually from global templates, server rules, or settings. Template-wide issues affect one page type. Isolated issues affect a few individual pages, usually from editing mistakes. Check the share of affected URLs per page type to classify them, then route sitewide fixes to developers and isolated fixes to content editors.

“Missing meta descriptions: 312 URLs.” Is that one broken template or 312 editing slips? The answer decides whether a developer spends an hour or an editor spends a week.

Three scopes

ScopeTypical causeFixed byExample
SitewideGlobal header, footer, server, CDN, pluginDeveloper or hostHTTP links in the footer on all pages
Template-wideOne page type’s template or plugin settingDeveloperAll products missing canonical
IsolatedManual page editsEditor6 posts missing titles

How to classify

Pivot affected URLs by page type and calculate the affected share:

Page typeTotalMissing descriptionShare
Product280280100%
Blog post400266.5%
Page40615%

Products: template-wide. Posts and pages: isolated editing gaps.

Watch for small patterns

Isolated issues with a shared trait, such as all published by one author or all created after a certain date, may point to a new process gap. Note them before they become template-wide.

Practice: which scope?

Sort each item into the right group.

  • Every page loads a 2 MB script from the header

  • 3 blog posts with duplicate H1s

  • All 500 product pages missing schema price

  • One landing page with a typo in its canonical

  • All pages return HSTS errors on the www host

Common mistakes

  • Sending template issues to editors. They cannot fix code.
  • Treating isolated issues as low priority automatically. The homepage is one page.
  • Ignoring patterns in isolated issues.
1. 100% of product pages share an issue. Scope?
2. Who usually fixes isolated issues?
3. Can an isolated issue be urgent?

Your action

Next, you will learn to spot false positives.

Key terms

Sitewide issue
A problem present on all or most pages, caused by global code, settings, or server rules.
Template-wide issue
A problem affecting most pages of one type, such as all products.
Isolated issue
A problem on a handful of individual pages, usually caused by manual edits.
Affected share
The percentage of URLs in a group that show the issue.

Questions beginners ask

Are sitewide issues always more important?

Usually, but not always. A single broken homepage canonical is isolated and urgent.

How do I quickly test an issue's scope?

Divide affected URLs by total URLs per page type. Near 100% means template or sitewide. Under 5% usually means isolated.

Who fixes isolated issues?

Often content editors or the site owner in the CMS, with a short list of URLs and the change needed.

Why care about small patterns?

A few pages with the same issue can be a new process gap, like a new editor skipping titles, that will grow.

Related lessons

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