Aranet-SearchBot: Robots.txt & Crawl Policy Reference

AI Summary: Aranet-SearchBot is an AI-powered search engine and content indexing crawler. It gathers data to support the Aranet AI platform, functioning primarily as a background indexer to feed data into their systems.

Role and policy boundary

This bot operates as a background indexer to feed data into Aranet's systems. Like many emerging AI search bots, webmasters must weigh the potential benefits of inclusion against the server resources required to serve the crawler.

Because it lacks the widespread recognition of crawlers like Googlebot or Bingbot, many administrators opt to block it unless they have a specific strategic reason to be included in Aranet's index.

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

User-agent: Aranet-SearchBot
Allow: /
Disallow: /staging/
Disallow: /internal/

To stop access for the entire site, use:

User-agent: Aranet-SearchBot
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.

Aranet-SearchBot is generally expected to respect standard robots.txt directives. You can manage its access by explicitly targeting the Aranet-SearchBot User-Agent.

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 wish to block this crawler at the network layer to conserve server resources or enforce a strict allowlist policy, use a WAF rule:

{
  "description": "Block Aranet-SearchBot",
  "expression": "lower(http.user_agent) contains \"aranet-searchbot\"",
  "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_aranet_searchbot_private {
    default 0;
    ~*Aranet-SearchBot 1;
}

server {
    location ~ ^/(admin|account|private|licensed|internal|api)/ {
        if ($block_aranet_searchbot_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.