SEO intelligence · Review overdue

OpenSEO

A fit for small teams that want keyword, backlink, site-audit, GSC, and agent workflows in a controllable interface. Do not treat it as a complete Ahrefs or Semrush replacement with its own index, zero external data cost, or production SEO data that can be exposed to agents without review.

Reviewed 2026-09-17Review due 2026-10-17GitHub ↗

Adoption statusReview overdueBased on the evidence below

LicenseMITCheck per-directory terms

Repository snapshotActive at review★ 12,679 · Fork 1,450 · 2026-08-20
Last push 2026-09-12

Better fit

Small teams willing to self-host and manage SEO data cost by API usage
Technical marketing teams connecting Search Console and SEO data to MCP or agent skills
Users who want source inspection, deployment control, and ownership of the data workflow

Think twice

Teams requiring a vendor-owned global keyword and backlink index, enterprise SLA, or complete managed support
Users unwilling to manage DataForSEO balance, OAuth, databases, secrets, and Cloudflare or Docker operations

Adoption and exit evidence

A repository is a dependency decision, not only a download.

Compatibility

The official repository documents Docker self-hosting for personal use and Cloudflare deployment for multi-device or team access, plus MCP and agent skills for compatible clients such as Claude Code, OpenClaw, and Hermes. Client, GSC, and data-provider configuration still require individual validation.

Installation

Pilot with the official local Docker path first; use the Cloudflare path only when multi-device or team access is required. Both paths require documented environment configuration, and SEO data requires a DataForSEO API key.

Removal

After removing containers or Cloudflare resources, revoke Google OAuth and GSC access, rotate or delete DataForSEO and model API keys, export or delete the database, and remove MCP and skill configuration from agent clients.

Permissions

Relevant permissions may include GSC OAuth data, the billable DataForSEO API, a database, deployment secrets, and SEO tools callable by MCP clients. Internet-facing Cloudflare deployments need a separate access-control review; open source alone is not authentication.

Maintenance

The official repository was rechecked on September 17, 2026. The latest release was v0.1.8 on September 12, adding keyword case preservation, searchable Google Analytics and Search Console properties, and SAM reply controls while fixing audit rate-limit handling. Stars and forks remain explicitly dated to the August 20 snapshot rather than being presented as current stability evidence.

License boundary

The main repository code is MIT. That license does not cover DataForSEO data, Google services, model APIs, hosted subscriptions, or other third-party terms. Self-hosting does not remove their cost or compliance requirements.

Primary risk

What can go wrong after installation?

The easiest things to underestimate are total cost and permission surface: free code does not make SEO data free, and agent access to SEO and GSC data does not justify write, secret, or cross-team access. For internet-facing deployments, OAuth, secret, and access-control errors matter more than star count.

Evidence status

The Product Hunt launch record, official README, self-hosting and cost disclosure, MIT license, and public GitHub metadata were reviewed. ToolPickly has not connected a real GSC property, purchased DataForSEO usage, or completed an end-to-end Docker and Cloudflare sandbox test.

Choose the deployment model before comparing features

The code license is only one cost line. Data, access control, maintenance, and exit work change by deployment.

Hosted · fastest validation

The official README lists a $10/month hosted subscription and says hosted requests include a 28% markup over DataForSEO. Use it to test workflow fit before accepting infrastructure work.

Docker · local pilot

Runs on localhost with local_noauth. Keep port 3001 bound to localhost; do not expose it publicly without a separate authentication boundary. Budget DataForSEO and optional OpenRouter usage.

Cloudflare · shared workspace

The current guide provisions Workers, D1, KV, R2, and Cloudflare Access. R2 activation requires a payment method even within the free tier; updates and teardown remain the operator's job.

Decision boundary

Choose Search Console for first-party demand, OpenSEO for a controllable API-backed workspace, and Semrush when a mature hosted database and team workflow justify subscription cost.

Compare the Semrush workflow →Score all three paths →Model recurring cost →

Run this controlled pilot

Do not use production credentials or sensitive customer data.

01
Use local Docker with a fresh test database and a separate low-balance DataForSEO key
02
Authorize one non-critical GSC property and record OAuth scopes and network requests
03
Record API cost and results for 20 fixed keywords, one audit, and one competitor query
04
Limit exposed tools before connecting one agent, then revoke access, delete keys, and verify data removal

Open the complete adoption checklist →

Alternatives by decision

Google Search Console

Start here for free first-party query and page data; it does not provide complete competitor and backlink research.

Semrush

Better for teams needing a mature hosted data platform, broad databases, and team workflows and willing to pay subscription pricing.

Writesonic

Better when content production and GEO workflows matter more than maintaining an SEO data stack.

Official sources and disclosure

Stars are a dated attention signal. They do not determine the verdict. ToolPickly reviewed public repository documentation and clearly identifies what has not been sandbox-tested.

Report a project change or correction →