SEO OS GSC
A read-only reporting tool for Google Search Console performance data. An owner-operated tool at a proof stage, used for the operator's own web properties, and for a client's property where the client has authorised the operator to report on it.
What this application does
SEO OS GSC is designed to connect to the Google Search Console API and retrieve search performance data — search queries, page URLs, clicks, impressions, click-through rate and average position — and turn it into search-performance reports.
The application reads only the property configured for the report being produced. The
operator's own property, used for its proof runs, is
https://seoos-proof.pages.dev/. Where a client authorises the operator to
report on the client's property, that property is configured in the same way and is read
in the same read-only way. This page describes what the application does; it makes no
claim about data belonging to anyone who has not authorised that access.
The application is read-only. It does not submit, change or delete anything in Search Console, and it cannot add, remove or alter Search Console properties or their verification status.
Who operates it, and at what stage
SEO OS GSC is an owner-operated tool at a proof stage. It is run by its operator, to produce search-performance reporting on the operator's own properties and on a client's property where the client has authorised the operator to report on it.
It is not a public service, there is no sign-up, and the application itself is not offered to other people to use.
Google data the application requests
The application requests exactly one Google OAuth scope:
https://www.googleapis.com/auth/webmasters.readonly— view Search Console data for properties the signed-in Google account can access.
No other Google scope is requested. The application has no access to Gmail, Google Drive, Google Contacts, Google Calendar, Google Ads or Google Analytics.
Google grants this scope at the account level, so it covers every Search Console property the authorising account can access — not only the one the application is configured to read. What limits the application to the configured property is its own configuration. The Privacy Policy states this plainly rather than implying the scope itself is narrower than it is.
How sign-in works
Authorisation happens through Google's own OAuth consent screen, started from the application. Google shows you what access is being requested before you approve it. You are never asked to type your Google password into this application.
How to withdraw access
You can withdraw access at any time at myaccount.google.com/permissions. Google lists each authorisation under the name shown on the consent screen you approved. For this application that name is expected to be SEO OS GSC, but Google controls how an app's name is displayed and may show something different until the app's branding has been verified, so check the requested scope shown alongside a grant before removing it.
One limit worth knowing: Google records the authorisation against the Google Cloud
project behind the application — seo-os-gsc-512719 — rather than against a
single OAuth client. Removing that grant withdraws the authorisations held by that
project. Today this application is the only thing in that project, but if others are added
to it later, the same removal would cover those too. It does not affect grants belonging to
any other Google Cloud project you have authorised; those are listed and removed separately.
Once the grant is removed, the application can no longer request new Search Console data for your account. Withdrawing access does not erase Search Console data that was already retrieved and saved — see the Privacy Policy for how to ask for deletion.
Policies
- Privacy Policy — what Google user data is accessed, how it is used, where it is stored, who it is shared with.
- Terms of Service
Contact
Questions about this application or its handling of data: connectsalmanofficial@gmail.com