RRepoGEO

REPOGEO REPORT · LITE

BloopAI/bloop

Default branch oss · commit 431e9e82 · scanned 6/19/2026, 6:12:20 PM

GitHub: 9,508 stars · 600 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 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 BloopAI/bloop, 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

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

OVERALL DIRECTION
  • mediumabout#1
    Update the repository description to highlight AI assistant features

    Why:

    CURRENT
    bloop is a fast code search engine written in Rust.
    COPY-PASTE FIX
    Bloop is an AI assistant for your code, offering natural language search, code understanding, and patch generation across your repositories.
  • lowreadme#2
    Reinforce key AI assistant capabilities in the README's opening

    Why:

    CURRENT
    bloop is ChatGPT for your code. Ask questions in natural language, search for code and generate patches using your existing codebase as context.
    COPY-PASTE FIX
    bloop is ChatGPT for your code. Ask questions in natural language for code understanding and navigation, search for code, and generate patches using your existing codebase as context.

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 BloopAI/bloop
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Cursor
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Cursor · recommended 2×
  2. OpenAI API · recommended 2×
  3. GitHub Copilot Enterprise · recommended 1×
  4. sourcegraph/sourcegraph · recommended 1×
  5. sourcegraph/cody · recommended 1×
  • CATEGORY QUERY
    AI assistant for code understanding and navigation across multiple repositories?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot Enterprise
    2. Sourcegraph (sourcegraph/sourcegraph)
    3. Cody (sourcegraph/cody)
    4. Cursor
    5. Tabnine Enterprise
    6. OpenAI API
    7. Anthropic's Claude

    AI recommended 7 alternatives but never named BloopAI/bloop. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tool to ask natural language questions about my codebase and generate code patches?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot Chat
    2. Cursor
    3. Continue
    4. OpenAI API
    5. GPT-4
    6. GPT-3.5 Turbo
    7. Codeium
    8. Tabnine Chat

    AI recommended 8 alternatives but never named BloopAI/bloop. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    warn

    Suggestion:

  • 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 BloopAI/bloop?
    pass
    AI named BloopAI/bloop explicitly

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

  • If a team adopts BloopAI/bloop in production, what risks or prerequisites should they evaluate first?
    pass
    AI named BloopAI/bloop 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 BloopAI/bloop solve, and who is the primary audience?
    pass
    AI named BloopAI/bloop 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 BloopAI/bloop. 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/BloopAI/bloop.svg)](https://repogeo.com/en/r/BloopAI/bloop)
HTML
<a href="https://repogeo.com/en/r/BloopAI/bloop"><img src="https://repogeo.com/badge/BloopAI/bloop.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

BloopAI/bloop — 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