RRepoGEO

REPOGEO REPORT · LITE

YassKhazzan/openperplex_backend_os

Default branch main · commit 5b916472 · scanned 6/7/2026, 6:38:02 PM

GitHub: 894 stars · 87 forks

AI VISIBILITY SCORE
28 /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
2 / 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 YassKhazzan/openperplex_backend_os, 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
  • highreadme#1
    Clarify README's opening to prevent 'backend OS' misinterpretation

    Why:

    CURRENT
    # OpenPerPlex
    
    OpenPerPlex is an open-source AI search engine that leverages cutting-edge technologies to provide search capabilities over the web.
    COPY-PASTE FIX
    # OpenPerPlex: An Open-Source AI Search Engine Backend
    
    OpenPerPlex is the backend component of an open-source AI search engine. It leverages cutting-edge technologies to provide semantic search capabilities over the web. (Note: The '_os' in the repository name refers to 'open-source' and not 'operating system'.)
  • highlicense#2
    Add a LICENSE file to the repository root

    Why:

    COPY-PASTE FIX
    Create a file named `LICENSE` in the repository root with the full text of the MIT License.

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 YassKhazzan/openperplex_backend_os
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Hugging Face Transformers
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Hugging Face Transformers · recommended 2×
  2. Weaviate · recommended 2×
  3. Elasticsearch · recommended 1×
  4. Lucene · recommended 1×
  5. spaCy · recommended 1×
  • CATEGORY QUERY
    How to build an open-source web search engine with semantic capabilities?
    you: not recommended
    AI recommended (in order):
    1. Elasticsearch
    2. Lucene
    3. spaCy
    4. NLTK
    5. Hugging Face Transformers
    6. Apache Solr
    7. Weaviate
    8. Qdrant
    9. Milvus
    10. PostgreSQL
    11. pgvector
    12. Scrapy
    13. Beautiful Soup
    14. requests
    15. sentence-transformers

    AI recommended 15 alternatives but never named YassKhazzan/openperplex_backend_os. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are good libraries for integrating large language models into search applications?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack (deepset/haystack)
    4. Hugging Face Transformers
    5. Faiss
    6. Weaviate
    7. Pinecone

    AI recommended 7 alternatives but never named YassKhazzan/openperplex_backend_os. 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 YassKhazzan/openperplex_backend_os?
    pass
    AI did not name YassKhazzan/openperplex_backend_os — likely talking about a different project

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

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

Subscribe to Pro for deep diagnoses

YassKhazzan/openperplex_backend_os — 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