io.github.AntonioBlagoPublished by GitHub account AntonioBlagov0.1.0Updated Oct 26, 2026
Remote SEO/GEO MCP: Search Console, keyword research, backlinks, competitor & on-page audits.
Remote SEO/GEO MCP server that gives an assistant keyword classification, SEO checklists and guidance, URL audits, and, with a key, Search Console and…
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.AntonioBlago%2Fvisibly-ai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"visibly-ai-seo": {
"type": "http",
"url": "https://mcp.visibly-ai.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}A batteries-included Claude Code blueprint for SEO freelancers and agencies. Wire up the Visibly AI MCP, get ready-made slash commands for the full client workflow — Status-Quo → Potential Analysis → Offer → CI-compliant PDF — and a smart hook that nudges Claude toward real SEO data instead of guessing.
Built and battle-tested by Antonio Blago — SEO Freelancer & creator of the Neuro-SEO System®.
Quickstart • What's inside • Workflows • CTR Model • Customise • Get a free key • Book a call
SEO consulting is the same five jobs over and over: pull the real ranking data, map it against the client's keyword set, quantify the opportunity, turn that into an offer, and ship a presentable PDF. Claude Code can do all of it — if you give it the data sources, the methodology, and the guardrails.
This repo packages exactly that — and it runs without any API key. Install it and the bundled .mcp.json connects to the Visibly AI MCP keyless, giving you the free knowledge tools (keyword classification, SEO checklists, Google guidelines, URL-structure analysis) plus the full local methodology; bring your own Search Console export and the entire Status-Quo → Potential → Offer → PDF chain runs offline. Add a Visibly AI key when you want the data engine on tap — live GSC/GA at 0 credits, keywords, backlinks, competitors and on-page audits through one MCP. Free by default, pro when you need it.
There are two ways to use this — pick one.
You get the /visibly-seo-status-quo, /visibly-seo-potential, /visibly-seo-offer, /visibly-seo-pdf-build commands, the
auto-invoked SEO skills, the SEO-intent hook, and the keyless Visibly AI MCP — wired in.
No key needed to start — approve the MCP server and you have the free knowledge tools plus
the full local workflow.
Want the full data engine (live GSC, keywords, backlinks, on-page)? Add a Visibly AI key — grab one at visibly-ai.com (~30s, no card), then connect it once (resolves at write time, stays out of git):
Restart with /reload-plugins if needed. See docs/setup.md for the
pro tier, Google-OAuth (0 credits) and optional DataForSEO wiring.
Use the full repo (docs, PDF template, setup script) as a project scaffold.
curl -fsSL https://claude.ai/install.sh | bash (macOS, Linux, WSL) or irm https://claude.ai/install.ps1 | iex (Windows PowerShell). New to Claude Code? Start with claude-homebase: /homebase sets up your global CLAUDE.md and project structure, then pick the SEO path to land here.Skip this for the free tier — the keyless .mcp.json already works. To unlock the
full data engine, create a free account at visibly-ai.com,
copy your lc_... key, and connect it once (resolves at write time, stays out of git):
Full tier breakdown, Google-OAuth (live GSC/GA at 0 credits) and optional DataForSEO
wiring: docs/setup.md.
On first run, Claude Code will ask you to approve the Visibly AI MCP server. Approve it, then try:
That's it. On the free tier, feed a GSC export to the Python templates; with a key, data is pulled live. Either way you're running the full SEO workflow.
Each slash command corresponds to one phase of a real client engagement. They chain:
Full methodology is documented in docs/workflows.md.
The potential analysis is only as good as its click-through-rate curve. This repo ships the Keyword Study 2026 — CTR by position from first-party Google Search Console data (1.3M keywords, 94 domains) — instead of the inflated textbook numbers most templates still use.
The differentiator: the curve is intent-aware. A navigational keyword at position 1 earns ~8.9% CTR; an informational one ~3.2%. Forecasting with one blended number quietly mis-states the upside. See docs/ctr-model.md for the full intent-by-position table and the Python to apply it. Honest inputs → defensible forecasts → offers that survive scrutiny.
No surprises about data flow:
.mcp.json connects to mcp.visibly-ai.com without an account. Only the free knowledge tools respond (checklists, guidance, Google guidelines, keyword classification, URL-structure checks) — no client data involved.query_search_console, query_analytics, keywords, backlinks, on-page) route through the Visibly AI backend, hosted on Railway in the EU. Your GSC/GA data passes through that backend to reach Claude — that's the product, not a side effect. And it takes three explicit opt-ins before a single GSC row can flow: create a Visibly account, add your API key, and connect your Google account via OAuth inside Visibly. Without the Google consent, query_search_console has no property to read. Not acceptable for a client? Don't add the key: feed a GSC export to the local Python templates instead — the full workflow still runs..claude/settings.json auto-allows only metadata and the free knowledge tools. Every tool that reads client data (GSC, GA, keywords, backlinks, on-page, crawling) sits in ask — Claude prompts before using it..claude/hooks/seo-check.sh) runs locally, sends nothing anywhere, and only injects a reminder to use real data instead of guessing when your prompt looks SEO-related. Don't want the nudge? Delete the hook.Everything is plain Markdown and shell — fork and adapt:
CLAUDE.md and templates/pdf_example.py with your colours, fonts, contact block..mcp.json. See docs/setup.md. Free walkthrough for building your own GSC access from scratch: Indexing Checker für die Google Search Console (German)..claude/commands/*.md files are the workflows. Rewrite them in your own words..claude/hooks/seo-check.sh with your own keyword triggers.See docs/setup.md for a deeper walkthrough and docs/best-practices.md for the hard-won lessons.
More on the method: best Claude Code skills for developers.
PRs welcome — see CONTRIBUTING.md. Found this useful? A ⭐ helps others find it.
MIT — see LICENSE. Use it commercially, fork it, ship it for your own clients.
If you'd rather have this dialled in to your agency's workflow — or want to talk SEO, Claude Code, or vibe coding — book a consultation.
Created by Antonio Blago — SEO Freelancer & Neuro-SEO System®
📅 Book a consultation
If this saves you an afternoon per client, it did its job.
Source: README.md at commit 82bb028
Classify keywords locally by intent, funnel stage, brand type, and topic. Free and available without an API key.
keywordsrequiredbrand_namecompetitorsbrand_variationsproduct_keywordsGet an SEO checklist. Types: general, blog, ecommerce, discover, backlink, all. Available in English and German. Free - no API key required.
languagechecklist_typeGet SEO best practices on a topic. Topics: title_tags, meta_descriptions, heading_structure, internal_linking, core_web_vitals, eeat, keyword_research, schema_markup, image_optimization, local_seo. Use topic='list' for all. Free - no API key required.
topicrequiredAnalyze a URL for SEO-friendliness. Checks length, structure, and common issues. Free - no API key required.
urlrequiredList available countries/locations for SEO data queries. Free - no API key required.
Takes no parameters.
Get an SEO workflow skill with step-by-step methodology, triggers, credits, and quality gates from the current seo_skills catalog. Use name='content-nss-optimize' to write with your own model and improve an article toward measured NSS 70/80 using free Visibly scoring, then save it and show the editor link. Use name='list' for all available skills. Free - no API key required.
namerequiredGet official Google Search developer guidelines by category. Free.
category100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
com.kitchenwattOfficial publisher
Lets an assistant search, filter and compare food processors in KitchenWatt's catalogue, with links to each model's page for prices and reviews.
com.heavenpcOfficial publisher
Searches, filters and compares server racks in HeavenPC's online comparison catalogue, returning specs and links to each model's page.
/plugin marketplace add AntonioBlago/claude-code-seo-starter/plugin install seo-starter@antonioblagoclaude mcp add --transport http visiblyai https://mcp.visibly-ai.com/mcp --header "Authorization: Bearer lc_xxxxxxxxxxxxxxxx"# Use it as a GitHub template, or just clone:git clone https://github.com/AntonioBlago/claude-code-seo-starter.gitcd claude-code-seo-starterclaude mcp add --transport http visiblyai https://mcp.visibly-ai.com/mcp --header "Authorization: Bearer lc_xxxxxxxxxxxxxxxx"claude/visibly-seo-status-quo example.com/visibly-seo-status-quo <domain> → /visibly-seo-potential <domain> → /visibly-seo-offer <domain> → /visibly-seo-pdf-build <script.py> (where do we (what's the upside, (what should the (hand the client a rank today?) in clicks & €?) client buy?) polished PDF)claude-code-seo-starter/├── .claude-plugin/ # makes this repo an installable plugin + marketplace│ ├── plugin.json # plugin manifest│ └── marketplace.json # marketplace catalog (one repo = both)├── .mcp.json # Visibly AI MCP connection — keyless (free tools); add key for pro├── server.json # MCP-registry manifest (publish via mcp-publisher)├── .env.example # copy → .env — optional key + separate data sources├── CLAUDE.md # project instructions Claude reads on every run├── .claude/│ ├── commands/ # /visibly-seo-status-quo /visibly-seo-potential /visibly-seo-offer /visibly-seo-pdf-build│ ├── skills/ # auto-invoked SEO skills (status-quo, potential, offer, pdf)│ ├── hooks/ # seo-check.sh + hooks.json — SEO-intent nudge│ └── settings.json # hook registration + permissions (free tools allowed, data tools ask)├── docs/│ ├── setup.md # detailed setup│ ├── workflows.md # the 4-phase methodology│ ├── ctr-model.md # empirical CTR curve│ ├── folder-structure.md # client knowledge base + CI base conventions│ ├── best-practices.md # lessons learned│ └── promote.md # discoverability checklist (registry, awesome lists)├── templates/│ ├── ci/ # CI base — brand.py (constants) + CI.md (reference)│ ├── client-template/ # copy → clients/<domain>/ (CLAUDE.md + _knowledge/)│ ├── status-quo-template.md # fill-in status-quo skeleton (classification, quick wins)│ ├── potential-template.md # fill-in potential skeleton (deltas, clusters, ROI scenarios)│ ├── offer-template.md # fill-in offer skeleton (phases, pricing, ROI, terms, CTA)│ └── pdf_example.py # minimal CI-PDF starter (fpdf2)└── scripts/ └── check-setup.sh # verify your env is wired correctly