Skip to content

Hosted MCP server for SEO

Put your Search Console in the chat.

RankLens gives Claude, ChatGPT, Cursor and other AI assistants live access to Search Console, GA4 and 38 SEO tools. Sign in with Google, paste one URL, and ask your question.

Free plan: one property and 100 tool calls a month. No card needed.

Example conversation. Someone asks why organic clicks dropped. The assistant calls three RankLens tools, then explains that clicks fell 18 percent starting October 19, during a Google core update, concentrated on six guide pages, with no indexing problems found.

Organic clicks on example.com dropped last month. What happened?

  1. compare_search_periods page, last 28 days vs previous 1.4s
  2. list_algorithm_updates since Sep 1 0.2s
  3. check_indexing_issues 6 URLs under /guides/ 2.1s

Clicks fell 18%, from 41.2k to 33.8k. The slide starts on Oct 19, the second day of a Google core update, and six pages under /guides/ account for most of it.

Indexing is clean on all six, so this looks like a ranking change, not a technical one. Want a page-by-page brief for those guides?

Works with any client that supports remote MCP

  • Claude
  • ChatGPT
  • Cursor
  • Windsurf
  • Codex
  • Zed
  • Gemini CLI
  • Claude Code

The data and checks an SEO would reach for

Raw Search Console rows are only the start. RankLens also does the analysis, so your assistant gets findings it can explain instead of 25,000 rows it has to guess at.

Ask it the way you'd ask a colleague

Eight questions people ask in their first week, and the tools that answer them.

Browse all 38 tools
  • Monthly report

    “Write October's SEO report for example.com, with what changed and what to do next.”

    Tools used: generate_seo_reportga4_organic_landing_pages

  • Cannibalization

    “Which of my pages are competing for the same queries, and which one should win each?”

    Tools used: detect_keyword_cannibalizationget_search_by_page_query

  • Indexing audit

    “Check my top 25 product URLs and tell me which aren't indexed and why.”

    Tools used: batch_url_inspectioncheck_indexing_issues

  • Striking distance

    “Find keywords on page two that would be worth pushing onto page one.”

    Tools used: find_striking_distance_keywordsfind_ctr_opportunities

  • Core Web Vitals

    “Is the pricing page passing Core Web Vitals on mobile? What's dragging LCP?”

    Tools used: get_core_web_vitalsaudit_page_seo

  • Schema audit

    “Validate the structured data on these five recipe pages and list missing fields.”

    Tools used: validate_structured_data

  • Traffic drop diagnosis

    “Traffic fell in mid-October. Was it a Google update, or something we broke?”

    Tools used: compare_search_periodslist_algorithm_updatescheck_http_status

  • Content brief

    “Write a brief to improve /guides/trail-shoes: what it ranks for and what the copy is missing.”

    Tools used: page_optimization_brief

Set up in about five minutes

  1. Sign in with Google

    Pick the Search Console properties and GA4 properties your assistant is allowed to see. We request read-only access.

  2. Add RankLens to your assistant

    Paste the server URL into your client's connector or MCP settings. Most clients then open a sign-in window, and you approve the connection.

    https://api.ranklens.app/mcp
  3. Ask in plain language

    Your assistant decides which tools to call, runs them against your live data, and answers with numbers you can check.

Client without OAuth? Create an API key in the dashboard and send it as a bearer token. How to use API keys

Hosted, and more than a Search Console wrapper

Open-source Search Console MCP servers are great if you want to run your own. Here's what changes when someone runs it for you.

How RankLens compares with a self-hosted open-source MCP server and with using no MCP server
Capability RankLensSelf-hosted open-source MCPNo MCP (exports and screenshots)
Setup Yes: Sign in with Google, paste one URL Partly: Install Python, create a Google Cloud project and OAuth credentials, edit each client's config Partly: Export CSVs and upload them to every chat
Works in Claude.ai and ChatGPT on the web Yes: Yes, over remote MCP with OAuth No: Usually local only, unless you host and secure it yourself Partly: Only as file uploads
Search Console data Yes: Live, up to 25,000 rows per call Yes: Live Partly: A stale snapshot, capped at 1,000 rows in the UI export
Google Analytics 4 Yes: Included on Pro and Max No: Not included Partly: Separate manual exports
Computed insights Yes: Striking distance, CTR gaps, cannibalization, decliners and more Partly: The model has to work it out from raw rows No: Spreadsheet work
Technical checks Yes: Page audits, structured data, robots.txt, sitemaps, Core Web Vitals No: Not included No: Separate tools
Algorithm update timeline Yes: Built in, so drops are checked against known updates No: No No: You look it up
Dashboard and drop alerts Yes: Yes No: No No: No
Multiple Google accounts Yes: Up to 5 on Max Partly: One per configured install Partly: Switch accounts by hand
Upkeep Yes: We run, update and monitor it Partly: You update dependencies and keep tokens fresh Partly: Repeat the exports every time

Start free, upgrade when it earns its keep

Every plan includes the dashboard, alerts, API keys and the algorithm update timeline.

Compare every feature

Yearly billing gets you two months free.

  • Free

    Try it on one site and see what your assistant can do with real data.

    $0 / month

    Free forever, no card needed

    Start for free
    • 1 property
    • 1 Google account
    • 100 tool calls a month
  • Starter

    For site owners who want answers, audits and opportunities, not just numbers.

    $15 / month

    Billed monthly

    Choose Starter
    • 3 properties
    • 1 Google account
    • 3,000 tool calls a month
  • Max

    For agencies running many client sites across several Google accounts.

    $99 / month

    Billed monthly

    Choose Max
    • Unlimited properties
    • 5 Google accounts
    • Unlimited tool calls

Read-only unless you say otherwise

Your assistant gets answers from your data. It doesn't get your Google credentials, and it can't change anything without you asking.

Read the privacy policy
  • Read-only by default

    We ask Google for read-only Search Console and Analytics scopes. Write access is a separate opt-in.

  • Encrypted tokens

    Google refresh tokens are encrypted at rest and never sent to your AI client. Clients get their own short-lived tokens.

  • Revoke anytime

    Disconnect any AI client, API key or Google account from the dashboard, and access stops on the next request.

  • Confirmation for changes

    Tools that submit or delete sitemaps and properties refuse to run unless the call includes an explicit confirmation.

Questions

Something else? Check the docs or email support.

MCP (Model Context Protocol) is the standard way AI assistants call outside tools. RankLens is an MCP server, so once it's connected your assistant can pull your Search Console and GA4 data, run audits and compute insights while it answers you, instead of guessing or asking you to paste exports.

Any client that supports remote MCP servers over HTTP. That includes Claude (web, desktop and Claude Code), ChatGPT with connectors, Cursor, Windsurf, Zed, Codex CLI and Gemini CLI. The docs have setup steps for each one.

No. You sign in with Google on our site, choose which properties to expose, and paste one URL into your AI client. There's nothing to run on your machine and no OAuth credentials to set up.

Not by default. We ask Google for read-only access. Tools that submit or delete sitemaps and properties are opt-in, need a write scope you grant separately, and only run when the call includes an explicit confirmation.

Each time your assistant runs one RankLens tool, that's one call. A typical question uses two to five calls. The Free plan includes 100 calls a month, and you can see usage by day and by tool in the dashboard.

Those are a good choice if you want to self-host. RankLens runs the server for you, works in web clients like Claude.ai and ChatGPT, and adds GA4, computed insights, technical checks, reports, an algorithm update timeline, alerts and a dashboard on top of the raw Search Console tools.

No. RankLens doesn't train models, and we don't sell or share your Google data. Your AI client receives the results of the tools it calls; how that client handles conversations is set by its own provider and your settings there.

Yes. Any property your Google account can access in Search Console can be connected. Pro supports two Google accounts and Max supports five, so agencies can keep client logins separate.

This is the whole install.

Create a free account, then paste this URL into your AI client. Your first question takes about five minutes.

https://api.ranklens.app/mcp