SEO Content Writer
SkillSearchWrite search-optimized articles that read naturally - proper structure, intent match, and internal links, without keyword stuffing. Use for blog posts, guides, and landing page copy.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the SEO Content Writer skill
What this skill tells your AI
The instructions your AI receives, as published by navinspire-ia/navin in navin/skills/seo-content-writer/SKILL.md and read by ahel’s review.
Write for the reader first; structure for search engines second. No stuffing, no filler intros, no "in today's fast-paced world".
When to use
- Blog posts, guides, landing pages targeting a primary keyword
- Briefs that must be publish-ready with meta + schema
When not to use
- Pure technical audits
- Keyword maps without writing (use
keyword-research)
Article blueprint
- Title - primary keyword near the front, ≤60 chars, clear promise
- Meta description - 140-155 chars, keyword + hook
- H1 - one only, close to the title
- Intro - answer the query in the first 2-3 sentences (snippet-worthy)
- H2/H3 - each answers a sub-question (PAA themes)
- Entities - cover people/products/concepts SERP winners cover
- Internal links - 2-5 descriptive anchors to real/proposed site pages
- FAQ - real questions + FAQPage schema when useful
- Conclusion / CTA - next action aligned to business goal
Workflow
- Lock primary keyword + intent (
keyword-researchor user brief). - Fetch top 3 SERP results: format, depth, gaps to beat.
- Outline first; confirm with the user for long/high-stakes pieces.
- Write with short paragraphs, bullets/tables, concrete examples - never fabricated stats.
- Illustrate full articles: hero + section images via image tools (keyword-bearing filenames, natural alt). If image gen unavailable, list prompts + alts.
- Add JSON-LD draft (Article and/or FAQPage).
- Save
seo/content/<slug>.md(+ assets beside it); reference inseo-report-*.html.
GEO bonus
Add a 40-80 word answer-first block under major H2s so passages are quotable by AI answers (geo-ai-search-optimizer).
Rules
- Match audience language/register (FR/EN/AR).
- Never fabricate statistics or quotes - link real sources or omit.
- Respect
brand-voice-managerwhen defined. - Primary keyword in title, H1, intro, one H2, conclusion - naturally.
Anti-patterns
- 2000 words of fluff that never answers the query
- Keyword stuffing / synonym spam
- Placeholder "insert statistic here"
Signals
- GitHub stars
- 22
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
seo-content-writer-navinspire-ia- Source
- github.com/navinspire-ia/navin