RRepoGEO

REPOGEO REPORT · LITE

FireRedTeam/FireRedTTS2

Default branch main · commit 404f3f61 · scanned 5/19/2026, 8:32:31 AM

GitHub: 1,392 stars · 123 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
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 FireRedTeam/FireRedTTS2, 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
  • highreadme#1
    Reposition README's opening statement to clarify purpose and counter miscategorization

    Why:

    CURRENT
    The README currently starts with a centered HTML div containing the title and subtitle.
    COPY-PASTE FIX
    Add the following plain text sentence as the very first line of the README, before any HTML or markdown headings: 'FireRedTTS-2 is an official PyTorch implementation for long-form, multi-speaker, streaming text-to-speech (TTS) generation, designed for applications like podcasts and chatbots, not red team operations.'
  • mediumhomepage#2
    Add a homepage URL to repository metadata

    Why:

    COPY-PASTE FIX
    https://fireredteam.github.io/demos/firered_tts_2/

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 FireRedTeam/FireRedTTS2
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
ElevenLabs
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. ElevenLabs · recommended 2×
  2. Google Cloud Text-to-Speech · recommended 1×
  3. Amazon Polly · recommended 1×
  4. Microsoft Azure Cognitive Services Speech · recommended 1×
  5. DeepMotion · recommended 1×
  • CATEGORY QUERY
    What are the best text-to-speech solutions for generating long multi-speaker conversations?
    you: not recommended
    AI recommended (in order):
    1. ElevenLabs

    AI recommended 1 alternative but never named FireRedTeam/FireRedTTS2. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a low-latency streaming TTS system for real-time multilingual chatbot interactions.
    you: not recommended
    AI recommended (in order):
    1. Google Cloud Text-to-Speech
    2. Amazon Polly
    3. Microsoft Azure Cognitive Services Speech
    4. ElevenLabs
    5. DeepMotion

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

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

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

Subscribe to Pro for deep diagnoses

FireRedTeam/FireRedTTS2 — 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