Skip to main content
Use the @bijection/connectors/google-search-console entrypoint to declare Google Search Console resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Search analytics

daily: Daily search analytics settled by first_incomplete_date

The following example matches configuration queries.

Configuration: queries

Case: google-search-console/searchAnalytics/daily/queries. Connection and resource configuration are declared by this exact case. Credential kind: google-search-console. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: searchAnalytics
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Daily search analytics from POST https://www.googleapis.com/webmasters/v3/sites/{siteUrl}/searchAnalytics/query, one Pacific Time day per request, with date first and the declared dimensions after it, and dataState: "all" so fresh days are answered too. Rows are keyed by their dimension values. clicks and impressions are exact integers; ctr and position are Google’s own ratio and average, published as the floating point numbers sent. Google withholds anonymized queries, so query rows do not sum to the day’s totals. settled is Google’s own statement: a day before metadata.first_incomplete_date, or any day when the response names none. Google states data is typically available after two to three days and final data does not change, so restatementDays defaults to five. Pages are startRow offsets of up to 25,000 rows held in the engine-owned position; Search Console states no cursor, and rows of a fresh day can move between two pages of one read. The connection holds a google-search-console OAuth credential (searchConsole.credential, scope webmasters.readonly; a service account added as a property user works through the JWT bearer grant); setup names siteUrl (sc-domain:example.com or a URL-prefix property). Nothing here has run against Google or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.