Overview
Most teams have the data and none of the answers. Analytics lives in one dashboard, content lives in the CMS, and the question you actually care about — which of our pages are quietly rotting? — sits in the gap between them. Answering it usually means exporting two spreadsheets and spending an afternoon with a lookup formula.
Ask the agent instead. How many pages are live, what has not been touched in a year, which articles convert, where traffic actually comes from — all answered against your real content graph and your real analytics, joined up by URL. No dashboards to learn and no filters to configure.
The important difference from a normal report is what happens next. Because the thing answering the question is also the thing that can edit your site, every report can end in action rather than a to-do list.
How it works
- You ask a question in plain language — no query syntax, no report builder.
- The agent queries your content graph for what exists and when it last changed.
- It joins that to analytics and search data by URL.
- Results come back ranked — by traffic, age, conversion or whatever you asked about.
- Each report ends with suggested fixes the agent can carry out on request.
Questions teams actually ask
- Which blog posts have not been updated in 12 months but still get traffic?
- How many visits came from LinkedIn, email or referrals last month?
- Which pages are missing a meta description or alt text?
- What did we publish last quarter, and which of it earned any search impressions?
- Which service pages have no internal links pointing at them?
Why teams use it
- Plain-language questions — no dashboards or filters to learn.
- Actionable output — every report ends with suggested fixes the agent can make.
- Monday reports — schedule recurring reports to your inbox.
- Client-ready documents — export any report as a branded PDF or an interactive dashboard.
Staying in control
Reporting is read-only by nature — asking a question never changes your site. When a report suggests a fix, carrying it out is a separate, explicit request that follows the usual rules: draft or staging first, scoped to your permissions, approval before anything goes live.
Figures are quoted from the connected sources rather than estimated, so a number in a report is a number you can defend in a meeting.
Availability
Included on every plan. Traffic figures need Google Analytics connected under Integrations.
Frequently asked questions
Which data sources can it report on?
Your CMS content graph is always available. Connect Google Analytics 4 for traffic and channel data and Google Search Console for impressions, clicks and ranking positions. Connecting Google is a consent link that you approve, and no credentials ever pass through the agent — Analytics access is read-only, while Search Console access also allows your sitemap to be submitted after you publish.
Can we get reports automatically?
Yes. Any report you can ask for can be scheduled — a Monday morning summary of last week’s traffic, a monthly content-freshness audit, a quarterly client review — delivered to your inbox as a PDF or a link to an interactive dashboard.
Can it fix the problems it finds?
That is the whole point of reporting inside the same tool that edits your site. Spot forty pages with missing meta descriptions and you can ask for them to be written in the same conversation — as drafts, for your approval, rather than applied silently.
Is this a replacement for Google Analytics?
No — it reads from it. GA4 remains your measurement system; the agent saves you the trip to the dashboard and, more usefully, joins that data to your content so you can ask questions neither tool can answer alone.
Can clients see reports without portal access?
Yes. Export as a PDF you can attach to an email, or share the interactive dashboard. Agencies on Growth and above can also brand the portal with their own logo and colours before giving a client direct access.
