By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Perplexity to Google Search Console is the Ryze AI connector. Connect Search Console in a Ryze AI workspace with your Google sign-in and confirm the Site, then in Perplexity open Plugins, choose Add custom, Add MCP connector, Remote, and enter https://connector.get-ryze.ai/mcp with OAuth, Streamable HTTP and Public network access. Select the new connector card to sign in to Ryze AI.
- In Ryze AI open Integrations, find Google Search Console and click Connect
- Sign in to Google, keep every permission checked, then confirm the Site and click Save
- In Perplexity open Plugins, Add custom, Add MCP connector, Remote, and enter the name and URL
- Set Authentication to OAuth, tick the acknowledgement, click Add, then select the connector card to sign in to Ryze AI
Perplexity to Google Search Console at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, added to Perplexity as a custom remote connector |
| Connector address | https://connector.get-ryze.ai/mcp |
| Form settings | OAuth, Streamable HTTP, Public network access |
| Sign-in | Google approves Ryze AI once; the connector card in Perplexity then opens the Ryze AI sign-in. No client ID or secret is typed into Perplexity |
| Search Console tools | 7: 5 read, 1 write (submit a sitemap) and 1 delete (remove a sitemap) |
| Changes from Perplexity | Only sitemaps. The connection holds the read and write webmasters scope, and no tool requests indexing or removes URLs |
| Other data in the same chat | Other platforms connected in the same Ryze AI workspace use the same address |
| Perplexity plan | Pro, Max or Enterprise, per Perplexity's changelog |
| Ryze AI price | SEO Starter, $129 per month with a 3-day free trial, or Paid Ads at $89 per month with a 7-day free trial. The connector is free |
| Google's own option | No Search Console MCP server was found on Google's pages. Google documents the Search Console API and a bulk export to BigQuery |
| Last tested | November 14, 2026, from Claude Code. Nothing was run inside Perplexity |
Before you start
- A Perplexity plan that allows custom connectors. Perplexity's March 2026 changelog names Pro, Max and Enterprise subscribers. The custom connectors help article names no plan. Inside an Enterprise organization, a member can add a connector for their own account only after an administrator switches on Allow members to add custom connectors, which starts off. Only administrators add organization-wide connectors.
- A Google login that can open the property in Search Console. The property must be verified. Google's permission levels are owner, full user, restricted user and associate, and the login you pick on the Ryze AI Connect step decides what the tools can reach. A Domain property covers every subdomain and protocol, while a URL-prefix property covers only URLs under that exact prefix.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial. Paid Ads is $89 per month with a 7-day free trial. Annual billing takes 30% off the first year. Connecting the connector is free; the Search Console tools need an active plan or trial.
- Trust in the server. Perplexity's help center tells users to add only connectors from sources they trust, because it cannot verify third-party servers. Check who runs a server first.
How to connect Perplexity to Google Search Console
Setup has two parts: Search Console is connected inside Ryze AI, then Perplexity is pointed at the Ryze AI connector. The Perplexity steps follow its help center for a personal account. Nothing was tested inside Perplexity while this page was written, so use the troubleshooting list below if a screen differs.
Connect Google Search Console in Ryze AI
Sign in to Ryze AI (or create an account), open Integrations in the left sidebar, find Google Search Console with the Search integrations box or the Analytics filter and click Connect.
Approve Google access and confirm the Site
Sign in to the Google login that can open your property and keep every requested permission checked. Back in Ryze AI, check the Site (Ryze AI pre-selects the one that matches the workspace domain), change it if needed and click Save. Until a Site is saved the card shows Require setup.
Open Plugins in Perplexity
Open Plugins in the sidebar. If Plugins is not there, open Customize, then Connectors. Perplexity describes Plugins on sales-assisted Enterprise plans as a beta that an administrator turns on, so members there may still see Customize.
Add a remote MCP connector
Select Add custom, then Add MCP connector, and choose Remote. Type Ryze AI as the name and https://connector.get-ryze.ai/mcp as the MCP server URL. The name takes up to 64 characters and the address must start with https://.
Set the advanced options
Under Advanced choose OAuth for Authentication, Streamable HTTP for Transport and Public for Network access. Ryze AI supports dynamic client registration, so no client ID or secret is entered. Skip API Key: the form has no field for custom headers.
Add the connector and sign in
Tick the acknowledgement checkbox and select Add. Perplexity checks the server then and tags the card with an error if the check fails. Select the connector card on the Plugins page to start the Ryze AI sign-in, choose the workspace that holds your Search Console connection and enable the connector.
The Ryze AI Google Search Console guide covers the Google sign-in and the Site step on the Ryze AI side.
Sources: Perplexity: custom remote connectors, changelog of March 12, 2026, what are plugins. Checked November 14, 2026.
Enterprise organization setup
An Enterprise administrator can add the connector once for everyone instead of each member adding it:
- Open Organization settings, then Connectors, and select Custom connector. Organization connectors are always remote, so the dialog offers no Remote choice.
- Enter the name and URL, set the advanced options as in the steps above, tick the acknowledgement checkbox and select Add.
- A new organization connector starts switched off. Turn it on under Organization settings, then Connectors.
- Decide between one shared sign-in for the organization and a sign-in for each member. A shared sign-in means every member reads Search Console through the same Ryze AI workspace, so pick per-member sign-in if people should reach only their own properties.
Perplexity's help center also describes a Cloudflare Access network option and AWS PrivateLink for Enterprise. The Ryze AI connector is a public address, so Public is the setting to use. Connector connections and disconnections appear in the organization's audit logs.
Sources: Perplexity: custom remote connectors, organization plugins. Checked November 14, 2026.
Local MCP and other surfaces
Local MCP servers on the desktop
Perplexity names two places that start a local MCP server from a command: the Mac app with its PerplexityXPC helper installed, and Portable Computer in Local mode. Perplexity on the web takes remote connectors only. The Ryze AI connector is remote, so it goes through the Plugins flow and needs neither. A remote connector that is connected anywhere is connected for the account everywhere, including inside plugins.
Other Perplexity surfaces
Perplexity says the Plugins page also exists in its desktop and mobile apps, but none of its pages says Add MCP connector works on mobile. This guide covers the web flow and the Enterprise organization flow. Add the connector on the web.
Perplexity and MCP: the facts in one table
| Topic | What Perplexity's pages say |
|---|---|
| Name | Custom remote connector, added with Add MCP connector |
| Where | Personal: Plugins, Add custom. Organization: Organization settings, Connectors, Custom connector, administrators only |
| Config file | None, it is a form. A custom plugin package can list up to 15 remote servers in mcp.json |
| Fields | A name of up to 64 characters and an https:// URL; an optional description and an icon of up to 128 KB |
| Transports | Streamable HTTP or SSE. Local commands only in the Mac app and Portable Computer |
| Sign-in | OAuth 2.0 with dynamic client registration, API Key or None. Without registration: Client ID, Client Secret and Perplexity's redirect URL |
| Headers | No custom headers, apart from two Cloudflare Access service-token headers |
| Approval | An approval card before consequential writes; Perplexity does not define consequential |
| Plan | Pro, Max and Enterprise on the changelog; the custom connectors article names none |
| Managed in | Plugins, Installed tab: status, Reconnect, Disconnect |
| Blocked by | A Web-only, Academic or Social source setting |
Sources: Perplexity: custom remote connectors, local and remote MCPs, troubleshooting connectors, installing plugins, custom plugins, Portable Computer, changelog of August 24, 2026, blog on MCP tools. Checked November 14, 2026.
Google Search Console access and scopes
Perplexity reaches Search Console through two separate sign-ins. Google decides what the login may open in Search Console; the Ryze AI connection then asks Google for the read and write scope.
- Google login
- Chosen when you click Connect on the Ryze AI Google Search Console card. It needs access to a verified property. The Site you save in Ryze AI serves the Ryze AI app; the tools take the property address in each call, so name the property in the thread.
- Permission level in Search Console
- Google's table lists Submit sitemap for owners and full users and leaves the restricted user cell empty. URL Inspection is listed for owners and full users, with Fetch only for restricted users, and the Performance report for all three. Google's pages describe the interface, and no call was run here to test a restricted login against the write tools.
- Perplexity connector settings
- Remote connectors in Perplexity take OAuth, API Key or None. Choose OAuth for Ryze AI. In an Enterprise organization, an administrator controls who may add connectors and whether sign-in is shared or per member.
The two Search Console scopes
Google defines two Search Console scopes. Google marks sitemaps.submit and sitemaps.delete as needing the read and write one, while the other five methods behind the tools accept either.
| Scope | How Google describes it | Used by Ryze AI |
|---|---|---|
| https://www.googleapis.com/auth/webmasters | Read/write access | Yes |
| https://www.googleapis.com/auth/webmasters.readonly | Read-only access | No |
What the connection can and cannot reach
The Ryze AI connection uses a person's Google sign-in with the webmasters scope. Together with the person's permission level on the property, it sets what Perplexity can read and change.
| Access piece | What it covers | Included for Perplexity? |
|---|---|---|
| webmasters scope, read side | Search Analytics queries, the list of properties, the sitemap list and a sitemap summary, and URL Inspection | Yes, 5 read tools |
| webmasters scope, write side | Submitting or resubmitting a sitemap | Yes, submitSitemap |
| webmasters scope, delete side | Removing a sitemap from Search Console; the sitemap file on the site is not touched | Yes, deleteSitemap |
| Adding or removing a property | The Search Console API has methods for it | No. The connector has no tool for it |
| Requesting indexing, removing URLs from Google, verifying a property | Actions Google keeps in the Search Console interface | No. No tool exists |
| Index coverage for every URL in one call | A site-wide coverage list | No. The API does not offer it; URL Inspection checks one URL per call |
Out of reach: site verification, adding or deleting properties, indexing requests, URL removals, and Search Console data older than 16 months. Anonymized queries are left out of Google's reports.
Sources: authorizing requests, searchanalytics.query, sitemaps.submit, sitemaps.delete, permission levels, property types. Checked November 14, 2026.
Removing access
To remove access, disconnect the login on the Google Search Console card in Ryze AI. In Perplexity, open Plugins, go to the Installed tab, open the Ryze AI connector and select Disconnect; Perplexity stops calling it at once. The ellipsis menu on the connector edits or removes it. Google also lists third-party access on your Google Account permissions page, where you can revoke it.
What Perplexity can do in Google Search Console
The Ryze AI connector gives Perplexity 7 Search Console tools: 5 read, 1 write and 1 delete. Every tool takes a workspace, an optional connection_id and, apart from the property list, the siteUrl of the property.
| Tool | Type | What it does |
|---|---|---|
| google_search_console__listSites | Read | Lists every Search Console property the connected login can access, with permission levels. |
| google_search_console__runRawSearchAnalytics | Read | Runs a Search Analytics query by query, page, country, device, search appearance or date, for web, image, video, news or Discover results, up to 25,000 rows per request. |
| google_search_console__inspectUrl | Read | Inspects one URL's index status: coverage, verdict, last crawl, canonical, indexing state, mobile usability and rich results. |
| google_search_console__listSitemaps | Read | Lists a property's sitemaps with last submitted and downloaded dates, pending state, errors, warnings and submitted counts. |
| google_search_console__getIndexationSummary | Read | Returns a sitemap summary for a property: number of sitemaps, submitted URLs, errors, warnings and pending items. |
| google_search_console__submitSitemap | Write | Submits or resubmits a sitemap to Search Console for a property. |
| google_search_console__deleteSitemap | Delete | Removes a sitemap from Search Console for a property; the file on the site is untouched. |
Two of the 7 tools change Search Console: submitSitemap and deleteSitemap. Perplexity says it shows an approval card before consequential writes but does not define the term, so whether a sitemap submission triggers one is not confirmed. Since August 24, 2026 Perplexity's changelog lets a connector tool be set to Always ask; whether that panel appears for a custom connector was not confirmed either. To stay in control, tell Perplexity in the prompt to describe a sitemap change and wait for your yes before it calls either tool. Organization administrators can set tool permissions per connector on its Base tool permissions tab.
Search Console limits in numbers
Google counts Search Console API usage in queries per minute and per day, and limits how much data one query returns. Each figure below comes from the Google page named under the table.
| Limit | Figure or rule |
|---|---|
| Search Analytics rate | 1,200 queries per minute per site and per user; per project 30,000,000 per day and 40,000 per minute |
| Search Analytics load | Short-term quota is measured in 10 minute chunks and long-term quota in 1 day chunks. Google says to wait 15 minutes after exceeding it. Grouping or filtering by page and query together costs the most, and a longer date range costs more |
| URL Inspection rate | 2,000 queries per day and 600 per minute per site; per project 10,000,000 per day and 15,000 per minute |
| Sites and sitemaps | 20 queries per second and 200 per minute per user; per project 100,000,000 per day |
| Rows per request | 1 to 25,000, default 1,000. In the November 14 test a value of 25001 was refused |
| Paging | Repeat the query with startRow raised by 25,000 until a response has 0 rows |
| Rows per day | Google says the method exposes a maximum of 50K rows per day per search type (web, image and so on), sorted by clicks |
| Data delay | Data is typically available after 2 to 3 days. dataState all adds fresh data that may be incomplete; final or no value returns finalized data only |
| History kept | The last 16 months |
| Time zone | Dates are YYYY-MM-DD in Pacific time |
| Sort order | By clicks, highest first, unless you group by date, which sorts by date ascending |
| Filters | equals (default), contains, notContains, notEquals, includingRegex and excludingRegex (RE2) on country, device, page, query and searchAppearance. Only an AND group is supported |
| URL Inspection scope | One URL per call, and only the version in the Google index; a live URL cannot be tested. The URL must sit under the property |
| Sitemap counts | Google marks the per-sitemap indexed count as deprecated, so rely on submitted counts, errors and warnings |
| Hourly data | Google's API can return up to 10 days hourly, but the Ryze AI tool definition does not list the hour dimension and it was not tested |
| Perplexity | Connector names up to 64 characters. No printed cap on connectors or tools |
Sources: Search Console API usage limits, searchanalytics.query reference, getting all your data, URL Inspection reference, sitemaps reference, 16 months of history, Perplexity: custom remote connectors. Checked November 14, 2026.
Search Console calls through the connector, tested
On November 14, 2026, Claude Code sent six Search Console calls to the live Ryze AI connector, at the same address this guide gives Perplexity. Three were meant to return data, three were meant to be refused, and all were read-only. The properties belong to real test workspaces, so no name, domain or figure is shown.
| Request | Tool | Search Console answered |
|---|---|---|
| List the properties the login can reach | google_search_console__listSites | Worked |
| Last 7 days by query with a row limit of 25001 | google_search_console__runRawSearchAnalytics | HTTP 400 invalidParameter: the row limit is above the maximum |
| A dimension called keyword | google_search_console__runRawSearchAnalytics | HTTP 400 INVALID_ARGUMENT: the dimension does not exist |
| An end date before the start date | google_search_console__runRawSearchAnalytics | HTTP 400 invalidParameter |
| 7 days by query with an equals filter on a random 20-letter string | google_search_console__runRawSearchAnalytics | Worked. The response held no rows key, only responseAggregationType |
| 90 days by query, 120 rows, fresh data, a regex filter on the query | google_search_console__runRawSearchAnalytics | Worked. Rows came back with keys, clicks, impressions, ctr and position, highest clicks first |
No response carried a quota or rate-limit figure. The only limit that appeared in a response was the row limit named in the first error.
First 3 prompts to run
The prompts describe what each one asks for. Answers come from your own property, so this page shows no sample numbers.
1. Find your properties and the queries behind clicks
Using the Ryze AI connector, list the Search Console properties I can open, then for the first one show the top queries by clicks over the last 90 days with impressions, CTR and average position.
Tools used: google_search_console__listSites, google_search_console__runRawSearchAnalytics
What comes back: A list of properties with permission levels, then rows grouped by query, ordered by clicks, each with clicks, impressions, ctr and position.
2. Spot pages that sit just outside the click positions
Using the Ryze AI connector, group last month's Search Console data by page and query, and list the pages whose average position is between 8 and 20 with their impressions.
Tools used: google_search_console__runRawSearchAnalytics
What comes back: Rows with a page and a query per row and the four metrics. Grouping by page and query together is the costliest query shape, so Google may slow it on a large property.
3. Check one URL and the sitemaps
Using the Ryze AI connector, inspect this URL and tell me its verdict, last crawl and canonical, then list my sitemaps with their errors and warnings.
Tools used: google_search_console__inspectUrl, google_search_console__listSitemaps
What comes back: The index status of that single URL as Google holds it, then each sitemap with last submitted and downloaded dates, errors and warnings.
Name the property in the prompt or ask Perplexity to list properties first. The tools do not select one for you. Add a line telling Perplexity not to submit or remove a sitemap unless you say so.
10 jobs to hand to Perplexity
Ten jobs for Perplexity, each with its tool. Name Ryze AI in the request or pick it with @. The property list and the Search Analytics queries ran in the test; the other tools were read from their definitions and not called.
| Job | Ask Perplexity | Tool | Works on the default connection |
|---|---|---|---|
| Property list | Which Search Console properties can this login open, and at what permission level? | google_search_console__listSites | Yes, ran in the test |
| Top queries | Top queries by clicks and impressions for the last 90 days, with CTR and average position. | google_search_console__runRawSearchAnalytics | Yes, ran in the test |
| Query patterns | Only the queries that contain a brand term or start with a question word. | google_search_console__runRawSearchAnalytics | Yes. Equals and regex filters ran in the test |
| Near-miss pages | Pages that rank just outside the positions that earn clicks, with the queries they rank for. | google_search_console__runRawSearchAnalytics | Yes, grouping by page was not run |
| Country, device and appearance | Split clicks and impressions by country, device or search appearance. | google_search_console__runRawSearchAnalytics | Yes, not run |
| Page trend | A day-by-day trend for one page, to see whether a published article earns impressions and clicks. | google_search_console__runRawSearchAnalytics | Yes, not run |
| Other result types | Performance in image, video, news or Discover results instead of web. | google_search_console__runRawSearchAnalytics | Yes, not run |
| Index status | Index status of one URL: coverage, verdict, last crawl, canonical, mobile usability and rich results. | google_search_console__inspectUrl | Yes, not run. One URL per call |
| Sitemap health | Every sitemap with last submitted and downloaded dates, errors and warnings, and a property summary. | google_search_console__listSitemaps, google_search_console__getIndexationSummary | Yes, not run |
| Sitemap changes | Submit or resubmit a sitemap, or remove a stale one from Search Console. | google_search_console__submitSitemap, google_search_console__deleteSitemap | Yes, not run because it changes Search Console. Needs a permission level that allows it |
Not possible: requesting indexing for a URL, removing a URL from Google, verifying a property, and a coverage report for every URL of a site in one call. No tool exists for the first three, and the API does not offer the last.
3 ways to connect Perplexity to Google Search Console
Perplexity on the web takes remote connectors at an https address, and only its desktop software starts local commands. Google documents no Search Console connector, so every route here comes from a third party or from Google's API. The Ryze AI connector is the main way: one Google approval, one address and 7 tools that read queries, URL status and sitemaps and can submit or remove sitemaps. Windsor.ai and Coupler.io are hosted alternatives. Neither was tried in Perplexity. All vendor pages were read on November 14, 2026.
| Way | Runs where | Setup for Perplexity | What it reaches in Search Console | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted, one address for every user. The same address works in Claude, ChatGPT and other MCP clients | Add MCP connector, Remote, the address, OAuth. Sign in from the card | Search Analytics, URL Inspection, sitemap list and summary, plus submit and remove sitemap | SEO Starter $129 per month, 3-day free trial. Paid Ads $89 per month, 7-day free trial. Connector free |
| Windsor.ai (Windsor MCP) | Hosted by Windsor.ai | Connect Search Console as a data source in Windsor.ai, then add its connector. Windsor's page names Claude, ChatGPT, Gemini and Copilot, and Perplexity appears only in its site menu | Read-only, with no URL inspection. Clicks, impressions, CTR and position, plus query word counts and URL path levels. Web, image, video and news; Discover and Google News are not included | Free with a 30-day trial, then Forever Free with 1 data source. Basic $23 per month |
| Coupler.io Search Console MCP | Hosted by Coupler.io. The assistant queries a synced copy of the data, not Search Console itself | Build a Search Console data flow, add Custom MCP as its destination and paste the server URL and token into the assistant. Coupler.io lists Perplexity among its assistants | Read-only on synced data, refreshed on a schedule down to every 15 minutes. No sitemap management, URL submission or Indexing API calls | Free forever with manual refresh and 1 data source. Starter $32 per month. Which plans include the MCP destination was not shown on the page |
Eight Search Console options that do not fit Perplexity
- A Google Search Console MCP server. None was found on Google's pages on November 14, 2026: not on its list of products with a remote MCP server (87 rows, stamped November 12, 2026), not in the google/mcp repository, not in the Search Console API documentation, and not in the Cloud MCP release notes. Windsor.ai makes the same statement on its own page, as a vendor. Google does publish an open-source MCP server for Google Analytics, a different product.
- The Search Console API. A REST service you call from your own code with OAuth 2.0 and a Google Cloud project, free of charge within usage limits. Its pages describe no MCP endpoint and name no assistant. It reads Search Analytics, sitemaps, sites and URL Inspection, and can submit or delete sitemaps and add or remove properties.
- Bulk data export to BigQuery with Google's BigQuery MCP server. Two Google features: a daily export of performance data to BigQuery, set up by a property owner with a billed Google Cloud project, and a remote BigQuery MCP server at https://bigquery.googleapis.com/mcp that went generally available on April 20, 2026. The export starts from the day you set it up, leaves out anonymized queries and has no URL inspection or sitemap actions. Google's client guidance names Claude, ChatGPT Business, Cursor and others, and not Perplexity, and says Google's remote servers do not support dynamic client registration. The combined route was not run.
- Developer Knowledge MCP server. Google's server for searching its developer documentation. It holds no Search Console account data.
- AI-powered configuration inside Search Console. An experimental feature announced December 4, 2025 that turns a plain-language request into Performance report filters. It is limited to 20 requests per day per user, was visible to a small share of users and is not a connector for an outside assistant.
- Composio. Hosted, with 14 tools that include adding and deleting sites and verifying ownership. Its assistant pages name Claude, ChatGPT, Cursor and Codex among others, and not Perplexity. Its pricing page and its Search Console page give different free-plan call counts.
- Zapier MCP. No Search Console page was found on Zapier on November 14, 2026, and Perplexity is not in its list of clients.
- Community servers. AminForou/mcp-gsc, a free MIT server with 2,202 GitHub stars on November 14, 2026, runs on your own computer with your own Google credentials, and its README names Claude Desktop, Cursor, Codex CLI, Gemini CLI and Antigravity. Its destructive tools are off by default. ahonn/mcp-server-gsc has one search_analytics tool and 286 stars.
Which one to pick
Ryze AI is the best way to connect Perplexity to Google Search Console when one thread should read queries, URL status and sitemaps through a single https address with OAuth, with two caveats: the tools need an active Ryze AI plan or trial, and two of the 7 can change sitemaps. Windsor.ai suits Search Console next to many other sources. Coupler.io suits scheduled read-only questions on synced data and names Perplexity. The Search Console API suits teams that write their own code. Perplexity's Discover tab also lists prebuilt connectors; this page did not check whether one covers Search Console.
The Ryze AI row follows the Ryze AI Google Search Console guide.
Sources: Google MCP supported products, google/mcp repository, Search Console API, API pricing, bulk data export, BigQuery MCP server, Google MCP authentication, Developer Knowledge MCP, AI-powered configuration, Windsor.ai, Windsor.ai pricing, Coupler.io, Coupler.io pricing, Composio, Composio pricing, Zapier MCP quickstart, AminForou/mcp-gsc, ahonn/mcp-server-gsc, Perplexity: custom remote connectors, installing plugins. Checked November 14, 2026.
Perplexity, Search Console and MCP: dates that matter
| Date | What happened |
|---|---|
| January 31, 2022 | The URL Inspection API launched with a quota of 2,000 queries per day and 600 per minute per property. |
| February 21, 2023 | Google announced bulk data export of Search Console performance data to BigQuery. |
| April 9, 2025 | The Search Analytics API gained hourly data: an hour dimension and dataState hourly_all, for up to 10 days. |
| December 4, 2025 | Google announced AI-powered configuration for the Performance report as an experimental feature. |
| December 10, 2025 | Google's BigQuery remote MCP server entered Preview. The Google Cloud MCP release notes still have no Search Console entry in their newest item, dated September 14, 2026. |
| March 12, 2026 | Perplexity shipped Bring Your Own Connector: custom remote connectors by URL for Pro, Max and Enterprise. |
| April 20, 2026 | Google's BigQuery MCP server became generally available. |
| June 3, 2026 | Google introduced Search Generative AI performance reports in Search Console and said they reached all websites by August 31, 2026. The post does not say whether the data is in the API. |
| August 24, 2026 | Perplexity's changelog added a per-tool Always ask setting for connectors. |
| November 4, 2026 | Windsor.ai's Search Console MCP page, last updated this day, says Google does not publish a Search Console MCP server. |
| November 6, 2026 | mcp-search-console 0.4.2, the newest version on PyPI, was uploaded. The same day Perplexity's changelog announced Agent Plugins and the Plugins page. |
| November 14, 2026 | Google's supported-products list, MCP repository and Search Console API pages were checked again and still showed no Search Console MCP server. The Ryze AI connector test for this page ran the same day. |
Sources: URL Inspection API launch, bulk data export, hourly data, AI-powered configuration, BigQuery release notes, Google Cloud MCP release notes, generative AI performance reports, Windsor.ai, mcp-search-console on PyPI, changelog of March 12, 2026, changelog of August 24, 2026, changelog of November 6, 2026, Perplexity: custom remote connectors. Checked November 14, 2026.
How this guide was tested
The live Ryze AI connector was checked on November 14, 2026, with calls sent from Claude Code to the same address this guide gives Perplexity. Every call was read-only.
| What was run | What came back |
|---|---|
| Tool list | All 7 Search Console tool names loaded by exact name and each returned a definition, with access as 5 read, 1 write and 1 delete. |
| Schema checks | Every tool takes a workspace and an optional connection_id. All but the property list require siteUrl. The property list definition says no site is auto-selected, so pass siteUrl to the others. |
| Three reads | The property list worked, and two Search Analytics queries returned either an empty result or rows. Their contents are withheld. |
| Three planned failures | A row limit of 25001, a dimension that does not exist and an end date before the start date, each refused with the errors below. |
| Quota figures | No response showed a quota number, so the limits above come from Google's pages. |
Not run: anything inside Perplexity. No connector was added, no sign-in completed and no tool called from a Perplexity thread, on any plan; those steps follow Perplexity's help center as read on November 14, 2026. URL inspection, the sitemap list and the sitemap summary were not called. Sitemap submission and removal were not called because they change Search Console. Grouping by page, country, device, search appearance or date, the image, video, news and Discover types, and a restricted-user login were not tried. No quota was exhausted. Windsor.ai, Coupler.io and the community servers were not tried.
Errors and fixes
Exact Search Console messages from the test
Copied from the Search Console answers of November 14, 2026. The connector returns each failure as Error 400 followed by Google's JSON error body.
| Message | What it means | What to do in Perplexity |
|---|---|---|
| '25001' is not a valid row limit value. | The row limit was above the maximum of 25,000 rows per request (HTTP 400, reason invalidParameter). | Ask for 25,000 rows or fewer and page with startRow. |
| Invalid value at 'dimension[0]' ... "keyword" | The dimension name does not exist (HTTP 400, status INVALID_ARGUMENT). Search terms are the dimension query. | Use query, page, country, device, searchAppearance or date. |
| Invalid date range defined by startDate and endDate. End date cannot precede the start date. | The end date was earlier than the start date (HTTP 400, reason invalidParameter). | Swap the dates. Both are YYYY-MM-DD in Pacific time. |
Two more answers are documented and were not triggered in the test. Google's limits page says the quota exceeded error is the same for every kind of quota event. The runRawSearchAnalytics tool definition says a request timed out answer means Search Console did not respond in time; it says to resend once on its own, never in parallel, and to narrow the request if it times out again (shorter date range, one dimension, no regex filter).
Other problems
- Add MCP connector is missing in Perplexity
- Check your plan. Perplexity's changelog names Pro, Max and Enterprise for custom remote connectors. In an Enterprise organization, ask an administrator to switch on Allow members to add custom connectors, or to add the connector for everyone.
- The Add button stays unavailable
- Fill in the name, the whole https address and the acknowledgement checkbox.
- The connector is added but does nothing
- Select its card on the Plugins page to start the Ryze AI sign-in and enable it. In an organization, a new connector starts switched off until an administrator turns it on.
- The sign-in window never opens
- Connector sign-in needs pop-ups and cross-site cookies for perplexity.ai. Allow both, then select the card again.
- The Search Console tools do not load
- First check that the Google Search Console card in Ryze AI shows a saved Site rather than Require setup. If the connector was added before Search Console was connected, remove it under Plugins, Installed and add it again, then open a new thread. The Ryze AI help center gives this advice for Claude and ChatGPT, which cache the tool list; Perplexity's pages do not say whether it does the same.
- Perplexity never calls Ryze AI
- A Web-only, Academic or Social source setting stops connector calls. Change it and name Ryze AI in the request.
- It works in my own account but not in the company workspace
- A personal connector does not carry into an Enterprise workspace or a Project. Add Ryze AI there too.
- Sign-in fails with API Key selected
- Use OAuth. The form has no field for custom request headers, and Perplexity's documentation does not say which header the API Key option sends.
- Perplexity asks for a client ID and secret
- It asks for them only for OAuth servers without dynamic client registration. Ryze AI supports dynamic client registration, so leave them empty. If a server needs a redirect URL, Perplexity's is https://www.perplexity.ai/rest/connections/oauth_callback.
- A property is missing from the results
- Ryze AI sees only the properties the connected Google login can open. Attach another login through Add one more account on the card, or ask a property owner to add your login.
- Insufficient permissions on a property or a write
- The login's permission level on that property may be too low. Google's table gives Submit sitemap to owners and full users. Ask an owner for a higher level, or connect a login that has it.
- Recent days are empty or look low
- Google says data is typically available after 2 to 3 days. Ask for dataState all to include fresh data, which may be incomplete.
- A page URL gets an error in URL Inspection
- The URL must sit under the property you name. For a URL-prefix property, include the protocol and the trailing slash in siteUrl.
- Perplexity says a subscription is required
- The tools sit behind an active Ryze AI plan or free trial. Start the trial, then ask again.
Sources: troubleshooting connectors, Perplexity: custom remote connectors, Search Console API usage limits, searchanalytics.query reference. Checked November 14, 2026.
Terms on this page
- Custom remote connector
- Perplexity's name for an MCP server you add by its https address.
- Dynamic client registration
- An OAuth feature Perplexity uses when a server offers it. The Ryze AI connector supports it, so no Client ID or Client Secret is typed in.
- Domain property
- A Search Console property that aggregates every subdomain, protocol and subpath. In the API its siteUrl is written sc-domain:example.com and it is verified by DNS record.
- URL-prefix property
- A property that includes only URLs with the given prefix, protocol included. In the API the siteUrl must end with a slash.
- Average position
- Google defines it as the average position of the topmost result from your site.
- CTR
- Clicks divided by impressions. In the API the value runs from 0 to 1.
- Anonymized queries
- Queries Google leaves out of reports to protect user privacy. They are also left out of bulk data export.
Sources: Perplexity: custom remote connectors, property types, performance metrics, searchanalytics.query reference, anonymized queries. Checked November 14, 2026.
Frequently asked questions
How do I connect Perplexity to Google Search Console?
Connect Google Search Console in a Ryze AI workspace: open Integrations, click Connect on Google Search Console, approve every permission and save the Site. Then in Perplexity open Plugins, Add custom, Add MCP connector, Remote, enter https://connector.get-ryze.ai/mcp, set Authentication to OAuth and select Add. Select the connector card to sign in.
Does Perplexity have a Google Search Console connector?
Perplexity lets Pro, Max and Enterprise subscribers add a custom remote MCP connector by URL, and the Ryze AI connector is one you can add that way. Perplexity also lists prebuilt connectors; this page did not verify one for Search Console.
Is there a Google Search Console MCP server from Google?
None was found on Google's pages on November 14, 2026: not on its list of products with a remote MCP server, not in its MCP repository and not in the Search Console API documentation. Google documents the Search Console API and a bulk export to BigQuery.
What is the Google Search Console MCP server URL for Perplexity?
For the Ryze AI connector it is https://connector.get-ryze.ai/mcp, the same for every user, entered as a remote connector with OAuth. Other hosted servers have their own addresses, such as the Coupler.io URL generated per data flow.
Is there a free Google Search Console connector for Perplexity?
Adding the Ryze AI connector costs nothing, though its tools need an active Ryze AI plan or a free trial: 3 days on SEO Starter or 7 days on Paid Ads. Coupler.io has a free plan with one data source and manual refresh, and Windsor.ai has a Forever Free plan with one data source after a 30-day trial. Neither was tried for this page.
Which Search Console connector should I use with Perplexity?
It depends on the job. The Ryze AI connector gives live queries, single-URL index status and sitemap actions through one address, and needs a Ryze AI plan or trial. Coupler.io fits scheduled read-only questions on synced data, and Windsor.ai fits Search Console next to other sources.
Which Perplexity plan do I need?
Perplexity's March 2026 changelog says Pro, Max and Enterprise subscribers can add a custom remote connector. In an Enterprise organization, members need an administrator to switch on Allow members to add custom connectors, which starts off.
Can Perplexity change my Search Console settings?
Only sitemaps. Two of the 7 tools write: submitSitemap submits or resubmits a sitemap and deleteSitemap removes one from Search Console, leaving the file on the site. There is no tool to request indexing, remove URLs from Google, verify a property or add a property.
Can Perplexity ask Google to index a URL?
No. The connector has no indexing request tool. inspectUrl reads the index status of one URL as Google holds it, and submitSitemap tells Google about a sitemap.
Which authentication option should I pick?
Pick OAuth, with Streamable HTTP and Public network access. Ryze AI supports dynamic client registration, so no client ID or secret is needed. The form has no field for custom headers, so the API Key option does not fit.
Can my whole Enterprise organization use it?
Yes. An administrator opens Organization settings, Connectors, adds a Custom connector, switches it on and chooses between one organization sign-in and a sign-in for each member.
Can I use more than one Search Console account or site?
Yes. Several Google logins can be connected to one workspace with Add one more account, each with its own Site, and one is the primary. Tools accept an optional connection_id, and listSites shows every property a login can open. Keep separate clients in separate workspaces.
Why do the Search Console tools not show up in Perplexity?
Check that the Google Search Console card in Ryze AI has a saved Site. If the connector was added before Search Console was connected, remove it under Plugins, Installed, add it again and open a new thread.
Why does the Search Console tool return insufficient permissions?
The Google login behind the connection may not have a high enough permission level on that property, or the property may belong to another login. Ask Perplexity to run the property list to see the levels, then get owner or full user access, or connect the right login.
Why are my newest Search Console numbers missing?
Google says data is typically available after 2 to 3 days. Ask for fresh data with dataState all, and treat those rows as possibly incomplete. Google also keeps only the last 16 months.
How much does it cost to connect Perplexity to Google Search Console?
The connection costs nothing, while the Search Console tools run only on an active Ryze AI plan or trial. SEO Starter is $129 per month with a 3-day free trial. Paid Ads is $89 per month with a 7-day free trial. Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect Search Console from Perplexity?
Open the Ryze AI connector under Plugins, Installed in Perplexity and select Disconnect, or remove it from its ellipsis menu. To cut Search Console off at the source, disconnect the login on the Google Search Console card in Ryze AI or revoke access on your Google Account permissions page.