# Google Search Console
Your Toolhouse AI Worker can connect to Google Search Console using 9 specialized tools.
## Auth Connection
This service requires an auth connection to use its tools. You can set this up in your Toolhouse dashboard under [Auth Connections](https://toolhouse.app/auth-connections?authkit_slugs=google_search_console).
## Tools (9)
### `Google Search Console Add Site`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_ADD\_SITE**
Adds a site to the set of the user's sites in Google Search Console. This action registers a new property (site) in Google Search Console for the authenticated user. After adding the site, you will need to verify ownership through one of the available verification methods. The site URL must be properly formatted as either a URL-prefix property (with protocol) or a domain property (with sc-domain prefix).
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| ---------- | ------ | :------: | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `site_url` | string | ✅ | `"https://www.example.com/"` | The site URL to add to Google Search Console. For URL-prefix properties, use the full URL with protocol (e.g., ''). For domain properties, use the sc-domain format (e.g., 'sc-domain:example.com'). The site will need to be verified after being added. |
***
### `Google Search Console Delete Site`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_DELETE\_SITE**
Removes a site from the user's Google Search Console sites. This action permanently removes a site property from the authenticated user's Search Console account. The site URL must be URL-encoded. Use this when you need to unregister a site from tracking in Search Console.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| ---------- | ------ | :------: | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `site_url` | string | ✅ | `"http://www.example.com/"` | The site URL to remove from Google Search Console. For URL-prefix properties, use the full URL with protocol (e.g., ''). For domain properties, use the sc-domain format (e.g., 'sc-domain:example.com'). The site must be currently registered in Search Console for the authenticated user. |
***
### `Google Search Console Get Site`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_GET\_SITE**
Retrieves information about a specific Search Console site. Use when you need to get site details including permission level for a specific property.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| ---------- | ------ | :------: | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `site_url` | string | ✅ | `"http://www.example.com/"` | The URL of the property to retrieve, as defined by Search Console. Examples: (for a URL-prefix property) or sc-domain:example.com (for a Domain property). |
***
### `Google Search Console Get Sitemap`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_GET\_SITEMAP**
Retrieves sitemap metadata (submitted/indexed counts, errors, warnings, last-submission timestamps) for a specific sitemap in Search Console. Returns metadata only, not raw XML content. Note: numeric fields like `errors`, `warnings`, `submitted`, and `indexed` may be returned as strings; cast to int before comparisons. Values such as `contents.indexed` can lag several days after submission.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| ---------- | ------ | :------: | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| `feedpath` | string | ✅ | `"https://www.example.com/sitemap.xml"` | The URL of the sitemap to retrieve. For example: |
| `site_url` | string | ✅ | `"https://www.example.com/"` | The site's URL, including protocol. For example: For domain properties, use `sc-domain:example.com` format instead. |
***
### `Google Search Console Inspect Url`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_INSPECT\_URL**
Inspects a URL for indexing issues and status in Google Search Console. Results may reflect cached data lagging real changes by several days. High-volume use can trigger 429 quota errors; limit to priority URLs.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| ---------------- | ------ | :------: | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| `site_url` | string | ✅ | `"https://www.example.com/"` | The URL of the property as defined in Search Console. URL-prefix properties must include a trailing slash. For example: |
| `language_code` | string | | `"en-US"` | IETF BCP-47 language code for localizing the inspection results. For example: en-US, es-ES, fr-FR |
| `inspection_url` | string | ✅ | `"https://www.example.com/page"` | The fully-qualified URL to inspect. Must be a page under the site specified in site\_url. For example: |
***
### `Google Search Console List Sitemaps`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_LIST\_SITEMAPS**
Lists all sitemaps for a site in Google Search Console. Response fields `errors`, `warnings`, `contents.submitted`, and `contents.indexed` may be returned as strings; cast to integers before numeric operations. Evaluate these fields alongside `isPending` for sitemap health.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| --------------- | ------ | :------: | ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `site_url` | string | ✅ | `"https://www.example.com/"` | The site's URL, including protocol. For example: Must exactly match the Search Console property string — include trailing slash for URL-prefix properties or use `sc-domain:example.com` format for domain properties. An inexact match silently returns no data. |
| `sitemap_index` | string | | `"http://www.example.com/sitemapindex.xml"` | A URL of a site's sitemap index file (e.g., ). When specified, lists the sitemaps contained within this sitemap index file instead of all sitemaps for the site. |
***
### `Google Search Console List Sites`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_LIST\_SITES**
Lists all verified sites (properties) owned by the authenticated user in Google Search Console. Response contains a siteEntry array — always iterate it, never assume a single object. Each entry includes permissionLevel, which varies per site; do not assume owner-level access for all returned properties. When calling downstream tools, use the site\_url value exactly as returned, including protocol, subdomain, sc-domain: prefix, and trailing slash — any deviation causes empty results or permission errors. Empty siteEntry may indicate missing OAuth scopes or no verified properties. Newly added properties may not appear immediately due to propagation delay.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
*No parameters required.*
***
### `Google Search Console Search Analytics Query`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_SEARCH\_ANALYTICS\_QUERY**
Queries Google Search Console for search analytics data including clicks, impressions, CTR, and position metrics. Only returns URLs with at least one impression; missing rows do not confirm non-indexing. Position is an impression-weighted average rank.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| ------------------------- | ------- | :------: | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `end_date` | string | ✅ | `"2023-12-31"` | The end date of the date range for the query, in YYYY-MM-DD format. |
| `site_url` | string | ✅ | `"https://www.example.com/"` | The site's URL, including protocol (e.g., ) or a domain property (e.g., sc-domain:example.com). URL-prefix properties specify exact protocol and path, while domain properties aggregate data across all subdomains and protocols. |
| `row_limit` | integer | | — | The maximum number of rows to return. Must be between 1 and 25,000. Note: The API returns top results sorted by clicks (or date when grouping by date). Must be between 1 and 5000. Use start\_row to paginate; stop when response rows < row\_limit. |
| `start_row` | integer | | — | The first row to return from the result set. Used for pagination. |
| `data_state` | string | | `"final"` | The data state to return. |
| `dimensions` | array | | `["query","page"]` | The dimensions to group the data by. Results are sorted by clicks descending, except when grouping by date (sorted by date ascending). |
| `start_date` | string | ✅ | `"2023-01-01"` | The start date of the date range for the query, in YYYY-MM-DD format. Data lags 2–3 days (UTC); most recent 1–2 days may be incomplete. Data retention is \~16 months; older ranges return zero rows. |
| `search_type` | string | | `"web"` | The search type to filter results by. |
| `aggregation_type` | string | | `"auto"` | How data is aggregated. |
| `dimension_filter_groups` | array | | — | Optional filters to apply to dimensions. Each filter group contains an array of filters with structure: \[{'filters': \[{'dimension': 'country', 'operator': 'equals', 'expression': 'USA'}]}]. Operators: equals, notEquals, contains, notContains, includingRegex, excludingRegex. Invalid dimension names, unsupported operators, or mismatched expressions return zero rows without an error — verify each filter before trusting empty results. |
***
### `Google Search Console Submit Sitemap`
Integration name: **GOOGLE\_SEARCH\_CONSOLE\_SUBMIT\_SITEMAP**
Submits a sitemap to Google Search Console for indexing. This action registers or resubmits a sitemap for a verified property in Google Search Console. The sitemap file must be accessible at the specified URL and properly formatted as XML. Supported sitemap types include standard sitemaps, sitemap index files, RSS feeds, and Atom feeds. The authenticated user must have site owner or full user permissions for the property. After submission, Google will crawl and process the sitemap according to its standard indexing schedule.
#### Parameters
Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called.
| Parameter | Type | Required | Example | Description |
| ---------- | ------ | :------: | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `feedpath` | string | ✅ | `"https://www.example.com/sitemap.xml"` | The full URL of the sitemap to submit (e.g., ''). Must be accessible and properly formatted as a valid sitemap XML file. Can also be a sitemap index file or RSS/Atom feed URL. Must exactly match the registered sitemap URL including protocol, host, path, and trailing slash; mismatches return notFound or invalid errors. |
| `site_url` | string | ✅ | `"https://www.example.com/"` | The site URL as registered in Google Search Console. For URL-prefix properties, use the full URL with protocol (e.g., ''). For domain properties, use the sc-domain format (e.g., 'sc-domain:example.com'). The site must be verified and owned by the authenticated user. |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.toolhouse.ai/toolhouse/integrations/google-search-console.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.