I have worked with Google Search Console (GSC) and Google Analytics (GA) for long enough to know that organic GA traffic to a specific page is typically higher than GSC traffic to the same page.

However, until now, I have never come across the reverse situation.

One of my clients is a recruiter. We recently made a change to their job board and were excited to see in GSC that the number of clicks to the individual jobs had jumped dramatically (screenshot).

When I run a custom report in GA (screenshot of parameters), I see far fewer clicks to the same page type (screenshot).

I've tested GA and as far as I can tell, it is working but I guess it's possible I am missing something. Alternatively, is it possible that GSC's data is inaccurate?

Any thoughts would be welcome.

  • For future reference, please use Imgur for screenshots, not Evernote. Evernote forces the user to download the image rather than display it in the browser. Commented Jan 14, 2022 at 0:05
  • This was a result of an incorrect setting in Evernote. I have fixed it.
    – zgall1
    Commented Jan 17, 2022 at 20:55

4 Answers 4


Google Search Console uses Clicks which will count every time a person clicks on your results in the SERPs, regardless of whether it is the same person or if there are multiple clicks in a short period of time.

In your Google Analytics custom report, you are using Users, a calculated GA metric based on a single identifier (Client ID or User ID).

How can we explain the differences in your reports?

  1. If a person performs several Google searches and clicks three times on your results within 30 minutes, GSC will show 3 clicks but GA will show only 1 user. You should use Sessions instead of Users in your custom report.
  2. If a person clicks twice on your results in the SERPs within 30 minutes, Google Analytics will only record as a Landing page the first URL that was visited (essentially the arrival point during that session). Using Landing page as a dimension in your custom report will exclude actual organic traffic. In this case, there is no quick fix to get the data, since if you use Page instead of Landing Page you will get the organic sessions that went through those URLs but not just the ones that were arrival point.

In summary, you are not using the correct metric/dimension in Google Analytics to get the data you are looking for. In the following image, assuming that all page views are organic and first access (landing page), the results would be:

  • GSC: 9 clicks
  • GA: 1 user, 3 sessions, 3 landing pages, 9 pageviews

enter image description here


It's more likely there's a problem with Analytics than Search Console being inaccurate.

It's possible that you might have a filter in place on that Analytics view which tells it to ignore certain visitors. That would definitely mean that Analytics would show fewer visitors than Search Console shows clicks.

There is the possibility that it's the standard Analytics filter which ignores known bots. I'm not entirely familiar with any similar filters in Search Console, but it's possible they might be different. As such Search Console is reporting clicks, which aren't being logged as pageviews in Analytics because the latter does not recognise them as valid users.

One thing to bear in mind is how each service records their separate metrics. Search Console record a click on a search result, that's entirely done server side by Google. Analytics records a pageview, typically using JavaScript to send that data when the page loads. There's three things I can think of off the top of my head that might interfere with that:

  1. You happen to attract a noticeable percentage of users who have JavaScript deactivated in their browser by default. I'd suggest that this was unlikely, but it is possible. Again, going back to the potential of bots, recruitment is one industry where I am aware that automatic scrapers prowl the net for vacancies. The capability of such bots to run JS might account for your issue.

  2. Something is wrong with that page, it is taking too long to load and users are abandoning it before the pageview data is sent to Analytics. Pageview Insights should let you narrow down any problems there.

  3. Some non-universal condition is causing the tracking code to fail. What this could be varies massively, but one example might be that you may have a cookie consent script which entirely blocks Analytics tracking until the user grants consent - and some of your users are not granting consent. That would explain a reduced but non-zero number of pageviews being logged.

The nuclear option of determining what the problem is depends on if you have access to the server's log files. You could manually track down hits on the most affected page and look for patterns which might help you diagnose why Search Console is reporting clicks, but Analytics isn't reporting pageviews. If you have log files from before the surge in traffic, running a comparison would be ideal.


Some popular browser extensions block google analytics. For example, ublock origin.

So in this case, Google is tracking the clicks from their site via the actual clicking event, but the javascript on the destination page running the google analytics is blocked by the client's browser.


After some additional research, I was able to figure this out.

When a person clicks a Google job posting to view the job listing on Google, this is considered a click and is labelled as "Job listing" under the Search Appearance tab. enter image description here

If the user is interested in the job and then clicks on the Apply button to be taken to the website, this is considered a click as well and is labelled as "Job details". Obviously, only this click is tracked in Google Analytics.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.