DoubleVerify
DoubleVerify is a brand-safety and ad-quality verifier operated by Doubleverify. It checks that ads render in safe contexts, are visible to humans, and meet creative-quality requirements.
Ad verification is allowed by default in most ad stacks. Blocking it can cause ads to be marked unverified, which reduces fill rate and lowers the price your inventory sells for.
If you are a publisher, allow it. If you are not running ads, you should rarely see meaningful volume.
See DoubleVerify 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
Doubleverify runs 3 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Should I let DoubleVerify through?
In most cases, yes. Required for ad serving and brand safety. Blocking causes fill-rate and revenue drops. If volume gets noisy, rate-limit it before you block it outright.
Does blocking DoubleVerify affect my Google rankings?
No. DoubleVerify 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 DoubleVerify?
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 DoubleVerify", not "the traffic is genuinely DoubleVerify". If you need stronger guarantees, look for a reverse-DNS check or wait for Doubleverify to publish IP ranges.
What's the best way to understand what DoubleVerify 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.
How is DoubleVerify different from Doubleverify's other bots?
Doubleverify splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Doubleverify family above to see which ones actually matter for your site.
What's the cleanest way to control DoubleVerify?
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.