Does QueryWatch need write access to my Search Console?

No. QueryWatch signs in with read-only scopes: openid, userinfo.email and webmasters.readonly. QueryWatch is an independent Google Search Console app for iPhone and Android, and the write scope is requested only when a Pro user submits or deletes a sitemap. Sign-in happens on Google’s own sign-in sheet, not inside a QueryWatch form.

What can a read-only scope do?

The webmasters.readonly scope lets an app read Search Console data for the properties your Google account can access: performance rows, URL inspection results and the sitemap list. It cannot add or remove users, change settings, delete a property or submit anything. Google lists the scopes on its Search Console API authorisation page.

Scope	What it allows	When QueryWatch asks
openid	Confirm who signed in	At sign-in
userinfo.email	Show the account’s email address	At sign-in
webmasters.readonly	Read Search Console data	At sign-in
webmasters (write)	Submit or delete a sitemap	Only when a Pro user submits or deletes a sitemap

Why would an app ever need write access?

Submitting a sitemap is a write. So is deleting one. Search Console treats both as changes to the property, so any app that offers them needs the write scope for that action. QueryWatch keeps that request separate: you see Google’s consent sheet at the moment you use the feature, and not before. Viewing the sitemap list is on the free tier and needs only the read-only scope. See can you submit a sitemap from a Search Console phone app.

Where is the sign-in kept?

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 by the developer’s own relay server in Germany every six hours. For the full path, read where your Google token goes.

Can I check what QueryWatch has access to?

Yes. Your Google Account lists every third-party app you have connected, at myaccount.google.com/connections. Select QueryWatch to see the access Google granted, and remove it at any time. Removing it cuts the app off; your Search Console data and settings are not changed.

Should I give a phone app my Search Console at all?

That is your call, and the scope list is the part to check. A Search Console app that asks for full write access at sign-in can do more than it needs to show you numbers. For a checklist that applies to any app, see is it safe to connect Google Search Console to a mobile app. If you would rather look first, Demo Mode runs the whole app, including Pro screens, on four sample properties without signing in.

Can ChatGPT or Claude read my Search Console through QueryWatch?

No. QueryWatch does not pass your data or your sign-in to an AI assistant. If you want an assistant to look at your numbers, export a CSV and share it yourself. See can ChatGPT or Claude read Search Console data.

What does it cost?

The free tier lists every property the account can access, with no site limit. Pro costs $4.99 a month or $14.99 a year. New subscribers can start the yearly plan with a first month for $0.99, and it renews at $14.99 a year after that. There is no free trial.

Requirements

QueryWatch requires iOS 26 or later on iPhone, or Android 12 or later on Android. It is available on the App Store and Google Play, and is not affiliated with Google.