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

Technical SEO Audit vs. General SEO Audit

Covered here

  • What a general SEO audit covers that a technical audit does not
  • Where technical, on-page, content, and off-page audits overlap
  • Why the technical audit usually comes first
  • How to label findings so the right team fixes them

Short answer

A general SEO audit reviews everything that affects rankings: content, keywords, backlinks, and technical setup. A technical SEO audit focuses only on infrastructure, checking whether search engines can crawl, render, and index your pages. Run the technical audit first, because great content cannot rank on pages Google cannot reach.

When a client says “Can you audit my website?”, they rarely mean the same thing. A Legazpi hotel owner might mean “Why are we not on page one?” A developer might mean “What is broken?” Before you start, you need to know which audit you are doing, because each one asks different questions and produces different fixes.

The four parts of a general SEO audit

A general (or full) SEO audit looks at everything that affects rankings. It usually has four parts:

  1. Technical audit: Can search engines crawl, render, and index the site?
  2. On-page audit: Is each page optimized for its target keyword, with clear titles, headings, and internal links?
  3. Content audit: Does each page satisfy search intent, and is it accurate, useful, and better than competing pages?
  4. Off-page audit: Does the site have quality backlinks, brand mentions, and consistent local citations?

A technical SEO audit is one slice of that pie, done deeply.

Where the line sits

The easiest test is this: does the problem stop Google from accessing or understanding the page, or does it stop the page from deserving to rank?

  • A blocked folder in robots.txt is technical. Google cannot get in.
  • A thin product description is content. Google gets in, but the page is not good enough.
  • A 404 page with 30 backlinks pointing to it is both: a technical fix (redirect it) that recovers off-page value.

Some topics overlap. Title tags are a good example. In this course, you check them at scale: missing, duplicated, or truncated across 5,000 URLs. Whether a title is persuasive is a content and on-page question, covered in other courses.

Why the technical audit goes first

Think of a sari-sari store with a locked door. Restocking the shelves does not help if nobody can enter. In the same way:

  • Content improvements are wasted on pages that carry a noindex tag.
  • New backlinks lose value if they point to URLs that redirect three times.
  • Keyword optimization does nothing if the main text only loads after JavaScript Google fails to render.

So the usual order is technical first, then on-page and content, then off-page. A full audit can run them in parallel, but technical blockers are fixed first.

Practice: which audit owns this finding?

Sort each item into the right group.

  • 1,200 pages have duplicate title tags from one template

  • Service page does not explain prices or coverage areas

  • XML sitemap lists URLs that return 404

  • Competitors have links from Bicol tourism sites, you have none

  • Blog post targets the wrong search intent

  • Mobile pages hide the main content behind a script error

  • Business name is spelled differently across directories

Common mistakes

  • Selling a “technical audit” that is really a keyword report. Set expectations in writing.
  • Mixing all findings in one list. Developers ignore reports full of content advice. Label each finding by audit type and owner.
  • Skipping technical checks on content-led sites. Blogs break too, especially after theme or plugin updates.
  • Judging writing quality in a technical audit. Flag duplicates and missing tags, then hand quality questions to the content team.
1. Which finding belongs in a technical SEO audit?
2. Why do most auditors run the technical audit first?
3. In a technical audit, what do you check about title tags?

Your action

Next, you will learn when a website actually needs an audit, and which events should trigger one immediately.

Key terms

General SEO audit
A full review of a site's search performance, covering technical health, content quality, keyword targeting, and backlinks.
Content audit
A review of whether each page satisfies search intent, is accurate, and deserves to rank.
Off-page audit
A review of signals outside your site, mainly backlinks, brand mentions, and local citations.
Technical on-page
Page-level HTML elements, like title tags and headings, checked for presence and duplication at scale rather than for writing quality.

Questions beginners ask

Which audit should a new website get first?

The technical audit. It confirms that pages can be crawled and indexed. Content and backlink work only pays off once that foundation is in place.

Are title tags technical SEO or content SEO?

Both. A technical audit checks whether titles are missing, duplicated, or too long across thousands of URLs. A content audit checks whether each title matches search intent and earns the click.

Can one person do both audits?

Yes, on small sites. On larger sites, the technical audit often goes to developers and the content audit to writers, so separating findings makes delegation easier.

Does a technical audit include backlinks?

Usually not. Backlink analysis belongs to the off-page audit. A technical audit only looks at links when they cause crawling problems, such as internal links pointing to redirects or broken pages.

Related lessons

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