/audit-technical

Runs technical SEO diagnostics, prioritizes issues, and packages remediation guidance.

BOOST

gtmagents@gtmagents

GitHub

From plugin

gtm-agents

407199 skills200 agents199 commands

Install

$ npx -y skills add gtmagents/gtm-agents --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/audit-technical

Context preview

What this command does when you run it.

Runs technical SEO diagnostics, prioritizes issues, and packages remediation guidance.

Command definition

audit-technical.md

name: audit-technical
description: Runs technical SEO diagnostics, prioritizes issues, and packages remediation guidance.
usage: /seo-workflow-orchestration:audit-technical --scope "core-web-vitals" --window 30d --detail full

Command: audit-technical

Inputs

**scope** – focus area (crawl, index, CWV, schema, hreflang, redirects).
**window** – data range (7d, 30d, 90d) for Search Console/log metrics.
**detail** – summary | full output detail.
**environment** – optional prod | staging to analyze releases.
**pages** – optional URL or directory filter for targeted audits.

Workflow

1. **Signal Collection** – pull Search Console, log files, crawler data, Lighthouse/CWV metrics for specified scope. 2. **Diagnostics** – run automated checks (status codes, render depth, CLS/LCP, schema validation, hreflang pairs). 3. **Impact Assessment** – quantify affected pages, traffic at risk, and business impact. 4. **Remediation Plan** – outline recommended fixes, owners, SLAs, and dependencies. 5. **Governance Logging** – document incidents, change requests, and QA requirements before deployment.

Outputs

Technical audit report (issue, severity, pages impacted, evidence links, proposed fix).
Ticket backlog or PRD with prioritized actions.
Monitoring plan (dashboards/alerts) for post-fix validation.