Data-driven blog content pipeline for AI agents.
Keyword research → content gaps → SEO writing → GEO optimization → publish.
Works with OpenClaw, Claude Code, or any agent that reads markdown.
Turns your Google Search Console data into published blog content — automatically.
| Skill | What it does |
|---|---|
| keyword-research | Pulls GSC data, classifies intent, clusters topics, scores opportunities, generates content calendar |
| content-gap-analysis | Maps your content vs. competitors, finds missing topics, identifies format gaps |
| blog-writer | Researches, writes, optimizes, and publishes SEO + GEO articles to your CMS |
| geo-content-optimizer | Makes content citable by AI systems (ChatGPT, Perplexity, Google AI Overviews) |
| seo-audit | Finds quick wins from GSC data — indexing issues, CTR drops, cannibalization |
No paid SEO tools required. Just GSC, optional GA4, and your AI agent.
- Solo founders / small teams who need consistent blog output but don't have a content team
- E-commerce sites wanting data-driven content strategies tied to real search data
- SaaS companies running content marketing on autopilot
- SEO practitioners who want to skip the manual research grind
- Anyone with GSC access who wants their agent to handle the content pipeline end-to-end
Impact: Sites using this pipeline typically see 3-5x content output, better keyword targeting (real data vs. guessing), and measurable organic traffic growth within 2-3 months.
git clone https://github.com/watchdealer-pavel/seo-content-autopilot.git
cd seo-content-autopilotPaste this into your agent chat:
I want to set up SEO Content Autopilot for my blog.
Read SETUP.md and walk me through the configuration.
The agent will ask you ~5 questions (site URL, competitors, industry, CMS type) and configure everything.
Replace placeholders in skill files ({{SITE_URL}}, {{COMPETITORS}}, {{INDUSTRY}}) with your values.
# GSC data access (required) — v0.3.0+ recommended for quick wins, regex filters, rich results
git clone https://github.com/watchdealer-pavel/mcp-server-gsc.git
cd mcp-server-gsc && npm install && npm run build
# GA4 reporting (optional)
pip install google-analytics-dataBoth require a Google Cloud service account with access to your GSC/GA4 properties. See connectors/ for setup guides.
| Tool | What it does |
|---|---|
search_analytics |
Core GSC query — clicks, impressions, CTR, position |
enhanced_search_analytics |
Regex filtering + auto quick-wins flagging |
detect_quick_wins |
Find ranking opportunities with revenue estimation |
coverage_report |
Cross-reference sitemap vs analytics for orphaned pages |
rich_results_check |
Audit structured data (Product, FAQ, Review) |
batch_inspect |
Check indexing status for multiple URLs |
list_sitemaps / submit_sitemap |
Sitemap management |
Just ask your agent naturally:
"Find keyword opportunities for my blog"
"What content gaps do we have vs. competitors?"
"Write a blog article about [topic] and publish it as draft"
"Run an SEO audit — what are our quick wins?"
"Optimize this article for AI citations"
The agent reads the matching skill file and follows the workflow. No special commands needed.
# Monthly keyword research (1st of month, 9am)
openclaw cron add "0 9 1 * *" "Run keyword research and save report" --model anthropic/claude-opus-4
# Blog articles 2x/week
openclaw cron add "0 10 * * 1,4" "Write and publish a blog article from keyword priority list" --model anthropic/claude-opus-4Pre-built workflows in scheduling/github-actions/:
- Weekly keyword research → creates GitHub issue with report
- Monthly content gap analysis → creates GitHub issue
- On-demand article publishing → manual trigger
Copy to your repo: cp -r scheduling/github-actions/.github .
See scheduling/system-cron.md for crontab examples.
GSC Data → keyword-research → content calendar
↓
content-gap-analysis → gap priorities
↓
blog-writer → draft article
↓
geo-content-optimizer → AI-optimized
↓
CMS → published
↓
seo-audit → performance tracking → back to keyword research
| Connector | Purpose | Guide |
|---|---|---|
| GSC | Search Console data (required) | connectors/gsc/ |
| GA4 | Analytics traffic data (optional) | connectors/ga4/ |
| CMS | Framer, WordPress, Ghost, or markdown | connectors/cms/ |
Ready-to-use configs for different industries:
- examples/ecommerce/ — E-commerce product blog
- examples/saas/ — B2B SaaS content marketing
MIT
Built for the OpenClaw community.
Inspired by real-world SEO workflows from chronotimepieces.com.
