SeekportBot
SafeUser-agent: SeekportBot
Category: Data Scrapers
SEO impact if blocked: 2/10
Seekport
1 crawler operated by Seekport
Who Seekport is, for site owners
Seekport operates 1 crawler in our directory, filed under Data Scrapers. Its crawl behaviour is rated safe.
Blocking Seekport carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Seekport: Generally safe to allow; provides legitimate crawling value.
Seekport at a glance
| Operator | Seekport |
|---|---|
| Crawler in directory | 1 |
| Categories | Data Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
| Official crawler docs | Seekport crawler documentation |
Crawler operated by Seekport
What Seekport's crawlers are for
Seekport runs 1 crawler in our database. Grouped by the job each one does:
- a utility crawler:
SeekportBot
The highest-priority token is Tier 6. That makes Seekport a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat Seekport
None of Seekport's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
Writing one policy for Seekport
A robots.txt file cannot say "Seekport"; it can only name Seekport's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Seekport fetches through it
User-agent: SeekportBot
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the AI crawler checker after any change to see the result for each Seekport token, including firewall refusals.
Test yourself: does User-agent: Seekport block all of Seekport's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token SeekportBot.
Test yourself: if you block one Seekport token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Seekport crawler, explained
A one-paragraph brief for every Seekport token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- SeekportBot (
SeekportBot, Tier 6): a utility crawler that harvests pages for a dataset or data product. Rated safe. 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. Not tracked in our robots.txt study.
Common mistakes with Seekport's crawlers
The errors we see most often with Seekport's crawlers in the files and firewalls we test:
- Treating Seekport's crawlers as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
- Relying on robots.txt alone when Seekport's crawlers is rated caution or aggressive. Back the rule with a server-side block.
- Blocking Seekport's crawlers by IP alone. Ranges change; match the token and verify with logs.
All three hide inside a file that looks correct, so check Seekport's crawlers from outside after every change.
What our own data shows about Seekport
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Seekport's marketing. Seekport has one token in our database, so the whole picture fits in one place.
SeekportBot in our records
We first recorded SeekportBot on March 17, 2026. Seekport documents it on bot.seekport.com, and we recheck that page before each release. No file in our top-10,000 scans names SeekportBot, so any rule you write for it puts you ahead of almost every large site.
Among the 39 data scrapers in our database, SeekportBot sits 34th by priority (Tier 6), level with Amazon Kendra, ApifyBot, Barkrowler, BLEXBot. 29 of the 39 share its safe rating. Other operators with a crawler that harvests pages for a dataset or data product: FirecrawlAgent (Firecrawl, Tier 2), iaskspider (iAsk, Tier 2), NovaAct (Amazon, Tier 2), CloudflareBrowserRenderingCrawler (Cloudflare, Tier 3), Amazon Kendra (Amazon, Tier 6). A policy for SeekportBot is usually a policy for these too.
A decision record for SeekportBot
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the SeekportBot entry reads:
- Operator and job: Seekport; it harvests pages for a dataset or data product.
- Priority and behaviour: Tier 6, rated safe, blocking impact low.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: 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.
User-agent: SeekportBot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the SeekportBot entry once a quarter, or when Seekport publishes a new token next to it.
Checking SeekportBot on your own site
Because Seekport runs only SeekportBot in our records, one check covers the whole operator. Search your access logs for the string SeekportBot over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. Match the requests against what Seekport publishes about the crawler, since that page is the only authority on its behaviour. A Tier 6 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.
How top sites treat Seekport's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Seekport's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Seekport's crawlers too.
More questions about Seekport
- Will blocking Seekport affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Seekport's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Seekport?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Seekport on some sections and block it on others?
- Yes. Inside the group for
SeekportBot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Seekport delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Seekport offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Seekport?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Seekport review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI bot checker to see the outcome from outside, including any firewall layer.
How to block or allow Seekport in robots.txt
This rule covers the single crawler Seekport operates. Add it to the robots.txt file at the root of your domain.
Block Seekport completely
User-agent: SeekportBot
Disallow: /
Allow Seekport explicitly
User-agent: SeekportBot
Allow: /
These Seekport rules ask; they do not enforce. If a Seekport token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about Seekport
What crawler does Seekport run?
Seekport operates 1 crawler in our directory: SeekportBot (user-agent SeekportBot).
Should I block Seekport?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block Seekport in robots.txt?
Add the following to robots.txt at your domain root: User-agent: SeekportBot then Disallow: /.
Does blocking Seekport hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking Seekport does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.