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

Noindex and Canonical Conflicts

Inside this lesson

  • Why noindex and canonical send opposite messages
  • The four most common directive conflicts
  • How to filter conflicts in a crawl
  • How to choose one clear signal per URL

Short answer

A noindex tag says remove this page, while a canonical tag says index another page instead and merge signals there. Using both on one URL sends Google mixed messages. Pick one: canonical for duplicates you want consolidated, noindex for pages that should never appear. Also never block noindexed pages in robots.txt.

Imagine a sign on a door that says “This room is closed” and a second sign that says “Please use Room 5 instead, it is the same room.” Visitors do not know whether Room 5 is closed too. Google faces the same confusion with mixed signals.

The four common conflicts

  1. Noindex + canonical to another URL. “Remove me” plus “index that one with my signals.” Risk: Google may carry the noindex to the target.
  2. Noindex + robots.txt Disallow. Google cannot crawl the page, so it never sees the noindex. The URL may stay indexed.
  3. Canonical to a URL that is noindexed, redirected, or 404. The target cannot be the preferred version.
  4. Noindexed or canonicalized URLs in the XML sitemap. The sitemap says “index me,” the page says otherwise.

How to find them in a crawl

  • Filter Noindex URLs, add the canonical column, and look for canonicals pointing elsewhere.
  • Filter Blocked by Robots.txt, then check those URLs against Search Console’s “Indexed, though blocked” list.
  • Open the Canonicals report and filter for canonical targets that are non-200 or noindexed.
  • Use the Sitemaps report to find non-indexable URLs listed in sitemaps.

How to fix

  • Duplicate you want merged: keep the canonical, remove the noindex.
  • Page that should vanish: keep noindex, remove the cross-canonical (or make it self-referencing), keep it crawlable.
  • Blocked + noindex: remove the robots.txt block until Google drops the pages, then decide whether to block again.
  • Bad canonical target: point to the final, indexable 200 URL.

Practice: conflict or clean?

Sort each item into the right group.

  • noindex + canonical to /main-page/

  • Indexable page with self-referencing canonical

  • noindex page blocked by robots.txt

  • Duplicate with canonical to a 200 indexable page

  • Canonical pointing to a 301 redirect

  • noindex page, crawlable, not in sitemap

Common mistakes

  • Adding noindex “just to be safe” to canonicalized duplicates.
  • Blocking pages you are trying to deindex.
  • Fixing the page but not the sitemap.
1. What is the risk of noindex plus a canonical to another page?
2. A page has noindex and is disallowed in robots.txt. What happens?
3. Best fix for a duplicate you want merged into the main page?

Your action

Next, you will validate your XML sitemaps.

Key terms

Directive conflict
Two or more signals on the same URL that tell search engines different things.
Canonicalized URL
A page whose canonical tag points to a different URL.
Self-referencing canonical
A canonical tag pointing to the page's own URL, which confirms it as the preferred version.
Consolidation
Combining ranking signals from duplicate URLs onto one preferred URL.

Questions beginners ask

What does Google do with noindex plus canonical?

Google has said it may follow the noindex and pass that noindex to the canonical target, so you could accidentally deindex the main page. Avoid combining them.

Is noindex plus a self-referencing canonical a conflict?

It is contradictory but common. Google will usually follow the noindex. Clean it up so the page has one clear intent.

Should paginated pages use canonical or noindex?

Neither by default. Paginated pages should usually be indexable with self-referencing canonicals, so products on later pages can be found.

How do I find these conflicts quickly?

Filter your crawl for noindex pages and add the canonical column. Any noindex URL with a canonical to a different URL is a conflict.

Related lessons

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