Which search queries bring people to your website?
Google Search Console shows which search queries a website appears for on Google and how often it is clicked. BrandZaps connects read-only and uses this data as real performance evidence.
How the connection is made.
Each source is authorised separately. An error with one source takes nothing away from the others – it appears as a warning on the source concerned.
The connection runs via Google OAuth with its own account selection. BrandZaps reads the data but changes no settings in Search Console.
Google keeps 16 months. BrandZaps backfills this history in full on the first fetch and also keeps its own daily series.
What BrandZaps fetches.
16 months of history, plus its own daily series. The connection delivers data to BrandZaps and changes nothing in the connected accounts.
Where the data makes a difference.
Search Console data does not sit in a separate interface. It confirms topics, points to possible gaps and makes developments visible on the dashboard.
Search queries enrich keywords and topics with real clicks, impressions and positions – but they never create a topic themselves. If an interesting search query fits no topic, it is flagged as a possible gap for review.
DashboardA source card with clicks from Google Search, a sparkline and a comparison with the previous period. If the trend is down, the line turns red.
Project BrainThe data becomes available as part of the project’s knowledge context.
Keyword research only starts once Search Console and Google Analytics 4 are connected and selected. On every new run, BrandZaps syncs both sources – so research and performance data work from the same up-to-date state.
Access tokens are encrypted with AES-256-GCM before they are stored. Sign-in runs via OAuth with PKCE.
All integrations →What already happens on Google becomes part of the strategy – without replacing the strategy.
Google Search Console is connected per project and only ever read.