How do Search Console apps get your data?
Search Console apps read your data through Google's public API after you sign in with Google. What they can read, what stays on the phone, and what to check.
A Search Console app signs you in with Google, then asks Google’s public Search Console API for the same numbers you see in the website: clicks, impressions, CTR and average position. It can only read properties your Google account already has access to. Google has never released an official Search Console app, so every app in the stores works this way.
What happens when you sign in?
You see Google’s own sign-in sheet and approve a list of permissions. After that, the app can request reports for the properties your account can open. The app does not get your Google password.
| Step | What happens |
|---|---|
| Sign in | Google’s sign-in sheet shows the permissions requested |
| Approve | You grant read-only access to Search Console data |
| Fetch | The app calls the Search Console API for each property |
| Show | Numbers appear in the app, with the same delay as the website |
Which permissions should you expect?
Read-only scopes are enough to show performance data. QueryWatch requests openid, userinfo.email and webmasters.readonly. The write scope is requested only when a Pro user submits or deletes a sitemap. If any app asks for more than it needs to display reports, ask why before approving.
Where does the credential live?
It depends on the platform. In QueryWatch on iPhone the refresh token stays in the Keychain. On Android, Google Play services hold the grant and the app never receives a refresh token. A credential leaves the phone only if push alerts are turned on, because alerts are computed on the developer’s own relay server in Germany every six hours. For the longer explanation see where does your Google token go.
Does an app show different numbers from the website?
It should not, because both read Search Console data. The data still lags by a couple of days; read why Search Console data is days behind. Exports and API calls are also limited in rows, covered in row limits and anonymised queries.
How can you check an app before signing in?
Read the store listing for the permissions and price, find a privacy page that names where data goes, and use a demo mode if one exists. QueryWatch, which publishes this page, has a Demo Mode that runs the whole app on four sample properties without signing in. Store links are on the product page. QueryWatch is independent and not affiliated with Google.
Questions
Is there an official Google Search Console app?
No. Google has never released an official Search Console app for iPhone or Android. Every Search Console app in the stores is a third-party client of Google's public Search Console API.
What permission does a Search Console app need?
Read-only access to Search Console data. QueryWatch asks for openid, userinfo.email and webmasters.readonly, and requests the write scope only when a Pro user submits or deletes a sitemap.
Can an app see data for sites I do not own?
Only properties your signed-in Google account can already access. An app cannot add access that your account does not have in Search Console.
Where does QueryWatch keep my Google credential?
On iPhone the refresh token stays in the Keychain. On Android, Google Play services hold the grant and the app never receives a refresh token. A credential leaves the phone only if push alerts are turned on.
Keep reading
Get QueryWatch
Free on iPhone and Android for every property you have, with no site limit. Open Demo Mode first if you want to look around before you connect a Google account.
iPhone needs iOS 26 or later; Android needs Android 12 or later. Free to download, with an optional Pro subscription. An independent app, not affiliated with Google.