Connect your Google Search Console data to PQ Intel and discover which search queries bring your ideal customer profile to your site. Turn SEO analytics into a lead generation signal source.
The PQ + Google Search Console integration brings your GSC search analytics into PQ Intel's signal engine. By analyzing which search queries drive traffic to your site and cross-referencing that data with PQ's ICP patterns, you can identify which queries are most commonly used by your ideal customers — and which visitors are likely in-market. PQ Intel enriches GSC query data with ICP fit scores, signal classifications, and trend analysis, turning raw search data into actionable prospect intelligence.
Unlike standalone SEO tools that only surface keyword rankings and click-through rates, PQ Intel applies its ICP signal engine to your GSC data to identify high-value search behaviors. The integration detects branded search spikes that indicate prospect research, competitor query crossover where your ICP is comparing alternatives, and emerging keyword themes tied to buying intent. Each signal is assigned a confidence score and surfaced in your Signals feed alongside context from your ICP profiles — so you can prioritize outreach based on demonstrated search behavior rather than guesswork.
The integration runs on a 24-hour refresh cycle, pulling the latest GSC search analytics each day and re-processing it against your active ICP profiles. As you refine your ICP criteria or add new competitor domains for overlap analysis, previously collected data is re-evaluated to surface any newly relevant signals — ensuring no search pattern is missed.
Search queries, pages, clicks, impressions, CTR, and average position — mapped and cross-referenced against PQ Intel's ICP profiles. Results are surfaced as signal types including branded search mentions, competitor query overlap, and ICP-aligned keyword patterns.
PQ Intel ingests six core fields from Google Search Console's Search Analytics API and maps each one to lead intelligence attributes. The table below shows how raw GSC data translates into ICP signals.
| GSC Field | Type | PQ Intel Mapping | Lead Intelligence Use |
|---|---|---|---|
| Query | Direct | Stored as the raw search term; classified against ICP keyword library and competitor brand terms | Identifies branded search mentions, competitor comparisons, and ICP-aligned research queries. Each query is scored for intent level (navigational, informational, transactional). |
| Page | Direct | Mapped to the landing URL; cross-referenced with PQ's content categorization (blog, pricing, product, case study, etc.) | Reveals which content types are attracting ICP traffic. A pricing page visit from a branded query signals high purchase intent; a blog visit from an informational query signals early-stage research. |
| Clicks | Direct | Raw click count per query/page combination; normalized as a trend line over the selected date range | Spike detection: a sudden increase in clicks on branded queries indicates rising prospect interest. Combined with ICP scoring, click volume helps prioritize which signals to act on first. |
| Impressions | Direct | Raw impression count; used as a visibility baseline for calculating CTR and competitive share-of-voice | High impressions with low clicks (low CTR) on ICP-relevant queries suggests a meta-description or ranking position issue — a content optimization signal. Sudden impression loss on branded terms flags a potential ranking drop. |
| CTR | Calculated | Calculated as clicks / impressions; compared against segment averages to flag outliers | A high CTR on ICP-aligned queries confirms strong relevance between your snippet and prospect intent. A low CTR on high-impression branded queries is a red flag that triggers a content review signal. |
| Position | Derived | Average search position per query; tracked over time for trend analysis | Position movements on ICP-targeted keywords are tracked as competitive signals. A ranking drop on a high-value ICP query may indicate a competitor has published competing content — triggering an alert to review and update your page. |
In PQ Intel, go to Settings > Integrations > Google Search Console. Click Connect GSC — this opens Google's OAuth 2.0 consent screen asking for access to your Search Console data.
After authorizing, PQ Intel shows a list of your verified GSC properties (domain or URL-prefix). Select the property you want to analyze. PQ Intel only requests read access — it will not make changes to your GSC settings.
Set your analysis preferences — choose the date range (last 7, 28, or 90 days), minimum impressions threshold, and which query categories to monitor. You can also upload a list of competitor domains for overlap analysis.
Ensure the Google account you authorized has the correct permissions on the GSC property. The account must be listed as an Owner or Full User in GSC's property settings. Restricted users or users with only "Limited" access may not return the full search analytics data set. To verify permissions, go to your GSC property settings > Users and permissions and confirm your account's role.
After selecting your property, enable site-level aggregation in PQ Intel to pull search analytics across all pages on your domain. This step ensures that PQ Intel collects query data for your entire site — not just individual pages or URL patterns. Toggle Include site-level analytics in the connection settings to aggregate clicks, impressions, and position data across your full property. This is especially important for branded search monitoring, where prospects may land on any page on your site.
Once connected, PQ Intel processes your GSC data against your ICP profiles and surfaces insights in the Signals feed. Branded mentions, competitor query overlaps, and ICP-aligned keyword patterns appear as trackable signals with score and context.
Track branded search queries targeting your company and products. PQ Intel alerts you when branded query volume spikes, when new related terms emerge, or when branded impressions come from geographically relevant regions — each is a signal that your ICP is actively researching you.
Upload competitor domains and PQ Intel cross-references their GSC query patterns against yours. Identify queries where you're losing impression share, discover competitor-branded terms that your ICP searches for, and find keyword gaps where competitors rank but you don't — each gap is a signal of unmet demand.
PQ Intel analyzes your GSC query data through the lens of your ICP profiles, identifying clusters of search behavior that correlate with high-value prospects. These patterns inform your content strategy, ad targeting, and outbound messaging — giving you search-powered audience intelligence.
PQ Intel requests the minimum GSC scope: https://www.googleapis.com/auth/webmasters.readonly. This grants read access only — PQ cannot modify your GSC property settings, submit URLs, or make any changes.
PQ Intel only stores aggregated query analytics and ICP cross-reference results. Raw GSC data is not permanently stored — it is processed in memory and the results are cached for up to 24 hours before refreshing.
OAuth tokens are encrypted at rest using AES-256 and stored in PQ Intel's secure credential vault. Tokens are automatically refreshed before expiry and never exposed in logs, client-side code, or API responses.
You can revoke PQ Intel's access at any time from your Google Account's Third-party Apps & Services page. Revocation takes effect immediately — PQ Intel will stop syncing GSC data on the next refresh cycle.
If you run into problems during or after connecting Google Search Console, check the scenarios below for the most common causes and their solutions.
Symptom: The integration shows as connected but the Signals feed and data dashboard remain empty — no queries, pages, or metrics are displayed.
Cause: The most common reason is that the selected GSC property has not been fully verified in Google Search Console. GSC will only return search analytics data for properties that have completed the verification process (DNS record, HTML file upload, Google Analytics, or Google Tag Manager). Additionally, newly verified properties may take 24-48 hours before GSC begins collecting search data.
Fix: Go to Google Search Console, select your property, and confirm the verification badge is active. If the property shows as "Not verified," complete the verification process using one of the supported methods. After verification, allow up to 48 hours for GSC to populate data, then check PQ Intel again.
Symptom: When trying to connect or refresh data, PQ Intel returns an error message stating something like "Access denied" or "User does not have sufficient permissions for this property."
Cause: The Google account used during OAuth authorization does not have the required permissions on the selected GSC property. Even if the account has access to Google Search Console itself, it may only have "Restricted" or "Limited" user permissions that prevent the Search Analytics API from returning full data.
Fix: In Google Search Console, navigate to Settings > Users and permissions for the property. Ensure your account is listed with at least Full User permissions. If you are not the property owner, ask the owner to add your account with the appropriate role. After updating permissions, go back to PQ Intel and click Re-authorize to refresh the connection.
Symptom: The data shown in PQ Intel appears to be 1-2 days old. Today's search data is not visible yet.
Cause: This is expected behavior — Google Search Console's Search Analytics API has an inherent data processing delay of approximately 24 to 48 hours. Data for a given day is not final until GSC finishes processing all queries, clicks, and impressions for that day. PQ Intel pulls the latest available finalized data on each refresh cycle.
Fix: No action needed — this is a GSC platform limitation, not a PQ Intel issue. Check your data again after 24-48 hours. The most recent finalized data available will always be displayed, and PQ Intel notes the data freshness date in the dashboard. If data is more than 72 hours stale, try re-authorizing the connection from Settings > Integrations > Google Search Console.
Symptom: When selecting a GSC property during setup, the property you expect to see does not appear in the list, or PQ Intel reports "Property not found" after selection.
Cause: GSC distinguishes between domain properties (e.g., example.com) and URL-prefix properties (e.g., https://example.com/ or https://www.example.com/). If your GSC property is registered as a domain property but you selected a URL-prefix format (or vice versa), the mismatch causes a "not found" error. Additionally, if you have both https://example.com/ and https://www.example.com/ as separate properties, the data returned depends on which one you select.
Fix: Confirm the exact property URL format used in your GSC account. If you use a domain property, select the bare domain option (no protocol prefix). If you use a URL-prefix property, include the full protocol (https://) and subdomain (www if applicable). When in doubt, add both property types in GSC — PQ Intel can connect to multiple properties to give you the most complete picture.
PQ Intel pulls fresh data from the Google Search Console API once every 24 hours. Each sync retrieves the latest finalized search analytics for your selected date range and date range and re-processes it against your active ICP profiles and competitor domains. You can manually trigger a refresh from the integration settings page if you need updated data sooner.
You can select from three preset date ranges: Last 7 days, Last 28 days, or Last 90 days. The 90-day range provides the most comprehensive trend analysis but includes more data, which may increase processing time. You can change the date range at any time from the integration configuration settings — PQ Intel will re-process data for the new range on the next sync cycle.
Yes. You can connect multiple GSC properties (e.g., separate domains for different product lines, or both example.com and www.example.com as separate URL-prefix properties). Each property connection is independent — you configure signal parameters and ICP profiles per property. All connected properties contribute signals to your unified Signals feed, with the source property labeled on each signal so you know where it originated.
No. PQ Intel processes GSC search analytics in memory and retains only the ICP cross-reference results — which queries were classified as branded mentions, competitor overlaps, or ICP-aligned patterns, along with the associated metrics (clicks, impressions, CTR, position) at the time of analysis. Raw query logs are not permanently stored. Processed results are cached for up to 24 hours to avoid redundant API calls, and the cache is automatically invalidated on each refresh.
Absolutely — that is the primary use case. When PQ Intel identifies a branded search spike or an ICP-aligned query pattern, it surfaces that as a signal in your feed. You can then drill into the signal to see context (which page was visited, what query was used, the trend over time) and use that information to prioritize outreach. For example, a spike in branded navigational queries suggests prospects are actively researching your company — a strong trigger for outreach sequencing. Combined with PQ Intel's other data sources, GSC signals help you time outreach when intent is highest.
If you revoke PQ Intel's access from your Google Account's Third-party Apps & Services page, the integration will stop syncing on the next scheduled refresh cycle. Existing processed signals in your Signals feed will remain visible but will not be updated with new data. To restore the connection, go back to Settings > Integrations > Google Search Console in PQ Intel and click Reconnect to initiate a fresh OAuth authorization. Your signal configuration parameters (date range, thresholds, competitor domains) are preserved even after disconnection.
Connect Google Search Console to PQ Intel and start discovering which queries drive your ideal customers to your site. No credit card required.
View pricing & plansGrowth+ plan required. Free 14-day trial available.