skimbot
Bot User-Agent:skimbot
🤖 Overview
SkimBot is a web crawler operated by Skimlinks (a Sovrn company), designed to automatically identify and convert product links within publisher content into affiliate (monetized) links. It was first introduced as part of Skimlinks' publisher monetization platform, which enables websites to earn commissions from e‑commerce referrals without manual affiliate tagging. The bot scans web pages in real time and on a scheduled basis to detect hyperlinks pointing to merchant sites, then rewrites them using Skimlinks’ proprietary affiliate tracking system. Its primary purpose is commercial link monetization, not search indexing or AI training.
🌐 Technical Behavior
SkimBot performs both initial full‑page crawls and subsequent re‑crawls to detect changes in existing links. It typically requests pages using standard HTTP/1.1 and HTTPS protocols, with a default crawl frequency that varies by publisher agreement but is generally moderate (e.g., a few requests per minute per domain). The bot’s IP ranges are documented in Skimlinks’ official support materials; they publish a list of IPv4 addresses (e.g., 104.18.0.0/16 and 172.64.0.0/16 are often cited, though exact ranges may change). SkimBot follows the robots.txt directives it encounters and respects Crawl‑Delay instructions when present. It also parses HTML and JavaScript‑rendered content to find links that are dynamically inserted, but it does not execute complex JavaScript in a full browser environment — it relies on server‑side parsing of the final DOM. The bot identifies itself via a custom User‑Agent string and typically does not spoof other crawlers.
📋 robots.txt Compliance
According to Skimlinks’ official documentation (skimlinks.com/crawler) and public forum posts, SkimBot fully honors the robots.txt file on a per‑domain basis. If a publisher denies access to certain paths via Disallow, the bot will not request those resources. However, because Skimlinks’ business model relies on crawling the entire page to detect product links, some publishers choose to allow the bot only on specific sections (e.g., /articles/) while blocking it on administrative or dynamic pages. Compliance is verified by Skimlinks’ own technical team, and they recommend that site owners test their robots.txt configuration to ensure desired behavior.
🔍 Detection Indicators
The primary User‑Agent string is SkimBot/1.0 (or variants like SkimBot/2.0), and it also announces itself via the HTTP From header when enabled. Additional identifying headers include X‑Forwarded‑For and a custom Via header in some deployments. Behavioral fingerprints include a consistently high request rate that spikes after new content is published, and a tendency to request pages in the same order as a sitemap (if provided). Logs will show very low variance in inter‑request intervals compared to human traffic. Skimlinks also provides a public IP list and a verification endpoint on their website that allows site owners to confirm a request actually originates from SkimBot.
📊 Data Usage
Collected data is used solely for affiliate link monetization: SkimBot scans the content of a page to extract existing merchant links (e.g., Amazon, eBay, etc.) and then rewrites them with Skimlinks tracking parameters so that purchase commissions are credited to the publisher. The bot does not store or repurpose the text, images, or user‑generated content for any other purpose, and it does not feed the data into AI training or general indexing. All processed link data is kept temporarily for deduplication and reporting purposes, as described in Skimlinks’ privacy policy (skimlinks.com/privacy).
⚙️ Rate Limiting Policy
Although SkimBot is a legitimate and compliant crawler, it can be aggressive on high‑traffic publisher sites where every page with product links is visited frequently. Rate‑limiting is warranted to prevent the bot from overloading server resources when its crawl tempo exceeds the site’s available bandwidth or connection limits. Implementing a threshold‑based block (e.g., after exceeding a configurable request count per minute) is a standard defensive measure that preserves site performance without malicious intent.
Similar Threats
53% of Web Traffic Is Bots in 2026
— Imperva Bad Bot Report 2026
How much of your traffic is automated? Get your personal bot traffic report and see exactly what's hitting your server — completely free.
📊 Get My Bot ReportSign up in seconds · No card required
ⓘ 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.