RRepoGEO

REPOGEO REPORT · LITE

clidey/whodb

Default branch main · commit 4a401d37 · scanned 5/16/2026, 7:46:20 AM

GitHub: 4,823 stars · 207 forks

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface clidey/whodb, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition README H2 to explicitly state core function and supported databases

    Why:

    CURRENT
    ### *Lightweight, Fast, and Beautiful Database Management*
    COPY-PASTE FIX
    ### *A Lightweight, Next-Gen Data Explorer and Database Client for Postgres, MySQL, SQLite, MongoDB, Redis, MariaDB, Elastic Search, and Clickhouse, with a Powerful AI Chat Interface.*
  • mediumabout#2
    Strengthen the 'About' description to emphasize its category and AI features

    Why:

    CURRENT
    A lightweight next-gen data explorer - Postgres, MySQL, SQLite, MongoDB, Redis, MariaDB, Elastic Search, and Clickhouse with Chat interface
    COPY-PASTE FIX
    WhoDB is a lightweight, next-gen data explorer and database client for Postgres, MySQL, SQLite, MongoDB, Redis, MariaDB, Elastic Search, and Clickhouse, featuring an intuitive UI and a powerful AI Chat interface for data exploration and management.
  • lowcomparison#3
    Add a 'Comparison' section to the README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, e.g., "## WhoDB vs. The Competition", that explicitly compares WhoDB to popular database clients like DBeaver, TablePlus, or DataGrip, highlighting its lightweight nature, speed, modern UI, and unique AI chat capabilities.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface clidey/whodb
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
dbeaver/dbeaver
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. dbeaver/dbeaver · recommended 1×
  2. DataGrip · recommended 1×
  3. microsoft/azuredatastudio · recommended 1×
  4. TablePlus · recommended 1×
  5. beekeeper-studio/beekeeper-studio · recommended 1×
  • CATEGORY QUERY
    What is a lightweight, modern database management tool supporting multiple SQL and NoSQL databases?
    you: not recommended
    AI recommended (in order):
    1. DBeaver Community Edition (dbeaver/dbeaver)
    2. DataGrip
    3. Azure Data Studio (microsoft/azuredatastudio)
    4. TablePlus
    5. Beekeeper Studio (beekeeper-studio/beekeeper-studio)
    6. OmniDB (OmniDB/OmniDB)

    AI recommended 6 alternatives but never named clidey/whodb. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Recommend a database client with AI chat for exploring data across different database types.
    you: not recommended
    AI recommended (in order):
    1. DataChat
    2. Seek AI
    3. ThoughtSpot
    4. PopSQL
    5. Dremio
    6. Tableau

    AI recommended 6 alternatives but never named clidey/whodb. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of clidey/whodb?
    pass
    AI named clidey/whodb explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts clidey/whodb in production, what risks or prerequisites should they evaluate first?
    pass
    AI named clidey/whodb explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo clidey/whodb solve, and who is the primary audience?
    pass
    AI named clidey/whodb explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of clidey/whodb. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/clidey/whodb.svg)](https://repogeo.com/en/r/clidey/whodb)
HTML
<a href="https://repogeo.com/en/r/clidey/whodb"><img src="https://repogeo.com/badge/clidey/whodb.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

clidey/whodb — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite