mcpField
3
30x-seo-page

30x-seo-page

github.com/norahe0304-artMarketing & growth5663 installsUpdated 33w ago
Repository

About 30x-seo-page

30x-seo-page is a skill for auditing a single page’s SEO, content, technical elements, schema, and images. It produces a scorecard, prioritized issues, and actionable recommendations.

Key features

  1. 01On-page SEO review
  2. 02Content quality checks
  3. 03Technical metadata review
  4. 04Schema detection and suggestions
  5. 05Image and Core Web Vitals checks
  6. 06Prioritized scorecard and recommendations

Use cases

  1. 01Audit a page before publication
  2. 02Find metadata and content gaps
  3. 03Review structured data opportunities

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/norahe0304-art/30x-seo --skill 30x-seo-page

After installing, type/30x-seo-pagein Claude Code to confirm it loaded.

Details

From the project README

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

[PROTOCOL]: Update this header on changes, then check CLAUDE.md

Comments

Markdown supported