SEO and search / QA preview
Google Search Console + EarShots
The EarShots Google Search Console integration is designed to read query and page performance for a selected property. It lets a marketing team inspect traditional search evidence alongside AI-search questions and citations. The first adapter is read-only and remains in QA until live testing passes.
Open connection setupWhat can you do with this integration?
- Choose an accessible domain or URL-prefix property
- Read page and query clicks, impressions, click-through rate and position
- Use the same report contract in the app, MCP, CLI and REST API
Worked examples
These examples explain the QA adapter. They are not customer results or certification evidence.
Review a documentation page
- Input
- Illustrative request: choose a verified property and the last complete week.
- Action
- Read page/query rows and compare a documentation page with the related questions in EarShots.
- Expected result
- A traceable search report with the selected property and reporting window, useful for choosing which page to investigate.
Check results after an update
- Input
- Choose two comparable periods around a documented content update.
- Action
- Run separate read operations and compare the returned clicks and impressions alongside EarShots' citation evidence.
- Expected result
- An observed before/after comparison. Seasonality, demand and reporting changes remain possible explanations; no ranking lift is promised.
Fields and data direction
The selected provider property returns aggregate read-only report data to EarShots.
| Field | Meaning |
|---|---|
| Property | Exact URL-prefix or sc-domain property |
| Query / page | Reported search query and landing page |
| Clicks / impressions | Search performance counts |
| CTR / position | Provider-reported ratio and average position |
How to connect Google Search Console
A Google account with permission to the selected Search Console property, the Search Console API enabled, and the webmasters.readonly OAuth scope. No write or indexing submission permission is requested.
- Open setup, sign in to EarShots and choose your workspace.
- An owner or admin reviews the requested provider access and completes consent. QA setup must first be enabled for this provider.
- Select the exact property to use. Other resources are not automatically imported.
- Create a preview and run a small test. Read a short reporting period and check it against the provider's own report.
- Inspect the saved operation result. Manage or disconnect the account from workspace integrations.
Limits and recovery
Search Console reports may omit anonymized queries and do not contain every query or every row. Data may arrive after a delay. Search clicks and positions do not measure AI-engine citations. The initial adapter does not submit URLs or change your site.
Queued work follows the workspace worker schedule. If authorization expires, reconnect and reselect the resource. Keep the same operation and idempotency key when checking a retry. Disconnect blocks new work; an external request already in progress can still finish.
Common questions
Can I use this through MCP, CLI or the API?
The QA implementation shares the same workspace authorization and operation service across all four surfaces. Start setup from a tool or command, then complete provider consent in your browser. Machine requests do not receive provider credentials.
Is this available now?
This adapter is in QA. Setup depends on provider configuration, your workspace permissions and plan. Live availability will be recorded after account authorization and workflow tests pass.
Does connecting authorize publishing or marketing sends?
No. Connecting grants only the configured provider permissions. Workflow execution, content approval, publication and marketing consent are separate decisions.
Provider reference: Google Search Console developer documentation. Adapter behavior requires live verification before launch.