Skill

Perform Technical SEO Audits

A 9-category technical SEO audit skill covering crawlability, AI crawlers, indexability, security, CWV, and JS rendering.

Works with githubgoogle

89
Spark score
out of 100
Updated last month
Version 13.3.0

Add to Favorites

Why it matters

Conduct comprehensive technical SEO audits to identify and resolve issues impacting crawlability, indexability, performance, and rendering. Ensure optimal AI crawler management and adherence to modern SEO best practices.

Outcomes

What it gets done

01

Analyze robots.txt and sitemaps for AI crawler directives.

02

Evaluate indexability, canonicalization, and duplicate content issues.

03

Assess Core Web Vitals and mobile optimization for performance.

04

Review JavaScript rendering and structured data implementation.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-seo-technical | bash

Overview

Technical SEO Audit

A 9-category technical SEO audit skill covering crawlability, AI crawler management, indexability, security, Core Web Vitals, and JavaScript rendering correctness. Use it for infrastructure- and implementation-focused technical SEO review, not for content-quality analysis, which is handled by a separate content skill.

What it does

This skill runs a technical SEO audit across nine categories, focused on infrastructure and implementation rather than content. Crawlability checks robots.txt validity, XML sitemap presence, intentional vs accidental noindex tags, crawl depth (important pages within 3 clicks), JavaScript-dependent content, and crawl budget for large sites - including a dedicated AI crawler management section listing known bots (GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Bytespider, Google-Extended, CCBot) with the key distinction that blocking Google-Extended stops Gemini training use without affecting Google Search indexing or AI Overviews, since those use Googlebot. Indexability checks canonical tag consistency, duplicate/thin content, pagination, hreflang, and index bloat. Security checks HTTPS enforcement, CSP/HSTS/X-Frame-Options/X-Content-Type-Options/Referrer-Policy headers, and HSTS preload-list inclusion. URL structure checks clean hyphenated URLs, logical hierarchy, redirect chains (max 1 hop), and length. Mobile optimization checks responsive design, touch target sizing, minimum font size, and confirms mobile-first indexing is 100% complete as of July 5, 2024 (Google now crawls exclusively via the mobile Googlebot user-agent). Core Web Vitals checks LCP (<2.5s), INP (<200ms - explicitly noting INP replaced FID on March 12, 2024 and FID was fully removed from all Chrome tooling by September 2024, never to be referenced), and CLS (<0.1) at the 75th percentile of real user data. Structured data detection defers to a dedicated schema skill. JavaScript rendering checks distinguish CSR from SSR and flag SPA frameworks, incorporating Google's December 2025 JS SEO clarifications: canonical tags must match between server-rendered and JS-rendered HTML (Google may pick either if they conflict), a noindex present in raw HTML may still be honored even if JS removes it, JavaScript is never rendered on non-200 status pages, and time-sensitive structured data (especially Product/Offer) should ship in server-rendered HTML rather than being JS-injected. Finally it checks IndexNow protocol support for faster indexing on Bing/Yandex/Naver. Output is a Technical Score (0-100) with a pass/warn/fail breakdown per category and issues prioritized Critical to Low. If DataForSEO MCP tools are available, it can pull real page-status, Lighthouse, and technology-stack data.

When to use - and when NOT to

Use it for a technical SEO review focused on crawlability, indexability, performance, or rendering - auditing robots.txt, canonicalization, JavaScript SEO, Core Web Vitals, or AI crawler access - rather than a content-focused review. On an unreachable URL it reports the connection error; missing robots.txt is noted with a creation recommendation while the rest of the audit continues; missing HTTPS is flagged Critical; if CrUX data is unavailable (common for low-traffic sites) it uses Lighthouse lab data as a proxy and notes the limitation rather than fabricating field data.

Inputs and outputs

Inputs: a target site URL.
Outputs: a Technical Score with a pass/warn/fail breakdown across the nine categories, and issues prioritized Critical to Low with specific fixes.

Who it's for

SEO and technical teams who need an infrastructure-focused audit - crawlability, AI crawler policy, security headers, Core Web Vitals, and JS rendering correctness - separate from a content-quality review.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.