Visigate – Conditional Content & Visibility Rules

Yes. Open the Page/Post settings sidebar, expand Visigate and click “Open Visigate”. You can also open Pattern Visibility from the editor’s Plugins menu (or its eye icon when pinned). Select a synced or inserted unsynced pattern on the page, or choose it from the Pattern placement list. Pick a saved rule set or add custom rules. The rules are saved on that placement, so two uses of the same synced pattern can have different visibility. Rules on blocks inside the original pattern continue to apply as well.

This sidebar also works when WordPress uses content-only pattern editing and hides the usual block settings. You can configure the placement without entering Edit pattern. Pro fallback controls are available in the same panel according to your plan.

No. Visigate works with the block editor on its own, and its Elementor support turns on when Elementor is active. WooCommerce conditions are part of Visigate Pro.

Yes, through the [visigate] shortcode or the visigate_visible() PHP helper. Any builder or theme that can output a shortcode or run PHP can use them.

Select a widget, section, column or container, then open Advanced → Visigate: Visibility and choose a saved rule set or use “Custom rules for this element”. The custom rule builder supports the same conditions, AND/OR groups and show/hide actions as the block editor. If you configure both a saved set and custom rules, both must allow the element to show. Flexbox and Grid containers are supported. A rule on a container controls the whole container and its contents. Elements remain visible while editing in Elementor.

Atomic elements use their own Visigate: Visibility section in the atomic settings panel. Saved sets and custom rules work on atomic widgets and layouts, including Flexbox, Grid and Div Block. Requires an Elementor version with the atomic controls and props-schema APIs; classic Elementor support remains available on older versions.

Visigate loads no CSS or JavaScript on the front end. Rules are checked on the server while the page is being built.

For specific user, device, and time rules, Visigate can flag the page with DONOTCACHEPAGE , which is on by default and can be changed under Visigate settings. Most page cache plugins respect this flag, but some server or CDN caches may not, so you may need to exclude those pages there. Login and role rules usually need no exclusion, because most page caches are bypassed for logged-in users.

Day, time and date rules use the time zone set under Settings → General.

Visigate uses the browser’s user agent on the server, so it detects the device type rather than the screen width. Developers can adjust the result with the visigate_device filter.

Add Specific users and search by display name or username. Is any of matches the selected accounts. Is none of also matches logged-out visitors. Add a Logged in condition in the same group to limit it to signed-in accounts.

Categories / tags is included in Free. Search built-in WordPress categories and tags by name and select one or more. Selecting a parent category also matches its child categories. On a single page/post it checks assigned terms; on a category or tag archive it checks the archive term. Neither operator matches on other views, such as search results or custom-taxonomy archives. Rules use the page being visited, not an item inside a Query Loop. Custom taxonomies, including WooCommerce product categories and tags, require Pro.

Specific Page or Post searches published content by title, including public-facing custom post types. Use is any of to match selected entries or is none of to match other singular entries. Both operators check the page being visited. Archive pages and the blog posts index do not match this condition.

Post type checks the current page’s single item or dedicated post type archive. It supports public-facing custom post types. Page view matches either a single item or a WordPress archive, including category, tag, author, and date archives. Search results and the blog posts index are separate views. These rules check the page being visited, regardless of which item a Query Loop block is displaying.

While logged in as an administrator, open View as in the admin bar on any front-end page and pick a logged-out visitor, a role or a device. The page reloads as that visitor would see it, while you stay logged in. Choose Stop viewing as to go back. More options… opens the full View As screen.

You can also use the Visigate toggle in the admin bar to reveal hidden content, faded and outlined in red. The two work together: reveal hidden content while viewing as a visitor to see exactly what they miss. Only you see these previews.

Yes. In Appearance → Menus, open a menu item and choose a saved rule set or “Custom conditions” under “Visigate: visibility”. Custom conditions use the same visual builder, including Show/Hide actions and AND/OR groups. When visibility rules hide the item, its sub-items are hidden too. In block themes, select a link inside a Navigation block and use its Visibility Rules panel.

The Rule Sets list has a Used in column, and Visigate → Usage lists every rule set. Open one to see each page, post, pattern, template, template part, navigation menu, menu item, widget and Elementor element that uses it. When you trash a rule set that is in use, Visigate asks you to confirm first, because content that uses a missing rule set is hidden. Rule sets used only from PHP, with visigate_visible() , cannot be detected.

Visigate removes its settings but keeps your rule sets, so reinstalling won’t break your pages. Blocks and shortcodes stop being filtered while it’s inactive, so check any sensitive content before you deactivate it.

Yes. Visigate Pro is a separate plugin sold outside WordPress.org. This plugin doesn’t require it.