Seo page

Skill PIXARTSeu/Synapse/packages/codegraph/data/skill/seo-page

Self-improving AI brain for Claude Code & Desktop — 28 MCP tools, 253 skills, collective memory, project tracking, work logs. One server, all your sessions share the same knowledge. Deploy on Coolify in 2 minutes.

Install

npx -y skills add PIXARTSeu/Synapse --skill seo-page

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
8 stars8 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", or provides a single URL for review.

SKILL.md

2.7 KB, 563 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: 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