Skip to content
TrustedSkillsbeta
Back to all skills

Seo Technical Audit

Listed
schwepps·vlatest·marketing·MIT

Helps with SEO, auditing as part of marketing, SEO, and growth tasks workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add schwepps/skills --skill seo-technical-audit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

schwepps

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 4 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.ssllabs.com, validator.schema.org, www.googleapis.com, www.webpagetest.org.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.ssllabs.comundeclaredwww.googleapis.comundeclaredwww.webpagetest.orgundeclaredvalidator.schema.orgundeclared

    What it found (3 of 6)

    • seo-technical-audit/references/tool-commands.md:44contacts api.ssllabs.com
      curl "https://api.ssllabs.com/api/v3/analyze?host=example.com"
    • seo-technical-audit/references/tool-commands.md:163contacts www.googleapis.com
      curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://example.com&strategy=desktop&key=YOUR_API_KEY"
    • seo-technical-audit/references/tool-commands.md:166contacts www.googleapis.com
      curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://example.com&strategy=mobile&key=YOUR_API_KEY"

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned schwepps/skills at 8aa9a4e0ee.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
8aa9a4e0ee
Manifest
seo-technical-audit/SKILL.md
Scanned
4 files, 1,058 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides a framework for conducting comprehensive technical SEO audits, aligning with best practices expected in 2025. It enables AI agents to systematically analyze website crawlability, indexation, Core Web Vitals, site architecture, mobile-friendliness, security, structured data implementation, and AI crawler configurations. The process is designed to identify and diagnose issues impacting search engine visibility and performance.

When to use it

  • Performing full technical SEO audits for websites.
  • Diagnosing crawling or indexation problems that are hindering site appearance in search results.
  • Analyzing Core Web Vitals (LCP, INP, CLS) to ensure a good user experience.
  • Reviewing website architecture and URL structure for optimal navigation and SEO.
  • Validating the implementation of schema markup for enhanced rich result visibility.

Key capabilities

  • Crawlability & Indexation Analysis: Robots.txt analysis, XML sitemap validation, indexation status checks (using Google Search Console).
  • Core Web Vitals Assessment: Evaluation of LCP, INP, and CLS metrics using data from Google Search Console, CrUX Dashboard, and PageSpeed Insights.
  • Site Architecture Review: Analysis of URL structure, internal linking strategy, and navigation depth.
  • Mobile-First Readiness Check: Verification of mobile usability and responsiveness.
  • Schema Markup Validation: Testing and validation of structured data using Google's Rich Results Test and Schema.org validator.
  • AI Crawler Configuration Audit: Reviewing robots.txt to ensure proper access for AI search crawlers (e.g., OAI-SearchBot, ChatGPT-User).

Example prompts

  • "Perform a technical SEO audit of [website URL]."
  • "Analyze the Core Web Vitals performance for [website URL] and suggest improvements."
  • "Check the XML sitemap for [website URL] and identify any errors."
  • “Review the robots.txt file for [website URL] to ensure AI crawlers can access all content.”

Tips & gotchas

  • The audit workflow should be executed in priority order, starting with crawlability issues as they impact subsequent steps.
  • Data sources are prioritized: Google Search Console (field data) is considered the most important, followed by CrUX Dashboard and PageSpeed Insights.
  • Focus on warnings during schema validation, not just errors, as these often indicate areas for improvement.