Title: Widget Visibility Control Author: Fernando Tellado Published: December 18, 2025 Last modified: August 14, 2026 --- Search plugins ![](https://ps.w.org/widget-visibility-control/assets/banner-772x250.jpg?rev=3442857) ![](https://ps.w.org/widget-visibility-control/assets/icon-256x256.png?rev=3423400) # Widget Visibility Control By [Fernando Tellado](https://profiles.wordpress.org/fernandot/) [Download](https://downloads.wordpress.org/plugin/widget-visibility-control.1.4.0.zip) [Live Preview](https://pcd.wordpress.org/plugins/widget-visibility-control/?preview=1) * [Details](https://pcd.wordpress.org/plugins/widget-visibility-control/#description) * [Reviews](https://pcd.wordpress.org/plugins/widget-visibility-control/#reviews) * [Installation](https://pcd.wordpress.org/plugins/widget-visibility-control/#installation) * [Development](https://pcd.wordpress.org/plugins/widget-visibility-control/#developers) [Support](https://wordpress.org/support/plugin/widget-visibility-control/) ## Description Widget Visibility Control lets you decide exactly where each widget appears on your site. Show widgets only on specific pages, hide them for logged-out users, display different content for different categories – all without writing a single line of code. #### Looking for Widget Visibility and Scheduling? This plugin gives you control over where your widgets appear: * **Page targeting** – Show widgets on the front page, blog page, specific pages, or 404 error page * **Content targeting** – Display widgets only on certain categories, tags, or custom taxonomies * **Cascading taxonomy selector** – Quickly find terms in sites with many taxonomies( WooCommerce friendly) * **Include child terms** – Match child terms automatically for hierarchical taxonomies * **User targeting** – Show different widgets to logged-in users vs. visitors * **Role-based display** – Target specific user roles (administrators, editors, subscribers, etc.) * **Capability targeting** – Go finer than roles and target a specific capability( manage_options, edit_posts, or any capability your plugins add) * **Single content, sticky posts and paginated archives** – Conditions for any single content, for sticky posts, and for page 2 and beyond of an archive * **Author pages** – Control visibility on author archive pages * **Date archives** – Target daily, monthly, or yearly archives * **Post type support** – Works with custom post types and their archives * **Time scheduling** – Schedule widgets to appear only during specific date and time ranges. Perfect for promotional banners, seasonal offers, holiday announcements, flash sales, event countdowns, and time-limited content * **JSON export and restore** – Download all your visibility rules as a file and load them back when you need them, merging into the current setup or replacing it #### Multiple Conditions Create sophisticated visibility rules by combining multiple conditions: * Use **OR logic** – Show if ANY condition matches * Use **AND logic** – Show only if ALL conditions match * Mix and match – Create exactly the rules you need #### Built for Performance * Minimal database queries with intelligent caching * Only loads assets where needed (widget screens) * Clean, optimized code following WordPress standards #### Why Choose This Plugin? * **Lightweight** – Focused functionality without unnecessary features * **All features included** – No premium version required * **Jetpack Compatible** – Migrate from Jetpack Widget Visibility without reconfiguring anything * **Independent Storage** – Your rules are stored separately, safe from Jetpack changes * **Block Editor Ready** – Works with both classic widgets and block-based widgets * **Privacy Focused** – No external connections, no tracking, no data collection * **Safe by design** – No PHP eval, no arbitrary code execution; rules are stored as structured data #### Coming from Jetpack? If you’ve been using Jetpack just for widget visibility and want to reduce your site’s load, this plugin can help: * **No configuration needed** – Your existing visibility rules are automatically imported on activation * **Same familiar interface** – The visibility panel works as you’re used to * **Keep or clean legacy data** – Choose to maintain Jetpack compatibility or clean up completely * **No disruption** – Your widgets will continue working as before #### Coming from Widget Logic? Widget Logic was closed on the WordPress.org plugin directory on 14 April 2026 and no longer receives updates. Widget Visibility Control is a safe, maintained alternative: * **No PHP eval** – Visibility rules are stored as structured data, not as executable PHP code * **Assisted import** – On detection of Widget Logic data, an importer translates the most common conditional tags (is_home, is_page, is_category, current_user_can, is_user_logged_in…) into proper visibility rules, including value lists and negated conditions. Works with data from both Widget Logic 5.x and 6.x * **Works even if you already removed it** – The importer reads the rules Widget Logic left in your database, so it works whether the plugin is still active, deactivated, or deleted * **You decide what’s tricky** – For rules we can’t translate automatically, the importer explains why and asks per widget whether to import as always visible, always hidden, or skip * **Original data preserved** – Your Widget Logic data stays in the database until you choose to clean it up, and the original code of each imported widget is kept as a reference even after that #### Coming from Widget Options? If you only use Widget Options for visibility and want a lighter, focused plugin without the pro upsells: * **No pro version** – All features included in the free plugin * **Visibility-first** – We do one thing well: show/hide widgets based on pages, content, users, roles, and schedule * **Compatible interfaces** – Works in the block-based widget editor, the classic widget editor, and the Customizer * **Quick try** – Install alongside Widget Options to compare; switch when you’re ready #### Developer Friendly * Follows WordPress Coding Standards * Fully translatable with complete i18n support * Action and filter hooks for customization * Clean uninstall – removes only its own data ### Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just [contact me](https://pcd.wordpress.org/plugins/widget-visibility-control/widget-visibility-control@ayudawp.com?output_format=md) and tell me what you need. Need help or have suggestions? * [Official website](https://servicios.ayudawp.com) * [WordPress support forum](https://wordpress.org/support/plugin/widget-visibility-control/) * [YouTube channel](https://www.youtube.com/@AyudaWP) * [Documentation and tutorials](https://ayudawp.com) Love the plugin? Please [leave us a 5-star review](https://wordpress.org/support/plugin/widget-visibility-control/reviews/#new-post) and help spread the word! ### About AyudaWP We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements. ## Screenshots [⌊Visibility Options settings on classic widgets⌉⌊Visibility Options settings on classic widgets⌉[ Visibility Options settings on classic widgets [⌊Visibility Options settings on block based widgets⌉⌊Visibility Options settings on block based widgets⌉[ Visibility Options settings on block based widgets [⌊Multiple conditions with AND/OR logic⌉⌊Multiple conditions with AND/OR logic⌉[ Multiple conditions with AND/OR logic [⌊Data Summary tab in the plugin settings⌉⌊Data Summary tab in the plugin settings⌉[ Data Summary tab in the plugin settings [⌊Import/Export tab in the plugin settings⌉⌊Import/Export tab in the plugin settings⌉[ Import/Export tab in the plugin settings ## Installation 1. Upload the `widget-visibility-control` folder to `/wp-content/plugins/` 2. Activate the plugin through the ‘Plugins’ menu in WordPress 3. Configure visibility rules for your widgets (see “Where to find visibility settings” below) #### Where to find visibility settings The location of visibility settings depends on your widget editing interface: **In Appearance > Widgets (block editor):** When using native block widgets, select any block in a widget area, then look in the right sidebar for the **Visibility** panel. Here you can add rules to show or hide the block. **In Appearance > Widgets (with Classic Widgets plugin):** If you have the Classic Widgets plugin active, click the **“Visibility”** button that appears below each widget’s settings. **In Appearance > Customize > Widgets:** The Customizer always uses the classic interface. Click the **“Visibility”** button below each widget’s settings to configure rules. **Legacy Widgets in block editor:** When you add a Legacy Widget block, expand the widget settings and you’ll find the **“Visibility”** button in the classic interface within the block. **Coming from Jetpack?** Your existing visibility rules will be automatically imported. Visit Appearance > Widget Visibility to review your imported data. ## FAQ ### Does this work with the block-based widget editor? Yes! Widget Visibility Control works with all widget editing interfaces: * **Block-based widgets** (Appearance > Widgets): Visibility settings appear in the **Visibility** panel in the right sidebar. * **Legacy Widgets** in the block editor: The classic “Visibility” button appears within the legacy widget interface. * **Classic Widgets plugin**: If you prefer the traditional widget interface, the“ Visibility” button appears below each widget. * **Customizer** (Appearance > Customize > Widgets): Always uses the classic “Visibility” button interface. ### I’m using Jetpack. Will my visibility rules be preserved? Yes. On activation, the plugin automatically imports all your existing Jetpack Widget Visibility rules. No reconfiguration needed. ### Can I use this alongside Jetpack? Yes, but to avoid conflicts, our visibility interface is automatically disabled while Jetpack Widget Visibility module is active. You can continue using Jetpack’s interface, and when you disable the Jetpack module, our interface will take over automatically. Your visibility rules are stored in both formats, so the transition is seamless. ### What happens if I deactivate or uninstall this plugin? On deactivation, your rules are preserved for when you reactivate. On uninstall, only this plugin’s data is removed. If you haven’t cleaned the legacy data, Jetpack can still read your original rules. ### Can I use multiple conditions on a single widget? Yes. You can add multiple conditions and choose whether ALL conditions must match( AND logic) or just ONE condition needs to match (OR logic). ### Does this plugin slow down my site? No. The plugin is optimized for performance with intelligent caching. Assets only load on admin widget screens, and frontend checks are minimal and cached. ### Does this require a WordPress.com connection? No. This plugin works completely standalone without any external connections or dependencies. ### Does this work with full site editing (FSE) themes? This plugin is designed for widget areas (sidebars, footers, etc.). Full Site Editing themes typically don’t use traditional widget areas – instead, they manage all content through the Site Editor using template parts and blocks. If your FSE theme includes widget areas, the plugin will work in those areas. If you need conditional visibility for blocks in FSE templates, you would need a different solution designed for the Site Editor. ### How does time scheduling work? Time scheduling allows you to show or hide widgets during specific date and time ranges. This is ideal for: * **Promotional banners** – Display ads only during sale periods * **Seasonal content** – Show holiday greetings or seasonal offers automatically * **Flash sales** – Schedule countdown widgets for limited-time deals * **Event announcements** – Display event info until the event date passes * **Time-sensitive notices** – Show maintenance warnings or temporary announcements You can configure: * **Show only during period** – Widget appears only between the start and end dates * **Hide during period** – Widget is hidden between the start and end dates * **No end date** – Widget starts showing from a specific date and continues indefinitely The schedule uses your WordPress timezone setting (Settings > General). If you also have visibility rules configured (like “show only on homepage”), both conditions must be met – the widget will only appear on the homepage AND within the scheduled time range. ### How does the taxonomy selector work on sites with many taxonomies? When you select “Taxonomy” as a condition, a second dropdown appears where you pick the specific taxonomy (e.g., Product Category, Color, Size). Only then does the third dropdown show the terms for that taxonomy. This cascading approach makes it much faster to find the right term on WooCommerce sites or any site with many custom taxonomies. For hierarchical taxonomies, you can also check “Include children” to automatically match all child terms of the selected term. ### Can I import my rules from Widget Logic? Yes, both from Widget Logic 5.x and 6.x — they use the same storage format in the database. When the plugin detects Widget Logic data, you’ll see a notice and a section in Appearance > Widget Visibility > Import / Export. The importer shows each widget that had Widget Logic code, the original PHP, and the rule we extracted. For widgets whose code we can’t translate automatically, you decide per widget: import as always visible, import as always hidden, or skip. ### What Widget Logic functions are supported on import? Most of the common conditional tags: is_home, is_front_page, is_single, is_singular( with or without a post type), is_page (with an ID, a slug, or no arguments at all), is_category, is_tag, is_author, is_archive, is_search, is_404, is_date / is_day / is_month / is_year, is_user_logged_in, is_sticky, is_paged, is_attachment, is_privacy_policy, is_tree, current_user_can, is_tax, has_term, has_category, is_post_type_archive, in_category, and has_tag. WooCommerce shops are covered too: is_product, is_shop, is_cart, is_checkout, is_account_page, is_product_category, is_product_tag and is_woocommerce. Rules that are just a constant (true, false, or combinations like !(true || false)) import as always visible or always hidden. Lists of values are supported too, in both notations: is_page( array( 1, 2, 3 ) ) and is_page( [ 1, 2, 3 ] ). So are negated rules like !is_home(), !is_page(2) &&! is_page(3), or !( is_home() || is_category(5) ), which are imported as “hide” rules. Combinations using only AND or only OR are supported. What still cannot be translated automatically: mixed AND/OR expressions, a negated condition combined with a positive one, wp_is_mobile, code reading $_SERVER or post meta, and custom functions. For those the importer tells you why and asks what to do with that widget. ### Will my Widget Logic data be deleted after import? No. The original Widget Logic data stays in the database so you can roll back if needed. From Appearance > Widget Visibility > Import / Export you can delete it later with “Remove Widget Logic data”. ### Can I export and restore my visibility rules? Yes, both. In Appearance > Widget Visibility > Import / Export, the Export section downloads a JSON file with every rule, which widget each one belongs to, the plugin version and the site it came from. The same section restores a file back, so it works as a real backup and as a way to carry a setup from a staging site to production. When restoring you choose what happens to what is already there: **Merge** only touches the widgets present in the file and leaves the rest alone, while **Replace** clears every current rule first so the site ends up exactly as the file describes. Rules are matched to widgets by their identifier (`text-3`, `categories-2`…), so a restore lands correctly on the same site or on a copy of it. On a different site the identifiers may belong to other widgets, so check the result. Anything the file contains that this version does not understand is skipped and reported, never imported half-way. ### Can I import my rules from Widget Options? Not yet. Widget Options stores its visibility data in a format that’s very different from Widget Logic and Jetpack, and an importer is a separate effort. If you only used Widget Options for visibility, you can configure the equivalent rules in our plugin manually — the most common scenarios (pages, post types, taxonomies, user roles, login state) are all supported. ## Reviews ![](https://secure.gravatar.com/avatar/4ce628d6c37c97d8bf7dbe1779249bf47e702d3d1ce415f64d7423a96b2caae9? s=60&d=retro&r=g) ### 󠀁[Another excellent plugin](https://wordpress.org/support/topic/another-excellent-plugin-2/)󠁿 [Alain Aubry](https://profiles.wordpress.org/caban13/) May 17, 2026 1 reply Another excellent plugin—thank you! As expected from Fernando Tellado, this plugin is simple, focused, and does exactly what it promises without unnecessary complexity. I had been using another plugin for the same purpose, but it was full of ads, upsells, and artificially restricted features. After years of frustration, switching to this was a relief. What stands out the most: All features are available in the free version, with no hidden limitations. Clean and focused functionality—no bloat, just what you need. No external connections, tracking, or data collection, which is increasingly rare and very appreciated. If you’re looking for a lightweight and trustworthy solution for widget visibility control, this plugin is a solid choice. ![](https://secure.gravatar.com/avatar/1015a864deb5e9e809793ead209f4e37bd012c743a034dc96c7623834e9f02de? s=60&d=retro&r=g) ### 󠀁[Good plugin](https://wordpress.org/support/topic/good-plugin-7325/)󠁿 [Themico](https://profiles.wordpress.org/themico/) April 14, 2026 3 replies The plugin works and is made for optimization.One ask – when there are many taxonomies( WC site) with many terms. When you select a Taxonomy, it takes minutes to find a term in the dropdown, because they are all listed in one dropdown. Would be great to have Txonomy > Select specific taxonomy > Select term in that taxonomy. ![](https://secure.gravatar.com/avatar/8439c0b8e69dba402a16468e80e8f09ee3113b50c71fecbe41426ef070b3d1cd? s=60&d=retro&r=g) ### 󠀁[Good one](https://wordpress.org/support/topic/good-one-629/)󠁿 [Alvaro Torres](https://profiles.wordpress.org/algato333/) January 16, 2026 1 reply A must! ![](https://secure.gravatar.com/avatar/5b0a1b43796cabd58557441ad319e078e81a1cf7020562e73b1c377da0d5bd37? s=60&d=retro&r=g) ### 󠀁[Needed for control](https://wordpress.org/support/topic/needed-for-control/)󠁿 [Héctor Tellado](https://profiles.wordpress.org/hectortellado/) January 12, 2026 Just great to add some control when you have so many over the years [ Read all 4 reviews ](https://wordpress.org/support/plugin/widget-visibility-control/reviews/) ## Contributors & Developers “Widget Visibility Control” is open source software. The following people have contributed to this plugin. Contributors * [ Fernando Tellado ](https://profiles.wordpress.org/fernandot/) * [ Ayuda WordPress ](https://profiles.wordpress.org/ayudawp/) “Widget Visibility Control” has been translated into 2 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/widget-visibility-control/contributors) for their contributions. [Translate “Widget Visibility Control” into your language.](https://translate.wordpress.org/projects/wp-plugins/widget-visibility-control) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/widget-visibility-control/), check out the [SVN repository](https://plugins.svn.wordpress.org/widget-visibility-control/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/widget-visibility-control/) by [RSS](https://plugins.trac.wordpress.org/log/widget-visibility-control/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.4.0 * New: Export and restore — download every visibility rule as a JSON file and load it back later, with a choice of merging it into what you already have or replacing everything. Replaces the placeholder that was in the Import / Export tab, and works as a real backup or as a way to move a setup from staging to production. * New: “Capability” rule type — show or hide widgets based on a specific user capability( manage_options, edit_posts, or any capability registered by your plugins), not just by role. The list of capabilities can be tailored with the `ayudawp_wvc_capabilities` filter. * New: Three new page conditions — any single content, sticky post, and paginated archive (page 2 and beyond). * New: The Widget Logic importer understands many more rules: current_user_can(), is_singular(), is_sticky(), is_paged(), is_page() with no arguments, has_term(), has_category(), is_attachment(), is_privacy_policy(), is_tree(), lists of values such as is_page( array( 1, 2, 3 ) ) in both array notations, and negated conditions such as !is_home() or !is_page(2) && !is_page(3). * New: The Widget Logic importer covers WooCommerce shops: is_product(), is_shop(), is_cart(), is_checkout(), is_account_page(), is_product_category(), is_product_tag() and is_woocommerce(). * New: Widget Logic rules that are just a constant, like true, false or !(true || false), now import as always visible or always hidden instead of asking you to decide. * New: The original Widget Logic code is now kept when you import, including for the widgets you decide by hand, so you can still check what each widget used to do even after removing the Widget Logic data. * Improved: The Widget Logic notice and the import screen now state that Widget Logic was closed on the WordPress.org plugin directory on 14 April 2026, and explain that the import works even if the plugin is already deactivated or deleted. * Improved: Clearer explanations in the importer for the rules that still cannot be translated automatically, so it is easier to decide what to do with each widget. * Improved: The Import / Export sections can now be folded away, and each one remembers whether you left it open. Export is now the first section, since the import steps stop being useful once you have run them. * Improved: Tested up to WordPress 7.1 * Fix: The “Dismiss” button on the Jetpack and Widget Logic notices was rendered as an underlined link inside a box instead of a regular button. For older changelog entries, please check the [changelog.txt](https://plugins.svn.wordpress.org/widget-visibility-control/trunk/changelog.txt) file ## Meta * Version **1.4.0** * Last updated **7 days ago** * Active installations **100+** * WordPress version ** 5.8 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Languages * [English (US)](https://wordpress.org/plugins/widget-visibility-control/), [Spanish (Chile)](https://cl.wordpress.org/plugins/widget-visibility-control/), and [Spanish (Spain)](https://es.wordpress.org/plugins/widget-visibility-control/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/widget-visibility-control) * Tags * [jetpack](https://pcd.wordpress.org/plugins/tags/jetpack/)[widget logic](https://pcd.wordpress.org/plugins/tags/widget-logic/) [Widget Options](https://pcd.wordpress.org/plugins/tags/widget-options/)[widget visibility](https://pcd.wordpress.org/plugins/tags/widget-visibility/) * [Advanced View](https://pcd.wordpress.org/plugins/widget-visibility-control/advanced/) ## Ratings 5 out of 5 stars. * [ 4 5-star reviews ](https://wordpress.org/support/plugin/widget-visibility-control/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/widget-visibility-control/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/widget-visibility-control/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/widget-visibility-control/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/widget-visibility-control/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/widget-visibility-control/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/widget-visibility-control/reviews/) ## Contributors * [ Fernando Tellado ](https://profiles.wordpress.org/fernandot/) * [ Ayuda WordPress ](https://profiles.wordpress.org/ayudawp/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/widget-visibility-control/)