Which user-agent strings identify Omnisend?

The following user-agent strings identify Omnisend: Omnisend/1.0.

Does Omnisend respect robots.txt rules?

According to official documentation, Omnisend does not respect robots.txt rules.

How can I verify Omnisend traffic with live traffic data?

You can verify Omnisend requests by checking your server access logs for the documented user-agent strings. For accurate verification, correlate user-agent patterns with IP ranges or verification methods provided by Omnisend.

What is Omnisend?

Direct Answer: Omnisend bot checks integration in WooCommerce shops and Shopify, operated by Omnisend.

Operator: Omnisend Type: Other Bot Purpose: Checking Omnisend integration in e-commerce platforms

The Omnisend bot is used for checking Omnisend integration in WooCommerce shops and Shopify. It is operated by Omnisend. The bot's user-agent is Omnisend/1.0. It does not follow robots.txt from the database.

User-Agent Identification

The following user-agent strings identify Omnisend in your live traffic data:

Omnisend/1.0

robots.txt Rules for Omnisend

Respects robots.txt: No

This bot does not commit to following robots.txt

Omnisend does not officially follow robots.txt directives. The only reliable way to control access is through server-side blocking (IP filtering, user-agent rules in your web server config) combined with log monitoring to verify effectiveness.

Need continuous verification across 500+ bots? Can AI See It automates this.

Crawl Behavior

Frequency:Not Documented

Request Pattern:Not Documented

Crawl Activity Index

Relative crawl activity for Omnisend over the past 28 days. Higher values indicate increased crawling intensity compared to the period baseline.

View recent activity data (last 7 days)

Date	Activity Index
Mar 28, 2026	16.3
Mar 29, 2026	19.2
Mar 30, 2026	19.5
Mar 31, 2026	18.4
Apr 1, 2026	19.9
Apr 2, 2026	18.3
Apr 3, 2026	16.3

Source: Cloudflare Radar

Why track Omnisend traffic?

Identify and classify unknown crawler activity. Omnisend may appear in your live traffic data with varying frequency. Tracking its behavior helps you decide whether to allow, throttle, or block it based on actual data.

Protect your crawl budget. Every bot request consumes server resources. Understanding what Omnisend crawls helps you prioritize the crawlers that matter.

Log Verification

To verify Omnisend traffic in your live traffic data:

Search access logs for the user-agent strings listed above
Check if the IP addresses match documented ranges (if provided by Omnisend)
Verify the crawl pattern matches documented behavior
Use reverse DNS lookup for additional verification if available

Note: Observed behavior in production environments may differ from official documentation. Live traffic monitoring provides the only reliable verification of actual bot behavior.

Undocumented Information

The following information is not officially documented for Omnisend:

crawl frequency
request pattern
JavaScript rendering
verification URL

Official Documentation

View Official Omnisend Documentation →

Information sourced from official documentation. Content generated with AI assistance.