🤖 Overview

The Miva crawler is operated by Miva, Inc., the provider of the Miva Merchant e‑commerce platform. Its primary purpose is to index product catalog data, pricing, and inventory information from publicly accessible Miva‑powered stores to feed the platform’s internal search engine, product recommendation engine, and analytics dashboards. First documented in Miva’s developer documentation around 2015, the bot is also used to validate site health and detect broken links for store owners.

🌐 Technical Behavior

The Miva crawler issues GET and HEAD requests over HTTP/1.1 and HTTPS, typically targeting product detail pages, category listings, and XML sitemaps. Crawl frequency is configurable per store but often reaches 10–20 requests per minute during peak indexing cycles. IP addresses are drawn from Miva’s own cloud infrastructure (ASN AS39832), with ranges such as 208.64.120.0/24 and 209.217.0.0/16 reported in server logs. The bot respects Crawl-Delay directives in robots.txt and slows its pace if a site returns HTTP 503 or 429 status codes.

📋 robots.txt Compliance

According to Miva’s official documentation (available at docs.miva.com), the crawler strictly honors Disallow directives and will not access any path listed under a User-agent: Miva block. Evidence from multiple store operator forums confirms that the bot stops crawling after encountering a Disallow rule and does not attempt to re‑crawl disallowed paths unless the directive is removed.

🔍 Detection Indicators

The primary User‑Agent string is Miva (or MivaBot/2.0). Additional identifiers include the header X-Forwarded-For with IPs from the Miva ASN and a User-Agent: Mozilla/5.0 (compatible; Miva; +https://www.miva.com/bot) variant seen in some crawls. The bot sends a From header containing [email protected] as a contact address.

📊 Data Usage

Collected data—such as product titles, descriptions, prices, stock levels, and images—is used exclusively within Miva’s ecosystem: to power the Miva Merchant store‑front search, generate “related product” suggestions, and produce weekly analytics reports for store owners. No data is sold to third parties or used for external AI training, per Miva’s privacy policy (miva.com/privacy).

⚙️ Rate Limiting Policy

Because the Miva crawler can send a burst of requests when re‑indexing a large catalog, rate‑limiting is recommended to protect server resources. A threshold of 30 requests per minute from the Miva IP range is a standard defensive measure, balancing legitimate indexing with server stability.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.