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

Mobile Usability and Responsive Rendering

This lesson covers

  • What mobile-first indexing means for audits
  • The mobile usability checks that still matter
  • How to check mobile and desktop content parity
  • Which tools replace the retired Mobile Usability report

Short answer

Google indexes the mobile version of your pages, so a mobile audit checks that the viewport is set, text is readable, tap targets are large enough, nothing overflows the screen, and mobile pages contain the same content, links, structured data, and metadata as desktop. Use a mobile user agent crawl and Lighthouse to check.

A Legazpi hardware store’s desktop product pages had specifications, reviews, and related products. On mobile, a “lite” theme removed all three to save space. Because Google indexes the mobile version, those specs and links effectively disappeared from Google too.

Mobile-first indexing in practice

Googlebot Smartphone crawls your site. Whatever is missing on mobile is, for Google, missing. That makes mobile checks part of indexability, not only design.

Usability checks

  1. Viewport: <meta name="viewport" content="width=device-width, initial-scale=1">
  2. No horizontal scrolling: content fits the screen.
  3. Readable text: around 16px base font.
  4. Tap targets: large enough and spaced apart (about 48px).
  5. No intrusive pop-ups covering content on arrival.

Parity checks

Crawl once with Googlebot Smartphone and once with Googlebot Desktop, then compare per URL:

  • Word count and main content
  • H1, title, meta description
  • Internal links and their counts
  • Structured data
  • Images and alt text

Large differences in word count or outlinks point to missing mobile content.

Tools

  • Lighthouse (mobile) for viewport, font, and tap target issues
  • Chrome DevTools device mode for visual checks
  • URL Inspection, View Tested Page, for Googlebot Smartphone’s rendered screenshot
  • Your crawler with both user agents for parity

Practice: problem or fine?

Sort each item into the right group.

  • Specs hidden in an accordion on mobile

  • Reviews removed entirely on mobile

  • Missing viewport meta tag

  • Same structured data on mobile and desktop

  • Full-screen pop-up on mobile arrival

Common mistakes

  • Checking only desktop crawls.
  • Looking for the old Mobile Usability report. Use Lighthouse instead.
  • Treating accordions as hidden content. They are indexed.
1. Which version does Google use for indexing?
2. How do you check content parity at scale?
3. Is content inside a mobile accordion indexed?

Your action

Next, you will prioritize performance fixes.

Key terms

Mobile-first indexing
Google uses the mobile version of a page for crawling, indexing, and ranking.
Content parity
Mobile and desktop versions having the same main content, links, headings, structured data, and metadata.
Tap target
A button or link users tap. Too small or too close together causes mis-taps.
Responsive design
One URL and HTML that adapt layout to screen size with CSS, Google's recommended setup.

Questions beginners ask

Does Search Console still have a Mobile Usability report?

No. Google retired it in December 2023. Use Lighthouse, Chrome DevTools device mode, and a mobile user agent crawl instead.

Is content in mobile tabs or accordions indexed?

Yes, content hidden in tabs or accordions for mobile usability is indexed normally.

What if the mobile site removes content?

Removed content may not be indexed at all, since Google uses the mobile version.

Are separate m. sites still okay?

They work but are harder to maintain. They need correct annotations and full parity. Responsive design is simpler.

Related lessons

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