Qwantbot is a bot in the search engine crawlers category, operated by Qwant.
Based and designed in Europe, Qwant is the first search engine which protect privacy.
Search engine crawlers index your pages so they can appear in search results. Keep the genuine ones allowed and verify them, because fake search crawlers are one of the most common disguises for scrapers.
Sample user agent strings sent by Qwantbot:
Mozilla/5.0 (compatible; Qwantbot/2.4w; +https://www.qwant.com/)Mozilla/5.0 (compatible; Qwantbot-junior/1.0; +https://www.qwant.com/)Mozilla/5.0 (compatible; Qwantbot-news/2.0; +https://www.qwant.com/)Mozilla/5.0 (compatible; Qwantbot-official/1.0; +https://www.qwant.com/)Mozilla/5.0 (compatible; Qwantbot-wikidata/1.0; +https://www.qwant.com/)Mozilla/5.0 (compatible; Qwantbot-opt/1.0; [email protected])Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
Qwantbot follows robots.txt, so these rules stop it crawling the paths you choose. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: Qwantbot Disallow: /
User-agent: Qwantbot Disallow: /private/ Disallow: /search
User-agent: Qwantbot Allow: /blog/ Disallow: /
User-agent: Qwantbot Allow: / User-agent: * Disallow: /
User-agent: Qwantbot group, Qwantbot ignores your User-agent: * rules, so repeat any that should still apply.Qwantbot from Qwantbot's user agent; check Qwant's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Qwantbot brings search traffic, so keep the real one allowed. Fake Qwantbot requests are a common cover for scrapers, so verify it by network rather than by name.
Transfon Security for publishersSearch crawlers fetch landing pages to check them. Keep Qwantbot allowed, but out of campaign and conversion data.
Transfon Security for advertisersQwantbot indexes products for search results. Allow it, and block impersonators that use its name to scrape prices.
Transfon Security for e-commerceAllow Qwantbot on marketing and docs pages, and keep it off signed-in app pages it cannot use.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows Qwantbot by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
Qwantbot is a bot in the search engine crawlers category, operated by Qwant. Based and designed in Europe, Qwant is the first search engine which protect privacy.
Yes. Qwantbot follows robots.txt, so a Disallow rule for the Qwantbot user agent stops it from crawling the paths you list.
Add "User-agent: Qwantbot" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "Qwantbot" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so Qwantbot may not follow it, and anyone can send Qwantbot's user agent, so a fake Qwantbot ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Search engine crawlers index your pages so they can appear in search results. Keep the genuine ones allowed and verify them, because fake search crawlers are one of the most common disguises for scrapers.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.