Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesYou can show WordPress.org directory rating summaries—average rating, number of ratings, and star counts—on another site by retrieving the directory item’s data and rendering those fields. Showing the actual written reviews is different: the official documentation covered here does not establish a generally supported feed for reproducing all review text. For most sites, display a clearly labeled rating summary and link it to the item’s WordPress.org Reviews page.
Choose what you want to display
“Reviews” can refer to two different things: a rating summary or individual written reviews. WordPress’s plugin and theme installer APIs document rating fields, but that does not establish that you can fetch and republish every written review through a supported interface.
- Rating summary: Display the average, rating count, and—when available—the number of ratings at each star level.
- Written review posts: Link visitors to the official WordPress.org Reviews page unless you have independently confirmed a supported way to retrieve and republish the review text.
Keep the source clear: identify the plugin or theme, say that the ratings come from WordPress.org, and show when you retrieved the data. Do not present directory reviews as reviews submitted on your own site.
Choose the API that matches the directory item
For a plugin
Inside WordPress, the plugin installer helper plugins_api() can request rating percentage, total rating count, and per-star counts. Its reviews field is not requested by default. WordPress core’s plugin information screen provides a useful model: it displays the average rating, number of ratings, star distribution, and a link to the WordPress.org reviews page. See the plugins_api() reference.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a theme
For themes, use the theme installer helper themes_api() and explicitly request the rating and per-star count fields. The documented defaults for these fields are false, so do not assume a theme query will include them automatically. See the themes_api() reference.
These helpers are WordPress installer APIs for directory information; they are not the same as your site’s /wp-json/wp/v2/ endpoints. The WordPress REST API is an interface for exchanging JSON data with an individual WordPress site. It does not, by itself, provide WordPress.org plugin or theme directory reviews. The REST API is also optional for building a WordPress theme or plugin. See the REST API Handbook.
Pick an implementation approach
| Approach | Best for | What it can provide | Trade-off |
|---|---|---|---|
plugins_api() |
A WordPress implementation focused on a plugin | Rating percentage, total rating count, and star-count fields | Confirm the current response and directory behavior for the target plugin. Review objects are optional and not requested by default. |
themes_api() |
A WordPress implementation focused on a theme | Theme rating and per-star counts when requested | Request the rating fields explicitly; plugins may filter or override the helper. |
| Your site’s REST API | A front end consuming content from that WordPress site | JSON access to the site’s public content and, subject to normal access controls, protected content | It is not a substitute for the WordPress.org directory APIs. |
| A review plugin such as Site Reviews | Collecting and displaying reviews submitted on your own site | A separate review system for your site | The plugin listing does not establish that it imports WordPress.org reviews; verify import behavior before relying on it. |
Build a useful rating display
- Identify the directory item. Determine whether the page is for a plugin or a theme, and use the corresponding installer API.
- Request the rating fields. For a plugin, request the rating percentage, total count, and star counts you intend to display. For a theme, explicitly request its rating and per-star fields.
- Render only values returned. Present the average, count, and distribution as a summary. Do not imply the numbers are the written reviews themselves.
- Label the source and retrieval date. For example, “WordPress.org rating data retrieved September 30, 2026.” Use the actual retrieval date each time the data is refreshed.
- Link to the original review page. Send visitors to the item’s WordPress.org reviews so they can read the full review context and original posts.
- Handle missing or failed data gracefully. If the request fails or fields are absent, omit the rating display or show a neutral message with a link to the directory page. Do not substitute guessed or stale values.
Escape returned values for the HTML context in which you output them. Keep the display tied to the particular directory item so that a label or link cannot accidentally point to a different plugin or theme.
What to do about written reviews
The documented plugin rating fields distinguish summary data from review objects: review objects are not requested by default. The reviewed official documentation does not establish a generally supported endpoint for retrieving all written WordPress.org reviews for republication. Avoid building a feature that promises a full, live review feed on that basis alone.
If your goal is to let visitors assess the product, show the summary and make the WordPress.org Reviews link prominent. If you want to collect testimonials or ratings on your own site, a separate tool such as Site Reviews may fit that purpose; treat those as your site’s reviews, not imported directory reviews.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Plan for changes and failures
The cited documentation does not establish rate limits, a required caching interval, guaranteed synchronization timing, or legal permissions for republishing directory review text. Do not promise a refresh frequency or full-text import behavior without verifying the current API details and applicable terms for your use.
For a resilient summary, decide how your implementation behaves when the API returns an error, no ratings, or a response without an expected field. A cached last-known summary can avoid an empty page during a temporary failure, but label its retrieval date so visitors can judge its age; do not make it appear current if it is not.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
