Open SEO MCP Skills ↗
Open SEO MCP Skills · Claude-based SEO/GEO workflows using connected first-party search and analytics data
← All toolsAnother direction / 01 Another direction / 02 Another direction / 03
The selection guideSource-backed research ↗
AI Search Monitoring / Open-source AI visibility workbench with hosted diagnosis and human-testing services.
NiubiGEO
Open-source AI visibility diagnosis, monitoring, and human testing
AI visibility diagnosisEvidence-preserving GEO workbenchOpen-source AI search monitoring
Why it stands out
Evidence-oriented reporting rather than an opaque score alone.
Source review: · Public-source research, not a hands-on test
The open-source workbench and the hosted diagnosis, human-testing, publishing, and distribution services are separate boundaries; model, search, infrastructure, and operational costs remain relevant.
↗ Best for
Technical SEOs, GEO researchers, and developers able to manage model credentials.
! Know before you buy
External commentary supports discussion of the evidence model and deployment, but no checked source provides a representative customer sample or controlled validation of GEO outcomes.
01 / Editorial assessment
Is NiubiGEO for you?
The AICiteKit take
NiubiGEO is a credible evidence-oriented option for teams that want to inspect the questions, model answers, citations, competitors, and test conditions behind an AI-visibility diagnosis. Its public repository and active release line make the workbench inspectable, while the official site bounds the entry report at ¥99 for up to three questions across three models. The tradeoff is that public evidence does not establish a representative customer-review sample, universal quotas, enterprise retention, or causal GEO outcomes. Shortlist it for a self-hosted or low-cost pilot; choose a mature monitoring vendor when you need a documented SLA, broad independent reviews, or a proven historical panel.
A good fit if you are…
- Technical SEOs, GEO researchers, and developers able to manage model credentials.
- Teams that need original answers, citations, competitors, and test conditions preserved.
- Early-stage products wanting a bounded ¥99 diagnosis before buying ongoing monitoring.
- Agencies able to define client prompts and record model, region, and date context.
Consider another option if…
- Non-technical buyers wanting a turnkey enterprise SaaS and SLA.
- Regulated teams requiring independently audited security, retention, or residency evidence.
- Buyers expecting the report to prove rankings, traffic, conversions, or revenue lift.
- Global programs needing established coverage across every model, language, and region.
02 / Scope, not promises
Features & coverage
- Named model coverage
The official site names ChatGPT, Claude, Gemini, and Perplexity; actual availability depends on provider configuration and model version.
Archived research · Official site and repository checked 2026-10-28.Research excerpt · Coverage limits- Open-source boundary
The public repository and Docker releases support an inspectable, self-hosted workbench; infrastructure, credentials, model/search usage, backups, and operations remain buyer responsibilities.
Archived research · Repository and releases checked 2026-10-28.Research excerpt · Open-source workbench and deployment- Independent evidence boundary
External commentary supports discussion of the evidence model and deployment, but no checked source provides a representative customer sample or controlled validation of GEO outcomes.
Archived research · External sources checked 2026-10-28.Research excerpt · What the evidence does not prove
Evidence-preserving diagnosis
The official workflow and external technical commentary describe preserving questions, model answers, citations, competitors, and test conditions. This supports inspectability, not answer accuracy or business impact.
Open-source workbench
The public repository and Docker releases make the workbench inspectable and deployable, while model keys, infrastructure, security, backups, and provider costs remain operational responsibilities.
Model and monitoring configuration
The site names ChatGPT, Claude, Gemini, and Perplexity; v0.3.0 adds keyword monitoring but labels it early access. Confirm actual providers, quotas, model versions, and regional behavior before scaling.
Human testing and execution services
The site separately offers human AI testing, publishing, product trials, and custom tasks. Public pages do not establish a bundled price, fixed participant sample, or white-label package.
A focused evaluation workflow
- Review the official scope and repository boundary.
- Define buyer questions, models, providers, region, and date.
- Run a bounded diagnosis or self-hosted workbench test.
- Preserve original answers, citations, competitors, and conditions.
- Separate recognition, discovery, recommendation, and citation observations.
- Re-test the same prompt set before claiming improvement.
03 / Commercial boundaries
Pricing & limits
Terms below reflect the 2026-10-28 source review, not a new live quote. Confirm currency, billing term, tax and required scope with the provider.
- Diagnosis price
Official site advertises a ¥99 AI diagnosis report.
Archived research · Public pricing checked 2026-10-28.Research excerpt · Pricing and limits- Diagnosis scope
Up to 3 buyer questions × 3 models, with original answers, available sources, and delivery within 1 business day, according to the official site.
Archived research · Official homepage checked 2026-10-28.Research excerpt · Quick facts
- Open-source boundary
The public repository and Docker releases support an inspectable, self-hosted workbench; infrastructure, credentials, model/search usage, backups, and operations remain buyer responsibilities.
Archived research · Repository and releases checked 2026-10-28.Research excerpt · Open-source workbench and deployment
Pricing context & qualifications
The official site advertises a ¥99 diagnosis report covering up to 3 questions × 3 models, while human testing is priced per test and publishing per site. Self-hosting has no hosted subscription price but requires infrastructure, model/search usage, credentials, backups, and maintenance. Confirm current terms before scaling.
04 / The tradeoffs
Strengths & weaknesses
Reasons to shortlist
- Evidence-oriented reporting rather than an opaque score alone.
- Public repository and active release history.
- Bounded public diagnosis price and explicit service separation.
- Clear distinction between recognition, discovery, recommendation, and citation evidence.
Reasons to pause
- Independent user evidence and controlled efficacy studies are sparse.
- Self-hosting transfers model, search, storage, security, and maintenance costs to the buyer.
- Keyword monitoring is described as early access and subject to change.
- Public pages do not establish universal quotas, retention, SLA, white-label, or residency terms.
External commentary supports discussion of the evidence model and deployment, but no checked source provides a representative customer sample or controlled validation of GEO outcomes.
05 / Choose by the job
Alternatives to consider
Editorial fit comparisons—not performance rankings or claims that one option always wins.
SE Visible ↗
SE Visible · recurring AI-search visibility monitoring
GetCito ↗
GetCito · open-source AEO/GEO optimization workflow
06 / What we can substantiate
Reviews & evidence
Public feedback is not yet a representative customer sample. GitHub stars, releases, external technical commentary, and a deployment guide provide existence, activity, methodological, and operational context, but they do not validate customer satisfaction, citation accuracy, or GEO outcomes.
AICiteKit assessment: public-source research, not a hands-on product test. Official materials establish stated scope; reviews are dated and may concern the broader platform. Neither establishes guaranteed citations, traffic or revenue.
Sources & original verification dates
| Source | Evidence type | Checked |
|---|---|---|
| NiubiGEO official homepage ↗ | Official product page | |
| NiubiGEO services and pricing ↗ | Official pricing page | |
| NiubiGEO GitHub repository ↗ | Official public repository | |
| NiubiGEO GitHub releases ↗ | Official release history | |
| The original answers and evidence behind the report ↗ | External technical commentary | |
| Knowing a brand when prompted versus discovering it unprompted ↗ | External GEO analysis | |
| From a product introduction to a step-by-step deployment guide ↗ | Independent deployment guide |
Original review evidence & date context
Preserved from the published research. Dates, review counts and product-scope qualifications below have not been refreshed by this layout migration.
Evidence snapshot
| Source | Public signal | What it supports | Confidence |
|---|---|---|---|
| Official homepage | Named models, report scope, evidence language, and services | Vendor-stated product workflow | High for stated behavior; not efficacy evidence |
| Official pricing | ¥99 diagnosis and separate human-testing/publishing boundaries | Current public pricing boundary | High for checked vendor page |
| GitHub repository and releases | Active public repository, releases, keyword monitoring, and security update | Existence, inspectability, and current implementation notes | High for repository facts; stars are not reviews |
| DEV Community analysis | External discussion of preserved answers, citations, and conditions | Methodological commentary | Medium; vendor-linked and not controlled evaluation |
| The GEO Community | External analysis of recognition, discovery, recommendation, and evidence | Methodological context | Medium; not a customer study |
| LumaDock | Third-party deployment guide | Practical self-hosting context | Medium for deployment; not product-quality evidence |
No checked source provides a representative customer-review sample or controlled validation of GEO outcomes.
Research notes & unresolved discrepancies
- Official homepage, pricing page, repository, and releases checked 2026-10-28.
- DEV Community and The GEO Community articles used as external commentary; LumaDock used for deployment context.
- No checked source proves rankings, traffic, conversions, revenue lift, complete model coverage, enterprise SLA, or security audit.
Layout migration: October 4, 2026. The original MDX research is retained in the repository; this reorganization does not refresh its factual verification dates.