Single Page Analysis
When to Use
- Use when the user provides a single URL for detailed on-page SEO review.
- Use when auditing one page rather than an entire site.
- Use when checking metadata, content, schema, images, and page-level technical signals together.
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. |
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Source: sickn33/agentic-awesome-skills → skills/seo-page/SKILL.md
Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/seo-page/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/seo-page/SKILL.md
1---
2name: seo-page
3description: "> 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\", or provides a single URL for review."
4allowed-tools: "Read Grep Glob Bash WebFetch"
5category: marketing-and-growth
6source_repo: sickn33/agentic-awesome-skills
7source_path: "skills/seo-page/SKILL.md"
8source_url: https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/skills/seo-page/SKILL.md
9metadata:
10 source: https://skillmd.com/skills/sickn33/seo-page
11---
12
13
14# Single Page Analysis
15
16## When to Use
17- Use when the user provides a single URL for detailed on-page SEO review.
18- Use when auditing one page rather than an entire site.
19- Use when checking metadata, content, schema, images, and page-level technical signals together.
20
21## What to Analyze
22
23### On-Page SEO
24- Title tag: 50-60 characters, includes primary keyword, unique
25- Meta description: 150-160 characters, compelling, includes keyword
26- H1: exactly one, matches page intent, includes keyword
27- H2-H6: logical hierarchy (no skipped levels), descriptive
28- URL: short, descriptive, hyphenated, no parameters
29- Internal links: sufficient, relevant anchor text, no orphan pages
30- External links: to authoritative sources, reasonable count
31
32### Content Quality
33- Word count vs page type minimums (see quality-gates.md)
34- Readability: Flesch Reading Ease score, grade level
35- Keyword density: natural (1-3%), semantic variations present
36- E-E-A-T signals: author bio, credentials, first-hand experience markers
37- Content freshness: publication date, last updated date
38
39### Technical Elements
40- Canonical tag: present, self-referencing or correct
41- Meta robots: index/follow unless intentionally blocked
42- Open Graph: og:title, og:description, og:image, og:url
43- Twitter Card: twitter:card, twitter:title, twitter:description
44- Hreflang: if multi-language, correct implementation
45
46### Schema Markup
47- Detect all types (JSON-LD preferred)
48- Validate required properties
49- Identify missing opportunities
50- NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)
51
52### Images
53- Alt text: present, descriptive, includes keywords where natural
54- File size: flag >200KB (warning), >500KB (critical)
55- Format: recommend WebP/AVIF over JPEG/PNG
56- Dimensions: width/height set for CLS prevention
57- Lazy loading: loading="lazy" on below-fold images
58
59### Core Web Vitals (reference only, not measurable from HTML alone)
60- Flag potential LCP issues (huge hero images, render-blocking resources)
61- Flag potential INP issues (heavy JS, no async/defer)
62- Flag potential CLS issues (missing image dimensions, injected content)
63
64## Output
65
66### Page Score Card
67```
68Overall Score: XX/100
69
70On-Page SEO: XX/100 ████████░░
71Content Quality: XX/100 ██████████
72Technical: XX/100 ███████░░░
73Schema: XX/100 █████░░░░░
74Images: XX/100 ████████░░
75```
76
77### Issues Found
78Organized by priority: Critical -> High -> Medium -> Low
79
80### Recommendations
81Specific, actionable improvements with expected impact
82
83### Schema Suggestions
84Ready-to-use JSON-LD code for detected opportunities
85
86## DataForSEO Integration (Optional)
87
88If DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.
89
90## Error Handling
91
92| Scenario | Action |
93|----------|--------|
94| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |
95| 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. |
96| 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. |
97
98## Limitations
99- Use this skill only when the task clearly matches the scope described above.
100- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
101- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
102
103---
104
105**Source:** [`sickn33/agentic-awesome-skills`](https://github.com/sickn33/agentic-awesome-skills) → `skills/seo-page/SKILL.md`
106
107**Also appears in:** `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/seo-page/SKILL.md`, `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/seo-page/SKILL.md`