What this prompt does
This prompt takes your domain context — authority, existing content, competitors, and business goals — and produces a structured 90-day editorial plan built around topic clusters, not a flat keyword list. The template forces the AI to organize keywords by search intent before assigning them to calendar slots, which means informational posts land at the top of funnel and transactional pages get scheduled when supporting content already exists to link to them.
The content brief section is where the real work happens. For each priority post, the AI produces a competing-pages analysis and a "unique angle" field — the template explicitly asks what makes this better than existing content, not just what keywords to target. That framing pushes output toward genuine differentiation rather than thin rewrites of SERP incumbents. Your [business_goals] input shapes the CTA and conversion goal fields inside each brief, so a "grow trial signups" goal produces different CTAs than a "build newsletter list" goal.
The E-E-A-T signal at the end of the template is not decorative. It constrains the AI to reason about developer audiences specifically, which changes the tone and depth of suggested content types compared to a generic SEO calendar prompt.
When to use it
- You are launching a developer tools SaaS and need 12 weeks of content before your Product Hunt launch.
- Your blog has scattered posts with no internal linking and you need a plan to consolidate authority into pillar pages.
- You have a developer-facing API product and need to map documentation-adjacent content to commercial keywords without sounding like marketing copy.
- You are an agency onboarding a new devtools client and need a deliverable-quality calendar in one session.
- Your existing content targets high-difficulty keywords and you need a reset toward low-competition, long-tail terms first.
Example output
The calendar section outputs as a table — paste it directly into Notion or a spreadsheet:
| Week | Title | Target Keyword | Search Intent | Word Count | Content Type | Pillar/Support |
|------|-------|----------------|---------------|------------|--------------|----------------|
| 1 | Docker Compose for Production: The Complete Guide | docker compose production | Informational | 3,800 | Pillar | Pillar |
| 3 | Managing Secrets in docker-compose.yml | docker compose env secrets | Informational | 1,400 | Supporting | Supports Week 1 |
The content brief for the Week 1 pillar looks like this:
Title: "Docker Compose for Production: The Complete Guide"
Target Keyword: docker compose production
Search Intent: Informational → Educational
Unique Angle: Existing top results skip multi-service health checks and
zero-downtime deploys. Cover both with working compose files,
not pseudocode. Add a "what breaks in prod" section incumbents avoid.
CTA: Subscribe to the DevOps newsletter (maps to business_goal: grow list)
Internal links to: env secrets post (Week 3), Docker volumes guide (existing)
Pro tips
- Set
[domain_authority]honestly — the AI uses this as a signal to calibrate keyword difficulty targeting. A DA 12 site should be pushed toward KD under 20 for the first six weeks, and a realistic DA input makes that happen. That said, always validate every suggested keyword and difficulty score in Ahrefs, SEMrush, or Google Search Console before committing — the AI is generating plausible estimates from training data, not live SERP data. - Keep
[posts_per_week]at 1–2 unless you have dedicated writers. The calendar quality degrades when it has to pad 5 posts/week for a solo founder. - Use
[existing_content]to paste a bullet list of your current post titles, not just a URL. The AI uses this to build the internal linking map — without it, the plan ignores your existing authority. - Run the prompt once for planning, then feed individual rows from the calendar back to the prompt as separate "content brief" requests with the full brief section as context. The calendar is the strategy layer; the briefs are the execution layer. This two-pass workflow produces significantly sharper briefs than trying to do both in one run.
- After generating, sanity-check the pillar page titles against your
[competitors]manually. The AI cannot access live SERPs, so it may suggest a pillar topic a competitor already dominates with a five-year-old authoritative post.
