REPOGEO REPORT · LITE

teivah/sre-roadmap

Default branch main · commit 48627066 · scanned 6/16/2026, 9:33:01 PM

GitHub: 543 stars · 48 forks

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 teivah/sre-roadmap, 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 H1 and opening paragraph to clarify category

Why:

CURRENT

# SRE Roadmap

An opinionated roadmap to become an SRE (Concepts > Tools)

COPY-PASTE FIX

# SRE Roadmap: A Concept-First Learning Path

An opinionated, concept-first learning roadmap and comprehensive curriculum for aspiring Site Reliability Engineers, emphasizing foundational distributed systems knowledge and general reliability principles over specific tools.

mediumtopics#2

Add more specific SRE and distributed systems topics

Why:

CURRENT

roadmap, sre

COPY-PASTE FIX

roadmap, sre, site-reliability-engineering, distributed-systems, system-design, reliability, scalability, performance, observability, databases, caching, load-balancing, microservices, distributed-computing-concepts, devops

lowreadme#3

Add a sentence to clarify the roadmap's focus regarding specific platforms like Kubernetes

Why:

COPY-PASTE FIX

While Kubernetes is an important SRE tool, this roadmap prioritizes foundational distributed systems concepts and general reliability principles, rather than focusing on any single platform or technology.

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 teivah/sre-roadmap

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

Python

Recommended in 1 of 2 queries

COMPETITOR LEADERBOARD

Python · recommended 1×
Go · recommended 1×
Bash · recommended 1×
grep · recommended 1×
awk · recommended 1×

CATEGORY QUERY
What's a good learning path to become a site reliability engineer, focusing on core concepts?
you: not recommended
AI recommended (in order):
1. Python
2. Go
3. Bash
4. grep
5. awk
6. sed
7. systemd
8. cron
9. tcpdump
10. netstat
11. Wireshark
12. Docker
13. Kubernetes
14. AWS
15. EC2
16. S3
17. VPC
18. RDS
19. IAM
20. CloudWatch
21. Lambda
22. Google Cloud Platform
23. GKE
24. Compute Engine
25. Cloud Storage
26. Cloud SQL
27. Stackdriver
28. Microsoft Azure
29. Virtual Machines
30. Storage Accounts
31. Virtual Networks
32. Azure Monitor
33. Prometheus
34. Grafana
35. Elasticsearch
36. Logstash
37. Kibana
38. OpenTelemetry
39. PagerDuty
40. Terraform
41. Ansible
42. Helm
43. Git
44. GitHub Actions
45. GitLab CI/CD
46. Jenkins
47. Gremlin
48. Chaos Mesh
AI recommended 48 alternatives but never named teivah/sre-roadmap. This is the gap to close.
Show full AI answer
CATEGORY QUERY
Where can I find a comprehensive guide to distributed systems concepts for reliability engineering?
you: not recommended
AI recommended (in order):
1. Designing Data-Intensive Applications
2. Site Reliability Engineering: How Google Runs Production Systems
3. The Site Reliability Workbook: Practical Ways to Implement SRE
4. Distributed Systems: Concepts and Design
5. Building Microservices
6. Release It! Design and Deploy Production-Ready Software
7. Designing for Scalability with Erlang/OTP
AI recommended 7 alternatives but never named teivah/sre-roadmap. 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 teivah/sre-roadmap?
pass
AI named teivah/sre-roadmap explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
If a team adopts teivah/sre-roadmap in production, what risks or prerequisites should they evaluate first?
pass
AI named teivah/sre-roadmap 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 teivah/sre-roadmap solve, and who is the primary audience?
pass
AI named teivah/sre-roadmap 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 teivah/sre-roadmap. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

Live preview

MARKDOWN (README)

[![RepoGEO](https://repogeo.com/badge/teivah/sre-roadmap.svg)](https://repogeo.com/en/r/teivah/sre-roadmap)

HTML

<a href="https://repogeo.com/en/r/teivah/sre-roadmap"><img src="https://repogeo.com/badge/teivah/sre-roadmap.svg" alt="RepoGEO" /></a>

Pro

Subscribe to Pro for deep diagnoses

teivah/sre-roadmap — 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