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

XML Sitemap Validation

Covered here

  • What a clean XML sitemap should contain
  • Format rules and size limits
  • How to crawl a sitemap to find bad URLs
  • How to read the Search Console Sitemaps report

Short answer

XML sitemap validation checks that the file is readable, within limits of 50,000 URLs or 50 MB, and lists only final, indexable, 200-status canonical URLs. Crawl the sitemap URLs to find redirects, 404s, noindexed and canonicalized pages, compare it with your site crawl, and confirm it is submitted in Search Console without errors.

An XML sitemap is your official list of “pages worth indexing.” If that list includes deleted pages, redirects, and duplicates, Google learns to trust it less. A clean sitemap is a short audit with a big payoff.

What a good sitemap looks like

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.ph/rooms/deluxe/</loc>
    <lastmod>2026-09-14</lastmod>
  </url>
</urlset>
  • Absolute URLs on the correct protocol and host
  • UTF-8, valid XML, max 50,000 URLs or 50 MB uncompressed per file
  • Only URLs that are 200, indexable, and self-canonical
  • Accurate lastmod dates

The validation steps

  1. Find all sitemaps: robots.txt Sitemap lines, /sitemap.xml, /sitemap_index.xml, and Search Console.
  2. Check they load: 200 status, valid XML, within limits.
  3. Crawl the sitemap URLs in list mode or with sitemap integration.
  4. Flag non-indexable entries: 3xx, 4xx, 5xx, noindex, canonicalized, blocked by robots.txt.
  5. Compare with your site crawl: indexable pages missing from the sitemap, and sitemap pages missing from the crawl (orphans).
  6. Check Search Console’s Sitemaps report: status “Success,” and discovered URL counts that make sense.

Practice: keep in sitemap or remove?

Sort each item into the right group.

  • Indexable product page returning 200

  • URL that 301 redirects

  • Page with noindex

  • Blog post with self-referencing canonical

  • Parameter URL canonicalized to the clean URL

  • Deleted page returning 404

Common mistakes

  • Static sitemaps that never update. Use a CMS-generated one.
  • Staging or HTTP URLs in the live sitemap.
  • lastmod set to today for every URL. Google stops trusting it.
  • Submitting but never checking the report.
1. What is the URL limit per sitemap file?
2. Which URL belongs in a sitemap?
3. Why avoid setting lastmod to today on every URL?

Your action

Next, you will audit canonical URLs in depth.

Key terms

XML sitemap
A file listing URLs you want search engines to discover and consider for indexing.
Sitemap index
A file that lists multiple sitemaps, used for large sites or separate content types.
lastmod
A date in the sitemap showing when the page last changed significantly. Google uses it only if it is consistently accurate.
Sitemaps report
The Search Console report showing submitted sitemaps, fetch status, and discovered URLs.

Questions beginners ask

Does a sitemap guarantee indexing?

No. It helps discovery and signals preference, but Google still decides what to index.

Should I include every page?

Include every page you want indexed, and only those. Leave out redirects, errors, noindexed pages, and duplicates.

Do priority and changefreq matter?

Google ignores them. Accurate lastmod dates are more useful.

How many sitemaps can I have?

As many as you need, grouped in sitemap index files. Splitting by type (products, posts, locations) makes reporting easier.

Related lessons

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