--- title: Google Search Console API Integration on Truto slug: googlesearchconsole category: Analytics canonical: "https://truto.one/integrations/detail/googlesearchconsole/" --- # Google Search Console API Integration on Truto **Category:** Analytics **Status:** Generally available ## MCP-ready AI tools Truto exposes 10 tools for Google Search Console that AI agents can call directly. - **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. ## How it works 1. **Link your customer's Google Search Console account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Google Search Console.** The Proxy API is a 1-to-1 mapping of the Google Search Console API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **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 - **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. ## FAQs ### 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.