How do you connect Google Search Console API to an SEO platform?

Connecting the Google Search Console API to an SEO platform normally involves authorising the platform through Google OAuth, selecting a verified Search Console property and allowing the platform to retrieve the required data. You do not need to share your Google password with the platform. Once authorisation is complete, the platform can request Search Console performance data for reporting, analysis and SEO workflow features.

Before you begin

• Make sure you can sign in to the Google account that has access to the relevant Search Console property.
• Confirm that the website has already been added and verified in Google Search Console.
• Check that you have sufficient permission for the property. Full or owner-level access is commonly required to complete the connection, although the exact requirement depends on the platform and the authorisation method it uses.
• Have the correct property type to hand. Search Console may contain a domain property and one or more URL-prefix properties for what appears to be the same website. Select the property whose data you want to analyse.

How the connection works

1. Open the integrations, data sources or account settings area in the SEO platform.
2. Select the Google Search Console integration and choose the option to connect or authorise an account.
3. Sign in to Google if prompted, then review the account and property access requested by the platform.
4. Approve the requested Google Search Console API permission. A read-only connection generally uses the webmasters.readonly scope, while a platform that needs to make changes may request broader access. Only approve permissions that match the platform’s stated functionality.
5. Return to the SEO platform and select the Search Console property to associate with the project, campaign or website record.
6. Save the configuration and run a synchronisation or data refresh if the platform does not start one automatically.

Google OAuth creates an authorisation token for the platform. The platform uses that token to make approved API requests on your behalf, rather than storing your Google account password. The connection is tied to both the authorised Google account and the selected Search Console property, so authorising the wrong account or property can result in missing or apparently incomplete data.

Selecting the correct property

Property selection is one of the most common causes of confusion during setup. A domain property covers the domain and its protocol and subdomain variations, subject to how the property was verified. A URL-prefix property covers only the specified URL prefix. For example, an HTTPS property may not represent an HTTP property, and a subdomain property may not include the main domain.

Choose the property that matches the scope of the SEO project. If the platform offers several similar properties, compare the property name and URL with the one shown in Search Console. If expected data is missing after connection, check whether the data belongs to a different property rather than assuming that the API connection has failed.

What happens after authorisation

The SEO platform sends requests to the Search Console API using the selected property and a defined date range. Depending on the platform, it may retrieve queries, pages, clicks, impressions, click-through rate and average position, together with dimensions such as date, country, device and search appearance. The platform may then store or process this information for dashboards, keyword analysis, trend monitoring and automated reports.

Search Console data is not always available immediately for the latest date, and different tools may apply their own synchronisation schedules, filters or data-retention rules. A newly connected project may therefore need a refresh or an initial import before charts and reports are populated.

If the connection does not work

• No properties are displayed: verify that you authorised the Google account with access to the property, then reconnect and review the account selected during OAuth.
• Access is denied: ask a Search Console property owner to grant the required access, or use an account that already has it. Being able to view a website in another Google service does not necessarily provide Search Console access.
• The wrong website is shown: disconnect or edit the integration and select the correct property. Check protocol, subdomain and path differences carefully.
• Data is empty: confirm that the property has historical Search Console data, that the date range is supported, and that filters have not excluded all rows. Also check whether the platform is still completing its initial synchronisation.
• Authorisation loops or fails: sign out of unwanted Google accounts, retry in a private browser window and complete the OAuth process with the intended account. Organisational Google Workspace policies can also restrict third-party application access.
• The connection has expired: reconnect the integration and approve the request again. Token expiry, revoked permissions or changes to the Google account can interrupt an existing connection.

Security and access management

Use the least-privileged permission that supports the required features. A read-only Search Console connection is appropriate for reporting and analysis where the platform does not need to submit changes. Review connected applications in the Google account periodically, particularly when a staff member leaves or an agency relationship ends. Revoking the platform’s access in Google will stop future API requests, although data already imported into the SEO platform may need to be removed separately according to its account controls.

For a reliable setup, record which Google account authorised the integration, which Search Console property was selected and when the connection was last tested. If the platform supports multiple projects, confirm that each project is mapped to the intended property rather than assuming that one account connection automatically selects the correct website for every project.