WordPress made a big bet on the block editor. Every piece of content on your page—headings, paragraphs, images, buttons, groups—is a block. You can rearrange them, style them, nest them inside each other. It’s a flexible system.

But there’s one thing blocks can’t do out of the box: respond to time.

You can’t tell a block to appear only during business hours. You can’t swap a “Register Now” button for an “Event Has Ended” message after a deadline passes. You can’t show Friday’s promotion on Friday and Monday’s promotion on Monday. Every block you publish is visible to every visitor, all the time.

That’s a problem if your content has any relationship to a calendar.

Why Block-Level Scheduling Matters

Page-level scheduling already exists in WordPress. You can schedule an entire post or page to publish at a future date. But that’s a blunt tool. It publishes or unpublishes the whole page. What if you only need to change one section?

Think about a university department page. The core information—faculty bios, office locations, program descriptions—stays the same year-round. But the sidebar needs to show different announcements depending on the academic calendar: application deadlines in the fall, registration reminders in January, commencement details in the spring. Without block-level scheduling, you’d either maintain multiple copies of the page or set calendar reminders to manually swap that sidebar content every few months.

Block-level scheduling lets you keep one page and attach time rules to individual blocks within it. The stable content stays put. The time-sensitive content rotates on its own.

How It Works in the Gutenberg Editor

Advanced Content Scheduler adds scheduling directly to the block editor. You don’t need shortcodes, custom fields, or a separate interface. The workflow stays inside Gutenberg where you’re already building your content.

Here’s the basic idea: you wrap any block (or group of blocks) in a schedule container. Then you define one or more time slots, each containing its own content. The plugin evaluates the current time against your rules and renders only the matching content on the front end.

A Simple Example

Say you run a café and want your homepage hero to reflect the time of day.

You’d create a schedule container with three time slots:

Morning (6 AM – 11 AM): A hero image of coffee and pastries with the text “Start your morning with us.”

Afternoon (11 AM – 5 PM): A lunch spread with “Fresh sandwiches and salads, made to order.”

Evening (5 PM – 10 PM): A dimly lit dining scene with “Join us for dinner and drinks.”

Each slot contains normal Gutenberg blocks—images, headings, paragraphs, buttons. You build them the same way you build any other content. The schedule container just controls which set is visible at any given time.

Recurring Rules

Most scheduled content follows a pattern. Your lunch menu doesn’t just appear once—it appears every day from 11 to 2. Recurring rules let you define these patterns without recreating the schedule each week.

You can set rules based on time of day, day of week, or both. “Every weekday from 9 AM to 5 PM” is a single rule. “Saturdays and Sundays, all day” is another. The plugin evaluates these rules on each page load, so visitors always see the right content.

Exceptions

Recurring rules need exceptions. Your office is open every weekday—except holidays. Your promotion runs every weekend—except during your annual clearance event when different messaging takes over.

Exceptions let you override a recurring rule for specific dates. You define the exception once, and the schedule skips that date without you having to remember to intervene.

Multiple Schedules on One Page

Nothing limits you to one schedule per page. A real-world page might have several:

A gym’s class schedule page could have one schedule container rotating the featured class of the day in the hero section, another toggling between “Open Now” and “Currently Closed” in the header, and a third showing weekday vs. weekend class timetables in the main content area.

Each schedule operates independently. They can overlap, cover different time ranges, or target different parts of the page.

What You Can Schedule

Any block. That’s the short answer.

Because the schedule container wraps standard Gutenberg blocks, anything you can put inside a group block can be scheduled. Paragraphs, images, buttons, embeds, WooCommerce product grids, form blocks from your favorite plugin—if it’s a block, it’s schedulable.

This also means you can schedule nested layouts. Put a columns block inside a time slot, and you’re scheduling an entire multi-column layout. Put a reusable block inside, and you’re scheduling content that’s shared across multiple pages.

The Alternative: Doing It Manually

Without block-level scheduling, site owners typically handle time-sensitive content in one of these ways:

Manual updates. Someone logs in and edits the page when content needs to change. This works for infrequent changes, but it doesn’t scale. It also depends on someone being available at the right time—which is why your “Black Friday Sale!” banner was still up on December 3rd.

Multiple pages. You create separate pages for each variation and swap links or redirects. This fragments your SEO, confuses your navigation, and creates maintenance headaches.

Custom code. A developer writes PHP or JavaScript to conditionally render content based on time. This works, but it’s fragile, hard to maintain, and impossible for non-developers to update.

Third-party page builders. Some page builders offer basic visibility conditions, but they lock you into their ecosystem and often don’t integrate cleanly with the native block editor.

Block-level scheduling in Gutenberg avoids all of these tradeoffs. You stay in the native editor, you maintain a single page, and content authors can manage schedules without touching code.

SEO Considerations

A common concern with dynamic content is SEO impact. If Google crawls your page at 2 AM, does it see the overnight content instead of your primary messaging?

There are a few things to understand here. First, Google crawls pages at unpredictable times, so your “default” content—whatever’s visible most of the time—is what typically gets indexed. Second, because scheduled content lives on the same URL (not on separate pages), you’re consolidating page authority rather than splitting it across multiple URLs. Third, your page’s metadata, headings, and primary content structure should reflect the page’s evergreen purpose. The scheduled blocks are supplementary—they enhance the experience without replacing the core content.

That said, you should think about what happens when no schedule matches. A good practice is to always define a fallback or default time slot so the page never renders with a blank section.

Getting Started

If you’re already building pages in the Gutenberg editor, adding time-based scheduling is a small step. Advanced Content Scheduler integrates directly into the editor—no new interfaces to learn, no shortcodes to memorize.

Start with one schedule. Pick a piece of content on your site that you’re currently updating manually on a regular basis. Set up a schedule container, define your time slots, and let it run. Once you see how much time it saves, you’ll start noticing scheduling opportunities everywhere.

Your content should work as hard as your business does. Block-level scheduling makes that possible without adding complexity to your workflow.