ForwardQR
ForwardQR is a general-purpose automated agent with no publicly identified operator. The behavior depends entirely on what it is configured to do, so the right response depends on the request pattern, not the user-agent string alone.
Watch what it actually does on your site for a few hours before deciding whether to allow, rate-limit, or block.
If you cannot identify the operator and the traffic is meaningful, treat it as you would any unknown bot: rate-limit, observe, and only block if it misbehaves.
See ForwardQR on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
User-Agent only
Crawl frequency
Variable
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Should I let ForwardQR through?
Watch your logs for a week first. Behavior varies wildly. Observe the request pattern before allow/block decisions.
Does blocking ForwardQR affect my Google rankings?
No. ForwardQR is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.
How do I confirm a request is really from ForwardQR?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be ForwardQR", not "the traffic is genuinely ForwardQR". If you need stronger guarantees, look for a reverse-DNS check or wait for the operator to publish IP ranges.
What's the best way to understand what ForwardQR is doing on my site?
Look at which URLs it hits, how often, and what time of day. The request pattern usually tells you whether it's building an index, watching for a specific change, or trying to pull data in bulk. The User-Agent name alone rarely tells the full story.
Why can't I tell who operates ForwardQR?
Some bots run under generic User-Agent strings or are operated by smaller, less-documented companies. The pragmatic default is to treat unverified operators as untrusted traffic. If volume climbs, log the source IPs and check whether they cluster around a single network or ASN. That'll usually surface who's actually behind it.
What's the cleanest way to control ForwardQR?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.