For SaaS teams
The blog subdomain is its own Search Console property. Not its own question.
Murkuz connects your marketing site, your blog subdomain and your Analytics property to Claude or ChatGPT, read-only. You ask which posts are sliding and which pages convert the traffic they get, and the rows come back with the property and the window attached. Both properties answer in the same reply.
The friction
The data already exists. Getting to it is the work.
The quarterly review is due, so you export the blog property, export the marketing property, then join them in a spreadsheet before you can write a single line.
You paste a screenshot of last quarter into Claude and ask what changed. It reasons from a picture, and it sounds certain either way.
Search Console holds the blog and the marketing site as two properties, so nothing you open is ever the whole funnel.
In practice
You do not learn an interface. You just ask.
These are the questions a content-led growth team argues about on a Monday. You ask in your own words and your agent picks the tool. Reading your own Search Console and Analytics data is never metered, on any plan.
“How did the marketing site and the blog do on clicks this month against last?”
One answer covering both properties, so the review starts from rows rather than two exports.
Get every site you run in one answerAll_Sites_OverviewNo credit“Which posts from last year have been quietly sliding since spring?”
Names the older posts worth an editor's time, instead of publishing over them and hoping.
Spot pages sliding slowly over monthsLive_Content_DecayNo credit“Which blog posts have real search demand and actually convert once people land?”
Separates the posts that fill the funnel from the posts that only fill the traffic chart, on the conversions Analytics measured.
Work out where effort would pay off mostOpportunity_MatrixNo creditNeeds Search Console + Analytics“Are the feature page and the blog post fighting over the same query?”
Catches the product page losing to your own explainer, which is a fix you can ship this week.
Find your own pages competing with each otherLive_CannibalizationNo credit“Which product pages are sitting just off page one on terms with real volume?”
Gives the next sprint a shortlist ranked by what is already close.
Find the keywords you are nearly ranking forLive_Quick_WinsNo credit“Did Google index the pricing page we shipped on Tuesday, and which URL did it pick?”
Settles an argument about a new release page in one call, before anyone blames the CMS.
Ask Google about one specific URLInspect_URLNo credit“What does this competitor rank for that we do not?”
The gap list a roadmap argument needs, and your agent can price the sweep before it runs one.
Find what a competitor ranks for and you do notCompetitor_Gap3 credits
Built for more than one site
Search Console shows you one property. We show you all of them.
Most SaaS teams run at least two properties: the marketing site and a blog on its own subdomain, plus a docs or changelog host once the product grows. Search Console treats each as a separate world, and one connector covers all of them. Stand up a docs subdomain next quarter and it is simply there in the next question.
Two tools take the whole account
Get every site you run in one answer
Every site you run in one response: traffic, direction of travel and what needs attention.
All_Sites_OverviewCompare your sites against each other
Sites compared against each other on the same metrics over the same window.
Portfolio_Comparison
Operator is usually the rung that fits. A marketing site and a blog subdomain count as two properties, not one, and the research credits cover the competitor sweeps a positioning argument runs on.
See what each rung includesSetup
Three steps, then you are done with us.
About three minutes, most of it waiting on Google's consent screen. Read-only, through the official APIs, with your own permissions, revocable from your Google account at any time.
Connect your properties
Sign in with Google, pick the Search Console and Analytics properties you want, then connect Bing Webmaster.
Add Murkuz as a connector
Paste one URL into Claude or ChatGPT and approve it. Any other MCP client works the same way.
Ask, and stop logging in
The web app exists to change what is connected. Most people never open it again.
Questions we get
The things people ask before they connect.
Do the marketing site and the blog subdomain count as one site or two?
Two. Murkuz follows Search Console, where a blog on its own subdomain is a separate property from the marketing site. Both sit behind the same connector, and the cross-site tools answer for both in one reply.
Can Murkuz write the fix or publish to our CMS?
No. Murkuz reads Search Console, Analytics and Bing Webmaster and hands the rows to your agent, which tells you what to change. The only write in the launch surface is submitting a sitemap.
What happens if we have not connected Analytics yet?
The tools that need it say so. A source that is not connected returns a reason explaining what is missing, rather than a zero that would read as bad news about your site.
Does this work in ChatGPT as well as Claude?
Yes. Murkuz is a remote MCP connector, so you paste one URL into Claude, ChatGPT or any other MCP client and approve it. There is nothing to install and no API key to rotate.