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

Heading Hierarchy and HTML Structure

Your roadmap for this lesson

  • What a logical heading outline looks like
  • How to spot skipped and misused headings
  • Which semantic HTML elements help search engines
  • Which HTML errors actually affect SEO

Short answer

Heading hierarchy means using H1 for the main topic, H2 for sections, and H3 for subsections, without using headings just for styling. Audit it by extracting headings from your crawl, checking key templates for skipped levels and fake headings, and confirming semantic elements like main, nav, and article, plus HTML errors that break the head section.

Headings are a page’s table of contents. When they are used for font size instead of meaning, the outline turns into noise for screen readers and search engines alike.

A clean outline

H1 Apo Island Day Trip
  H2 What's included
  H2 Schedule
    H3 Morning dive
    H3 Afternoon snorkel
  H2 Prices
  H2 FAQs

What to check

  1. Skipped levels in templates (H1 then H4).
  2. Fake headings: bold paragraphs used as section titles, or H tags used only to make text big.
  3. Boilerplate headings: sidebar and footer widgets like “Follow Us” as H2 on every page.
  4. Semantic elements: content inside <main>, menus in <nav>, posts in <article>.
  5. Head errors: non-head elements in <head> that end it early.

How to audit

  • Use custom extraction in your crawler to pull all H2 and H3 text, or a headings browser extension on key templates.
  • Review one page per template, not every page.
  • Check the Validation tab (Screaming Frog) for “Invalid HTML elements in head” and “Head not first in HTML.”

Practice: good structure or issue?

Sort each item into the right group.

  • H1 topic, H2 sections, H3 subsections

  • <img> tracking pixel placed inside <head>

  • Footer 'Contact Us' marked as H2 on every page

  • Main content wrapped in <main>

  • Section titles written as bold <p> text

Common mistakes

  • Chasing every validation error. Most do not matter.
  • Ignoring head errors. These can disable canonicals and hreflang.
  • Auditing pages instead of templates.
1. What can an <img> inside <head> cause?
2. What is a fake heading?
3. Best way to audit heading structure?

Your action

Next, you will audit image alt attributes.

Key terms

Heading outline
The tree of H1 to H6 headings that shows a page's structure.
Semantic HTML
Elements that describe meaning, such as <main>, <nav>, <article>, <header>, and <footer>.
Fake heading
Text styled to look like a heading without heading tags, or a heading tag used only for style.
Broken head
Invalid HTML in the <head> that causes browsers and Google to end the head early, ignoring tags after the error.

Questions beginners ask

Does skipping from H2 to H4 hurt rankings?

Not directly. A clean outline helps users, accessibility tools, and Google's understanding of sections, so fix it in templates when easy.

Do I need perfectly valid HTML?

No. Most validation errors do not matter for SEO. Focus on errors that break the head, hide content, or break links.

What breaks the head section?

Elements that are not allowed in the head, such as <div>, <img>, or <iframe>, often added by tag scripts. Google may then treat later tags like canonical or hreflang as body content and ignore them.

Are headings in sidebars and footers a problem?

They add noise. Widget titles like 'Recent Posts' marked as H2 on every page can crowd the outline. Prefer non-heading styling.

Related lessons

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