Skip to content
Enjoy 20% off for 12 months on all plans. Use promo code: HYPERGROWTHClaim it
Help

Run the Technical SEO audit

The deep infrastructure audit: a health score, every check filed as To fix, Needs review or Passed, and the fix for each failure.

Open in the appUpdated 2026-10-12

Overview

The Technical SEO audit crawls your site and works through a fixed checklist of infrastructure checks: indexability, redirects, status codes, canonicals, meta tags, sitemaps, security headers, page weight, internal linking, and more. Every failing check names the pages it affects and the fix.

It answers one question: is anything broken at the level that makes the rest of SEO pointless?

When to use this

Run it after a migration or redesign, the first time you take on a site, or whenever the main report's Technical discipline scores below a B. For choosing between this and the other deep audits, see choosing between the deep audits.

How it works

  1. It crawls. It reads your sitemap and internal links and crawls the number of pages you choose: 10, 25 or 50, your homepage among them. The card says how many eligible pages your site has and offers only the sizes it can fill, such as "All 18 pages". On a larger site it chooses a representative sample.
  2. It runs the checklist on every crawled page, in eight groups: crawl and indexing; titles, meta and headings; internal linking; images and page experience; mobile and HTTPS; errors and redirects; structured data; and international and other.
  3. It files every check. A failure goes under To fix, a warning under Needs review, and a pass under Passed. A check the crawl could not read goes under Not verified and counts as neither a pass nor a fail.
  4. It scores the result. The health score out of 100 weighs each failure by its severity (Critical, High, Medium, Low) and by the share of pages it affects.

Steps

To run a Technical SEO audit:

  1. Open your website, then Deep Audits under Site Audit, and pick the Technical SEO tab. You can also go to Tools and pick Technical SEO Audit.
  2. Select Run Technical SEO Audit and leave it to work. A run takes up to 5 minutes.
  3. The report saves against the website when it finishes. Re-run audit starts a fresh one.

Understand the results

The health card shows the Health score, a one-line verdict, and Compared to previous audit with the change in points. Below it, Audit findings lists every check in the four tabs, with search, an issue-type filter and a sort.

Open a finding to see What the audit found, Why it matters, Where it happens (or Across the site), the Recommended fix with a code Example where one applies, and How to check it's fixed. On WordPress, Wix, Shopify, Squarespace and Webflow sites the fix also has steps for that builder.

Export downloads the findings as Excel, a PDF, or both in one zip. Open full report opens the workbook, where every check is a permanent row, so two audits line up row by row.

Sample output

This is an example on a made-up website, not a real report:

Health score 74
Your site needs some attention: 6 issues to fix and 3 checks to review.
Compared to previous audit: +5 points

To fix (6) · Needs review (3) · Passed (41) · Not verified (2)

High · Canonical tag points to a redirecting URL
What the audit found: 12 pages declare a canonical that redirects (301).
Where: /services/roof-repair/, /services/gutters/ and 10 more
Recommended fix: point each canonical at the final URL.
Example: <link rel="canonical" href="https://www.example.com/services/roof-repair/">
How to check it's fixed: the canonical URL answers 200 with no redirect.

What to do with the results

To work through a Technical SEO audit:

  1. Open the To fix tab and start with the Critical and High findings. What's next? names how many there are.
  2. Open each finding and apply the Recommended fix, or send the finding to your developer with its Example and affected pages.
  3. When the changes are live, select Re-run audit. The next run checks each fix against the live site.
  4. Compare: Compared to previous audit shows the change in points, Health score trend shows the runs over time, and View history opens every saved run.

Limits and usage

  • The crawl covers the 10, 25 or 50 pages you choose (5, 12 or 23 credits). Pages outside that number are not checked; the report says how many.
  • A run stops at 5 minutes and costs 5 credits. A run that fails is not charged. See plans and credits.
  • Rate limited per account, like the other deep audits.

Troubleshooting

The run finishes with very few pages crawled

Your site is likely blocking the crawler. See fix an audit that failed or came back empty.

A check fails that you believe you fixed

Re-run the audit rather than editing the workbook row: the row reflects the crawl it came from, and the next run checks it again against the live site.

A JavaScript-heavy page reads as empty

The crawler renders JavaScript where it detects the need, but a page that requires a click to show its content is checked as it arrives over the network.

Was this page helpful?

Still stuck?

Email us and the team replies from the same address. If you're signed in, Ask anything in the app answers from these guides.

hello@searchblueprint.ioAsk in the app