SEO / Analytics MCP Bundle
GA4 + Search Console connectors.
Two MCP servers for measurement: Google Analytics 4 reporting and Google Search Console.
Not a promise. A record.
Run the playbook. Then hold the records up to the light.
how to run it
Add both
Connect your properties
And pull GA4 + GSC data straight into Claude for cross-checks
The measurement connectors behind our reports. GA4 and GSC cross-validation built in.
All statistics are valid as of January 2025.
Inside the run · no black box
How the two connectors cross-check the numbers
This kit is not two separate feeds, and not the stock connectors either. It is the measurement line behind our reports, production-hardened from running a live agency: more tools and real-world fixes than the basic versions. GA4 and Search Console run together, so clicks and sessions get cross-checked instead of one source taken on trust.
- Google Search Console MCP pulls impressions, clicks, and positions from search.
- Google Analytics MCP pulls sessions and on-site behavior.
- The two get read side by side, clicks against sessions.
- Any gap between them gets named in the report instead of hidden.
GSC: search clicks and positions in
GA4: sessions and behavior in
CROSS: clicks read against sessions
GAP: any mismatch named, not hidden
One power source. 6 lines out.
seo-analytics-mcp-kit · core
core active · 6 lines
- ✓ diagnose an organic traf…
Diagnose an organic traffic drop with GSC + GA4 read together
- ✓ pull a monthly traffic and
Pull a monthly traffic and search-performance report from real data
- ✓ check index health, cove…
Check index health, coverage and top queries/pages
- ✓ cross-read search clicks
Cross-read search clicks vs GA4 sessions (single-source claims avoided)
- ✓ feed an seo audit with l…
Feed an SEO audit with live impressions, position and conversions
- ✓ wire the connectors into
Wire the connectors into recurring client reports
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Traffic and search data in one assistant, cross-validated
license: perpetual -
Your analytics stays yours, self-hosted, your credentials
license: perpetual -
Real measurement behind every SEO claim, not estimates
license: perpetual -
Foundation for honest, two-source reporting
license: perpetual
subscriptions expire · deeds don't
Two parts. One line.
Watch the work travel, every station is a product you could buy alone. Together, they run as one.
google-
view part →google-search-console-mcp
view part → every part also sold alone, the line is the discount.
Everything in the box.
Pick a piece up. Watch it work.
google-analytics-mcp
2 parts · one working system · ships instantly by email
From the field · a real case
When one source told half the story
A report read traffic from a single source and called it settled. The clicks and the sessions never got lined up, so a tracking gap sat there unseen.
We ran the cross-check. Search Console gave the search clicks, Analytics gave the sessions, and we read them side by side. The mismatch got named in the report instead of smoothed over.
The report stood on two sources that confirmed each other, and the tracking gap surfaced where it could be fixed.
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Teams whose reports lean on one analytics source and have been burned by a silent tracking gap · SEOs who want clicks and sessions cross-checked as a reflex, not a special investigation · Agencies that need GA4 and Search Console data living next to the rest of the work
then this was forged for you.Catch what's on your mind.
-
Why cross-check GSC and GA4 instead of trusting one?
They measure different things, search clicks versus on-site sessions. Reading them side by side catches tracking gaps that one source alone would hide.
-
Is a gap between clicks and sessions always a problem?
Not always. Some difference is normal because they count differently. The point is to name the gap and check it, not to assume the numbers agree.
-
Do these connectors only support reporting?
Reporting is the main use, but the live pulls also back any analysis where the two sources need to be lined up against each other.
-
Any refunds?
No refunds, every claim is proven before you buy. The proof is your safety net.
-
How is it delivered?
A file + install guide, instantly by email. No account needed.
-
Does it only work with Claude?
No. The format is open and any AI can set it up; it just needs an agent harness: Claude Code or a compatible setup (the guide explains it).