Coupons.com
Coupons.com is a catalog crawler operated by Quotient. It indexes product feeds, category pages, and product detail pages so they can be surfaced inside shopping experiences and AI-powered commerce assistants.
Allowing it is one of the main ways your products become discoverable inside agentic commerce flows. As AI shopping agents grow, this category of crawler will matter more, not less.
Blocking is fine for sites that are not retail, but think twice if you sell products online.
See Coupons.com 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 Coupons.com through?
In most cases, yes. Catalog crawlers feed AI shopping experiences. If you sell online, you want to be in their index. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Coupons.com affect my Google rankings?
No. Coupons.com 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 Coupons.com?
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 Coupons.com", not "the traffic is genuinely Coupons.com". If you need stronger guarantees, look for a reverse-DNS check or wait for Quotient to publish IP ranges.
Will Coupons.com change how my products surface in AI search?
If Quotient runs an AI shopping surface, then yes. The crawler builds the catalog those experiences pull from. Blocking it means your products won't appear when users ask the AI to shop on their behalf.
What's the cleanest way to control Coupons.com?
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.