Install
mkdir -p .claude/skills/seo-page && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17050" && unzip -o skill.zip -d .claude/skills/seo-page && rm skill.zipInstalls to .claude/skills/seo-page
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Analyze on-page SEO elements like title tags and H1s
- →Evaluate content quality based on word count and readability
- →Check technical elements such as canonical tags and Open Graph data
- →Detect and validate schema markup types
- →Assess image optimization for alt text, file size, and format
- →Provide a page score card and prioritized recommendations
How it works
The skill analyzes a given URL by checking on-page SEO, content quality, technical elements, schema markup, and images. It also checks a shared data cache for reusable context before gathering new information.
Inputs & outputs
When to use seo-page
- →Analyze single page SEO
- →Check meta tags
- →Verify heading hierarchy
- →Audit page content
About this skill
Single Page Analysis
Shared Data Cache
Step 0 -- Check shared data cache:
Before gathering, check .seo-cache/ for reusable context from related SEO skills.
Reference: ../seo/references/shared-data-cache.md for schemas and dependency map.
Check these cache files when present:
-
.seo-cache/site-meta.jsonfor domain, business type, industry, and crawl context -
.seo-cache/audit-scores.jsonfor prior full-audit priorities -
.seo-cache/pages/{url-slug}/page-analysis.jsonfor page-level context when a URL is provided -
If found: parse and use clearly valid fields (note "Using cached [X] from [date]")
-
If missing, corrupt, or irrelevant: continue with fresh evidence
-
If the user says "refresh" or "re-run": ignore cache reads and overwrite on write
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: loading="lazy" on below-fold images
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. |
Write to shared data cache
After completing all work, write a concise JSON summary to .seo-cache/ when the workflow produced durable findings.
Use the schemas and naming rules in ../seo/references/shared-data-cache.md; include at least cache_type, analyzed_at, source URL/domain, key findings, issues, recommendations, and tool limitations. Add .seo-cache/ to .gitignore if it is missing.
When not to use it
- →When the URL is unreachable due to DNS failure or connection refused
- →When the page requires authentication (401/403 errors)
- →When a user explicitly requests to ignore cache reads and overwrite on write
Limitations
- →Core Web Vitals are referenced but not directly measurable from HTML alone
- →The skill does not guess page content if the URL is unreachable
- →Results may be incomplete if key content is rendered client-side via JavaScript
How it compares
This workflow automates the detailed analysis of various SEO factors on a single page, providing structured feedback and scores, unlike a manual review that would require checking each element individually.
Compared to similar skills
seo-page side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| seo-page (this skill) | 0 | 3mo | No flags | Beginner |
| google-official-seo-guide | 143 | 10mo | No flags | Beginner |
| seo-optimizer | 33 | 8mo | No flags | Intermediate |
| seo-content-writer | 24 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by AgriciDaniel
View all by AgriciDaniel →You might also like
google-official-seo-guide
littleben
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
seo-optimizer
davila7
Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements. Use when optimizing website content, improving search rankings, conducting keyword analysis, or implementing SEO best practices. Expert in on-page SEO, meta tags, schema markup, and Core Web Vitals.
seo-content-writer
sickn33
Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.
content-creation
anthropics
Draft marketing content across channels — blog posts, social media, email newsletters, landing pages, press releases, and case studies. Use when writing any marketing content, when you need channel-specific formatting, SEO-optimized copy, headline options, or calls to action.
content-marketer
sickn33
Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing. Masters modern content tools, social media automation, and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive content marketing.
competitor-alternatives
davila7
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.