Technical SEO Audit: 5 Steps + Free Template (2026)

Last updated: Q2 2026.

When Ahrefs crawled more than a million domains for its Site Audit study, it found slow pages on 72.3% of them and a 3XX redirect issue on 95.2%. Technical problems are not rare edge cases. They sit on almost every site, quietly capping how much of your content Google can crawl, render, and rank.

The trouble is that most technical SEO audits produce a 200-line spreadsheet of red flags that nobody ever acts on. A list of problems is not an audit. The audit that moves rankings is the one you finish: crawl, diagnose, prioritize, fix, and verify, in that order, with a clear rule for what to fix first.

This guide walks through that exact process, the tools to use at each stage, an impact-versus-effort model for triaging what you find, and a downloadable audit template you can run on your own B2B site today. For the line-item inventory of every check, our technical SEO checklist for B2B sites is the companion piece. This article is how to actually run the audit.

What Is a Technical SEO Audit?

A technical SEO audit is a structured review of the infrastructure that lets search engines find, crawl, render, index, and rank a website, covering crawlability, indexation, site architecture, page speed and Core Web Vitals, mobile-first readiness, structured data, and security. It diagnoses why pages underperform for reasons that have nothing to do with the words on the page.

It is worth being precise about scope, because the word “audit” gets stretched to mean everything. A technical audit asks one question: can search engines access and understand this site cleanly? It does not assess whether your content matches search intent, and it does not review your backlink profile. Those are real audits too, just different ones, and a strong B2B SEO strategy treats technical health as the foundation the other two sit on.

Throughout this guide we use one named method, the Crawl-to-Verify loop: five stages that take you from raw crawl data to confirmed fixes. It is a loop rather than a checklist because a technical site changes every time you publish, redirect, or add a tool, so the audit is something you re-run, not something you finish once.

Technical SEO Audit vs On-Page and Backlink Audits

A technical SEO audit, an on-page or content audit, and a backlink audit answer three different questions, and running the wrong one wastes a week. Use this table to confirm you are auditing the layer that is actually holding rankings back.

The three overlap at the edges. A page that renders blank in Google’s render queue is a technical problem that looks like a content problem, and a slow page is a technical issue that drags on conversions a content audit would never catch. When intent and depth are the real gap, that work lives in your content strategy for SEO, where mapping pages to buyer intent is the job, not in the crawl.

The Technical SEO Audit Process: The Crawl-to-Verify Loop

To run a technical SEO audit, work through five stages in order: crawl the site, diagnose the findings against benchmarks, prioritize them by impact and effort, fix the highest-impact issues, then verify the fixes held. Skipping the prioritize stage is why most audits stall, the team drowns in a flat list of 300 issues with no signal about which three actually matter.

Stage 1: Crawl the Site

Crawling means running a desktop crawler over your site the way Googlebot would, to build a complete map of every URL and its technical state. Start with Screaming Frog, free up to 500 URLs and unlimited on a paid licence, or Sitebulb if you want guided explanations. Set the user-agent to Googlebot, turn JavaScript rendering on, and let it finish.

Export everything: status codes, indexability, canonical tags, redirect chains, response times, title and meta length, and orphan candidates. The first pass is about coverage, not judgment. You want one row per URL so the diagnose stage has a complete picture, and you want a benchmark crawl saved so the next audit can show what changed. For a deeper view of which crawlers fit which job, our roundup of the tools that handle crawling, log analysis, and monitoring compares the options.

Stage 2: Diagnose Against Benchmarks

Diagnosing means comparing crawl data against the reports and thresholds that tell you what “healthy” looks like, so you keep the real issues and drop the false alarms. A crawler flags symptoms; Search Console tells you what Google actually did with each page. Open the Page indexing report and reconcile it against your crawl: pages you want indexed that sit in “Crawled, currently not indexed” or “Discovered, currently not indexed” are crawl-budget and quality signals worth chasing.

This is also where the render check matters. Google crawls a page, queues it for rendering when resources allow, then indexes the rendered HTML, so JavaScript-dependent content can be delayed or missed entirely. Use the URL Inspection tool to view the rendered HTML and confirm your key content and links are present. For large sites, Google defines crawl budget as crawl capacity plus crawl demand, which becomes a real constraint past roughly a million pages or on sites that change daily.

Page speed gets a hard benchmark from Core Web Vitals, measured at the 75th percentile of real visits. Google’s thresholds are LCP at or under 2.5 seconds, INP at or under 200 milliseconds, and CLS at or under 0.1, with INP having replaced First Input Delay in March 2024. Read these from field data in PageSpeed Insights or the Chrome UX Report, not just lab scores, because lab numbers miss the slow render your real buyers feel.

Stage 3: Prioritize by Impact and Effort

Prioritizing means scoring each finding so the team works the few issues that move rankings before the many that do not. This is the stage every competitor and every tool skips, and it is the difference between an audit that ships and a report that rots. A crawler will happily hand you 300 issues with equal-looking red icons; your job is to rank them.

Plot each finding on an impact-versus-effort grid. High-impact, low-effort issues are quick wins you fix this week. High-impact, high-effort issues are scoped projects you brief into the dev backlog. Low-impact issues wait, regardless of how many a crawler flagged. A single robots.txt line blocking your resources section is a P0 even though it is one row, while 4,000 missing alt attributes are a real but low-priority cleanup.

Stage 4: Fix the Highest-Impact Issues

Fixing means assigning each prioritized finding an owner and shipping it, which is where most B2B audits break because no one decided whether marketing or engineering owns the work. Crawlability and indexation fixes (robots.txt, canonicals, redirects, sitemaps) usually sit with marketing or SEO. Core Web Vitals, JavaScript rendering, and server response belong to engineering. Name the owner on every row before you hand the audit over.

Ship the quick wins immediately and scope the rest as tickets with enough context that a developer who has never read your audit can act on them. “INP is 480ms on the demo-request template, caused by a third-party chat script blocking the main thread” is a ticket. “Improve page speed” is not.

Stage 5: Verify and Monitor

Verifying means confirming each fix worked and setting up monitoring so it cannot silently regress. Use the Validate Fix flow in the Search Console Page indexing report, re-crawl the affected URLs, and re-test Core Web Vitals once field data refreshes. A fix you did not verify is a fix you are guessing about.

Then close the loop. Schedule a re-crawl on a cadence and watch status codes and indexation between full audits, because the next CMS update or new landing-page tool will reintroduce the same problems. That is why this is the Crawl-to-Verify loop and not a one-time checklist.

The Technical SEO Audit Checklist (With Pass/Fail Thresholds)

This is the working checklist behind the audit: each check paired with why it matters, the tool that finds it, the threshold that decides pass or fail, and a priority tier. Copy it into your own sheet, or download the editable version below, and score every row as you work the five stages. It is the scoresheet competitors describe but never hand over.

The thresholds are the part most checklists omit. “Check your page speed” is advice; “LCP at or under 2.5s at the 75th percentile” is a test you can pass or fail. For the deeper, item-by-item explanation of how to fix each line, including B2B-specific schema types and the quarterly maintenance schedule, work alongside the full technical SEO checklist, which catalogs every check this audit scores.

Tools for Each Stage of the Audit

A technical SEO audit needs a crawler, Search Console, a speed tool, and a validator at minimum, and you can run a credible audit on free tiers alone. The point is matching the tool to the stage rather than buying one platform and hoping it covers everything.

Use a desktop crawler (Screaming Frog or Sitebulb) for stage one, Search Console and PageSpeed Insights for diagnosis, and a cloud auditor (Ahrefs or Semrush) when you want scheduled re-crawls that handle the verify-and-monitor stage automatically. There is also a newer layer worth auditing: whether AI engines can read you. Our guide to AI SEO tools and GEO platforms covers checking AI-crawler access and citation visibility, the technical groundwork for showing up in ChatGPT and Perplexity answers.

How Often Should You Run a Technical SEO Audit?

Run a full technical SEO audit once or twice a year, a quarterly spot-check on your highest-value pages, and a dedicated audit before and after any migration. Match the depth to the trigger rather than auditing everything every time, which is how audits become busywork nobody repeats.

The pre-migration case is the one teams regret skipping. A replatform without a verified redirect map and a before-and-after crawl is the single fastest way to erase years of rankings overnight, so treat any migration as a mandatory two-audit event rather than a hopeful launch.

B2B Technical SEO Audit Gotchas Generic Audits Miss

B2B sites break in places a generic audit never looks, because the stack is built for lead capture, not for crawlers. The marketing-automation tools, gated assets, and CRM embeds that run a B2B funnel each introduce a technical failure mode of their own. These are the checks worth adding to the standard list.

The usual offenders are marketing-automation URLs that spawn near-duplicate pages with tracking parameters, gated content stuck behind forms that crawlers never get past, and JavaScript-rendered demo and contact forms whose content sits in the render queue rather than the initial HTML. Multi-subdomain setups (a HubSpot blog on a subdomain, a separate app domain) split authority, and a staging site that ships with Disallow: / or a stray noindex can quietly deindex production after a deploy.

None of these appear on a stock checklist, yet on a B2B site they are often the highest-impact findings in the whole audit. A demo-request page that renders blank to Googlebot is worth more attention than fifty cosmetic warnings, which is exactly why the prioritize stage matters as much as the crawl.

DIY vs Hiring a Technical SEO Audit Service

Run the audit yourself when you have the tools and a few focused hours; hire a technical SEO audit service when the site is large, a migration is at stake, or no one in-house owns technical SEO. The five-stage loop in this guide is genuinely runnable by an in-house marketer, and for most mid-market B2B sites a self-run audit each quarter catches the issues that matter.

Cost scales with site complexity rather than a fixed sticker. Ahrefs’ survey of SEO providers puts agency work near $99 an hour and consultants around $171, so a small-site audit of a few hours and a large enterprise audit of forty-plus hours sit far apart on price. Agency estimates for a standalone technical audit commonly range from roughly $500 to $15,000 depending on scale, though that range is illustrative rather than a published standard.

Outsource when the stakes or the scale outrun your time, not by default. When you do, choosing a partner is its own evaluation, and our rundown of B2B SEO agencies worth shortlisting walks through how to vet one on technical depth rather than retainer size. The right move for many teams is a hybrid: run quarterly spot-checks in-house and bring in specialists for migrations and annual deep audits.

Frequently Asked Questions