Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Decisions first
Authenticate with read-only Search Console scope, inventory accessible properties, query Search Analytics in bounded date windows with explicit type, dimensions, filters, aggregation, rowLimit, startRow, and dataState, then store raw source-labelled rows before deriving page jobs. Treat returned query rows as top data rather than a guaranteed exhaustive export.
- Property, search type, aggregation, dimensions, timezone, and data state belong in every extract.
- The API can return top rows under internal limits; absence from an extract is not proof of zero demand.
- Automate candidate detection, then require diagnosis before changing a page.
Define an extract contract
A reusable Search Console job names the property, date window, search type, data state, dimensions, filters, aggregation, and pagination behavior before it requests data.
Search Analytics supports dimensions such as query, page, country, device, date, hour, and search appearance, with filters and aggregation choices. The date boundary is Pacific Time, not necessarily the business timezone. Store the request body and extraction timestamp beside the response.
Use the webmasters.readonly scope for analysis. Inventory Sites access and fail if the expected domain or URL-prefix property is missing. Domain and URL-prefix properties are not interchangeable identifiers; switching them silently changes the dataset.
| Parameter | Decision | Common error |
|---|---|---|
| siteUrl | Exact GSC property | Mixing domain and URL-prefix data |
| type | Web, image, video, news, or discover | Combining unlike search surfaces |
| dimensions | Grain needed for the question | Exploding sparse rows |
| aggregationType | Property or canonical page logic | Comparing incompatible totals |
| dataState | Final or fresh monitoring | Treating partial data as settled |
Paginate without pretending the export is complete
Use a rowLimit up to the documented 25,000 and advance startRow until an empty response, but retain Google's warning that Search Analytics may return top rows rather than every row.
For high-volume properties, split work into useful grains and dates rather than requesting query, page, country, device, and date for a long period in one giant job. Compare control totals at a coarser grain and alert when detail coverage changes unexpectedly.
Preserve null and zero distinctions, original URLs, query case, and response aggregation type. Normalize canonical page identity in a derived table, never by overwriting raw URLs. Backfills and daily incremental loads should use the same contract and versioned transformation rules.
Turn rows into diagnostic candidates
Use transparent rules to flag striking-distance demand, CTR opportunities, decay, cannibalization, and new query-page matches; each flag remains a hypothesis until a person inspects context.
A CTR flag needs sufficient impressions and comparable device or country mix. A decay flag needs matched periods and should decompose impressions, CTR, and position. A cannibalization flag needs multiple URLs sharing a query cluster and may still be legitimate when the pages serve different intents.
Attach the supporting rows and rule version to the candidate. The operator then chooses refresh, new page, consolidation, snippet change, internal linking, technical investigation, or no action. Automation earns trust by making the evidence easy to challenge.
- Striking-distance query cluster
- High-impression CTR gap
- Matched-window decay
- Multi-URL query overlap
- New demand without a strong page
Schedule for stable decisions
Use fresh data for monitoring with an explicit partial-data label, and finalized data for scorecards, experiments, and historical decisions.
Run a daily incremental extraction for incident awareness, a weekly page-query decision job, and a monthly frozen snapshot for governance. Alert on authentication failure, missing property, empty control totals, schema change, incomplete pagination, and late data—not merely on traffic movement.
SearchHandled's Search Console connection is read-only and operational today. The Growth Map can use the site's own Search Console evidence, but any derived priority remains a recommendation with visible limits, not a ranking guarantee.
Continue the workflow
Run one 28-day page-query extract, reconcile its coarse totals, test pagination and fresh-data labels, then review ten generated candidates by hand.
- Google Search Console integration: connect the operational read-only data source
- Search Console operator guide: turn the extract into a weekly decision routine
- content decay automation: implement one conservative diagnostic rule
Questions teams ask
- How many Search Analytics rows can one API request return?
The current rowLimit range is 1 to 25,000, with 1,000 as the default. Use startRow pagination, while recognizing that the API does not guarantee every data row.
- What dimensions should an automated GSC report use?
Use only the grain needed for the decision. Page and query support content work; date supports trends; country, device, and search appearance explain mix changes but increase sparsity.
- Can Search Console API automation update pages automatically?
It can identify candidates, but a metric change is not a diagnosis. Review intent, SERP, page job, technical state, and business consequence before choosing an intervention.
Primary sources
The SearchHandled Editorial Team prefers first-party documentation and names the limits of each source. Links were checked on the access date.
- Google for Developers: Search Console API referenceAccessed August 29, 2026
- Google for Developers: Search Analytics: queryAccessed August 29, 2026 · The API can return top rows rather than a guaranteed exhaustive dataset.
- Google for Developers: Getting your performance dataAccessed August 29, 2026
- Google Search Console Help: Performance report: clicks, impressions, CTR, and positionAccessed August 29, 2026
- Google Search Central: Creating helpful, reliable, people-first contentAccessed August 29, 2026 · Quality guidance, not a guarantee that a page will rank.
