RRepoGEO

REPOGEO REPORT · LITE

xgo-dev/llgo

Default branch main · commit eecba9f4 · scanned 6/4/2026, 8:17:31 PM

GitHub: 669 stars · 49 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 xgo-dev/llgo, 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
  • hightopics#1
    Add specific topics to improve categorization

    Why:

    COPY-PASTE FIX
    go-compiler, llvm, c-interop, python-interop, javascript-interop, webassembly, game-development, embedded-systems, xgo
  • highreadme#2
    Reposition the README's opening sentence to emphasize 'compiler'

    Why:

    CURRENT
    LLGo is a Go compiler based on LLVM in order to better integrate Go with the C ecosystem including Python and JavaScript. It's a subproject of the XGo project.
    COPY-PASTE FIX
    LLGo is an alternative Go compiler built on LLVM, designed to deeply integrate Go with the C ecosystem (including Python and JavaScript) by leveraging ABI compatibility. It's a subproject of the XGo project.
  • mediumreadme#3
    Add a comparison section to the README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, perhaps titled 'LLGo vs. Other Integration Tools' or 'Why LLGo?', explaining how LLGo's compiler-based approach differs from tools like cgo, SWIG, or gopy for C/Python/JS integration, and from other Go compilers like TinyGo for specific use cases.

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 xgo-dev/llgo
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
cgo
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. cgo · recommended 1×
  2. SWIG · recommended 1×
  3. gopy · recommended 1×
  4. gRPC · recommended 1×
  5. Apache Thrift · recommended 1×
  • CATEGORY QUERY
    How to integrate Go applications with existing C, Python, or JavaScript codebases?
    you: not recommended
    AI recommended (in order):
    1. cgo
    2. SWIG
    3. gopy
    4. gRPC
    5. Apache Thrift
    6. WebAssembly
    7. gRPC-Web
    8. Twirp

    AI recommended 8 alternatives but never named xgo-dev/llgo. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools compile Go for game development or WebAssembly with C ecosystem support?
    you: not recommended
    AI recommended (in order):
    1. TinyGo (tinygo-org/tinygo)
    2. Go's Official syscall/js and wasm Toolchain
    3. GopherJS (gopherjs/gopherjs)
    4. Emscripten (emscripten-core/emscripten)
    5. Ebitengine (hajimehoshi/ebitengine)
    6. Wasmtime (bytecodealliance/wasmtime)
    7. Wasmer (wasmerio/wasmer)

    AI recommended 7 alternatives but never named xgo-dev/llgo. 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 xgo-dev/llgo?
    pass
    AI named xgo-dev/llgo explicitly

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

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

Subscribe to Pro for deep diagnoses

xgo-dev/llgo — 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