For SEO teams, agencies & consultants
GeoRanker SEO & SERP MCP is a Beta connector for AI agents and SEO teams to research localized search results, rankings, keyword demand, backlinks and page health through GeoRanker tools.
Recorded with SEO MCP
A fixed snapshot. Rankings can change.
The response returned 20 Google organic results for “car insurance”. Here are the first five, in the order returned, with the remaining results available below.
Your website. Your market.
Build a prompt to check where your website ranks for the keywords and market you choose. Copy the prompt into your connected assistant to run a one-time check, with no recurring schedule.
Add your details to create a prompt. You can review it before running anything in your assistant.
Made for your everyday work
From keyword research to page improvements, bring the evidence for your next SEO decision into one conversation. Start with a search, or use your own public domain for website reports.
Research keywords across Google, Bing or Yahoo, with ranking positions, titles and source links. Choose the location and language, then ask your assistant to compare competing pages or build a content brief.
Show the top 20 Google organic results for car insurance in Bucharest, Romania. Return ranking positions, titles, source URLs and available freshness information.Request up to 100 organic results. Actual coverage depends on the search.
Check where your domain appears across the keywords, locations and search engines you choose. Compare the returned positions and see which markets need a closer look.
Up to 200 keywords, 50 locations and 10 engines, checking the top 1–100 positions. Each keyword is checked in every requested location and engine, subject to your allowance.
Review a public page on mobile, desktop or both with a Lighthouse / PageSpeed Insights summary. Bring category scores, audit findings, explanations and metrics into a conversation about what to improve.
Analyze https://example.com/ on mobile and desktop. Summarize the Lighthouse scores and findings, explain the main issues, and help me prioritize the next improvements.One page per report. Includes a Lighthouse summary; screenshots and detailed audit/resource tables are not included.
Find broken internal links with a bounded public-site crawl or a single-page check. Set the crawl depth and page limit, then ask your assistant to organize the returned issues into a repair list.
Check the public website I provide for broken internal links using site scope, up to 2 levels deep and at most 20 pages. Ask for the URL if missing. List the returned broken links and referring pages, and show actual coverage and completion state. Do not check external links.Choose site or page scope, depth 1–10 and up to 1,000 requested pages, subject to allowance and provider capacity. Defaults are depth 2 and 20 pages. Path-restricted crawling is not supported; external-link checking is disabled.
Explore links to a domain or URL, referring websites, anchor text, historical changes and competitors. Choose the report that answers your question, with all eight options illustrated below.
Create a backlink summary for example.com. Explain the returned metrics and coverage, then help me identify what to investigate next.Use the metrics and coverage returned by the selected report. Historical views here describe backlinks.
Compare search volumes for your keyword ideas, with an optional target location. Use returned monthly trends and cost-per-click data, when available, to put demand into context.
Compare search volumes for car insurance and travel insurance in Romania. Include monthly trends and cost per click where returned, keeping the original dates, locations and units. Flag missing data.Research up to 200 keywords, subject to your allowance. Missing values are not zero; a currency is shown only when the source supplies it.
Go deeper into backlinks
Explore all eight backlink report types for a public domain or URL. Each prompt asks for a different view of the available data.
Start with the profile's reported metrics.
Give me a backlink summary for example.com and explain the available metrics.Inspect the links pointing to your target.
Show the backlinks report for example.com and organize the returned links for review.See which websites link to your target.
Show the referring domains for example.com and summarize the websites represented.Explore the wording used in links to your site.
Show the anchor-text report for example.com and group the returned phrases into themes.Understand changes in the available historical data.
Show the backlink history for example.com. Describe the changes using the returned dates and coverage.Compare gains and losses over the reported periods.
Show the new and lost backlink time series for example.com. Compare gains and losses for the periods returned.Explore the competitors returned by the backlink report.
Create a backlink competitors report for example.com and compare the competitors using the metrics returned.Explore page-level backlink information for a domain.
Show the domain pages backlink report for example.com and highlight pages worth investigating using the available metrics.Report admission units depend on the requested work: keywords × locations × engines for rank checks, selected devices for on-page reports, ceil(maxPages / 100) for broken-link checks (one unit for up to 100 requested pages), one unit for a backlink report, and keyword count for volumes. These are admission weights, not provider credit prices. A schema-valid request can exceed the configured allowance. A create call can count even when it reuses completed data; retrieval has separate limits. Setup and tool discovery do not submit reports. Respect returned limits and retry instructions. Read the SEO report guide ↗
Requirements: Node.js 22.22.2+ on the 22 release line, 24.15.0+ on the 24 release line, or 26.0.0+; npm and Git. No GeoRanker signup or manually entered API key is required for the Beta trial.
Reviewed client 0.13.1 (2026-09-18). Install from GitHub source; the npm package is unpublished.
Run these commands in your terminal. Setup enrolls a local installation, saves its credentials and checks the hosted tools without running a data query.
git clone https://github.com/georanker/georanker-seo-mcp.git
cd georanker-seo-mcp
npm ci
npm run build
node dist/src/cli.js --setupRun this from the client folder above. Reconnect Codex, then use /mcp to check the connection.
codex mcp add georanker-seo -- node "$PWD/dist/src/cli.js"Reconnect your assistant, enable the GeoRanker connection if prompted, and try this:
Show the top 20 Google organic results for car insurance in Bucharest, Romania. Return ranking positions, titles, source URLs and available freshness information.The local stdio client connects to GeoRanker over HTTPS. It checks for verified client updates automatically; set GEORANKER_MCP_AUTO_UPDATE=0 in your host configuration to manage versions yourself. Read client privacy and data flow ↗
Keep your research moving
Set a rank-check schedule when you need one, return to an existing report, or choose when to request a fresh result.
Rank reports start as one-time checks. Where scheduling is available, ask for recurring checks every 1–365 days, change the interval or stop the schedule for a report you created.
Future scheduled runs can consume credits. The initial request allowance does not cap future spending. If a schedule change is unconfirmed, check the same report before making another change.
Schedule the rank-tracking report we just created to run every 7 days.Change that rank-tracking report to run every 14 days.Stop the recurring schedule for that rank-tracking report.Return to an existing rank, on-page, internal-link, backlink or keyword-volume report without creating it again. Your assistant can check whether it is ready and use the information available.
Use the same MCP installation that created the report. Pending or unknown completion is kept visible, even if some data is available.
Check the SEO report we just created. If it is ready, summarize the findings. If it is still running or its status is unclear, tell me what is available without starting another report.Completed reports can be reused for up to seven days by default. Ask for a fresh one-time report when you need to bypass that reuse, or retrieve the latest available data from an existing recurring report.
A recurring report refresh reads the existing report; it does not manually run a new rank check. Matching work that is still pending is reused to avoid duplicate requests.
Run a fresh one-time on-page report for https://example.com/ on mobile and desktop. Bypass the completed cached result and show the source's observation time when available.Retrieve the latest available data for my recurring rank report, keeping its current schedule. Tell me when the rankings were observed.For agent builders
Local MCP clients connect your agent to GeoRanker’s search and public-page tools. Check the contracts, data flow and result limits before building your workflow.
Public Beta · Client 0.13.1 reviewed . Documentation links below preserve the reviewed source version.
GeoRanker SEO & SERP MCP is a Beta connector for AI agents and SEO teams to research localized search results, rankings, keyword demand, backlinks and page health through GeoRanker tools.
search_serpsget_serp_resultcreate_rank_tracking_reportget_rank_tracking_reportupdate_rank_tracking_schedulecreate_onpage_reportget_onpage_reportcreate_broken_links_reportget_broken_links_reportcreate_backlinks_reportget_backlinks_reportcreate_keyword_volume_reportget_keyword_volume_reportGeoRanker SEO & SERP MCP provides search_serps for a query, region and search engine. For example, query car insurance with region Bucharest,Romania, searchEngine google and pages 2 requests up to 20 organic results. Requested depth is capped at 100 organic results; returned coverage can be lower. Results include available ranking positions and source URLs. Multi-keyword domain checks use create_rank_tracking_report instead.
Reviewed first-party documentationThe documented integration is a local stdio MCP client launched by your assistant. That client connects over HTTPS to GeoRanker's hosted service. Use a host that can launch local Node.js processes and follow its configuration guide. A cloud-only connector needs a separately supported remote authentication flow; entering a hosted endpoint URL alone is not the documented installation path.
Reviewed first-party documentationThe client enrolls automatically and stores an installation credential and signing identity locally. You do not enter a reusable provider API key or create a GeoRanker account for the Beta trial. The two clients share installation state for the same service origin. This enrollment is not OAuth. The setup check verifies enrollment and tool contracts without submitting a data query; subsequent tool calls use the configured allowance.
Reviewed first-party documentationPass forceLive: true to bypass eligible completed MCP cache reuse, which defaults to seven days and is configurable. Matching pending or uncertain work keeps its existing ID. This does not bypass the upstream provider's processing rules or create a background refresh schedule. Preserve cached, cachedAt and generatedAt when supplied; cache storage time is not observation time.
Reviewed first-party documentationIndependent tasks may run in parallel within shared and per-installation service limits. For pending SERPs, retain jobId and call get_serp_result; for pending web pages, call get_fetch_result with the same jobId. SEO report families use their own reportId and matching get tool. Retrieval does not create a new data job. Follow returned nextAction and retry information, preserve pending, unknown and failed states, and avoid duplicate creation. Cancelling or timing out a call does not prove that submitted work stopped.
Reviewed first-party documentationReport admission units depend on the requested work: keywords × locations × engines for rank checks, selected devices for on-page reports, ceil(maxPages / 100) for broken-link checks (one unit for up to 100 requested pages), one unit for a backlink report, and keyword count for volumes. These are admission weights, not provider credit prices. A schema-valid request can exceed the configured allowance. A create call can count even when it reuses completed data; retrieval has separate limits. Setup and tool discovery do not submit reports. Respect returned limits and retry instructions. For example, three keywords in two locations on one engine require six rank-report admission units. A broken-link request for 20 or 100 pages requires one unit; 1,000 requested pages require ten. None of these values establishes a monetary price or a fixed free quota.
Reviewed first-party documentationNo. The current SEO report contract supports site scope or a single-page check. Path scope is rejected before submission. Site crawls accept depth 1–10 and up to 1,000 requested pages, subject to allowance and provider capacity; defaults are depth 2 and 20 pages. External-link checking is disabled. Report the actual returned internal checks and completion state, rather than claiming complete site coverage.
Reviewed first-party documentationRetain the report ID and inspect returned validation diagnostics or nextAction. Correct a confirmed rejected input instead of recreating unresolved work. REMOTE_SCHEMA_MISMATCH requires compatible client and hosted contracts before new work. After SCHEDULE_UNCERTAIN, retrieve the same rank report to reconcile the schedule; do not repeat or reverse the change blindly. Unknown completion and HTTP success alone do not establish a completed report.
Reviewed first-party documentationThe client sends requested search arguments or the public URL, an installation identifier, a revocable token and a persisted device signal to GeoRanker over HTTPS. GeoRanker uses its upstream infrastructure to process the request. Local identity and credentials normally live under ~/.config/georanker-search-mcp/client/; GEORANKER_STATE_DIR can change that location. Keep this state private. Shared result caching follows service isolation rules, so avoid secret URLs or sensitive content. Removing the host configuration does not revoke the installation or erase its saved credentials.
Reviewed first-party documentationThe public clients reviewed on 2026-09-18 are version 0.13.1; the website presents both products as Beta. The launcher checks for verified GitHub release packages at startup and every five minutes. It verifies release provenance and installs locked production dependencies without lifecycle scripts. Compatible worker updates apply during an idle period; calls are not replayed. Set GEORANKER_MCP_AUTO_UPDATE=0 in the host environment to review and manage releases yourself. Update downloads contact GitHub, npm and signature-verification services; the client privacy guide explains this data flow.
Reviewed first-party documentationThe reviewed release uses a GitHub source installation: clone, install dependencies, build, run the setup check and configure your host. Its npm packages are unpublished, so an npx command is not available for this release. Requirements are Node.js 22.22.2+ on the 22 release line, 24.15.0+ on the 24 release line, or 26.0.0+; npm and Git. Public source availability does not imply an open-source license; the packages are marked UNLICENSED. Repository metadata is not an official MCP Registry submission.
Reviewed first-party documentationGeoRanker MCP is in Beta. Request more free Beta credits through the website chat powered by Tidio, or use the contact page. Tell the team which MCP you use, what you are building and the workload you need. Our team reviews your request and confirms the allowance. The hosted service controls shared and per-installation allowances and concurrency, so follow returned limit and retry information. API calculator estimates do not define MCP Beta allowances or report admission units.
MCP Beta credit policyBetter together
Read JavaScript-powered pages, access supported Cloudflare-protected sources, and turn website content into useful research. Install both MCPs in the same assistant.