skilld
All skills
agricidaniel avatar

/seo-page

@93b720e
by Agrici.Danielagricidaniel/claude-seo18k stars
2,665

Analyze one supplied URL across on-page, content, technical metadata, schema, images, and performance. Use only for a single-page review.

Ask your Agent

Use this Skill: https://skilld.dev/gh/agricidaniel/claude-seo/seo-page

This session only. Nothing lands on disk.

SKILL.md

≈37 tokens always: the name and description. ≈1k when used: this file.

Single Page Analysis

What to Analyze

On-Page SEO

  • Title tag: 50-60 characters, includes primary keyword, unique
  • Meta description: 150-160 characters, compelling, includes keyword
  • Meta description is not a restatement of the title: run "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run metadata_template.py --title "<title>" --description "<desc>" --json (heuristic, deterministic string comparison). A description that opens by repeating its own title and closes on a stock CTA ("Try it free now.", "Start free!") is templated metadata, the shape bulk generation jobs produce site-wide, and duplicated or templated metadata is a documented content-quality problem regardless of how original the body copy is
  • 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 for rich results (retired May 2026); existing FAQPage need not be removed, use QAPage for genuine Q&A

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: report lazy_method per image (native | perfmatters | ewww | js-generic | none). Do not flag "not lazy-loaded" when JS lazy-loaders (Perfmatters, EWWW, lazysizes) are detected, they intentionally strip the native loading="lazy" attribute and use data-src placeholders

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.

Source: SKILL.md on GitHub

Third-party checks

1 warning1d5 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill is a single-page SEO analyzer that evaluates metadata, content quality, and technical elements. It uses local scripts for analysis and optionally integrates with DataForSEO tools. No security issues were detected.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: MEDIUM · 1 issue

  • Runlayer6mo

    1 file scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 93b720e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 3 days ago

Capability

user-invocable
true
argument-hint
[url]
metadata
{
  "author": "AgriciDaniel",
  "version": "2.4.1",
  "category": "seo"
}

Topics

  • SEO
  • on-page
  • schema
  • content-analysis
  • technical-seo
  • core-web-vitals
  • images
  • metadata

README badge

README badge for agricidaniel/claude-seo/seo-page

What it does

Analyzes a single webpage for SEO quality across on-page elements, content, technical meta tags, schema markup, images, and Core Web Vitals signals. Scores title tags, meta descriptions, heading hierarchy, keyword density, E-E-A-T signals, canonical tags, Open Graph, schema types, image optimization, and flags render-blocking resources or layout shift risks.

Generated from the current SKILL.md.

Frequently asked

Does this skill analyze JavaScript-rendered content?
The skill analyzes the HTML as served, which may be incomplete for client-side rendered pages. For JavaScript-heavy sites, results may not capture dynamically injected content — the skill will flag this limitation and suggest providing a browser-rendered snapshot if available.
Does this skill check actual search rankings or Core Web Vitals?
No. The skill analyzes on-page elements, content, and markup only. If DataForSEO MCP tools are available, it can optionally fetch real SERP positions and backlink data, but Core Web Vitals (LCP, INP, CLS) are identified through HTML inspection and potential risk factors only, not measured live.
What happens if the URL is unreachable or behind authentication?
The skill reports the error clearly and does not guess page content. For authenticated pages, it suggests providing the rendered HTML directly or a publicly accessible URL instead.
Does this skill recommend HowTo or FAQ schema?
No. The skill does not recommend HowTo (deprecated) or FAQ schema for rich results (FAQ retiring May 2026). It treats existing FAQPage as a citation signal and uses QAPage for genuine Q&A content.
How does this skill handle lazy-loaded images?
The skill reports the lazy-loading method per image (native, Perfmatters, EWWW, js-generic, or none) and does not flag JS-based lazy loaders as missing the native `loading='lazy'` attribute, since they intentionally use `data-src` placeholders instead.

Generated from the current SKILL.md. These answers refresh after source changes.