Skip to content
SkillModel-led1,433 tokens in use

seo-matomo

Report organic traffic, top pages, devices, countries, referrers and keywords from Matomo Cloud or a self-hosted instance as a GA4 alternative in Claude Code.

31,134 stars on the repository MIT LicenseAgriciDaniel/claude-seo · extensions/matomo/skills/seo-matomo
/plugin marketplace add AgriciDaniel/claude-seo /plugin install claude-seo@agricidaniel-claude-seo
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing seo-matomo costs

78tokens idle
1,433tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure9/25
  • Examples12/15
  • Output15/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 72

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community72
  • Maturity32
  • Momentum40

seo-matomo reads the Matomo Reporting API for teams that own their analytics or avoid Google. It works against Matomo Cloud and self-hosted instances, and its report types match what GA4 users expect: organic trend, landing pages, device and country split, referrers and search keywords.

All requests pass through an SSRF guard that validates the instance URL and refuses private addresses unless you list them in an allowlist.

What You Get

  • A credential check command
  • Seven report commands over the Matomo Reporting API
  • Tables labelled as Matomo Reporting API (live)
  • A share figure for anonymized or not-provided keywords
  • Guidance for instances on private addresses through an allowlist

Common Use Cases

  • Replace GA4 reports with Matomo data in an SEO audit
  • Show organic landing pages for an EU privacy-first site
  • Compare device and country split of organic visits
  • Run both GA4 and Matomo agents in one audit

What Makes It Unique

It covers self-hosted setups with a documented SSRF allowlist (an environment variable naming host and port) and forbids weakening the guard. During /seo audit the orchestrator starts a Matomo agent automatically when credentials check out.

Under The Hood

The skill runs bundled Python scripts through the claude-seo launcher for the auth check and each report. They read the Matomo URL, token and site ID from a permission-restricted JSON file in the profile folder or from environment variables, then call the Matomo Reporting API over the network. Requests are DNS-pinned and redirects off the instance are refused. The skill says it never logs the token.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers