4 ways to connect Google Business Profile to Claude in 2026 (the easy way)

Prerequisites

• A Porter Metrics account with your Google Business Profile account connected (free tier is enough to try it end-to-end)
• A Claude account — the free plan works for Claude Web; a Pro subscription is needed for Claude Code and Desktop MCP features
• Admin or standard access to the Google Business Profile locations you want to connect

Connect Google Business Profile to Claude with MCP

For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for Google Business Profile.

MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Claude Code and others access and use external APIs — the things that make tools like Google Business Profile work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.

The full setup takes under 5 minutes and breaks into three moves: connect Google Business Profile to Porter, point Claude at the Porter MCP, and ask your first question.

1. Connect your Google Business Profile data to Porter

Porter sits between Google’s Business Profile API and Claude. It handles OAuth, rate limiting, pagination and all the plumbing so Claude only ever sees clean, structured data.

Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.

Connect your Google account. In Porter, click Create → pick Claude as the destination → select Google Business Profile as the source → sign in with Google to grant access to your locations.

Select your locations. Choose the Google Business Profile locations you want Claude to query. When you select multiple locations under a single connection, Porter automatically blends their data together so you can query them as one.

Optional: enable automatic BigQuery storage if you’re connecting multiple locations with large data volumes. This keeps Claude’s responses fast even at scale.

2. Connect the MCP to Claude

Porter’s MCP URL is what you paste into Claude. Once added, Claude can query Google Business Profile data on demand in any conversation.

Go to claude.ai and click the + icon in the chat input to open the tools menu.

In the menu that opens, hover over Connectors and click Manage connectors.

In the Connectors panel, click the + button at the top of the list to start adding a new connector.

Pick Add custom connector from the dropdown that appears.

A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.

In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.

Click Add at the bottom right of the dialog. Claude opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.

Once the authorization finishes, you’ll see Porter’s read-only tools appear in the connectors panel. You’re ready to start asking questions.

For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.

3. Start building questions and dashboards

With Porter connected, open a new Claude chat and ask anything about your Google Business Profile in plain English. Claude calls Porter behind the scenes, pulls live data from Google, and answers with tables, charts, or summaries.

Try one of these to verify the setup is working:

For a full catalogue of copy-paste prompts organized by use case (agencies, SEO/SEM, e-commerce, cross-channel), jump to the prompts section below.

Alternative ways to connect Google Business Profile to Claude

MCP is the path we just walked through — and the one we recommend for most marketers. But it’s not the only way to get Google Business Profile data in front of Claude. The most common alternatives are Google Business Profile’s direct API (or its official MCP if it has one), a live Google Sheets bridge, and BigQuery for scale. Each has its trade-offs — pick the one that fits how your team already works.

• 🔌 Google Business Profile’s direct API (or official MCP) — Talk to Google’s Business Profile API yourself, or install Google Business Profile’s native MCP if one exists. Maximum control, but you handle auth, rate limits and pagination — and you only get one source.
• 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
• 🗄️ Google BigQuery — For large locations or agencies running multi-location analysis. BigQuery aggregates; Claude only queries pre-built summaries.

Via Google Business Profile’s direct API (or official MCP)

If you’re building a product around Google Business Profile — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to Google’s Business Profile API yourself. Google doesn’t publish an official MCP server for Google Business Profile, so this means writing API calls directly in Claude Code or in your own scripts. You’ll need to follow Google’s rate limits & quotas. Either way, you skip Porter entirely and call Google from your own code or from Claude Code with raw HTTP requests.

Via Google Sheets (live Sheet or manual CSV)

If your team already lives in Google Sheets — or you want a paper trail before Claude touches anything — feed Google Business Profile into a Sheet, then let Claude read the Sheet. You can automate the Google Business Profile → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from Google Business Profile’s native dashboard for static analysis.

Read the full Sheets tutorial →

Via Google BigQuery (for scale)

This is the path most people overlook — and it’s the one that saves you when your Google Business Profile location gets serious. A single large local SEO specialist or an agency managing 10+ locations will hit API rate limits and latency problems querying Claude directly. Claude will literally tell you it’s taking too long or timing out on big pulls.

BigQuery fixes that. You load Google Business Profile data into BigQuery tables on a schedule, then connect BigQuery to Claude — either through a BigQuery MCP or via Claude Code with SQL queries. Instead of asking Claude to pull raw Google Business Profile data, you let BigQuery aggregate into small, optimized tables, and Claude only queries the summarized output. Scale problem solved.

Read the full BigQuery tutorial →

Connecting Google Business Profile to Claude Code

Most marketers lump Claude and Claude Code together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with Google Business Profile data seriously.

Claude is a chat interface. You ask a question, Claude pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.

Claude Code is Claude running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for Google Business Profile, a whole category of work becomes possible.

What Claude Code unlocks that Claude alone cannot

This is where the MCP ecosystem pays off most. Because Claude Code can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.

🛠️ Build your own local SEO dashboard Stack: Porter MCP + Vercel MCP (or Cloudflare Pages, Netlify) Feed Claude Code your Google Business Profile targets and goals — review response time goals, post frequency targets, rating thresholds — and ask it to generate a custom local SEO performance dashboard for each client. It builds the HTML, pulls live data, deploys to a URL. No Data Studio embed to break when the vendor changes pricing, no template constraints. The dashboard updates automatically because it queries Porter’s MCP on every page load. Best for: agencies that want white-label client dashboards without Looker or Data Studio dependencies.

🔍 Full competitor + performance monitoring Stack: Porter MCP + Firecrawl MCP Combine your own Google Business Profile performance from Porter with competitor Google Business Profile listings and reviews scraped via Firecrawl. Claude Code stitches both into a weekly competitive intelligence report — your numbers next to their review ratings and post frequency, with an LLM summary on top of what changed week over week. Runs on cron, lands in your inbox every Monday morning. Best for: in-house teams that need market context, not just internal numbers.

📚 Internal marketing wiki with live metrics Stack: Porter MCP + Airtable MCP (or Notion MCP) Use Airtable or Notion as the schema, Porter as the data source. Claude Code keeps every page populated with current total reviews, average review rating, and Review Time to Respond for every location — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account. Best for: agencies and ops teams onboarding analysts or rotating account managers frequently.

🔔 24/7 alerts on review ratings, response times, and post activity drops Stack: Porter MCP + Slack MCP (or Gmail MCP) A Claude Code routine on cron pulls Google Business Profile via Porter, evaluates thresholds — average rating drops below 4.0, response time spikes above 48 hours — and pushes Slack or Gmail alerts the moment something crosses the line. You stop checking dashboards reactively; the dashboard checks itself and tells you when to look. Best for: any team that’s ever discovered a problem 48 hours too late because nobody opened the report.

Bottom line: Claude is for quick questions and ad-hoc dashboards. Claude Code is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.

Use cases — what you can actually do once Google Business Profile is connected to Claude

Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their Google Business Profile data — from simple Q&A to full client-facing workflows.

1. Chat and ask questions directly

The simplest use case — and still the one 80% of marketers start with. Open Claude, ask a question, get an answer grounded in live data.

It’s the fastest way to replace a daily Google Business Profile dashboard check-in. But chat is table stakes — the interesting use cases come next.

2. Blend Google Business Profile with your analytics data (Google Analytics 4, Meta Ads, Google Ads)

This is where a 360° view gets real. When you connect Google Business Profile and your web analytics and ad performance (Google Analytics 4 for web traffic, Meta Ads for social reach, Google Ads for paid search), Claude can map local listings to actual website visits and conversions — using location names, campaign names, and timestamps — and give you local SEO performance that no platform-side number can.

Claude handles the location names, campaign names, and timestamps mapping and joins. You get a client-ready local SEO performance report that no single platform can generate on its own.

3. Automated alerts and notifications on Slack or Gmail

With Claude Code you can turn Google Business Profile monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Claude Code scheduled task that pulls performance every morning and pings you only when something actually needs attention.

No dashboards, no daily check-ins. The report comes to you — and only when it matters.

4. Client-ready presentations with live data (Gamma, HTML, PDF)

A common agency pain: you send clients a Google Business Profile dashboard link, Looker breaks, the client panics — and you spend an hour explaining a broken dashboard. With Claude you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.

The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.

Google Business Profile fields and metrics you can query with Claude

Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives Claude access to 145 Google Business Profile fields and metrics across every reporting level, plus breakdowns by location, day of week, review rating, and hour of day. And the same MCP URL also unlocks 25+ other sources — so Claude can blend Google Business Profile with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.

location information

AdWords phone numberAdditional phonesAddress linesAdministrative areaLocation service typeLocation can be deletedLocation can have business callsLocation can have food menus

local post

Local post action typeLocal post offer coupon codeLocal post creation dateLocal post event ending dateLocal post event ending timeLocal post event nameLocal post event starting dateLocal post event starting time

review

Total average review ratingAverage review ratingReview commentReview creation dateReview IDReview star rating (Number)Review modification dateReview Time to Respond (Days)

media customers

GMB customer profile nameGMB customer profile photoGMB customer profile photo URLGMB customer profile URLMedia customer creation dateMedia customers countMedia customers formatMedia customers google photo

time

DateDayDay of week (Mon – Sun)Hour of dayMonthMonth dayQuarterWeek

insight

BookingsConversationsFood ordersImpressions on desktop mapsImpressions on desktop searchImpressions on mobile mapsImpressions on mobile searchDirections requests

media

Media creation dateMedia formatMedia google photoMedia google URLMedia IDMedia thumbnailMedia thumbnail URLMedia views

account id

Account ID

account name

Account name

account state

Account state

follower

Followers

location id

Location ID

location name

Location name

Prompts you can copy-paste today

For agencies

Use these when managing 10–200+ locations across clients with white-label reporting and fast review-response turnaround.

For SEO/SEM teams

Use these when tracking local ranking signals and correlating them with organic search performance.

For e-commerce teams

Use these when using GBP posts to drive foot traffic to showrooms or syncing inventory to listings.

Cross-channel

Use these when blending Google Business Profile with other marketing data sources through the same MCP.

Limits, safety, and best practices for Google Business Profile via Claude

This is the most common “suspension” story in the GBP ecosystem, and it illustrates a critical distinction: Google Business Profile suspensions are triggered by profile-level policy violations (fake names, address conflicts, prohibited categories) — not by API or MCP usage. Marketers connecting GBP to Claude via the official API are not at risk of account suspension. The real cost of mismanagement is quieter: a marketing team bulk-updating 50 locations via API hits the 10 edits-per-minute hard limit, their sync job fails silently, and review-response automation goes down for 24 hours while they wait for quota reset. The pipeline stalls, not the account.

Google’s enforcement is quota-based and scope-based, not tool-based. Google doesn’t suspend accounts because you used Claude or an MCP server. It throttles or returns 429 errors because of how the API was used: exceeding the 300 requests-per-minute project quota, bursting more than 10 edits per minute per location, or requesting data without the correct OAuth 2.0 scopes. Read-only usage within daily quotas (1,000 requests/day for Business Information API, 500/day for Performance API) is safe. Write at scale without batching, parallel bursts across dozens of locations, or ignoring the 10-edits-per-minute hard cap is not.

The two ways to burn through your Google Business Profile quota

After reviewing official docs and community threads, two patterns come up again and again.

1. Bulk write bursts exceeding 10 edits per minute per location. The My Business Business Information API enforces a hard limit of 10 edits per minute per Google Business Profile — this cannot be increased via quota request. Marketers using Claude to programmatically update hours, posts, or responses across dozens of locations will hit this wall immediately. The API returns 429 RESOURCE_EXHAUSTED and the update queue stalls. What to do instead: batch edits, serialize per-location updates with ≥6-second spacing, and use Porter’s built-in rate-limiting backoff.

2. Ignoring OAuth 2.0 scope requirements and PII exposure. The GBP API requires specific OAuth 2.0 scopes (https://www.googleapis.com/auth/business.manage for write access). Granting overly broad scopes to third-party tools or piping raw customer review data (names, emails, phone numbers from review responses) into Claude without data-processing agreements creates a privacy violation, not an API ban. Under GDPR and CCPA, review responder names and customer PII in review text are personal data. What to do instead: use minimum-scope OAuth (read-only where possible), enable Porter’s field-level PII masking before data reaches Claude, and document your data-processing basis.

3. AI-generated content that violates GBP content policies. Google’s Business Profile content policies prohibit spam, deceptive content, and fake engagement. Claude-generated review responses that are overly promotional, repetitive across locations, or fail to address the specific review content can trigger profile-level suspension (not API suspension). A marketer auto-generating 200 identical “Thank you for your feedback!” replies across a franchise chain risks the entire profile group being flagged. What to do instead: use Claude to draft personalized responses with location-specific details, always require human approval before posting, and maintain a response-variation library.

Both behaviors trigger quota exhaustion or profile-level policy enforcement. If you want to use Claude for Google Business Profile safely, stay read-only by default, batch any writes, and never let AI publish without human review.

The 5-rule scaling protocol

Based on Google Business Profile’s documented quotas and the behaviors that have actually caused pipeline stalls — not guesswork:

• Limit requests to 300 per minute across all GBP APIs. This is the default project-level QPM (queries per minute) limit shared across Business Information, Account Management, Performance, Verifications, Q&A, Lodging, Place Actions, and Notifications APIs. Exceeding this triggers 429 errors across all endpoints. [Source: Google Business Profile APIs — Limits] If you ignore this, your multi-location sync job will cascade-fail. Porter MCP enforces per-project request pacing automatically.

• Restrict edits to 10 per minute per Google Business Profile. The My Business Business Information API enforces a hard cap of 10 edits per minute per location. This limit cannot be increased via quota request. [Source: Google Business Profile APIs — Limits] Bulk-updating 50 store hours via Claude without throttling will fail at location #2. Porter serializes write operations per-location with built-in 6-second spacing.

• Stay within 1,000 read requests per day for Business Information API (default). New projects start with 1,000 requests/day for the Business Information API and 500 requests/day for the Performance API. Request a quota increase via the GBP API contact form if you manage 100+ locations. Without this, a daily “sync all locations” job will exhaust quota by mid-morning.

• Use minimum-scope OAuth and mask PII before Claude ingestion. Grant only the scopes your use case requires (business.readonly for reporting, business.manage only if Claude needs to post responses). Review data may contain customer names and contact information. Porter’s field-level transformation can strip PII fields before they reach Claude, keeping your data pipeline GDPR/CCPA-compliant.

• Require human approval for all AI-generated posts and review responses. Google’s content policies prohibit spam and deceptive practices. Claude should draft, not publish directly. Implement a human-in-the-loop checkpoint for any write operation — especially review replies, local posts, and business description updates. This prevents profile suspension due to repetitive or promotional AI content.

What Porter MCP does differently: it enforces these limits at the platform level. Porter’s Google Business Profile connector applies per-project rate limiting with automatic backoff on 429 responses, serializes write operations per-location to respect the 10-edits-per-minute hard cap, and defaults to read-only OAuth scopes unless write access is explicitly enabled. Field-level transformations allow PII masking before data ever reaches Claude. That’s the behavior Google’s automated quota systems handle gracefully — no throttling, no surprise quota burns, no profile suspension risk.

Frequently asked questions