See which posts are actually being read
A digest that separates the pieces people found from the pieces they did not. Built for a content lead who publishes steadily and reviews performance rarely.
Google Analytics
Google Search Console
Notion
4 steps3 integrationsRuns weekly
Analytics is a dashboard nobody opens. What it costs while the work is still done by hand.
- 01Analytics is a dashboard nobody opens.
- 02The best-performing piece is often a surprise.
- 03Next month's plan repeats last month's guesses.
- Pull traffic38 pages · 7d window
- Pull search12k impressions · 340 clicks
- Build digest6 rose · 4 fell · 3 not found
- Post to Notioncreate_page · Content plan
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Pull traffic and engagement per page.Google Analytics
- 02Pull search impressions for the same pages.Google Search Console
- 03Assemble a digest of what rose, what fell, and what nobody found.ModuleX
- 04Post it where the content team plans.Notion
The workflow is an editable graph. Reading runs freely; post it where the content team plans waits for your opt-in approval until you loosen it. The graph is the receipt.
What was actually read. Paste this into ModuleX chat, or hit Use this workflow.
see which posts are actually being read: pull traffic and engagement per page; pull search impressions for the same pages; assemble a digest of what rose, what fell, and what nobody found; post it where the content team plans. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
See which posts are actually being read. A digest that separates the pieces people found from the pieces they did not.
- google analytics · run_report
- google search console · retrieve_site_performance_data
- notion · create_page
A digest that separates the pieces people found from the pieces they did not.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Adapt one announcement for each channelOne announcement, rewritten per channel, reviewed in one place before anything goes out. Built for a one-person marketing team posting the same text everywhere.
Fix what the SEO crawl actually foundA short ordered list of page-level fixes, each already written as a ticket. Built for a marketer holding a 200-row audit export and no idea which row matters.
Flag the campaigns that stopped workingA short list of campaigns to act on, each with the numbers that put it there, and your approval in front of the change. Built for a growth lead who notices wasted spend a month late.
About this use case.
It reports what happened. The call is yours.