blog
starsforks
How to install blog?
kostja94/marketing-skills/blog
$npx -y skills add kostja94/marketing-skills --skill blogWhen the user wants to create, optimize, or audit blog index or listing page structure (not a single post). Also use when the user mentions "blog page," "blog index," "blog layout," "content hub," "blog homepage," "blog listing," "subdomain vs subdirectory," "blog structure," or
SKILL.md
| 1 | # Pages: Blog |
| 2 | |
| 3 | Guides blog page structure, SEO, and content marketing best practices. |
| 4 | |
| 5 | **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. |
| 6 | |
| 7 | ## Initial Assessment |
| 8 | |
| 9 | **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for topics, audience, and keywords. |
| 10 | |
| 11 | Identify: |
| 12 | 1. **Blog purpose**: SEO traffic, thought leadership, product education |
| 13 | 2. **Content mix**: Pillar pages, cluster content, news |
| 14 | 3. **Audience**: Buyers, existing customers, developers |
| 15 | |
| 16 | ## Best Practices |
| 17 | |
| 18 | ### Blog Placement: Subdomain vs Subdirectory |
| 19 | |
| 20 | | Option | Example | SEO / Use | |
| 21 | |--------|---------|-----------| |
| 22 | | **Subdirectory** | `example.com/blog` | SEO weight flows to main domain; recommended for product blogs | |
| 23 | | **Subdomain** | `blog.example.com` | Treated as separate entity; consider for distinct brands or technical isolation | |
| 24 | |
| 25 | Choose based on SEO weight distribution, brand consistency, and technical architecture. See [Alignify subdomain vs subdirectory guide](https://alignify.co/zh/seo/create-blog) for details. |
| 26 | |
| 27 | ### Blog Index Page Structure |
| 28 | |
| 29 | | Section | Purpose | |
| 30 | |---------|---------| |
| 31 | | **Featured/Recent** | Highlight newest or most important posts | |
| 32 | | **Categories/Topics** | Help users find by theme | |
| 33 | | **Editor's Picks** | Curate best content | |
| 34 | | **Related posts** | Per-article recommendations | |
| 35 | | **Search** | Help users find specific topics | |
| 36 | |
| 37 | ### Content Strategy |
| 38 | |
| 39 | - **Topical authority**: Topic clusters -> pillar page per core topic + 6-12 cluster articles |
| 40 | - **Intent mapping**: Transactional, problem-aware, informational |
| 41 | - **EEAT signals**: Author bios, Organization schema, citations, changelog |
| 42 | - **Refresh > new**: For established sites, updating existing content often outperforms publishing new posts; avoid changing only the date without substantive edits |
| 43 | - **Quality > quantity**: Fewer high-quality posts beat many mediocre ones; consider deleting, merging, or refreshing underperformers |
| 44 | - **Topic focus**: Avoid blindly expanding topics; dilution can hurt authority on core topics |
| 45 | - **Conversion as north star**: SEO KPIs should tie to leads, signups, or sales -> not just traffic |
| 46 | |
| 47 | ### SEO |
| 48 | |
| 49 | - **Title**: 55 chars, power words, primary keyword |
| 50 | - **Meta**: Clear CTA in description |
| 51 | - **Headers**: H1-H3 hierarchy, table of contents |
| 52 | - **Content depth**: 2,500+ words for pillars; Grade 8 readability |
| 53 | - **URL**: Use **url-slug-generator** -> clean slugs, 3-5 words, under 60 chars |
| 54 | - **Schema**: Article, BlogPosting, FAQPage where relevant |
| 55 | |
| 56 | ### Technical |
| 57 | |
| 58 | - **Core Web Vitals**: LCP < 1.0s on mobile |
| 59 | - **Images**: WebP, compressed |
| 60 | - **IndexNow**: For fast indexing of new posts |
| 61 | |
| 62 | ### Design |
| 63 | |
| 64 | - **Scannable**: Preview copy, thumbnails, hero images |
| 65 | - **Social sharing**: Share buttons on article pages -> see **social-share-generator** |
| 66 | - **Quick answers**: Definition boxes, mini-FAQs for AEO |
| 67 | - **TOC**: Table of contents for Featured Snippets; jump links in long articles; see **featured-snippet**, **toc-generator** |
| 68 | - **CTA placement**: Sidebar CTA or in-paragraph CTA at key conversion points |
| 69 | - **Related/Recent posts**: Manual curation or plugin; same topic cluster |
| 70 | |
| 71 | ## Output Format |
| 72 | |
| 73 | - **Structure** for blog index and post template |
| 74 | - **Content** strategy (pillar + clusters) |
| 75 | - **SEO** metadata and schema |
| 76 | - **Internal linking** approach |
| 77 | |
| 78 | ## Related Skills |
| 79 | |
| 80 | - **card**: Article card structure for blog index; cover image, title, excerpt, date |
| 81 | - **grid, list**: Grid for visual; list for text-heavy blog index |
| 82 | - **article-page-generator**: Single article/post page structure, SEO, schema -> use for individual post templates |
| 83 | - **featured-snippet**: TOC, answer-first format for snippet opportunities |
| 84 | - **url-slug-generator**: URL slug for blog posts; 3-5 words, primary keyword |
| 85 | - **content-strategy**: Content clusters, editorial calendar |
| 86 | - **keyword-research**: Keywords for blog topics |
| 87 | - **title-tag, meta-description, page-metadata, open-graph, twitter-cards**: Blog metadata and social previews |
| 88 | - **schema-markup**: Article schema |
| 89 | - **resources-page-generator**: Blog may be part of resources hub |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
