Open-source Generative Engine Optimization (GEO) & Answer Engine Optimization (AEO) toolkit — optimize content to rank in ChatGPT, Perplexity, Gemini & Claude. AI SEO / LLM SEO. CLI, Claude Code, MCP.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 82%
Response Time: 11h
First Timer Success: 100%
mverab/eGEOagents has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mverab/eGEOagents respond to incoming external pull requests in approximately 11.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 60.6 places mverab/eGEOagents in the A tier.
The external contributor pull request merge rate for mverab/eGEOagents is 82.1%, based on public PR activity from non-core contributors.
mverab/eGEOagents does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Growing Python project in mverab/eGEOagents welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/mverab/eGEOagents?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~55 hours (37% approval). Keep your diff compact for rapid review.
The documentation would benefit from real-world before/after examples showing E-GEO optimizations. What's needed: Find 2-3 public pages to use as examples Run /geo:audit to save before state Run /geo to generate optimized versions Add to docs/examples.md with: Original content GEO score before/after What changed Screenshot of output Resources: Current examples folder: examples/ Documentation structure in docs/
Currently, optimized content is exported as markdown. Add option to export as HTML. What's needed: Add --format flag to /geo:optimize command Support markdown (default) and html formats Convert markdown to HTML while preserving formatting Example: /geo:optimize content.md --format html # Creates: geo-output/optimized/content.html Resources: Python markdown library: https://pypi.org/project/markdown/ Current export logic in commands
When running /geo:batch on multiple files, users don't see progress until all files complete. What's needed: Show progress indicator during batch processing Display "Processing X of Y files..." Show completion status for each file Example output: Processing batch (3 files)... [1/3] pricing.md ✓ [2/3] about.md ✓ [3/3] contact.md ✓ Complete! Results in geo-output/ Resources: Current batch command: .claude/commands/geo-batch.md Output style: .claude/output-styles/geo-optimizer.md
When optimizing local markdown files with /geo:optimize, preserve frontmatter (YAML/TOML) instead of treating it as content. Example: Input: --- title: My Page description: My description --- # Content here Expected: Frontmatter preserved, only "Content here" optimized. What's needed: Detect frontmatter in markdown files Parse and preserve it separately Only optimize the content body Reassemble with original frontmatter Resources: Python frontmatter library: https://pypi.org/project/frontmatter/ Current file handling in commands
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to mverab/eGEOagents, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of mverab/eGEOagents acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.1% were successfully merged into the primary branch.
mverab/eGEOagents has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 60.6 places mverab/eGEOagents in the Welcoming tier.
The external pull request merge rate is 82.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
mverab/eGEOagents does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for mverab/eGEOagents are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.