RRepoGEO

REPOGEO REPORT · LITE

RUC-NLPIR/Search-o1

Default branch main · commit c76a700f · scanned 6/24/2026, 4:27:58 PM

GitHub: 1,232 stars · 106 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)

3 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 RUC-NLPIR/Search-o1, 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
    Add a clear introductory sentence to the README

    Why:

    COPY-PASTE FIX
    Add the following sentence immediately after the H1: "Search-o1 is an agentic framework designed to enhance large reasoning models with advanced search capabilities, accepted at EMNLP 2025."
  • mediumtopics#2
    Expand repository topics with relevant LLM and agentic terms

    Why:

    CURRENT
    aimo, amc, gpqa, livecode, math, o1, qwq, r1, rag, reasoning
    COPY-PASTE FIX
    aimo, amc, gpqa, livecode, math, o1, qwq, r1, rag, reasoning, llm, large-language-models, agentic-ai, agent-framework, retrieval-augmented-generation, emnlp
  • mediumhomepage#3
    Add the project homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://search-o1.github.io/

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 RUC-NLPIR/Search-o1
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LangChain
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. LangChain · recommended 1×
  2. LlamaIndex · recommended 1×
  3. Haystack · recommended 1×
  4. Pinecone · recommended 1×
  5. Weaviate · recommended 1×
  • CATEGORY QUERY
    How can I improve large language model reasoning capabilities using external search and retrieval?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack
    4. Pinecone
    5. Weaviate
    6. Chroma
    7. Qdrant
    8. Google Search API
    9. SERP API
    10. SerpApi
    11. Neo4j
    12. Amazon Neptune

    AI recommended 12 alternatives but never named RUC-NLPIR/Search-o1. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are effective agentic frameworks for enhancing LLM performance on complex problem-solving tasks?
    you: not recommended
    AI recommended (in order):
    1. AutoGPT (Significant-Gravitas/AutoGPT)
    2. LangChain (langchain-ai/langchain)
    3. LlamaIndex (run-llama/llama_index)
    4. CrewAI (joaomdmoura/crewAI)
    5. BabyAGI (yoheinakajima/babyagi)
    6. Microsoft AutoGen (microsoft/autogen)

    AI recommended 6 alternatives but never named RUC-NLPIR/Search-o1. 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 RUC-NLPIR/Search-o1?
    pass
    AI named RUC-NLPIR/Search-o1 explicitly

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

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

Subscribe to Pro for deep diagnoses

RUC-NLPIR/Search-o1 — 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