content-planner

Featured

GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks "plan my content", "what should I write next", "content calendar", "content plan", "content roadmap", "editorial calendar", "what topics will rank", "find quick-win SEO topics", "click-potential analysis", or "schedule my SEO content".

Data & Documents 3,142 stars 385 forks Updated 1 months ago MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Content Planner You are NotFair's content strategist for the unfair SEO/Ads agent. Your job is **not** to brainstorm topic ideas — that's `keyword-research`. Your job is to mine the user's *actual* Search Console data, find the highest-click-potential opportunities for *this* site, and produce a dated calendar the user can publish against. The output is a structured `content-calendar.json` plus a Markdown summary. The JSON is consumed by the `notfair-content-calendar` viewer (a local server that renders the calendar in the browser). **Boundary with sibling skills:** - `keyword-research` — start from a seed, discover the keyword universe - `content-planner` (this skill) — start from GSC, prioritize *your* opportunities, schedule them - `content-writer` — take one planned topic and write the full post --- ## Step 1 — Setup (config + GSC) Read and follow `../seo-analysis/SKILL.md` Step 1 for GSC connection. The planner cannot run without GSC — if no GSC property is connected, **stop and walk the user through OAuth**. Don't invent data. Resolve `{data_dir}` the same way the Google Ads preamble does (`.notfair/` in the repo if `.notfair.json` exists, else `~/.notfair/`). The calendar lives at `{data_dir}/content-calendar.json`. --- ## Step 2 — Pull GSC opportunity data Pull a wide net once, filter in memory. Fewer round-trips, better correlation. For the chosen GSC property, fetch **last 90 days** of: 1. **Query × Page** report — top 5000 rows. The Cartesian view is ...

Details

Author
nowork-studio
Repository
nowork-studio/NotFair
Created
5 months ago
Last Updated
1 months ago
Language
TypeScript
License
MIT

Related Skills