RRepoGEO

REPOGEO REPORT · LITE

upgundecha/howtheysre

Default branch main · commit 4fd5a3a0 · scanned 5/9/2026, 3:57:29 PM

GitHub: 9,726 stars · 886 forks

AI VISIBILITY SCORE
28 /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
2 / 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 upgundecha/howtheysre, 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 introduction to explicitly state it's a resource collection, not a tool

    Why:

    CURRENT
    __How They SRE__ How They SRE is a curated knowledge repository of Site Reliability Engineering (SRE) best practices, tools, techniques, and culture adopted by leading technology or tech-savvy organizations.
    COPY-PASTE FIX
    **How They SRE** is a curated knowledge repository of publicly available resources on Site Reliability Engineering (SRE) best practices, tools, techniques, and culture. This is a collection of external articles, talks, and papers, *not* a software tool or library.
  • mediumabout#2
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    https://github.com/upgundecha/howtheysre
  • lowtopics#3
    Add topics that describe the repo's format as a resource collection

    Why:

    CURRENT
    alerting, chaos-engineering, dev-ops, devops, hacktoberfest, hacktoberfest-accepted, incident-management, incident-response, infrastructure, ml-ops, monitoring, observability, on-call, post-mortem, reliability, security, site-reliability-engineering, software-engineering, sre, sre-culture
    COPY-PASTE FIX
    alerting, chaos-engineering, dev-ops, devops, hacktoberfest, hacktoberfest-accepted, incident-management, incident-response, infrastructure, ml-ops, monitoring, observability, on-call, post-mortem, reliability, security, site-reliability-engineering, software-engineering, sre, sre-culture, resource-collection, knowledge-base

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 upgundecha/howtheysre
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Chaos Monkey
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Chaos Monkey · recommended 1×
  2. Chaos Gorilla · recommended 1×
  3. Amazon Web Services (AWS) · recommended 1×
  4. Azure · recommended 1×
  5. Datadog · recommended 1×
  • CATEGORY QUERY
    Where can I find real-world examples of SRE best practices from leading tech companies?
    you: not recommended
    AI recommended (in order):
    1. Chaos Monkey
    2. Chaos Gorilla
    3. Amazon Web Services (AWS)
    4. Azure
    5. Datadog
    6. New Relic
    7. Splunk
    8. Grafana Labs

    AI recommended 8 alternatives but never named upgundecha/howtheysre. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for resources on improving incident response and on-call reliability practices.
    you: not recommended
    AI recommended (in order):
    1. PagerDuty

    AI recommended 1 alternative but never named upgundecha/howtheysre. 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 upgundecha/howtheysre?
    pass
    AI did not name upgundecha/howtheysre — likely talking about a different project

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

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

Subscribe to Pro for deep diagnoses

upgundecha/howtheysre — 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