new-term-radar
Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Open Source Ahrefs & SEMrush
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗OpenSEO (openseo.gg) is an open-source alternative to Ahrefs and Semrush. It covers full SEO audits of any domain, keyword research, rank tracking, backlinks, technical site audits, AI visibility and local rank tracking, and reads your own Google Search Console and Analytics data. Run it on your own machine or server, read every line of it, and hand it to your AI agent.
No monthly plan: the software is free, and search data is paid per lookup, under a monthly limit you set. A rank check is from $0.02, a keyword search of 150 ideas about $0.08.
⭐ If OpenSEO is useful to you, a star helps other people find it.
[!NOTE] OpenSEO is released and gets active updates. Issues and ideas are very welcome.
Every tool is one search: type a keyword, domain or URL, pick a country (and a city or state where it helps), press Enter, and everything loads together. The search is in the address, so any view can be bookmarked or shared. Each tool has its own page, and the guide goes through every screen.
Six tools run right on the website, a few free checks a day, no sign-up:
| Tool | What it checks |
|---|---|
| Keyword generator | 50 keyword ideas for a seed, with volume, difficulty and CPC |
| Keyword difficulty checker | Difficulty of up to 20 keywords |
| SERP checker | The live Google top 20 for a keyword |
| Website traffic checker | Estimated Google traffic of up to 5 sites |
| Website authority checker | Domain Rating, referring domains and backlinks of up to 3 sites |
| AI Overview checker | Whether Google shows an AI Overview, and which sites it cites |
dry_run and max_cost_usd, so an agent cannot spend more than you agreed.| Ahrefs, Semrush, SE Ranking, Moz | OpenSEO | |
|---|---|---|
| Source code | Closed | Open source (MIT) |
| Where it runs | Their cloud | openseo.gg, or your own server with Docker |
| Price | Monthly plans from $49 (Moz) to $140 (Semrush) to start | Free software; data paid per lookup |
| Seats | Paid per user | No seats |
| AI agents | API or MCP on some plans | 76 MCP tools and a REST API, spending capped per call |
| Data depth | Their own crawlers and indexes, the deepest | A large commercial dataset through a provider |
Honest side-by-sides, including when each one is the better buy: Ahrefs · Semrush · SE Ranking · Mangools · Ubersuggest · Moz · Screaming Frog · Otterly.AI
You need Docker. On Windows or macOS that's Docker Desktop with at least 4 GB of memory.
git clone https://github.com/duckduckdeploy/openseo.git openseo
cd openseo
cp .env.example .env
# In .env, set AUTH_SECRET (32+ random characters)
# and ENCRYPTION_KEY (openssl rand -base64 32)
docker compose up -d --build
| Service | Address |
|---|---|
| Dashboard | http://localhost:3200 |
| Site and docs | http://localhost:3101 |
| API and MCP | http://localhost:4100 (/api/*, /mcp) |
One image runs everything: Postgres, the API with its MCP server and background worker, the dashboard and the site. Database migrations run when the API starts.
On a cloud server with your own domain, add HTTPS with automatic Let's Encrypt certificates:
app. and api. at the server.OPENSEO_DOMAIN, APP_URL, WEB_URL, PUBLIC_API_URL and POSTGRES_PASSWORD in .env.docker compose --profile https up -d --build.The self-hosting guide covers servers, updates, backups and every setting.
The SEO MCP server gives agents the whole workspace as 76 tools, listed with their prices in MCP tools.
ChatGPT and Claude (web and desktop): add a custom connector with the URL {API_URL}/mcp and OAuth sign-in. You sign in with your OpenSEO account and approve; no key needed. Connected apps can be revoked in Settings.
For other agents, create an API key under Settings and store it in an environment variable named OPENSEO_API_KEY.
The quick way: copy the setup prompt from Settings and paste it into your agent. The agent connects itself and checks the connection with free calls only.
Claude Code: install the plugin, which bundles the connection and the skills:
/plugin install openseo --marketplace duckduckdeploy/openseo
Set OPENSEO_MCP_URL to point it at a self-hosted install.
Any other MCP client: add {API_URL}/mcp with the header Authorization: Bearer <key>. The MCP guide has the exact config for:
Ready-made SEO workflows in plugins/openseo/skills, built on the 76 MCP tools:
| Skill | What it does |
|---|---|
seo-coach | Learn SEO on your own site, and pick the first thing worth doing |
seo-audit | Any domain's rankings, links and competitors, as a short plan |
site-audit | Crawl your site: the one or two technical fixes that matter most |
keyword-research | Topics worth writing about, grouped and saved |
competitor-analysis | Their strategy, the keyword gap, and where you can win |
search-console-review | Quick wins from your own Google data, free |
local-seo | Your Maps profile, reviews and rankings street by street |
Every skill prices paid steps with dry_run first and passes the limit you agree as max_cost_usd. In Claude Code, /seo-audit example.com audits any domain in one call (the seo_audit tool, about $0.50 to $0.65) and turns it into a short plan. Or just ask, for example "which of my pages are stuck on page two?". The same features are available over the REST API.
The crawler, site audit and Google data are free. Keyword volumes, rankings, backlinks and other search data come from YepAPI. You add your own key when you set up your account, and each lookup is billed to it at the price the app shows first: a page-one rank check costs $0.01, and 150 keyword ideas cost about $0.08.
Requirements: Node 26+, pnpm 10, Postgres 15+ (or docker compose up -d postgres).
pnpm install
pnpm db:migrate
pnpm dev # API :4100, dashboard :3200, site :3101, with live reload
pnpm typecheck
pnpm test
The tests need no database, network or API keys. apps/api/test runs the real API against an in-memory Postgres (PGlite) with the real migrations, plus stand-ins for the data provider (apps/api/src/testing/fake-yepapi.ts) and Google (apps/api/src/testing/fake-google.ts). For local work without a data key, run the stand-in with pnpm --filter @openseo/api fake-yepapi and set YEPAPI_BASE_URL=http://localhost:4199.
apps/api Fastify API, MCP server, background worker (pg-boss)
apps/app Dashboard (Next.js)
apps/web Public site and docs (Next.js)
packages/yepapi Typed data client with price estimates
packages/crawler Site-audit crawler
packages/shared Model catalog and shared helpers
User documentation and tutorials live on the site under /docs (apps/web/src/app/docs).
ENCRYPTION_KEY) and never returned by the API.Clear issues are the most useful contribution: what you did, what you expected and what happened. For code, run pnpm typecheck and pnpm test before opening a pull request.
MIT. Use it, change it, host it.