RRepoGEO

REPOGEO REPORT · LITE

google-research/bleurt

Default branch master · commit cebe7e6f · scanned 6/5/2026, 7:27:52 PM

GitHub: 792 stars · 94 forks

AI VISIBILITY SCORE
81 /100
Healthy
Category recall
2 / 2
Avg rank #3.0 when recommended
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 google-research/bleurt, 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
  • mediumreadme#1
    Refine README's opening sentence to highlight learned metric and human correlation

    Why:

    CURRENT
    # BLEURT: a Transfer Learning-Based Metric for Natural Language Generation
    
    BLEURT is an evaluation metric for Natural Language Generation. It takes a pair of sentences as input, a *reference* and a *candidate*, and it returns a score that indicates to what extent the candidate is fluent and conveys the meaning of the reference. It is comparable to `sentence-BLEU`, `BERTscore`, and `COMET`.
    COPY-PASTE FIX
    # BLEURT: a Transfer Learning-Based Metric for Natural Language Generation
    
    BLEURT is a *learned evaluation metric* for Natural Language Generation, explicitly trained on human quality judgments to predict the quality of generated text. It takes a pair of sentences as input, a *reference* and a *candidate*, and it returns a score that indicates to what extent the candidate is fluent and conveys the meaning of the reference. It is comparable to `sentence-BLEU`, `BERTscore`, and `COMET`.
  • lowreadme#2
    Add a 'Comparison with other metrics' section to the README

    Why:

    COPY-PASTE FIX
    ## Comparison with other metrics
    
    BLEURT is a learned metric, distinguishing it from traditional lexical overlap metrics like `BLEU` and `ROUGE`. Unlike `BERTScore` which relies on contextual embeddings similarity, BLEURT is explicitly trained on human quality judgments (e.g., WMT human ratings) to predict text quality, often correlating better with human perceptions. `COMET` is another learned metric, and while both aim for high human correlation, BLEURT's training methodology and model architecture (based on BERT/RemBERT) offer a distinct approach. For specific use cases, fine-tuning BLEURT on domain-specific human ratings can yield superior performance.

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
2 / 2
100% of queries surface google-research/bleurt
Avg rank
#3.0
Lower is better. #1 = top recommendation.
Share of voice
13%
Of all named tools, what % are you?
Top rival
BERTScore
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. BERTScore · recommended 2×
  2. ROUGE · recommended 1×
  3. METEOR · recommended 1×
  4. Amazon Mechanical Turk · recommended 1×
  5. Appen · recommended 1×
  • CATEGORY QUERY
    How to accurately evaluate the fluency and semantic similarity of generated text?
    you: #2
    AI recommended (in order):
    1. BERTScore
    2. BLEURT ← you
    3. ROUGE
    4. METEOR
    5. Amazon Mechanical Turk
    6. Appen
    7. Scale AI
    8. Hugging Face Transformers library
    9. MAUVE
    Show full AI answer
  • CATEGORY QUERY
    What are robust, learned metrics for assessing natural language generation quality?
    you: #4
    AI recommended (in order):
    1. COMET
    2. BERTScore
    3. MoverScore
    4. BLEURT ← you
    5. GEMBA
    6. UniTE
    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 google-research/bleurt?
    pass
    AI named google-research/bleurt explicitly

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

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

Subscribe to Pro for deep diagnoses

google-research/bleurt — 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