algo-seo-content
Execute content SEO strategy from keyword research through content planning, writing, and on-page optimization. Use this skill when the user needs to create SEO-optimized content, perform keyword research, identify content gaps, or improve existing content rankings — even if they say 'content strategy', 'keyword research', or 'how to rank for this topic'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/algo-seo-content”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/algo-seo-contentmetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
52 words · 357 chars — "Execute content SEO strategy from keyword research through content planning, wri…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 52 words.
Documentation present and substantive
Documentation present (SKILL.md, 663 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Content SEO Strategy
Overview
Content SEO is the systematic process of creating and optimizing content to match search intent and rank organically. The pipeline: keyword research → intent mapping → content creation → on-page optimization → performance monitoring. Success depends on intent match, not keyword density.
When to Use
Trigger conditions:
- Planning new content to capture organic search traffic
- Optimizing existing underperforming content
- Conducting keyword research and content gap analysis
When NOT to use:
- When the issue is technical (page speed, crawlability) — use technical SEO
- When the issue is off-page (backlinks, authority) — use backlink analysis
Algorithm
IRON LAW: Content Must Match SEARCH INTENT
A perfectly optimized page targeting the wrong intent will NOT rank.
Four intent types:
1. Informational — wants to learn ("how to", "what is")
2. Navigational — wants a specific site ("github login")
3. Commercial — comparing options ("best CRM 2025")
4. Transactional — wants to buy/do ("buy iPhone 16 case")
Check SERP results to determine actual intent before writing.
Phase 1: Input Validation
Define target topic/niche. Gather seed keywords from brainstorming, competitor analysis, and tools (Ahrefs, SEMrush, Google Keyword Planner). Gate: Seed keyword list with search volume and difficulty estimates.
Phase 2: Core Algorithm
- Keyword clustering: Group related keywords by intent and topic
- SERP analysis: Check top 10 results for each cluster — identify intent, content format, and depth
- Content gap analysis: Find keywords competitors rank for that you don't
- Content brief: Define: target keyword, intent, format (guide/list/comparison), word count benchmark, required subtopics from SERP analysis
- On-page optimization: Title tag (keyword front-loaded), meta description, H1/H2 structure, internal links, image alt text
Phase 3: Verification
Check: title contains primary keyword, intent matches SERP, all key subtopics covered, internal links to related content. Gate: Content matches identified intent and covers SERP-derived subtopics.
Phase 4: Output
Return content brief and optimization checklist.
Output Format
{
"content_brief": {"primary_keyword": "...", "intent": "informational", "format": "how-to guide", "target_word_count": 2000, "subtopics": ["...", "..."]},
"optimization": {"title": "...", "meta_description": "...", "h2_structure": ["...", "..."], "internal_links": 5},
"metadata": {"search_volume": 2400, "keyword_difficulty": 35}
}
Examples
Sample I/O
Input: Topic "email marketing automation", target market: Taiwan SMBs Expected: Primary KW: "email行銷自動化", intent: commercial investigation, format: comparison guide, 2500 words
Edge Cases
| Input | Expected | Why |
|---|---|---|
| Zero search volume keyword | Consider if it's emerging or nonexistent | May be worth targeting if topically relevant |
| KD > 80 for new site | Target long-tail variants first | New sites can't compete on high-KD terms |
| Mixed intent SERP | Create content matching dominant intent | Don't try to serve all intents in one page |
Gotchas
- Keyword density is dead: There's no optimal keyword density. Write naturally. Forced keyword insertion hurts readability and may trigger spam signals.
- Search volume ≠ traffic: A #1 ranking for a 10K volume keyword won't bring 10K visits. Click-through rates vary by SERP features (ads, featured snippets, PAA).
- Content freshness: Some queries demand fresh content (e.g., "best laptop 2025"). Outdated content drops rankings even if it once ranked #1.
- Cannibalization: Multiple pages targeting the same keyword compete with each other. One strong page outperforms three mediocre ones.
- E-E-A-T: For YMYL topics (health, finance), Google requires demonstrated Experience, Expertise, Authority, and Trust. Anonymous content won't rank.
References
- For keyword clustering methodology, see
references/keyword-clustering.md - For content brief templates, see
references/content-brief-template.md
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/algo-seo-content