RRepoGEO

REPOGEO REPORT · LITE

linsa-io/blogs

Default branch master · commit 91597023 · scanned 6/10/2026, 3:27:32 PM

GitHub: 532 stars · 53 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 linsa-io/blogs, 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 state it's a curated list

    Why:

    CURRENT
    # Blogs
    COPY-PASTE FIX
    Replace the current H1 with: # Awesome Blogs: A Curated List of Technical and Niche Blogs
  • highlicense#2
    Add a LICENSE file to the repository

    Why:

    COPY-PASTE FIX
    Create a LICENSE file (e.g., MIT or Apache-2.0) in the root of the repository.
  • mediumhomepage#3
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    Add the URL for the hosted version of this blog list (if one exists) or a relevant project page to the repository's homepage field.

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 linsa-io/blogs
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Dev.to
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Dev.to · recommended 2×
  2. Hacker News · recommended 2×
  3. Medium · recommended 2×
  4. GitHub Awesome Lists · recommended 1×
  5. Indie Hackers · recommended 1×
  • CATEGORY QUERY
    Where can I find a curated list of excellent technical blogs for software development?
    you: not recommended
    AI recommended (in order):
    1. Dev.to
    2. Hacker News
    3. GitHub Awesome Lists
    4. Medium
    5. Indie Hackers
    6. StackShare Blog

    AI recommended 6 alternatives but never named linsa-io/blogs. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    I need a comprehensive collection of programming and computer science blogs to expand my knowledge.
    you: not recommended
    AI recommended (in order):
    1. Hacker News
    2. Dev.to
    3. Medium
    4. Towards Data Science
    5. Better Programming
    6. The Startup
    7. freeCodeCamp.org Blog
    8. Smashing Magazine
    9. Google Developers Blog
    10. Microsoft Learn Blog

    AI recommended 10 alternatives but never named linsa-io/blogs. 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 linsa-io/blogs?
    pass
    AI named linsa-io/blogs explicitly

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

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

Subscribe to Pro for deep diagnoses

linsa-io/blogs — 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