agentleFS
architshahdigitalarchitshahdigital/claude-marketing-skills/skills/seo-technical-audit/SKILL.md

seo-technical-audit

Skill0 starsChanged 4 months agoLicence not identifiedView on GitHub

Run a technical SEO audit of a website and return a prioritized fix list — crawlability, indexation, site architecture, Core Web Vitals / page speed, mobile, and structured data. Use when the user wants a site audited, rankings are stalling for non-content reasons, a migration or redesign needs checking, or Core Web Vitals are failing. Produces a scored audit with issues ranked by impact × effort. Triggers on: "technical SEO", "site audit", "Core Web Vitals", "page speed", "crawl issues", "indexing problem", "why isn't my site ranking", "SEO health check".

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

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“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.

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.