usulpro
/
banatie-strategy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
banatie-strategy/content/CONTENT-TRACKS.md

12 KiB
Raw Permalink Blame History

Content Tracks: SEO-First & Product-First

Date Created: January 9, 2026
Purpose: Two parallel content strategies for Banatie
Status: Active
Source: Keyword research ($3.60 DataForSEO) + strategic discussion

Overview

Два параллельных трека контента:

Track Цель Измерение успеха
SEO-First Трафик, domain authority, ранжирование Позиции в Google, organic traffic
Product-First Conversion, validation, brand positioning User engagement, signups, feedback

Принцип: SEO-first даёт трафик. Product-first конвертит и валидирует. Оба нужны параллельно.

TRACK 1: SEO-FIRST

Цель: Low-hanging SEO fruits. Начать ранжироваться сейчас → результаты через 3-6 месяцев.

Validated Opportunities

# Контент Volume KD Тип Приоритет Brief
1 Placeholder Images API 14,800 32 Landing + Guide 🔥 HIGH 0-inbox/placeholder-images-api.md
2 Midjourney Alternatives for Developers 1,300 3 Listicle 🔥 URGENT 0-inbox/midjourney-alternatives-developers.md
3 Dark Mode Placeholder Images 4,400 2 Docs section MEDIUM Data в research/keywords/placeholder-niche-deep-dive-2026-01-02.md
4 Advertising Images Guide 1,600 4 Guide MEDIUM 0-inbox/advertising-images-guide.md — нужна SERP validation

Needs SERP Validation

Keyword Volume KD Риск
marketing images 2,900 19 Может быть stock photo intent
social media images 1,900 14 Может быть stock photo intent
blog images 720 7 Низкий риск

Include as Sections (не standalone)

Keyword Volume KD Где включить
test images 6,600 9 H2 в Placeholder guide
lorem picsum 880 15 Comparison в Placeholder
placeholder api 880 28 Placeholder guide

Skip (validated as wrong intent)

Keyword Volume Причина
banner images 27,100 Stock photo intent, dominated by Unsplash/Adobe

SEO Content Details

1. Placeholder Images API (PRIMARY)

Target: /placeholder-images landing page

Keywords cluster:

  • placeholder images (14,800)
  • placeholder api (880)
  • lorem picsum (880) — comparison
  • dummy images (720)
  • test images (6,600) — as section

SERP Validation: ✅

  • "AI placeholder images" в related searches
  • Competitors beatable (placehold.co, Lorem Picsum)
  • 100% developer intent

Differentiation:

Feature placehold.co Lorem Picsum Banatie
Real images ❌ ✓ (random) ✓ (contextual)
AI-generated ❌ ❌ ✓
Prompt-based ❌ ❌ ✓
Live URLs ❌ ❌ ✓

Content structure:

  1. What are placeholder images (answer base intent)
  2. Best placeholder image services (comparison)
  3. AI Placeholder Images: Next Generation (our pitch)
  4. Getting started with Banatie Live URLs
  5. Code examples (HTML, React, Next.js)

Outreach opportunity: loremipsum.io ranks with "15 Best Placeholder Generators" — get listed.

2. Midjourney Alternatives for Developers (URGENT)

Target: Blog post (dev.to, cross-post)

Why urgent: Volume declining rapidly (8.1K → 1.3K). Window closing.

Keywords:

  • midjourney alternative (1,300, KD 3)
  • midjourney api (720, KD 35)
  • ai image generator api (590, KD 32)

Angle: "5 Midjourney Alternatives with API Access for Developers"

Include competitors:

  • Replicate
  • fal.ai
  • Runware
  • DALL-E API
  • Banatie (our positioning)

Key message: Midjourney = Discord-only, no API. Developers need programmatic access.

3. Dark Mode Placeholder Images

Target: /docs/placeholders/dark-mode

Keywords:

  • image placeholder dark (4,400, KD 2)
  • placeholder image dark (1,300, KD 6)

Why separate: Combined 5.7K volume, ultra-low KD. Easy win.

Content: How to generate dark-mode-friendly placeholders with Live URLs.

4. Advertising Images Guide

Target: Blog post or guide

Keywords:

  • advertising images (1,600, KD 4)
  • promotional images (880, KD 17)

Status: Needs SERP validation before writing. Could be stock photo intent like "banner images".

Angle if validated: "How developers can generate advertising images programmatically"

TRACK 2: PRODUCT-FIRST

Цель: Core product positioning, conversion, validation. Нужно независимо от SEO volume.

Core Content

# Контент SEO Vol Зачем нужен Тип Приоритет Brief
1 Live URLs Guide ~0 Core feature documentation Docs + Landing 🔥 HIGH Нет brief, core docs
2 Claude Code + Banatie Workflow 10-20 ICP контент, позиционирование Tutorial 🔥 HIGH 0-inbox/claude-code-image-generation-mcp.md
3 Cursor Image Generation Workflow ~0-50 ICP контент, workflow demo Tutorial HIGH 0-inbox/cursor-image-generation-workflow.md
4 MCP Image APIs Compared ~0 Competitive positioning Comparison MEDIUM 0-inbox/mcp-image-apis-compared.md
5 Vibecoding Images Tutorial ~0 Future SEO, trend positioning Tutorial MEDIUM Нет brief

Blocked Content

Контент Блокер
MCP Integration Guide MCP feature must ship first
Cursor Workflow (полный) MCP feature must ship first

Product Content Details

1. Live URLs Guide (CORE)

Target: /docs/live-urls/ + /live-urls landing

Why critical:

  • Core differentiator от всех конкурентов
  • Без гайда пользователь не поймёт главную фичу
  • Validation scenario для interviews

Content structure:

  1. What are Live URLs
  2. How they work (URL → generation → CDN)
  3. Use cases (placeholders, prototypes, production)
  4. Code examples (HTML, React, Next.js)
  5. Prompt syntax and parameters
  6. Best practices

2. Claude Code + Banatie Workflow

Target: Tutorial (blog + docs)

Keywords (low but exact ICP):

  • can claude code generate images (20 vol)
  • claude code image generation (10 vol)

Why important despite low volume:

  • Direct hit на наш ICP
  • Показывает что мы понимаем workflow
  • Может ранжироваться по unexpected queries
  • Needed для validation interviews

Content structure:

  1. The problem: broken images in Claude Code projects
  2. Current solutions (copy stock photos manually)
  3. Better way: Banatie integration
  4. Step-by-step setup
  5. Real examples with prompts
  6. Before/after comparison

3. Cursor Image Generation Workflow

Target: Full tutorial (blog + cross-post)

Why important:

  • Cursor = massive user base
  • AI-first developers = our ICP
  • Detailed tutorial = conversion
  • Competitors have docs, we need tutorial

Content structure:

  1. The old way (context switching pain)
  2. The new way (MCP integration)
  3. Setup guide (step-by-step)
  4. Real use cases with code
  5. Comparison: Banatie vs other MCP servers
  6. Advanced features (@name, project organization)

Note: Partially blocked until MCP ships. Can prepare outline and screenshots.

4. MCP Image APIs Compared

Target: Comparison article (blog)

Why important:

  • Shows we understand ecosystem
  • Honest comparison = trust
  • Competitive positioning

Compare:

  • Replicate MCP
  • Together AI MCP
  • fal.ai MCP
  • Banatie MCP
  • Amazon Bedrock MCP

Criteria:

  • Setup time
  • Cost per image
  • Project organization
  • Developer experience

Key message: "You don't need cheapest. You need the one that fits your workflow."

5. Vibecoding Images Tutorial

Target: Tutorial (blog)

Why despite 0 volume:

  • Vibecoding = explosive trend (10 → 135K in 3 months)
  • Search behavior not formed yet
  • Early indexed content = advantage when demand comes
  • Shows we understand the movement

Content structure:

  1. What is vibecoding
  2. The image problem in vibecoding
  3. How Banatie solves it
  4. Workflow examples
  5. Live URLs for rapid prototyping

Site Structure Plan

Landing Pages (banatie.app)

/placeholder-images     ← SEO landing (14.8K vol)
/live-urls              ← Product feature landing
/integrations/cursor    ← Workflow landing (when MCP ready)
/integrations/claude-code ← Workflow landing

Documentation

/docs/
├── getting-started/
├── live-urls/           ← Core feature docs (Product-first)
├── placeholders/        ← SEO + utility
│   ├── dark-mode/       ← 4.4K vol, KD 2
│   ├── sizes/
│   └── profiles/
├── integrations/
│   ├── mcp/
│   ├── cursor/
│   └── claude-code/
└── api-reference/

Blog (dev.to, cross-post)

  • Midjourney Alternatives (URGENT, SEO)
  • MCP Servers Compared (Product)
  • Claude Code + Banatie Workflow (Product)
  • Cursor Image Generation (Product, when MCP ready)

Priority Summary

TOP 5 (делать первыми)

  1. Placeholder Images Landing — SEO foundation (14.8K vol) ✅ Brief ready
  2. Live URLs Documentation — core product story
  3. Midjourney Alternatives — URGENT, easy win (KD 3) ✅ Brief ready
  4. Claude Code Workflow Tutorial — ICP content ✅ Brief ready
  5. Cursor Workflow Tutorial — ICP content (blocked by MCP) ✅ Brief ready

SECONDARY

  1. Dark Mode Placeholders (docs section)
  2. Advertising Images (needs SERP validation)
  3. MCP Comparison Article
  4. Vibecoding Tutorial (future SEO bet)

Research Files Reference

Keyword Research:

  • banatie-content/research/keywords/research-report-2026-01-09.md — final report
  • banatie-content/research/keywords/serp-analysis-2026-01-09.md — SERP validation
  • banatie-content/research/keywords/placeholder-niche-deep-dive-2026-01-02.md — placeholder deep dive
  • banatie-content/research/keywords/ai-web-dev-images-2026-01-09.md — main research

Content Briefs:

  • banatie-content/0-inbox/placeholder-images-api.md
  • banatie-content/0-inbox/midjourney-alternatives-developers.md
  • banatie-content/0-inbox/advertising-images-guide.md
  • banatie-content/0-inbox/claude-code-image-generation-mcp.md
  • banatie-content/0-inbox/cursor-image-generation-workflow.md
  • banatie-content/0-inbox/mcp-image-apis-compared.md

Key Insights from Research

  1. Solution keywords > Problem keywords

    • "placeholder images" (14.8K) vs "how to get images for vibe coding" (0)
    • Target what people search, not what they need

  2. Generic > AI-prefixed

    • "placeholder images" (14.8K, KD 32) vs "ai image generator" (high KD)
    • Position as "images for developers" not "AI image generator"

  3. Long-tail questions = ~0 volume

    • People don't google problems, they google solutions
    • Don't target question keywords standalone

  4. SEO ≠ Market validation

    • SEO shows search behavior, not real pain
    • Customer interviews still needed

Document Owner: @men + Oleg
Last Updated: January 9, 2026
Related: BANATIE-CONTENT-INTEGRATION.md