Know which searches bring visits with Google Search Console

What upTake reads from Google Search Console

With read-only access to Google Search Console, upTake reads the search queries that led people to your site, with their impressions, their clicks and their average position, day by day. It asks Google for that single permission and nothing more, and among your properties it picks the one that matches the site of your project.

How to connect Google Search Console

You need an upTake project first; creating one takes about four minutes. Click Connect on the Integrations page: a Google Search Console window opens, you sign in there and approve the access. upTake never sees your Google Search Console password.

What you see afterwards

Visits that come from a search engine already appear on your overview, measured by the script on your site and filed under Google search. The queries add the words people typed before they arrived. They are stored with your project; the screen that shows them on the overview is still being built.

What upTake never reads

upTake cannot change anything in your Google account, and it reads nothing else from it.

Whatever you connect, the IP addresses of your visitors are never stored, and the keys and accesses you give are stored encrypted and never sent back to your browser.

Good to know

You can disconnect Google Search Console at any time from the Integrations page: upTake stops at once, and what was already imported stays in your project until you delete it. Your data is hosted in the European Union, and you can export all of it, or delete your account, from Settings.

Why connect it

Most analytics tools stop at where your visitors came from. upTake goes one step further: it ties each visit and each payment back to the thing you did, whether a post, a link you shared or a release you shipped, and tells you every week what to do more of. Google Search Console is one more piece of that picture.