Seekbot: Robots.txt & Crawl Policy Reference

AI Summary: The registry describes Seekbot as a search engine crawler and records a browser-compatible User-Agent, but the linked seekbot.net domain has been repurposed into a blog about flowers and celebrations. No current operator, robots policy, rate limit, IP range, reverse-DNS method, or opt-out process is verified. Treat the token as a historical registry signal rather than an authenticated search crawler.

Role and policy boundary

The registry describes this entry as a Seekbot search engine web crawler for indexing and records this User-Agent:

Seekbot/1.0 (http://www.seekbot.net/bot.html) RobotsTxtFetcher/1.2

That description is the only search-engine evidence available in this review. The registry-linked HTTP bot page returned no content during headless-browser review, and the seekbot.net root domain now hosts an unrelated blog about flowers, cultural celebrations, and special occasions. The domain has been repurposed and no longer publishes a search-crawler specification.

This profile therefore uses legacy-label and does not present the registry description as a current operator policy. A matching request could be a legacy deployment, a test client, a private tool, or a spoofed header. Do not infer that a current Seekbot search engine exists, that it indexes content, or that it has any relationship to AI input, model training, or data retention. A User-Agent is a label, not an authentication mechanism.

Because no current policy was verified, do not publish an assumed Seekbot robots group as if it came from an operator. If logs establish a current, attributable token and you decide to exclude it, use the exact observed value in a deliberate site-owner rule:

User-agent: CONFIRMED-SEEKBOT
Disallow: /

For selective access after confirmation:

User-agent: CONFIRMED-SEEKBOT
Allow: /public/
Allow: /docs/
Disallow: /admin/
Disallow: /account/
Disallow: /private/
Disallow: /licensed/
Disallow: /api/

These are explanatory site-owner controls, not recovered Seekbot instructions. Robots.txt is advisory and cannot secure private or licensed content; use authentication, authorization, signed URLs, data minimization, and origin controls.

Layered verification

Start with raw access logs and preserve the complete User-Agent, source IP, ASN, reverse-DNS result, HTTP method, requested path, response status, response size, redirect chain, timestamp, concurrency, and request rate. No current Seekbot source in this review published an IP range, reverse-DNS procedure, Crawl-delay, rate guidance, removal address, or verification workflow. The registry token is useful for triage but is not authentication.

Do not treat the URL in the header as proof of operator ownership. A client can copy any URL, and the referenced domain is currently repurposed. Check source IP and DNS evidence independently, and require a current authoritative response before creating a trust exception.

Compare observed behavior with the historical search-indexing hypothesis without turning it into attribution. Public HTML, metadata, feeds, sitemaps, and ordinary assets may be requested by many tools. Private endpoints, licensed content, account routes, APIs, high concurrency, repeated retries, or unexpected bulk downloads establish impact and load risk, not Seekbot attribution or downstream use.

Evaluate /robots.txt only after the actual observed token is known. Confirm that it is served by the intended host, returns a successful text response, and contains the exact group you intend to publish. An absent operator source and a repurposed domain are not evidence of robots compliance. If no exact group exists, a global rule may affect unrelated clients and should be adopted only as an explicit site-wide decision.

Page-level directives can express indexing preferences:

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

X-Robots-Tag: noindex, nofollow

These signals do not authenticate an undocumented crawler or secure private paths. Enforce sensitive boundaries in the application and at the origin. If your policy distinguishes search indexing, AI input, reference use, and model training, document each purpose separately rather than inferring permission from a registry label.

WAF and Nginx remediation examples

When the source is unverified, use report-only logging and a narrow observation. Avoid broad seek, bot, or browser rules that can affect unrelated clients:

{
  "description": "Observe unverified Seekbot candidates",
  "expression": "lower(http.user_agent) contains \"seekbot/\"",
  "action": "log"
}

After independent verification and a policy decision, scope enforcement to sensitive routes and preserve evidence for the rule:

map $http_user_agent $block_confirmed_seekbot_private {
    default 0;
    # Add only a complete, independently verified token here.
    # ~*Seekbot/1\.0 1;
}

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

A User-Agent match is easy to spoof, and the registry URL now points to a repurposed domain. Do not invent an IP allowlist, reverse-DNS suffix, rate, training policy, or permanent trust exception. Use per-client rate limits, concurrency ceilings, timeouts, response-size controls, caching, and anomaly detection at the edge or origin. Start in report-only mode, review false positives, and restrict only after evidence supports the action.

Test public pages, feeds, sitemaps, structured data, licensed assets, account routes, APIs, 429 behavior, response-size limits, and approved integrations separately. Pair WAF controls with authentication and application authorization instead of using robots.txt as an access-control mechanism.

Review checklist

Search logs for the exact Seekbot substring and preserve the complete header, source IP, ASN, PTR result, forward lookup, path, method, response size, status, timing, rate, concurrency, and redirects. Treat the URL in the header as an unverified string, not a support channel.

Re-check the crawler registry, any future Seekbot source, robots.txt, and operator contact path. In this review the historical domain was repurposed into an unrelated blog. Keep this profile at legacy-label until a current source publishes an exact token, purpose, robots behavior, source-verification method, rate guidance, or opt-out process.

Decide whether your objective is to preserve public discovery, reduce crawl load, limit extraction, protect licensed material, or prevent private access. Publish exact robots rules only after the token is known; enforce private routes with authentication and origin controls.

Review search indexing, AI input, reference use, and model-training decisions separately. Neither the registry description nor a header containing a repurposed URL establishes downstream permission or use. Do not claim successful blocking or verification from configuration alone; validate later logs and obtain a current operator response when possible.

Record the date and reason for the legacy-label classification so future evidence can be compared without silently upgrading an unsupported historical label. If a new deployment identifies itself differently, create a separate evidence trail.

References

1. Crawler User Agents community registry — registry context for the Seekbot label and User-Agent; it does not authenticate current infrastructure.
2. Seekbot historical domain — registry-linked domain; headless-browser review on 2026-08-25 revealed it has been repurposed into an unrelated blog.
3. Google Robots.txt Introduction — general explanation of crawler directives and their limitations.
4. RFC 9309 — Robots Exclusion Protocol standard; it does not authenticate a User-Agent.

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