Ship integrations faster
Deliver Search Console features without building connectors from scratch.
Google Search Console Connector
Embed Search Console capabilities inside your product to surface per-tenant search performance, automate sitemap submission and run URL inspections. Build in-app dashboards, scheduled exports and tenant-scoped troubleshooting workflows using the Search Console API.
Tenant-scoped workflows
Map credentials and run per-customer performance pulls and inspections.
Governed MCP tools
Expose selected methods as permissioned, auditable tools for your teams.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate with Google Search Console to query performance (clicks, impressions, CTR, position), list and manage verified properties, submit and audit sitemaps, and call the URL Inspection tool programmatically. Use these methods to build tenant-specific dashboards, scheduled exports and automated sitemap workflows for many customer accounts. (developers.google.com)
PRODUCT USE CASES
Top Use Cases for Google Search Console Integrations
Create integrations with Cyclr’s low-code builder and publish them into your app via Cyclr’s embedded marketplace. Deliver tenant-scoped Search Console reports, automate sitemap submission after publishing, and surface URL inspections without custom connector engineering.
Tenant performance dashboards
Use Search Analytics to show clicks, impressions, CTR and average position per tenant in-app. (developers.google.com)
Automate sitemap submission
Call the Sitemaps endpoints to submit or re-submit sitemaps when content is published, keeping Google up to date. (developers.google.cn)
On-demand URL inspection
Invoke the URL Inspection API (index:inspect) to surface index status and last crawl information for specific tenant URLs. (developers.google.com)
ORCHESTRATION
How Google Search Console works with Cyclr
Cyclr sits between your SaaS product and Google Search Console to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Google Search Console
Google Search Console processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Google Search Console methods you can orchestrate through Cyclr.
Search Analytics2
Search Analytics (URL-Prefix Property)
ActionQuery your search traffic data with filters and parameters that you define.
Search Analytics (Domain Property)
ActionQuery your search traffic data with filters and parameters that you define.
Sites2
Get Site
ActionGet a Search Console site.
List Sites
ActionLists the user's Search Console sites.
TECHNICAL DETAILS
Google Search Console integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Google Search Console integrations in Cyclr.
API and authentication
- API host
https://searchconsole.googleapis.com- Authentication
- OAuth 2.0
- Credentials
OAuth Client ID; OAuth Client Secret; Cyclr Service Domain (redirect URI)
- Method categories
Search Analytics (performance); Sites management; Sitemaps management; URL Inspection
Pagination and rate limits
Pagination
Search Analytics returns top rows and may not return every row; list endpoints (Sites, Sitemaps) use standard list methods and may include page tokens. (developers.google.com)
Rate limits
Subject to Google API quotas and per-method limits; check your project quotas in Google Cloud Console. (developers.google.com)
IMPLEMENTATION
Authentication at a glance
OAuth 2.0: register a Google Cloud project, create an OAuth client ID/secret and add your Cyclr Service Domain as the redirect URI. Confirm Console options in Cyclr. (community.cyclr.com)
- Authentication method
- OAuth 2.0
- Credential required
OAuth Client ID; OAuth Client Secret; Cyclr Service Domain (redirect URI)
Before you begin:
View setup guideRequires custom Cyclr Service Domain and a registered Google Project; re-authentication if domain changes. (community.cyclr.com)
COMMON QUESTIONS
Frequently asked questions
It pulls Search Console performance data, lists and manages verified sites, submits and audits sitemaps, and runs URL inspections. Use these to build tenant-scoped dashboards, scheduled exports and automated sitemap workflows. (developers.google.com)
OAuth 2.0. Register a Google Cloud project, create an OAuth client ID/secret and add your Cyclr Service Domain as the redirect URI so Cyclr can obtain tokens. Project quotas and verification may apply. (community.cyclr.com)
Yes. Cyclr orchestration maps individual tenant credentials and authorized properties so you can surface tenant-specific Search Console reports and inspections inside each account. Tenant properties must be verified or delegated as required by Google. (community.cyclr.com)
Yes. You can expose selected API actions as governed, permissioned MCP tools in Cyclr to control which teams or processes may call Search Console methods. Governance and audit are handled by Cyclr orchestration, not by Google. (community.cyclr.com)
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorAmazon S3
Related Analytics connector for customer-facing integration workflows.
Related connectorDataDog
Related Analytics connector for customer-facing integration workflows.
Related connectorGoogle Analytics
Related Analytics connector for customer-facing integration workflows.