What You'll Set Up

By the end of this guide, your AI agent will be able to pull data from your Google Search Console account — querying search performance metrics, inspecting how Google indexes your pages, and managing your sitemaps. No manual key or credential is needed. You simply sign in with your Google account and Pipeworks handles the rest.

Your agent can answer questions like "What are our top search queries this month?" or "Is Google indexing our new landing page?" using live data from your Search Console account.

Google Search Console

9 tools · See exactly how Google sees your site

Before You Begin

Make sure you have:

A Google Search Console account — Set one up at search.google.com/search-console if you haven't already. You need at least one verified property (either a URL-prefix or domain property).
A Pipeworks workspace — Sign up at pipeworks.ai if you haven't already

Info

Google Search Console is free to use. Make sure you have at least Owner or Full user access to the properties you want your agent to work with.

Steps

Open your Pipeworks console

Log into your Pipeworks workspace and go to the Integrations page. Find Google Search Console in the list and click on it.

Sign in with Google

Click Connect with Google. You will be redirected to Google's sign-in page. Choose the Google account that has access to your Search Console properties and grant the requested permissions.

Pipeworks requests access to your Search Console data. You can review the exact permissions on the Google consent screen before approving.

Authorize access

After signing in, Google will ask you to confirm that Pipeworks can access your Search Console data. Click Allow to complete the connection. You will be redirected back to your Pipeworks console.

Pipeworks securely stores your authorization using industry-standard encryption. Your Google password is never shared with Pipeworks.

Start the integration

Click Start to launch the Google Search Console integration container. Once the status shows Running, your agent is ready to query your search data.

Test the connection

Use the Test button to verify everything works. This sends a simple request to Google Search Console to confirm your connection is active and your properties are accessible.

What Your Agent Can Do

Once connected, your AI agent has access to 9 Google Search Console tools for:

Search analytics — Query clicks, impressions, click-through rates, and average position. Filter by query, page, country, device, date range, and search type
Page-level performance — See which pages drive the most organic search traffic, sorted by clicks
URL inspection — Check whether Google can find and index a specific page, and see any crawl or mobile usability issues
Sitemap management — List submitted sitemaps, check their status, submit new sitemaps, or remove old ones
Site listing — List all verified properties in your Search Console account and view their details

Tip

Most Google Search Console tools are read-only — your agent can pull search data, inspect URLs, and list sitemaps without modifying anything. The only write operations are submitting and removing sitemaps, which your agent will confirm with you before proceeding.

Connecting from Your AI Agent

Add the Pipeworks tools endpoint to your agent's configuration. Here's an example for Claude Desktop:

json

{
  "mcpServers": {
    "pipeworks-google-search-console": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.pipeworks.ai/tools/google-search-console"]
    }
  }
}

Claude Desktop will prompt you to sign in through Pipeworks when you first connect. No access key needed.

Troubleshooting

Google sign-in fails? Make sure you are signing in with the Google account that has access to your Search Console properties. If you have multiple Google accounts, check that you selected the right one.

No properties showing up? Verify that your Google account has Owner or Full user access to the properties you want to query. You can check this in Google Search Console under Settings > Users and permissions.

Connection expired? Google authorizations can expire over time. If your agent stops working, go to the Pipeworks console, click Disconnect, and reconnect by signing in with Google again.

Search data seems delayed? Google Search Console data typically has a 2-3 day delay. This is normal — Google needs time to process search data before it becomes available through the API.

Agent can't find tools? Verify your Pipeworks session is authenticated and that the integration status shows "Running" in your Pipeworks console.

Connect Google Search Console to Pipeworks

Prerequisites