AISearchBot: Robots.txt & Crawl Policy Reference

AI Summary: AISearchBot is an obscure search-engine crawler with no publicly identified major operator. Its job is to find, fetch, and index web pages, likely for a niche or managed AI-search service. Due to the lack of a prominent operator, many webmasters choose to block it.

Role and policy boundary

AISearchBot acts as a background indexer. Because it lacks a well-known, reputable operator (like Google, Microsoft, or OpenAI), many webmasters choose to block it to save server bandwidth, as the return on investment (traffic generated from its index) is typically negligible or non-existent.

If you are running a strict allowlist policy for bots, this crawler should likely remain blocked unless you can specifically identify the service it feeds and determine that it provides value to your business.

A robots rule is a declaration of intent; it does not replace authentication, authorization, or rate limiting. Start with a dedicated group:

User-agent: AISearchBot
Allow: /
Disallow: /staging/
Disallow: /internal/

To stop access for the entire site, use:

User-agent: AISearchBot
Disallow: /

Avoid assuming that User-agent: * expresses the same business intent. A wildcard can affect assistant and training crawlers too, and it makes later audits harder because the source of the decision is less specific.

Layered verification

Verify the same URL through each control plane instead of assuming that one green signal represents the whole request path. Compare the bot-specific robots group, the page-level metadata, and the response headers captured at the public edge.

Like most standard crawlers, AISearchBot is generally expected to respect robots.txt directives. Adding a specific Disallow rule for the AISearchBot User-Agent is the first step to blocking it.

The Policy Engine evaluates the selected user-agent, path scope, and the other supplied layers independently. It can therefore explain why a bot is allowed while another is blocked, rather than returning one blended website score.

Page-level directives can still override the intended outcome for indexing:

<meta name="robots" content="noindex, nofollow">

X-Robots-Tag: noindex, nofollow

If a response uses these tags, the report marks the result as blocked or conflicting even if the crawler-specific robots group is permissive. This is especially important for canonical pages served through an edge cache where headers may differ from the origin response.

WAF and Nginx remediation examples

If you employ a default-deny policy for unknown or low-value bots, or if you find that AISearchBot is ignoring your robots.txt directives, you should block it at the WAF or server level:

{
  "description": "Block obscure AISearchBot",
  "expression": "lower(http.user_agent) contains \"aisearchbot\"",
  "action": "block"
}

Use your platform's actual middleware response pattern rather than copying this simplified example without review. Never place a secret, verification token, or internal policy identifier in a public header.

map $http_user_agent $block_aisearchbot_private {
    default 0;
    ~*AISearchBot 1;
}

server {
    location ~ ^/(admin|account|private|licensed|internal|api)/ {
        if ($block_aisearchbot_private) { return 403; }
        try_files $uri $uri/ =404;
    }
}

Review checklist

Use this checklist after every policy change and after a CDN or WAF migration. Record the request URL, User-Agent, HTTP status, final redirect, and the exact evidence used to reach the decision.

Verify that the dedicated group appears before relying on a wildcard, test a representative public and private path, and compare live response headers with robots.txt. Keep the policy close to the content owner's intent and record whether the site wants discovery, citation, or no access at all.

Need to optimize your entire site for AI search visibility? Run a comprehensive audit with Geolify.ai.