RRepoGEO

REPOGEO REPORT · LITE

lingodotdev/lingo.dev

Default branch main · commit 0f262782 · scanned 5/20/2026, 8:17:01 PM

GitHub: 5,402 stars · 834 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
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 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 lingodotdev/lingo.dev, 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
  • highabout#1
    Update the 'About' description to be more explicit about the platform's purpose

    Why:

    CURRENT
    Open-source localization engineering tools. Connects to Lingo.dev localization engineering platform for consistent, quality translations.
    COPY-PASTE FIX
    Open-source localization engineering platform and tools for automated i18n, translation workflows, and CI/CD integration. Connects to Lingo.dev for consistent, quality translations.
  • hightopics#2
    Expand repository topics with more specific localization and platform terms

    Why:

    CURRENT
    i18n, javascript, react, react-native, typescript
    COPY-PASTE FIX
    i18n, localization, l10n, translation-management, translation-automation, ci-cd, github-actions, javascript, react, react-native, typescript
  • mediumreadme#3
    Ensure the README's initial text clearly states the platform's core purpose

    Why:

    CURRENT
    The README starts with centered text and internal links before the 'Quick Start' table, with the core description within a <p align="center"> tag.
    COPY-PASTE FIX
    Ensure the very first non-badge, non-image text in the README clearly states: 'Lingo.dev is an open-source localization engineering platform providing tools for automated i18n, translation workflows, and CI/CD integration. It connects to Lingo.dev for consistent, quality translations.'

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 lingodotdev/lingo.dev
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Crowdin
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Crowdin · recommended 1×
  2. Transifex · recommended 1×
  3. Phrase · recommended 1×
  4. Localazy · recommended 1×
  5. i18next · recommended 1×
  • CATEGORY QUERY
    How can I streamline translation workflows for my React and React Native applications?
    you: not recommended
    AI recommended (in order):
    1. Crowdin
    2. Transifex
    3. Phrase
    4. Localazy
    5. i18next
    6. React-Intl

    AI recommended 6 alternatives but never named lingodotdev/lingo.dev. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What open-source tools help automate i18n string extraction and translation updates in CI/CD?
    you: not recommended
    AI recommended (in order):
    1. Format.JS CLI (formatjs/formatjs)
    2. i18next-parser (i18next/i18next-parser)
    3. Babel-plugin-react-intl (formatjs/babel-plugin-react-intl)
    4. gettext
    5. i18n-tasks (glebm/i18n-tasks)
    6. vue-i18n-extract (pixari/vue-i18n-extract)
    7. ngx-translate-extract (ngx-translate/extract)

    AI recommended 7 alternatives but never named lingodotdev/lingo.dev. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    pass

  • 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 lingodotdev/lingo.dev?
    pass
    AI named lingodotdev/lingo.dev explicitly

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

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

Subscribe to Pro for deep diagnoses

lingodotdev/lingo.dev — 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