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

How Search Engines Process JavaScript

Covered here

  • The three phases Google uses for JavaScript pages
  • What the Web Rendering Service does
  • What Googlebot does not do when rendering
  • Why non-Google crawlers may miss JavaScript content

Short answer

Google processes JavaScript pages in three phases: it crawls the HTML, queues the page for rendering in an evergreen Chromium browser, then indexes the rendered result. Rendering can be delayed, and Googlebot does not click, scroll, or keep state between pages. Many other crawlers, including some AI crawlers, do not render JavaScript at all.

Open a React app’s page source and you might see almost nothing: an empty <div id="root"></div> and a script tag. Everything visible appears only after JavaScript runs. Google can handle that, but with extra steps and extra risk.

The three phases

  1. Crawl: Googlebot fetches the HTML. Links in the raw HTML can be found immediately.
  2. Render: the page waits in the render queue, then Google’s Web Rendering Service runs it in an evergreen Chromium browser.
  3. Index: Google indexes the rendered HTML, including content and links added by JavaScript.

What Googlebot does not do

  • No clicking, typing, or “Load more” buttons
  • No real scrolling; it uses a tall viewport instead
  • No saved state: no cookies, logins, or data from earlier pages
  • No waiting forever: slow or failing scripts can leave content out
  • No access to blocked resources: scripts disallowed in robots.txt cannot run

Not every crawler renders

Bing renders with tighter limits. Many social media previews, SEO tools in default mode, and AI crawlers read only the raw HTML. For broad visibility, the safest place for important content and links is the initial HTML.

Practice: will Googlebot see it?

Sort each item into the right group.

  • Text inserted by JavaScript on page load

  • Reviews loaded only after clicking 'Show reviews'

  • Product data from an API blocked in robots.txt

  • Links in the raw HTML navigation

  • Prices shown only to logged-in users

Common mistakes

  • Assuming Google sees exactly what you see in your browser.
  • Blocking JavaScript or API endpoints in robots.txt.
  • Forgetting non-Google crawlers.
1. What are Google's three phases for JavaScript pages?
2. Does Googlebot click 'Load more' buttons?
3. Where should critical content live for the widest crawler support?

Your action

Next, you will compare HTML source with rendered HTML.

Key terms

Rendering
Running a page's JavaScript in a browser to produce the final HTML users see.
Web Rendering Service (WRS)
Google's system that renders pages using an up-to-date headless Chromium.
Render queue
The waiting line of crawled pages scheduled for rendering.
Stateless rendering
Googlebot loads each page fresh, without cookies, local storage, or a previous session.

Questions beginners ask

Does Google render all JavaScript?

Google attempts to render all indexable HTML pages, but scripts that error, time out, or are blocked by robots.txt can fail.

How long does rendering take?

Often seconds to minutes after crawling, sometimes longer for large or low-priority sites.

Do Bing and AI crawlers render JavaScript?

Bing renders, with limits. Many AI and social crawlers read only the raw HTML, so important content there is safest.

Does Googlebot interact with pages?

No. It does not click buttons, scroll like a user, or type into forms. Content that needs these actions may not be seen.

Related lessons

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