RRepoGEO

REPOGEO REPORT · LITE

Liamour/UE-Mapping

Default branch master · commit dfd1d511 · scanned 6/10/2026, 6:18:52 AM

GitHub: 601 stars · 46 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)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
30 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 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 Liamour/UE-Mapping, 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
  • highabout#1
    Add a concise description to the repository's About section

    Why:

    COPY-PASTE FIX
    An Unreal Engine 5 editor plugin with a Python backend that uses LLMs to generate a 'narrative map' of your project's Blueprints, aiding in onboarding and understanding complex UE5 projects.
  • highlicense#2
    Add a LICENSE file and clarify the license in the README

    Why:

    COPY-PASTE FIX
    Create a 'LICENSE' file in the repository root with your chosen license text (e.g., MIT, Apache-2.0). Then, update the README's 'License' section to explicitly state the license, for example: 'This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.'

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 Liamour/UE-Mapping
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Unreal Engine
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Unreal Engine · recommended 1×
  2. Unreal Engine Learning · recommended 1×
  3. Perforce · recommended 1×
  4. Git LFS · recommended 1×
  5. GitKraken · recommended 1×
  • CATEGORY QUERY
    What helps new developers quickly onboard to large, undocumented Unreal Engine 5 projects?
    you: not recommended
    AI recommended (in order):
    1. Unreal Engine
    2. Unreal Engine Learning
    3. Perforce
    4. Git LFS
    5. GitKraken
    6. SourceTree
    7. Confluence
    8. Notion
    9. Google Docs
    10. Microsoft OneNote
    11. Visual Studio Code
    12. Rider for Unreal Engine
    13. Discord
    14. Slack

    AI recommended 14 alternatives but never named Liamour/UE-Mapping. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Are there AI tools for automatically documenting Unreal Engine blueprint logic and dependencies?
    you: not recommended
    AI recommended (in order):
    1. BlueprintUE.com
    2. Unreal Engine's Built-in Commenting and Graph Organization Features
    3. ChatGPT/GPT-4
    4. GitHub Copilot

    AI recommended 4 alternatives but never named Liamour/UE-Mapping. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    fail

    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 Liamour/UE-Mapping?
    pass
    AI named Liamour/UE-Mapping explicitly

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

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

Subscribe to Pro for deep diagnoses

Liamour/UE-Mapping — 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