VibeToGeoBot and why it reads your site

Identity

User-agent

VibeToGeoBot/1.0 (+https://vibetogeo.com/bot)

robots.txt name

VibeToGeoBot

When it visits

Only when someone asks: when an audit starts in the dashboard or the free tool, when Ai-ready pages are prepared, when a brand is added and for the free score.

What it reads

The home page, robots.txt, llms.txt, the sitemap and up to 9 more pages. It sends at most 3 requests at a time so your site isn't strained.

What it doesn't do

It doesn't run JavaScript, keep cookies, log in or fill in forms.

Contact

info@vibetogeo.com

How does it treat robots.txt?

VibeToGeoBot follows only the rules written for it by name. To keep us off your whole site, add this to robots.txt:

User-agent: VibeToGeoBot
Disallow: /

To close only part of the site, use a path such as Disallow: /dashboard/. If you close the home page, the audit won't start and the dashboard says why.

We don't treat User-agent: * rules as binding, because a person starts every read by hand. Google's user-triggered fetchers generally ignore robots.txt the same way. Rules you write for other bots we measure: if you block GPTBot, the report shows it.

Source: developers.google.com/search/docs/crawling-indexing/google-user-triggered-fetchers

Does our bot see what Ai sees?

On most sites, yes. What we see depends on how your site builds its pages.

1. 1

   Sites that build pages on the server

   WordPress, Shopify and most company sites send everyone the same HTML. Our bot sees what Ai bots see; you don't need to do anything. The one exception is a firewall that blocks bots (below).

2. 2

   Sites that draw pages only in the browser

   If the text is created later by JavaScript, most Ai bots see an empty page too, because they don't run JavaScript. The audit measures this correctly and "Readable content" comes out low. The fix is server-side rendering or static generation.

3. 3

   Sites that serve ready pages only to bots they know

   When Prerender.io, Rendertron or a hand-written nginx rule sends a full page to listed bots and an empty shell to everyone else, our bot sees the shell. The audit comes out worse than it should and shows a "returned the same content" note. Add our bot to your list.

Add it to your ready-page list

Add VibeToGeoBot to your list. Make sure the Ai answer bots are on it as well; some stock templates leave them out, so they get the empty shell too:

OAI-SearchBot · ChatGPT-User · Claude-SearchBot · Claude-User · PerplexityBot · Perplexity-User · VibeToGeoBot

map $http_user_agent $prerender_ua {
    default 0;
    "~*googlebot" 1;
    # ...
    "~*oai-searchbot" 1;
    "~*chatgpt-user" 1;
    "~*claude-searchbot" 1;
    "~*claude-user" 1;
    "~*perplexitybot" 1;
    "~*perplexity-user" 1;
    "~*vibetogeobot" 1;
}

app.use(
  require('prerender-node')
    .set('prerenderToken', 'TOKEN')
    .addUserAgents("VibeToGeoBot")
);

const rendertron = require('rendertron-middleware');
app.use(rendertron.makeMiddleware({
  proxyUrl: 'https://RENDERTRON/render',
  userAgentPattern: new RegExp(
    [...rendertron.botUserAgents, 'OAI-SearchBot', 'ChatGPT-User', 'Claude-SearchBot', 'Claude-User', 'PerplexityBot', 'Perplexity-User', 'VibeToGeoBot'].join('|'),
    'i',
  ),
}));

If a firewall blocks our bot

If pages return 403 or 429 in the audit, your bot protection may be stopping VibeToGeoBot. The audit then counts those pages as not loading.

(http.user_agent contains "VibeToGeoBot")

How to check

See what your server sends our bot with this command. Replace the address with one of your pages; the output should contain the page's text.

curl -s -A "VibeToGeoBot/1.0 (+https://vibetogeo.com/bot)" https://example.com/your-page

After the change, restart the audit in the dashboard. The "returned the same content" or "refused our bot" note should be gone.