Use when analyzing a single page via /seo page. Covers meta extraction, schema validation, header hierarchy, content quality, and GEO readiness for one URL or local file.
Scanned 5/28/2026
npx -y skills add fusengine/agents --skill seo-page --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Seo Page?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/fusengine-seo-page)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: seo-page
description: Use when analyzing a single page via /seo page. Covers meta extraction, schema validation, header hierarchy, content quality, and GEO readiness for one URL or local file.
user-invocable: false
related-skills: seo, seo-schema, seo-content, seo-geo
---
# Single-Page SEO Analysis
## Workflow
1. Fetch page (URL via WebFetch, or read local file)
2. Run `scripts/parse-meta.ts <input>` → extract title, description, OG, Twitter, canonical
3. Run `scripts/validate-schema.ts <input>` → JSON-LD validation
4. Analyze H1-H6 hierarchy
5. Run `scripts/geo-score.ts <input>` → LLM-readiness score
6. Output structured report
## Checks
| Element | Rule |
|---------|------|
| `<title>` | 50-60 chars, primary keyword, brand |
| `<meta description>` | 120-155 chars, hook + benefit + CTA |
| `<h1>` | Exactly one, contains primary keyword |
| `<h2>-<h6>` | Hierarchical, no skip |
| Canonical | Self-referencing or pointing to authoritative URL |
| Open Graph | og:title, og:description, og:image (1200x630), og:url |
| Twitter Cards | summary_large_image with og:image |
| Schema | At least one JSON-LD block, validates against schema.org |
| Images | All have alt, lazy-loaded, WebP/AVIF |
## References
- `skills/seo/02-onpage-seo/` (meta-tags, open-graph, twitter-cards, headers, alt-text)
- `skills/seo/09-checklists/pre-publication.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!