by Abhishek Kumar
0 (0 reviews)
RenderWhen for Blocks
Show or hide any block when conditions match. Developer-first API and true server-side rendering — hidden blocks never reach the browser.
Tested up to WP 6.9.5 (Current: 7.0.2)
v1.0.0
Current Version v1.0.0
Updated 2 months ago
Last Update on 17 May, 2026
Refreshed 8 hours ago
Last Refreshed on
Rank
#51,321
—
No change
Active Installs
0+
—
No change
KW Avg Position
N/A
—
No change
Downloads
131
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
11,628
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
Need 5 more installs to reach 10+
Rank Changes
Current
#51,321
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 0 of 0| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| No keyword data available yet. | ||||
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.0
- Last Updated
- May 17, 2026
- Requires WP
- 6.5+
- Tested Up To
- 6.9.5
- PHP Version
- 7.4 or higher
- Author
- Abhishek Kumar
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about RenderWhen for Blocks
Yes. Conditions apply to blocks anywhere they render — posts, pages, template parts, navigation menus, and patterns.
Yes. The visibility attribute is registered on every registered block, including blocks from other plugins (ACF Blocks, GenerateBlocks, Stackable, etc.).
Hidden blocks are never rendered into the page HTML. Search engines see what your visitors see — not the hidden content. This is the opposite of CSS-based hiding, where the content is still in the DOM.
Not in v1.0 — one rule per block. AND/OR condition groups are planned for v1.1.
The dashed left border indicates a block has a visibility rule attached. It's editor-only — visitors never see it. The cue helps prevent confusion when blocks disappear from the published version.
The preview can't know which roles an arbitrary visitor would have. When you preview as "Any role," role-restricted blocks appear hidden because the safest assumption is that an unknown visitor doesn't have the required role. To verify a role-restricted block actually shows for that role, pick the specific role from the preview dropdown.
Both are excellent, mature plugins with broader feature sets. RenderWhen is intentionally smaller in surface area, server-side-only in rendering, and built around a public extension API. If you need ACF/WooCommerce/cookie conditions today, use one of those. If you want a small, fast, extensible foundation, this is for you.
By default, via wp_is_mobile() plus a user-agent check for tablets. The result is filterable via renderwhen_device_type so you can plug in a more sophisticated library.
Mostly yes — visibility is evaluated at render time, so server-side page caches will cache whatever was rendered for that request. For varying-by-user content (login state, role), you'll want a cache layer that varies on cookies. The renderwhen_render_block_hidden action is provided so cache plugins and edge integrations can hook in.