Search engine crawler
Qwantify
Crawlers that index the web for search engines. Blocking them costs rankings.
Last updated
At a glance
| Category | Search engine crawler |
|---|---|
| User agent match | contains "qwantify" |
| Executes JavaScript | No |
| Respects robots.txt | Generally yes |
| Identity verifiable | No, the name is only a claim |
| IVT class | GIVT (general invalid traffic: declared automation) |
What Qwantify is
Qwantify crawls pages to build a search index. It is declared automation of the most ordinary kind: every site on the web is visited by it, and its traffic should be filtered out of your human numbers, never billed to a campaign and never blocked.
Can the name be trusted?
There is no published way to verify Qwantify: the operator provides no IP ranges and no reverse DNS scheme, so the name in the user agent is only a claim. Any script can send it. TrueVisit still names the traffic, and weighs the claim against behavioral signals instead of trusting it.
Famous crawler names attract impostors, and a confirmed impostor is one of the few verdicts that carries intent. The routine for catching one is in how to spot fake Googlebot traffic.
Should you block it?
Do not block Qwantify. Blocking a search engine crawler removes your pages from its index, and no bandwidth saving is worth that. The real risk with a famous crawler name is the opposite one: scrapers impersonate it to walk past filters, which is why verification matters more than blocking here.
How TrueVisit reports it
Visits from Qwantify appear in your bot report under this exact name, never as an anonymous percentage, and every verdict stores the reason it was reached. Because this client never executes JavaScript, a browser-only tracker cannot see it at all; it is visible through server-side collection, which is how the visits reach your report.