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

Types of Technical SEO Issues

What we will go through

  • The eight categories of technical SEO issues
  • Real examples of problems in each category
  • Which issue types usually have the biggest impact
  • How grouping issues helps you find root causes

Short answer

Technical SEO issues fall into eight groups: crawlability, indexability, status codes and redirects, duplicate URLs, on-page HTML, performance, JavaScript rendering, and structured data. Grouping issues this way helps you spot root causes, because one broken template or setting often creates hundreds of findings across the same group.

When you crawl a site for the first time, the tool may report hundreds of issues. That list is overwhelming until you see that almost every finding fits into one of eight categories. Each category matches a module in this course.

The 8 categories

1. Crawlability (Module 2 and 4). Can bots reach the page? Examples: robots.txt blocking a folder, orphan pages with no internal links, pages buried seven clicks deep.

2. Indexability (Module 4). Is the page allowed into the index? Examples: accidental noindex tags, canonical tags pointing elsewhere, pages missing from the XML sitemap.

3. Status codes and redirects (Module 3). Does the URL respond correctly? Examples: 404 broken links, 5xx server errors, redirect chains and loops, soft 404s.

4. Duplicate URLs (Module 5). Does the same content live at many addresses? Examples: HTTP and HTTPS versions both working, trailing slash variations, URL parameters, faceted navigation on an online shop.

5. On-page HTML (Module 6). Are page elements present and unique? Examples: missing or duplicate title tags, multiple H1s, missing alt attributes, thin or near-duplicate pages.

6. Performance (Module 7). Is the page fast and stable for real users? Examples: poor LCP from huge hero images, poor CLS from late-loading ads, slow INP from heavy scripts.

7. JavaScript rendering (Module 8). Does important content survive rendering? Examples: product descriptions loaded only by JavaScript, links built with click handlers instead of <a href>.

8. Structured data (Module 9). Is schema valid and accurate? Examples: missing required fields in Product schema, duplicate Organization markup, schema that does not match visible content.

Severity: not all categories are equal

As a rough rule, blocking issues come first. These stop pages from appearing at all: crawl blocks, noindex mistakes, server errors, and wrong canonicals. Next come issues that waste or split signals, like duplicates and redirect chains. Last come enhancement issues, like missing alt text or optional schema fields.

Think in root causes

A Cebu online shop might show 3,400 duplicate title tags. That looks like 3,400 problems, but it is one: the category template does not add the filter name to the title. Grouping by category, then by URL pattern, turns huge lists into a few real fixes. Module 10 teaches this in depth.

Practice: name the category

Sort each item into the right group.

  • Blog folder is disallowed in robots.txt

  • Old promo URL redirects 4 times

  • Same page works with and without www

  • Hero image makes LCP 6 seconds on mobile

  • Room pages have a noindex tag

  • Out-of-stock pages show 'not found' but return 200

  • 500 pages share the title 'Home'

  • Product schema is missing the price

Common mistakes

  • Fixing in tool order instead of severity order. Alphabetical issue lists hide the blockers.
  • Counting issues instead of root causes. Report “1 template problem affecting 3,400 URLs.”
  • Ignoring categories the tool does not show. Many crawlers skip JavaScript rendering unless you enable it.
1. Which is a blocking issue?
2. A page shows 'Product not found' but returns 200. What is it?
3. Why group issues by category and URL pattern?

Your action

Next, you will define the scope and objectives of your audit, the final step before you start crawling.

Key terms

Root cause
The single underlying problem, such as a template or server rule, that produces many individual issues.
Blocking issue
A problem that stops a page from being crawled or indexed at all, such as a noindex tag or a robots.txt disallow.
Soft 404
A page that returns a 200 status code but shows an error or empty content, so Google treats it as not found.
Faceted navigation
Filters on category pages, like size or price, that can create thousands of near-duplicate URLs.

Questions beginners ask

Which technical SEO issues are the most serious?

Blocking issues: robots.txt disallows on important sections, accidental noindex tags, 5xx server errors, and canonical tags pointing to the wrong URLs. These can remove pages from search entirely.

Are missing alt attributes a serious technical issue?

Usually low priority for rankings, but they matter for accessibility and image search. Fix them, but after blocking issues.

Can one issue belong to two categories?

Yes. A redirect chain is a status code issue, but if it affects canonical URLs it also becomes an indexability issue. Classify by the main effect.

Do all crawl tool warnings need fixing?

No. Many warnings are minor or false positives. Module 10 teaches you how to judge severity and filter them out.

Related lessons

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