AissistBot

AissistBot reads a website only because an Aissist.io customer added that website as a knowledge source for their AI support agent. It reads the site's public pages so the agent can answer that customer's own support questions.

• It follows robots.txt. It uses the rules for the AissistBot user agent when your robots.txt has them, otherwise the rules for *. It never requests a page that robots.txt disallows. If robots.txt cannot be read because of a server error, it fetches nothing.
• It requests one page at a time per site, at least 1 second apart. If your robots.txt sets a Crawl-delay, it waits that long between requests, up to 30 seconds.
• It re-checks the site about once a day: it reads your sitemaps and follows links to find new pages, and asks for pages it already has with conditional requests (If-None-Match / If-Modified-Since), which your server can answer with a short 304 when nothing changed.
• It only reads public pages with plain GET requests. It does not log in or submit forms, and it skips login, account, cart, checkout and search pages it finds while following links.
• It does not run JavaScript. Pages that need JavaScript to show their content are fetched the way described under “When bot protection refuses it” below.

Add these lines to your robots.txt to stop AissistBot from reading any page of your site:

User-agent: AissistBot
Disallow: /

To block only part of your site, use Disallow with that path instead of /.

If your site uses a firewall or bot manager, it may refuse AissistBot even though your robots.txt allows it. To let it through, allow requests whose User-Agent contains AissistBot:

• Cloudflare: create a WAF custom rule that matches requests where the User-Agent contains AissistBot, with the action Skip, and choose the protections it should skip (for example Super Bot Fight Mode and the managed rules).
• Other bot managers and firewalls: add the user agent AissistBot to the allow list.

We do not publish a fixed list of IP addresses for AissistBot, so allow it by user agent.

When bot protection refuses a page that robots.txt allows, or the page needs JavaScript to show its content, the customer's knowledge source may fetch that page through a third-party fetching service instead. Those requests come from that service's network and may not carry the AissistBot user agent.

If you don't want your pages read at all, use robots.txt as shown above. The fallback is never used for pages that robots.txt disallows.

Questions about AissistBot, or a problem with how it reads your site: email support@aissist.io.