WebmasterID logoWebmasterID
Robots & crawl control

How to block the Seekport Crawler

The Seekport Crawler is the bot for Seekport, a search engine. This page shows how to disallow it in robots.txt, what blocking it costs in Seekport visibility, and how to confirm the rule is honoured.

Partially verified

robots.txt rule

Seekport's crawler identifies with a self-identifying user agent containing its token. To disallow it site-wide:

User-agent: Seekport Crawler Disallow: /

Confirm the exact token from your access logs before committing, and match on the documented token rather than a version string. As with any engine, a Disallow asks the crawler to stop but does not enforce it.

Scope and limits

Blocking the Seekport Crawler affects only Seekport; Google, Bing, and others keep their own tokens and policies. A Disallow does not remove pages already in Seekport's index — use noindex on a fetchable URL for that.

Since the user agent can be copied, persistent hits after a correct rule may be a non-compliant client rather than the genuine Seekport Crawler.

How it appears in analytics and logs

Seekport Crawler hits mean the Seekport search engine is indexing your pages. Continued hits after a Disallow point to a cached robots.txt or a token mismatch.

Diagnostic use case

Reduce crawl load from the Seekport Crawler when Seekport visibility is not valuable to your audience.

What WebmasterID can help detect

WebmasterID records the Seekport Crawler as a search bot so you can verify a block is respected and keep its hits out of human analytics.

Common mistakes

Privacy and accuracy notes

The rule matches the Seekport Crawler token only; no visitor data is involved. robots.txt requests compliance from cooperative crawlers.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.