agentleFS
surendranbsurendranb/google-analytics-mcp/skills/content-performance/SKILL.md

content-performance

Skill244 starsChanged 43 days agoMITView on GitHub

Identify top-performing pages, find underperforming content, and understand engagement patterns across your site.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not use pageviews — the correct metric is screenPageViews.

    line 28
  2. Distinctive:

    Run Step 1, then flag pages where:

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Content Performance Analysis

Identify top-performing pages, find underperforming content, and understand engagement patterns across your site.

When to use

  • You want to know which pages drive the most traffic and engagement
  • You want to find pages with high views but low engagement (poor content fit)
  • You want to identify content that drives conversions or return visits

Correct dimension and metric names

ConceptGA4 API name
Page pathpagePath
Page titlepageTitle
Landing pagelandingPage
Page viewsscreenPageViews
Unique page views (users)totalUsers
Engagement rateengagementRate
Avg engagement timeuserEngagementDuration
Scroll depthscrolledUsers (if scroll event is tracked)
Entries (landing views)sessions with landingPage dimension

Do not use pageviews — the correct metric is screenPageViews.

Step 1 — Top pages by traffic

dimensions: ["pagePath", "pageTitle"]
metrics: ["screenPageViews", "totalUsers", "userEngagementDuration",
          "engagementRate", "bounceRate"]
date_range: last 30 days
order_by: screenPageViews DESC
limit: 25

Step 2 — Landing page performance

Which pages do users enter your site through, and how well do they engage:

dimensions: ["landingPage"]
metrics: ["sessions", "newUsers", "userEngagementDuration",
          "engagementRate", "keyEvents"]
date_range: last 30 days
order_by: sessions DESC
limit: 25

Step 3 — Underperforming content (high views, low engagement)

Run Step 1, then flag pages where:

  • screenPageViews is in the top 50% AND
  • engagementRate is below 0.3 (30%) OR userEngagementDuration < 30 seconds

These pages attract traffic but fail to hold attention — candidates for content improvement or better internal linking.

Step 4 — Content trend over time

dimensions: ["date", "pagePath"]
metrics: ["screenPageViews", "totalUsers"]
dimension_filter: pagePath contains "/blog" (or your content path)
date_range: last 90 days
order_by: date ASC

What to report

  • Top 10 pages by views and by engagement time
  • Top 5 landing pages and their conversion rate
  • 3–5 underperforming pages (high traffic, low engagement) as actionable findings
  • Any page with a notable trend (growing or declining) over the period

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.