Google Search Console in Claude: RightBlogger MCP Setup

Google Search Console holds the answers to most of your SEO questions. The problem is the interface buries them. Finding striking-distance keywords, spotting pages that lose clicks every month, or checking CTR by device usually means exporting a CSV, deleting the summary rows, and building a pivot table you will not look at twice.

There is a faster way. You can connect Search Console to the AI you already use and ask in plain language, with your own live data. No spreadsheets, no copy and paste, no API keys to manage.

This guide shows you how to do it with the RightBlogger MCP, a connector that puts your Search Console performance, keyword research, and your published posts inside Claude, ChatGPT, or Cursor. I will walk through the setup screen by screen, then share three prompts you can paste in today.

Key Takeaways

One sign-in, no API keys. You add a single URL and log in with your RightBlogger account. Standard OAuth, so your AI client never sees a password or a key.
It reads your real data. Live Search Console metrics, RightBlogger’s keyword database, and the posts on your connected CMS. The same sources the app uses, not a stale copy.
It is included with your plan. No separate subscription and no extra cost.
Reads today, edits soon. The tools are read-only right now, which means it can analyze and recommend, but it will not touch your site.

What You Can Do Once Search Console Is Connected

Once the connector is live, you stop navigating reports and start asking questions. A few examples you can run in one prompt:

Pull every keyword sitting in positions 4 to 15 with real impressions, your fastest path to page one.
Find pages that rank well but get a weak click-through rate, the ones that need better titles, not better rankings.
Spot keyword cannibalization, where two of your pages compete for the same query.
Compare the last 28 days against the previous 28 to catch content decay early.

The prompts that do all of this are further down. First, the setup.

What the RightBlogger MCP Is

MCP stands for Model Context Protocol, an open standard that lets AI clients talk to outside tools and data. The RightBlogger MCP is a remote MCP server that connects your RightBlogger account to those clients.

Once you connect it, your AI can pull your Search Console performance, research keywords from RightBlogger’s database, and read the posts on your connected CMS, all by asking in plain language. It reuses the same Search Console and CMS connections you set up for the Site Agent, so if you already use that, there is nothing new to wire up.

How to Connect Google Search Console to Claude

You need three things: a RightBlogger account, a project with Google Search Console connected, and a Claude account. The whole setup takes about a minute, and there are no API keys to manage.

Step 1: Open the connector settings in Claude

In Claude, open Settings and find Connectors. In the current version, connectors live under Customize, so follow that link to manage them.

Claude Settings showing Connectors have moved to the Customize area.

Step 2: Add a custom connector

On the Connectors screen, click the plus icon and choose Add custom connector.

Claude Customize Connectors panel with the Add custom connector option open.

Step 3: Paste the RightBlogger URL

Name it RightBlogger, paste the connector address below, then click Add.

https://rightblogger.com/api/mcp

Claude Add custom connector dialog with RightBlogger and the MCP URL entered.

Step 4: Connect your account

The connector shows up but is not linked yet. Click Connect to start the sign-in.

RightBlogger connector in Claude showing a Connect button before authorization.

Step 5: Authorize access

RightBlogger asks you to approve the connection. It only requests your identity and email address, nothing that can change your site. Click Allow.

RightBlogger Authorize access screen requesting identity and email with Allow and Deny buttons.

Step 6: Set tool permissions

Your projects connect and the ten read-only tools appear, including gsc_query, gsc_status, and keyword_research. Set them to allow so Claude can pull data without stopping to ask each time.

RightBlogger tool permissions in Claude listing read-only tools like gsc_query and keyword_research.

That is the whole setup. Open a new chat and ask a question about your search performance. Something as simple as “Using RightBlogger, what are my top pages in Search Console?” returns a clean table of clicks, impressions, CTR, and position.

Claude using RightBlogger to return top Search Console pages with clicks, impressions, CTR, and position.

Using a different client? The URL is the same everywhere. In Claude Code, run claude mcp add --transport http rightblogger https://rightblogger.com/api/mcp. In Cursor, add the server to your .cursor/mcp.json. In ChatGPT, use Settings, then Connectors (Developer Mode, currently in beta) and paste the same URL.

The Tools You Get

The connector exposes ten read tools, each scoped to the projects you can access. Search Console is the headline, but the keyword and CMS tools are what make the analysis genuinely useful, because Claude can connect your rankings to your actual content.

Tool	What it does
`list_projects`	Lists the sites you can access, with CMS and Search Console status. Claude calls this first.
`gsc_query`	Clicks, impressions, CTR, and position, grouped by page, query, country, device, or date, with filters.
`gsc_status`	Confirms Search Console is connected and which property it points to.
`keyword_research`	RightBlogger’s keyword engine: volume, CPC, and difficulty for any seed term.
`search_posts` / `get_post`	Search and read the posts on your connected CMS (WordPress, Ghost, or Webflow), including the raw body and SEO meta.
`search_content` / `get_content`	Search and read your RightBlogger drafts and generated articles.
`list_planner`	Your content calendar: planned and scheduled posts with dates and destinations.

The tools are read-only today. Editing is coming soon, which will let you ask Claude to update a post or its SEO meta directly, with reversible changes.

7 Interesting Use Cases for a Search Console Connection

These move past basic reporting. Each one uses your live data, so the output is specific to your site. Swap in your own domain where it says [your site], and mention RightBlogger in the prompt so Claude picks the right connector.

Prompt 1: Striking-distance keywords

Using RightBlogger, pull all my Google Search Console queries for [your site] over the last 28 days. Show me the ones ranking in positions 4 to 15 that have the most impressions, these are my best quick-win opportunities. Sort by impressions and tell me which single page each query belongs to.

What it surfaces: keywords one edit away from page one or the top three, the highest-ROI work on the site.

Prompt 2: CTR and cannibalization audit

Using RightBlogger, query my GSC data for [your site] grouped by both page and query for the last 28 days. Flag two things: (1) pages that rank well (position under 10) but have a low click-through rate, those need better titles and meta descriptions, not better rankings; and (2) any query where multiple URLs are competing for the same term, since that is keyword cannibalization hurting both pages.

What it surfaces: easy title and meta rewrites, plus internal competition that is quietly splitting your traffic. The CTR side pairs well with the workflow in finding blog posts with high impressions and low CTR.

Prompt 3: Content decay

Using RightBlogger, compare my GSC page performance for [your site] across two periods: the last 28 days versus the 28 days before that. Show me the pages that lost the most clicks between the two windows. These are my content-refresh priorities. If seasonality might be a factor, also compare against the same 28-day window from last year.

What it surfaces: the posts quietly losing traction, your highest-value refresh targets, with seasonality controlled for. It is the live version of a full content decay audit.

Prompt 4: Rewrite a weak title using the live post

Using RightBlogger, find the page on [your site] with the most impressions but a click-through rate below my site average over the last 28 days. Read the live post, then write three new title options and a meta description, each based on the exact queries that page already ranks for in Search Console.

What it surfaces: a ready-to-paste title and meta rewrite grounded in your real content, not a guess. Reading the actual post is the step a tool that only pipes numbers cannot do.

Prompt 5: Spot rising queries before competitors

Using RightBlogger, compare my Search Console queries for [your site] over the last 28 days against the previous 28 days. Show me the queries gaining the most impressions, sorted by the size of the jump. These are the topics picking up momentum that I should publish on or expand now.

What it surfaces: the searches trending up for your site, so you can ride the momentum instead of finding out months later.

Prompt 6: Find device and country gaps

Using RightBlogger, show my Search Console clicks, CTR, and average position split by device and by country for my top 10 pages on [your site] over the last 28 days. Where am I underperforming, for example strong desktop CTR but weak mobile, or high impressions in a country where I barely rank?

What it surfaces: the segment problems a single sitewide number hides, like a mobile CTR gap or a country where you are leaving clicks on the table.

Prompt 7: Spot AI-style and conversational queries

Using RightBlogger, pull my Search Console queries for [your site] over the last 3 months and flag the long, conversational ones: questions and phrases of five or more words that read like something a person would type into an AI assistant. Which of these am I getting impressions for but not ranking well on?

What it surfaces: the natural-language and AI-search queries your audience is starting to use, so you can publish direct answers before competitors catch on.

The same connection reaches beyond Search Console. Keyword research and your content calendar are tools too, so you can ask Claude to pull related keywords from RightBlogger’s database for a topic, or to check whether anything on your planner targets a query you already rank for.

Why This Beats Exporting CSVs

You can still get Search Console data into an AI by hand. Export the CSV, delete the summary rows so the headers do not confuse the model, and upload the file with a long prompt explaining what it is. That works for a one-time check, but it falls apart as a habit for three reasons.

The export is a snapshot. A CSV is yesterday’s data frozen in a file. The connector reads live, so you can ask a follow-up question and get fresh numbers.
The file has no context. A spreadsheet of queries does not know what your pages say. Because the connector can also read your posts, Claude can tie a weak query to the exact paragraph that needs work.
It does not scale. Nobody exports and cleans a CSV every morning. A saved connector turns a 10-minute chore into a one-line question.

Two honest limits worth knowing. Each Search Console query returns up to 1,000 rows, so very large sites work in segments by filtering to a section or a date range. And Search Console data lags about three days, so the freshest numbers you will see are from a few days back. That lag is a Google constraint, not a RightBlogger one, and it applies to the export route too.

How Secure It Is

The connector uses the same identity and access rules as the RightBlogger app. You sign in through standard OAuth 2.1, so your AI client gets a scoped token and never your credentials. The consent screen only requests your identity and email, and every call checks your access to a project first, which means you only ever see your own sites and data.

It is also read-only today, so there is no risk of an AI changing your site while it analyzes it. Teammates connect with their own login and see only the projects they belong to. If you want a version that acts on its own and improves your site automatically on a schedule, that is what the Site Agent does, and it runs through the same connections.

Final Thoughts

Search Console is the source of truth for how you show up in Google. The hard part has always been turning that data into a decision. Connecting it to Claude removes the export step and lets you ask the question directly, with your own numbers and your own posts in the room.

Add the connector once, sign in, and start with the striking-distance prompt above. It is the fastest way to feel the difference. You can set up the RightBlogger MCP here, and it is included with every plan.

FAQs

Is the RightBlogger MCP free?

Yes. It is included with every RightBlogger plan at no extra cost. You can see what each plan includes on the pricing page.

Which AI clients can connect?

Any client that supports remote MCP servers over Streamable HTTP. That includes Claude (Desktop, web, and the CLI), Cursor, and ChatGPT in Developer Mode (currently beta). The connector URL is the same everywhere.

Does it see my Google password?

No. You connect Search Console to RightBlogger once through Google’s official read-only permissions, and your AI client signs in to RightBlogger through OAuth. The client receives a scoped token, never a password or an API key.

Can it edit my posts?

Not yet. The tools are read-only today, so the AI can analyze and recommend but cannot change anything. Editing is coming soon, and when it lands, every change will be reversible.

How is this different from uploading a Search Console export?

An export is a static snapshot with no knowledge of your site. The connector reads live data and can also open your actual posts, so the AI can connect a weak query to the content that needs changing and answer follow-up questions without a new file.

How fresh is the data?

It is as fresh as Search Console itself, which runs about three days behind. When you ask for the last 28 days, the connector reads the most recent data Google has finalized.