NeevaBot
Neeva's search crawler. Neeva shut down in 2023; the token is kept so an old robots.txt is read correctly, and it is not scored.
Where this comes from
- Retired by the vendor. No vendor page names this token.
- Robots.txt behaviour undocumented.
- Listed, not scored. It cannot keep a site out of today's answers, so the check shows a block without deducting for it.
In the top 1,000 websites
- 7.4% block it in robots.txt (42 of the 569 sites with a robots.txt), as of 2026-10-12.
- Method, limits and the full data: the October 2026 study of the top 1,000 websites.
What blocking it costs
Nothing: the vendor no longer sends this name. A rule for it is harmless and is not scored.
The robots.txt lines
To let it in (a group that names the crawler replaces any wildcard rules for it, so this also lifts a User-agent: * block):
User-agent: NeevaBot
Allow: /To keep it out:
User-agent: NeevaBot
Disallow: /A rule in robots.txt is a request. Whether this crawler honours it is undocumented. The robots.txt generator writes a whole file with the same split: block the training crawlers, keep the search and answer crawlers.
Does NeevaBot get through on your site?
Run the free check: it reads your robots.txt against all 51 crawlers and tells you which ones can read you, and what to change.