Bot Traffic IndexThe bot problem, quantified

Sep 15, 2026 - Bot Traffic Index

The Economics of Inventory Bots: Who Pays When Bots Buy First

On paper, a sellout is a sellout. If bots clear your limited release in ninety seconds, the revenue looks identical to a human sellout. The damage shows up everywhere except the top line.

The real costs

Customer trust. Genuine shoppers who repeatedly lose drops to bots learn that your store is not worth trying. That is a churn event that never appears in churn reporting. Data quality. Bot purchases pollute customer records, sizing curves, and demand forecasts - you start planning inventory for a buyer mix that does not exist. Support load. Drops followed by waves of 'order canceled' and 'why did this sell out' tickets cost real hours. Marketplace leakage. Your product immediately appears on resale platforms at a markup, training your best customers to shop there instead.

Why simple defenses fail

Rate limits and CAPTCHAs catch crude bots and frustrate real customers at exactly the wrong moment - during the drop. Modern purchasing bots route through residential proxies, rotate device fingerprints, and solve challenges faster than humans. Queue systems help fairness but do not stop automated buyers from joining the queue.

What works

The effective stack is behavioral: detection at the network edge that scores sessions on signals bots cannot cheaply fake, applied before the storefront ever sees the request. Blocking scraper and hoarder traffic at the edge also restores analytics accuracy as a side effect - fake sessions never reach your pixels. Post-purchase order screening is the second line, not the first.

The takeaway

Inventory bots are not a security footnote; they are a customer-experience and data-integrity problem with a revenue-shaped hole in the middle. Measure them, block them at the edge where possible, and stop counting bot demand in your forecasts.

Bot Traffic Spikes After a Press Mention: How to Read the Surge

A press mention brings humans and bots together. The bots arrive first, in larger numbers, and they distort every metric the mention was supposed to improve.

A store gets mentioned in a gift guide. Traffic triples overnight, the team celebrates, and the analytics show a bounce rate of 90 percent and a conversion rate near zero. The humans came, but they were outnumbered. The bots that scrape gift guides, monitor prices, and probe new links arrived within minutes of publication, and they are most of the spike.

A press mention is a bot magnet, and the surge is the wrong time to read the analytics at face value. The bots come first because they are automated, and they come in larger numbers because there are more of them than there are readers. The job is to separate the two before drawing any conclusion about the mention.

Why bots arrive first

Gift guides, press pages, and product roundups are monitored continuously by scrapers, price trackers, and affiliate checkers. The moment a new link appears, those systems fetch it, and they fetch it from many IP addresses at once, which is why the spike looks like a flood rather than a trickle. Human readers arrive over hours, as the article is shared and discovered. Bots arrive in the first minutes, because they never sleep.

The traffic pattern gives it away. Bot traffic in a press spike is concentrated in the first hour, comes from data centre IP ranges, requests the page and little else, and never reaches the checkout. Human traffic builds over the day, comes from residential networks, and moves through the site. A spike with no add-to-carts and no checkouts is a bot spike, whatever the session count says.

Reading the surge without fooling yourself

Split the spike by behaviour, not by volume. Sessions that viewed one page and left in under five seconds are mostly bots. Sessions that viewed a product, added to cart, or reached checkout are humans, and they are the only ones that matter for the question the team actually asked, which is whether the mention sold anything.

Check the referrer and the user agent together. A surge from the publication's domain, with a mix of browsers and devices, is human. A surge with no referrer, or a referrer that does not match the publication, is not. The invalid traffic guidelines from the Media Rating Council draw the same line: general invalid traffic, including known scrapers and data centre traffic, should be filtered before reporting, and sophisticated invalid traffic needs behavioural analysis.

What to do during the spike

Do not make budget decisions on the spike. A press mention that triples traffic and sells nothing in the first hour has not failed. It has been measured badly. Wait a day, filter the bot sessions, and then look at the human numbers: sessions from the publication, time on site, add-to-carts, and orders. Those are the numbers the mention should be judged on.

Use the spike to set a baseline. Record the bot share of the surge, the IP ranges involved, and the request patterns, so the next press mention can be compared against it. A store that has been mentioned before has a bot baseline, and a store with a baseline can spot the next surge for what it is within an hour, instead of celebrating a number that was never real.

Related reading: Bot Traffic Index, Answers, Glossary.

Frequently asked questions

Why does bot traffic spike after a press mention?

Gift guides and press pages are monitored continuously by scrapers, price trackers, and affiliate checkers. They fetch a new link within minutes of publication, from many IP addresses at once, while human readers arrive over hours. The bots are most of the spike.

How do I tell bot traffic from human traffic in a spike?

Split by behaviour. Bot sessions usually view one page, leave in under five seconds, and never reach the checkout. Human sessions move through the site, add to cart, and come from the publication's domain with a mix of browsers and devices.

Should I judge a press mention by its traffic spike?

No, not on the first day. Filter the bot sessions first, then look at the human numbers: sessions from the publication, time on site, add-to-carts, and orders. A spike with no add-to-carts is a bot spike, whatever the session count says.

What is the Media Rating Council standard for invalid traffic?

The MRC guidelines split invalid traffic into general invalid traffic, such as known scrapers and data centre traffic, which should be filtered before reporting, and sophisticated invalid traffic, which needs behavioural analysis to detect.

Frequently asked questions

Who pays when bots buy limited stock first?

Almost everyone except the bot operator: genuine customers pay resale prices or miss out, the store pays in support, returns, and reputation, and the market pays as launch data and pricing signals fill with automated demand.

Why do stores tolerate inventory bots for so long?

Because bot purchases still record as sales, and the costs land in other budgets: support time, chargebacks, customer anger, and distorted demand data. The revenue is visible immediately. The costs are diffuse and delayed.

What is the real cost beyond the sold out product?

Corrupted information. Launches read as more popular than they are, waitlists inflate, and stock and pricing decisions get made on demand that was never human. The store optimises for an audience of scripts.

What actually reduces inventory bot economics?

Raising the cost per attempt: verified accounts for limited drops, queues that reward patience over speed, per customer limits enforced across identities, and detection aimed at behaviour. Defences work when they make botting unprofitable, not merely harder.