How to Connect Google Search Console to Promptwatch
How we connect Google Search Console to Promptwatch on client accounts: read-only OAuth, one property per project, and query import into Prompt Explorer.
Every retainer already has Search Console. The miss is treating those queries as a Google-only list while the assistant work lives in a second tool. We connect Promptwatch so the same property feeds Prompt Explorer. We do not replace GSC. We stop pretending the two lists are unrelated. The buyer questions that earn impressions in Google are the same buyer questions that get answered in ChatGPT, and keeping them in two unconnected tools is how a team ends up with two prompt lists that disagree.
This is setup, not a citation tactic. For passage shape after you know which queries matter, see how to get cited by ChatGPT.
What we connect
In Promptwatch: Settings, then Google Search Console. The OAuth grant is org-level and read-only. We can attach more than one Google account when a client's properties sit under different logins. We still map one Search Console property to one Promptwatch project. Mixing two hostnames in one project is how the query list turns into noise. Blog property and app property in the same project is the usual way that happens, and it is a mess to unwind later, because the prompts from each hostname answer different buyer questions and the citation data blends them into one meaningless column.
The client does not need to make us an owner on the Search Console property. They need a Google account that can authorize a read-only grant for that property. We do not need write access. We do not want it. If their IT wants a dedicated Google user, that works. We can attach more than one Google account on the org. The org owner is the one who runs Settings → Google Search Console and attaches the Google account that actually owns the property. Read-only is the whole posture, and it is the posture we describe to every security team.
After the grant, we turn on the optional pieces only when the SOW needs them. Auto URL import puts GSC pages in the project inventory. If that inventory must sit next to Promptwatch crawler logs, the project needs Professional, Business, or an agency plan because Essential has no listed crawler-log allowance. Details are in how we import sitemaps and Search Console URLs. We use URL Inspection when we need Google's view of a URL next to whether an AI crawler fetched it. Performance sync covers up to one year of clicks, impressions, CTR, and position. We turn on performance sync on most retainers. We turn on URL import when we also want inventory, and we add Agent Analytics only on a plan that includes it. Turning everything on by default is how a project gets noisy and expensive. Turn on what the SOW actually calls for.
Then we import queries into Prompt Explorer. That is the step that changes the weekly work. The phrases people already type in Google become the first draft of the prompt list. We still edit. We drop brand vanity queries. We keep the ones sales actually hears. We do not connect a property and then import every query. A year of Search Console is a lot of junk. We import, then we cut, before we spend responses. The cut is the work. The import is just the raw material.
Promptwatch never writes back to Search Console. No sitemap submit, no inspection spam, no property edits. If a client's security review asks, that is the sentence we send. If a URL is excluded or a sitemap is stale, that is still a job in GSC or the CMS. Promptwatch can show you the performance rows and, if you turned on URL import, put those URLs in inventory. Create or open one Promptwatch project per hostname first. Kick-off if there is more than one client.
What we do not do with this pipe
We do not treat GSC position as an AI rank. Overviews can show up in Google's own generative AI performance reports. ChatGPT and Perplexity do not. Those stay in Promptwatch columns. A position-one Google ranking and a ChatGPT mention are different measurements of different surfaces, and pretending they are the same number is how a report misleads.
We do not average last year's impressions with this week's mentions. The sync window is useful context. It is not a blended KPI. I have sat in QBRs where someone tried that average. It sounds tidy and it explains nothing. The customer who saw an impression in March and the customer who got a citation on Tuesday are not the same event, and adding them produces a number that answers neither question.
Explore is free: 10 ChatGPT prompts. Fine for a sandbox. Not a client property. Essential is $95/mo and is the first brand plan with MCP and API if you want to read those imported prompts from Claude later, but it has no listed crawler-log allowance. Professional is $245/mo and is the first brand plan with Agent Analytics. Business is $579/mo. On retainers we use Kick-off at $199/mo with crawler logs, unlimited projects and prompts, and 10 seats. G2: 4.7/5.
FAQ
Does Promptwatch write back to Search Console?
No. No sitemap submit, no inspection spam, no property edits. If a client's security review asks, that is the sentence we send.
Do we treat GSC position as an AI rank?
No. Overviews can show up in Google's generative reports. ChatGPT and Perplexity do not. Those stay in Promptwatch columns.
Can we mix two hostnames in one project?
No. We map one Search Console property to one Promptwatch project. Mixing a blog property and an app property is how the query list turns into noise.
If you want us to wire it, hello@1001seomedia.com. Send the hostname and which Google login holds Search Console.