RRepoGEO

REPOGEO REPORT · LITE

spotify/voyager

Default branch main · commit 2a2f1f13 · scanned 5/13/2026, 8:32:20 PM

GitHub: 1,570 stars · 79 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 spotify/voyager, 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 and strengthen README's core identity statement

    Why:

    CURRENT
    The README currently starts with several bare links (representing stripped badges/images), followed by "**_Voyager_** is a library for performing fast approximate nearest-neighbor searches..."
    COPY-PASTE FIX
    Ensure the README begins with a clear, concise statement of purpose, appearing *before* any badges, external links, or images. For example: "Voyager is a high-performance, approximate nearest-neighbor (ANN) search library for Python and Java, designed for ease of use and deployability in production environments like Spotify."
  • mediumtopics#2
    Add more specific topics to improve category visibility

    Why:

    CURRENT
    hnsw, hnswlib, java, machine-learning, nearest-neighbor-search, python
    COPY-PASTE FIX
    hnsw, hnswlib, java, machine-learning, nearest-neighbor-search, python, vector-search, similarity-search, ann-search, embeddings
  • lowreadme#3
    Elevate production usage statement in README

    Why:

    CURRENT
    Voyager is used extensively in production at Spotify, and is queried hundreds of millions of times per day to power numerous user-facing features.
    COPY-PASTE FIX
    Used extensively in production at Spotify, Voyager handles hundreds of millions of queries daily, powering numerous user-facing features. (Integrate this sentence into the first or second paragraph of the README, immediately following the core project definition.)

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 spotify/voyager
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Faiss
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Faiss · recommended 2×
  2. Annoy · recommended 1×
  3. Hnswlib · recommended 1×
  4. ScaNN · recommended 1×
  5. NMSLIB · recommended 1×
  • CATEGORY QUERY
    What's a good library for fast approximate nearest neighbor search in Python?
    you: not recommended
    AI recommended (in order):
    1. Faiss
    2. Annoy
    3. Hnswlib
    4. ScaNN
    5. NMSLIB
    6. Pyserini

    AI recommended 6 alternatives but never named spotify/voyager. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Need an easy-to-deploy HNSW-based vector similarity search library for Java.
    you: not recommended
    AI recommended (in order):
    1. Apache Lucene
    2. Chroma
    3. Weaviate
    4. Faiss
    5. Elasticsearch
    6. Milvus

    AI recommended 6 alternatives but never named spotify/voyager. 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 spotify/voyager?
    pass
    AI named spotify/voyager explicitly

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

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

Subscribe to Pro for deep diagnoses

spotify/voyager — 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