Only on request
We crawl a site when someone with a VibeSEO account starts an audit of it. There is no background discovery crawl, and we do not index the web at large.
Crawler · VibeSEObot
VibeSEObot is herebecause someone asked it to be.
It crawls a site only when that site's owner — or the person running their SEO — starts an audit in VibeSEO. It reads pages, obeys your robots.txt, and takes them one at a time. Here is everything you need to allowlist it, slow it down, or turn it off.
- user-agent token
- VibeSEObot
- outbound IP
- 165.227.211.167
- crawl rate, sequential
- 1 page / 0.5s
- honours robots.txt
- Always
How to allowlist it.
If a firewall — ModSecurity, Cloudflare, or your host's managed WAF — is returning 403 to our requests, allow the user-agent below.
Full user-agent string
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36 (compatible; VibeSEObot/1.0; +https://vibeseo.dev/bot)
Matching on the token VibeSEObot is enough — and it is the durable choice, because the Chrome version in the string moves as Chrome does.
Allow the user-agent, not the IP
Pages that need JavaScript to render are fetched through a headless browser provider, so those requests arrive from its addresses rather than ours. An IP-only rule would let part of the crawl through and block the rest — which looks like a half-broken audit, not a blocked one.
If you need an address anyway
The audit crawler's static fetches come from a single stable address:
165.227.211.167
Pair it with the user-agent rule above rather than using it alone.
How it behaves.
A crawler should be boring. This one is.
One page at a time
The crawl is sequential — a single request at a time, with a half-second pause between pages. If your robots.txt sets a longer Crawl-delay, we use yours instead.
HTML only
We fetch pages, your robots.txt, and your sitemap. Images, video, fonts, archives and other binary assets are skipped rather than downloaded.
Read-only
We issue GET requests (and HEAD when checking whether a link is broken). We never submit forms, log in, place orders, or change anything on your site.
Not an AI training bot
Your pages are crawled to produce a technical SEO report for the person who requested it. We do not sell your content or use it to train models.
Easy to turn off
A robots.txt rule stops us for good, on the next crawl. No account, no form, no waiting for a support reply.
How to slow it down — or stop it.
We read your robots.txt at the start of every crawl and follow it. No account or support ticket needed.
Block it entirely
User-agent: VibeSEObot Disallow: /
Add this to /robots.txt. We will stop from the next audit onwards.
Just make it gentler
User-agent: VibeSEObot Crawl-delay: 10
Ten seconds between requests instead of half a second. Any value works — we use yours whenever it is slower than our default.
Questions? We have answers.
Why is this bot crawling my site?
Someone asked VibeSEO to audit it — usually you, your agency, or whoever manages your SEO. VibeSEObot only visits a site when a signed-in user starts an audit of that site, so a crawl means a person clicked a button.
Why does the user-agent look like Chrome?
Because a bare bot user-agent gets blocked or served stripped-down HTML by a large share of sites and firewalls, which would make the audit wrong rather than merely blocked. So we do what Googlebot does: a real browser user-agent with the bot identity appended, so you can still see exactly who we are and allowlist us by name.
Should I allowlist the IP or the user-agent?
The user-agent. Pages that need JavaScript to render are fetched through a headless browser provider, so those requests do not come from our IP — an IP-only allowlist would let some of the crawl through and block the rest.
The crawl is too heavy for my server.
Set a Crawl-delay for VibeSEObot in your robots.txt and we will slow down to it on the next crawl. If something still looks wrong, email support@vibeseo.dev with the timestamps from your logs and we will look into it.
I blocked it and it still shows up in my logs.
We read robots.txt at the start of every crawl, so a rule takes effect from the next audit, not retroactively for one already running. If you still see VibeSEObot well after adding the rule, send us the log lines — a bot faking our user-agent is worth knowing about.
Still not sure what you're looking at?
Send us the log lines — the timestamp, the path, and the IP — and we will tell you exactly what the request was and why it was made. A real person reads it.