Connect Google Search ConsolePRO
Step-by-step guide to connecting Google Search Console (GSC) to SEObolt Pro. Once connected, SEObolt reads your organic search performance directly from Google (impressions, clicks, average position, top queries) and surfaces it inside the Analytics tabs alongside your GA4 traffic data. This guide covers the OAuth flow, the expected "Google hasn't verified this app" warning screen, property picker guidance, first data fetch expectations, and common connection issues.
What Search Console Gives You in SEObolt
Google Search Console is Google's own reporting surface for organic search. It tracks every search query that led to a click or impression on your site, alongside average ranking position, click-through rate, and per-URL performance. Google publishes each day's data around 2 days after the fact, so the freshest data you'll ever see is 48 hours old.
Once GSC is connected, SEObolt populates five Analytics tabs with GSC data:
- Dashboard, an at-a-glance rollup of clicks, impressions, CTR, and average position across the whole site over the selected date range.
- Keywords, every search query bringing visitors to any page on your site with impressions and clicks for each. Sort to find your highest-CTR queries or biggest-impression low-CTR opportunities.
- SEO Performance, per-page ranking metrics showing which URLs are climbing, which are sliding, and the day-over-day movement.
- Site Analytics, blended with GA4 for on-site behavior once you connect that separately.
- Rank Tracker, daily-tracked target keywords with position history over time, per country and device.
A Google account with Search Console access, a verified property in that account matching this site's URL, and SEObolt Pro (any tier) active on this WordPress install. If you don't have a verified GSC property yet, set one up first at search.google.com/search-console, verify it, then come back.
Connect via OAuth
SEObolt uses standard Google OAuth so your Google credentials never touch WordPress. Google issues SEObolt a read-only access token scoped to Search Console; that token is what SEObolt uses to fetch your data.
Open Connections
In your WordPress admin, go to SEObolt → Settings → Connections. The tab shows two large cards: Google Search Console (top) and Google Analytics 4 (below). Each has its own Connect with Google button.
Click "Connect with Google" on the Search Console card
The button opens Google's OAuth flow in the same tab. Google first asks you to pick which account you want to sign in with; pick the account that owns (or has manager access to) the Search Console property for this site.
Google may show a brief "You're signing back in to Royal Plugins" confirmation screen instead of the full permission grant, since it remembers your previous consent. Click Continue to complete the sign-in.
Expect the "Google hasn't verified this app" screen
This is normal. Because the SEObolt OAuth app is registered under Royal Plugins and is pending Google's formal app-review process, Google shows a warning before the consent screen. Confirm the app name displayed is Royal Plugins, then click Advanced, then Go to Royal Plugins (unsafe) to continue.
Google labels every unverified OAuth app the same way, regardless of who published it. The verification process is a Google-side review, not a security seal. Your Google credentials never leave Google during OAuth; SEObolt only receives a scoped access token when you approve the consent screen. If you'd rather see this warning removed, so would we; the review process is on Google's timeline.
Approve the Search Console scope
Google shows the "Royal Plugins wants access to your Google Account" screen with the exact permissions SEObolt is requesting: read access to your Search Console properties and their aggregated performance data. No write access is granted, so SEObolt cannot modify your GSC settings, delete properties, or change verification. Click Continue.
Pick your GSC property
Google redirects you back to SEObolt → Settings → Connections. The Search Console card immediately shows a green Connected status with your Google email, and a yellow Select a Property panel appears with a dropdown listing every verified property on your Google account. Pick the one matching this WordPress site's URL and click Select. See Select Your GSC Property below for guidance on URL-Prefix vs Domain properties.
Confirm the connected state
Once a property is selected, the Google Search Console card updates to show a green Connected heading with a checkmark, your Google email, and the selected property URL. Two buttons appear: View Analytics Dashboard (which jumps straight to the Analytics page) and Disconnect. If you don't reach this state after approval, either your browser blocked the redirect (rare) or a firewall stripped the callback URL; retry from Step 1.
Select Your GSC Property
If your Google account has multiple GSC properties, SEObolt shows a property picker right after connection. Pick the one matching this WordPress site's URL. This step is silent but critical: GSC returns zero rows for a property that doesn't match the URL, which looks identical to "no traffic" and is the most common cause of empty Analytics tabs.
URL-Prefix vs Domain properties
GSC supports two property shapes for the same domain, and they return different data:
| Property type | Example | What it returns |
|---|---|---|
| URL-Prefix | https://example.com/ |
Only traffic to URLs matching that exact scheme + host + optional path prefix. A separate http:// property returns zero rows for HTTPS traffic. |
| Domain | example.com |
All traffic to the domain across every scheme, subdomain, and path. Requires DNS TXT verification instead of file-based verification. |
If your GSC has both a URL-Prefix property and a Domain property for the same site, they'll show up as separate entries in the picker. Pick whichever your Google-side dashboards actually track against. Domain properties are the newer shape Google introduced in 2019 and now recommends for most sites; URL-Prefix properties remain the older common shape.
Open Search Console on google.com in another tab, look at which property has actual data flowing today, then pick that same one in SEObolt. If you pick the wrong property, disconnect from the Connections tab and reconnect to run the picker again.
First Data Fetch
Once connected, visit SEObolt → Analytics. The five tabs (Dashboard, Site Analytics, SEO Performance, Keywords, Rank Tracker) each pull their own slice of GSC data and cache it inside your WordPress database, so subsequent tab loads are near-instant.
Land on the Dashboard tab
Click the View Analytics Dashboard button on the Search Console card (or navigate manually to SEObolt → Analytics). The Dashboard tab is selected by default. On a fresh connection, data starts loading automatically. Expect the first fetch to take 20 to 60 seconds because Google needs to build the initial query result for your property; subsequent visits are near-instant thanks to the cache.
Switch through the other tabs
Click Site Analytics, SEO Performance, Keywords, and Rank Tracker in turn. Each tab loads its own data on first click and caches independently. The tab-content area shows a "Loading data..." indicator during the fetch.
Force a fresh pull with the Refresh button
The Refresh button sits at the top of the Analytics page, next to the date-range selector. Click it to force a fresh fetch from Google for the currently-visible tab. Also use the date-range selector to switch between the last 7, 15, 30, 60, 90, or 180 days.
Google Search Console publishes each day's data approximately 2 days after the fact. This is a Google-side delay, not a SEObolt caching issue. If you connected GSC yesterday and haven't received search traffic in the last 3 days, the tabs will be genuinely empty until Google ships that batch. Give it 48 hours after connecting on a low-traffic or brand-new site before assuming something's wrong.
Troubleshooting
Most connection issues fall into one of four categories. If your data isn't populating after connection, the dedicated guide at Analytics not populating covers the full diagnostic tree. Quick hits here:
OAuth flow completes but Connections still shows Not connected
Your browser likely blocked the callback redirect from Google back to your WordPress admin. Common culprits: strict tracking-protection settings, an ad-blocker rewriting the callback URL, or a proxy stripping OAuth state parameters. Retry from a different browser (or an incognito window with the ad-blocker off), or temporarily whitelist your admin URL in your browser's tracking-protection settings.
Property picker shows no properties
The Google account you approved doesn't have any verified Search Console properties. Confirm at search.google.com/search-console that at least one property is listed and shows verified status. If you have properties but they don't appear in SEObolt's picker, disconnect and reconnect; occasionally Google's property list needs a fresh OAuth pull.
Property connected but Analytics tabs are empty
This is the top-of-list cause covered in the dedicated Analytics not populating guide. Usually a mismatch between the selected property's URL and your site's actual URL (URL-Prefix vs Domain), or you haven't clicked Refresh on the affected tab yet.
"Insufficient permissions" error during OAuth
The Google account you signed in with doesn't have GSC access to any property. Either sign in with a different account that owns/manages a property, or ask a GSC property owner to grant your account Full user access at Search Console → Settings → Users and permissions.
Disconnecting or Reconnecting
To disconnect Search Console from SEObolt, go to SEObolt → Settings → Connections and click the Disconnect button on the Google Search Console card (next to View Analytics Dashboard). This revokes SEObolt's access token, wipes the cached data, and drops the property selection. Your GSC account itself is untouched; SEObolt just loses its read access.
To reconnect, click Connect Google Search Console again and follow the same OAuth flow from the top of this guide. You can reconnect with the same Google account or a different one; SEObolt will re-run the property picker either way.
To switch which GSC property SEObolt reads from, disconnect and reconnect. The property picker runs again on reconnect, and you can pick a different property (or a different Google account entirely) without losing your GA4 connection.
Privacy and Data Handling
Connection is managed via Google's standard OAuth flow. SEObolt receives only the read-only Search Console scope you approve on the consent screen, and uses that access solely to fetch your own report data. No telemetry, no analytics forwarding, no third-party sharing.
Data pulled from GSC (queries, clicks, impressions, per-URL performance) is cached inside your WordPress database so subsequent tab loads don't re-hit Google. The cache is invalidated when you click Refresh or when SEObolt is disconnected. If you're operating under GDPR or a similar regime, the GSC data flow is Google-account-holder to Google-account-holder; you're not exposing any third-party visitor data to SEObolt.