Seo page

Skill khymerao/cursor-seo/skills/seo-page

SEO toolkit for Cursor — technical SEO, E-E-A-T, Schema.org, GEO/AI search, local SEO, keyword clustering, drift monitoring & DataForSEO. 25 skills, 18 workflows.

Install

npx -y skills add khymerao/cursor-seo --skill seo-page

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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", "single URL", "check this page", "page analysis", or provides a single URL for review.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.9 KB, 797 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it: 1 file

143 B alongside SKILL.md

LICENSE.txt143 B

Gives 0 of the 12 instructions most research analysis skills give in 797 tokens

Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07

Generate a markdown reportin 32 of 1063, across 23 files
Cite each claim's sourcein 30 of 1063, across 15 files
Define the ideal customer profilein 20 of 1063, across 2 files
Search for companies matching the criteriain 20 of 1063, across 2 files
Assign a fit score from one to tenin 20 of 1063, across 2 files
Analyze the codebase to understand the productin 19 of 1063, across 1 file
Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
Look for signals of immediate needin 19 of 1063, across 1 file
Identify the target decision maker rolein 19 of 1063, across 1 file
Suggest a personalized contact strategyin 19 of 1063, across 1 file
Provide conversation starters for outreachin 19 of 1063, across 1 file
Format results in a scannable markdown templatein 19 of 1063, across 1 file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.