Site Kit is a one-stop solution for WordPress users to use everything Google has to offer to make them successful on the web.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 75%
Response Time: 2d
First Timer Success: 58%
google/site-kit-wp has a recorded first-timer success rate of 58.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in google/site-kit-wp respond to incoming external pull requests in approximately 46.5 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 69.0 places google/site-kit-wp in the A tier.
The external contributor pull request merge rate for google/site-kit-wp is 75.4%, based on public PR activity from non-core contributors.
google/site-kit-wp currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Site Kit is a one-stop solution for WordPress users to use everything Google has to offer to make them successful on the web.
Highly welcoming maintainers in google/site-kit-wp. Prompt code reviews with positive guidance for new contributors.
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/google/site-kit-wp?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~30 hours (94% approval). Large PRs (>500 lines) take ~223 hours (34% approval). Keep your diff compact for rapid review.
Bug Description The plain text version of the email report shows HTML entity codes, such as ’ for an apostrophe and for a space. The HTML version of the same email shows the right characters because the email app turns each code into its character. An email app shows the plain text version when it can't show HTML. The codes appear in three places: A page title in Pages with the most clicks from Search and Pages with the biggest increase in Search clicks. Site Kit gets the title from get_the_title(), which turns an apostrophe into ’ and an ampersand into &. A category name in Top categories by pageviews and an author name in Top authors by pageviews. WordPress stores an ampersand in either name as &. The Analytics tag sends that stored name to Analytics. A Site Goals total of 1,000 or more, such as Total form completions. In Russian, Ukrainian, Czech, and other languages that separate thousands with a space, a total of 1,234 reads 1 234. The total comes
Feature Description This is a follow-up from #11266. That issue updated almost all <p> tags in the codebase, but a few new ones snuck in while this was in progress. I already spent far too much time on that so I'm opening this to follow up on these: assets/js/modules/analytics-4/components/common/MeasurementSettingRow.tsx assets/js/modules/reader-revenue-manager/components/setup/SetupMainExpress/SetupCTANewsletter/DisclaimerText.tsx Any new examples added by the time this reaches execution should also be addressed. Do not alter or remove anything below. The following sections will be managed by moderators only. Acceptance criteria Implementation Brief Test Coverage QA Brief Changelog entry
Bug Description On a small screen, the G on the Site Kit row in the WordPress menu sits higher than the words next to it. Every other icon in the menu lines up with its label. At desktop width the G and the words line up. Steps to reproduce In a browser window under 783px wide, open any WordPress administrator screen. At the top left, click the menu button to open the WordPress menu. Look at the Site Kit row. Expected: the G lines up with the words Site Kit. Actual: the G sits higher than the words. Screenshots Additional Context Plugin Version: (1.185.0). Browser: Chrome. Device: iPhone SE, 375px wide. Do not alter or remove anything below. The following sections will be managed by moderators only. Acceptance criteria Implementation Brief Test Coverage QA Brief Changelog entry
Bug Description When intercepting a request with tweak and returning an error with an empty response payload the request can dispatch an empty error which will be rejected by setErrorForAction and setErrorForSelector, meaning an error will never be set and certain components will not display an error and continue to appear in progress. In all likelihood this is a quirk of tweak, and unlikely to be encountered in the real world, but a few extra lines in siteKitRequest can ensure that a completely empty error is not passed down into the stores and defends against possible edge cases where the promise is rejected with unexpected values. https://github.com/google/site-kit-wp/pull/13294/changes#diff-6a9602e4374f64ce8a1eb8a241d1bcc2beb2df75f3ac6f0c559ecf27738cc2ecR190-R194 🤖 The exact “spinner forever” failure was likely caused by Tweak producing a falsy rejection value such as null, rather than by an ordinary empty HTTP body. A genuine zero-length error response can occur in normal
Bug Description Clicking a point on the graph in Find out how your audience is growing pins its tooltip open. Scrolling the page then moves the tooltip up over the sticky header and the navigation chips, instead of behind them. #4360 and #4496 fixed this for the other dashboard charts. This graph never got the fix. Steps to reproduce Open the Site Kit main dashboard and scroll to Find out how your audience is growing. Click a point on the graph, so its tooltip stays open. Scroll the page down. Expected: the header and the navigation chips cover the tooltip. Actual: the tooltip covers them. Screenshots GIF: the tooltip covers the header while scrolling Additional Context Plugin Version: 1.184.0. Browser: Chrome. Do not alter or remove anything below. The following sections will be managed by moderators only. Acceptance criteria In the Find out how your audience is growing section, clicking a point on the chart below the All Visitors count pins the tooltip open. Scrolling the
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 google/site-kit-wp, 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 google/site-kit-wp acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.4% were successfully merged into the primary branch.
google/site-kit-wp has a recorded first-timer success rate of 58.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 69.0 places google/site-kit-wp in the Welcoming tier.
The external pull request merge rate is 75.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, google/site-kit-wp currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for google/site-kit-wp 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.