agentleFS
schweppsschwepps/skills/seo-technical-audit/SKILL.md

seo-technical-audit

Skill16 starsChanged 10 months agoMITView on GitHub

Professional technical SEO audit that analyzes crawlability, Core Web Vitals, site architecture, mobile readiness, security, structured data, and AI crawler configuration. Use when auditing websites for technical SEO issues, diagnosing indexation problems, or preparing comprehensive SEO reports.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-local, seo-schema and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mangollcSkill

    seo-local

    Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.

    Also in 5 projects that use this

  • megastepSkill

    seo-schema

    Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".

    Also in 5 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 3 projects that use this

  • 01claudingSkill

    seo-content-brief

    Generate comprehensive, SERP-driven content briefs for writers. Analyzes top-ranking competitors, identifies content gaps, specifies structure, word count, keywords, E-E-A-T requirements, AI citation readiness, and schema recommendations. Use when user says "content brief", "writing brief", "content outline", "article brief", or "create brief for".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check for warnings, not just errors

    line 126

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Technical SEO Audit Framework

Professional methodology for comprehensive technical SEO analysis aligned with 2025 best practices.

When to Use This Skill

  • Full technical SEO audits
  • Diagnosing crawling/indexation issues
  • Core Web Vitals analysis
  • Site architecture review
  • Schema markup validation
  • Mobile-first readiness assessment
  • AI crawler configuration audit

Audit Workflow

Execute in priority order—crawlability issues block all downstream optimizations.

Phase 1: Crawlability & Indexation (CRITICAL)

1. robots.txt Analysis
   □ Accessible at /robots.txt
   □ No global Disallow: /
   □ CSS/JS not blocked
   □ Sitemap reference present

2. XML Sitemap Validation
   □ Only canonical, 200-status URLs
   □ No noindex pages included
   □ Submitted to GSC

3. Indexation Status (GSC)
   □ Check indexed vs excluded pages
   □ Identify "Crawled - not indexed"
   □ Find soft 404s
   □ Verify canonical consistency

4. Meta Robots
   □ Key pages: index,follow
   □ No accidental noindex
   □ Canonical self-references

Phase 2: Core Web Vitals (2025 Standards)

Passing Thresholds:

MetricGoodNeeds ImprovementPoor
LCP≤2.5s2.5-4.0s>4.0s
INP≤200ms200-500ms>500ms
CLS≤0.100.10-0.25>0.25

Data Sources (Priority Order):

  1. Google Search Console (field data)
  2. CrUX Dashboard (field data)
  3. PageSpeed Insights (lab + field)

Common Fixes:

  • LCP: Optimize images, preload critical resources, reduce server response time
  • INP: Break up long tasks, optimize JavaScript, use web workers
  • CLS: Set dimensions on images/embeds, avoid inserting content above existing

Phase 3: Site Architecture

Optimal Structure:
□ Max 3 clicks from homepage to any page
□ Flat hierarchy (avoid deep nesting)
□ Logical URL structure: /category/subcategory/page
□ Breadcrumb navigation implemented
□ Internal linking strategy documented

URL Best Practices:
□ Descriptive, keyword-relevant
□ Lowercase, hyphens (not underscores)
□ Under 60 characters
□ No parameters when possible

Phase 4: Mobile-First Readiness

□ Mobile-friendly test passes
□ Responsive design (no horizontal scroll)
□ Touch targets ≥48px
□ Font size ≥16px base
□ No intrusive interstitials
□ Same content on mobile and desktop

Phase 5: Security & HTTPS

□ HTTPS with valid certificate
□ HTTP → HTTPS redirects (301)
□ No mixed content warnings
□ HSTS header implemented
□ Security headers present (CSP, X-Frame-Options)

Phase 6: Structured Data

Priority Schema Types:

  1. Organization/LocalBusiness
  2. BreadcrumbList
  3. Article/BlogPosting (with author)
  4. Product (for e-commerce)
  5. FAQPage (for AI visibility)
  6. HowTo (for tutorials)

Validation:

  • Google Rich Results Test
  • Schema.org validator
  • Check for warnings, not just errors

Phase 7: AI Crawler Configuration

2025 robots.txt for AI Search:

# Allow AI search crawlers
User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

# Optional: Block AI training (not search)
User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

Output Format

Generate reports using this structure:

# Technical SEO Audit Report

**Site:** [URL]
**Date:** [Date]
**Overall Score:** X/100

## Executive Summary
[2-3 sentence overview]

## Scores by Category

| Category | Score | Status |
|----------|-------|--------|
| Crawlability & Indexation | X/20 | [Good/Needs Work/Critical] |
| Core Web Vitals | X/20 | [Good/Needs Work/Critical] |
| Site Architecture | X/15 | [Good/Needs Work/Critical] |
| Mobile Readiness | X/15 | [Good/Needs Work/Critical] |
| Security & HTTPS | X/10 | [Good/Needs Work/Critical] |
| Structured Data | X/10 | [Good/Needs Work/Critical] |
| AI Crawler Readiness | X/10 | [Good/Needs Work/Critical] |

## Priority Issues (Fix First)
1. **[Issue]** - [Impact] - [Fix]
2. **[Issue]** - [Impact] - [Fix]
3. **[Issue]** - [Impact] - [Fix]

## Detailed Findings
[Category-by-category analysis]

## Action Plan

**Immediate (This Week):**
- [ ] Critical fix 1
- [ ] Critical fix 2

**Short-term (This Month):**
- [ ] High priority 1
- [ ] High priority 2

**Ongoing:**
- [ ] Monitoring task 1
- [ ] Regular audit 2

Scoring Guide

  • 90-100: Excellent - Minor optimizations only
  • 70-89: Good - Some improvements needed
  • 50-69: Needs Work - Significant gaps
  • Below 50: Critical - Major overhaul required

Quick Audit (5-Point Check)

For rapid assessments:

  1. Indexation - Are key pages indexed? (GSC)
  2. Speed - Core Web Vitals passing? (LCP <2.5s)
  3. Mobile - Mobile-friendly test pass?
  4. Security - HTTPS with valid cert?
  5. Crawlability - robots.txt not blocking content?

Tools Reference

# Check robots.txt
curl -s https://example.com/robots.txt

# Check response headers
curl -I https://example.com

# Fetch and validate sitemap
curl -s https://example.com/sitemap.xml | head -50

# Check mobile-friendliness (requires API key)
# Use Google's Mobile-Friendly Test: https://search.google.com/test/mobile-friendly

Additional Resources

For detailed checklists and schema patterns, ask for:

  • "Show me the full crawlability checklist"
  • "Give me JSON-LD schema examples"
  • "List all Core Web Vitals optimization techniques"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.