by Bahar Hussain 0 (0 reviews)

Awesome Content Reactions

Name: Awesome Content Reactions
Author: Bahar Hussain

Add like buttons and emoji reactions to WordPress posts and pages, with reaction counts, analytics, and no external tracking.

Awesome Content Reactions ranks #73,012 among WordPress.org plugins with 0+ active installations, is #2,286 of 2,802 in the Contact Forms category, and was last updated Oct 30, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v3.0.0 Current Version v3.0.0

Updated 2 days ago Last Update on 30 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#2,286 of 2,802 in Contact Forms Actively maintained

View on WordPress.org

Rank

#73,012

— No change

Active Installs

— No change

KW Avg Position

— No change

Downloads

+69 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 0%

0+ 10+

45,444

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 10 more installs to reach 10+

Rank Changes

Current #73,012

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 3.0.0
Last Updated: Oct 30, 2026
Requires WP: 6.4+
Tested Up To: 7.1.4
PHP Version: N/A
Author: Bahar Hussain

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

emoji reactions engagement feedback like button post reactions

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More

5M+ installs

Jetpack – AI Agents & MCP, Security, Backup & Analytics

3M+ installs

#17

MC4WP: Mailchimp for WordPress

1M+ installs

#35

Hostinger Reach – AI-Powered Email Marketing for WordPress

Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

800K+ installs

#81

Joinchat – Enhanced “click to chat”

700K+ installs

#89

View all Contact-forms plugins

Frequently Asked Questions

Common questions about Awesome Content Reactions

Enable automatic placement under Content Reactions > General. You can also place reaction buttons manually with the Content Reactions block or the [bhcr_reactions] shortcode. Enable the Like reaction and disable other reactions if you want to show only a like button.

Yes. Enable guest reactions in the plugin settings. A first-party cookie identifies returning guests after their first reaction; clearing cookies creates a new anonymous identity.

This plugin is the renamed successor of Post Reactions 2.3.0. Install and activate it, then deactivate Post Reactions; while Post Reactions is active, this plugin waits and shows a notice. On the next page load it moves the reactions table, settings, reaction definitions, and per-post choices. Existing [bh_post_reactions] shortcodes and Post Reactions blocks keep rendering on the site, and guests keep their reactions. Delete Post Reactions only after the move (if it was already deleted with "Keep reaction data" on, its data is still moved). On multisite, each site moves its own data on its first page load. Theme code that calls bh_post_reactions_render() or uses bh_post_reactions_* filters must switch to the bhcr_ names.

No. Reaction data stays in the site's WordPress database.

When a guest reacts for the first time, the site sets a first-party, HTTP-only cookie named bhcr_visitor that holds a random anonymous identifier for one year. Viewing reactions does not set the cookie. The database stores a keyed hash of the identifier, not the cookie value or an IP address. Clearing cookies creates a new anonymous identity, so guest reactions are not a strong one-person-one-vote mechanism.

Reaction writes are rate limited per visitor identity and per network address for each piece of content. The network limit uses a keyed hash of the connecting IP address in a short-lived cache entry (at most 10 minutes). Behind a reverse proxy that does not pass the visitor address to PHP, use the bhcr_rate_limits filter to adjust or disable the network limit. Limits are exact with a persistent object cache; without one they are approximate under bursts of simultaneous requests. Rate limiting slows scripted voting; it does not make anonymous voting abuse-proof.

Yes. Pages contain no personal reaction state; each visitor's state is loaded from the REST API, whose responses are sent with Cache-Control: private, no-store. If a CDN or proxy is set to cache everything regardless of headers, exclude /wp-json/bhcr/ and bypass the cache for signed-in visitors, or visitors may see each other's selections.

Choose "Manual only" under Content Reactions > General > Automatic placement, then use the Content Reactions block, [bhcr_reactions], or bhcr_render() in a theme. The shortcode accepts post_id, reactions (comma-separated keys), and layout (one of the six layout keys). A block placed in a site-editor template or template part is detected, so automatic placement does not add a second component.

Check that the reaction is enabled, that its position is within "Maximum reactions shown", and, for a single post, whether the post's Content Reactions box uses "Use all enabled reactions" or a specific selection.

Frontend styles are scoped to the component and use high-specificity selectors so that generic theme button styles do not change it. To customize it, target the component's own bh-post-reactions classes with a selector of equal or higher specificity.