Is DeepSeekBot in my logs really DeepSeek?

There is no way to prove it. DeepSeek publishes neither an address list nor a reverse DNS record for this crawler, so the user agent is the only evidence and anyone can send it. We record the visit as an unverified claim rather than presenting it as confirmed.

How do I match DeepSeekBot in my own logs?

Match the token as a substring of the user-agent header, case-insensitively. DeepSeek adds and changes the version and product text around it without notice, so a rule pinned to the whole header stops working the first time they bump a version number, while a rule matching DeepSeekBot keeps working.

Does DeepSeekBot run JavaScript?

No. It requests the HTML and leaves. That is why a browser-based analytics tag never records these visits: the tag is JavaScript, and nothing runs it. Seeing this crawler at all requires reading it server-side.

Why is DeepSeekBot counted as Training?

Because that is what the fetch is for. The four categories separate what a crawler came to do rather than who sent it, so a visit from DeepSeek moves this row and not the others. Where an operator publishes nothing to settle the question, we say so on the page rather than choosing quietly.

Why does DeepSeekBot not show up in Google Analytics?

Google Analytics runs in the browser. This crawler never opens a browser — it requests the HTML, reads it, and leaves, so the tracking script is never executed and no event is ever sent. Every browser-based analytics tool has the same blind spot, which is why crawler traffic has to be read from the server side to be seen at all.

Why can a DeepSeekBot visit not be verified?

DeepSeek publishes neither a machine-readable list of the addresses its crawler uses nor a reverse DNS record pointing back at itself. With neither, the user-agent header is the only evidence, and anyone can send it. Rather than showing a confidence we cannot support, the visit is recorded as an unverified claim — which is also the honest answer to give anyone asking how much of your AI traffic is real.

AI crawlers

DeepSeekBot

Also known as DeepSeek DeepSeekBot

3 min read · updated 2026-09-09

Definition

DeepSeekBot is DeepSeek's crawler for collecting training data. DeepSeek's crawler. DeepSeek fetched your page.

For the reference card — DeepSeekBot in the crawler directory.

What DeepSeekBot is

DeepSeek publishes no crawler documentation and no address ranges. The token is recognised from community lists and observed traffic rather than from anything the company has stated.

On this site DeepSeekBot is counted as training, which is the row it appears in on your dashboard. The category matters because it decides which number moves when this crawler visits, and the four are reported separately for exactly that reason.

What its traffic looks like

Broad and slow: many pages, few repeats, spread over days or weeks rather than concentrated. Training crawls tend to want everything once, so the long tail of a site sees traffic it never gets from search — old posts, deep archive pages, anything reachable by a link. Bandwidth is the usual reason people notice these at all.

How it is verified

DeepSeek publishes neither a machine-readable list of the addresses this crawler uses nor a reverse DNS record pointing back at itself. The user-agent header is therefore the only evidence, and anyone can send it — so a visit is recorded as an unverified claim rather than as a confirmed fetch.

That is not a gap in the measurement so much as an honest ceiling. A report that showed these as verified would be inventing a confidence nobody can support, and the number it produced would be the first thing to fall apart when somebody asked where it came from.

If you block it

DeepSeek stops collecting your pages as training material. Nothing about how you appear in search or in live answers changes — those are separate crawlers with separate rules.

Nothing you see today changes if you block this. Training crawls feed models that ship months later, so the decision is about whether your work becomes part of a commercial model, not about this quarter's traffic.

The honest counter-argument is that being in the training data is part of how a model comes to mention you at all. There is no measurement that settles this either way — anyone who tells you there is has not looked — so it is a decision about your terms rather than about your numbers.

Questions

Is DeepSeekBot in my logs really DeepSeek?: There is no way to prove it. DeepSeek publishes neither an address list nor a reverse DNS record for this crawler, so the user agent is the only evidence and anyone can send it. We record the visit as an unverified claim rather than presenting it as confirmed.
How do I match DeepSeekBot in my own logs?: Match the token as a substring of the user-agent header, case-insensitively. DeepSeek adds and changes the version and product text around it without notice, so a rule pinned to the whole header stops working the first time they bump a version number, while a rule matching DeepSeekBot keeps working.
Does DeepSeekBot run JavaScript?: No. It requests the HTML and leaves. That is why a browser-based analytics tag never records these visits: the tag is JavaScript, and nothing runs it. Seeing this crawler at all requires reading it server-side.
Why is DeepSeekBot counted as Training?: Because that is what the fetch is for. The four categories separate what a crawler came to do rather than who sent it, so a visit from DeepSeek moves this row and not the others. Where an operator publishes nothing to settle the question, we say so on the page rather than choosing quietly.
Why does DeepSeekBot not show up in Google Analytics?: Google Analytics runs in the browser. This crawler never opens a browser — it requests the HTML, reads it, and leaves, so the tracking script is never executed and no event is ever sent. Every browser-based analytics tool has the same blind spot, which is why crawler traffic has to be read from the server side to be seen at all.
Why can a DeepSeekBot visit not be verified?: DeepSeek publishes neither a machine-readable list of the addresses its crawler uses nor a reverse DNS record pointing back at itself. With neither, the user-agent header is the only evidence, and anyone can send it. Rather than showing a confidence we cannot support, the visit is recorded as an unverified claim — which is also the honest answer to give anyone asking how much of your AI traffic is real.

See whether DeepSeekBot is reaching your pages.

AI crawlers take your HTML and leave without running a line of JavaScript, so a browser tag records nothing. TrueStat reads them server-side, checks each address against what the operator publishes, and shows you which pages were fetched — including the ones that returned a 404.

Start tracking All terms