- Docs
- Connect Google Search Console to Perplexity
How to Connect Google Search Console to Perplexity with CorpusIQ MCP¶
Perplexity is good at search itself. What a query means, who ranks for it, what changed in the results page this month.
It cannot see your own query data. Which pages lost clicks, which queries brought impressions without a click, where position moved. That lives in Search Console, behind your verified property.
Connecting Search Console through CorpusIQ MCP puts both in one thread. Perplexity answers the question about your search performance from your own property, read-only, and states the property, the date range and the dimensions it read.
Why Connect Google Search Console to Perplexity?¶
- Query intent plus your numbers. "We rank 7th for this query with a 1.2 percent CTR. What do the top three results do differently?" Both halves in one thread.
- Cannibalisation checks. "Which queries bring up more than one of our pages, and which page wins?"
- Lost click diagnosis. "Where did impressions rise while clicks fell last quarter?"
- Page decay. "Which pages lost more than 20 percent of their clicks over three months?"
- Content planning. "Which queries do we rank for on page two, and what intent do they carry?"
- Read-only by scope. Nothing in the retrieval path can submit a sitemap, request indexing or change a property setting.
How It Works¶
- Connect Google. Search Console is part of the Google connector in CorpusIQ, alongside Gmail, Calendar, Drive, Sheets, Google Analytics and Google Ads. One authorization covers them.
- Grant read access. You approve the Search Console read scope for properties you own or administer.
- Add CorpusIQ to Perplexity as a custom remote MCP server, using the endpoint from your CorpusIQ account settings.
- Perplexity answers from your query and page data, then adds the external context the question needs.
Direct MCP retrieval is read-only. It does not retain raw customer files or full connector response payloads; operational query logs are kept for up to 30 days.
Setup Steps¶
In CorpusIQ
- Open your dashboard and go to Connectors.
- Select Google and sign in with the Google account that is a verified owner or full user of the Search Console property.
- Approve read access on Google's consent screen. Search Console data arrives through that same connection.
- If you manage several properties, confirm which one the question should target. The answer names the property it read.
In Perplexity
- Open Settings and find the MCP servers section.
- Add a custom remote MCP server and paste the endpoint:
https://mcp2.corpusiq.io/mcp
- Connect and approve the CorpusIQ authorization page once.
- Start a new thread and ask a question about search performance.
An agency can read a client property under the client's own permission set, because access follows the Google account you authorize.
Example Perplexity Questions¶
Performance
- "How many clicks and impressions did the site get last month, and how did that change year over year?"
- "Which ten queries brought the most clicks last quarter?"
- "What is our average position by country?"
Queries and intent
- "Which queries have more than a thousand impressions and a click-through rate under one percent?"
- "Which page-two queries look commercial rather than informational?"
- "What questions are people asking that we rank for but never answer directly?"
Pages
- "Which pages lost the most clicks over the last three months?"
- "Which new pages gained traction since they were published?"
- "Which pages rank for more than twenty queries but convert nothing?"
Technical
- "Which pages were indexed this month, and which are excluded?"
- "Did the core update change our position on our top twenty queries?"
Comparison: The Search Console Interface vs Search Console Through Perplexity¶
| Search Console | Search Console through Perplexity | |
|---|---|---|
| A query report | Filter, sort, export, then read | Ask the question |
| Adding outside context | Copy it into a chat somewhere else | Same thread |
| Explaining a drop | Read the chart and infer | Ask for the cause, then verify against the cited rows |
| Long history | Bounded by the 16-month window | Same window, asked as a question |
FAQ¶
Which properties can be connected?
Any property the authorized Google account owns or has full access to, including domain properties and URL-prefix properties. Access follows your Google permissions, not a CorpusIQ-side list.Can it submit a sitemap or request indexing?
No. The grant carries the read scope for search performance data. Write operations such as sitemap submission, indexing requests and property settings are outside the retrieval path.How much history is available?
Search Console keeps a bounded history of about 16 months. Questions about older periods have no data behind them, and recent days can still be filling in, so ask for a closed range when a figure has to be final.Do I need both Google Analytics and Search Console?
They answer different questions. Search Console covers what happened on the results page, Analytics covers what visitors did after they arrived. Both arrive through the same Google connection, so adding the second costs one authorization.Does this work only in Perplexity?
No. Search Console is exposed to ChatGPT, Claude and Perplexity through the same endpoint on the same subscription.Where is the search data stored?
CorpusIQ does not retain raw customer files or full connector response payloads. Operational logs may persist for up to 30 days. See the [read-only and security documentation](/hermes/security/read-only-and-security).Next steps: Connect Google Search Console to Perplexity now
Part of the MCP knowledge base at corpusiq.io - connect 40+ business tools to AI.
This Hermes repo is one of the largest structured collections of public AI, automation, business, and technology documentation. Content remains attributed to original authors and repositories. Indexed and organized by www.CorpusIQ.io.