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

Orphan Pages and URL Discovery

This lesson covers

  • What an orphan page is and why it happens
  • Which data sources reveal URLs that links do not
  • How to find orphans step by step
  • How to decide whether to link, redirect, or remove them

Short answer

An orphan page is a URL that exists but has no internal links pointing to it. Crawlers that follow links cannot find it, so you discover orphans by comparing crawl data with XML sitemaps, Google Search Console, analytics, and server logs. Then link to valuable orphans or redirect and remove the rest.

A Sorsogon resort removed its “Whale Shark Packages” link from the menu during a redesign. The page stayed live and was still in the sitemap, but nothing linked to it. Its rankings slid for months before anyone noticed. That page was an orphan.

Why your crawler cannot see orphans

In Lesson 2.1, you learned that crawlers follow links. An orphan has no links, so a normal crawl never reaches it. To find orphans, you need other lists of URLs and compare them with your crawl.

Where orphan URLs hide

  • XML sitemaps: URLs your CMS still lists.
  • Google Search Console: URLs with impressions in the Performance report, or listed in the Pages report.
  • Analytics: Landing pages that received visits.
  • Server logs: URLs Googlebot requested.
  • Backlink tools: URLs that other sites link to.

Finding orphans step by step

  1. Crawl the site normally and export all crawled URLs.
  2. Collect URLs from the sources above.
  3. Combine them and remove duplicates.
  4. Compare: any URL in the sources but not found by the link crawl is a possible orphan.
  5. Crawl those URLs in list mode to check their status codes. Ignore ones that 404 or redirect for now (Module 3 covers them).
  6. The remaining 200-status pages are your orphans.

Screaming Frog can do steps 2 to 4 for you through Crawl Analysis, if you connected sitemaps, Search Console, and analytics in Lesson 2.2.

What to do with each orphan

  • Valuable and current: Add internal links from relevant pages, hubs, or the menu.
  • Outdated but has backlinks or traffic: 301 redirect to the closest relevant page.
  • Intentional (ads landing page): Keep it, but add noindex if it should not rank, and remove it from the sitemap.
  • No value: Remove it (404 or 410) and take it out of the sitemap.

Practice: what should happen to this orphan?

Sort each item into the right group.

  • Current service page that gets search impressions

  • 2021 promo page with 15 backlinks

  • Google Ads landing page duplicating the main offer

  • Live product page removed from its collection by mistake

  • Test page called /test-page-2/

Common mistakes

  • Relying on one data source. Each source misses something. Combine them.
  • Counting redirects and 404s as orphans. Check status codes first.
  • Leaving orphans in the sitemap. It tells Google the page matters while your links say it does not.
1. Why does a normal crawl miss orphan pages?
2. A URL appears in the sitemap and analytics but not in the link crawl. It returns 200. What is it?
3. Best action for a valuable current orphan page?

Your action

Next, you will learn why crawl data and search engine data often disagree, and how to use both.

Key terms

Orphan page
A live URL with zero internal links from other crawlable pages on the site.
Server log file
A record from the web server of every request, including visits from Googlebot, with URL, time, and status code.
List mode crawl
A crawl of a pasted URL list instead of following links from a seed page.
Landing page report
An analytics report showing the pages where visitors entered the site.

Questions beginners ask

Why do orphan pages happen?

Common causes are removed menu items, deleted categories, campaign landing pages, old URL structures after a redesign, and products taken out of collections but left live.

Are orphan pages always bad?

Not always. A paid ads landing page may be orphaned on purpose. In that case, add a noindex tag if it should not rank. Orphans that should rank need internal links.

Can Google index orphan pages?

Yes, if it found them through the sitemap, backlinks, or past crawls. But they usually rank poorly because they receive no internal link value.

Do I need server logs to find orphans?

No, but they help on large sites. Sitemaps, Search Console, and analytics find most orphans on small sites.

Related lessons

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