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.
1---2name: seo-page3description: {}4license: MIT5---67# Single Page Analysis89## When to Use10- Use when the user provides a single URL for detailed on-page SEO review.11- Use when auditing one page rather than an entire site.12- Use when checking metadata, content, schema, images, and page-level technical signals together.1314## What to Analyze1516### On-Page SEO17- Title tag: 50-60 characters, includes primary keyword, unique18- Meta description: 150-160 characters, compelling, includes keyword19- H1: exactly one, matches page intent, includes keyword20- H2-H6: logical hierarchy (no skipped levels), descriptive21- URL: short, descriptive, hyphenated, no parameters22- Internal links: sufficient, relevant anchor text, no orphan pages23- External links: to authoritative sources, reasonable count2425### Content Quality26- Word count vs page type minimums (see quality-gates.md)27- Readability: Flesch Reading Ease score, grade level28- Keyword density: natural (1-3%), semantic variations present29- E-E-A-T signals: author bio, credentials, first-hand experience markers30- Content freshness: publication date, last updated date3132### Technical Elements33- Canonical tag: present, self-referencing or correct34- Meta robots: index/follow unless intentionally blocked35- Open Graph: og:title, og:description, og:image, og:url36- Twitter Card: twitter:card, twitter:title, twitter:description37- Hreflang: if multi-language, correct implementation3839### Schema Markup40- Detect all types (JSON-LD preferred)41- Validate required properties42- Identify missing opportunities43- NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)4445### Images46- Alt text: present, descriptive, includes keywords where natural47- File size: flag >200KB (warning), >500KB (critical)48- Format: recommend WebP/AVIF over JPEG/PNG49- Dimensions: width/height set for CLS prevention50- Lazy loading: loading="lazy" on below-fold images5152### Core Web Vitals (reference only, not measurable from HTML alone)53- Flag potential LCP issues (huge hero images, render-blocking resources)54- Flag potential INP issues (heavy JS, no async/defer)55- Flag potential CLS issues (missing image dimensions, injected content)5657## Output5859### Page Score Card60```61Overall Score: XX/1006263On-Page SEO: XX/100 ████████░░64Content Quality: XX/100 ██████████65Technical: XX/100 ███████░░░66Schema: XX/100 █████░░░░░67Images: XX/100 ████████░░68```6970### Issues Found71Organized by priority: Critical -> High -> Medium -> Low7273### Recommendations74Specific, actionable improvements with expected impact7576### Schema Suggestions77Ready-to-use JSON-LD code for detected opportunities7879## DataForSEO Integration (Optional)8081If DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.8283## Error Handling8485| Scenario | Action |86|----------|--------|87| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |88| 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. |89| 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. |9091## Limitations92- Use this skill only when the task clearly matches the scope described above.93- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.94- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
nous-hermeshub