What is QueryN Metasearch?

Monitor it before deciding. QueryN Metasearch has not been categorized, so there is no established behavior profile to rely on. Review which pages it requests and how often, then block it if the traffic is excessive or targets content you would not share with an unknown bot. For context, 1% of the top websites we track currently have robots.txt rules for QueryN Metasearch.

Yes. QueryN Metasearch is expected to follow robots.txt directives, so a disallow rule is the appropriate first step. Automatic Robots.txt can add and maintain that rule, while Agent Analytics lets you verify whether QueryN Metasearch respects it.

Unknown. QueryN Metasearch has no established scope, so monitor what it requests. Repeated attempts to reach login or admin paths are a reason to investigate or block it.

QueryN Metasearch's purpose has not yet been identified. Until it is categorized or its operator explains it, its behavior on your site is the best 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". Record the paths it requests and how often because no reliable behavior profile exists yet. Because QueryN Metasearch does not publish a verification method, any client can claim its identity and a log match is only a clue.