seo-posthog treats PostHog as a GA4 alternative or complement for sites that already send pageview events to PostHog. It ships no script and stores no token: all data comes through the PostHog MCP server, and the skill delegates each report to a seo-posthog agent that runs HogQL SELECT queries.
The skill recommends a read-only API key or member so a write cannot succeed even if the prompt rule fails.
What You Get
- A check command that confirms the MCP connection and pageview events
- Reports for organic visits per day, top landing pages, devices, countries and referrers
- Tables labelled as PostHog MCP (live)
- Priority labels for follow-up actions
- Automatic use in /seo audit when the PostHog tool is available
Common Use Cases
- Add organic traffic context to an SEO audit for a PostHog site
- Find which landing pages bring organic visitors
- Split organic traffic by device or country
- Run PostHog beside Google and Matomo data in one audit
What Makes It Unique
It stores no credential and ships no code, and it tells the user to connect the MCP with a read-only key because the exec tool can also create, update and delete PostHog objects. Query results are treated as untrusted data.
Under The Hood
The skill is one instruction file with no scripts. It routes each command to a seo-posthog agent, which runs read-only HogQL SELECT queries through the PostHog MCP exec tool. The extension install script registers the MCP server. Authentication belongs to that server, and the skill tells the model never to ask you to paste an API key into the chat or to write to PostHog.