Content Expiry

Wrap content in [content_expiry], set a date, and it is removed from the page once that moment passes. Nothing is left behind: no empty wrapper and no hidden markup. Each example below shows the shortcode used, then what a visitor sees.

[content_expiry date="2030-12-31"]Winter booking offer: 10% off visits before the end of 2030.[/content_expiry]

A date on its own keeps the content up for the whole of that day, then removes it at midnight.

[content_expiry date="2024-01-01" fallback="This offer has ended."]Early-bird price[/content_expiry]

This date has passed, so the content is replaced by the fallback text.

[content_expiry date="2030-12-31" time="18:00" timezone="Europe/London"]Book by 6pm for same-day confirmation.[/content_expiry]

Goes offline at 6pm UK time. Use timezone if the site timezone is set to a plain UTC offset.

[content_expiry start="2030-01-01" date="2030-12-31"]Our 2030 price list[/content_expiry]

Nothing shows before the start date. This one opens on 1 January 2030, so right now the box above is empty on purpose.

[content_expiry date="2024-01-01"]Old announcement[/content_expiry]

Expired and no fallback: it simply is not on the page. Check the page source if you like.

Logged-in editors can preview any moment by adding ?content_expiry_preview=2031-01-01 to this page address. The Bricks builder always shows the content so it can still be edited. Cached pages are purged at the exact moment content expires or goes live.