Buy Website Hits? What Traffic Sellers Actually Count

A hit, in the sense your server counts it, is any single request: the page, then every image, script, stylesheet and font it loads from you. So a hit counter mostly measures how many files your pages need, and you almost never want to pay for that. When a seller says hits, it can mean visits, page views, timed views or bare requests, and each lands differently in your reports. A bare request leaves one line in your log and nothing in GA4. A visit can become a session. Until you know which one you're buying, the price means nothing.

Three questions settle almost any listing:

1. What does one unit count? A request, a page view, a visit, a click, a search or a credit. Get the answer in writing.
2. What's the ratio to the unit you care about? Pages per visit, credits per click, seconds per point. A listing that won't give its ratio can't be compared with anything.
3. Which of your records will count it? GA4 counts page views and sessions, Search Console counts clicks and impressions from Google's results, and your server log counts requests. Price the unit in the record you'll actually read.

Then buy the unit that matches the job. For visits you can see in GA4, buy visits priced per visitor and test a free tier first. For clicks you can see in Search Console, buy clicks from a seller whose people actually search. For raw requests to test your server's capacity, use a load-testing tool, not a traffic listing. We sell traffic ourselves, and our own cards count in credits, page views, visitors and browsers, so everything below applies to us too.

The word has had several jobs, and they don't agree on size.

Sources: the AWStats glossary, Cloudflare's analytics documentation, Google's legacy definition of a hit and 10KHits' pricing page, all read on September 11, 2026.

Your hosting panel probably still prints the word. cPanel's Awstats screen "displays traffic statistics from the Advanced Web Statistics (AWStats) software" (cPanel), and AWStats keeps Hits apart from Pages, which are "usually HTML, PHP or ASP files, not images or other files requested as a result of loading" a page, such as its scripts and stylesheets. A report showing 40,000 hits and 2,000 pages describes 2,000 page views, not 40,000 visitors.

The analytics meaning is gone. Standard Universal Analytics properties "stopped processing hits" on July 1, 2023 (Google). GA4's nearest figure is Event count, defined simply as "The count of events", and one page view usually produces more than one: a first-time visitor's first page is logged as page_view, session_start and first_visit, and a user_engagement event follows once the page has been "in focus for at least one second" (Google's automatically collected events). A seller quoting Google Analytics hits in 2026 is quoting a number GA4 doesn't report.

Why the word inflates. A page is rarely one file. HTTP Archive's 2024 Web Almanac found that "The median page makes 71 requests on desktop and 66 on mobile" (Web Almanac). Not all of those reach your server, because fonts, widgets and tags load from other companies' servers and a returning browser reuses what it already has, but enough do that hits run far ahead of page views in any log report. A tool that fetches pages without a browser is the exception: one request per hit, no files, and nothing in GA4, as our breakdown of what a traffic generator sends to your site shows request by request.

Published medians are a starting point, but hits depend on the page and on what the visitor's browser already holds. So on September 11, 2026 we loaded three pages of sparkcliks.com in one headless Chrome 152 window at desktop size, the way one visitor would: our Website Traffic page in a fresh browser, then a blog post, then the Website Traffic page again. We logged every request the browser made. The Google Tag Manager, Meta, Microsoft Advertising and Clarity tags were blocked so the test wouldn't count as a visit in those tools. Requests to our own domain were left alone, because those are the hits a server log records.

What the three rows show:

• Three page views, 110 hits. Had our analytics tag been allowed to run, GA4 would have recorded three views in one session from one user. The servers on our domain received 110 requests (69, 19 and 22), so a log report built from them would show three pages and 110 hits for the same visit.
• The same page cost less than a third as many hits the second time. The Website Traffic page sent 69 requests to our servers on a first view and 22 on a repeat, because the browser already held most of its files. A hit count moves with the visitor's cache, so no fixed ratio turns hits into visits.

The 82 is a floor, too: each blocked tag would have gone on to make requests of its own, and even without them the first view was above the web's desktop median of 71. Now put a price on it. A seller who counted hits the way our log does could deliver "10,000 hits" to a page like our Website Traffic page with about 145 first-time page views, or with roughly 455 to 525 page views from visitors whose browsers already hold the files. That's the range hiding behind one word. Your pages will give different numbers. To get yours, open a page in a private window, open your browser's developer tools, tick Disable cache on the Network tab and reload, then read the request count at the bottom and filter it to your own domain. Reload once more with the cache on for the repeat-visit figure.

Below hits, the units get smaller: page views, then visits, then visitors. Each tool draws the lines in its own place, which is why the same traffic produces different numbers in different reports.

Page views. GA4's Views are "The number of app screens or web pages your users viewed. Repeated views of a single page or screen are counted." A log report counts a page view as a request for a page file, and Cloudflare defines one as "a successful HTTP response with a content-type of HTML". A listing priced in page views needs one more number before it means anything, pages per visit, which is how a "60K" plan turned out to be 20,000 visits in our read of VisitorBoost's plan cards.

Visits and sessions. GA4 counts "The number of sessions that began on your site or app (event triggered: session_start)", and by default a session "ends or times out after 30 minutes of user inactivity" (Google). The same page says GA4 estimates session counts with an algorithm called HyperLogLog++ rather than tallying every one, so small differences from an exact count are expected. A server log has no sessions at all, so log reports infer them. AWStats illustrates a visit this way: "say a unique IP accesses a page, and then requests three other pages within an hour." An hour in one tool and 30 minutes in another will split the same browsing differently.

Visitors. GA4 counts browsers, not people: Active users are "The number of distinct users who visited your site or app", told apart by an identifier each browser keeps, a point our guide to four meanings of real traffic takes further. Log and CDN tools count addresses instead. AWStats calls a unique visitor "a person or computer (host)", and Cloudflare says "Once Cloudflare identifies a unique IP address for a request, we identify such request as a visit." An office of 40 people behind one address is one visitor to Cloudflare and up to 40 users in GA4.

That last difference is what "buy unique visitors traffic" usually buys: each visit arrives in a new browser from a different address. GA4 then counts every visit as a new user, since New users are "The number of users who interacted with your site or launched your app for the first time (event triggered: first_open or first_visit)". A campaign built that way never sends the same user twice, so on its landing page New users and Sessions climb in step, while a real audience brings people back.

Clicks and searches are the only units here that begin on a search engine's results page, and they're the only ones Search Console can see.

A search click is counted by Search Console when someone clicks your listing and leaves Google: "For most result types, any click that sends the user to a page outside of Google Search, Discover, or News is counted as a click" (Search Console Help). If your tag runs, the same click becomes a GA4 session filed under Organic Search, and your log records a page request with the search engine as its referrer, followed by the page's files. A click on a Bing results page shows in Bing Webmaster Tools instead.

Not every "click" on a listing is that kind. Sellers also sell ad clicks, link clicks and visits that carry a search engine's name as their referrer without any search behind them. Our own Website Traffic's organic setting is one of those: the visit carries the keyword and referrer you set, and no search happens. None of them reach Search Console.

A search is one query typed into a search engine. If your listing appears in the results, Search Console can count an impression, which "means that a user has seen (or potentially seen) a link to your site". A search that ends without a click on your listing adds nothing to GA4 or your log. One seller in our price comparison sells "searches per day" and doesn't say how many end in a click, which is why our SparkTraffic pricing breakdown left it out of its per-click table.

Neither unit buys a position. Google denies using click data as a direct ranking factor, while Bing says it "considers how users interact with search results" (How Bing delivers search results). Our look at click data as a ranking signal sets out the record, and it's why we price a click as a click.

A credit isn't traffic. It's the unit a seller bills in, and it converts to clicks or visits at a rate the seller sets, which can change with your settings. Three published rates show how far a credit can move:

• Our own SERP Clicks. An untargeted click costs 1 credit and a geo-targeted click costs 2. So LITE's 120 credits buy 120 untargeted clicks or 60 geo-targeted ones, or 156 and 78 while our current offer adds 30% more credits at checkout. Our terms of use add that "The number of credits required per click, as well as the number of credits offered per subscription tier, are subject to change without notice."
• Another search-click seller in that price comparison charges 9 credits a click from any country and 17 from one specific country, so picking a country roughly halves what the same credits buy.
• SparkTraffic's traffic credits are charged "per visit delivered to your website", in its own FAQ's words, so there a credit reads as one visit.

Points on a traffic exchange work the same way, with time as the rate. 10KHits sells "50,000 hits @ 10 secs" on its $10-a-month Pro plan, says "1 point is equivalent to a 10 second hit", and lists "up to 60s visit duration" on the same card. Its pricing page doesn't say how points convert for longer views. If a point buys 10 seconds whatever the view length, those 50,000 hits would cover about 8,333 views of 60 seconds each, so ask before you set it beside a seller that prices visits. (10KHits calls itself "the leading website traffic exchange". Its prices were shown to us in US dollars on September 11, 2026, and may differ where you are.)

The rule for any credit or point: divide the balance by what one unit costs at your settings (targeting, view length, location), not at the headline rate.

Here's the whole set in one table. Read across to see what one unit becomes in each record, and use the last column to convert.

Two things hold for every row. Each GA4 cell assumes your tag runs, the visitor's consent lets it send data and GA4 doesn't drop the visit as known bot traffic, so delivered visits usually outnumber recorded sessions; why analytics shows less than arrived goes through the causes. And Search Console only reports what happens on Google's own surfaces, so a unit that never touches a Google results page is invisible there, whatever the listing calls it.

Here are the same five steps on two listings. The first is invented for this example, and so are its numbers:

100,000 website hits for $19.99. Unique visitors. Up to 3 pages per visit.

Step 1. Name the counter. Ask the seller what one hit is: a request, a page view or a visit. Say the answer is "a page view". Get it in writing.

Step 2. Get the ratio. At three pages a visit, 100,000 page views is about 33,333 visits. At one page a visit it's 100,000 visits, and "up to" allows both, so ask which the seller will deliver.

Step 3. Convert into each record.

Step 4. Discount for what your records drop. Run the seller's free tier or smallest plan against one page you aren't otherwise promoting, then compare the seller's delivered count with GA4's Sessions for that page on those dates. That ratio is your conversion rate from what the seller counts to what you count.

Step 5. Price the unit you'll read. Divide the price by the sessions GA4 records. If 30,000 of the 33,333 visits record (an example figure), $19.99 buys sessions at about 67 cents per 1,000. And if the seller's hit had meant a request, the same 100,000 hits could have been as few as 900 three-page visits on pages like ours.

The same steps on our SERP Clicks LITE plan. Step 1: the card counts credits. Step 2: one credit per untargeted click, two per geo-targeted click. Steps 3 and 5 then look like this, with the current 30% bonus in parentheses:

Step 4 applies to us as well. GA4 can only record the sessions your setup lets it record, and Search Console only shows clicks from Google Search orders, since a Bing Search order's clicks show up in Bing Webmaster Tools. Read any SERP Clicks price per click as the untargeted rate unless it says geo-targeted, because a geo-targeted click costs two credits and so twice as much.

We sell four products, and their cards count in credits, page views, visitors and browsers, so here's each one next to the record we stand behind.

Two candid notes:

• Our Website Traffic cards print the bigger number as well. MINI lists 60,000 page views from 20,000 unique visitors. The page-view figure is the bigger one, but the visitor figure is the one to set against GA4's Sessions, and our own FAQ notes that "a higher bounce rate means fewer total page views". Compare it as 20,000 visits.
• Automated visits aren't invisible, and they aren't ad impressions you want. Our Website Traffic FAQ says plainly "It is automated traffic". Automated traffic counted as ad impressions is invalid traffic under every major ad network's rules, and the penalty lands on your account, so keep any bought traffic, ours included, off pages that carry ads.

Whatever the unit, from us or anyone, judge it by what your own records count, and never by a promise about rankings.