Seo Page
Run a structured single-URL SEO audit before you ship or refresh a landing page, blog post, or product page.
Overview
seo-page is an agent skill for the Launch phase that deep-audits a single URL for on-page SEO, content quality, technical meta tags, schema, images, and performance-related signals.
Install
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-pageWhat is this skill?
- Checks title (50–60 chars), meta description (150–160), single H1, and H2–H6 hierarchy without skipped levels
- Scores content quality: word count vs page-type minimums, readability, keyword density, and E-E-A-T markers
- Reviews technical SEO: canonical, meta robots, internal/external links, and orphan-page risk
- Covers schema, image SEO, and performance-oriented on-page factors for one URL
- Triggered by phrases like analyze this page, check page SEO, single URL, or page analysis
- Title tag guidance: 50–60 characters
- Meta description guidance: 150–160 characters
- Keyword density check: natural 1–3%
Adoption & trust: 2.2k installs on skills.sh; 8.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to ship or promote a page but lack a consistent checklist for titles, headings, content depth, and technical tags on that one URL.
Who is it for?
Solo builders validating one landing page, blog post, or product URL before launch or after a content refresh.
Skip if: Full-site crawls, backlink campaigns, or rank-tracking dashboards—use multi-page or off-page SEO tooling instead.
When should I use this skill?
User says analyze this page, check page SEO, single URL, check this page, page analysis, or provides a single URL for review.
What do I get? / Deliverables
You get a structured single-page SEO review aligned to quality gates so you can fix on-page and technical issues before publishing or refreshing the URL.
- Structured on-page and technical SEO findings for one URL
- Actionable fixes for titles, meta, headings, links, and content quality
Recommended Skills
Journey fit
Launch is where on-page and technical SEO directly affects crawlability, snippets, and organic discovery for pages you are about to publish or promote. The SEO subphase is the canonical shelf for URL-level audits covering titles, meta, headings, schema, images, and performance signals tied to one page.
How it compares
Use instead of ad-hoc “does this page look OK?” chat reviews when you want a documented on-page and technical checklist for one URL.
Common Questions / FAQ
Who is seo-page for?
Indie and solo builders shipping content sites, SaaS marketing pages, or ecommerce PDPs who need a focused SEO pass on a single URL without enterprise audit suites.
When should I use seo-page?
During Launch SEO when you say analyze this page or check page SEO; also after Build docs/pages and before Grow content pushes when one URL must meet title, meta, heading, and E-E-A-T gates.
Is seo-page safe to install?
It is MIT-licensed from AgriciDaniel’s claude-seo repo; review the Security Audits panel on this Prism page and avoid sending sensitive authenticated URLs you would not fetch yourself.
SKILL.md
READMESKILL.md - Seo Page
MIT License - see repository root LICENSE file for complete terms. Copyright (c) 2026 AgriciDaniel https://github.com/AgriciDaniel/claude-seo --- name: seo-page description: > Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", "single URL", "check this page", "page analysis", or provides a single URL for review. user-invokable: true argument-hint: "[url]" license: MIT metadata: author: AgriciDaniel version: "2.0.0" category: seo --- # Single Page Analysis ## What to Analyze ### On-Page SEO - Title tag: 50-60 characters, includes primary keyword, unique - Meta description: 150-160 characters, compelling, includes keyword - H1: exactly one, matches page intent, includes keyword - H2-H6: logical hierarchy (no skipped levels), descriptive - URL: short, descriptive, hyphenated, no parameters - Internal links: sufficient, relevant anchor text, no orphan pages - External links: to authoritative sources, reasonable count ### Content Quality - Word count vs page type minimums (see quality-gates.md) - Readability: Flesch Reading Ease score, grade level - Keyword density: natural (1-3%), semantic variations present - E-E-A-T signals: author bio, credentials, first-hand experience markers - Content freshness: publication date, last updated date ### Technical Elements - Canonical tag: present, self-referencing or correct - Meta robots: index/follow unless intentionally blocked - Open Graph: og:title, og:description, og:image, og:url - Twitter Card: twitter:card, twitter:title, twitter:description - Hreflang: if multi-language, correct implementation ### Schema Markup - Detect all types (JSON-LD preferred) - Validate required properties - Identify missing opportunities - NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health) ### Images - Alt text: present, descriptive, includes keywords where natural - File size: flag >200KB (warning), >500KB (critical) - Format: recommend WebP/AVIF over JPEG/PNG - Dimensions: width/height set for CLS prevention - Lazy loading: report `lazy_method` per image (native | perfmatters | ewww | js-generic | none). Do not flag "not lazy-loaded" when JS lazy-loaders (Perfmatters, EWWW, lazysizes) are detected — they intentionally strip the native `loading="lazy"` attribute and use `data-src` placeholders ### Core Web Vitals (reference only, not measurable from HTML alone) - Flag potential LCP issues (huge hero images, render-blocking resources) - Flag potential INP issues (heavy JS, no async/defer) - Flag potential CLS issues (missing image dimensions, injected content) ## Output ### Page Score Card ``` Overall Score: XX/100 On-Page SEO: XX/100 ████████░░ Content Quality: XX/100 ██████████ Technical: XX/100 ███████░░░ Schema: XX/100 █████░░░░░ Images: XX/100 ████████░░ ``` ### Issues Found Organized by priority: Critical -> High -> Medium -> Low ### Recommendations Specific, actionable improvements with expected impact ### Schema Suggestions Ready-to-use JSON-LD code for detected opportunities ## DataForSEO Integration (Optional) If DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores. ## Error Handling | Scenario | Action | |----------|--------| | URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. | | Page requires authentication (401/403) | Report that the page is behind authentication. Suggest the user provide the rendered HTML directly or a publicly accessible URL. | | JavaScript-rendered content (empty body in HTML) | Note that key content may be rendered client-side. Analyze the available HTML and flag that results may be incomplete. Suggest using a browser-rendered snapshot if available. |