agentleFS
ninrytninryt/seo-analysis-skill/SKILL.md

seo-analysis

Skill0 starsChanged 6 months agoMITView on GitHub

SEO and web/mobile audit workflows : website audits, single-page audits, technical SEO, content quality, E-E-A-T, AI search/GEO readiness, schema, XML sitemaps, image optimization, hreflang, competitor comparison pages, programmatic SEO, and SEO strategy. Foundation skill : Nina will build on top of it as audits come up. Trigger when Nina mentions auditing a website, landing page, app landing page, app store listing, or competitor site; planning SEO work; reviewing content for search or AI-citation readiness; generating schema or sitemaps; or asking for a "web audit", "mobile audit", "competitor audit", or "SEO audit". Does NOT cover UX/UI heuristic evaluation, usability testing, or in-product user-flow audits : those are a separate discipline.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. nowork-studio/toprank★ 4.1ksame name
    2. nowork-studio/notfair-plugin★ 4.1ksame name
    3. infranodus/skills★ 126same name
    4. jpcaparas/skills★ 53same name
    5. agencia-conversion/agentic-seo-skills★ 51same name
    6. YepAPI/skills★ 8same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 1 is distinctive, and 13 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.

  • 13

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read references/seo-workflows.md when you need the detailed workflow list, scoring areas, outputs, or quality checks.

    line 12
  2. Very specific:

    Use seo-audit for full-site SEO health checks and prioritized action plans.

    line 16
  3. Very specific:

    Use seo-page for one landing page, article, product page, campaign page, or app landing page.

    line 17
  4. Very specific:

    Use seo-content for E-E-A-T, helpfulness, readability, thin content, intent coverage, and AI citation readiness.

    line 18
  5. Very specific:

    Use seo-technical for crawlability, indexability, robots.txt, Core Web Vitals, mobile, JavaScript rendering, security, structured data …

    line 19
  6. Very specific:

    Use seo-schema for Schema.org detection, validation, and JSON-LD generation.

    line 20
  7. Very specific:

    Use seo-sitemap for XML sitemap validation or generation.

    line 21
  8. Very specific:

    Use seo-images for alt text, file size, formats, responsive images, lazy loading, CLS prevention, and CDN usage.

    line 22
  9. Very specific:

    Use seo-hreflang for international SEO and language/region targeting.

    line 23
  10. Very specific:

    Use seo-competitor-pages for "X vs Y", "alternatives to X", comparison tables, and "best tools" pages.

    line 24
  11. Very specific:

    Use seo-programmatic for pages generated at scale from structured data, including quality gates against thin content and index bloat.

    line 25
  12. Very specific:

    Use seo-geo for AI search visibility in ChatGPT, Perplexity, Google AI Overviews, and similar answer engines.

    line 26
  13. Very specific:

    Use seo-plan for SEO roadmaps, content strategy, competitor research, and implementation sequencing.

    line 27
  14. Very specific:

    When working inside a marketing-analysis project, keep SEO artifacts organized under an seo/ folder:

    line 42

“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

SEO Analysis

Quick Start

Select the narrowest workflow that matches the request. If the user asks for a full audit, start with seo-audit, then deepen with specialist workflows where issues appear.

Read references/seo-workflows.md when you need the detailed workflow list, scoring areas, outputs, or quality checks.

Workflow Picker

  • Use seo-audit for full-site SEO health checks and prioritized action plans.
  • Use seo-page for one landing page, article, product page, campaign page, or app landing page.
  • Use seo-content for E-E-A-T, helpfulness, readability, thin content, intent coverage, and AI citation readiness.
  • Use seo-technical for crawlability, indexability, robots.txt, Core Web Vitals, mobile, JavaScript rendering, security, structured data presence, AI crawler management, and IndexNow.
  • Use seo-schema for Schema.org detection, validation, and JSON-LD generation.
  • Use seo-sitemap for XML sitemap validation or generation.
  • Use seo-images for alt text, file size, formats, responsive images, lazy loading, CLS prevention, and CDN usage.
  • Use seo-hreflang for international SEO and language/region targeting.
  • Use seo-competitor-pages for "X vs Y", "alternatives to X", comparison tables, and "best tools" pages.
  • Use seo-programmatic for pages generated at scale from structured data, including quality gates against thin content and index bloat.
  • Use seo-geo for AI search visibility in ChatGPT, Perplexity, Google AI Overviews, and similar answer engines.
  • Use seo-plan for SEO roadmaps, content strategy, competitor research, and implementation sequencing.

Standard Output

For most SEO tasks, produce:

  1. Executive summary.
  2. Priority table: issue, severity, affected area, evidence, recommendation, expected impact.
  3. Detailed findings grouped by workflow area.
  4. Quick wins versus deeper work.
  5. Measurement plan: rankings, impressions, CTR, indexed pages, conversions, revenue, or ASO/web landing-page metrics as relevant.
  6. Next actions with owner-friendly wording.

Project Fit

When working inside a marketing-analysis project, keep SEO artifacts organized under an seo/ folder:

seo/
  audits/
  notes/
  reports/
  templates/
  scripts/

For mobile app work, use this skill for ASO-adjacent and web discoverability tasks: app landing pages, App Store or Play Store copy review, competitor positioning, review-mined messaging, schema on app webpages, AI search visibility, and SEO/ASO roadmap planning. For in-app funnels, retention, push performance, revenue cohorts, or crash/performance analytics, use a separate app growth analysis workflow.

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.