RRepoGEO

REPOGEO REPORT · LITE

johnsusek/praeco

Default branch master · commit 4ece29d8 · scanned 6/14/2026, 7:36:49 AM

GitHub: 577 stars · 90 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 johnsusek/praeco, 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
    Clarify and strengthen the README's opening statement

    Why:

    CURRENT
    **Praeco** is an alerting tool for Elasticsearch – a GUI for ElastAlert 2, using the ElastAlert API.
    COPY-PASTE FIX
    **Praeco** is a powerful, web-based GUI for ElastAlert 2, designed to simplify and streamline Elasticsearch alerting. It provides an intuitive interface to build, test, and manage complex alerts for your Elasticsearch data, ensuring you stay informed about critical events.
  • mediumhomepage#2
    Add the project's official homepage URL

    Why:

    COPY-PASTE FIX
    https://[YOUR_PROJECT_HOMEPAGE_URL]
  • lowtopics#3
    Expand topics to include 'monitoring'

    Why:

    CURRENT
    alerting, elastalert, elasticsearch, logstash
    COPY-PASTE FIX
    alerting, elastalert, elasticsearch, logstash, monitoring

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 johnsusek/praeco
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Datadog
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Datadog · recommended 2×
  2. Splunk · recommended 2×
  3. grafana/grafana · recommended 1×
  4. elastic/kibana · recommended 1×
  5. prometheus/prometheus · recommended 1×
  • CATEGORY QUERY
    Looking for a web-based tool to easily configure and manage alerts for my search engine data.
    you: not recommended
    AI recommended (in order):
    1. Grafana (grafana/grafana)
    2. Kibana Alerting (elastic/kibana)
    3. Datadog
    4. Splunk
    5. Prometheus (prometheus/prometheus)
    6. Alertmanager (prometheus/alertmanager)
    7. PagerDuty

    AI recommended 7 alternatives but never named johnsusek/praeco. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are good solutions for defining complex log anomaly detection rules with extensive notification integrations?
    you: not recommended
    AI recommended (in order):
    1. Splunk Enterprise Security (ES)
    2. Splunk
    3. Elastic Stack
    4. Elasticsearch
    5. Kibana
    6. Beats
    7. Logstash
    8. X-Pack Alerting
    9. Datadog Log Management & Security Monitoring
    10. Datadog
    11. Dynatrace (with Log Monitoring)
    12. Dynatrace
    13. Davis
    14. Sumo Logic
    15. Cortex XSOAR
    16. Demisto
    17. Grafana
    18. Loki
    19. Alertmanager

    AI recommended 19 alternatives but never named johnsusek/praeco. 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 johnsusek/praeco?
    pass
    AI named johnsusek/praeco explicitly

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

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

Subscribe to Pro for deep diagnoses

johnsusek/praeco — 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