Safe Official docs Data Scrapers

SeekportBot

Operated by Seekport

Quick Facts

User-Agent:
SeekportBot
Category:
Data Scrapers
Operator:
Seekport
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
bot.seekport.com

Confirmed by the operator

Seekport names SeekportBot on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is SeekportBot?

SeekportBot is the web crawler for Seekport, a German search engine.

SeekportBot is the web crawler for Seekport, a German search engine.
SeekportBot is a data aggregation crawler. Unlike search bots or AI crawlers, its purpose is typically to collect content for private datasets, price monitoring, or research. Blocking SeekportBot via robots.txt or at the server level has NO negative SEO impact. If you see excessive crawl volume from this bot in your logs, a hard block is recommended.

What happens if you block SeekportBot?

✅ Minimal Impact - Blocking SeekportBot has no meaningful effect on your search engine rankings or organic traffic.
Generally safe to allow; provides legitimate crawling value.

How to block SeekportBot with robots.txt

<code>User-agent: SeekportBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: SeekportBot Disallow: /
Allow all (robots.txt)
User-agent: SeekportBot Allow: /
Block private only (robots.txt)
User-agent: SeekportBot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block SeekportBot if ($http_user_agent ~* "SeekportBot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block SeekportBot SetEnvIfNoCase User-Agent "SeekportBot" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is SeekportBot safe to allow?

Yes, SeekportBot is a safe and legitimate crawler. It is operated by Seekport, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string SeekportBot is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).
Verify by reverse-DNS lookup: legitimate SeekportBot requests resolve to seekport's domain.

What does SeekportBot do?

Understanding SeekportBot's purpose helps you decide whether to allow or block it.

  • Extracts content, prices, or data from websites
  • May be used for competitive intelligence
  • Often operates without explicit permission
  • Can increase server load and bandwidth usage
  • May violate terms of service or copyright

SeekportBot in context

SeekportBot is a utility crawler operated by Seekport. In plain terms, it harvests pages for a dataset or data product. Our database files it under data scrapers and ranks it Tier 6, the lowest priority: scrapers and tools that offer most sites little or nothing. 37 of the 39 data scrapers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about SeekportBot rests on what you want from Seekport, not on its behaviour. How we rate safety and impact.

How site owners treat SeekportBot

Our robots.txt study of the Tranco top 10,000 did not track SeekportBot as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

SeekportBot's operator does not clearly document how it treats robots.txt. Write the SeekportBot rule anyway, then confirm in your logs that its requests stop.

Seekport crawlers and close alternatives

Seekport runs only this one crawler in our database, so a single User-agent: SeekportBot group controls everything Seekport fetches through it.

Other data scrapers that do the same job (harvests pages for a dataset or data product) include Amazon Kendra from Amazon, ApifyBot from Apify, Barkrowler from Babbar, BLEXBot from WebMeUp, coccocbot-web from Unknown, Crawl4AI from Unknown. Deciding about SeekportBot is usually a decision about the whole group, so check how your file treats these too.

We first recorded SeekportBot on March 17, 2026. Seekport documents it on bot.seekport.com, and we recheck that page before each release.

Which rule SeekportBot actually follows

SeekportBot reads exactly one group in robots.txt, the most specific one that names SeekportBot, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: SeekportBot
Disallow: /drafts/
  1. Find the group. SeekportBot looks for a group naming SeekportBot. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to SeekportBot, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to SeekportBot if the file also has a User-agent: SeekportBot group?

No. Once a group names it, SeekportBot reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking SeekportBot remove your pages from AI answers?

Often, yes. SeekportBot is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: seekportbot the same as User-agent: SeekportBot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Related: how AI engines choose their sources

Should you allow SeekportBot? Decide by situation

Recommended setting for SeekportBot by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itLow stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI trainingBlocking it does not stop training, because SeekportBot is a utility crawler. Block the operator's training crawler instead.
You run an online shopConsider blocking it, especially on price and stock pages that competitors scrape.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check SeekportBot on your own site

  1. Open /robots.txt on your domain and search for SeekportBot. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group SeekportBot follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse SeekportBot even when robots.txt allows it, and that never shows in the file.
  4. Run our AI bot crawlability test to see how SeekportBot and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with SeekportBot

The errors we see most often with SeekportBot in the files and firewalls we test:

  1. Treating SeekportBot as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
  2. Relying on robots.txt alone when SeekportBot is rated caution or aggressive. Back the rule with a server-side block.
  3. Blocking SeekportBot by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check SeekportBot from outside after every change.

Spotting SeekportBot in your logs

robots.txt says what SeekportBot may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "SeekportBot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "SeekportBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the SeekportBot user-agent, so confirm the source before acting on a match:

  • SeekportBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable SeekportBot request with caution.

Frequently Asked Questions

What is the official user-agent string for SeekportBot?
The official user-agent string for SeekportBot is: SeekportBot. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from SeekportBot by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.
Is SeekportBot safe?
Yes, SeekportBot is a safe and legitimate crawler. It is operated by Seekport, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string SeekportBot is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).
Will blocking SeekportBot hurt my SEO?
✅ Minimal Impact - Blocking SeekportBot has no meaningful effect on your search engine rankings or organic traffic.
How do I block SeekportBot in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: SeekportBot
Disallow: /

This instructs SeekportBot not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.
Does SeekportBot respect robots.txt?
Yes - SeekportBot is a well-behaved bot operated by Seekport. It fetches and parses /robots.txt before crawling any page, following RFC 9309.
How do I verify if SeekportBot is crawling my site?
Search your web server access logs for the string SeekportBot (case-insensitive grep: grep -i "SeekportBot" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For SeekportBot specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).
What is the crawl frequency of SeekportBot?
SeekportBot crawls at a moderate rate. If you notice excessive traffic in your logs, you can add a Crawl-delay directive: 
User-agent: SeekportBot
Crawl-delay: 10
(10 second delay between requests).
Can I block SeekportBot from specific pages only?
Yes. Instead of a global Disallow: / you can restrict SeekportBot to specific paths:
User-agent: SeekportBot
Disallow: /private/
Disallow: /staging/
Allow: /

This allows SeekportBot everywhere except the listed paths. Path matching in robots.txt uses prefix matching - Disallow: /private/ blocks /private/page.html but NOT /public/private/.
Is SeekportBot causing high server load?
If SeekportBot is generating excessive requests, you can:
1. Add Crawl-delay: 30 below the User-agent directive in robots.txt.
2. Rate-limit the user-agent via Nginx's limit_req_zone or Apache's mod_ratelimit.
3. Block it outright at Cloudflare WAF with rule: http.user_agent contains "SeekportBot".
4. Use fail2ban to auto-block IPs exceeding request thresholds.

Related Bots

WhatsApp us