Bot intelligence record

Qwantbot

Usually allow

Use the Qwantbot identifier to separate Qwant search indexing traffic from normal visitor requests in server logs.

Search Search Indexing Verified Bot Confidence: Medium Verified: Yes robots.txt: Yes
Operator
Qwant
Family
Qwant
Type
Search
Source type
Verified Directory
Last checked
2026-06-02

User-Agent Pattern

Qwant
Qwantbot
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
User-agent: Qwantbot Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Search indexing, news indexing, and Qwant product-specific crawling.

Record Details

Structured data
Operator
Qwant
Family
Qwant
Type
Search
Purpose
Search Indexing
Identity type
Verified Bot
Confidence
Medium
Last verified
2026-06-02
Last checked
2026-06-02
Source type
Verified Directory
Verification
Validate Qwantbot using documented Qwantbot user-agent variants and source verification before creating allow-list rules.
Spoofing risk
User-agent strings can be spoofed. Verify the request source and published operator documentation before creating hard allow rules.

Notes

Qwantbot is a candidate Botcrawl directory record for Qwant. The primary identifier for log review is Qwantbot.

Identification

  • User-agent pattern: Qwantbot
  • Family: Qwant
  • Type: Search
  • Kind: Crawler

Common use

Search indexing, news indexing, and Qwant product-specific crawling.

Verification and handling

Validate Qwantbot using documented Qwantbot user-agent variants and source verification before creating allow-list rules.

Candidate guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Evidence and Source

  • Validate Qwantbot using documented Qwantbot user-agent variants and source verification before creating allow-list rules.
  • Match `Qwantbot` as a case-insensitive substring in HTTP user-agent logs. Review aliases and full HTTP agent examples where available. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Search indexing, news indexing, and Qwant product-specific crawling.
  • User-agent strings can be spoofed. Verify the request source and published operator documentation before creating hard allow rules.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.