Choosing a Coming Soon Page Plugin

Decide first whether you are launching or pausing, because the correct HTTP status is different and no amount of design fixes the wrong one. A coming soon page is a page that exists and should be found. A maintenance page is a temporary outage that should tell crawlers to return later.

Plugins in this category almost always offer both modes behind one switch, and people pick whichever button looks closer. That is where the damage happens.

The three kinds of tool here

The third category is worth knowing about because it is often what people actually want. If the site must not be visible to anyone, a landing page with a design is the wrong tool — you want the whole site behind authentication, and you want it to stay that way.

For the pausing case specifically, putting a WordPress site into maintenance mode covers the mechanics and the status code in more detail.

What to evaluate

• Status code control. Can you choose between 200 and 503, and does the plugin set Retry-After on 503? If the plugin does not say, assume it does not.
• Bypass method. A secret URL, a role check, or an IP allowlist. All three are fine; a shared admin password is not.
• What is excluded. The login page must stay reachable. So must the REST API if anything else depends on it, and any webhook endpoints for payments or forms.
• Editing experience. Whether the page is built with the block editor, the plugin's own builder or a page builder. A plugin with a locked-in builder means the page cannot be reused after launch.
• Email capture. Where the addresses go. A plugin that stores them only in its own database table becomes a data-export problem on launch day.
• Assets loaded. Some launch plugins pull in an entire framework for a single page. The landing page is often the first impression of the site's speed.
• Clean removal. What is left behind after deactivation — see deleting a WordPress plugin completely.

The traps

Serving 503 for months. Search engines tolerate a 503 for a while, then start removing URLs. If the site will be unavailable for more than a day or two, it is a coming soon page, not maintenance.

A page with no text. A logo, a countdown and an email box give search engines nothing. Write two or three real paragraphs saying what the site will be and who it serves — it is the only content the domain has, and it starts the association early. The wider picture is in the WordPress SEO checklist.

Forgetting the cache. A caching layer can serve the coming soon page to visitors after launch, or serve the real site to visitors before it. Purge on both transitions, per clearing the WordPress cache.

Leaving it on for logged-out administrators. You will eventually check the site in a private window, panic, and re-enable something. Know your bypass URL before you need it.

Test it in this order

1. Load the site in a private browser window and confirm you see the placeholder.
2. Check the status code returned — how to check HTTP headers shows how, and this is the step nearly everyone skips.
3. Confirm /wp-login.php still loads.
4. Submit the email capture form and confirm the address arrives somewhere you can retrieve it.
5. Open the bypass URL in a second browser and confirm you see the real site.
6. Check the page on a phone.
7. Turn the mode off, purge caches, and confirm the real site returns for logged-out visitors.

Deciding

If the domain is new and the site is weeks away, use a coming soon page with a 200 status, real copy and an email form, and treat it as the first page of the site rather than a placeholder. If the site is live and you are working on it for an afternoon, use maintenance mode with a 503 and turn it off the same day. If nobody outside the project should see anything, skip both and put the whole site behind a login. Choosing the wrong one is far more expensive than choosing the wrong plugin within the right one.