Cheap Traffic: What Gets Cut to Hit the Lowest Price

Cheap traffic is fine when the job only needs a page to load in a real browser and register in your analytics, from a country you picked. It's the wrong buy when the job needs anything a person supplies: a search, a decision, a purchase, a form, an ad click. No price level makes that second list cheap, because the cost is the person.

Four things worth holding onto before you compare offers:

• A price is a sum of inputs. A lower price usually means fewer inputs, a smaller unit, or a seller not delivering what the listing says.
• The cheapest traffic that survives into your analytics runs in a real browser. Strip the browser out and visits either never run your analytics tag or get discarded as known bots before your reports are built.
• "Real human" at an automated price is arithmetic you can check. The attention-hour test below takes about a minute.
• No traffic, at any price, comes with a ranking promise. Anyone offering one is telling you something they can't know.

One note on the word itself. Search for cheap traffic and several of the top results come from ad networks selling popunder, push and banner placements. That's a different purchase from the one this post covers. Those visitors are people, and the input cut is usually intent: a popunder, for example, opens your page for someone who clicked on something else. Everything below is about bought visits, but the same question works on both. Which input did the low price remove?

A seller's price per visit is the cost of everything that goes into one visit, plus margin, divided by whatever unit they chose to quote. Remove an input and the price can fall. These are the inputs, roughly in the order they disappear as prices drop.

Every row is a real saving for the seller, and almost none of them shows up on a sales page. That's the trouble with shopping on price alone: the listing shows you a number of visits and hides the bundle.

There's also a way to look cheaper that costs nothing to deliver, which is to shrink the unit. Our Website Traffic MINI plan is 60,000 page views or 20,000 unique visitors for the same $9.99, because each visitor views up to three pages. Quoted per 1,000 page views, that's about $0.17. Quoted per 1,000 visitors, it's about $0.50. Same traffic, a headline price three times smaller. Before you compare two sellers, convert both to cost per 1,000 visitors. Our guide to buying website traffic without wasting budget covers the other places spend leaks once the units line up.

Our four products sit on different rungs of that ladder, which makes them a useful way to see what each step up actually buys. The figures below are list prices as published on 10 September 2026, before coupons or bonus-credit offers, divided by the units each plan includes.

Three things fall out of it.

Behavior costs exactly 3x. Realistic Traffic is three times the Website Traffic price on every paid tier, with volume held identical. That multiple is the price of a visit doing work on the page instead of loading it and waiting. Our Website Traffic vs Realistic Traffic comparison shows which reports that extra work can and can't move.

A person costs roughly 250 to 1,300 times more. One SERP click at DIAMOND's $0.12 is about 250 times the $0.0005 of a MINI automated visitor. One click at LITE's $0.39 is about 1,300 times the $0.0003 of a SMALL visitor. No automation trick closes that gap, because the missing input is the person.

Volume stops lowering the unit price early. Website Traffic reaches about $0.10 per 1,000 page views at SMALL and stays there all the way up to ULTIMATE. A bigger plan buys more traffic, not cheaper traffic, so if the lowest unit price is the goal, the $29.99 plan already has it.

At the very bottom, the free tier is the cheapest traffic of all, and its spec tells you what paid for it: visits capped at 30 seconds and no country choice.

Each of these is a legitimate saving for the seller. Some won't matter to your job at all. Two can cost you more than the traffic did.

Human attention has a cost floor. Machine time barely does. So turn any traffic offer into a price per hour of claimed attention, and see which side of the floor it lands on. You need a calculator and about a minute.

price per attention-hour = price / (visits × minutes per visit / 60)

Here it is on an example listing, with numbers invented for illustration: 10,000 real human visitors from the US, staying 2 minutes each, for $20.

1. Claimed attention: 10,000 visits × 2 minutes = 20,000 minutes, or about 333 hours.
2. Price per claimed hour: $20 / 333 = about $0.06.

Now compare that with what people's time costs. The US federal minimum wage is $7.25 an hour (US Department of Labor), so the listing implies American visitors working for under 1% of it. Global crowd work, which pays far less, doesn't close the gap either: a CHI 2018 study of 2,676 Amazon Mechanical Turk workers found a median of roughly $2 an hour (Hara et al.). Six cents is about a thirtieth of that. The listing can't be describing people doing what it says. The visitors are automated, the two minutes aren't real, or the visitors aren't in the US.

Run the same test on us:

The test can't prove a click is human. A seller could charge a human price for bot traffic, which is what the Search Console and server log checks in the worked example are for. What it does reliably is rule offers out: when the answer comes back in cents per hour, the listing is selling machine time, whatever the sales page calls it.

Cheap traffic isn't a bad product. It's a product with specific inputs missing, and plenty of jobs never needed them. Name the job, list the inputs it depends on, then buy the cheapest thing that still has them.

One job deserves its own warning. Don't use cheap traffic to make a site look busier for somebody else's decision: a buyer looking at a site for sale, an advertiser pricing a placement, an investor reading your analytics. They are relying on those numbers as a record, and padding them with bought visits is misrepresentation, whatever the traffic cost.

Whoever sold you the traffic, don't judge it on the seller's dashboard. Judge it in the three places the seller can't write to: your server logs, GA4 and Search Console. This design fits inside the smallest paid plan.

Step 1. Pick a quiet test page. Use a real page that gets little traffic of its own, such as an unlinked path like /traffic-test/. Record its daily sessions and its Search Console clicks for the previous 14 days as the baseline. A quiet page makes the bought visits easy to isolate.

Step 2. Order narrowly. One URL, one country, one traffic type. If you're testing an "organic" claim, pick organic. Write down exactly what you ordered: visits per day, visit length, country.

Step 3. Read at 24 hours, then again at three days. Pull the same three readings for the same page and dates both times. The first catches a seller that isn't delivering while you can still act on it. The second is the one to judge on.

• Server or CDN logs: count requests for the test path, excluding images, scripts and other assets.
• GA4: open Explore, then Free form. Add the dimensions Landing page + query string, Session source / medium and Country, and the metrics Sessions and Average engagement time per session. Filter Landing page + query string to contain /traffic-test/.
• Search Console: Performance, then Search results. Add a Page filter for the test URL, set the same dates, and read Clicks.

Step 4. Compare against the order. The table shows two illustrative outcomes. Every number in it is invented to show the pattern, not a measured result.

Example A delivered what automated traffic can deliver: requests close to the order, sessions close to the requests, visit length in line with the settings, and zero Search Console clicks because no search ran. That last row is correct, not a failure, and it's what every automated product should show. Example B delivered requests that mostly never ran the analytics tag or were thrown out as known bots, so the seller can point at its logs while your reports show almost nothing.

Time the first reading to your refund terms. Our delivery policy says traffic starts between 30 minutes and 6 hours after a campaign is created, and asks you to check GA4 after 24 hours. That 24-hour reading is the one that protects your money: MINI's published daily speed is 500 to 600, so after one day only a few percent of the plan has gone out, inside both the 72-hour refund window and the 10% delivery limit. For the full audit, including referrers, the shape of visit durations and device mix, see how to spot bought traffic in analytics.

The same eight inputs, held against our own $9.99 plan:

So would we sell you MINI to lift conversions, earn ad revenue or climb the rankings? No. It doesn't have the inputs for any of those, and no price we could charge would add them. What it does is put real-browser visits from the countries you choose into your analytics for $9.99, and the unit price drops to our lowest, about $0.10 per 1,000 page views, from the $29.99 plan up. If that's the job, it's the right buy, and the Website Traffic plans list every tier.

Run this against any offer, ours included:

1. Write down the job and the report you'll judge it in. If that report is sales, leads, ad revenue or rankings, stop here.
2. Convert the price to cost per 1,000 visitors, not page views or hits.
3. Run the attention-hour test on any "real human" claim.
4. Ask whether visits run in a real browser, and whether they identify as a known bot.
5. Ask where the traffic's IP addresses come from, and whether you'll be asked to lower your bot protection.
6. If "organic" is on the menu, ask whether a search actually runs, then verify it in Search Console anyway.
7. If your pages carry ads, ask how ad requests are handled. No clear mechanism, no purchase.
8. Read the refund and delivery terms, and note the date the refund window closes.
9. Start with the smallest plan on a quiet page, and read logs, GA4 and Search Console before scaling.