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

Lazy Loading and Crawl Accessibility

Inside this lesson

  • Which lazy loading methods Google supports
  • Why scroll and click events can hide content
  • How to make infinite scroll crawlable
  • How to test lazy-loaded content

Short answer

Lazy loading is safe when it uses native loading="lazy" or loads content as it enters the viewport, since Googlebot renders with a tall viewport. It fails when content waits for scroll events, clicks, or load more buttons. Make infinite scroll crawlable with paginated URLs and real links, and test with URL Inspection's rendered HTML.

A Davao furniture shop’s category pages showed 12 products, then loaded more as you scrolled. There were no page 2 or page 3 URLs. Googlebot saw the first 12 products in each category. The other 400 were reachable only through the sitemap, with almost no internal links.

What works

  • Native lazy loading: <img src="sofa.webp" loading="lazy">
  • Viewport-based loading with IntersectionObserver
  • Real src in rendered HTML, not only data-src waiting for a script
  • Paginated URLs behind infinite scroll

What fails

  • Content loading only on scroll events
  • Content behind “Load more” or “Show all” buttons with no URL
  • Images that keep a placeholder src until user interaction
  • Lazy-loading the LCP image (performance problem, Lesson 7.4)

Making infinite scroll crawlable

  1. Give each chunk a real URL: /sofas/?page=2.
  2. Link to those pages with <a href> (visible pagination or in the HTML).
  3. Update the URL with the History API as users scroll.
  4. Make each paginated URL load directly with its items.

How to test

  • URL Inspection rendered HTML: are all images’ src real? Are lower items present?
  • Rendered crawl: compare product links found per category with the real count.
  • Image tab: look for placeholder images repeated across many pages.

Practice: crawler friendly or not?

Sort each item into the right group.

  • <img loading="lazy" src="chair.webp">

  • Products load only on scroll events, no page URLs

  • Load more button backed by /sofas/?page=2 links

  • Images with data-src and a blank placeholder src until scrolled

  • IntersectionObserver loading content in view

Common mistakes

  • Infinite scroll without paginated URLs.
  • Old lazy-load plugins relying on scroll events.
  • Checking only how it looks in your browser.
1. Does Googlebot scroll like a user?
2. How do you make infinite scroll crawlable?
3. Which lazy loading method is safest?

Your action

Next, you will put it all together to diagnose JavaScript SEO problems.

Key terms

Native lazy loading
The loading="lazy" attribute on images and iframes, handled by the browser.
IntersectionObserver
A browser API that loads content when it enters the viewport. Works with Google's tall viewport.
Scroll event loading
Loading content only when a scroll event fires. Googlebot does not scroll, so this can fail.
Infinite scroll
A list that keeps loading items as the user scrolls, often without unique URLs.

Questions beginners ask

Does Googlebot scroll?

Not like a user. It renders with a very tall viewport, so content that loads when in view usually appears.

Are lazy-loaded images indexed?

Yes, with native lazy loading or viewport-based loading and a real src in the rendered HTML.

Is a 'Load more' button bad?

Only if it is the only way to reach items. Add paginated URLs with real links behind it.

Should I put noscript fallbacks?

They can help non-rendering crawlers, but real src attributes and paginated URLs are better solutions.

Related lessons

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