How do I connect Google Search Console to Perplexity?

In Perplexity open Plugins, choose Add custom, then Connector, then Add MCP connector, select Remote and paste https://mcp.paidsync.ai/mcp with OAuth 2.0 and Streamable HTTP. Click the PaidSync connector card, sign in to PaidSync and press Approve, then ask Perplexity to connect your Google Search Console account. No API key is needed. Full steps are above.

Is PaidSync free to use with Perplexity?

Yes. The free plan gives you 15 tasks per month at $0. Paid plans start at $99/month for Pro, and Team plans from $249/month for 5 seats.

What Search Console data can Perplexity access?

Perplexity can query clicks, impressions, CTR, and average position by query, page, country, device, and date. The full Search Analytics API is exposed, including 16-month historical data.

Does PaidSync support multiple GSC properties?

Yes. If your Google account has access to multiple properties, PaidSync exposes all of them. You can ask Perplexity to compare performance across domains in the same conversation.

What OAuth scopes does PaidSync request for Search Console?

PaidSync requests https://www.googleapis.com/auth/webmasters.readonly, Google's read-only Search Console scope, for performance, property and sitemap data. It does not request the full webmasters scope.

Why is the Search Console integration read-only?

PaidSync's Search Console connection is read-only by design: it reads your search data and never changes your property. Google's own API can also submit sitemaps and add sites; PaidSync does not.

What does PaidSync cost with Perplexity?

PaidSync has its own pricing: the free plan is $0 for 15 tasks a month with no card, and Pro starts at $99 a month. Whether your Perplexity plan can add a custom connector depends on Perplexity, and an Enterprise admin must allow it first.

Does the same PaidSync connection work in other assistants?

Yes. PaidSync is one endpoint, https://mcp.paidsync.ai/mcp, with OAuth sign-in, and the same login works in Claude, Claude Code, ChatGPT, Gemini, Microsoft Copilot through Copilot Studio, Cursor and Windsurf. Set up PaidSync once and use it from any of them.

Connect Google Search Console to Perplexity in 2 Minutes

How to connect Search Console to Perplexity with PaidSync

This is the route through Perplexity's custom connectors. No API key is needed, because Perplexity connects with a PaidSync sign-in (OAuth).

Before you start

Custom connectors are a Perplexity feature you add in step 1, and nothing needs installing. On a Perplexity Enterprise organization, an admin must first allow members to add custom connectors.
Signing in with Google? There is no separate sign-up. You pick Continue with Google in step 2, and your free PaidSync account (15 tasks a month, no credit card) is created when you press Approve.
Prefer an email and password? Create the account at paidsync.ai/signup first. The sign-up link inside the sign-in window opens the website and does not bring you back to Perplexity.
Know which Google login is an owner or user of your Search Console property. You use it in step 3.

Add PaidSync to Perplexity as a custom connector

In Perplexity open Plugins in the sidebar (or Customize, then Connectors), choose Add custom, then Connector, then Add MCP connector, and select Remote. Name it PaidSync and paste the server URL:

https://mcp.paidsync.ai/mcp

Set authentication to OAuth 2.0 and transport to Streamable HTTP. PaidSync supports dynamic client registration, so the Client ID and Client Secret fields stay empty. Tick the acknowledgement, click Add, then click the PaidSync connector card and sign in with your PaidSync login. A custom connector needs a Perplexity plan that includes them, and on an Enterprise organization an admin must allow members to add custom connectors first.

Sign in to PaidSync and press Approve

The PaidSync sign-in screen opens. Pick Continue with Google, or sign in with your PaidSync email and password. A PaidSync screen then asks whether to allow Perplexity to manage your ad accounts via PaidSync. Press Approve and PaidSync is connected.

New to PaidSync and signing in with Google? Your free account (15 tasks a month, no credit card) is created when you press Approve. The screen also mentions ad accounts already connected inside PaidSync. On a new account that list is empty until you finish step 3.

Connect your Search Console property and ask Perplexity

In any chat, ask: "Connect my Search Console." Perplexity replies with a link that opens Google's own sign-in and consent screen. Sign in with the Google account that has access to your Search Console property and approve access. PaidSync asks Google for the read-only webmasters.readonly scope, so it reads your search data and never changes the property. PaidSync never sees your Google password.

Come back and ask: "List my Search Console properties." Perplexity uses list_gsc_properties to show every property your Google login can open, and you tell it which one to use. Connecting and listing properties uses none of your tasks. Then try: "What queries drove the most clicks in the last 28 days?" You can also connect Search Console from the PaidSync dashboard instead. Both routes use the same PaidSync login, so Perplexity sees the property either way.

The Cross-Channel Angle

PaidSync's 6 Search Console tools read your search data next to Google Ads, so Perplexity can compare what you pay for with what you already rank for. That means Perplexity can run paid-organic analysis in a single conversation without any data exports or tab switching.

Ask Perplexity to find organic queries where you rank in positions 5 to 15, then check whether you are running paid coverage on those same terms. Perplexity pulls both data sets, compares them, and tells you exactly where organic clicks are costing more than a paid click would.

The reverse check works too. Ask Perplexity which Google Ads keywords you pay for where you already rank in the top five organically, and it runs analyze_paid_organic_overlap, which estimates the monthly spend on each overlap.

What Perplexity Can Do with Search Console

Top query report. Perplexity returns your top 50 queries by clicks for any date range, with impressions, CTR, and position. Filtered by device or country in one follow-up.
Position drop detection. Ask Perplexity to find pages that lost more than 3 positions week over week. It returns a ranked list with the delta and current averages.
CTR gap analysis. Perplexity identifies queries with high impressions but low CTR, the fastest path to organic traffic gains without new content.
Sitemap status. Perplexity can check your sitemap submission status and flag any indexing errors across your properties.
Paid vs organic comparison. With Google Ads also connected, Perplexity can overlay paid spend data against organic query performance and find gaps in coverage.

What each Search Console report tells Perplexity

Top queries

Ask Perplexity which queries brought the most clicks this month, last month or any date range. It runs get_gsc_search_analytics by query and returns clicks, impressions, CTR and average position for each one, and can filter to queries that contain a word or to one page.

Top pages

Ask which pages get the most organic clicks, and which rank but are not clicked (high impressions, low CTR). Perplexity runs the same tool by page. To see which pages are losing position, it compares two date ranges.

Sitemaps and indexing

Perplexity reads your sitemaps with get_gsc_index_coverage and compares submitted with indexed page counts for each one, with any sitemap errors and warnings. Sitemap errors can keep whole sections of a site out of the index. PaidSync does not read the Page indexing report or URL Inspection.

Country and device

Ask Perplexity to break clicks and impressions down by country or by device, one breakdown per request. It shows where your organic audience comes from and whether mobile search keeps up with desktop.

Search Console prompts to try in Perplexity

Each prompt runs on the PaidSync tools named after it and uses one or more of your tasks. None of them changes anything, because PaidSync's 6 Search Console tools read your search data.

"What are my top 20 organic queries by clicks this month, with the average position for each?" Runs get_gsc_search_analytics by query.
"Which pages get a lot of impressions but a low click-through rate?" Runs get_gsc_search_analytics by page, ranked by impressions.
"How many of the URLs in my sitemaps are indexed, and which sitemap has the biggest gap?" Runs get_gsc_index_coverage.
"Compare my organic search performance this month with the same month last year." Perplexity runs get_gsc_search_analytics for both ranges. Search Console keeps 16 months of data.
"Which of my top organic queries am I not bidding on in Google Ads?" Runs get_gsc_search_analytics and the Google Ads tool get_keyword_performance, which covers your top 100 keywords by cost, then compares the two lists.
"Which Google Ads keywords am I paying for where I already rank in the top five?" Runs analyze_paid_organic_overlap, which estimates the monthly spend on each overlap.
"Break down my organic clicks and impressions by country for the last 90 days." Runs get_gsc_search_analytics by country.
"Which queries bring clicks to my pricing page, and at what average position?" Runs get_gsc_search_analytics by query, filtered to that page.

Troubleshooting Search Console in Perplexity

The sign-in fails. Sign in to PaidSync the way you signed up, with Continue with Google or with your PaidSync email and password. Email users without an account create one at paidsync.ai/signup first, then click the PaidSync connector card in Perplexity again. If Google's own consent screen fails, ask Perplexity "Connect my Search Console" again for a fresh link.
Perplexity used the wrong property. PaidSync keeps no default Search Console property. Every request names the property, so tell Perplexity which one you mean, and it sends that property with each request. A domain property (sc-domain:example.com) and a URL-prefix property (https://www.example.com/) are separate properties with different numbers, so name the one you mean. Ask Perplexity to list your properties with list_gsc_properties if you are not sure. Listing uses none of your tasks.
A property is not listed. PaidSync lists the properties your connected Google login can open. In Search Console, an owner adds that login under Settings, then Users and permissions. Connected with the wrong Google login? Disconnect it in the PaidSync dashboard and connect again with the login that has access.
Perplexity says it has no Search Console tool. PaidSync shows Perplexity a short starter list of tools to keep the chat light. Ask Perplexity to call paidsync_context first. It returns your connected platforms and the full tool list, Search Console included, and Perplexity then runs those tools through paidsync_exec. If PaidSync is missing from Perplexity altogether, check that its connector card is enabled under Plugins.