domains / marketing / single-page-seo-audit / seo-page

seo-page

Skill card

combined

The two copies overlap in scope (single-page SEO audit) but each contains material steps the other lacks. The nowork-studio copy is a thin pointer to an external WORKFLOW.md and emphasizes GSC data, search intent, and internal linking depth, but it does not define the audit checklist or output format. The sickn33 copy provides a detailed, self-contained checklist (on-page, content quality, technical, schema, images, Core Web Vitals heuristics), a scored output format, error handling, and optional DataForSEO integration, but it does not mention GSC or search intent. Crowning one would hide a real alternative: the first is a workflow wrapper with GSC/intent focus, the second is a concrete audit procedure. They do not directly conflict on parameters, but they disagree on what the skill is (a pointer vs. a full procedure).

Repositories

Other copies

Combined skill

---
name: seo-page
argument-hint: "<URL of the page to analyze, e.g. https://example.com/blog/my-post>"
description: >
  Single-page SEO audit: content quality under Google's E-E-A-T framework and
  Helpful Content guidelines, on-page factors, search intent, technical signals and
  readability. Pulls GSC data for the page, crawls the live HTML, checks metadata,
  schema, internal linking and depth, and produces a scored report with fixes. Use
  whenever the user wants to analyze a specific page or URL, not the whole site.
---

# Single Page SEO Audit

## 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.

## Workflow
1. Resolve the target URL from the user's input.
2. If GSC data is available for the page, pull impressions, clicks, CTR, and average position to inform search intent and performance context.
3. Crawl the live HTML of the page.
4. Analyze the page using the checklist below.
5. Produce a scored report with prioritized fixes.

## 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; check internal linking depth
- External links: to authoritative sources, reasonable count

### Content Quality
- Word count vs page type minimums
- 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
- Search intent alignment: does the content match the likely intent for the target query?

### 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.