Keywords Everywhere review

Keywords Everywhere is a browser extension paired with an API and an MCP server. It is not a self-hosted analytics stack or a keyword-research library that you add to an application. The extension runs in Chrome, Firefox or Edge and overlays marketing data while you browse. The API and MCP surfaces provide access to live keyword data for other tools.

For an SEO or marketing workflow, it sits between search and social sites and the person or AI assistant researching them. Free features include traffic and backlink metrics, social engagement metrics and prompt templates. Paid credits unlock search volume, CPC and competition across 15+ sites, plus historical trend charts, bulk keyword uploads and competitor gap analysis. The product also covers competitor keywords, ranking pages and backlink data. This makes it useful as a research layer for people, but teams building a data pipeline should evaluate the API separately: the browser extension's convenience does not establish that the API fits automated workloads.

The named integration surfaces are the browser extension, an API key and an MCP server. The homepage says to add a free API key to purchase a plan and access paid metrics. For AI workflows, the MCP server connects to ChatGPT, Claude, Cursor and VS Code, where an assistant can pull live keyword data. Prompt templates are available in ChatGPT, Claude, Gemini and DeepSeek; those templates are separate from the live-data MCP connection.

The extension installs in Chrome, Firefox and Edge, and the vendor says free browser features work without an API key. The homepage does not name an API protocol, SDKs, programming languages, CLI or webhook integration. Confirm API methods, authentication details, SDK support and usage accounting in the vendor's API and MCP docs before choosing a client or building an automated workflow. The homepage lists integrations spanning Google Search, Search Console, Analytics, YouTube, Amazon, eBay and Etsy, among others; that breadth describes marketing surfaces, not necessarily API endpoints.

The Free plan costs $0 and includes browser features, prompt templates and social metrics, but it has zero keyword search-volume credits. Paid plans are annual: Bronze costs $7 per month-equivalent for 100,000 credits per year and one seat; Silver is $14 for 400,000 credits and three seats; Gold is $40 for 2,000,000 credits and 10 seats; Platinum is $120 for 8,000,000 credits and 20 seats. The plans also raise the limits for top keywords and backlinks per website. The vendor says paid plans can be cancelled anytime; standalone monthly pricing is not published.

The vendor says paid data includes search volume, CPC and competition, and the pricing page lists no add-ons. A fixed cost per API request or credit-to-query conversion is not published, so estimate usage before relying on annual credits. Reddit users report that one search can consume dozens of credits, and some say one page can use hundreds depending on what loads. Treat that as a warning to check settings and monitor balances, not as a guaranteed rate.

The vendor does not publish an open-source license or a self-hosting option. Treat Keywords Everywhere as a proprietary service unless the vendor confirms otherwise; the browser extension, API and MCP server are the integration surfaces it names. That means teams should not plan on running its data service inside their own infrastructure.

The vendor does not publish a data-export path on its homepage. Before adopting it for a recurring workflow, ask what query history, saved research and account data can be exported, and in what format. Migration risk depends on how much your process relies on the extension or API: keyword research can move to another provider, but data access and any saved workflow may need rebuilding. Keep your own query records and avoid making vendor-specific outputs the only copy of research needed by other systems.

Before depending on the API, confirm its rate limits, availability commitments, authentication requirements and credit accounting with the vendor. The homepage does not give production limits or reliability commitments. It says paid plans include annual credits, but does not publish a request-to-credit rate. That makes capacity planning harder for automated jobs than for occasional manual research.

Credit consumption is the clearest operational concern in Reddit discussions. Users report that a search may count the typed keyword and related suggestions, or load data across multiple services if the extension stays enabled. Other commenters say their usage was much lower, so actual consumption appears workflow-dependent. Configure the extension to load data only when needed, if that setting is available in your workflow, and monitor credits before scaling usage. The homepage does not describe security controls, data retention or compliance terms; review the vendor's terms and ask how API and browsing data are handled before sending sensitive queries.