RRepoGEO

REPOGEO REPORT · LITE

yihong0618/gitblog

Default branch master · commit 57f8b59e · scanned 5/23/2026, 3:38:19 PM

GitHub: 1,609 stars · 143 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

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 yihong0618/gitblog, 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
  • highreadme#1
    Reposition README's opening to clarify project's purpose as a blog generator

    Why:

    CURRENT
    ## Gitblog
My personal blog(About Me) using issues and GitHub Actions (随意转载，无需署名)
    COPY-PASTE FIX
    ## Gitblog
A lightweight, personal blog generator that leverages GitHub Issues as a CMS and GitHub Actions for publishing. Create your own blog posts directly from issues, powered by Git.
  • mediumreadme#2
    Add a sentence to README highlighting GitHub Issues as CMS differentiator

    Why:

    COPY-PASTE FIX
    Unlike traditional static site generators, Gitblog uniquely uses GitHub Issues as its content management system, allowing you to write and manage blog posts directly within your repository's issues.

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 yihong0618/gitblog
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Jekyll
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Jekyll · recommended 2×
  2. Hugo · recommended 2×
  3. Next.js · recommended 2×
  4. Gatsby · recommended 2×
  5. octokit · recommended 2×
  • CATEGORY QUERY
    How can I create a personal blog leveraging GitHub issues and actions for content management?
    you: not recommended
    AI recommended (in order):
    1. Jekyll
    2. jekyll-github-issues
    3. Hugo
    4. Next.js
    5. Gatsby
    6. octokit
    7. Vercel
    8. Netlify
    9. requests
    10. node-fetch
    11. octokit
    12. Issue Blog
    13. issue-blog
    14. Eleventy
    15. Astro
    16. SvelteKit

    AI recommended 16 alternatives but never named yihong0618/gitblog. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a lightweight blogging solution that publishes content directly from a GitHub repository.
    you: not recommended
    AI recommended (in order):
    1. Jekyll
    2. Hugo
    3. Astro
    4. Eleventy
    5. Next.js
    6. Gatsby
    7. Nuxt.js

    AI recommended 7 alternatives but never named yihong0618/gitblog. 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 yihong0618/gitblog?
    pass
    AI named yihong0618/gitblog explicitly

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

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

Subscribe to Pro for deep diagnoses

yihong0618/gitblog — 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