Seekport Crawler
Seekport Crawler is associated with the Seekport search project. Its user agent is reported to contain a SeekportBot identifier. Public documentation is sparse and some specifics cannot be confidently sourced, so this entry describes the identification pattern and leaves unconfirmed details unverified.
What this means
Seekport Crawler is associated with the Seekport search project. In logs it appears as an automated fetcher whose user agent is reported to contain a SeekportBot identifier.
Public, stable documentation about Seekport's crawler is limited. For that reason this entry describes the identification pattern and does not assert specifics — exact scope, ownership history, or verification methods — that cannot be confidently sourced. Treat any such claims you read elsewhere with caution.
Identification and caveats
Match on the SeekportBot identifier in the user agent rather than a full version string. The user agent is a claim and can be copied; because verification guidance is not clearly published, do not assume IP-range authenticity and do not fabricate IP ranges. To set a robots.txt rule, target the SeekportBot token, treating compliance as a request rather than a guarantee.
- User agent reported to contain: SeekportBot
- Associated with the Seekport search project
- Public documentation sparse — specifics not yet confirmable
How it appears in analytics and logs
A request whose user agent contains a SeekportBot identifier is likely the Seekport crawler fetching a URL — a bot event, not a human visit. Because public documentation is limited, identify it by the token and treat unsourced specifics conservatively.
Diagnostic use case
Recognise Seekport Crawler activity in logs by its identifier and decide robots.txt policy, while treating undocumented specifics with caution.
What WebmasterID can help detect
WebmasterID classifies Seekport crawling server-side as search-crawler activity and shows it separately from human traffic, so its crawl footprint is visible without log parsing.
Common mistakes
- Assuming documented behaviour exists where public docs are sparse.
- Inventing IP ranges to verify the Seekport crawler.
- Counting crawler hits as human sessions.
Privacy and accuracy notes
Identification uses only the user agent — no human identity. WebmasterID records Seekport crawling as a bot event, separate from human analytics.
Related pages
- MojeekBot — independent index crawler
MojeekBot is the crawler for Mojeek, a search engine notable for building and operating its own independent web index rather than reselling another engine's results. Its robots.txt token is MojeekBot. Mojeek documents the crawler, though some specifics are marked partially verified.
- Crawler IP verification methods
Because user-agent strings are trivially copied, the reliable way to confirm a crawler is to check its source. The two documented methods are reverse DNS with a forward-confirm step, and matching the source IP against the engine's published IP ranges. Together they defend against spoofed crawler traffic.
- Bot intelligence
See search-engine crawlers separated from human traffic.
Sources and verification notes
- Seekport — search project (token observed in logs)SeekportBot identifier is observed in logs; comprehensive official docs are limited, so specifics are partially verified.
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.