Technical SEO

Technical SEO Audit: The Complete Foundation Guide

A complete reference for auditing technical SEO foundations before any content or link work.

SRConsoleBoard SEO Research๐Ÿ“… Published October 1, 2026โฑ 14 min read

A technical SEO audit examines the structural foundation of a website โ€” how search engines crawl, render, index, and understand it. Before any content investment or link-building work, the technical layer must be sound. This cornerstone guide defines the audit areas, the tools, and the order of operations for a local business website. It anchors our Technical SEO category.

It is written for SEO professionals and agencies who manage local sites. ConsoleBoard is mentioned only where the platform performs a specific operation described in the text.

The five audit areas

A technical audit covers five connected areas. A problem in one often surfaces as a symptom in another, so audit them together rather than in isolation.

AreaWhat it examinesPrimary tool
Crawlabilityrobots.txt, crawl directives, server responsesGoogle Search Console + crawler
IndexationWhat Google has indexed vs. what it shouldSearch Console Coverage report
ArchitectureURL structure, internal links, canonicalsSite crawl + Search Console
Structured dataSchema markup validity and richnessRich Results Test
SpeedCore Web Vitals, render-blocking, asset weightPageSpeed Insights

Crawlability and indexation

Crawlability asks whether Googlebot can reach your pages. Check robots.txt for accidental blocks on important paths, confirm meta robots tags are not set to noindex on pages you want indexed, and verify the server returns HTTP 200 (not 5xx errors or redirect chains) for canonical URLs. Google documents how robots.txt controls crawling in its Search Central documentation.

Indexation asks whether Google has actually included those pages in its index. Use the Search Console Coverage report to see indexed, excluded, and error URLs. A page can be crawlable but not indexed โ€” common reasons include duplicate content, thin content, or a canonical pointing elsewhere. See our Index Coverage Checklist for the full procedure.

Site architecture and internal links

A sound local site architecture separates service pages (what you do) from location pages (where you do it), links them contextually, and avoids near-duplicate pages that cannibalize each other. Every page should be reachable within a few clicks from the homepage. Audit for orphan pages (pages with no internal links pointing to them), redirect chains, and broken links.

Canonical tags must point to the preferred URL on every page. Self-referencing canonicals are the default; cross-domain canonicals should be deliberate. See Canonical Tags for Local Sites for common mistakes. Run the Internal Linking Audit Checklist as part of this area.

Structured data and schema

Structured data helps Google understand the entities on a page. For local businesses, LocalBusiness schema is the baseline โ€” it carries name, address, phone, hours, and geo coordinates. Validate it with the Rich Results Test and fix any errors before launch. See our Schema Markup Checklist for Local Businesses.

Speed and Core Web Vitals

Core Web Vitals are Google's field-data metrics for loading (LCP), interactivity (INP), and visual stability (CLS). Google documents them in Search Central. Audit with PageSpeed Insights, which shows both lab and field data. Prioritize fixes by impact: render-blocking resources, large images, and layout shift. See the Page Speed and Core Web Vitals Checklist.

Order of operations

  1. Crawl the site to map all URLs and find structural issues.
  2. Check indexation in Search Console to see what Google actually has.
  3. Validate structured data with the Rich Results Test.
  4. Measure Core Web Vitals with PageSpeed Insights.
  5. Prioritize findings by effort and expected effect.

Limitations

An audit is a point-in-time snapshot. Crawl errors, indexation, and Core Web Vitals change continuously. Re-audit quarterly or after any major site change. Audit findings identify risk and opportunity โ€” they do not predict ranking outcomes. See our content methodology for how findings are reported.

Primary sources