Analytics for GitHub Issues

Open-source maintainers track project health through GitHub Issues. BetterMeter bridges the gap between analytics data and actionable work — automatically filing issues when it detects broken links after deploys, performance regressions, or new bot patterns hitting your docs site.

Auto-filed issues with context

When BetterMeter detects an anomaly, it creates a GitHub issue using the REST API. Each issue includes a descriptive title, markdown body with affected URLs and metrics, and auto-applied labels for easy triage.

POST /repos/{owner}/{repo}/issues

{
  "title": "Broken links detected: 43 pages returning 404",
  "body": "## BetterMeter Alert\n\nDetected **43 URLs** returning 404 errors starting at 2026-03-23 14:32 UTC, coinciding with the v2.4.0 release.\n\n### Top affected pages\n| URL | Hits | Referrer |\n|-----|------|----------|\n| /docs/v1/api-reference | 18 | google.com |\n| /guides/quick-start | 12 | github.com |\n| /changelog/2025 | 8 | chatgpt.com |\n| /blog/roadmap | 5 | direct |\n\n### Suggested action\nSet up redirects from old URLs to their v2 equivalents.\n\n[View full report in BetterMeter](https://bettermeter.com/dashboard)",
  "labels": ["bug", "broken-links", "bettermeter"],
  "assignees": []
}

What triggers an issue

• 01 404 spike after deploy — Broken links from renamed or removed pages. Includes referrer data.
• 02 Traffic regression — A key docs page loses significant traffic, suggesting a broken link or SEO issue.
• 03 New bot pattern — An unknown crawler starts aggressively indexing your repo's docs site.
• 04 AI crawler changes — ChatGPT or Claude stops visiting your docs, possibly due to robots.txt changes.

Built for open-source workflows

Open-source projects live on GitHub. Contributors check issues, not analytics dashboards. By creating issues from analytics data, BetterMeter makes site health visible to the entire contributor community. Anyone can pick up a broken-links issue and submit a PR to fix the redirects.