RRepoGEO

REPOGEO REPORT · LITE

neuphonic/neutts

Default branch main · commit 857bec02 · scanned 5/24/2026, 12:08:14 AM

GitHub: 5,899 stars · 643 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 neuphonic/neutts, 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 relevant topics to the repository

    Why:

    COPY-PASTE FIX
    text-to-speech, tts, on-device, voice-ai, speech-synthesis, gguf, voice-cloning, multilingual, deep-learning, machine-learning
  • mediumhomepage#2
    Add a homepage URL to the repository

    Why:

    COPY-PASTE FIX
    (Add the official project or company homepage URL in the repository settings)
  • mediumreadme#3
    Clarify the repository's license in the README

    Why:

    COPY-PASTE FIX
    Add a section (e.g., "License") to the README explicitly stating the terms under which the repository's code and models are distributed, referencing the existing LICENSE file.

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 neuphonic/neutts
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Coqui TTS (XTTS-v2)
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Coqui TTS (XTTS-v2) · recommended 1×
  2. VALL-E-X · recommended 1×
  3. Bark · recommended 1×
  4. OpenVoice · recommended 1×
  5. YourTTS · recommended 1×
  • CATEGORY QUERY
    What are good open source text-to-speech models for local deployment with GGUF?
    you: not recommended
    AI recommended (in order):
    1. Coqui TTS (XTTS-v2)
    2. VALL-E-X
    3. Bark
    4. OpenVoice
    5. YourTTS

    AI recommended 5 alternatives but never named neuphonic/neutts. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    I need an on-device TTS solution with real-time performance and instant voice cloning capabilities.
    you: not recommended
    AI recommended (in order):
    1. Coqui TTS (coqui-ai/TTS)
    2. Mozilla TTS (mozilla/TTS)
    3. NVIDIA Riva (nvidia-riva/riva)
    4. TensorFlow Lite (tensorflow/tensorflow/lite)
    5. PyTorch Mobile (pytorch/pytorch/mobile)
    6. OpenVINO (openvinotoolkit/openvino)
    7. Edge Impulse (edgeimpulse/edgeimpulse)

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

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

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

Subscribe to Pro for deep diagnoses

neuphonic/neutts — 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