Claude Code alone
- Writes code and reads your repo
- No live keyword or domain data
- Cannot read your Search Console
- No publishing pipeline to your blog
Claude Code + VibeSEO MCP
Claude Code for SEO. Powered by VibeSEO MCP.
Run keyword research, audits, GSC reads, and content workflows from your terminal. Claude Code plus VibeSEO MCP turns SEO into commands you can script, repeat, and commit alongside the code that ships your site.
How it compares
Claude Code + VibeSEO MCP
- Keyword research from the terminal
- Site audits triggered from a prompt
- Search Console data in conversation
- Draft → approve → publish via VibeSEO
What you get
Scriptable keyword research
Ask Claude Code to pull volumes, difficulty, and related queries — fold the result into a JSON file in your repo or feed it into the next prompt.
Audits next to your code
Trigger a VibeSEO site audit, read crawl issues, and have Claude Code open the relevant template, layout, or route file to fix them in place.
GSC data in the terminal
Pull Search Console queries, top pages, and trends as part of a release review — without opening a separate dashboard.
Drafts from real data
Generate SEO-ready article drafts with title, meta, headings, FAQ, internal links, and CTA — based on live keyword data instead of imagined examples.
Repeatable SEO recipes
Save common prompts (weekly audit, monthly content batch, GSC review) as CLAUDE.md instructions or shell snippets, then re-run them on a schedule.
Human approval preserved
Claude Code can prepare drafts and queue them, but VibeSEO still enforces the approval gate before anything appears under your brand.
From research to indexed pages
VibeSEO keeps the human approval step, then handles the public surface search engines expect.
- Analyze
VibeSEO reads your site and market
Your pages, offer, audience, and search landscape inform which topics are worth pursuing.
- Draft
SEO-ready articles are prepared
Titles, meta descriptions, headings, FAQ blocks, internal links, and CTAs are built into each draft.
- Approve
You control what goes live
Review, edit, reject, or reschedule. Nothing publishes under your brand without approval.
- Publish
Pages go live on a crawlable blog
Approved articles render as indexable HTML — on the shared host, your subdomain, or yoursite.com/blog — with sitemaps, canonicals, and structured data.
- Track
Search signals flow back
Google Search Console data shows impressions, clicks, and progress at the article level.
Common questions
How do I connect VibeSEO MCP to Claude Code?
In your terminal run: claude mcp add --transport http vibeseo https://mcp.vibeseo.dev/mcp. Claude Code will open an OAuth flow in your browser — sign in with your VibeSEO account, and the connection persists across sessions.
Can I commit my VibeSEO MCP setup to a repo?
You can commit the server entry (host + transport) to .claude/mcp.json so collaborators have the same connector. Authorization tokens stay local to each developer, so secrets never end up in source control.
Which SEO tasks are best run from Claude Code?
Repeatable, scriptable work: weekly audit runs, monthly content batches, release-time GSC reviews, and batch keyword research feeding a content calendar. Interactive analysis still works, but the CLI shines for repetition.
Does VibeSEO see my code?
No. VibeSEO MCP only exposes SEO tools (keywords, audits, GSC, content, publishing). Your repo contents stay between Claude Code and Anthropic; VibeSEO receives only the SEO-related arguments you send to its tools.
Run SEO from Claude Code.
Free MCP server, one CLI command to connect. Keyword research, audits, and publishing — all from the terminal you already live in.
Start free