Google Search Console

The Google Search Console app connects Search Console to Sprigr Team. Agents can query search analytics (clicks, impressions, CTR and position) across web, image, video, news, Discover and Google News, by query, page, country, device, date, hour and search appearance, inspect a URL’s index status, mobile usability and rich results, and manage sites and sitemaps. A scheduled import mirrors 16 months of search performance into month-sharded data indexes so search data can be queried next to the rest of your data.

Note

Google Search Console ships as a marketplace app with per-user connections. Each person links their own Google account and sees only the properties Google permits for that identity. The scheduled import runs as one nominated connection.

Prerequisites

• A Google account with access to the Search Console properties you want agents to report on. The import needs owner or full access on a property.
• Admin or Owner role in your Sprigr Team organisation to install the app. Any member can connect their own Google account once it is installed.

Installing and connecting

1. Install the app

   Sign in to team.sprigr.com, open Apps in the sidebar, find Google Search Console under Available, and install it. See Installing Apps.

2. Connect your Google account

   Ask your agent to connect Google Search Console. It calls start_google_search_console_oauth and hands you a Google consent link bound to you. Approve it, and the app lists your properties; if exactly one is verified it becomes your default. Consent links expire after 24 hours. You can also use the connect link on the app’s settings page while signed in to Sprigr.

3. Choose the reporting connection for the import

   With no explicit choice, the import acts as the earliest connected person with a default property. Any connected person can nominate their own connection with gsc_set_reporting_connection; an owner or admin can nominate another connected person, and optionally restrict the import to specific properties.

4. Check the connection

   Ask your agent “Which Search Console properties can you see?” It calls list_sites through the google_search_console tool.

Try asking your agent

“Which queries gained the most clicks in the last 28 days compared with the 28 before?”

“Which pages rank between position 8 and 15 for queries with over 500 impressions?”

“Is /pricing indexed, and does it pass mobile usability?”

Search performance import and data indexes

Every 15 minutes the import walks each property one report date at a time, per grain, into four month-sharded indexes: site daily (by search type, country and device), pages, queries, and query-by-page daily. The first pass backfills 16 months; after that a rolling refresh keeps recent days current as Google finalises them. Days that hit Google’s per-day row cap are recorded as truncated so the index is read as a floor, not a total.

• gsc_import_status shows which connection the import acts as (and why, or why none qualifies), the property allowlist, and per property and grain the phase, cursor date, days done, rows imported and truncated days.
• gsc_import_restart resets the walk for everything, one property or one grain. Rows are upserted on deterministic ids, so nothing is duplicated or deleted.

What agents can do

The app exposes a single google_search_console tool that takes an action, with 15 actions:

• Search analytics: query_search_analytics with every search type, dimension, filter (including regex and contains) and data state, paged to 25,000 rows; export_search_analytics paginates everything.
• URL inspection: inspect_url for index status, AMP, mobile usability and rich results.
• Sites: list_sites, get_site, add_site, delete_site, set_default_site.
• Sitemaps: list_sitemaps, get_sitemap, submit_sitemap, delete_sitemap.
• Connection: get_connection, disconnect, list_actions.

Deleting a site or a sitemap pauses for your confirmation in the chat.

Common use cases

• Monthly SEO report. A scheduled workflow reports clicks, impressions, CTR and average position by month, with the top movers among queries and pages.
• Striking-distance queries. The agent lists queries ranking just off page one with high impressions, for content work.
• Indexing checks after a release. “Are the new product pages indexed?” runs URL inspection on each.
• Cannibalisation. Query-by-page data shows queries where several pages compete.
• Sitemap hygiene. The agent lists sitemaps, their last-read time and errors, and resubmits after a site change.

Troubleshooting

Not connected You have not linked your Google account. Ask the agent to connect Google Search Console and approve the link it gives you.

A property is missing The app shows the properties your Google identity can access. Ask a property owner to add you, then reconnect. The import only covers properties where the nominated connection has owner or full access.

The import is not running No connected person qualifies as the reporting connection. gsc_import_status explains why; nominate one with gsc_set_reporting_connection.

Numbers differ from the Search Console UI Google’s API applies the same sampling and row caps as the UI, but the import records days that hit the cap as truncated. Recent days also change until Google finalises them.

Next steps

• Google Analytics: Sessions and conversions for the same pages.
• Google Merchant Center: Shopping listings and their performance.
• Integrations Overview: See all available integrations.