This guide shows how to add a WordPress countdown timer in about a minute, with no plugin: you paste one snippet into the post or page itself, because a countdown works above the fold on the page that's actually selling the thing. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.
The countdown timer counts down to a date you choose: a product launch, the end of a sale, an event or a deadline. There are presets for common dates like Black Friday, Christmas and New Year, or you can set any custom date, and it comes in pill or card layouts with several themes.
On WordPress, the right spot is the post or page itself. A countdown works best above the fold, on the page that's actually selling the thing it counts down to, close to the button people need to press. Use one countdown per page; several timers competing for attention cancel each other out.
WordPress.org sites you host yourself can use every method on this page. On WordPress.com, adding scripts with a Custom HTML block or a header plugin needs a plan that allows plugins and custom code (the Business plan or above at the time of writing), because lower WordPress.com plans strip script tags. If you're not sure which you have, check whether your dashboard has a Plugins menu.
WP Rocket, W3 Total Cache, LiteSpeed Cache and your host's edge cache all serve a stored copy of your HTML. Until you purge, you'll be looking at the version from before you pasted and assuming the widget is broken. The widget's own data is fetched client-side on every load, so page caching never makes the numbers go stale — it only hides a freshly-added snippet.
Optimisation plugins that concatenate or defer every script can break an async third-party tag by moving it out of order. If the widget renders nothing after a purge, add the script URL to your plugin's JS exclusion list — in WP Rocket that's File Optimization → Excluded JavaScript Files. Nothing else needs changing.
WordPress sanitises script tags typed into a paragraph or the Visual editor tab, silently. The Custom HTML block, the Classic editor's Text tab, and Elementor's HTML widget all pass markup through untouched. If your snippet vanished on save, that's why.
Only count down to real deadlines. A timer that resets on every visit or an offer that never really ends is easy to spot, damages trust and, in many countries, can breach consumer-protection rules.
No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs. Installing a plugin for this would mean another dependency and update cycle just to show one widget.
The post or page itself, because a countdown works above the fold on the page that's actually selling the thing.
It adds one small script, loaded asynchronously, so it doesn't block your page from rendering. Any third-party script has some cost, so check your page speed before and after adding it. Your caching and optimisation plugins keep working exactly as before — the only thing to remember is to purge the cache after you paste, otherwise you'll be looking at the stored copy of your old HTML.
Elementor: drag in the HTML widget and paste there. Divi: use a Code module. Beaver Builder: use the HTML module. WPBakery: use the Raw HTML element. Any builder with a raw-HTML or code block will render it.
No. It counts down to the fixed date you set, the same for everyone. We think that's the honest way to use a countdown.