Ext Ops Panel
Open dashboard
Comparison

geo-generative-engine-optimisation vs RankControl

geo-generative-engine-optimisation is a plugin bundle for AI coding tools published by arturseo-geo. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). RankControl is an MCP server published by rankcontrol. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacegeo-generative-engine-optimisationRankControl
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.19.0
Downloads/month (npm): 2 049
Downloads/week (npm): 375
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

geo-generative-engine-optimisation vs RankControl
Factgeo-generative-engine-optimisationRankControl
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)5 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleRemote server (api.rctrl.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)17Not a bundle
LicenceMITMIT
Repository (differs)github.com/arturseo-geo/cowork-geo-plugingithub.com/rankcontrol/rankcontrol
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 405

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

geo-generative-engine-optimisation

In its own words, on Claude Code: claude-plugins-community:

Monitor AI citations, score content for AI search visibility, validate crawl parity, and optimise structured data for ChatGPT, Perplexity, and Google AI Overviews. The only plugin in the directory dedicated to Generative Engine Optimisation (GEO) — the emerging discipline of making content visible to AI search engines. Includes 6 skills: geo-score, citation-check, crawl-parity, schema-optimization, ai-content-strategy, and llms-txt.

RankControl

In its own words, on Official MCP Registry:

Plan, write and publish SEO articles on your own site, and track your Google and AI search traffic.

How to run each

geo-generative-engine-optimisation As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install geo-generative-engine-optimisation@claude-community

RankControl As a remote MCP server

Claude Code
claude mcp add --transport http rankcontrol https://api.rctrl.com/mcp

Requires: RANKCONTROL_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only RankControl has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of geo-generative-engine-optimisation publish no settings it asks for, so we do not compare settings.

What it can do: geo-generative-engine-optimisation · What it can do: RankControl · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built