RRepoGEO

REPOGEO REPORT · LITE

edwko/OuteTTS

Default branch main · commit f5eac6e7 · scanned 5/18/2026, 2:12:42 PM

GitHub: 1,431 stars · 116 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 edwko/OuteTTS, 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 README's opening to highlight core features

    Why:

    CURRENT
    The README starts with `## OuteTTS` followed by links and a compatibility table.
    COPY-PASTE FIX
    Add the following sentence immediately after `## OuteTTS`: "OuteTTS is a high-performance, zero-shot Text-to-Speech (TTS) interface designed for local GGUF models (via llama.cpp) and efficient batched inference, enabling speech synthesis for unseen speakers without target audio."
  • mediumabout#2
    Update the repository description

    Why:

    CURRENT
    Interface for OuteTTS models.
    COPY-PASTE FIX
    High-performance, zero-shot Text-to-Speech (TTS) interface supporting local GGUF models (llama.cpp) and batched inference for unseen speakers.
  • lowtopics#3
    Expand repository topics for better query matching

    Why:

    CURRENT
    gguf, llama, text-to-speech, transformers, tts
    COPY-PASTE FIX
    gguf, llama, text-to-speech, transformers, tts, batched-inference, zero-shot-tts, python, javascript

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 edwko/OuteTTS
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Coqui TTS
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Coqui TTS · recommended 2×
  2. Bark · recommended 2×
  3. Piper · recommended 1×
  4. OpenVINO · recommended 1×
  5. Google Cloud Text-to-Speech · recommended 1×
  • CATEGORY QUERY
    What are good options for running text-to-speech models locally with GGUF support?
    you: not recommended
    AI recommended (in order):
    1. Piper
    2. Coqui TTS
    3. Bark
    4. OpenVINO

    AI recommended 4 alternatives but never named edwko/OuteTTS. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How to implement high-performance batched text-to-speech generation in Python or JavaScript?
    you: not recommended
    AI recommended (in order):
    1. Google Cloud Text-to-Speech
    2. Amazon Polly
    3. Microsoft Azure Cognitive Services Speech
    4. Coqui TTS
    5. Mozilla TTS
    6. Bark
    7. ElevenLabs

    AI recommended 7 alternatives but never named edwko/OuteTTS. 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 edwko/OuteTTS?
    pass
    AI named edwko/OuteTTS explicitly

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

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

Subscribe to Pro for deep diagnoses

edwko/OuteTTS — 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