seo-page

Trigger phrases

Phrases that activate this skill when typed to Claude Code:

• analyze this page
• check page SEO
• single URL
• page analysis
• check this page

What it does

seo-page is a Claude Code skill from AgriciDaniel’s claude-seo repo. It performs a comprehensive single-page SEO analysis across five scored categories — On-Page SEO, Content Quality, Technical, Schema, and Images — and produces a visual scorecard with a prioritized findings list.

On-page checks cover title tag (50–60 characters, includes primary keyword, unique), meta description (150–160 characters, compelling), H1 (exactly one, matches page intent), heading hierarchy, URL structure, and internal/external linking. Technical checks cover canonical tag, meta robots, Open Graph tags, Twitter Card, and hreflang if multi-language. Schema checks detect all types and flag deprecated ones (HowTo removed September 2023, FAQ restricted to government/healthcare). Image checks cover alt text, file size, format, dimensions for CLS prevention, and lazy loading correctness. Core Web Vitals are flagged as potential issues based on HTML signals — not measured from real user data (use seo-google crux for that).

When to use it

Reach for it when:

• A single page is underperforming and you want a fast structured diagnosis across all SEO dimensions
• You want to check a newly published page before promoting it
• You are reviewing a page from a competitor or potential acquisition target

When not to reach for it:

• The page requires authentication — the skill cannot access authenticated content and will report what is visible
• You want site-wide analysis rather than a single page — use /seo audit <url> which spawns the full subagent pipeline

Install

Copy the seo-page SKILL.md into .claude/skills/seo-page/.

Trigger phrases: “analyze this page”, “check page SEO”, “single URL”, “check this page”, “page analysis”, or providing a single URL for review.

Invoke with /seo page <url>. DataForSEO MCP is optional — if available it adds real SERP positions and backlink data to the report.

What a session looks like

A typical session has three phases:

1. Page fetch and parse. The page is fetched via the SSRF-safe pipeline and parsed for all SEO elements — titles, metas, headings, canonical, robots directives, Open Graph, schema blocks, images. JavaScript-rendered pages are flagged: the skill analyzes available HTML and notes that results may be incomplete if content is client-side rendered.
2. Five-category scoring. Each category is scored independently on a 0–100 scale. The scorecard is rendered as a text bar chart showing relative performance across categories. Issues are organized Critical > High > Medium > Low with specific, actionable recommendations for each.
3. Schema opportunities. For any schema already on the page, validation results are shown. For missing schema opportunities (an article page without Article schema, a product page without Product schema), ready-to-use JSON-LD blocks are generated — never HowTo (deprecated), and FAQ only for government/healthcare.

Receipts

Works well: The scorecard format makes prioritization immediate — a page scoring 45/100 on Technical and 80/100 on Content tells you where to spend time without reading a 200-item checklist. The schema generation is practical: paste-ready JSON-LD with placeholders clearly marked for the user to fill.

Backfires: The CWV section flags potential issues from HTML signals (missing image dimensions, no async/defer on scripts) but cannot measure actual CWV values. Users expecting real LCP/INP/CLS numbers need seo-google pagespeed <url> or seo-google crux <url> instead.

Pattern that works: Use /seo page for spot-checks on individual pages, and reserve /seo audit for full site work. The single-page skill is faster and produces a tighter report when you already know which URL has a problem.

Source and attribution

Originally written by AgriciDaniel. The canonical SKILL.md and supporting files live in the seo-page folder of the claude-seo repository.

License: MIT. Install, adapt, and redistribute with attribution preserved.

This page documents the skill from a practitioner’s perspective. For the formal spec and updates, defer to the source repo.