RRepoGEO

REPOGEO REPORT · LITE

whyiyhw/chatgpt-wechat

Default branch main · commit b41fcb45 · scanned 6/24/2026, 7:36:59 PM

GitHub: 1,155 stars · 214 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
22 /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
1 / 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 whyiyhw/chatgpt-wechat, 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 the README H1 and opening sentence to clarify its role as a WeCom/WeChat LLM assistant/customer service solution.

    Why:

    CURRENT
    # chatgpt-wechat

可在微信 **安全使用（通过企业微信中转到微信，无封号风险）** 的 ChatGPT 个人助手应用,
    COPY-PASTE FIX
    # chatgpt-wechat: 企业微信/微信安全LLM个人助手与客服解决方案

一个基于企业微信中转，可在微信安全使用的LLM个人助手与客服解决方案，支持多模型接入和私有知识库，适用于个人和企业场景。
  • mediumtopics#2
    Add more specific topics related to AI customer service, enterprise chat, and LLM assistants.

    Why:

    CURRENT
    deepseek, dify, dify-services, gemini, gpt-4, gpt-4o, gpt4o-mini, wechat, wecom
    COPY-PASTE FIX
    deepseek, dify, dify-services, gemini, gpt-4, gpt-4o, gpt4o-mini, wechat, wecom, ai-assistant, llm-assistant, customer-service, enterprise-chatbot, private-knowledge-base, r-a-g, retrieval-augmented-generation
  • lowhomepage#3
    Add a homepage URL to the repository's About section.

    Why:

    COPY-PASTE FIX
    https://github.com/whyiyhw/agent-web

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 whyiyhw/chatgpt-wechat
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
ollama/ollama
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. ollama/ollama · recommended 1×
  2. LM Studio · recommended 1×
  3. AWS EC2 · recommended 1×
  4. Google Cloud Compute Engine · recommended 1×
  5. wechaty/wechaty · recommended 1×
  • CATEGORY QUERY
    How to safely integrate an AI assistant with large language models into WeChat for personal use?
    you: not recommended
    AI recommended (in order):
    1. Ollama (ollama/ollama)
    2. LM Studio
    3. AWS EC2
    4. Google Cloud Compute Engine
    5. WeChaty (wechaty/wechaty)
    6. itchat (littlecodersh/itchat)
    7. ChatGPT
    8. OpenAI API
    9. GPT-4o
    10. Microsoft Copilot
    11. WeChat Mini-Program Development Framework

    AI recommended 11 alternatives but never named whyiyhw/chatgpt-wechat. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking an open-source solution for enterprise chat platforms offering LLM customer service with private knowledge.
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Llama 3
    4. Ollama
    5. vLLM
    6. Weaviate
    7. Qdrant
    8. Chroma
    9. Chainlit
    10. Gradio
    11. Streamlit
    12. Rasa
    13. Open-WebUI
    14. Botpress
    15. Haystack
    16. Elasticsearch
    17. OpenSearch

    AI recommended 17 alternatives but never named whyiyhw/chatgpt-wechat. 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 whyiyhw/chatgpt-wechat?
    pass
    AI did not name whyiyhw/chatgpt-wechat — 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 whyiyhw/chatgpt-wechat in production, what risks or prerequisites should they evaluate first?
    pass
    AI named whyiyhw/chatgpt-wechat 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 whyiyhw/chatgpt-wechat solve, and who is the primary audience?
    pass
    AI did not name whyiyhw/chatgpt-wechat — 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?

Embed your GEO score

Drop this badge into the README of whyiyhw/chatgpt-wechat. 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/whyiyhw/chatgpt-wechat.svg)](https://repogeo.com/en/r/whyiyhw/chatgpt-wechat)
HTML
<a href="https://repogeo.com/en/r/whyiyhw/chatgpt-wechat"><img src="https://repogeo.com/badge/whyiyhw/chatgpt-wechat.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

whyiyhw/chatgpt-wechat — 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