Agent skill · Security

seo-analyzer

Analyzes HTML files for SEO issues using static analysis with cheerio. Checks meta tags, Open Graph, Twitter Cards, heading structure, and JSON-LD structured data. Use when user mentions "SEO check", "meta tags", "og tags", "structured data validation", "SEO audit", or wants to analyze HTML/JSX for SEO compliance.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill seo-analyzer-naporin0624-claude-web-audit-plu-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/analysis/seo-analyzer-naporin0624-claude-web-audit-plu-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SEO Analyzer Static SEO analysis for HTML files using cheerio-based parsing. Validates meta tags, social media tags, heading structure, and structured data. Also includes keyword analysis for content optimization. ## Analysis Workflow 1. **Parse HTML** with cheerio 2. **Check Critical Issues** (P0): - Title tag presence and length - Meta description presence and length - Single H1 tag - Canonical URL 3. **Check Important Issues** (P1): - Robots meta directives - Viewport meta - Heading hierarchy - Lang attribute 4. **Check Recommended** (P2): - Open Graph tags - Twitter Cards - JSON-LD structured data - Hreflang tags 5. **Generate Report** with issues and recommendations ## Usage ### Installation ```bash cd ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer npm install npm run build ``` ### Run Analysis ```bash # SEO analysis (default) npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer/src/index.ts path/to/file.html # SEO analysis with JSON output npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer/src/index.ts path/to/file.html --json # Keyword analysis npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer/src/index.ts path/to/file.html --keywords # Both SEO and Keyword analysis npx tsx ${CLAUD

What's inside
Steps it walks through
  1. Analysis Workflow
  2. Usage
  3. Installation
  4. Run Analysis
  5. Using Built Version
  6. Check Items
  7. P0 - Critical (Indexing/Ranking Impact)
  8. P1 - Important (SEO Quality)
  9. P2 - Recommended (Social/Rich Results)
  10. Output Format
  11. Text Report
  12. JSON Output
  13. Detection Features
  14. React/SPA Detection
Ships with 1 file
  • metadata.json
Commands it runs
cd ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer
npm install
npm run build
SEO analysis (default)
npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer/src/index.ts path/to/file.html
SEO analysis with JSON output
npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer/src/index.ts path/to/file.html --json
Keyword analysis
npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/seo-analyzer/src/index.ts path/to/file.html --keywords
Both SEO and Keyword analysis
More from claude-skill-registry
All skills →
About this skill
What does the seo-analyzer skill do?

Analyzes HTML files for SEO issues using static analysis with cheerio. Checks meta tags, Open Graph, Twitter Cards, heading structure, and JSON-LD structured data. Use when user mentions "SEO check", "meta tags", "og tags", "structured data validation", "SEO audit", or wants to analyze HTML/JSX for SEO compliance.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill seo-analyzer-naporin0624-claude-web-audit-plu-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going