Sign in or create an account on the connection page. Already connected? Open its GPT there.
Reviewed September 22, 2026 · Based on the current TalkToData implementation
Choose the right property
You need a TalkToData account and a Google account with access to a verified Search Console property. Both HTTP/HTTPS URL-prefix properties and sc-domain: domain properties are supported; unverified-user properties cannot be selected.
A domain property can include several subdomains. Choose the URL-prefix property for the site you mean to analyze, or use a page filter and state its scope. Do not report an entire domain's totals as one subdomain's traffic.
Connect your property
- Open the Search Console connection page. Create an account or sign in; you return to this connector.
- Choose Connect Google Search Console and approve Google's read-only authorization request.
- Back in TalkToData, choose the intended property returned by Google and save the selection. Test the connection using the control on that page.
- Open the linked Search Console GPT, sign in to ChatGPT and complete its authorization prompt if shown.
- Ask for the property and date range first, then request a focused query or page report.
Start with one decision, not an entire SEO audit
“For the selected property, show the returned pages with impressions but few clicks over the last 28 days. Include clicks, impressions, CTR and average position. State the property, date range, filters and row limits. Suggest three pages to inspect without claiming a cause.”
To compare periods, request two explicit date ranges separately, each no longer than 90 days. Ask the GPT to distinguish complete totals from capped rows and to leave hidden queries unclassified.
Available data and important limits
- Search-performance totals and rows by query, page, country or device.
- Clicks, impressions, CTR and average position, with date ranges of up to 90 days.
- Optional page, query, country and device filters where exposed by the action.
- Capped opportunity summaries for investigation, not guaranteed ranking improvements.
Low-volume queries can be hidden, rows are capped, and reports are not real time. Missing performance rows do not prove a URL is unindexed. This connector has no URL Inspection, sitemap submission or indexing-request action. Check those questions directly in Search Console.
Search Console describes Google Search visibility, not website sessions or conversions. Those are separate questions for your analytics system.
When a property or report is missing
Check that you authorized the correct Google account and selected the exact property. If no rows return, widen the date range or review filters before interpreting the result. Reconnect if access expired. Do not grant write permissions to solve a read-only reporting issue.
The connector uses webmasters.readonly. Google tokens stay server-side. Disconnect through TalkToData when needed, and never send a password or token to support.
Questions before you connect
Can ChatGPT connect to Google Search Console?
Yes. TalkToData connects an authorized, verified Search Console property to a dedicated read-only GPT workflow.
Can TalkToData request indexing or submit a sitemap?
No. Current actions read properties and search-performance data; they do not inspect URL indexing or submit sitemaps.
Why do query rows not add up to the total?
Search Console can hide low-volume queries and the connector caps returned rows. Do not treat partial rows as a complete list or infer the missing queries.
Can I compare date ranges?
Yes. Request each period separately, up to 90 days per range, using the same property and filters.
Ready for your first question?
Connect the right account, confirm the status and continue in the GPT linked to that channel.