RRepoGEO

REPOGEO REPORT · LITE

houko/wechatgpt

Default branch main · commit 8f4b9922 · scanned 6/14/2026, 6:07:10 AM

GitHub: 855 stars · 175 forks

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 houko/wechatgpt, 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 to specify category as a deployable bot

    Why:

    CURRENT
    ## 欢迎使用`wechatgpt`智能机器人，Let's Chat with ChatGPT
    COPY-PASTE FIX
    ## 🚀 wechatgpt: Deployable ChatGPT Bot for WeChat & Telegram (Go-powered, Docker-ready)
  • hightopics#2
    Update repository topics for accuracy and discoverability

    Why:

    CURRENT
    chatgpt, golang, slack, wechat
    COPY-PASTE FIX
    chatgpt, golang, wechat, telegram, ai-chatbot, docker-deployment, multi-modal
  • mediumhomepage#3
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    Add `https://github.com/houko/wechatgpt` as the homepage URL.

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 houko/wechatgpt
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
github.com/go-telegram-bot-api/telegram-bot-api/v5
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. github.com/go-telegram-bot-api/telegram-bot-api/v5 · recommended 1×
  2. github.com/wechat-go/wechat · recommended 1×
  3. wechaty/go-wechaty · recommended 1×
  4. net/http · recommended 1×
  5. OpenAI API · recommended 1×
  • CATEGORY QUERY
    How can I integrate an AI chatbot with WeChat or Telegram using a Go backend?
    you: not recommended
    AI recommended (in order):
    1. go-telegram-bot-api (github.com/go-telegram-bot-api/telegram-bot-api/v5)
    2. wechat-go/wechat (github.com/wechat-go/wechat)
    3. wechaty/go-wechaty (wechaty/go-wechaty)
    4. net/http
    5. OpenAI API
    6. sashabaranov/go-openai (github.com/sashabaranov/go-openai)
    7. Google Gemini API
    8. google/generative-ai-go (github.com/google/generative-ai-go/genai)
    9. Anthropic Claude API
    10. liushuang/go-anthropic (github.com/liushuang/go-anthropic)
    11. PostgreSQL
    12. jackc/pgx (github.com/jackc/pgx/v5)
    13. Redis
    14. go-redis/redis (github.com/go-redis/redis)

    AI recommended 14 alternatives but never named houko/wechatgpt. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking an open-source multi-modal AI assistant for messaging apps, deployable with Docker.
    you: not recommended
    AI recommended (in order):
    1. Rasa Open Source
    2. DeepPavlov
    3. Open Assistant
    4. Jarvis
    5. Mycroft AI

    AI recommended 5 alternatives but never named houko/wechatgpt. 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 houko/wechatgpt?
    pass
    AI named houko/wechatgpt explicitly

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

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

Subscribe to Pro for deep diagnoses

houko/wechatgpt — 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