agentleFS
Sign inStart free
6t9xstar6t9xstar/one-step-seo/skills/seo-audit/SKILL.md

seo-audit

Skill5 starsChanged 37 days agoMITView on GitHub

Run one-step-seo against a URL, local HTML file, or build directory, interpret the independent Search SEO and AI Visibility scores, and return an evidence-backed P0-P3 remediation plan.

  • Reads credentials

185 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openseo-review-web-content, openseo-release-notes and 10 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.
  • JwuthriSkill

    openseo-review-web-content

    Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.

    Also in 5 projects that use this

  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 12 projects that use this

  • +4 more from nicepkg
  • +2 more from Jwuthri

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 2 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use seo-audit when the user asks to:

    line 10
  2. Distinctive:

    Check why a page is underperforming in traditional search or generative answer engines (ChatGPT Search, Claude, Perplexity, Google AI …

    line 15
  3. Very specific:

    Do not activate this skill to directly mutate user HTML files without first running an audit.

    line 17
  4. Very specific:

    Check truncated (whether HTML exceeded the 5 MiB cap) and counts (P0, P1, P2, P3, pass).

    line 39
  5. Very specific:

    Check whether T05-robots-disallow is the sole finding (indicating robots.txt blocked the crawl and --force is needed only if the user owns …

    line 40
  6. Very specific:

    Every claim in your summary must cite the finding id (e.g., T08-canonical), severity (P1), and exact evidence string from report.findings …

    line 65
  7. Distinctive:

    Never invent unmeasured metrics, search volume, backlink counts, or ranking positions.

    line 67
  8. Very specific:

    Scorecard: Search SEO (scores.search.score/100, scores.search.band) and AI Visibility (scores.ai.score/100, scores.ai.band) side by side, …

    line 73
  9. Very specific:

    Use --block-private-ips when auditing untrusted or user-supplied URLs to enforce SSRF and DNS-rebinding protections.

    line 88
  10. Very specific:

    Never modify source or build files during seo-audit.

    line 89

“Common” is measured: kept by at least 6 in 10 of the 167 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-audit — End-to-End SEO & AI Visibility Audit

1. Description & Activation Criteria

Use seo-audit when the user asks to:

  • Audit a website, single page, local HTML file, or static build folder (./dist, ./out, ./public) for SEO or AI search visibility.
  • Interpret report.json, report.md, report.html, or multi-page index.html outputs.
  • Produce a prioritized P0–P3 remediation plan with effort, impact, and owner triage.
  • Check why a page is underperforming in traditional search or generative answer engines (ChatGPT Search, Claude, Perplexity, Google AI Overviews).

Do not activate this skill to directly mutate user HTML files without first running an audit; use seo-fix after user approval for local file edits.

2. Inputs & Prerequisites

  • Target (required): Public http(s) URL, local .html/.htm path, or build directory.
  • Node.js: >=18.0.0 (verify via npx one-step-seo doctor).
  • Optional parameters:
    • --pages <1..200>: Maximum pages to crawl (default 1 for audit, 5 for quick).
    • --crawl <links|sitemap>: Discovery strategy (links BFS or sitemap XML seeding).
    • --profile <default|blog|product|docs|home>: Page-type threshold calibration.
    • --skills <list> / --exclude-skills <list>: Domain-scoped check filtering.
    • --psi: Live Google PageSpeed Insights lab + CrUX field metrics (requires PSI_API_KEY).

3. Step-by-Step Workflow

  1. Select the execution mode:
    • Single live URL or local HTML file: npx one-step-seo page <target> --out ./seo-report
    • Multi-page site audit: npx one-step-seo audit <target> --pages 10 --crawl sitemap --out ./seo-report
    • Fast 5-page overview: npx one-step-seo quick <target> --out ./seo-report
    • Offline build folder audit: npx one-step-seo audit ./dist --pages 20 --offline --out ./seo-report
  2. Read the canonical machine artifact (./seo-report/report.json):
    • Inspect scores.search (0-100, band A-F) and scores.ai (0-100, band A-F). Never average or blend the two scores.
    • Check truncated (whether HTML exceeded the 5 MiB cap) and counts (P0, P1, P2, P3, pass).
    • Check whether T05-robots-disallow is the sole finding (indicating robots.txt blocked the crawl and --force is needed only if the user owns the site).
  3. Triage findings by severity and reach:
    • P0 (Critical blockers, -25 Search): T01-https, T02-status, T07-noindex, O01-title-missing. Fix immediately.
    • P1 (High impact, -10 Search): T03-redirects, T05-robots, T06-sitemap, T08-canonical, T11-viewport, T13-mixed (active), T16-broken-links, T17-canonical-http, O01-title-short, O02-meta-missing, O03-h1-missing, O03-h1-multi, O08-alt, O10-internal, C01-thin, C02-answer, S01-json-invalid, S01-none, G02-ai-blocked.
    • P2 (Medium optimization, -3 Search): O01-title-long, O02-meta-short, O02-meta-long, heading order (O04-headings, O04-heading-empty, O05-h2), O06-og, O07-favicon, O09-img-dims, C03-extractable, C04-faq (P1 on docs profile), S02-* schema properties, G01-llms, G03-facts, G09-snippet-controls, P01-html-size, P02-img-count, T14-third-party.
    • P3 (Polish & GEO depth, -1 Search or GEO-only): O03-h1-drift, O11-generic-anchors, C05-table-headers, S03-faq-parity, G04-entity, G05-llms-quality, G06-freshness, G07-question-headings, G08-stat-density, G10-author, G11-semantic-content, T15-security-headers, W01-social, W02-og-url, W03-hreflang.
  4. Synthesize the action plan:
    • Group recommendations into Immediate Blockers (P0/P1), Content & Schema Enhancements (P2), and AI Citability / Polish (P3).
    • Provide the exact verification command to re-run after fixes.

4. Tools & CLI Commands

# Single page audit (URL or local file)
npx one-step-seo page https://example.com --out ./seo-report

# Multi-page crawl seeded from sitemap with broken-link verification
npx one-step-seo audit https://example.com --pages 15 --crawl sitemap --check-links --out ./seo-report

# Offline static build directory audit
npx one-step-seo audit ./dist --pages 25 --offline --out ./seo-report

5. Evidence Requirements

  • Every claim in your summary must cite the finding id (e.g., T08-canonical), severity (P1), and exact evidence string from report.findings in report.json.
  • Quote actual measured values from report.page (title and title.length, metaDescription and metaDescription.length, canonical, wordCount, h1, images, internalLinks, externalLinks, and optional psi) and report.site (origin, robots, sitemap, sitemapUrls, llms). For detected schema types or blocked AI crawler tokens, quote the evidence of S01-present / G02-ai-blocked in report.findings.
  • Never invent unmeasured metrics, search volume, backlink counts, or ranking positions.

6. Expected Outputs

Present a structured response containing:

  1. Scorecard: Search SEO (scores.search.score/100, scores.search.band) and AI Visibility (scores.ai.score/100, scores.ai.band) side by side, plus counts (P0 / P1 / P2 / P3 / pass).
  2. One-Sentence Verdict: Plain-language health summary (matching report.md executive summary).
  3. Top 3 Urgent Fixes: Finding ID, severity, evidence, recommended fix, and Impact / Effort / Owner.
  4. AI Visibility & Citability Checklist: Passing ([x]) vs missing ([ ]) signals from report.md (## Make this page more citable, derived from report.findings via citableChecklist) or one-step-seo ai <url> --json (signals).
  5. Artifacts & Verification Command: Paths to report.html, index.html, report.md, and report.json, plus the re-run CLI command.

7. Limitations & External Data

  • Readiness signals, not Google scores: Scores measure adherence to documented technical SEO and AI extractability best practices, not live search rankings.
  • Static HTML parsing: Evaluates server-rendered or static HTML response bodies (up to 5 MiB); client-only JavaScript DOM mutations after hydration are not executed.
  • External data: Core Web Vitals (P03-psi-lab, P04-psi-field) are only populated when --psi is run with PSI_API_KEY. Missing PSI metrics are reported as null / unavailable, never 0.

8. Safety & Approval Rules

  • Respect robots.txt by default. Only pass --force if the user explicitly confirms they own the target property and want to bypass robots.txt for diagnostic testing.
  • Use --block-private-ips when auditing untrusted or user-supplied URLs to enforce SSRF and DNS-rebinding protections.
  • Never modify source or build files during seo-audit; transition to seo-fix and request approval before applying file changes.

9. Examples

# Audit a product page with the product calibration profile
npx one-step-seo page https://example.com/shop/backpack --profile product --out ./seo-report

# Audit a documentation site and fail CI if any P0 or P1 findings exist
npx one-step-seo audit https://docs.example.com --pages 10 --profile docs --fail-on P1 --out ./seo-report

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.

Check your setup, free