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: safe8source: "https://github.com/AgriciDaniel/claude-seo"9date_added: "2026-03-21"10user-invokable: true11argument-hint: "[url]"12allowed-tools:13 - Read14 - Grep15 - Glob16 - Bash17 - WebFetch18---1920# Single Page Analysis2122## When to Use2324- Use when the user provides a single URL for detailed on-page SEO review.25- Use when auditing one page rather than an entire site.26- Use when checking metadata, content, schema, images, and page-level technical signals together.2728## What to Analyze2930### On-Page SEO31- Title tag: 50-60 characters, includes primary keyword, unique32- Meta description: 150-160 characters, compelling, includes keyword33- H1: exactly one, matches page intent, includes keyword34- H2-H6: logical hierarchy (no skipped levels), descriptive35- URL: short, descriptive, hyphenated, no parameters36- Internal links: sufficient, relevant anchor text, no orphan pages37- External links: to authoritative sources, reasonable count3839### Content Quality40- Word count vs page type minimums (see quality-gates.md)41- Readability: Flesch Reading Ease score, grade level42- Keyword density: natural (1-3%), semantic variations present43- E-E-A-T signals: author bio, credentials, first-hand experience markers44- Content freshness: publication date, last updated date4546### Technical Elements47- Canonical tag: present, self-referencing or correct48- Meta robots: index/follow unless intentionally blocked49- Open Graph: og:title, og:description, og:image, og:url50- Twitter Card: twitter:card, twitter:title, twitter:description51- Hreflang: if multi-language, correct implementation5253### Schema Markup54- Detect all types (JSON-LD preferred)55- Validate required properties56- Identify missing opportunities57- NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)5859### Images60- Alt text: present, descriptive, includes keywords where natural61- File size: flag >200KB (warning), >500KB (critical)62- Format: recommend WebP/AVIF over JPEG/PNG63- Dimensions: width/height set for CLS prevention64- Lazy loading: loading="lazy" on below-fold images6566### Core Web Vitals (reference only, not measurable from HTML alone)67- Flag potential LCP issues (huge hero images, render-blocking resources)68- Flag potential INP issues (heavy JS, no async/defer)69- Flag potential CLS issues (missing image dimensions, injected content)7071## Output7273### Page Score Card74```75Overall Score: XX/1007677On-Page SEO: XX/100 ████████░░78Content Quality: XX/100 ██████████79Technical: XX/100 ███████░░░80Schema: XX/100 █████░░░░░81Images: XX/100 ████████░░82```8384### Issues Found85Organized by priority: Critical -> High -> Medium -> Low8687### Recommendations88Specific, actionable improvements with expected impact8990### Schema Suggestions91Ready-to-use JSON-LD code for detected opportunities9293## DataForSEO Integration (Optional)9495If DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.9697## Error Handling9899| Scenario | Action |100|----------|--------|101| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |102| 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. |103| 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. |
lucaspmarie-a11y