RRepoGEO

REPOGEO REPORT · LITE

browser-use/vibetest-use

Default branch main · commit fe0b90ac · scanned 6/7/2026, 5:23:10 PM

GitHub: 798 stars · 82 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 browser-use/vibetest-use, 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
    Strengthen README's opening sentence to clarify its role as a QA testing platform

    Why:

    CURRENT
    Automated QA testing using Browser-Use agents.
    COPY-PASTE FIX
    Vibetest Use is an automated QA testing platform that orchestrates Browser-Use agents to detect UI bugs, broken links, and accessibility issues on websites, perfect for both live and localhost development sites.
  • highlicense#2
    Add a LICENSE file to clarify usage terms

    Why:

    COPY-PASTE FIX
    Create a `LICENSE` file in the repository root with a standard open-source license (e.g., MIT, Apache-2.0, GPL-3.0) that reflects the project's intended usage.
  • mediumtopics#3
    Expand repository topics and add a homepage URL

    Why:

    CURRENT
    Topics: agents, browser, claude, cursor, mcp, mcp-server. Homepage: (none)
    COPY-PASTE FIX
    Add the following topics: `qa-testing`, `e2e-testing`, `ui-testing`, `browser-automation`, `web-testing`, `test-automation`. Also, add a relevant homepage URL in the repository settings if one exists.

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 browser-use/vibetest-use
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Cypress
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Cypress · recommended 1×
  2. Playwright · recommended 1×
  3. axe-core · recommended 1×
  4. Ahrefs · recommended 1×
  5. SEMrush · recommended 1×
  • CATEGORY QUERY
    How to automate website UI bug detection, broken links, and accessibility issues?
    you: not recommended
    AI recommended (in order):
    1. Cypress
    2. Playwright
    3. axe-core
    4. Ahrefs
    5. SEMrush
    6. Screaming Frog SEO Spider
    7. Google Lighthouse
    8. Selenium WebDriver
    9. BackstopJS

    AI recommended 9 alternatives but never named browser-use/vibetest-use. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking an automated solution for QA testing live and localhost web development sites.
    you: not recommended
    AI recommended (in order):
    1. Cypress (cypress-io/cypress)
    2. Playwright (microsoft/playwright)
    3. Selenium WebDriver (SeleniumHQ/selenium)
    4. Puppeteer (puppeteer/puppeteer)
    5. TestCafe (DevExpress/testcafe)
    6. Robot Framework (robotframework/robotframework)

    AI recommended 6 alternatives but never named browser-use/vibetest-use. 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 browser-use/vibetest-use?
    pass
    AI named browser-use/vibetest-use explicitly

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

  • If a team adopts browser-use/vibetest-use in production, what risks or prerequisites should they evaluate first?
    pass
    AI named browser-use/vibetest-use 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 browser-use/vibetest-use solve, and who is the primary audience?
    pass
    AI did not name browser-use/vibetest-use — 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?

Embed your GEO score

Drop this badge into the README of browser-use/vibetest-use. 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/browser-use/vibetest-use.svg)](https://repogeo.com/en/r/browser-use/vibetest-use)
HTML
<a href="https://repogeo.com/en/r/browser-use/vibetest-use"><img src="https://repogeo.com/badge/browser-use/vibetest-use.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

browser-use/vibetest-use — 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