WordPress Block Visibility: Hide, Schedule, and Target Blocks

Updated 9 November 2026 · Standard formula, shown below

Block visibility lets you control when a WordPress block appears and, when your editor or an installed plugin supports it, which visitors can see it. You can schedule a promotion, hide optional content, or target a block to a defined audience without deleting it. The exact controls depend on your WordPress editor, theme, and plugins, so check the available settings before relying on them.

What You’ll Need

Access to edit the WordPress page or post and permission to publish changes.
A current backup or a safe staging site if the page is important or the change affects a live campaign.
A visibility feature: some WordPress setups provide basic publishing controls, while block-level schedules or audience rules may require a compatible plugin or theme feature.
A way to preview the page as a visitor, such as a private browser window or a separate test account.

Step-by-Step

Identify the exact block and goal. Open the page or post in the block editor. Select the block you want to control in the canvas or List View. Decide whether you need to hide it for everyone, show it only during a time window, or display it only to a particular audience. These are different rules; confirm that your visibility tool supports the one you need.
Check what controls are available. With the block selected, inspect its settings in the editor sidebar. Look for a visibility, scheduling, display, or conditional-logic panel. If no such panel appears, check the plugin or theme documentation and confirm the feature is enabled. Do not assume the standard editor has a universal per-block scheduler or visitor-targeting option.
Save a recoverable version. Before adding conditions, note the current text and settings, or create a revision or backup. If you are working on a live page, make the change in staging when possible. Avoid installing an unfamiliar plugin directly on a high-traffic site just to test one block.
Set a simple visibility rule first. Configure one condition at a time. For a schedule, choose the start and end dates or times the tool requests. Confirm the time zone used by the site and whether the start and end are inclusive. For audience targeting, choose a clearly defined option, such as a logged-in state or a supported role, only if the tool explicitly offers it.
Keep the rule narrow and understandable. Apply the condition to the smallest block or group that needs it. If several adjacent blocks must appear together, group them and apply one rule to the group if your tool supports that. Avoid overlapping rules, contradictory conditions, or targeting based on assumptions about a visitor that the site cannot reliably identify.
Preview both sides of the condition. Use the editor preview and, where available, the plugin’s condition preview. Then check the published page in a private browser window and while signed out. For audience rules, also test with an account that matches the intended audience and one that does not. An editor preview may show hidden blocks to administrators, so it is not enough on its own.
Publish or update, then verify the live page. Save the settings and publish or update the page. Load the public URL in a fresh session, not just the editor. Check the block before, during, or after the scheduled window as practical, and confirm the intended audience sees the correct version. If a cache is active, clear the relevant page or site cache and retest.
Review and remove expired rules. After a campaign or temporary notice ends, check that the block is hidden or restored as intended. Remove obsolete conditions and verify links, navigation, and nearby content still make sense without the block.

Common Mistakes

Confusing post scheduling with block scheduling. WordPress can schedule a post for publication, but that does not automatically schedule an individual block inside an already published post.
Using the wrong time zone. A schedule may follow the site’s configured time zone rather than your computer’s local time. Check the site’s general settings and the tool’s schedule explanation.
Testing only while logged in. Administrators may see editor previews or cached content that ordinary visitors do not. Test signed out as well.
Relying on hiding for sensitive information. Visibility controls are for presentation, not access security. Do not place private data, credentials, or restricted material in a block and assume a display rule protects it.
Forgetting caching and other display rules. A cache, another plugin, or a theme condition can make an otherwise correct setting appear ineffective or inconsistent.

Tips

Write a short note explaining why a block has a condition and when it should be reviewed.
Use explicit start and end times for temporary content, and set reminders to verify the end behavior.
Keep a visible fallback or useful surrounding text so the page still reads naturally when the block is hidden.
After updates to the editor, theme, or visibility plugin, retest important conditions on the front end.
For content that must truly be restricted, use an appropriate access-control system and test it independently; hiding a block is not a substitute.

Troubleshooting

The block appears when it should be hidden: Confirm the rule is enabled and attached to the intended block or group. Check whether the condition means “show when” or “hide when,” and review date, time, and time-zone settings. Test while signed out, clear page or CDN caches if applicable, and temporarily disable conflicting display conditions on a staging copy.

The block is hidden for everyone: Look for an inverted condition, an expired schedule, or a role rule that does not match your test account. Remove the condition briefly on staging to confirm the block itself still renders. If it does, rebuild the rule with one condition and test again.

The settings panel is missing: Select the block rather than the page, expand the editor sidebar, and check that the relevant plugin or theme feature is active and compatible. If the feature is unavailable, use a supported alternative or consult its documentation instead of adding custom code you cannot maintain.

Changes do not appear after updating: Confirm the page update completed, then open the public URL in a private window. Clear the appropriate cache and check whether a staging/live-site mismatch or another plugin is serving a different version.

A scheduled block changes at the wrong time: Compare the schedule with the site’s configured time zone and the tool’s documented date handling. Adjust the rule, save, and verify the result around the intended boundary.

Frequently Asked Questions

Can WordPress schedule one block without scheduling the whole post?
Only if your installed editor feature, theme, or plugin supports block-level scheduling. Standard post scheduling controls when the entire post is published.

Can I hide a block from logged-out visitors?
Some visibility tools offer logged-in or role-based conditions. Confirm the exact condition is supported and test with a signed-out browser and suitable accounts.

Will a hidden block be deleted?
Usually, a visibility rule changes whether it is displayed rather than removing its content from the editor. Check the tool’s documentation; do not treat hiding as secure deletion or privacy protection.

Why can I see a block that visitors cannot?
Editors or administrators may see preview content regardless of front-end rules. Verify the published page in a private session while signed out.

Does block visibility work with caching?
It can, but cached pages may show an earlier result. Clear relevant caches and check whether the visibility tool supports the site’s caching setup, especially for visitor-specific conditions.

Is block visibility suitable for confidential content?
No. A display condition is not an access-control guarantee. Keep confidential information out of public page content and use a system designed to restrict access.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.