Google Search Console Integration
Your search performance data, ready for reporting.
SearchSignal connects to Google Search Console via secure read-only OAuth. Pull clicks, impressions, CTR, average position, queries, and landing pages directly into your SEO reports—no manual exports required.
Quick Setup Checklist
- Have access to the Google account with Search Console permissions
- Know which GSC property matches your client's site (domain vs URL prefix)
- Connect Google Account in SearchSignal
- Link the correct GSC property to the client
- Refresh a report to confirm data flows
What Search Console Data We Use
The integration pulls the metrics that matter for keyword and page-level SEO reporting.
Performance Metrics
- Clicks: How often users clicked through from search results
- Impressions: How often pages appeared in search results
- CTR: Click-through rate (clicks / impressions)
- Average position: Mean ranking position for queries
- Date-based trends: How performance changes over time
Dimensions and Breakdowns
- Queries: The search terms driving impressions and clicks (keywords)
- Pages: Which landing pages receive organic traffic
- Countries: Geographic breakdown of search performance
- Devices: Desktop, mobile, and tablet splits
What We Do Not Do
Your Search Console configuration remains exactly as you set it up.
Permissions, Privacy, and Access Controls
Connecting Search Console follows secure, standard practices.
How Authentication Works
- Google OAuth 2.0: Industry-standard authentication
- Read-only scope: Requests
webmasters.readonlypermission only - Secure token storage: Tokens stored securely with automatic refresh
- Per-client property linking: Each client connects to their own GSC property
Agency-Friendly Design
Connect your Google account once. Then link specific Search Console properties per client in their Connections area. This means:
- One OAuth connection serves multiple clients
- Each client's data stays isolated
- Revoking access is as simple as disconnecting the Google account
| Security Feature | What It Means |
|---|---|
| Read-only access | We can view data, not change anything |
| Automatic token refresh | Connections stay active without manual work |
| Client isolation | Client A's queries never appear in Client B's reports |
| Central token management | Revoke access anytime from your Google account |
How to Connect Search Console
Five steps to keyword data in your reports.
Connect Your Google Account
Go to Google Accounts in SearchSignal and click Connect Google Account. This starts the OAuth flow.
Approve Read-Only Permissions
On the Google consent screen, approve access. You'll see the webmasters.readonly scope requested—this allows reading Search Console data without modifying anything.
Link a GSC Property to the Client
Go to the client's Connections area. Select the Search Console property that matches this client's website.
Confirm the Right Property Type
Search Console offers two property types:
- Domain property: Covers all subdomains and protocols (example.com)
- URL prefix property: Covers only a specific protocol and subdomain (https://www.example.com)
Select the property that matches how you report on the site. Domain properties are usually preferable if available—they include all variations.
Validate Data Flow
Refresh a report for this client. If keyword data appears in the Keyword Performance section, the connection is working.
Best Practices
- Match the canonical domain: If the site uses
https://www.example.com, make sure the connected property covers that URL structure. - Prefer domain properties: When available, domain properties capture all subdomains and protocols in one view.
- Verify before reporting: Generate a test report to confirm the right data appears before sending to clients.
Where Search Console Appears in Your SEO Reports
GSC data powers the keyword and page-level sections in the SEO Reporting Dashboard.
Keyword Performance Section
Top queries by clicks, impressions, CTR, and average position. Shows which search terms drive traffic and how rankings are trending.
Page Performance Section
Top landing pages from organic search. Identifies which pages earn the most visibility and clicks.
CTR and Position Trend Insights
Track how CTR and average position change over time. Useful for measuring the impact of title tag updates or content improvements.
Opportunity Identification
The dashboard surfaces quick wins:
- High impressions, low CTR: Pages that rank but don't get clicks
- Position 8-20: Queries close to page one that could move up
- Declining pages: Pages losing rankings that need attention
Data Freshness and Reporting Delays
Search Console data has inherent delays. Here's what to expect.
Google's Processing Timeline
Search Console data is not real-time. Google's documentation notes that data can take 2-3 days to appear, sometimes longer. This is a platform limitation—the integration pulls whatever Google has made available.
Cached Reports
SearchSignal caches report data so reports load quickly. When you open a report, you see the last fetched data rather than waiting for a fresh API call.
Refresh Controls
Click Refresh on any report to pull the latest Search Console data (along with GA4 and PageSpeed). The report updates with current data from all connected sources.
Token Refresh
OAuth tokens can expire or be revoked—especially after password changes or Google security reviews. If Search Console data stops appearing, go to Google Accounts and reconnect.
Check the "Last refreshed" timestamp on reports to see when data was last pulled from Google.
Troubleshooting Search Console Issues
When connections break or data looks wrong, here's where to start.
No GSC Properties Available
Likely cause: The connected Google account doesn't have access to any Search Console properties.
Fix: Connect a different Google account that has Search Console access, or request access to the client's property first.
Connected But Missing Queries or Pages
Likely cause: Wrong property selected, very low data volume, or the selected date range is too narrow.
Fix: Verify the correct property is linked in the client's Connections. Expand the date range—new sites may have minimal data. Refresh the report after changes.
Property Mismatch
Likely cause: You linked a URL prefix property (e.g., https://www.example.com) but the site also receives traffic on a different subdomain or protocol not covered.
Fix: Link the domain property if available (covers all variations). Or link the specific URL prefix property that matches how the site is accessed.
Token Expired / Reconnect Required
Likely cause: OAuth token expired or was revoked by Google.
Fix: Go to Google Accounts and reconnect. Approve permissions again, then refresh reports.
Rate Limits
Likely cause: Too many refresh requests in a short period.
Fix: Wait a few minutes and retry. Reduce refresh frequency—consolidate actions rather than refreshing repeatedly.
Data Doesn't Match Search Console Interface
Likely cause: Different date ranges, filtering differences, or property type mismatch.
Fix: Verify the report date range matches what you're viewing in Search Console. Confirm you're looking at the same property (domain vs URL prefix can show different data).
Search Console Integration FAQs
Common questions about the Google Search Console integration.
Connect Search Console and Unlock Keyword Reporting
Pull your search performance data into client-ready SEO reports. Connect Search Console in minutes with secure, read-only access.