Connect Google Search Console to Claude

By the end of this walkthrough, Claude will be able to read your Google Search Console data through your own MCP connector. You'll clone the Typenode template, sign in with Google, then check a real result against Search Console.

The video uses Claude. You can also build with ChatGPT or another compatible AI app; its connector menus will differ.

Watch on YouTube

Follow the video alongside these instructions.

Have these ready:

• A Typenode account.
• A Claude account that allows custom connectors. A company administrator may need to enable them.
• A Google account with access to a property in Google Search Console.

The Google Search Console MCP template provides read-only tools for properties, performance, URL inspection and sitemaps. Check its page for the current tool list and required access.

Watch from 0:24.

1. Open the template page and click Use template.
2. Sign in to Typenode, or create your account.
3. Start cloning the template. If asked to connect your AI app, follow Connect Claude to Typenode.
4. Copy the prompt shown in Typenode. Start a new Claude conversation with Typenode enabled and paste that prompt.
5. Follow the Agent's questions about which Environment to use. If you need one, ask it to create an Environment before continuing.

Use the prompt supplied by the template so the Agent gets its current setup guidance. You don't need to copy the example Environment name from the video. Environments explains how their configuration is separated.

The Typenode MCP connector lets Claude build and manage the setup. Later, you'll add a separate custom MCP connector for reading Search Console data.

Watch from 2:27.

When Claude reaches the Google step, it gives you a link to connect your Google account. If it asks how you want to connect Google, choose the recommended option.

1. Open the link Claude gives you.
2. Click Connect and choose the Google account that can see your Search Console property.
3. Google shows what you're allowing: read-only access to your Search Console data. Approve it.
4. Return to Claude. It confirms the connection and carries on building your connector.

Claude can read your Search Console data but can't change anything in it. It sees only the properties your Google account can already see.

If Google blocks the connection, check that you chose the right Google account and that your company allows connecting apps to its Google accounts. If it still fails, contact Typenode.

Most people don't need this. Use it only if your company requires apps to connect through its own Google Cloud project. Follow Set up Google Cloud for integrations to create the project, consent screen, client ID and client secret, then ask Claude to use your own Google app instead of the recommended one. The earlier video, Manual OAuth Setup (Previous Version), shows this route from 3:17.

Watch from 4:39.

When the Agent finishes publishing the template's tools, it provides your custom MCP connector URL.

1. Copy that URL. It belongs to the connector you just built.
2. In Claude, open Settings → Connectors and add a custom connector.
3. Give it a recognizable name, such as Google Search Console, and paste the URL.
4. Complete the connection. On Typenode's approval screen, check the Workspace, Environment and connector match your setup before allowing access.
5. Start a new conversation and enable the Search Console connector.

If your organization manages connectors centrally, ask its owner to make the connector available. Claude's connector instructions cover its current account and organization options.

Watch from 5:58.

Start with a read-only check:

Use my Google Search Console connector to list the properties I can access. Ask me which property
to use, then retrieve its total clicks and impressions for the last 28 complete days. Show the
exact property and date range. Do not change anything.

Choose the property when asked. A successful check returns an identifiable property, date range, clicks and impressions from the connector's tools.

Open the same property in Search Console and compare the same date range, search type and filters. If you have little data, an empty or small result may be expected; ask Claude to show the API's response rather than inventing an explanation.

Check that the Search Console connector is connected and enabled in the conversation. Start a new chat, or refresh the app, then try the check again. The Typenode connector used to build the tools and your Search Console connector are separate entries.

Check which Google account you signed in with in Step 2. Open Search Console with that account and confirm it can access the property.

The earlier video, Manual OAuth Setup (Previous Version), shows the Google Cloud route. The current video uses Google sign-in, so follow Step 2 instead. You only need Google Cloud if you chose the advanced route.

Ask Claude to reconnect Google, then sign in again as in Step 2. Credential refresh and reconnection explains when this is needed.

Ask Claude to explain the tools available through your connector, then try a question about the queries bringing traffic to a page. You can also ask it to adapt the cloned Workflows to your needs.

For a teammate, invite them to your Typenode Workspace and share the custom MCP connector URL. They authorize their own access to the connector; they don't need to sign in with Google again. Review what data the connected Google account can read before sharing it. The video shows this from 7:17.

For current API availability, use the Search Console reference.