Tool Integration

Google Analytics + Claude: Post-Click Conversion Data for Local SEO

What happens after the click. Which location pages convert, which traffic sources drive leads, which markets produce business outcomes.

Get on GitHub

Google Analytics Tool Integration: Post-Click Conversion Data

GSC shows organic search performance. LocalSEOData shows SERP and GBP metrics. Local Falcon shows geogrid rankings.

None of them show what happens after the click.

GA4 closes the loop. Which pages convert. Which traffic sources drive qualified leads. Which location pages are producing business outcomes vs. which are just getting visits.

Without GA4 connected, the ROI story is incomplete. You can show rankings improved. You can show traffic increased. You can’t show whether any of it mattered to the business.

What This Integration Unlocks

Post-click performance — Sessions, bounce rate, time on page, and conversion events for every location page.

Source attribution — Which traffic sources drive qualified leads. Organic vs. GBP vs. direct vs. referral — broken down by location page.

Conversion tracking — Form submissions, phone calls, chat initiations — attributed to the local SEO work that drove them.

Geographic revenue mapping — Which markets are converting vs. which are generating traffic that doesn’t produce business outcomes.

Dispatch Routing

Routes to google-analytics-tool when:

  • Prompt involves website traffic analysis
  • Task requires connecting local SEO to business outcomes
  • Location page conversion performance is the question
  • ROI reporting needs actual conversion data

Works alongside GSC for the complete pre-click + post-click picture.

Three Workflows

Workflow 1 — Location Page Performance:

Prompt: "Pull GA4 data for all location pages on smithlaw.com for 6 months.
Which cities drive traffic and which convert best?"

Output:
LOCATION PAGE PERFORMANCE — smithlaw.com GA4 (6 Months)

                          Sessions | Bounce  | Avg Time | Conversions | Conv Rate
/chicago-office/          12,400   | 42%     | 2:34     | 186         | 1.5%
/naperville-office/       8,900    | 38%     | 2:52     | 178         | 2.0%
/oak-park-office/         5,670    | 44%     | 2:21     | 74          | 1.3%
/evanston-office/         2,100    | 61%     | 1:12     | 12          | 0.6%
/skokie-office/           1,800    | 58%     | 1:18     | 14          | 0.8%

Analysis:
- Naperville has highest conversion rate (2.0%) despite less traffic
- Evanston/Skokie have high bounce rates, low time on page
- Traffic quality issue, not traffic quantity issue

Diagnosis — Evanston:
- 61% bounce rate indicates content mismatch
- 1:12 avg time suggests thin content
- Page lacks testimonials, case results, and attorney bios
- Competitors in Evanston market have more comprehensive pages

Action: Enhance Evanston page content before investing in more traffic

Workflow 2 — Local SEO Attribution:

Prompt: "Show me traffic from organic search to location pages for smithlaw.com
before and after our local SEO campaign started in January 2024."

Output:
LOCAL SEO ATTRIBUTION — smithlaw.com

Before Campaign (Jul-Dec 2023):
Source: Organic Search → Location Pages
Sessions: 14,200 total (6-month period)
Conversions: 142 (1.0% conversion rate)
Monthly average: 2,367 sessions, 24 conversions

After Campaign (Jan-Jun 2024):
Source: Organic Search → Location Pages
Sessions: 31,800 total (+124%)
Conversions: 445 (+213%)
Monthly average: 5,300 sessions, 74 conversions

Conversion rate increased from 1.0% to 1.4%
— Traffic quality improved, not just volume

ROI Calculation:
- Average case value: $8,500
- Additional conversions: 303
- Estimated additional revenue: $2,575,500
- Campaign cost: $36,000
- ROI: 7,054%

Attribution breakdown:
- Chicago pages: +156% traffic, +189% conversions
- Naperville pages: +112% traffic, +267% conversions
- Suburban pages: +89% traffic, +134% conversions

Workflow 3 — Geographic Traffic Analysis:

Prompt: "Where are smithlaw.com visitors coming from geographically?
Which metro areas are sending the most qualified traffic?"

Output:
GEOGRAPHIC TRAFFIC ANALYSIS — smithlaw.com (Last 90 Days)

By Metro Area:
                          Sessions | Conv Rate | Revenue Est.
Chicago-Naperville-Elgin  28,400   | 1.6%      | $386,000
Rockford                  2,100    | 0.8%      | $14,300
Peoria                    890      | 0.4%      | $3,000
Springfield               670      | 0.3%      | $1,700

High-Value Submarkets (Chicago area):
Downtown Loop             4,200    | 2.1%      | $75,000
Oak Park                  3,100    | 1.8%      | $47,000
Naperville                2,800    | 2.4%      | $57,000
Evanston                  1,400    | 0.6%      | $7,100
Skokie                    1,100    | 0.7%      | $6,500

Underperforming vs. Investment:
Evanston — Spending $2,400/mo, generating $1,200/mo equivalent
Skokie — Spending $1,800/mo, generating $1,100/mo equivalent

Recommendation:
- Pause Evanston/Skokie investment until conversion issues fixed
- Double down on Oak Park and Naperville (2x+ ROI)
- Rockford worth testing with dedicated landing page

Setup

  1. GA4 property with API access enabled
  2. Google Cloud project with Analytics Data API activated
  3. Service account credentials or OAuth authentication
  4. In Claude Code: Settings → MCP Servers → Add Server
    • Name: Google Analytics
    • Credentials: Service account JSON or OAuth
  5. Verify connection

First Prompt After Setup

"Pull sessions by landing page for [website] for the last 30 days.
Show bounce rate, average session duration, and conversions."

Skill Documentation

For technical details on how this skill works, what data it pulls, and complete prompt reference, see the full skill documentation.

All 36 skills. Free. Open source. Get on GitHub →