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: 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.4---56# Single Page Analysis78## When to Use9- Use when the user provides a single URL for detailed on-page SEO review.10- Use when auditing one page rather than an entire site.11- Use when checking metadata, content, schema, images, and page-level technical signals together.1213## What to Analyze1415### On-Page SEO16- Title tag: 50-60 characters, includes primary keyword, unique17- Meta description: 150-160 characters, compelling, includes keyword18- H1: exactly one, matches page intent, includes keyword19- H2-H6: logical hierarchy (no skipped levels), descriptive20- URL: short, descriptive, hyphenated, no parameters21- Internal links: sufficient, relevant anchor text, no orphan pages22- External links: to authoritative sources, reasonable count2324### Content Quality25- Word count vs page type minimums (see quality-gates.md)26- Readability: Flesch Reading Ease score, grade level27- Keyword density: natural (1-3%), semantic variations present28- E-E-A-T signals: author bio, credentials, first-hand experience markers29- Content freshness: publication date, last updated date3031### Technical Elements32- Canonical tag: present, self-referencing or correct33- Meta robots: index/follow unless intentionally blocked34- Open Graph: og:title, og:description, og:image, og:url35- Twitter Card: twitter:card, twitter:title, twitter:description36- Hreflang: if multi-language, correct implementation3738### Schema Markup39- Detect all types (JSON-LD preferred)40- Validate required properties41- Identify missing opportunities42- NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)4344### Images45- Alt text: present, descriptive, includes keywords where natural46- File size: flag >200KB (warning), >500KB (critical)47- Format: recommend WebP/AVIF over JPEG/PNG48- Dimensions: width/height set for CLS prevention49- Lazy loading: loading="lazy" on below-fold images5051### Core Web Vitals (reference only, not measurable from HTML alone)52- Flag potential LCP issues (huge hero images, render-blocking resources)53- Flag potential INP issues (heavy JS, no async/defer)54- Flag potential CLS issues (missing image dimensions, injected content)5556## Output5758### Page Score Card59```60Overall Score: XX/1006162On-Page SEO: XX/100 ████████░░63Content Quality: XX/100 ██████████64Technical: XX/100 ███████░░░65Schema: XX/100 █████░░░░░66Images: XX/100 ████████░░67```6869### Issues Found70Organized by priority: Critical -> High -> Medium -> Low7172### Recommendations73Specific, actionable improvements with expected impact7475### Schema Suggestions76Ready-to-use JSON-LD code for detected opportunities7778## DataForSEO Integration (Optional)7980If DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.8182## Error Handling8384| Scenario | Action |85|----------|--------|86| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |87| 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. |88| 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. |8990## Limitations91- Use this skill only when the task clearly matches the scope described above.92- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.93- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Arjumaan