A useful answer starts here

Choose your MCP.
Set up GeoRanker MCP.

SEO research or website content. Pick your MCP and your AI assistant.

No GeoRanker signup for the trialNo API key to configureInstall one or both
YOUR CHOICESEO & SERP MCP

Requirements: Node.js 22.22.2+ on the 22 release line, 24.15.0+ on the 24 release line, or 26.0.0+; npm (including npx). No GeoRanker signup or manually entered API key is required for the Beta trial.

Reviewed client 0.15.1 (2026-10-08). Install from npm ↗. Git and a TypeScript build are not required.

01

Install SEO MCP.

Run this command in your terminal. Setup enrolls a local installation, saves its credentials and checks the hosted tools without running a data query.

SEO MCP · client installation
npx --yes @georanker/[email protected] --setup

02

Add it to Codex.

Reconnect Codex, then use /mcp to check the connection.

Codex · SEO MCP configuration
codex mcp add georanker-seo -- npx --yes @georanker/[email protected]

If your host cannot find npx, use its absolute executable path and follow the host’s platform-specific launch instructions. These configuration guides do not certify every host or operating system.

03

Ask your first question.

Reconnect your assistant, enable the GeoRanker connection if prompted, and try this:

Copy your first prompt
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. The npm version pins the bootstrap package. Signed automatic updates can still select a newer worker; set GEORANKER_MCP_AUTO_UPDATE=0 in your host configuration to keep the selected version and manage future updates yourself. Read client privacy and data flow ↗

The local client is MIT-licensed ↗. Hosted GeoRanker service terms and allowances are separate.

Install from GitHub source (fallback)

This route also requires Git. Build the reviewed source and run its setup check:

SEO MCP · source installation
git clone https://github.com/georanker/georanker-seo-mcp.git
cd georanker-seo-mcp
git checkout b908fc01f17f6638dc722147bef0ea1c75077199
npm ci
npm run build
node dist/src/cli.js --setup

In your host configuration, replace npx and its package arguments with node and the absolute path to georanker-seo-mcp/dist/src/cli.js. When switching between source and npm, preserve your state directory, service origin and environment settings so the client reuses your existing installation credentials.

A little help along the way

Ready for your
first question.

Setup enrolls the selected client automatically. Add it to your host and reconnect to enable its tools.

Can I install both MCPs? +

Yes. Install each client separately and add its entry to your assistant. Keep your existing MCP entries. Choose SEO MCP for search research and Web Scraping MCP for reading selected public pages.

My assistant cannot find Node.js +

Use a supported Node.js release: 22.22.2+ on the 22 release line, 24.15.0+ on the 24 release line, or 26.0.0+. Restart your assistant after installation. Ensure npm and npx are available too. Some desktop apps need the full path to the npx executable in their configuration; follow the host’s platform-specific launch instructions. Source installations use the Node executable instead.

The GeoRanker connection does not appear +

Check the selected assistant’s configuration location, use the matching npm package and version, and reconnect. For source installations, use the actual absolute client path. Enable the GeoRanker connection when your assistant prompts you.

My research request is still running +

Ask your assistant to continue the existing request. It can use the returned reference to pick up the result without starting the same work again.

I need more capacity +

MCP is in beta. If you need more free credits, contact our team through Tidio chat or the contact page. Respect the current allowance and retry information while your request is reviewed.

Request free beta credits ↗