How to Use Google Search Console Topics with Promptwatch MCP
How we import Search Console queries into Prompt Explorer, then read those prompts through Promptwatch MCP in Claude, Cursor, or ChatGPT.
Search Console topics are only useful if someone looks at them next to assistant answers. We do not want a Monday CSV ritual for that. We import GSC queries into Prompt Explorer, then we ask Claude, Cursor, or ChatGPT over the hosted Promptwatch MCP. Same project. Same prompts. No extra UI tour for the analyst.
The connection itself is in how to connect Google Search Console. This post is what we do after the queries are in.
Import, then edit
Settings → Google Search Console, read-only OAuth, one property per project. That is the first move. Performance sync can pull up to a year of clicks, impressions, CTR, and position. That is context for which queries earned traffic. It is not the prompt list. Google's generative AI performance reports stay in Search Console for Overviews. They do not become ChatGPT prompts on their own.
Import into Prompt Explorer. Then we cut. Delete vanity and pack-only terms before anyone spends a response. A query with impressions and no clicks is often a better GEO candidate than a branded query that already ranks. A query that is really a local pack job stays on the local SEO playbook, not in a ChatGPT persona row.
We do not invent topics the property never earned. If GSC never saw the phrase, we can still add a sales-language prompt by hand. We label it as ours, not as an import. Promptwatch does not write to GSC. Import is one way.
You can skip Prompt Explorer and only talk to MCP if you want. The server will answer from whatever the project already contains. If you never imported GSC queries, MCP will not invent them. Import first, then chat. That is the part people try to skip, and then they wonder why Claude has nothing useful to say about "the GSC list."
Ask over MCP, not over a screenshot
MCP is hosted HTTP. We add the Promptwatch MCP URL in Claude, Cursor, or ChatGPT. Auth is OAuth or an API key. ChatGPT's plugin and the Claude connector hit the same server. We are not running three integrations. On our side we usually put the URL in Claude or Cursor first, then ChatGPT if someone on the account lives there.
On analyst laptops we use read-only keys. Project-scoped when the person only works one account. Org-scoped when they sit across Kick-off projects. Write keys stay off Slack-adjacent machines and off the Looker connector. That split is in read-only API keys.
You do not need a write key so Claude can add prompts. Not for reading. If you want the model to create prompts, that is a write key on a controlled seat, not on every laptop. We add prompts in the UI after a human cuts the GSC list. We do not let a chat window bulk-create from a year of Search Console. Cleaning that up takes longer than importing by hand.
What we ask the model to do: show mention vs citation on the imported prompts, name the URL that got used, and flag prompts that still look like Google head terms but get a different answer in ChatGPT. What we do not ask: "average these GSC clicks with mentions." That number is fiction.
Wiring the clients is how to connect Promptwatch MCP. After the answers come back, we file content tickets from the ones that name a missing URL. Passage work is in how to get cited by ChatGPT.
Plan notes we actually use
Essential at $95/mo includes MCP and API. That is the first brand plan where this workflow is real. Explore is free, 10 ChatGPT prompts, and is not a GSC import program. Professional is $245/mo. Business is $579/mo. Agency side: Kick-off at $199/mo, unlimited projects and prompts, 10 seats. G2: 4.7/5.
We still measure ChatGPT, Gemini, Claude, Perplexity, and the rest of the paid set in the project. MCP does not add engines. It reads what you already track.
FAQ
Can we skip Prompt Explorer and only talk to MCP?
The server will answer from whatever the project already contains. If you never imported GSC queries, MCP will not invent them. Import first, then chat.
Do we need a write key so Claude can add prompts?
Not for reading. We add prompts in the UI after a human cuts the GSC list. We do not let a chat window bulk-create from a year of Search Console.
Which plan includes MCP?
Essential at $95/mo includes MCP and API. That is the first brand plan where this workflow is real. Explore is not a GSC import program.
If you want the import and the MCP key done on the account, hello@1001seomedia.com.