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.