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. |
1---2name: seo-page3description: >4 Deep single-page SEO analysis covering on-page elements, content quality,5 technical meta tags, schema, images, and performance. Use when user says6 "analyze this page", "check page SEO", or provides a single URL for review.7risk: unknown8source: "https://github.com/AgriciDaniel/claude-seo"9date_added: "2026-03-21"10user-invokable: true11argument-hint: "[url]"12allowed-tools:13 - Read14 - Grep15 - Glob16 - Bash17 - WebFetch18metadata:19 source: https://skillmd.com/skills/nimoqup046-collab/seo-page20---2122# Single Page Analysis2324## When to Use2526- Use when the user provides a single URL for detailed on-page SEO review.27- Use when auditing one page rather than an entire site.28- Use when checking metadata, content, schema, images, and page-level technical signals together.2930## What to Analyze3132### On-Page SEO33- Title tag: 50-60 characters, includes primary keyword, unique34- Meta description: 150-160 characters, compelling, includes keyword35- H1: exactly one, matches page intent, includes keyword36- H2-H6: logical hierarchy (no skipped levels), descriptive37- URL: short, descriptive, hyphenated, no parameters38- Internal links: sufficient, relevant anchor text, no orphan pages39- External links: to authoritative sources, reasonable count4041### Content Quality42- Word count vs page type minimums (see quality-gates.md)43- Readability: Flesch Reading Ease score, grade level44- Keyword density: natural (1-3%), semantic variations present45- E-E-A-T signals: author bio, credentials, first-hand experience markers46- Content freshness: publication date, last updated date4748### Technical Elements49- Canonical tag: present, self-referencing or correct50- Meta robots: index/follow unless intentionally blocked51- Open Graph: og:title, og:description, og:image, og:url52- Twitter Card: twitter:card, twitter:title, twitter:description53- Hreflang: if multi-language, correct implementation5455### Schema Markup56- Detect all types (JSON-LD preferred)57- Validate required properties58- Identify missing opportunities59- NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)6061### Images62- Alt text: present, descriptive, includes keywords where natural63- File size: flag >200KB (warning), >500KB (critical)64- Format: recommend WebP/AVIF over JPEG/PNG65- Dimensions: width/height set for CLS prevention66- Lazy loading: loading="lazy" on below-fold images6768### Core Web Vitals (reference only, not measurable from HTML alone)69- Flag potential LCP issues (huge hero images, render-blocking resources)70- Flag potential INP issues (heavy JS, no async/defer)71- Flag potential CLS issues (missing image dimensions, injected content)7273## Output7475### Page Score Card76```77Overall Score: XX/1007879On-Page SEO: XX/100 ████████░░80Content Quality: XX/100 ██████████81Technical: XX/100 ███████░░░82Schema: XX/100 █████░░░░░83Images: XX/100 ████████░░84```8586### Issues Found87Organized by priority: Critical -> High -> Medium -> Low8889### Recommendations90Specific, actionable improvements with expected impact9192### Schema Suggestions93Ready-to-use JSON-LD code for detected opportunities9495## DataForSEO Integration (Optional)9697If DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.9899## Error Handling100101| Scenario | Action |102|----------|--------|103| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |104| 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. |105| 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. |