How to Run a Technical SEO Audit

A technical SEO audit is the process of checking whether search engines can crawl, index, understand, and rank the pages that matter. It covers infrastructure and page signals together: robots rules, sitemaps, canonicals, Core Web Vitals, mobile fit, HTTPS, structured data, internal links, and on-page tags.

The work is valuable because SEO defects compound silently. One stray noindex, broken canonical pattern, deep orphan page, or slow mobile template can suppress an entire section of a site. A good audit does not produce a long list of observations. It produces a prioritized fix queue with evidence, severity, and effort.

Why technical SEO quietly costs you

Technical SEO issues rarely announce themselves as a single clean failure. Rankings dip after a migration. Product pages stay discovered but not indexed. A template change creates duplicate canonicals across hundreds of URLs. Core Web Vitals degrade on mobile, but only on the page type that drives demos.

The cost comes from poor prioritization. Teams spend time polishing titles while revenue pages are blocked from indexing, or they inspect individual URLs when the real defect lives in a shared template. A useful audit separates measured evidence from estimates, then puts blocking indexation and revenue risks first.

What the manual process looks like

A disciplined technical SEO audit follows a repeatable sequence:

1. Define the site scope: primary domain, subdomains, priority URLs, templates, known symptoms, and available Search Console exports.
2. Crawl the scoped URLs and collect status codes, robots and sitemap signals, titles, metas, headings, canonicals, schema, and internal links.
3. For large URL sets, group pages by template and sample two or three URLs per pattern instead of auditing every URL by hand.
4. Run the nine audit areas: crawlability, indexability, Core Web Vitals, mobile, HTTPS/security, URL structure, structured data, internal linking, and on-page tags.
5. Label every metric as Measured, User-provided, Estimated, or N/A.
6. Score each area and rank issues P0, P1, or P2 with impact and effort.
7. Send the report for approval before anyone schedules fixes.

The audit is only as good as its evidence labels. An estimated crawl-depth issue and a measured noindex on a money page should not carry the same confidence.

What an agent can automate

The technical SEO audit playbook turns the audit into a workflow with explicit evidence handling:

• Crawl and scope. The agent reads the site map document, crawls public URLs, and prioritizes money pages and high-traffic templates.
• Sample by pattern. For five or more URLs sharing a template, it switches to bulk mode and reports pattern-level findings.
• Run the nine-area audit. It checks crawlability, indexability, Core Web Vitals, mobile, HTTPS/security, URL structure, structured data, internal links, and on-page tags.
• Respect decision gates. If the AI-crawler stance is unstated, it asks whether to allow all, block all, or allow retrieval while blocking training. It does not promise deprecated FAQ or HowTo rich results.
• Prioritize fixes. It ranks P0 blockers first, then P1 and P2 issues by impact, affected URLs, and effort.
• Compile the approval report. It produces a scorecard, one fix queue, quick wins, and monitoring plan without applying changes.

The agent reads public pages and available exports. It does not change the site.

The guardrails that make it safe

The first guardrail is evidence labeling. Every metric must be Measured, User-provided, Estimated, or N/A. If Search Console or PageSpeed data is missing, the agent says so instead of inventing a number.

The second guardrail is severity discipline. P0 means a blocker or revenue risk, not "important sounding". The self-check step forces every issue to carry concrete evidence, an exact fix, and a defensible severity before the report is written.

The third guardrail is human approval. The workflow ends with a report approval step. The human decides which fixes to schedule, which AI-crawler stance to take, and which recommendations fit the business.

Set it up in Task Machine

The Technical SEO audit playbook installs the SEO auditor agent, the crawl and audit workflow, the site map document, the site-health goal, and optional SEO data services. Setup takes a few minutes. You need a Task Machine workspace and permission to install playbooks (workspace owners have it). Search Console access can be added later. Until then, the agent works from attached exports and public-page crawl evidence.

1. Find the playbook

Open Playbooks and search for "technical SEO audit", or browse the SEO category. The card shows the SEO auditor, workflow, site map document, goal, skills, and optional SEO data services.

2. Preview what it installs

Preview & install opens the full contents before anything is created: the SEO Auditor, the Crawl, audit, prioritize, approve workflow, the Site map / domain list document, the Site health above target goal, the audit skills, and Ahrefs and Semrush as optional services.

3. Pick SEO data services

Start setup asks which SEO data providers the auditor should pull from: Ahrefs and Semrush. Pick at least one if you use those tools. Only the providers you pick are installed. Unpicked providers are not added to the workspace.

4. Define the site scope

Add the primary website URL, priority URLs or templates, known symptoms, and Search Console export notes. Put the highest-value templates first so the agent samples the right patterns before it inspects lower-impact pages.

5. Generate and review

Generate customized playbook creates the audit agent, workflow prompts, site map document, goal, skills, and selected services for review. Check that the generated workflow includes the evidence labels, nine audit areas, P0/P1/P2 severity model, AI-crawler decision gate, and human approval step.

6. Install

Install customized playbook creates the records in your workspace. Two follow-ups arrive in your inbox: prepare the crawl scope and start the Crawl, audit, prioritize, approve workflow. The first run gathers evidence, audits the scoped templates, self-checks severity, writes the report, and waits for approval before any fix is scheduled.

What good looks like

The audit is useful when three outputs are clear:

• A scorecard with evidence labels. The reader can tell what was measured, supplied, estimated, or unavailable.
• One prioritized fix queue. P0 indexation or revenue blockers appear before lower-impact polish.
• Template-level recommendations. Shared defects are tied to the affected template and URL count, not scattered as disconnected page notes.

Common questions

Does the agent change SEO tags or site code? No. It produces an audit report and fix queue for approval. Scheduling or applying fixes is a separate human decision.

Can it run without Search Console access? Yes. It can use public-page crawl evidence and attached exports. Missing field data is marked N/A instead of guessed.

Why does the playbook include Ahrefs and Semrush choices? Those services can add backlink, keyword, and site-health context alongside crawl evidence. Pick only the services you use.

Should the audit inspect every URL? For small sites, it can inspect the scoped URL set. For larger sites, template sampling is better because one shared template fix can affect many pages.