Rank Tim Logo

Documentation

Integrations · Claude

Use Claude with Google Analytics 4 and Search Console

Ask Claude about your traffic, search queries, AI referrals and SEO opportunities, using the GA4 property and Search Console site you connected in Ranktim — read-only.

What it does
Ranktim's MCP server gives Claude five read-only tools over the Google Analytics 4 and Search Console data Ranktim already collects for your website. Claude can summarise trends, compare periods, look at a page from both sources and surface search opportunities, in the chat you're already having.
Who can use it
Pro, Growth and Enterprise plans, which include Ranktim's MCP server. Google Analytics in Ranktim is also available on Starter, but connecting it to Claude needs one of these plans. Sign in to Claude with the Ranktim account that owns the website; it only sees that account's websites.

What Claude can access

  • get_analytics_overview

    GA4 traffic, engagement, key events and AI referrals plus Search Console clicks and position, compared with the previous period.

    Read
  • get_search_performance

    Search Console queries or pages with clicks, impressions, CTR and average position.

    Read
  • get_page_performance

    A page's GA4 and Search Console metrics side by side, kept as separate sources.

    Read
  • get_ai_referral_traffic

    GA4 sessions referred by AI assistants, by assistant, daily trend and landing page.

    Read
  • find_search_opportunities

    Page-two queries, low-CTR queries and declining queries from Search Console.

    Read
  • Windows of 7, 28, 90, 180 or 365 days, within your plan's Google Analytics history (365 days on Pro, Growth and Enterprise), with the previous period for comparisons when it is cached.
  • GA4 (on-site sessions, users, engagement, key events, AI referrals) and Search Console (Google clicks, impressions, CTR, position) are always reported as separate sources.
  • Claude reads Ranktim's cached reports, refreshed automatically every day and when a new window is requested. Answers say when the data was fetched.
  • Only the website you choose, with its selected GA4 property and Search Console site. Claude cannot see other websites, other properties or other Ranktim accounts.
Read-only boundary
  • The five Google Analytics and Search Console tools are read-only: they cannot change GA4 or Search Console settings, publish content or edit your website.
  • Ranktim reads Google with the read-only permissions you granted when connecting (Analytics read-only, Search Console read-only) and stores a copy of the reports. Claude only reads that copy.
  • Your Google tokens stay encrypted in Ranktim. Claude receives a Ranktim access token only, never your Google password or Google tokens.
  • Ranktim's MCP server also has one unrelated action tool (run_site_audit). You can turn action tools off, or disconnect Claude, in Settings → MCP Server at any time.

Before you start

  • An active Pro, Growth or Enterprise plan.
  • Your website added in Ranktim.
  • A Google account with access to the site's GA4 property, and to its Search Console site for search metrics.
  • Claude (web, desktop or mobile) with custom connectors, or Claude Code.
1

Connect Google Analytics and Search Console in Ranktim

Open Google Analytics → Settings in Ranktim and connect your Google account. Allow Search Console when Google asks, if you want search metrics. Already connected? Check that the status shows Connected.

Connect Google Analytics
2

Select the website, GA4 property and Search Console site

Pick the website in Ranktim's website switcher, then choose its GA4 property and Search Console site on the same settings page. Claude only reads the property and site selected here, and you can change them at any time.

Illustration of Ranktim's Google Analytics settings with sample data: a Google account connected with read-only access, a GA4 property and a Search Console domain property selected.
Illustration of the Ranktim interface with sample data.
3

Add Ranktim's MCP server in Claude

In Claude, open Settings → Connectors → Add custom connector, name it Ranktim and paste the server URL below. In Claude Code, run: claude mcp add --transport http ranktim https://ranktim.com/api/mcp

https://ranktim.com/api/mcp
Illustration of Ranktim's Settings → MCP Server page: the server URL https://ranktim.com/api/mcp with a Copy button and the five read-only Google Analytics and Search Console tools.
Illustration of the Ranktim interface with sample data.
Illustration, not a real Claude screenshot: adding a custom connector named Ranktim with the server URL, then connecting and signing in to Ranktim.
Illustration with sample data, not a screenshot of Claude.
4

Sign in to Ranktim and authorize the connector

Click Connect. Ranktim's sign-in page opens: sign in with the account that owns the website and approve access on the consent screen. Then turn on the Ranktim connector in a chat from the tools menu.

5

Try the example prompts

Copy a prompt below. If you have several websites, name the domain, for example "for example.com". The first request for a new window can take about a minute while Ranktim fetches it from Google.

“Give me my GA4 and Search Console overview for the last 28 days, compared with the previous period.”

Traffic, engagement, key events and AI referrals from GA4, plus clicks, impressions, CTR and position from Search Console, each with its change.

Weeklyget_analytics_overview

“Show my top 20 Search Console queries by clicks for the last 28 days.”

The queries that bring the most Google clicks, with impressions, CTR and average position.

Weeklyget_search_performance

“How is /pricing performing? Show GA4 and Search Console metrics separately.”

Sessions, users and key events from GA4 next to clicks, impressions and position from Search Console for that page.

After you update a pageget_page_performance

“How much traffic did AI assistants send us in the last 90 days, and which pages did they land on?”

AI-referred sessions by assistant, their share of all sessions, the daily trend and top landing pages.

Monthlyget_ai_referral_traffic

“Find Search Console queries on page two with at least 100 impressions and tell me which to improve first.”

Queries averaging positions 11–20, sorted by impressions: candidates for a content or title refresh.

Every two weeksfind_search_opportunities

“Which Search Console queries lost the most clicks compared with the previous 28 days?”

Queries that lost at least 30% of their clicks, with clicks and positions before and after.

Monthlyfind_search_opportunities
Illustration with sample data: an answer to a page-two question, listing three Search Console queries with impressions, clicks and average position.
Illustration with sample data, not a screenshot of Claude.
Limitations
  • Search Console finalizes data with a ~2-day delay, so the most recent days are incomplete.
  • Lists cover the top 100 GA4 landing pages and the top 1,000 Search Console queries or pages per window, so long tails are not exhaustive.
  • GA4 sessions and Search Console clicks measure different things and are not expected to match.
  • The first request for a window Ranktim has not cached yet returns "data pending" while it fetches from Google. Ask again after about a minute.
  • Not available yet: keyword cannibalization (Ranktim stores query and page data separately) and period-over-period changes for individual pages.
Claude + Google Analytics 4 & Search Console