---
title: "Nexter Blocks Countdown, Progress Bar and Infobox: Building a High-Converting Landing Page Section"
url: https://nexterwp.com/blog/nexter-blocks-countdown-progress-infobox/
date: 2026-09-06
modified: 2026-09-07
lang: en
author: "Aditya Sharma"
description: "A launch or sale landing page usually needs the same three things: urgency, a way to signal progress, and a clean way to break down features or steps. Nexter Blocks..."
image: https://nexterwp.com/wp-content/uploads/2024/12/Nexter-Blocks-Countdown-Activation-1024x358.png
word_count: 1974
---

# Nexter Blocks Countdown, Progress Bar and Infobox: Building a High-Converting Landing Page Section

## Key Takeaways

- Nexter Blocks Countdown supports a real fixed end date/time and an evergreen per-visitor countdown, with end actions that can show a custom message, redirect to another URL, or hide the section.
- FTC guidance names fake countdown timers and false urgency claims as deceptive practices, including timers that reset on page reload and offers that stay live after the countdown hits zero.
- Progress Bar fits a funding goal, limited-stock indicator, or multi-step signup flow, but its number needs to reflect a real stock count, funding total, or completion state.
- Infobox pairs an icon or image with a short title and description in a repeatable card format, and it can work with Nexter’s Repeater block to pull from a custom-fields data source.
- A ticking countdown can create screen reader problems if it uses aria-live to announce every second; the safer pattern is no live announcement or a much less frequent one, such as once a minute.

A launch or sale landing page usually needs the same three things: urgency, a way to signal progress, and a clean way to break down features or steps. Nexter Blocks covers all three natively — Countdown, Progress Bar, and Infobox — so a full landing-page section is a layout exercise, not a plugin-shopping trip. The bigger risk with this trio isn't the layout, though — it's using a fake countdown or an invented progress number, which regulators have specifically named as a deceptive pattern, not just a design faux pas.

Table of Contents

## Countdown: Real Urgency, Configurable Endings

Nexter’s Countdown block supports a real fixed end date/time as well as an “evergreen” per-visitor countdown. Beyond the timer itself, it includes configurable behavior for what happens when it hits zero: show a custom message, redirect to another URL, or hide the section entirely — useful for a sale that should genuinely disappear once it ends, rather than a countdown that just sits at 00:00:00 looking broken.

![Activating the Countdown block in Nexter Blocks](https://nexterwp.com/wp-content/uploads/2024/12/Nexter-Blocks-Countdown-Activation.png)Enabling the Countdown block. Source: Nexter Blocks documentation.

## The Legal Line: Real Deadlines vs. Fake Urgency

This is worth taking seriously, not treating as a design nitpick. The FTC's own "Bringing Dark Patterns to Light" report explicitly names false urgency claims and fake countdown timers as deceptive practices that can trigger enforcement action, and its more recent guidance specifically calls out timers that reset on page reload and offers that stay live after the countdown hits zero. The evergreen per-visitor countdown option Nexter's block supports is exactly the pattern regulators flag when it's used to imply a real, shared deadline that in fact resets for every new visitor — the technical capability isn't the problem, using it to misrepresent urgency is. The safer, and more defensible, uses of Countdown are a real fixed-end-date sale that actually ends when the timer says it will, or an honestly-labeled evergreen offer (a "limited to your first visit" framing that doesn't imply a shared, ticking clock everyone else is also watching).

## Progress Bar: Signaling Momentum

The Progress Bar block works for anything with a visible completion state — a funding goal, a limited-stock indicator, a multi-step signup flow. Style it to match your Global Styles brand colors, and it doubles as a subtle trust signal alongside a Countdown: “73% funded, 4 days left” reads very differently from either element alone.

## The Same Rule Applies to Progress Bars and Stock Counters

The FTC's dark-patterns guidance flags fake low-stock messaging alongside fake countdowns — the specific example cited is an "Only 2 left in stock" claim shown when supply is actually plentiful, and identical scarcity numbers displayed across unrelated products regardless of their real inventory. A Progress Bar used as a stock counter or funding tracker inherits the same obligation a Countdown does: the number needs to reflect something real. If a specific SKU's stock count, a campaign's actual funding total, or a genuine multi-step completion state exists to display, the Progress Bar block is the right tool for it. If no real number exists yet, the honest move is leaving the block out rather than inventing a plausible-looking percentage.

## Infobox: Breaking Down Features Without a Wall of Text

Infobox pairs an icon (or image) with a short title and description, in a repeatable card format — the standard shape for a “why choose us” or feature-comparison section. Combined with Nexter’s Repeater block, an Infobox grid can pull from a custom-fields data source instead of being hand-built card by card.

***Also Read:** [Nexter Blocks Repeater: How to Build Dynamic Layouts with ACF and JetEngine](https://nexterwp.com/blog/nexter-blocks-repeater-block/) — for building a large Infobox grid from a data source instead of by hand.*

## Countdown Timers and Screen Readers

A ticking countdown is a moving-content accessibility consideration worth a quick check, not just a visual element. A timer that updates every second and is wrapped in an `aria-live` region set to announce every change can flood a screen reader user with a new announcement every single second, making the rest of the page unusable while the timer is present. The more considerate pattern is either no `aria-live` announcement at all (the visible timer still works fine for sighted users, and a screen reader user can navigate to it deliberately if they want the current value) or a much less frequent, deliberately-throttled announcement (once a minute, for instance, rather than every second). It's worth checking which behavior a given countdown implementation actually uses rather than assuming the constant visual update is harmless just because it looks fine.

## Writing Infobox Copy That Doesn't Read as Filler

A three- or four-card Infobox row is easy to fill with generic, interchangeable copy ("Fast," "Reliable," "Easy to use") that could describe almost any product and therefore convinces nobody. The stronger version of an Infobox row names a specific, concrete detail per card instead of an adjective — a real number, a specific capability, or a named comparison point — so each card is doing actual persuasive work rather than filling visual space. Before publishing a row, it's worth checking whether swapping the product name out of each card's copy would still leave it reading as true; if the answer is yes, the copy is too generic to be useful.

## A Worked Example: A Real Product Launch Section

Picture a plugin launch with a genuine 72-hour early-bird discount window. The Countdown block gets a real fixed end date set to exactly when the discount reverts to full price — not an evergreen per-visitor timer, since the discount really is shared and time-bound across every visitor. Its end action is set to swap the price display back to full price and update the headline copy, rather than hiding the section or redirecting, since the product is still purchasable after the window closes, just at a different price.

Below that, an Infobox row covers three concrete capabilities of the plugin (not generic adjectives) — each card naming a specific feature and what it actually does, so a skimming visitor gets real information even without reading the full page copy. No Progress Bar appears in this particular section, because there's no genuine funding goal or stock count to report — a plugin launch doesn't have a natural "percent complete" metric, and manufacturing one to fill the layout would be exactly the kind of fabricated urgency worth avoiding. The section closes with a single CTA button styled from the site's Global Styles palette, linking straight to checkout with the discount already applied.

## Troubleshooting: When These Blocks Look Broken

- **Countdown shows 00:00:00 instead of hiding or redirecting:** the end-action setting is likely still on its default (often "show 00:00:00") rather than switched to redirect, custom message, or hide-section — revisit that specific setting rather than assuming the block is broken.
- **Progress Bar shows the wrong percentage after a manual update:** confirm whether the value is hardcoded or pulled from a live data source (like a custom field) — a hardcoded percentage has to be manually revisited every time the real number changes, which is an easy step to forget.
- **Infobox cards look uneven in height across a row:** uneven copy length per card is the usual cause; either trim the longer descriptions to match, or check whether the block's layout settings have an equal-height option enabled.
- **The whole section feels cluttered even with only three blocks:** this is often a spacing problem rather than a content problem — check that consistent spacing (ideally following a baseline grid) separates each block, rather than each one carrying its own inconsistent margin.

## Putting the Section Together

- Countdown at the top of the section — the first thing a visitor should register is the deadline.
- A short headline and one line of supporting copy.
- An Infobox row (3–4 items) covering the core value props or what’s included, with specific concrete details rather than generic adjectives per card.
- A Progress Bar if there’s a genuine scarcity or momentum metric to show — skip it if there isn’t one; a fake progress bar is easy for visitors to spot and erodes trust faster than having none at all.
- A single, clear call-to-action button styled from your Global Styles brand colors.

***Also Read:** [Nexter Theme Global Styles: How to Set Up Brand Colors, Fonts and Spacing Sitewide](https://nexterwp.com/blog/nexter-theme-global-styles/) — set this up first so every block in the section matches your brand automatically.*

## A Compliance Checklist Before You Ship the Section

- **Does the Countdown's end date match reality?** If the offer stays live after the timer hits zero, that's the specific pattern the FTC has named as deceptive.
- **Does the timer reset per visitor, and if so, is that disclosed?** An evergreen countdown isn't inherently dishonest, but implying it's a shared, one-time deadline when it resets for every new visitor is the failure mode to avoid.
- **Is the Progress Bar's number real?** A genuine funding total, real stock count, or actual step-completion state is fine; an invented plausible-looking percentage is not.
- **Would this section survive a screenshot next to a "how many people have actually bought this" fact-check?** If not, the urgency messaging is doing more harm to trust than good.
- **If a countdown announces itself to screen readers, is the announcement frequency reasonable?** A once-a-second live-region update on a countdown is a real usability problem for screen reader visitors, separate from the legal-risk questions above.

## FAQ

### Can the Countdown block redirect visitors once it hits zero?

Yes, the block supports a configurable end action including a redirect, a custom message, or hiding the section.

### Are these blocks available in Nexter Blocks free?

Countdown, Progress Bar, and Infobox are all available in the free version of Nexter Blocks; some advanced styling and end-behavior options may require Pro depending on your current version.

### Should I always include a progress bar on a landing page?

Only if you have a real metric to show. A fabricated or vague progress indicator tends to undermine trust rather than build it.

### Is it actually illegal to use a fake countdown timer?

The FTC has named fake countdown timers and false urgency claims as deceptive practices in its dark-patterns guidance, and several state consumer-protection laws separately cover false representations of limited-time offers. Federal enforcement specifically against timers has been relatively rare, but the regulatory risk is real and growing, not merely a UX best practice.

### Is an evergreen, per-visitor countdown automatically a dark pattern?

Not automatically — it depends on how it's framed. An evergreen countdown honestly presented as a per-visitor, first-time offer is different from one designed to imply a shared, ticking deadline that resets on every reload, which is the specific pattern regulators have flagged.

### Can a countdown timer cause accessibility problems?

It can, if it's wrapped in an `aria-live` region that announces every second-by-second update to screen reader users, which floods and effectively blocks the rest of the page. A well-implemented countdown either skips live announcements entirely or throttles them to something much less frequent.

## Conclusion

None of these three blocks needs a separate plugin, and none of them needs to appear together — use only the ones your specific page actually calls for. A landing page with a fake progress bar and no real deadline undermines its own urgency messaging; use these blocks to tell the truth faster, not to manufacture urgency that isn’t there. Treat the Countdown's end date and the Progress Bar's number as claims that need to be true, not just visually convincing, since regulators now explicitly name the fake versions of both as deceptive practices.

## Suggested Reading

- [Nexter Blocks Repeater: How to Build Dynamic Layouts with ACF and JetEngine](https://nexterwp.com/blog/nexter-blocks-repeater-block/)
- [Nexter Theme Global Styles: How to Set Up Brand Colors, Fonts and Spacing Sitewide](https://nexterwp.com/blog/nexter-theme-global-styles/)
- [Nexter Blocks AI Features: What the New AI-in-Every-Block Update Actually Does](https://nexterwp.com/blog/ai-in-nexter-blocks-features/)

#### Stay updated with Helpful WordPress Tips, Insider Insights, and Exclusive Updates – Subscribe now to keep up with Everything Happening on WordPress!

Subscribe

## Frequently Asked Questions

**Q: Can a countdown timer redirect visitors when it reaches zero?**
A: Nexter Blocks supports a configurable end action, so the Countdown block can redirect visitors, show a custom message, or hide the section when time runs out. That matters because a dead timer at 00:00:00 looks broken and weakens the offer. For a real launch or sale, the redirect option keeps the page behavior aligned with the deadline instead of leaving stale urgency on screen.

**Q: Are Countdown, Progress Bar, and Infobox included in the free version of Nexter Blocks?**
A: Countdown, Progress Bar, and Infobox are all available in the free version of Nexter Blocks. The page also notes that some advanced styling and end-behavior options may require Pro depending on your current version. That split is useful if you want to build the section first and only upgrade later for extra control over design or countdown behavior.

**Q: Should I use a progress bar on every landing page?**
A: A progress bar only makes sense when there is a real metric to show, like funding progress, limited stock, or a multi-step signup flow. The page is blunt about this: a fake or vague progress indicator erodes trust faster than having none at all. If you do use one, it works best as a supporting signal next to a Countdown, not as decoration.

**Q: What’s the best way to combine Countdown, Infobox, and Progress Bar in one landing page section?**
A: The strongest layout puts the Countdown first so visitors register the deadline immediately, then uses a short headline and one line of supporting copy. After that, an Infobox row with 3 to 4 items can break down value props without turning into a wall of text. Add a Progress Bar only when there is a genuine scarcity or momentum metric, then finish with one clear CTA button styled from Global Styles.

**Q: Can I build an Infobox grid from custom fields instead of hand-creating every card?**
A: Nexter Blocks supports that workflow through its Repeater block. The page says an Infobox grid can pull from a custom-fields data source instead of being built card by card, which is useful when you need a larger feature section that stays consistent. For that setup, the linked [Nexter Blocks Repeater: How to Build Dynamic Layouts with ACF and JetEngine](https://nexterwp.com/blog/nexter-blocks-repeater-block/) article is the relevant follow-up.

**Q: How do I keep these landing page blocks visually consistent with my brand?**
A: Global Styles is the key piece here because the Progress Bar can be styled to match your brand colors, and the CTA button should also come from those same sitewide settings. The page specifically points to [Nexter Theme Global Styles: How to Set Up Brand Colors, Fonts and Spacing Sitewide](https://nexterwp.com/blog/nexter-theme-global-styles/) as the setup step before building the section. That keeps the Countdown, Infobox cards, and button from feeling like separate widgets.
