RRepoGEO

REPOGEO REPORT · LITE

firecrawl/llmstxt-generator

Default branch main · commit 2f887b46 · scanned 5/31/2026, 2:32:36 AM

GitHub: 525 stars · 68 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 firecrawl/llmstxt-generator, 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 the deprecation notice in the README

    Why:

    CURRENT
    # ⚠️ DEPRECATION NOTICE
    
    This API is being deprecated in favor of our main endpoints. Here is an example repo that generates LLMs.txt files: https://github.com/mendableai/create-llmstxt-py. This API endpoint will still remain active but we will no longer be maintaining it after June 30, 2025.
    
    # llms.txt Generator 🚀
    COPY-PASTE FIX
    Move the '⚠️ DEPRECATION NOTICE' section to appear *after* the main 'llms.txt Generator 🚀' title and its initial description. The README should start with the value proposition.
  • mediumlicense#2
    Add a LICENSE file to the repository

    Why:

    CURRENT
    (no LICENSE file detected — the repo has no recognizable license)
    COPY-PASTE FIX
    Create a LICENSE file in the repository root with an appropriate open-source license (e.g., MIT, Apache-2.0) to clarify usage terms.

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 firecrawl/llmstxt-generator
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Scrapy
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Scrapy · recommended 2×
  2. Beautiful Soup 4 · recommended 2×
  3. Playwright · recommended 2×
  4. Common Crawl · recommended 2×
  5. Requests · recommended 1×
  • CATEGORY QUERY
    How to extract and consolidate website content into a single text file for LLM training?
    you: not recommended
    AI recommended (in order):
    1. Scrapy
    2. Beautiful Soup 4
    3. Requests
    4. Playwright
    5. Selenium
    6. Trafilatura
    7. wget
    8. Common Crawl

    AI recommended 8 alternatives but never named firecrawl/llmstxt-generator. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What's the best way to automatically prepare website data for large language model ingestion?
    you: not recommended
    AI recommended (in order):
    1. Scrapy
    2. Splash
    3. Playwright
    4. Beautiful Soup 4
    5. requests
    6. httpx
    7. Puppeteer
    8. Apify
    9. Common Crawl
    10. feedparser

    AI recommended 10 alternatives but never named firecrawl/llmstxt-generator. 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 firecrawl/llmstxt-generator?
    pass
    AI named firecrawl/llmstxt-generator explicitly

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

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

Subscribe to Pro for deep diagnoses

firecrawl/llmstxt-generator — 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