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

Rendering Failures and Missing Content

This lesson covers

  • The common causes of rendering failures
  • How to read URL Inspection's rendered output
  • How to find blocked resources and console errors
  • How to confirm whether Google indexed rendered content

Short answer

A rendering failure happens when JavaScript does not finish building a page for Googlebot, leaving it empty or partial. Common causes are script errors, resources blocked by robots.txt, slow APIs, timeouts, and code needing user interaction or storage. Diagnose with URL Inspection's screenshot, page resources, and console messages, then confirm with a site search for rendered text.

An Iloilo travel site moved its tour data to /api/tours. A developer then added Disallow: /api/ to robots.txt to “keep the API private.” Users saw full tour pages. Googlebot could not call the API, so it rendered empty templates with no prices, itineraries, or descriptions.

Common causes

  • Blocked resources: JS files or API paths disallowed in robots.txt
  • Script errors: one broken line stops later code
  • Slow APIs and timeouts: content arrives too late
  • Storage or cookie dependency: code expects localStorage, a session, or consent
  • User interaction required: content waits for a click or scroll
  • Unsupported features or geo blocks: content blocked for US-based Googlebot IPs

How to diagnose

  1. URL Inspection, Test Live URL, View Tested Page. Check:
    • Screenshot: does the page look complete?
    • HTML: search for key content
    • More info, Page resources: any “Couldn’t be loaded”?
    • JavaScript console messages: errors?
  2. Rendered crawl: compare word counts with expectations and look for templates with near-zero content.
  3. site: plus quote search: search an exact sentence from the rendered content to see if Google indexed it.

Practice: likely cause?

Sort each item into the right group.

  • Page resources list /api/products as blocked

  • Console shows 'Uncaught TypeError' before content loads

  • Content loads after an 8 second API delay

  • Main JS bundle disallowed in robots.txt

  • Content shown only after accepting cookies

Common mistakes

  • Testing only in a logged-in browser.
  • Blocking API paths that pages need to render.
  • Not searching the tested HTML. Screenshots can look fine while text is missing.
1. Where do you see resources Googlebot could not load?
2. Why might content render for you but not Googlebot?
3. How do you check that Google indexed rendered text?

Your action

Next, you will audit lazy loading and crawl accessibility.

Key terms

Rendering failure
When a page's scripts fail to produce the expected content during Google's render.
Page resources
Files a page loads. URL Inspection lists which ones Googlebot could not load.
JavaScript console error
An error message from a script that broke during execution.
Timeout
When rendering stops before slow scripts or API calls finish.

Questions beginners ask

How do I know if Google rendered my content?

Use URL Inspection, Test Live URL, View Tested Page. Check the screenshot and search the HTML for your content. Then search Google for an exact sentence in quotes.

Why does it work in my browser but fail for Google?

Your browser may have cookies, cached files, a login, or allowed resources that Googlebot does not.

Can errors on one script break the whole page?

Yes. An uncaught error early in a bundle can stop all later code, including content rendering.

Does the live test show what Google indexed?

It shows how Google renders now. The indexed version may differ if it was crawled earlier or rendered under different conditions.

Related lessons

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