How to Connect Claude to Google Business Profile in 2027

Connect Google Business Profile to Claude by authorizing your profile once inside Otto and adding Otto's hosted Claude MCP connector (https://otto.islaintel.com/api/mcp) with a single otto_mcp__ token—skipping Google's 60+ day API application and 0 QPM quota wait. In Otto MCP, Google Business Profile is read-only for daily performance metrics, monthly search keywords, and reviews across 227 tools and 15 integrations, while website NAP, schema, and landing-page fixes stage as WordPress drafts (29 tools) or GitHub pull requests with previews.

Run these five prompts inside Claude once your Google Business Profile is connected through Otto MCP.

Prompt 1: 30-day performance and interaction audit

Inspect my Google Business Profile for the last 30 days. Report daily trends for total interactions, website clicks, call clicks, and driving direction requests. Flag any days where driving directions or calls dropped by more than 20% week-over-week.

Prompt 2: Monthly search keyword comparison against Google Search Console

Pull the top 20 monthly search keywords from my Google Business Profile using locations.searchkeywords.impressions.monthly.list. Compare them with top queries from Google Search Console over the same 30 days. Identify high-intent local queries showing up on Google Maps that lack dedicated service pages on my website.

Prompt 3: Customer review audit and draft-first FAQ creation

Read the latest 25 reviews from my Google Business Profile. Group the recurring questions, complaints, and praise into three clear themes. Then, draft a new FAQ section for my WordPress site that directly addresses these customer concerns, keeping the new content saved as a draft.

Prompt 4: NAP consistency and LocalBusiness JSON-LD schema check

Read the business name, physical address, phone number, and operating hours from my Google Business Profile. Inspect the footer and contact page of my live website. Flag any discrepancies in phone formatting, suite numbers, or weekend hours, and output a valid LocalBusiness JSON-LD schema block matching GBP data.

Prompt 5: Landing-page Core Web Vitals check

Identify the primary website URL listed on my Google Business Profile. Run psi_analyze_url on that landing page for mobile devices. Report the Performance score, Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP), and list the three largest unoptimized assets slowing down mobile visitors.

Remote MCP servers need no per-device install when authentication stays on the server. Connect Claude to Otto MCP to query Google Business Profile metrics in chat.

Google's Business Profile API prerequisites require a verified profile active for 60+ days, a website listed on that profile, and an "Application for Basic API Access" with your Cloud Project Number; until Google approves it, quota stays at 0 QPM instead of 300 QPM.

Daily metrics and monthly search keywords use the Business Profile Performance API (businessprofileperformance.googleapis.com, v1)—including fetchMultiDailyMetricsTimeSeries, getDailyMetricsTimeSeries, and searchkeywords/impressions/monthly. Reviews use the Google My Business API (mybusiness.googleapis.com, v4) at v4.accounts.locations.reviews.

Otto Webmaster is built by IslaIntel in San Juan, Puerto Rico, with 227 tools across 15 integrations for Claude, ChatGPT, and Cursor. Otto exposes read-only GBP data through one HTTP MCP server instead of two Google API projects.

You can connect Claude to your Google Business Profile without applying for Google Cloud developer approval or managing API keys.

Step 1: Connect your Google Business Profile inside Otto

Sign in to your Otto account and navigate to /introduction/connect/google-business-profile. Click Connect Google Business Profile and authenticate using your verified Google account. Otto stores OAuth credentials securely on its server, ensuring third-party API tokens are never exposed in chat prompts.

Step 2: Copy your hosted Otto MCP endpoint and organization token

In your Otto account settings, locate the Model Context Protocol credentials under /introduction/mcp/claude. Copy the hosted server endpoint URL (https://otto.islaintel.com/api/mcp) and your organization-scoped bearer token, which uses the otto_mcp__ prefix.

Step 3: Add Otto MCP as a custom connector in Claude

In Claude Web, Desktop, or Claude Code, add a custom connector with URL https://otto.islaintel.com/api/mcp and your otto_mcp__ bearer token per /introduction/mcp/claude. In Cursor, follow /introduction/mcp/cursor with the same endpoint and token.

Step 4: Query Google Business Profile data in Claude

Ask Claude to list your verified locations. Test the connection by requesting daily performance metrics or monthly search keywords for the past 30 days. Claude queries Otto MCP, which retrieves data directly from Google's read-only endpoints without exposing tokens.

Step 5: Route insights to draft-first website updates

When review themes or keyword shifts indicate that your site needs an update, prompt Claude to stage changes. On WordPress, Otto MCP provides 29 tools (15 read tools and 14 write tools) where new posts and pages default to draft status. For custom codebases, Otto opens pull requests on GitHub paired with Vercel deployment previews. Under Otto v1.1.0, business owners can also review and approve content updates directly from WhatsApp without opening a dashboard.

Clinics, law firms, studios, cafés, agencies, gyms, and salons need listings, sites, and ads to match. Enrique Gomez, Owner of Enzo Maverick Pilates and Experiences Sensory, said: "Otto has been pivotal for us. The ease of making website changes on the fly lets us sharpen our brand and revise as fluidly as we need." Use Otto's AI Website Manager and AI SEO Agent with the steps below.

1. Sync operating hours and LocalBusiness structured data

LocalBusiness structured data tells Google about hours, departments, and contact details for knowledge panels and Maps carousels. When footer copy drifts from Google Business Profile, follow our guides on NAP mismatches and AI Overviews and LocalBusiness schema for citations.

For example, say a Pilates studio extends Saturday hours to 4:00 PM while the site footer still shows a 2:00 PM close. Claude reads verified GBP hours, flags the mismatch, and drafts updated openingHoursSpecification JSON-LD. Otto stages the change as a WordPress draft or GitHub pull request.

2. Convert monthly search keywords into localized service pages

The Performance API searchkeywords/impressions/monthly endpoint shows phrases customers typed before finding you on Maps. Claude can compare those terms to Search Console queries, then draft a missing service page—or an /es/* Spanish variant when both locales are live. New WordPress pages stay drafts until you publish.

3. Audit mobile performance on GBP landing pages

Run psi_analyze_url on the URL listed on your profile when mobile visitors bounce. Our write-up on Core Web Vitals drift ties slow GBP landing pages to lost calls and bookings. Otto v1.1.5 (June 15, 2026) also recompresses uploaded images during maintenance passes.

4. Compile weekly local reviews and search briefings

Otto v1.2.0 (June 24, 2026) added automated weekly SEO reports. Pair GBP reviews from v4.accounts.locations.reviews with GA4 traffic in one Claude thread for a Monday summary of praise, complaints, and local query shifts.

Otto enforces permission boundaries across 227 MCP tools: Otto ships changes only after you approve, and you approve every change that goes live or spends money—except that publishing to Facebook Pages and Instagram through Otto MCP goes live immediately for reviewers and admins on Master, unlike WordPress drafts.

• Read-only analytics: Google Business Profile, GA4, Search Console, Google Ads, YouTube, Google Sheets, Shopify, and PageSpeed Insights are read-only in Otto MCP—no spend or config changes.
• Draft-first websites: Otto works on your existing site, not a new builder. WordPress updates default to draft across 29 tools; GitHub edits open pull requests with Vercel previews.
• Protected pages: Checkout, contact, and legal pages need human approval in Otto core; otto_get_change_log records deploys. Approve or reject from WhatsApp since v1.1.0.
• Paid ads: LinkedIn Ads start as DRAFT; $0 budgets are rejected; Meta writes need reviewer or admin access.
• Social: Facebook Pages and Instagram publishes go live immediately (not draft) and need Master plus reviewer or admin rights—unlike WordPress.