Google Search Console Integration – Privacy & Data Handling

Available on:
Free
Premium
Marketing Add-on

WP Statistics is built on the principle that site analytics should be both powerful and privacy‑friendly. The Marketing add‑on brings those same values to its integration with Google Search Console (GSC). This document explains what the integration does, which permissions are requested, what data travels where, and how we protect your visitors’ and your own privacy every step of the way.

1  Why Connect Google Search Console?

Connecting GSC enables you to view valuable search‑performance metrics (impressions, clicks, average position, etc.) directly inside WP Statistics. This keeps your SEO insights in the same privacy‑centric dashboard you already use–no need to log in to multiple services or share access with third‑party analytics platforms.

2  Permissions Requested During Setup

When you press “Connect Google Account” in the WP Statistics settings, you are sent through Google’s standard OAuth 2.0 consent flow. You will see a screen titled “WP Statistics wants access to your Google account.”

We request the following read‑only OAuth scopes:

Google OAuth ScopeWhy we need it
openidRequired so Google can issue an ID token that verifies the sign‑in.
https://www.googleapis.com/auth/userinfo.emailLets WP Statistics show which Google account is connected by reading the email address.
https://www.googleapis.com/auth/userinfo.profileLets WP Statistics display your Google display name and avatar in the admin UI.
https://www.googleapis.com/auth/webmasters.readonly (shown as “View Search Console data for your verified sites”)Allows WP Statistics to fetch — but never modify — your Search Console performance data.

⚠️ WP Statistics cannot create, delete, or modify any properties in your Search Console account.

3  Data Stored on Our Middleware Server

To orchestrate secure, token‑based requests to Google’s APIs, the Marketing add‑on communicates with a lightweight middleware service we maintain. The only persistent record we keep is:

FieldWhat It IsWhy We Need ItWhere It Lives
Domain HashA non‑reversible SHA‑256 hash of your site’s domain, truncated to the first 40 characters.Used as an anonymous identifier so we can recognise that subsequent token refresh requests belong to the same site–even if you disconnect and reconnect.Our middleware database (encrypted at rest).

We do not store any other information from your website, Google account, or Search Console in our infrastructure.

3.1  How Anonymisation Works

  1. Hashing – When you connect, WP Statistics takes your site URL (e.g. https://example.com) and computes its SHA‑256 hash.
  2. Truncation – We store only the first 40 hex characters (160 bits) of that hash.
  3. No Reversal – Because SHA‑256 is a one‑way function and the stored fragment is incomplete, the original domain name cannot be derived from the hash alone.

4  Data Stored on Your WordPress Server

The OAuth tokens that Google provides are kept only in your own database (using WordPress’s Options API with autoload disabled so they are not loaded on every page‑view). These include:

TokenLifespanPurpose
Access Token~1 hourTemporarily authorises calls to Google’s Search Console API on your behalf.
Refresh TokenUntil revokedLets WP Statistics request a new access token without requiring you to log in again.
Expires InValue in secondsInforms WP Statistics when to use the refresh token.

Tokens are never written to disk on our middleware and are transmitted over TLS 1.2+ only.

5  Security Practices

6  Reconnect & Disconnect Logic

Because your domain name is hashed, WP Statistics can:

7 Use Your Own Google API Credentials (Advanced Option – Coming Soon)

This upcoming feature lets you supply a custom GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET in Settings → Marketing → Google Search Console.

Because nothing leaves your infrastructure, this mode provides the highest level of isolation for organisations with strict compliance needs.

8 Troubleshooting & Revoking Access  Troubleshooting & Revoking Access  Troubleshooting & Revoking Access

  1. Disconnecting in WP Statistics: Go to WP Statistics → Settings → Marketing → Google Search Console and click Disconnect. This immediately stops all API calls and removes stored tokens from your database.
  2. Still See WP Statistics in Google? In some cases Google may continue to list WP Statistics under Google Account → Security → Third‑party apps & services. If so, click the entry and press Remove Access to revoke the OAuth tokens manually.
  3. Re‑authorising: Simply connect again in WP Statistics; you will go through the OAuth consent screen once more.

9  Frequently Asked Questions

Q : Does WP Statistics store my search queries or performance data?
A: No. Search‑Console metrics are fetched on demand, cached in your WordPress database (if enabled), and never transmitted to our servers.

Q : Can I limit access to a single property instead of all verified sites?
A: Google’s OAuth scope is account‑wide. To limit scope, create a Google account dedicated to the specific property and verify only that site.

Let’s get started
Take your business to next level

Become part of our growing family of +600,000 users and get the tools you need to make smart choices for your website. Simple, powerful insights are just a click away.