SEO MCP · Search Console for agents

An SEO MCP server that reads your rankings and ships the fix

Blogizi gives your AI agent one MCP server for the whole content loop: get_search_performance reads your Google Search Console data, and draft_post and update_post publish the changes to your blog. Connect Google with one click. No Google Cloud project, no service account.

Read the setup guide

From $9/mo · read-only Google access · drafts by default

Terminal
$ blogizi draft ./posts/launch-week.md✓ Draft saved to blog.yourapp.com✓ Sitemap, OG image and canonical set # review in the dashboard, then:$ blogizi publish ./posts/launch-week.md

Blogizi vs self-hosted Search Console MCP servers

Works with Claude Code, Claude Cowork, Codex, Cursor and any MCP client over Streamable HTTP. Same account API key you publish with.

TopicSelf-hosted GSC MCPBlogizi
Google setupCloud project, enable API, OAuth client or service account JSONOne OAuth click in the dashboard
Where it runsLocal process (uvx, npx, a binary)Hosted at blogizi.com/api/mcp
Works in sandboxed or cloud agentsUsually notYes
Data depthFull Search Analytics API, filters, often URL InspectionTop 50 queries and pages, period compare, 7 days to 16 months, ranked opportunities, index status per post
Can publish the fixNoYes: draft_post, update_post, publish_post
CostFree (your time)Included in Blogizi, from $9/mo
Best forDeep audits across many propertiesA product blog where the agent writes and you review

If you need every row, country and device filters, or URL Inspection, use an open-source server. Blogizi is for the read → rewrite → publish loop on your own blog.

What your agent can do with it

  1. Find the posts Google is testing. Pull the top queries and pages for any range from 7 days to 16 months, with clicks, impressions, CTR and position, and how each moved against the previous period.
  2. Get the to-do list, already ranked. With include: ["opportunities"] the agent gets queries on page 2 sorted by opportunity, each with the page to improve or a note to write a new post, plus pages with high impressions and low CTR whose titles need work.
  3. Ship the change. The agent edits the markdown and runs update_post, so the fix lands on your blog. Keep it as a draft to review, or publish directly.
  4. Check it landed. With include: ["indexing"] the agent sees which posts Google hasn't indexed yet. Next week, same prompt: the numbers come back compared with last period.
Workflow

Example session

Claude Code
You: What should I write or fix on the     blog this week? Claude → get_search_performance({           days: 28, include: ["opportunities"] })Claude: ~120 clicks a month are within reach.  1. "add blog to nextjs": position 14.2,     2,140 impressions. Improve     /blog/nextjs-blog-setup with a section on MDX.  2. "markdown blog cms": position 11.8,     no matching post. New post.  3. /blog/markdown-vs-notion: 3,200 impressions,     0.4% CTR. Rewrite the title.  Want me to draft #2?You: Yes.Claude → draft_post({ slug: "markdown-blog-cms", … })
Setup

Setup in three steps

  1. Connect Google under Dashboard → Account (read-only scope).
  2. In your project's Search tab, pick the Search Console property: your blog's URL or your whole sc-domain:.
  3. Add the MCP server to your agent:
mcp.jsonjson
1{2  "mcpServers": {3    "blogizi": {4      "url": "https://blogizi.com/api/mcp",5      "headers": {6        "Authorization": "Bearer YOUR_ACCOUNT_API_KEY"7      }8    }9  }10}
Swap in your account API key from Dashboard → Account → API.

How much does it cost?

Every plan includes your own domain, SEO and agent publishing. 7-day trial for $0.

Compare plans

Solo

$9/mo

1 blog

Pro

$19/mo

5 blogs · Search Console

Agency

$49/mo

20 blogs · Search Console

Frequently asked questions

An MCP server that gives AI agents tools for SEO data or SEO actions. Blogizi's covers both halves for a blog: Search Console performance data in, published posts out.

Search Console docs →get_search_performance →Search analytics API →Claude SEO workflow →Google Search Console MCP guide →Publish from Claude Code →

Add a blog wherever your app lives

The same setup works wherever your app is built.

Blog for LovableKeep the app, blog on a subdomainBlog for Vercelyourapp.com/blog via rewritesBlog for WebflowSkip the Webflow CMSBlog for FramerFramer site, Blogizi blogBlog for ReplitBlog next to your Replit appBlog for BoltReal blog routes, not an embedBlog for v0Ship the app, publish the blogNext.js without a CMSAdd a blog to your Next.js app

Start publishing with your agent

Point your blog at Blogizi, let your agent draft the posts, and publish when you're ready. From $9/mo, 7-day trial for $0.

Ready to get started?

Your agents write. Blogizi publishes. Google sends the traffic to your domain.