What is QueryN Metasearch?

Watch it first. QueryN Metasearch has not been categorized yet, so there is no track record to lean on. Check which pages it requests and how often, and block it if the traffic is heavy or pointed at content you would not give an unknown bot. For comparison, 1% of the top websites we track already have robots.txt rules for QueryN Metasearch.

Yes. QueryN Metasearch is expected to follow robots.txt rules, so a disallow rule is the right first move. Automatic Robots.txt adds and maintains that rule for you, and Agent Analytics confirms QueryN Metasearch actually follows it.

Unknown. QueryN Metasearch has no documented scope, so watch what it actually requests. Repeated hits on login or admin paths are the signal to block it.

Nobody knows yet. QueryN Metasearch is undocumented, so until its operator explains it, its behavior on your site is the only evidence of its intent.

Agent Analytics tracks QueryN Metasearch visits in real time alongside every other known AI agent, crawler, and scraper. You can also check your server logs for requests whose user agent string contains "QueryN Metasearch". Log the paths it requests and how often, since nothing about it is documented. Keep in mind that QueryN Metasearch doesn't publish a verification method, so any client can claim its user agent string and a log match is a hint rather than proof.