Analytics
Google Search Console
API integration
Ship Analytics features without building the integration. Full Google Search Console API access via Proxy and 10+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Talk to usUse Cases
Why integrate with Google Search Console
Common scenarios for SaaS companies building Google Search Console integrations for their customers.
Embed organic search analytics in your reporting platform
Marketing analytics and BI SaaS can let customers connect their Google Search Console account to pull clicks, impressions, CTR, and position data alongside other channels. This gives agencies and in-house teams a single pane for organic performance without manual CSV exports.
Automate sitemap submission for CMS and site builders
CMS, e-commerce, and website builder platforms can automatically submit and monitor sitemaps whenever customers publish or restructure content. This removes the manual GSC setup step and markets your product as fully SEO-automated out of the box.
Ship a content decay monitor for SEO teams
Content optimization tools can compare rolling query performance per URL to detect ranking drops and declining impressions. Flagging decaying content as actionable tasks saves content teams hours of spreadsheet work and drives retention.
Monitor indexation for programmatic and large-scale sites
Programmatic SEO platforms, publishers, and enterprise sites can inspect URLs on a schedule to confirm pages are indexed by Google. Catching deindexation or 'crawled - currently not indexed' states early protects organic revenue.
Offer agency-grade multi-site onboarding
Agency management and white-label SEO SaaS can programmatically add client domains as GSC properties and list all accessible sites. This streamlines onboarding across dozens of clients without logging into the GSC UI.
What You Can Build
Ship these features with Truto + Google Search Console
Concrete product features your team can ship faster by leveraging Truto’s Google Search Console integration instead of building from scratch.
Keyword and page performance dashboards
Pull search analytics grouped by query, page, country, or device to render in-product dashboards with Google's exact (non-sampled) click and impression data.
Automated sitemap lifecycle manager
Submit new sitemaps on publish, list existing sitemaps, and surface Google's warnings or errors natively inside your product's UI.
URL inspection and indexation alerts
Run scheduled URL inspections on high-value pages and trigger alerts when a page drops from Google's index or returns coverage issues.
Historical search data warehouse
Ingest search analytics daily to extend GSC's 16-month retention window and offer customers multi-year keyword and ranking history.
Multi-property site management
Let customers list, add, and remove GSC site properties from inside your app so they can manage portfolios of domains without leaving your product.
Content decay and ranking drop detector
Compare rolling windows of query-level data per URL to flag pages where position or clicks have dropped, and push the alerts into your workflow tools.
SuperAI
Google Search Console AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_google_search_console_sites
List the Google Search Console sites the authenticated user has access to, together with each site's permission level. Returns: siteUrl, permissionLevel.
get_single_google_search_console_site_by_id
Get a single Google Search Console site by id — the site's URL as defined by Search Console (e.g. http://www.example.com/ for a URL-prefix property or sc-domain:example.com for a Domain property). Returns: siteUrl, permissionLevel. Required: id.
create_a_google_search_console_site
Add a site to the user's Google Search Console sites. Returns an empty response body on success. Required: site_url (e.g. http://www.example.com/ for a URL-prefix property or sc-domain:example.com for a Domain property).
delete_a_google_search_console_site_by_id
Remove a site from the user's Google Search Console sites by id (the site URL, e.g. sc-domain:example.com). Returns an empty 204 response on success. Required: id.
list_all_google_search_console_sitemaps
List the sitemaps submitted for a site in Google Search Console, including entries from a sitemap index file. Returns: path, lastSubmitted, isPending, isSitemapsIndex, lastDownloaded, warnings, errors, contents. Required: site_url.
get_single_google_search_console_sitemap_by_id
Get a single sitemap in Google Search Console by id (the sitemap's feedpath URL). Returns the sitemap resource including path, lastSubmitted, isPending, isSitemapsIndex, type, lastDownloaded, warnings, errors, and contents. Required: id, site_url.
google_search_console_sitemaps_submit
Submit a sitemap for a site in Google Search Console so Google crawls and processes it. Returns an empty 204 response on success. Required: feedpath (the URL of the sitemap to add), site_url.
delete_a_google_search_console_sitemap_by_id
Delete a sitemap from a site in Google Search Console by id (the sitemap's feedpath URL). Returns an empty 204 response on success. Required: id, site_url.
list_all_google_search_console_search_analytics
Query Google Search Console search traffic data for a property, grouped by dimensions you define. Returns rows with keys, clicks, impressions, ctr, and position, sorted by clicks descending. Required: site_url, startDate, endDate. Max 25,000 rows per request; Search Console may return only top rows, not all data.
google_search_console_url_inspection_search
Inspect a URL's index status in Google Search Console. Returns the UrlInspectionResult object detailing the URL's index status. Required: inspectionUrl, siteUrl. Only the version in Google's index is checked; live URL testing is not supported.
Why Truto
Why use Truto’s MCP server for Google Search Console
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 850+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Go live with Google Search Console in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Google Search Console account
Use Truto’s frontend SDK to connect your customer’s Google Search Console account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Google Search Console
Truto’s Proxy API is a 1-to-1 mapping of the Google Search Console API. You call us, we call Google Search Console, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Google Search Console’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Google Search Console on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How do end users authenticate their Google Search Console account?
Google Search Console uses OAuth 2.0. Truto handles the full OAuth flow, token storage, and refresh, so your users just click 'Connect' and grant access to the properties they manage.
Which Google Search Console operations are supported?
Truto exposes tools for listing, retrieving, creating, and deleting sites; listing, retrieving, submitting, and deleting sitemaps; querying search analytics; and running URL inspections.
How much historical search data is available?
The Google Search Console API returns up to 16 months of search analytics data. If you need longer retention, you can use Truto to pull data on a schedule and warehouse it in your own storage.
What are the API limits I should plan for?
Search analytics requests are capped at 25,000 rows per call and Google enforces per-site and per-user QPS quotas. Truto handles pagination and retries, and you should design ingestion jobs to batch queries by date, page, or query dimension.
Can I programmatically add new sites for my customers?
Yes. You can use the create site tool to add URL-prefix or sc-domain properties, though the underlying domain still needs to be verified in Google before data becomes available.
How fresh is the data returned by the search analytics endpoint?
Google Search Console data typically has a 2-3 day lag. The URL inspection endpoint returns the current index state in near real time, which is useful for indexation monitoring workflows.
Google Search Console
Get Google Search Console integrated into your app
Our team understands what it takes to make a Google Search Console integration successful. A short, crisp 30 minute call with folks who understand the problem.