Skip to main content

Technical SEO audit

A technical SEO audit evaluates the crawlability, indexability, rendering, performance, architecture, and structured data quality of a website. The goal is to identify technical barriers that prevent important pages from ranking and to prioritize fixes by their likely business impact — not by the number of crawl warnings in a tool report.

Learning objectives​

After completing this module, you will be able to:

  • Systematically audit technical SEO across all major technical dimensions.
  • Distinguish urgent technical issues from low-priority warnings.
  • Connect technical findings to business impact.

The technical audit mindset​

Most crawl tools generate hundreds of warnings. Most of these warnings do not matter. A technical SEO audit is a triage exercise:

  • Which issues prevent important pages from being indexed?
  • Which issues reduce page quality or user experience at scale?
  • Which issues waste crawl budget on low-value URLs?

Fix what matters. Document what doesn't for later review.

Crawlability review​

Robots.txt​

  • Does robots.txt block any important paths?
  • Are there paths that should be blocked but are not?
  • Is the sitemap referenced in robots.txt?

Test: Fetch yourdomain.com/robots.txt and review every Disallow rule. Verify against your most important page types.

Redirect chains and loops​

  • Chains of more than 2 hops slow crawling and dilute equity.
  • Loops (A → B → A) create permanent crawl failures.

Test: Crawl with Screaming Frog and filter to redirects. Review the redirect chain length for each.

  • Internal links pointing to 404 pages waste crawl resources.
  • High volume of 404s from important pages reduces internal link equity.

Test: Crawl report → internal links → filter by destination status = 404.

Server availability​

  • Consistent 5xx errors during crawl prevent indexation.
  • Slow server response times reduce crawl rate.

Test: Check GSC Crawl Stats report for server response time and crawl errors. Use server monitoring to confirm uptime.

Indexability review​

Canonical tags​

  • Every important page should self-reference its canonical.
  • No important page should canonical to a different URL unintentionally.
  • Canonical targets must be indexable, accessible, and return 200.

Test: Export canonical tags from crawl. Review for self-referencing canonicals on priority pages. Check GSC → "Google chose different canonical" for conflicts.

Noindex directives​

  • Review which pages carry noindex. Are they all intentional?
  • Are there any important pages accidentally noindexed?

Test: Crawl filter → noindex → review against intended indexation plan.

XML sitemaps​

  • Sitemaps should include only canonical, indexable URLs.
  • Review submitted vs indexed ratio in GSC Sitemaps report.
  • Remove redirected, noindex, and non-canonical URLs from sitemaps.

Index coverage review in GSC​

Review all exclusion categories:

  • "Crawled — currently not indexed" → quality or content issues.
  • "Discovered — currently not indexed" → crawl priority issue.
  • "Duplicate without user-selected canonical" → canonicalization needs improvement.

Rendering review​

JavaScript rendering check​

For JavaScript-heavy sites:

  • Use URL Inspection "Test Live URL" to see rendered HTML vs source HTML.
  • Verify that important content (navigation, headings, body text) appears in rendered HTML.
  • Confirm that internal links in rendered content are crawlable.

Mobile usability​

  • Confirm all important templates pass mobile usability test in GSC.
  • Test viewport, tap targets, and font sizes on representative URLs.

Core Web Vitals review​

  • Review GSC Core Web Vitals report by template type (desktop and mobile).
  • Identify templates with "Poor" or "Needs Improvement" status.
  • Use PageSpeed Insights and Chrome UX Report to identify LCP, INP, and CLS issues.
  • Prioritize by traffic volume × failing CWV score.

Structured data review​

  • Validate schema on key templates using Rich Results Test and GSC Enhancements.
  • Confirm schema matches visible page content.
  • Review schema for pages with rich result eligibility (Product, Recipe, FAQ, Article, etc.).
  • Fix critical errors before warnings.

Checklist​

  • Important pages are crawlable (not blocked by robots.txt or authentication).
  • Important pages are indexable (no noindex, correct canonical, no major quality issues).
  • Sitemaps include only canonical, indexable URLs.
  • Redirect chains are minimized.
  • CWV issues are identified by template and mobile/desktop.
  • Structured data validates for all key schema types.

Measurement​

MetricWhat it tracks
Crawl error URL countTechnical crawlability issues
Indexed URL count vs expectedIndexation completeness
CWV pass rate by templatePerformance health
Redirect chain countRedirect efficiency
Schema error countStructured data implementation quality
"Crawled not indexed" trendQuality signal alerts

Common mistakes​

Treating every tool warning as urgent. A "meta description too long" warning on 2,000 category pages is a low-priority cosmetic issue. Treating it as urgent obscures truly critical issues.

Ignoring templates and focusing only on individual pages. A canonical tag error on a product template may affect 100,000 pages. Always think at the template level, not the page level.

Not comparing crawler data with Search Console. A crawler reports what it sees; GSC reports what Google sees. These may differ significantly for JS-rendered content. Always cross-reference both data sources.

Missing JavaScript-rendered content issues. Static crawl tools see pre-render HTML. Important content rendered only via JavaScript may appear in the crawl as present but be invisible to Google. Always verify rendered output.

Confusing crawl warnings with SEO failures. A "missing alt text" warning on 500 image links is worth fixing over time — but it is not causing a traffic drop or blocking indexation. Focus audit energy on issues that block business outcomes.