Yes, Google uses clicks. That part is no longer a debate: Google says so itself, and a federal court has described the system that does it. What nobody outside Google can tell you is how much a click is worth on your query. The only way to find out is to measure it on your own site, and a test on one query costs less than $3. This page sets out what is on the record, what is not, and how to run that test.
What is on the record
Google's own description. On its How Search works page, Google writes: "We also use aggregated and anonymized interaction data to assess whether search results are relevant to queries. We transform that data into signals that help our machine-learned systems better estimate relevance." Interaction data is, among other things, what people click.
The antitrust case. In United States v. Google, the court's remedies Memorandum Opinion of 2 September 2025 describes NavBoost as "one of Google's core ranking models" that "runs on 13 months of Google click-and-query data", citing trial testimony by Pandu Nayak of Google. The same opinion lists "the number of clicks" among the "raw" signals that Google processes into higher-level ones. Search Engine Journal's reading of that opinion (April 2026) puts the consequence plainly: clicks feed aggregate signals and model training; they are not applied to results one by one.
The 2024 documentation leak. In May 2024 about 2,500 internal Google documents describing the Search API became public. Rand Fishkin published the first account, and Google confirmed to The Verge that the documents were authentic, while cautioning against "inaccurate assumptions about Search based on out-of-context, outdated, or incomplete information". The documents name click attributes such as goodClicks, badClicks and lastLongestClicks, and Mike King's analysis found a site-level count of Chrome views among the page quality features.
What the record leaves open
Every one of those sources describes inputs. None of them gives a weight.
The leak shows attribute names, not how they are combined; Fishkin's own post says the documentation "doesn't show things like the weight of particular elements in the search ranking algorithm", and King writes that "we do not know how features are weighted in the various downstream scoring functions." The court record establishes that click data trains and feeds ranking systems, not that a given number of clicks moves a given page.
So "clicks are used" has evidence behind it, and "this many clicks will lift you to the top" does not. A vendor who promises the second is promising something nobody can see. What you can do is measure the effect on your own query, which is what the rest of this page is about.
Two points that are often blurred:
- Your analytics account is not part of this. Everything in the record is Google's own data: what happens on its results pages and, for the Chrome views, in its browser. The engagement time in your GA4 reports is a separate measurement of your own, and the difference between the two matters when you read either.
- Long and short clicks have no published durations. Tables that say a click under 10 seconds is "bad" and over 30 is "good" are invented. The leak names attributes for long clicks; it does not define them in seconds.
Where a test is worth running
Position on a query is decided against everything else competing for it, and NavBoost, by the court's account, learns from more than a year of click data. That points to where a test has the best chance and is easiest to read: a page that already ranks for the query, typically somewhere on the first two pages, with a stable position and enough impressions in Search Console to give you a baseline. A page on page five gets almost no real clicks to compare against, and a page that already ranks first has little room to move.
Clicks do not fix the page itself. If it does not answer the query, visitors who land on it behave accordingly, and no click campaign changes what it says.
What automated SERP clicks give you
A browser runs a query on the search engine, finds a listing in the results and clicks it. You get three things, and only the third is uncertain.
A record. A session in your analytics for each click, when the tool drives a real browser that runs your analytics tag, and a delivery count you can check against it. Search Console is built by Google from its own data, so whether and how these clicks appear there is Google's decision: compare it with your baseline rather than expecting it to match what was delivered.
Control. You choose the query, the country, the device and how the sessions arrive over time. That is what separates this from buying undifferentiated traffic, and you can verify it on day one: if the geography and session length in your analytics do not match what you configured, the tool is not doing what it says.
A behavioral signal with an uncertain effect. Clicks feed the systems described above. Whether that moves your position on your query is what your test measures.
The risk, stated once
Google's spam policies list machine-generated traffic, "the practice of sending automated queries to Google", as a violation of those policies and of its Terms of Service, and automated searches that click a result fall under it. Our SERP Clicks always search from residential IPs of local internet providers, in real browsers, with varied session lengths and a gradual ramp. That makes automated clicks look less like a script, and it is most of what separates a serious tool from a cheap one. They lower the chance of looking anomalous; they do not make anyone invisible, and claims of undetectability are claims about a system the seller cannot see. The decision to take that risk is the site owner's, and a small test on one query keeps it small too.
Automated sessions also have no buyer at the other end, so they bring no leads or sales. That is what advertising is for.
How to test it on one query
- Pick one query your page already ranks for, with brand queries filtered out.
- Record the baseline. In the Search Console Performance report, note CTR and average position for that query over the last four weeks. The CTR by position guide shows how to build a baseline worth comparing against.
- Run a small volume. One or two clicks a day for 30 days. At $0.09 a click, one a day costs $2.70 for the month, and clicks are charged only when your site is found in the results and clicked.
- Check delivery the same week. The geography, device and session length in your analytics should match what you set.
- Compare after 30 days. Same query, same report. A before and after on one site is a read on your own campaign: other things change in the same weeks, so treat it as evidence for your query rather than a rule for every site.
We built our SERP Clicks for exactly this test: real browser sessions that search your query on Google, Bing or Yandex and click your listing, with the country, device and pacing you configure, and a free daily position check for each keyword so you can watch the result as it happens. If you want to try it first, ask support for a test budget; it is set up on request.



