Skip to content
SocialHelper
Get API key

Google Search Console data, from one API.

Connect Google Search Console once, then run its reports and lookups from your code or your AI agent through one REST API and MCP server.

Live Connects with OAuth 4 tools

Tools

Google Search Console tools.

Call them with POST /api/v1/accounts/{id}/tools/{tool}, or let your agent use list_account_tools and run_account_tool over MCP. Results come back straight away.

list_sites

read-only

List the Search Console properties this account can access, with its permission level on each.

search_analytics

read-only

Query search performance (clicks, impressions, CTR, average position), optionally grouped by query, page, country, device, search appearance, date or hour. Dates are Pacific Time; data usually lags 2–3 days unless data_state is "all".

site_url* string
The property exactly as list_sites returns it, e.g. "https://example.com/" or "sc-domain:example.com".
start_date* string
First day, YYYY-MM-DD (inclusive).
end_date* string
Last day, YYYY-MM-DD (inclusive).
dimensions array<string>
Group rows by these, in order: query, page, country, device, searchAppearance, date, hour. Omit for one total row.
type string
Which results to count. web | image | video | news | discover | googleNews default: 'web'
filters array<object>
Filters, all of which must match. Each is {"dimension": "query|page|country|device|searchAppearance", "operator": "equals|notEquals|contains|notContains|includingRegex|excludingRegex", "expression": "…"}. Countries are ISO 3166-1 alpha-3 (e.g. "usa"); devices are DESKTOP, MOBILE or TABLET.
aggregation_type string
How to aggregate: by page or by property. "auto" lets Google choose. auto | byPage | byProperty default: 'auto'
data_state string
"final" for finished data only, "all" to include fresh (incomplete) data, "hourly_all" with the hour dimension. final | all | hourly_all default: 'final'
row_limit integer
Rows to return (1–25000). default: 100
start_row integer
Zero-based offset for paging. default: 0

inspect_url

read-only

Inspect how Google sees one URL of a property: index status, coverage, last crawl, canonical, mobile usability and rich results.

site_url* string
The property exactly as list_sites returns it, e.g. "https://example.com/" or "sc-domain:example.com".
url* string
The full URL to inspect; it must belong to the property.
language_code string
Language for translated issue messages, e.g. "en-US". default: 'en-US'

list_sitemaps

read-only

List the sitemaps submitted for a property, with their status, errors, warnings and indexed content counts.

site_url* string
The property exactly as list_sites returns it, e.g. "https://example.com/" or "sc-domain:example.com".

Connect

Connect Google Search Console once.

Open Accounts in the SocialHelper dashboard and choose Google Search Console. You sign in on Google Search Console’s own screen and approve access; SocialHelper stores the connection encrypted. You don’t need a Google Search Console developer app of your own.

  1. 1

    Open Accounts

    In the dashboard, choose Google Search Console.

  2. 2

    Sign in on Google Search Console

    Approve access on Google Search Console’s own screen.

  3. 3

    Use the account ID

    GET /api/v1/accounts lists the account with its ID, whether it can publish, and its tools.

SocialHelper calls Google Search Console’s official API for you. Google Search Console API reference ↗

FAQ

Google Search Console questions.

Do I need my own Google Search Console developer app?

No. You connect with a normal Google Search Console sign-in through SocialHelper’s own app.

Can my AI agent use Google Search Console?

Yes. Connect the SocialHelper MCP server at https://socialhelper.app/mcp and your agent can list and run Google Search Console’s tools.

How much does it cost?

SocialHelper is free during early access, Google Search Console included.

Ship your Google Search Console integration today.

Create a free account, connect an account and send your first post in a few minutes.