Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问clear审计异常

seo-auditSEO 审核

Agent Skill

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

总安装

13,896

周安装

579

GitHub Stars

199

下载量

4,632
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:seo-audit(SEO 审核)
来源仓库:https://github.com/seo-skills/seo-audit-skill
仓库路径:skills/seo-audit
安装命令:
npx skills add https://github.com/seo-skills/seo-audit-skill --skill seo-audit
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/seo-skills/seo-audit-skill --skill seo-audit

简介

涵盖 251 条 SEO、技术、性能、安全和 AI 准备规则的全面网站审核。

  • 分析 20 个类别,包括核心 SEO、性能、链接、图像、安全性、JavaScript 渲染、可访问性、结构化数据和 AI/GEO 准备情况以及通过/警告/失败严重级别
  • 返回 LLM 优化的 XML 输出(比 JSON 小 50-70%)以及控制台、JSON、HTML 和 Markdown 格式,以实现灵活的报告
  • 支持单页面审核和多页面爬行,最多可包含 50 多个页面,包括 Core Web Vitals、渲染分析和按规则分组的可行修复建议
  • 需要 Node.js 18+、npm 和可选的 Chrome/Chromium 来进行性能指标和 JavaScript 渲染检查

SKILL.md

SEO Audit Skill

Audit websites for SEO, technical, content, performance, security, JavaScript rendering, and AI readiness using the SEOmator CLI.

SEOmator provides comprehensive website auditing by analyzing website structure and content against 251 rules across 20 categories.

It provides a list of issues with severity levels, affected URLs, and actionable fix suggestions.

Links

What This Skill Does

This skill enables AI agents to audit websites for 251 rules in 20 categories, including:

  • Core SEO (19 rules): Canonical URLs, indexing directives, title uniqueness, canonical conflicts/loops
  • Performance (22 rules): LCP, CLS, FCP, TTFB, INP, compression, caching, minification, HTTP/2
  • Links (19 rules): Broken links, redirect chains, anchor text, orphan pages, localhost/fragment links
  • Images (14 rules): Alt text, dimensions, lazy loading, modern formats, alt length, background images
  • Security (16 rules): HTTPS, HSTS, CSP, external link safety, leaked secrets, SSL expiry/protocol
  • Technical SEO (13 rules): robots.txt, sitemap.xml, URL structure, 404 pages, soft 404s, error codes
  • Crawlability (18 rules): Sitemap conflicts, indexability signals, canonical chains, pagination issues
  • Structured Data (13 rules): Schema.org markup, Article, Organization, FAQ, Product, Breadcrumb
  • JavaScript Rendering (13 rules): Rendered DOM checks, raw vs rendered mismatches, SSR detection
  • Accessibility (12 rules): ARIA labels, color contrast, form labels, landmarks, touch targets
  • Content (17 rules): Word count, readability, keyword density, duplicate detection, pixel widths
  • Social (9 rules): Open Graph tags, Twitter cards, share buttons, profile links
  • E-E-A-T (14 rules): Author bylines, citations, trust signals, about/contact pages, YMYL detection
  • URL Structure (14 rules): Keyword slugs, stop words, uppercase, underscores, session IDs, tracking params
  • Redirects (8 rules): Redirect loops, types (301/302), meta refresh, JavaScript redirects, broken redirects
  • Mobile (5 rules): Font sizes, horizontal scroll, intrusive interstitials, viewport issues
  • Internationalization (10 rules): lang attribute, hreflang validation (return links, conflicts, mismatches)
  • HTML Validation (9 rules): Doctype, charset, head structure, lorem ipsum, multiple titles/descriptions
  • AI/GEO Readiness (5 rules): Semantic HTML, AI bot access, llms.txt, schema drift
  • Legal Compliance (1 rule): Cookie consent

The audit crawls the website, analyzes each page against audit rules, and returns a comprehensive report with:

  • Overall health score (0-100) with letter grade (A-F)
  • Category breakdowns with pass/warn/fail counts
  • Specific issues with affected URLs grouped by rule
  • Actionable fix recommendations

When to Use

Use this skill when you need to:

  • Analyze a website's SEO health
  • Debug technical SEO issues
  • Check for broken links and redirect chains
  • Validate meta tags, canonical URLs, and structured data
  • Audit security headers, SSL, and HTTPS
  • Check accessibility compliance
  • Analyze JavaScript rendering and SSR compatibility
  • Evaluate AI/GEO readiness (semantic HTML, llms.txt, bot access)
  • Detect duplicate content across pages
  • Validate hreflang and internationalization setup
  • Check HTML document structure and validation
  • Generate site audit reports in multiple formats
  • Compare site health before/after changes

Prerequisites

This skill requires the SEOmator CLI to be installed.

Installation

npm install -g @seomator/seo-audit

Verify Installation

Check that seomator is installed and the system is ready:

seomator self doctor

This checks:

  • Node.js version (18+ recommended)
  • npm availability
  • Chrome/Chromium for Core Web Vitals and JS rendering
  • Write permissions for ~/.seomator
  • Local config file presence

Setup

Running seomator init creates a seomator.toml config file in the current directory.

seomator init                    # Interactive setup
seomator init -y                 # Use defaults
seomator init --preset blog      # Blog-optimized config
seomator init --preset ecommerce # E-commerce config
seomator init --preset ci        # Minimal CI config

If there is no seomator.toml in the directory, CREATE ONE with seomator init before running audits.

Usage

AI Agent Best Practices

YOU SHOULD always prefer --format llm - it provides token-optimized XML output specifically designed for AI agents (50-70% smaller than JSON).

When auditing:

  1. Prefer live websites over local dev servers for accurate performance and rendering data
  2. Use --no-cwv for faster audits when Core Web Vitals and JS rendering checks aren't needed
  3. Scope fixes as concurrent tasks when implementing multiple fixes
  4. Run typechecking/formatting after implementing fixes (tsc, eslint, prettier, etc.)

Website Discovery

If the user doesn't provide a website to audit:

  1. Check for local dev server configurations (package.json scripts,.env files)
  2. Look for Vercel/Netlify project links
  3. Check environment variables for deployment URLs
  4. Ask the user which URL to audit

If you have both local and live websites available, suggest auditing the live site for accurate results.

Basic Workflow

# Quick single-page audit with LLM output
seomator audit https://example.com --format llm --no-cwv

# Multi-page crawl (up to 50 pages)
seomator audit https://example.com --crawl -m 50 --format llm --no-cwv

# Full audit with Core Web Vitals + JS rendering analysis
seomator audit https://example.com --crawl -m 20 --format llm

Advanced Options

Force fresh crawl (ignore cache):

seomator audit https://example.com --refresh --format llm

Resume interrupted crawl:

seomator audit https://example.com --resume --format llm

Audit specific categories only:

seomator audit https://example.com -c core,security,js --format llm --no-cwv

Save HTML report for sharing:

seomator audit https://example.com --format html -o report.html

Verbose output for debugging:

seomator audit https://example.com --format llm -v

Command Reference

Audit Command Options

OptionAliasDescriptionDefault
--format <fmt>-fOutput format: console, json, html, markdown, llmconsole
--max-pages <n>-mMaximum pages to crawl10
--crawlEnable multi-page crawlfalse
--categories <list>-cComma-separated categories to auditAll
--refresh-rIgnore cache, fetch freshfalse
--resumeResume interrupted crawlfalse
--no-cwvSkip Core Web Vitals + JS renderingfalse
--verbose-vShow progressfalse
--output <path>-oOutput file path
--config <path>Config file path
--saveSave to ~/.seomatorfalse

Other Commands

seomator init              # Create config file
seomator self doctor       # Check system setup
seomator config --list     # Show all config values
seomator report --list     # List past reports
seomator db stats          # Show database statistics

Output Formats

FormatFlagBest For
console--format consoleHuman terminal output (default)
json--format jsonCI/CD, programmatic processing
html--format htmlStandalone reports, sharing
markdown--format markdownDocumentation, GitHub
llm--format llmAI agents (recommended)

The --format llm output is a compact XML format optimized for token efficiency:

  • 50-70% smaller than JSON output
  • Issues sorted by severity (critical first)
  • Fix suggestions included for each issue
  • Clean stdout for piping to AI tools

Examples

Example 1: Quick Audit with LLM Output

# User asks: "Check example.com for SEO issues"
seomator audit https://example.com --format llm --no-cwv

Example 2: Deep Crawl for Large Site

# User asks: "Do a thorough audit with up to 100 pages"
seomator audit https://example.com --crawl -m 100 --format llm --no-cwv

Example 3: Fresh Audit After Changes

# User asks: "Re-audit the site, ignore cached results"
seomator audit https://example.com --refresh --format llm --no-cwv

Example 4: Generate Shareable Report

# User asks: "Create an HTML report I can share"
seomator audit https://example.com --crawl -m 20 --format html -o seo-report.html

Example 5: Focus on Specific Areas

# User asks: "Just check my JavaScript rendering and redirects"
seomator audit https://example.com -c js,redirect --format llm

Evaluating Results

Score Ranges

ScoreGradeMeaning
90-100AExcellent - Minor optimizations only
80-89BGood - Address warnings
70-79CNeeds Work - Priority fixes required
50-69DPoor - Multiple critical issues
0-49FCritical - Major problems to resolve

Priority Order (by category weight)

Fix issues in this order for maximum impact:

  1. Core (12%) - Meta tags, canonical, H1, indexing
  2. Performance (12%) - Core Web Vitals + optimization
  3. Links (8%) - Internal linking structure
  4. Images (8%) - Performance + accessibility
  5. Security (8%) - Trust signals, SSL
  6. Technical SEO (7%) - Crawling foundation
  7. Crawlability (5%) - Indexability, pagination
  8. Structured Data (5%) - Rich snippets
  9. JavaScript Rendering (5%) - Rendered DOM, SSR
  10. Content (5%) - Text quality + duplicates
  11. Accessibility (4%) - WCAG compliance
  12. Social (3%) - Social sharing
  13. E-E-A-T (3%) - Trust, expertise
  14. URL Structure (3%) - URL hygiene
  15. Redirects (3%) - Redirect chains
  16. Mobile (2%) - Viewport, fonts
  17. Internationalization (2%) - Hreflang
  18. HTML Validation (2%) - Document structure
  19. AI/GEO Readiness (2%) - Semantic HTML, AI bots
  20. Legal Compliance (1%) - Cookie consent

Fix by Severity

  1. Failures (status: "fail") - Must fix immediately
  2. Warnings (status: "warn") - Should fix soon
  3. Passes (status: "pass") - No action needed

Output Summary

After implementing fixes, give the user a summary of all changes made.

When planning scope, organize tasks so they can run concurrently as sub-agents to speed up implementation.

Troubleshooting

seomator command not found

If you see this error, seomator is not installed or not in your PATH.

Solution:

npm install -g @seomator/seo-audit

Core Web Vitals not measured

If CWV metrics are missing, Chrome/Chromium may not be available.

Solution:

  1. Install Chrome, Chromium, or Edge
  2. Run seomator self doctor to verify browser detection
  3. Use --no-cwv to skip CWV if not needed

Crawl timeout or slow performance

For large sites, audits may take several minutes.

Solution:

  • Use --verbose to see progress
  • Limit pages with -m 20 for faster results
  • Use --no-cwv to skip browser-based measurements

Invalid URL

Ensure the URL includes the protocol:

# Wrong
seomator audit example.com

# Correct
seomator audit https://example.com

How It Works

  1. Fetch: Downloads the page HTML and measures response time
  2. Parse: Extracts DOM, meta tags, links, images, structured data
  3. Enrich: Fetches robots.txt and sitemap once per audit
  4. Render (if CWV enabled): Captures rendered DOM via Playwright for JS rendering analysis
  5. Crawl (if enabled): Discovers and fetches linked pages
  6. Analyze: Runs 251 audit rules against each page
  7. Score: Calculates category and overall weighted scores
  8. Report: Generates output in requested format

Results are stored in ~/.seomator/ for later retrieval with seomator report.

Resources

  • Full rules reference: See docs/SEO-AUDIT-RULES.md for all 251 rules
  • Storage architecture: See docs/STORAGE-ARCHITECTURE.md for database details
  • CLI help: seomator --help and seomator <command> --help

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Gemini CLI

26.71%
按下载量换算1,237

Antigravity

22.29%
按下载量换算1,032

Claude Code

17.54%
按下载量换算812

Cursor

13.47%
按下载量换算624

OpenCode

8.69%
按下载量换算403

Codex

3.61%
按下载量换算167

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills