What is traffic verification?
Traffic verification is checking that a website's claimed traffic is real before you buy a link placement on it. A seller lists a site at "25,000 monthly organic visitors". Traffic verification is asking for the site's Google Search Console data, seeing roughly 25,000 monthly clicks from Google Search spread across many real articles, and only then going ahead.
Traffic is one of the few signals that a site has actual readers and actual rankings. That makes it worth faking (see bot traffic on link sites), and that is why a claimed figure needs checking rather than trusting.
Why does traffic verification matter when buying links?
Traffic verification matters because a site's traffic figure is often the main reason a buyer picks it, and the figure is easy to misrepresent. A site with no real audience can still have a high authority score, a busy-looking analytics screenshot, or a large estimate in an SEO tool.
Verified traffic tells a buyer three things: real people find the site through Google, Google currently ranks it, and it is less likely to be a site built only to sell links. It does not make a paid link compliant with Google's policies, which is covered below.
What evidence of traffic can you trust?
The most trustworthy evidence of traffic is first-party Google Search Console data viewed live, because it comes straight from Google and is hard to edit in real time. The weakest is a static image or a number the seller typed.
| Evidence | What it shows | How easily it can mislead |
|---|---|---|
| Live screen share of Search Console | Clicks, impressions, CTR and position from Google Search [1] | Hardest to fake; the buyer can ask for filters on the spot |
| Search Console export or read access | Same data, browsable | Low, if access is granted directly by Google's tools |
| GA4 screenshot | Sessions and users from every source | Easy to crop, edit, or inflate with bots GA4 doesn't know about |
| Third-party SEO tool estimate | Modeled traffic from keyword rankings | Not a measurement; can be inflated by ranking for worthless keywords |
| A number in a listing or email | Whatever the seller writes | No evidence at all |
A useful rule: the further a piece of evidence sits from Google's own record of clicks, the more confirmation it needs.
How do you verify a website's traffic?
To verify a website's traffic, ask for a live view of the site's Search Console Performance report and check it against the claim, the content and the page your link will sit on. Step by step:
- Ask for Search Console, not a screenshot. The Performance report shows clicks, impressions, click-through rate and average position, with the past three months as the default view [1]. Ask the owner to switch to a longer range so you see the trend.
- Confirm the property. Check that the property shown is the domain you are buying on, not a different site.
- Look at Pages. Real search traffic spreads across many articles. Traffic concentrated on one URL, or on pages unrelated to the site's topic, is a warning sign.
- Look at Queries. The queries should match the site's subject and language. Thousands of clicks from misspellings, brand names of other companies, or a language the site isn't written in point to rankings built to inflate numbers.
- Look at Countries. Traffic should come from the markets the content is written for.
- Compare with the claim. Search Console clicks will rarely match a seller's "visitors" figure exactly. A small gap is normal. A claim several times higher than Search Console clicks needs an explanation from another real source.
- Check the trend. A sharp jump shortly before a site appears on a marketplace deserves questions.
- Record what you saw. Note the date, the figures and any filters used, so you can review the placement later.
Why don't Search Console and Google Analytics numbers match?
Search Console and Google Analytics numbers never match exactly because they count different things in different ways. Google lists several reasons [3]:
- Privacy filtering. The Performance report leaves out some queries that are searched very rarely.
- Processing. Search Console processes its data, for example by removing duplicates.
- Delay. Search Console data usually appears 2 to 3 days after it is collected.
- Time zones. Search Console reports daily data in Pacific Time; other tools may not.
- JavaScript. Google Analytics only tracks visitors with JavaScript enabled.
Clicks are also counted differently depending on the view. In a property-level view, a user who clicks one result, goes back and clicks another result from the same property counts as one click. In a page-level view, the same behavior counts as two clicks [2].
So the test is not whether the two numbers are equal. The test is whether the gap is small and explainable.
Can Google Analytics screenshots prove traffic is real?
No. A Google Analytics screenshot cannot prove traffic is real, because GA4 only filters known bots and anyone can crop or edit an image. Google Analytics 4 automatically excludes traffic from known bots and spiders, identified through Google research and the Interactive Advertising Bureau's International Spiders and Bots List [4]. Bots built to look human are not on that list.
Google also says you cannot see how much known bot traffic was excluded [4]. So even an unedited GA4 report can't show the buyer how clean it is. Use GA4 as supporting context alongside Search Console, never as the only proof.
What is the difference between traffic verification and site vetting?
Traffic verification is one check inside site vetting. Traffic verification answers one question: is the claimed traffic real? Site vetting asks the wider question: is this site safe and worth a placement at all, covering content quality, topic fit, outbound links, editorial standards and policy risk.
A site can pass traffic verification and still fail site vetting, for example a site with genuine traffic that sells followed links on every page.
How has traffic verification changed over time?
Traffic verification grew out of advertising, where fake clicks were a problem long before link buyers checked traffic. Click fraud, where a person or script imitates a real user clicking ads, was identified in 2001, and Google settled a click fraud class action for $90 million in July 2006 [7].
2001: fake clicks are identified
Jessie Stricchiola is credited with first identifying pay-per-click fraud in 2001 [7]. Advertisers learned early that a visit counted is not a visit from a person.
2006: fake clicks reach the courts
Yahoo settled a click fraud class action in July 2005 and Google settled one in July 2006 [7]. Verifying traffic became a standard concern in paid media.
Today: first-party data as proof
Link buyers face the same problem with a different product. The answer has moved the same way: away from numbers a seller reports and toward data that comes directly from the platform, which for organic traffic means Search Console.
What are the limits of traffic verification?
Traffic verification has limits a buyer should know. Search Console shows Google Search clicks only, so it says nothing about traffic from other search engines, social or email. It does not label clicks as human or automated, and Google's help pages on the Performance report do not say whether automated clicks are filtered. And site-level traffic says little about the new page your link will appear on, which starts with no traffic of its own.
Verification also does not settle the policy question. Google's spam policies list buying or selling links for ranking purposes, including exchanging money for links or for posts containing links, as link spam [5]. Paid links are acceptable to Google when they carry rel="sponsored" or rel="nofollow" [5], and Google prefers sponsored [6].
When should you verify a site's traffic?
Verify a site's traffic every time before you buy a placement, and again if you review the placement later. Figures from a list made months ago describe a site that may have changed since.
- Verify at the point of purchase, not from an old spreadsheet.
- Set a minimum traffic level that fits your campaign, and apply it to verified clicks, not to claims.
- Walk away from any site that refuses a live view of Search Console.
- Expect any paid link to be labeled
rel="sponsored"orrel="nofollow", as Google's policies require [5].