Connect SearchChamp to ChatGPT.
Turn on developer mode for full read/write access, add the SearchChamp connector, and let ChatGPT check in on your rankings, opportunities, and audits.
Three steps.
Enable developer mode
In the ChatGPT web app, open Settings → Connectors → Advanced and turn on developer mode. Developer mode is what unlocks full read-and-write connector access, not just read-only lookups — without it, ChatGPT can still read your SearchChamp data but can't queue fixes, draft content, or schedule a rescan on your behalf.
Add the SearchChamp connector
Add a new connector and paste in the SearchChamp connector URL from Settings → Connect your AI apps inside your SearchChamp workspace, then complete OAuth sign-in with your SearchChamp account. This is the same connector URL used for Claude — one URL works across every MCP-compatible client.
Create a Task with notifications on
Set up a recurring Task (for example, a daily or weekly check-in) with notifications enabled, so ChatGPT proactively reports back instead of waiting for you to ask. Word the Task in plain language — "check my rankings every Monday morning and flag anything that dropped" is enough; ChatGPT handles the scheduling and the connector calls.
How approval works
With developer mode on, ChatGPT has full read-and-write MCP access to the SearchChamp connector — but nothing runs silently. Before any action that changes data (queuing a fix, drafting content, scheduling a rescan), ChatGPT shows you the exact JSON payload it’s about to send and waits for your confirmation. Read-only lookups (rankings, opportunities, audit status) don’t need confirmation. This applies every time, not just the first time — ChatGPT doesn’t remember a past approval and reuse it silently on a later, different action, so you always see what’s about to change before it changes.
No developer mode? You still get read access.
On mobile, or if developer mode isn’t available on your account, the SearchChamp connector still works for read-only lookups. Any action that would normally need your JSON confirmation instead hands you an approval deep link that opens the SearchChamp app, where you can review and confirm it there. Nothing is silently blocked and nothing is silently allowed — you just approve it in the SearchChamp app instead of inline in the chat, and once approved the result comes back to your conversation the same way it would on desktop.
Connecting ChatGPT — FAQ
No — read-only lookups like rankings, opportunities, and audit status work without developer mode. You only need it turned on for actions that change data: queuing a fix, drafting content, or scheduling a rescan.
Yes — one connector URL from Settings → Connect your AI apps works across every MCP-compatible client, including Claude, ChatGPT, and Claude Code. You sign in separately per app, but there is nothing ChatGPT-specific to configure on the SearchChamp side.
The exact payload ChatGPT is about to send to SearchChamp — which tool it's calling and with what parameters — so you can see precisely what will change before approving it. Nothing that writes data runs without that step, developer mode or not.
Yes — each Task is independent, so you can run a daily ranking check, a weekly audit summary, and an AI-visibility check on their own schedules without them interfering with each other.
Read-only lookups still work the same way. Any action that would normally show you the JSON confirmation instead hands you an approval deep link that opens the SearchChamp app, where you review and confirm it there — so nothing runs unapproved on mobile either.
No — the connector shares your existing SearchChamp plan quotas rather than adding a separate allowance. Actions you approve through ChatGPT count the same way they would if you'd done them directly in the dashboard.
Something not working?
Check the troubleshooting guide for OAuth loops, workspace scoping, shared usage limits, and allow-listing OpenAI’s provider IP ranges if your network restricts outbound connections.