mcpbeat

Content Optimizer

nicepkg/content-optimizer

On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability. Use when optimizing existing content or validating new content against SEO requirements.

677 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
275
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nicepkg/ai-workflow --skill content-optimizer

The instruction itself

10 sections, as written by the author

Content Optimizer

When to Use

  • Optimizing existing content for better rankings
  • Validating new content against SEO requirements
  • Checking keyword density and placement
  • Improving readability scores
  • Creating meta tags

Keyword Density

Target: 1-2% for primary keyword

Calculation:

Density = (Keyword Count / Total Words) x 100

Placement Priorities:

  • Title/H1 (required)
  • First 100 words (required)
  • At least one H2 (recommended)
  • Conclusion (recommended)
  • Distributed in body (natural)

Warning Signs:

  • >3% = Keyword stuffing risk
  • <0.5% = Under-optimized
  • Exact match every paragraph = Unnatural

Meta Tag Optimization

Title Tag

  • Length: 50-60 characters
  • Keyword: Near the beginning
  • Format: {Keyword} - {Benefit} | {Brand}
  • Unique per page

Meta Description

  • Length: 150-160 characters
  • Keyword: Include naturally
  • CTA: End with action verb
  • Unique per page

URL Slug

  • Short: 3-5 words
  • Keyword: Include primary
  • Readable: Use hyphens
  • Lowercase only

Heading Structure

Valid Hierarchy:

H1: Page Title (exactly 1)
+-- H2: Main Section
|   +-- H3: Subsection
|   +-- H3: Subsection
+-- H2: Main Section
|   +-- H3: Subsection
+-- H2: Conclusion

Common Errors:

  • Multiple H1 tags
  • Skipping levels (H1 -> H3)
  • Using headings for styling only
  • No keyword in H1

Readability Optimization

Flesch Reading Ease Target: 60-70

| Score | Level | Audience |

|-------|-------|----------|

| 90-100 | Very Easy | 5th grade |

| 80-89 | Easy | 6th grade |

| 70-79 | Fairly Easy | 7th grade |

| 60-69 | Standard | 8th-9th grade |

| 50-59 | Fairly Difficult | 10th-12th grade |

| 30-49 | Difficult | College |

| 0-29 | Very Difficult | College graduate |

Improvement Techniques:

  • Shorten sentences (<20 words avg)
  • Shorten paragraphs (2-3 sentences)
  • Replace jargon with plain language
  • Use active voice
  • Add subheadings every 200-300 words
  • Use bullet points for lists

Optimization Checklist

Use this checklist when optimizing content:

  • [ ] Primary keyword in title/H1
  • [ ] Primary keyword in first 100 words
  • [ ] Keyword density 1-2%
  • [ ] Meta title 50-60 characters
  • [ ] Meta description 150-160 characters with CTA
  • [ ] Heading hierarchy valid (H1 -> H2 -> H3)
  • [ ] At least 3 internal links
  • [ ] At least 1 external authoritative link
  • [ ] Flesch score 60-70
  • [ ] No paragraphs > 3 sentences
  • [ ] Subheadings every 200-300 words

How to use it

Copy the folder

Take nicepkg/content-optimizer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.