.png)
Google Search Console Integration Guide
Integrate Google Search Console with enterprise systems through Google OAuth 2.0, REST APIs, scheduled workflows, and transformed performance data.
Google Search Console integration options at a glance
Google Search Console is primarily integrated through REST APIs secured with Google OAuth 2.0 and property-level permissions. Martini can query Search Analytics, list and manage verified properties, submit and monitor sitemap URLs, and request URL Inspection results from scheduled or API-triggered workflows. Search Analytics supports bounded, filtered, dimension-based retrieval rather than unrestricted bulk export. Google Search Console does not provide a confirmed general-purpose webhook or callback mechanism, so recurring workflows are the safer monitoring pattern. Martini can map the returned JSON, apply business rules, handle quotas and retries, and deliver normalized results to databases, reporting platforms, or enterprise applications.
| Integration point | Supported by Google Search Console? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Manage Sites properties, query Search Analytics, submit and manage sitemaps, and request URL Inspection results. | Martini can consume the documented REST endpoints from workflows, map JSON responses, and route results to downstream APIs or databases. |
| Authentication | Yes | Authorize access with Google OAuth 2.0, webmasters scopes, and permissions assigned to the Search Console property. | Martini can store OAuth configuration, client secrets, and refresh-token material in protected environment configuration and use authenticated API calls. |
| Database / analytics access | Limited | Search Analytics provides aggregated performance data grouped by query, page, country, device, date, or search appearance; direct database access is not provided. | Martini can retrieve bounded analytics responses, normalize metrics, and write them to a reporting database or another analytics API. |
| Bulk / async / batch APIs | Limited | Search Analytics supports filtered, bounded queries and result retrieval, while URL Inspection is request-oriented and is not an unrestricted bulk inspection interface. | Martini can partition date ranges, control concurrency, paginate where supported, and checkpoint completed query or inspection work. |
| File / attachment APIs | Limited | Sitemaps are submitted and managed by URL, but Google Search Console is not a general file or attachment repository. | Martini can receive sitemap URLs from deployment or content workflows, submit them, and schedule later status checks. |
| Webhooks / outbound callbacks | Not confirmed | No general-purpose notification mechanism was confirmed for ranking changes, indexing changes, Search Analytics availability, or sitemap processing. | Martini can use scheduler-triggered workflows to poll APIs, compare responses with stored state, and route meaningful changes. |
| GraphQL APIs | Not confirmed | No official Google Search Console GraphQL API was found in the supplied research. | Martini should consume the documented REST APIs rather than assume GraphQL support. |
| SOAP APIs | No | The current Google Search Console API documentation describes REST-based Google APIs and does not provide a current SOAP interface. | Martini can use its REST API consumption capabilities instead of SOAP for this integration. |
How Google Search Console exposes data and business events
Google Search Console REST APIs
Google Search Console exposes REST APIs for Sites properties, Search Analytics, Sitemaps, and URL Inspection. These APIs are the primary integration surface for retrieving authorized performance and indexing information and for submitting sitemap URLs.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with Google OAuth 2.0, calls the appropriate REST endpoint, validates the property context, transforms the JSON response, and sends the result to a target application or durable store. Query and inspection workloads can be scheduled and checkpointed.
Implementation sequence
Search Analytics queries
The Search Analytics API returns aggregated results for selected date ranges, dimensions, filters, row limits, and query configurations. It is designed for bounded reporting queries rather than unrestricted historical export.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow builds a stable query definition, partitions large periods, retrieves available result pages, maps metrics such as clicks and impressions, and writes normalized data to a reporting store while preserving query metadata.
Implementation sequence
Sitemaps and URL Inspection
The Sitemaps API supports submitting and managing sitemap URLs, while URL Inspection supports requests for selected URLs in an authorized property context. Neither should be treated as a general file store or unrestricted crawl interface.
Martini implementation pattern
Martini implementation pattern: an API or workflow receives a sitemap URL or deployed page, verifies the property, submits or inspects it, stores the response, and schedules a later check where processing latency means the initial response is not conclusive.
Implementation sequence
Scheduled monitoring
No general-purpose Search Console webhook or outbound callback mechanism was confirmed for indexing changes, rankings, data availability, or sitemap processing. Recurring API polling is therefore the safer monitoring approach.
Martini implementation pattern
Martini implementation pattern: a scheduler-triggered workflow retrieves selected Search Console resources, compares current results with a stored prior state, applies thresholds and deduplication rules, and sends only meaningful changes to operational or reporting systems.
Implementation sequence
Common Google Search Console integration patterns
Pattern 1: Build scheduled Search Analytics reporting
When to use this pattern
Use this pattern for daily SEO reporting, landing-page analysis, or anomaly detection across one or more authorized Search Console properties. It accommodates delayed data, bounded queries, and reporting-period extraction.
Integration direction
Example Mapping
| Google Search Console Field | Canonical Field | Target Field |
|---|---|---|
| keys.query | searchQuery | search_query |
| keys.page | landingPageUrl | landing_page_url |
| clicks | organicClicks | organic_clicks |
| impressions | searchImpressions | impressions |
Martini implementation pattern
A scheduled Martini workflow authenticates with Google, retrieves a stable Search Analytics query, partitions date ranges when necessary, and maps dimensions and metrics into a reporting model. Business rules can flag high-impression and low-click-through pages. The workflow uses stable property, date, dimension, and query keys to avoid duplicate loads and retries transient API failures.
Martini capabilities used
- workflows
- scheduled execution
- API consumption
- data mapping
- business rules
- error handling
Pattern 2: Submit and monitor sitemaps
When to use this pattern
Use this pattern when a deployment, content platform, or publishing process produces a sitemap URL that should be submitted to Google Search Console and monitored for processing results.
Integration direction
Example Mapping
| Google Search Console Field | Canonical Field | Target Field |
|---|---|---|
| sitemap | sitemapUrl | sitemap_url |
| siteUrl | propertyIdentifier | site_url |
| lastSubmitted | submissionTimestamp | submitted_at |
| isPending | processingPending | processing_pending |
Martini implementation pattern
Martini receives the sitemap URL through an API or workflow, validates the exact property identifier, submits the sitemap, and records the response. A later scheduled workflow retrieves status and applies rules for failed or unexpected processing results. Stable property and sitemap URL keys prevent duplicate submissions and duplicate operational tickets.
Martini capabilities used
- APIs
- workflows
- data mapping
- business rules
- scheduling
- error handling
Pattern 3: Inspect URLs after content deployment
When to use this pattern
Use this pattern for priority pages released by a content platform or deployment process where indexing and coverage status should be recorded and exceptions routed to SEO or engineering teams.
Integration direction
Example Mapping
| Google Search Console Field | Canonical Field | Target Field |
|---|---|---|
| inspectionUrl | pageUrl | url |
| indexStatusResult | indexingStatus | indexing_status |
| coverageState | coverageStatus | coverage_status |
| mobileUsabilityResult | mobileUsabilityStatus | mobile_usability_status |
Martini implementation pattern
A Martini API or workflow accepts the deployed URL and property, calls URL Inspection, and maps the response into an internal status model. The workflow prioritizes actionable results, accounts for indexing latency, and creates or updates a Jira issue using the URL and inspection timestamp as a deduplication key. Permission and quota errors are surfaced rather than retried indefinitely.
Martini capabilities used
- APIs
- workflows
- data mapping
- business rules
- deduplication
- error handling
Pattern 4: Synchronize SEO exceptions with operations
When to use this pattern
Use this pattern when Search Console performance, sitemap, or inspection results must be compared over time and converted into controlled work items for operational follow-up.
Integration direction
Example Mapping
| Google Search Console Field | Canonical Field | Target Field |
|---|---|---|
| property | siteProperty | configuration_item |
| page | affectedUrl | affected_url |
| clickThroughRate | organicCtr | u_organic_ctr |
| inspectionStatus | issueStatus | state |
Martini implementation pattern
Martini polls selected resources on a rate-aware schedule, loads the previous state, and applies thresholds for indexing failures, sitemap errors, or material performance changes. It creates or updates ServiceNow work items, suppresses repeated observations, and retains source responses or correlation identifiers for auditability. Transient API failures use bounded retries with backoff.
Martini capabilities used
- scheduled workflows
- API consumption
- state management
- business rules
- data transformation
- retry handling
Applications commonly integrated with Google Search Console
Google Search Console data is often combined with analytics, content, commerce, CRM, and operational systems. These are typically API-led enterprise architecture patterns rather than dedicated native integrations; Martini can orchestrate the calls, normalize data, and apply routing and quality rules.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Google Analytics 4 | Combine organic search queries and landing-page performance with sessions, engagement, and conversion data. | Google Search Console → Martini → Google Analytics 4 or reporting data store | Schedule Search Analytics extraction, normalize page and date dimensions, correlate results with Google Analytics 4 data, and persist or publish the combined metrics with duplicate protection. |
| Looker Studio | Build dashboards that combine Search Console performance with marketing and business metrics. | Google Search Console → Martini → Looker Studio | Query bounded reporting periods, map Search Analytics dimensions and metrics into a reporting model, and expose or load the normalized dataset for dashboard consumption. |
| Salesforce | Relate organic landing-page performance to leads, opportunities, campaigns, and acquisition reporting. | Google Search Console → Martini → Salesforce | Match page, campaign, or property data to Salesforce business records, apply thresholds such as high impressions and low click-through rate, and write prioritized insights or campaign context. |
| Shopify | Connect search performance for product and collection URLs with catalog and merchandising data. | Shopify → Martini → Google Search Console reporting store | Retrieve Shopify catalog URLs, correlate them with Search Analytics page results, and store normalized product-performance metrics while handling missing or changed URLs. |
| WordPress | Associate published content with sitemap submission, indexing checks, and search performance. | WordPress → Martini → Google Search Console | Receive publication information, identify the relevant property, submit the sitemap URL when required, and schedule URL Inspection or reporting workflows for selected content. |
| Contentful | Correlate published headless-content entries with URL Inspection and Search Analytics results. | Contentful → Martini → Google Search Console and reporting store | Use content publication events or scheduled retrieval to identify URLs, inspect selected pages, map results to content identifiers, and persist status and performance history. |
| Jira | Create engineering or SEO work items from indexing, sitemap, or performance exceptions. | Google Search Console → Martini → Jira | Run scheduled checks, compare current results with stored state, apply issue-creation and deduplication rules, and submit actionable exceptions to Jira. |
| ServiceNow | Route website indexing and search-performance exceptions into operational workflows. | Google Search Console → Martini → ServiceNow | Poll relevant Search Console resources, classify failures or threshold breaches, suppress duplicate cases using stable keys, and create or update ServiceNow work items. |
How to build a Google Search Console integration in Martini
Objective
Establish Google authorization and property access before building data flows. Google Search Console requires OAuth 2.0 and the authenticated principal must have appropriate permission for each property.
Instructions in Martini
- Configure Google OAuth 2.0 settings and required webmasters scopes
- Store client secrets and refresh-token material in protected environment configuration
- Enable the Google Search Console API in the relevant Google Cloud project
- Validate each exact URL-prefix or domain property identifier
Objective
Select a schedule or controlled API entry point because a general-purpose Search Console webhook mechanism was not confirmed.
Instructions in Martini
- Use a scheduler for recurring Search Analytics, sitemap, or inspection checks
- Use a Martini API or workflow entry point for deployment-driven sitemap and URL inspection requests
- Set reporting delays so incomplete Search Analytics dates are not treated as final
- Control concurrency across properties and inspection workloads
Objective
Call the appropriate Search Console REST API and retrieve bounded, authorized responses.
Instructions in Martini
- Query Search Analytics with explicit dates, dimensions, filters, and row limits
- Call Sites operations when validating properties and permissions
- Submit or retrieve sitemap resources by URL
- Request URL Inspection only for prioritized URLs
Objective
Coordinate multi-step processing, checkpoints, follow-up checks, and downstream actions in a maintainable Martini workflow.
Instructions in Martini
- Separate extraction, transformation, validation, and delivery stages
- Store query definitions, request timestamps, and prior state where comparisons are required
- Schedule delayed sitemap or inspection follow-up checks
- Route authentication, permission, quota, and resource-specific failures separately
Objective
Convert Google Search Console JSON into canonical reporting, content, or operational models without losing important source context.
Instructions in Martini
- Map query, page, country, device, date, and search appearance dimensions explicitly
- Normalize clicks, impressions, click-through rate, and average position
- Preserve optional fields and raw responses when auditability is important
- Apply stable identifiers for properties, URLs, date ranges, and query configurations
Objective
Use business rules to identify meaningful changes and prevent repeated or low-value downstream actions.
Instructions in Martini
- Flag high-impression and low-click-through pages when appropriate
- Prioritize inspection results requiring content or engineering attention
- Suppress duplicate sitemap submissions and operational issues
- Retry only transient API and transport failures
Common Google Search Console data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Sites / properties | Represent verified URL-prefix or domain properties and provide property permission information. | Configuration stores, governance systems, reporting databases | Martini stores the exact property identifier, validates access during initialization, and uses it in subsequent API requests. |
| Search Analytics queries and results | Report clicks, impressions, click-through rate, and average position by query, page, country, device, date, or search appearance. | Reporting databases, Google Analytics 4 data models, Looker Studio, Salesforce | Martini creates stable query definitions, partitions date ranges when needed, maps JSON metrics, and persists raw or normalized results. |
| Sitemaps | Submit, list, retrieve, and delete sitemap resources associated with a property. | WordPress, Contentful, deployment systems, ServiceNow | Martini receives sitemap URLs, submits them, stores timestamps and responses, and schedules status checks with idempotency controls. |
| URL Inspection results | Assess indexing status, coverage, mobile usability, and available rich-result information for a specified URL. | Content platforms, SEO operations, Jira, ServiceNow | Martini calls inspection for prioritized URLs, maps the response into an internal status model, and routes exceptions without treating the API as a crawler. |
| Inspection requests | Represent requests to inspect a URL in the context of a specific Search Console property. | Content release workflows, URL monitoring stores, operational systems | Martini validates the property and URL, throttles request workloads, records inspection timestamps, and prevents duplicate processing. |
Authentication and security considerations
Google authorization and property access
Google Search Console APIs use OAuth 2.0 and require the authenticated user or service account to have appropriate access to the requested property. The Google Search Console API must also be enabled in the relevant Google Cloud project.
Credential protection
Store OAuth client secrets, refresh tokens, and related configuration in protected Martini environment configuration or secrets management rather than embedding credentials in workflows.
Data protection
- Restrict access to stored Search Analytics responses and URL-level results.
- Use read-only authorization when management operations are not required.
- Validate property identifiers and permissions for every configured property.
Operational considerations for Google Search Console integrations
Quotas and data availability
Search Analytics queries are bounded by quotas, response limits, aggregation behavior, and data latency. Use date partitioning, controlled row limits, rate-aware scheduling, and a reporting delay for incomplete periods.
Pagination and inspection scope
Handle supported result continuation carefully and do not model URL Inspection as an unrestricted crawl or bulk index export. Prioritize URLs and throttle inspection workloads.
Reliability and idempotency
- Retry transient Google API or transport failures with bounded exponential backoff.
- Do not retry authentication or property-permission failures indefinitely.
- Use stable keys for property, date range, dimensions, sitemap URL, and inspection timestamp.
- Tolerate optional JSON fields and preserve raw responses when auditability is required.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond a script
Martini provides reusable workflows and APIs for coordinating authentication, extraction, transformation, validation, downstream delivery, and delayed follow-up checks. This is useful when Search Console data must be combined with content, analytics, CRM, or operational systems.
Maintainable integration logic
Mappings, business rules, checkpoints, retries, and error paths can be maintained as explicit integration assets rather than scattered across one-off scripts or point-to-point calls.
Controlled enterprise delivery
- Expose controlled Martini APIs for deployment-driven sitemap or inspection requests.
- Use scheduled workflows for polling where Search Console does not provide confirmed webhooks.
- Apply consistent deduplication, monitoring, and environment-specific security configuration.
Frequently asked questions
Google Search Console is integrated primarily through its REST APIs using Google OAuth 2.0 and property-level permissions. Enterprise workflows can query Search Analytics, manage sitemap URLs, inspect selected URLs, validate properties, and deliver transformed results to databases, reporting platforms, content systems, or operational applications.
Yes. Martini can integrate with Google Search Console by consuming its documented REST APIs from workflows and APIs. It can authenticate with Google OAuth 2.0, query Search Analytics, submit or monitor sitemaps, request URL Inspection results, transform JSON, and deliver results to other systems.
No. A dedicated Google Search Console connector is not required. Martini can use Google Search Console’s native REST APIs, Google OAuth 2.0 authentication, property permissions, scheduled workflows, and API-triggered workflows.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Google Search Console. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Google, cloud infrastructure, or other third-party systems based on subscription, API usage, and deployment model.
Use the documented REST APIs for Sites properties, Search Analytics, Sitemaps, and URL Inspection. Search Analytics is query-oriented and bounded, while URL Inspection should be used for prioritized URLs rather than unrestricted crawling. No current official GraphQL or SOAP API was confirmed.
A general-purpose Google Search Console webhook or outbound callback mechanism was not confirmed. Martini should use scheduled workflows to poll Search Analytics, sitemap status, or URL Inspection results, compare them with stored state, and route meaningful changes.
Martini can use scheduled or API-triggered workflows to retrieve bounded results, partition date ranges, map dimensions and metrics into canonical models, and write them to databases or applications. Stable property, URL, date-range, and query keys support idempotent loads and deduplication.
Workflows should use controlled scheduling, bounded queries, rate-aware concurrency, pagination where supported, and exponential backoff for transient failures. Authentication, permission, invalid-parameter, and quota issues should be classified separately. Stable keys for reports, sitemap submissions, inspections, and downstream issues help prevent duplicates.
Related Martini documentation
Integrate Google Search Console with Martini
Use Martini to connect Google Search Console REST APIs with reporting, content, analytics, CRM, and operational systems through secure workflows, reusable APIs, and controlled data synchronization.