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

URL Structure and Normalization

In this lesson

  • What makes a URL clean and consistent
  • What URL normalization means
  • The variations that create duplicate addresses
  • How to audit URL patterns in a crawl

Short answer

URL normalization means making sure every page has one consistent address, with the same protocol, hostname, letter case, trailing slash format, and no unneeded parameters. Clean URLs are short, readable, lowercase, and use hyphens. Audit them by sorting crawled URLs and flagging variations that return 200 instead of redirecting to the preferred version.

To a person, these all look like one page. To a server, they can be five:

https://www.example.ph/rooms/deluxe/
https://www.example.ph/Rooms/Deluxe/
https://www.example.ph/rooms/deluxe
http://example.ph/rooms/deluxe/
https://www.example.ph/rooms/deluxe/?ref=fb

If all five return 200, Google sees five copies. URL normalization picks one and makes the others point to it.

What clean URLs look like

  • Short and readable: /tours/mayon-volcano/ beats /index.php?id=4471&cat=9
  • Lowercase, hyphen-separated
  • Logical folders that match site sections
  • No session IDs or unneeded parameters
  • Stable: they do not change when titles or dates change

The normalization rules to check

For each, one format should return 200 and the others should 301 to it:

  1. Protocol: HTTPS, not HTTP
  2. Hostname: www or non-www
  3. Letter case: lowercase
  4. Trailing slash: with or without, consistently
  5. Index files: / not /index.html
  6. Parameters: tracking and sorting parameters canonicalized or ignored

How to audit

Sort crawled URLs alphabetically and scan for near-identical pairs. Use your crawler’s filters for uppercase, underscores, parameters, and non-ASCII characters. Then manually test variations of 5 key pages: change the case, remove the slash, switch to HTTP and non-www, and add ?test=1. Note the status code for each.

Practice: clean or needs work?

Sort each item into the right group.

  • /tours/mayon-volcano/

  • /Tours/Mayon_Volcano.html

  • /product.php?id=883&sessionid=a8f2

  • /locations/legazpi/

  • /2019/03/14/our-new-menu-update-final-v2/

Common mistakes

  • Renaming URLs without redirects.
  • Allowing every variation to return 200.
  • Mixed formats in internal links. Half link with a slash, half without.
1. What does URL normalization aim for?
2. /Rooms/ and /rooms/ both return 200. What is the risk?
3. Which separator should URLs use?

Your action

Next, you will learn how to find duplicate URLs and duplicate pages.

Key terms

URL normalization
Standardizing URLs so each page is reached at one preferred format, with other variations redirected or canonicalized.
Slug
The readable part of a URL that names the page, such as /deluxe-room/.
Percent encoding
How special characters and spaces appear in URLs, such as %20 for a space.
Case sensitivity
On most servers, /Rooms/ and /rooms/ are different URLs, which can create duplicates.

Questions beginners ask

Do keywords in URLs help rankings?

Only slightly. Readable URLs mainly help users and click-through. Never change working URLs just to add keywords without redirects.

Should URLs be lowercase?

Yes. Use lowercase consistently and redirect uppercase variations, since many servers treat them as separate pages.

Hyphens or underscores?

Use hyphens. Google treats hyphens as word separators.

Should I include dates in blog URLs?

Usually not. Dates make content look old and force URL changes when updating posts.

Related lessons

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