RRepoGEO

REPOGEO REPORT · LITE

PostHog/HouseWatch

Default branch main · commit ee46e990 · scanned 5/28/2026, 8:47:05 AM

GitHub: 620 stars · 42 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 PostHog/HouseWatch, 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 the README's opening to clearly differentiate HouseWatch

    Why:

    CURRENT
    ## 📈 Open source tool for monitoring and managing ClickHouse clusters
    COPY-PASTE FIX
    ## 📈 HouseWatch: A dedicated, self-hostable web UI for comprehensive monitoring and management of ClickHouse clusters
  • mediumhomepage#2
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    Add a relevant URL (e.g., a dedicated product page, documentation, or a demo instance) to the 'Homepage' field in the repository's 'About' section.
  • lowtopics#3
    Enhance repository topics with more specific monitoring terms

    Why:

    CURRENT
    clickhouse, database, database-management, django, mit-license, open-source, react
    COPY-PASTE FIX
    clickhouse, database, database-management, django, mit-license, open-source, react, monitoring, observability, performance-monitoring, query-analyzer

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 PostHog/HouseWatch
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Grafana
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Grafana · recommended 2×
  2. Prometheus · recommended 2×
  3. clickhouse-client · recommended 1×
  4. ClickHouse Keeper · recommended 1×
  5. Altinity.Cloud · recommended 1×
  • CATEGORY QUERY
    How can I effectively monitor and manage my ClickHouse database instances?
    you: not recommended
    AI recommended (in order):
    1. clickhouse-client
    2. Grafana
    3. Prometheus
    4. ClickHouse Keeper
    5. Altinity.Cloud
    6. DataGrip
    7. DBeaver

    AI recommended 7 alternatives but never named PostHog/HouseWatch. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are good open-source tools for analyzing ClickHouse query performance and cluster health?
    you: not recommended
    AI recommended (in order):
    1. ClickHouse built-in tools and system tables
    2. Grafana
    3. Prometheus
    4. clickhouse_exporter
    5. Vector
    6. Netdata
    7. Apache Superset

    AI recommended 7 alternatives but never named PostHog/HouseWatch. 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 PostHog/HouseWatch?
    pass
    AI did not name PostHog/HouseWatch — 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 PostHog/HouseWatch in production, what risks or prerequisites should they evaluate first?
    pass
    AI named PostHog/HouseWatch 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 PostHog/HouseWatch solve, and who is the primary audience?
    pass
    AI named PostHog/HouseWatch 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 PostHog/HouseWatch. 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/PostHog/HouseWatch.svg)](https://repogeo.com/en/r/PostHog/HouseWatch)
HTML
<a href="https://repogeo.com/en/r/PostHog/HouseWatch"><img src="https://repogeo.com/badge/PostHog/HouseWatch.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

PostHog/HouseWatch — 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