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

Identifying 5xx Server Errors

In this lesson

  • What the common 5xx codes mean
  • How 5xx errors affect Googlebot's crawling
  • How to tell real server errors from crawl-caused ones
  • What evidence developers need to fix them

Short answer

A 5xx error means the server failed to deliver a page. Find them in your crawl's response codes and in Search Console's Crawl Stats and Pages reports. Recheck each one at a slower crawl speed, because your own crawl can cause them, then give developers the URLs, times, and patterns.

During a 12.12 sale, a Davao gadget store’s product pages started returning 503 errors. The server could not handle the shoppers plus Googlebot. Sales stopped, and so did crawling. Server errors hurt people and search engines at the same time.

The codes you will meet

  • 500: something broke in the site’s code, plugin, or database.
  • 502: a CDN or proxy got a bad response from the origin server.
  • 503: the server is overloaded or in maintenance.
  • 504: the origin server took too long to answer the proxy.

Where to find them

  1. Your crawl: Response Codes, filter Server Error (5xx).
  2. Search Console Pages report: “Server error (5xx)” lists URLs Google could not fetch.
  3. Search Console Crawl Stats: check Host status and the breakdown by response. Spikes show when Googlebot hit problems.
  4. Server logs: confirm whether Googlebot itself received the errors.

Real errors or crawl-caused?

Your crawl can create the errors you report. Before reporting, recheck every 5xx URL in list mode at 1 URL per second.

  • Still failing: likely a real error. Report it.
  • Now returns 200: probably load or rate limiting. Note it as a server capacity risk, not a broken page.
  • Fails only for some user agents: a firewall or bot protection rule may be blocking crawlers, including Googlebot.

What developers need

Give them URLs, time stamps, the user agent used, the response code, and any pattern (one template, one folder, only under load). Include the Search Console Crawl Stats chart if it shows spikes.

Practice: what does this suggest?

Sort each item into the right group.

  • Every /checkout/ URL returns 500 even at slow speed

  • 503s appeared at 10 URLs per second, gone at 1 per second

  • Search Console shows the same 500s for Googlebot

  • 403 and 503 only when using a crawler user agent

  • Blog pages return 502 after a CDN change

Common mistakes

  • Reporting 5xx errors without rechecking. Developers lose trust in the audit.
  • Ignoring Crawl Stats. It shows what Googlebot experienced over 90 days.
  • Treating a short maintenance 503 as a crisis. Duration and frequency matter.
1. What should you do before reporting 5xx errors from a crawl?
2. Which Search Console report shows Googlebot's server problems over time?
3. How does Google react to many 5xx errors?

Your action

Next, you will audit redirect chains and loops.

Key terms

500 Internal Server Error
A general server failure, often caused by code bugs, plugin conflicts, or database problems.
502 Bad Gateway
A server or proxy received an invalid response from another server behind it, common with CDNs and load balancers.
504 Gateway Timeout
A server behind a proxy took too long to respond.
Host status
A section of Search Console Crawl Stats showing whether Google had problems reaching your server, robots.txt, or DNS.

Questions beginners ask

How do 5xx errors affect SEO?

Google slows its crawling when it sees many server errors. If important pages keep returning 5xx for days, Google may drop them from the index until they recover.

Is a 503 during maintenance safe?

Yes, for short periods. A 503 tells Google to come back later. Long or repeated 503s over several days can still cause pages to drop.

Why do I see 5xx errors only in my crawl?

Your crawl may be too fast for the server, or a firewall may be rate limiting you. Recrawl those URLs slowly before reporting them.

Who fixes 5xx errors?

Usually the developer or hosting provider. Your job is to supply clear evidence: affected URLs, time stamps, patterns, and how to reproduce the error.

Related lessons

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