Check Published Blog Performance Across Sprints
Retrieve blog performance for multiple sprints in one request over Content Hub MCP, including a chart, the full publish log, and analysis.
When Claude Desktop is connected to Content Hub through MCP, you can review published content performance across several sprints without opening each sprint in the dashboard. A single request for a range of months returns summary metrics, the list of published content, and a chart. A follow-up request returns analysis.
Before you start, confirm the following:
- The sprints you want to review exist and cover the target months.
- Their topics are published with live URLs, so Google Search Console (GSC) can track them.
- GSC is connected, so click and impression data can populate.
Retrieve blog performance across sprints
Request the performance of published blogs for the June, July, and August 2026 sprint cycles in the Infrasity organization.
Claude Desktop returns a summary table first, with one row per sprint: topics queued, published, publish rate, GSC clicks, and GSC impressions.
- June: 10 topics queued, 9 published (90% publish rate).
- July: 25 topics queued, 14 published (56%).
- August: 32 topics queued, 8 published (25%), with 0 clicks and 0 impressions so far.
Claude also renders a bar chart of topics planned against topics published, which shows the widening gap between the two. It then lists every published title by month:
- June (9 posts): GEO/AEO and conference content, such as "Top 11 Generative Engine Optimization Agencies" and "KubeCon India 2026: Attendee Guide".
- July (14 posts): GitHub and DevTools marketing, such as "Top GitHub Marketing Agencies for Open Source Companies" and "GitHub Marketing Strategies", plus a Qodo/MemClaw case study.
- August (8 posts): A new theme, described in the next step.
Request analysis and takeaways
With the metrics and title list in the conversation, request analysis and takeaways from the data.
Claude Desktop identifies the following trends:
- Volume and execution are diverging. Topics queued per sprint nearly tripled (10, 25, 32), while the publish rate fell from 90% to 56% to 25%. Claude identifies this as the most important trend: planned content exceeds delivery capacity, and the gap widens each month.
- Performance tracks published output, not sprint size. June had the fewest queued topics and the highest completion rate, and produced 14 clicks and 2,010 impressions from 9 posts. July published more than double the output and more than doubled the results (50 clicks, 3,873 impressions), which indicates higher-intent topics. August queued the most topics and published the fewest, with no measurable search performance yet. GSC data takes 2 to 3 weeks to populate, and most August posts went live in the second half of the month.
- Topic selection drives results. The strongest content across the three sprints falls into two themes. GEO/AEO and LLM-search topics, such as "Top LLM SEO Optimization Agencies" and "Top GEO Agencies", include one post that gained over 7,000 impressions in a single month. GitHub/DevTools marketing content delivers steady, compounding clicks across several related posts. Claude concludes that these results reflect a deliberate keyword and topic strategy.
- August introduces an unproven thematic pivot. Four of the seven August posts shifted to Influencer and YouTube marketing, away from the GEO/AEO and GitHub focus of June and July. Claude does not classify this as a miss, because the posts have not yet had time to appear in search data.
Claude closes with numbered takeaways, each paired with an action:
- Clear the draft backlog first. August alone has 24 topics in draft, and this is the highest-leverage fix available.
- Continue investing in GEO/AEO and LLM-search content, the fastest-growing performer.
- Continue building the GitHub/DevTools cluster as a steady, compounding asset.
- Defer evaluation of August until early to mid September, after indexing completes.
- Repeat the July sprint model, which balanced volume with a strong publish rate and the best per-post performance.
A single request for a three-month range produces a chart, a full publish log, and prioritized takeaways in one Claude Desktop conversation.
Open app.infrasity.com and retrieve your most recent sprints to compare planned and published content.
