Why Does My WordPress Site Say Coming Soon? (Answered)

Your dashboard loads fine. Your posts are published. And yet visitors get a holding page.

If you are asking why does my WordPress site say coming soon, the short answer is that a single setting is intercepting requests before your theme loads. Nothing is broken.

Six sources produce that screen: a coming soon plugin, a host-level toggle, the core .maintenance file, a theme or page builder setting, a stale cache, or DNS pointing somewhere unexpected.

This guide covers how to identify which one applies in under five minutes, using the HTTP status code as your first check.

You will also learn what the holding page does to your Google indexing, and how to stop it coming back after launch.

What Is the WordPress Coming Soon Page

The WordPress coming soon page is a front-end template that replaces your theme output for logged-out visitors. WordPress core, the database, and the admin dashboard keep running. Nothing is broken. One setting intercepts the request before your theme loads and serves a holding page instead.

You can still log in. You can still publish. Only the public view is swapped.

W3Techs puts WordPress at 41.5% of all websites as of mid-2026, down from a 43.6% peak in early 2025. At that scale, a launch setting left switched on is one of the most common reasons a site looks dead when it is not.

Coming Soon Mode vs Maintenance Mode

Coming soon mode targets sites that have never launched. Elementor’s own source code states that coming soon returns HTTP 200, meaning the page is ready to be indexed.

Maintenance mode targets sites already live in search. It returns a 503 response code, which tells crawlers to come back later.

Elementor’s code comment goes further and warns against running the 503 mode for more than a couple of days.

Coming Soon Mode vs a Genuinely Broken Site

A broken install locks you out of /wp-admin/ as well. Coming soon mode never does.

Three signals separate the two:

• The dashboard loads at full speed
• The holding page is styled, branded, and clearly intentional
• Logged-in administrators see the real site

Automattic ships the same behaviour on WordPress.com through Settings, Privacy, Coming Soon, where logged-in contributors see the full site and everyone else gets a placeholder. Deliberately taking a WordPress site offline works the same way on self-hosted installs.

Why Does My WordPress Site Say Coming Soon

Six sources produce the message: a coming soon plugin, a host-level toggle, the core .maintenance file, a theme or page builder setting, a cached copy of an old holding page, and DNS pointing at a parked or staging install. Plugins and host toggles account for most cases on new installs.

Fresh install: suspect the host toggle first, then a bundled plugin.

Previously live site: suspect DNS, a staging push, or a cache layer before you touch any plugin setting.

How Do I Identify Which Source Is Causing the Coming Soon Page

Read the HTTP status code first. A 200 points to a plugin, host toggle, or theme setting. A 503 points to maintenance mode or the core .maintenance file. That single check cuts the candidate list in half before you change anything.

Run these five checks in order:

• Incognito window. If the holding page only appears when logged out, the block is role-based, not server-based.
• Status code. Use the DevTools Network tab, curl -I https://yoursite.com, or httpstatus.io.
• View source. Search the HTML for seedprod, elementor-maintenance-mode, wpmm, or a host-specific class.
• Test /wp-admin/ and a random 404 URL. If both are blocked, you are looking at a server-level or core-level lock.
• Read the wording. “A new WordPress site coming soon” is Bluehost. “Briefly unavailable for scheduled maintenance” is WordPress core.

If the status code says 503 and nothing in the dashboard explains it, pull your server error log before editing files. Failed updates almost always leave a trace there.

One thing that trips people up: an admin bar indicator. Newfold Labs, the group behind Bluehost and HostGator, ships a module that displays a LIVE or NOT LIVE badge in the WordPress toolbar plus a banner telling logged-in users that visitors see something different.

Which WordPress Plugins Turn On Coming Soon Mode

SeedProd, LightStart (formerly WP Maintenance Mode by Designmodo), Elementor, and CMP hold roughly 2.2 million active installations between them. Each stores its own on/off flag. Deactivating the plugin removes the holding page, but the stored setting survives until the plugin is deleted.

Install counts come from the WordPress.org plugin directory and Cloudways’ 2024 roundup. SeedProd carries a 4.9 rating across 4,699 reviews.

Turning Off SeedProd Coming Soon Mode

SeedProd began life purely as a coming soon plugin before it became a full landing page builder. The original toggle never left.

Go to SeedProd, Landing Pages, then set Coming Soon Mode to Inactive.

Settings persist in wpoptions under the seedcspv5 prefix, so reactivating the plugin months later restores the exact same holding page.

Turning Off Elementor Maintenance Mode

Path: Elementor, Tools, Maintenance Mode, then set Choose Mode to Disabled.

Database flag: elementormaintenancemodemode in wpoptions.

Known conflict: WP Rocket users reported for years that Elementor’s mode change did not apply until the page cache was cleared manually. WP Rocket eventually hooked into Elementor’s mode-changed action to fix it.

The same principle covers every plugin here. Switching maintenance mode off and purging cache are two separate jobs.

Why Does My Host Show a Coming Soon Page

Managed hosts add their own coming soon toggle outside the plugins screen. Deactivating every plugin on the site will not remove it. New installs created through a host onboarding wizard default to coming soon until you confirm launch, which is why brand new sites show a holding page nobody remembers enabling.

Bluehost: Websites, your site, Settings, then scroll to the Coming Soon section. A second control sits in WordPress under Settings, General, labelled “Enable Bluehost coming soon page.”

WP Engine: password protection under Utilities, plus a separate holding page on new environments.

GoDaddy Managed WordPress: a Coming Soon control inside the site dashboard, applied automatically when you install WordPress through GoDaddy.

SiteGround, Kinsta, Hostinger, Cloudways: equivalent controls in the site tools panel rather than in WordPress.

Newfold Labs open-sourced the module that powers this behaviour across its hosting brands. It exposes a launch and unlaunch toggle, and it wires an admin notice into every WP Admin screen pointing at that toggle. Worth knowing if you would rather keep a WordPress site private using WordPress-native settings instead of a host layer you cannot see from the dashboard.

Why Does the Site Say Briefly Unavailable for Scheduled Maintenance

WordPress core writes a .maintenance file to the site root at the start of every core, plugin, and theme update, then deletes it on completion. An interrupted update leaves the file behind. The site returns 503 and serves “Briefly unavailable for scheduled maintenance. Check back in a minute.” until the file is removed.

This message is not a plugin. It is not a hack. It is a stuck flag.

Four things trigger it, according to Jetpack and WPBeginner:

• Closing the browser tab mid-update
• Bulk-updating a large batch of plugins at once
• A PHP execution timeout on an underpowered server
• Memory exhaustion during file extraction

WPBeginner reports that deleting .maintenance from the root directory resolves the problem in 95% of cases.

Connect over FTP or SFTP, or open your host File Manager, and enable hidden files. FileZilla hides dotfiles by default under Server, Force Showing Hidden Files. The root folder is usually publichtml.

DreamHost points out something most guides skip. WordPress ignores the lock after roughly 10 minutes on its own, so a message that survives past that window means a cached page, a repeated failed update, or a maintenance plugin is holding it up. Sites stuck in maintenance mode for hours are almost never a pure core problem.

Re-run the interrupted update afterwards. A half-copied plugin folder causes its own plugin update errors that look nothing like the original scheduled maintenance message.

Why Does My Theme or Page Builder Show a Coming Soon Screen

Premium themes ship maintenance features in their Pro addon layer, not in the theme itself. Kadence Theme Pro, Astra Pro, and OceanWP Extra all include one. No dedicated plugin appears on the plugins screen, which is exactly why this source gets missed.

Kadence documents the clearest implementation. Enable Maintenance Mode under Appearance, Kadence, Pro Addons, then configure it at Kadence, Maintenance Mode.

Kadence splits the behaviour the same way Elementor does:

• Maintenance Mode: 503 Service Unavailable
• Coming Soon Mode: 200 OK

Divi is the exception people expect to work and it does not. Elegant Themes never shipped a native toggle, so Divi sites rely on third-party plugins like Divi Coming Soon by Divi Life, DiviFlash, or Divi Pixel Maintenance Mode. If your Divi site shows a holding page, look at installed extensions rather than the theme options panel.

Switching themes does not always clear the flag. The value sits in a wpoptions row tied to the addon, not the theme, so a direct check in phpMyAdmin or Adminer settles it faster than clicking through settings screens.

Why Does the Coming Soon Page Still Show After I Turned It Off

A cache layer is serving the old HTML. The setting changed in the database, but the page a visitor receives was generated before you touched it. Purging in the wrong order wastes time, because a CDN will refill from a stale origin copy seconds later.

Hostaccent’s support team ranks the culprits by frequency: browser cache around 45%, caching plugin around 25%, and CDN cache around 15%.

Test in incognito first. If the holding page still appears there, the stale copy lives on a server, not on your machine.

Correct order: plugin cache, then server cache (Varnish on Cloudways, NGINX FastCGI on Kinsta, SG Optimizer on SiteGround), then CDN, then browser.

Cloudflare estimates that a Purge Everything clears all global nodes within 30 seconds to 5 minutes.

LiteSpeed Cache alone sits above 7 million active installations on WordPress.org, and SQ Magazine’s 2025 data put caching plugin adoption at 82.4% of WordPress sites. Odds are strong that a cache is involved in your situation whether you configured one or not.

WP Rocket users filed a public issue in 2022 reporting that Elementor’s maintenance mode did not apply until the page cache was cleared by hand. WP Rocket later hooked into Elementor’s mode-changed action to purge automatically.

Two layers people forget:

• Object cache. Redis or Memcached can hold the option value itself. Flush it separately.
• Must-use plugins. Some hosts drop their own caching drop-in into wp-content/mu-plugins, invisible on the normal plugins list.

Why Does the Coming Soon Page Appear on a Site That Was Already Live

Previously live sites fail differently from new installs. DNS pointing at a parked domain, an old host, or a staging environment produces a holding page that has nothing to do with your current WordPress settings. Check where the domain actually resolves before you open the plugins screen.

Four causes account for almost all of these cases:

• Nameservers or A records still pointing at the previous host after a migration
• A staging copy pushed to production with coming soon still switched on
• A plugin auto-update restoring a stored flag
• Domain expiry, where the registrar serves its own parking page

Namecheap, HostGator, and Network Solutions all quote the same window for nameserver changes: up to 48 hours, occasionally 72.

That figure is a ceiling, not an average. Most record changes reach the majority of resolvers within 1 to 4 hours, and lowering TTL to 300 seconds a day or two ahead of a migration shortens the tail considerably.

Migration symptom: you see the new site, a colleague in another city sees the old one. Different resolvers, different cache expiry times.

Staging symptom: everyone sees the same holding page, and the content matches a build you did weeks ago.

Run the domain through a global DNS lookup tool before changing anything. If the records are wrong, pointing the domain at the right WordPress host fixes the problem and no plugin setting needs touching.

What Does the Coming Soon Page Do to Google Rankings

Google drops URLs from the index after roughly 2 days of sustained 503 or 429 responses, per Search Central’s crawling documentation. A coming soon page returning 200 carries a different risk: Google indexes the holding page itself as your site content.

Google’s 2011 planned-downtime post is blunt about the 200 case. Placeholder pages returning OK get indexed as the site’s real content, and identical error pages across every URL can be read as duplicates.

Googlebot retries a 503 for about a week before treating it as permanent, according to Google’s 2017 guidance. Gary Illyes later clarified that 10 to 15 minutes of downtime now and then is not “extended” and will not hurt you.

Elementor bakes the same warning into its own source code, telling users not to run the 503 service unavailable response for more than a couple of days.

Most coming soon plugins also inject a noindex robots meta tag while active, which strips indexed URLs on the next recrawl rather than on a schedule you control.

Recovery runs through Search Console:

• Inspect the URL, then hit Test Live URL to confirm the noindex is gone
• Request indexing only after the live test comes back clean
• Expect a daily cap of roughly 10 to 15 URL requests
• Check the Pages report after 3 to 5 days, filtering for Server error (5xx)

Removing noindex only takes effect once Googlebot recrawls. Track the last crawl date rather than refreshing search results and guessing.

How Do I Prevent the Coming Soon Page From Coming Back

Delete the coming soon plugin instead of deactivating it once launch is done. Switch the host-level toggle off in the hosting dashboard, not just inside WordPress. Give staging its own HTTP authentication so production and staging never share a setting that can travel between them.

Delete, do not deactivate. A deactivated plugin keeps its wpoptions row. Reactivating it months later restores the exact holding page.

Fix the update timeout. Most hosts default maxexecutiontime to 30 seconds, and Kinsta notes that 300 seconds is a sensible ceiling. Large plugins like WooCommerce and Elementor routinely exceed 30 seconds during extraction on slow disks.

Update one plugin at a time. Bulk updates are the single most reported trigger for a stuck maintenance mode error.

Check the PHP layer. A recurring script timeout leaves a new .maintenance file behind every time an update fails, so raising the limit treats the cause rather than the symptom.

Monitoring is where most people stop too early. A standard uptime check confirms a 200 response, which a coming soon page happily returns.

UptimeRobot’s keyword monitor solves that by scanning the response body. Set a “Keyword Not Exists” alert on a phrase that only appears on your real homepage, and you get notified the moment the holding page replaces it.

Two habits worth building:

• Password-protect staging at the server level, then share individual draft pages with clients instead of locking the whole install
• Keep a launch checklist that names the exact toggle for each host you use, which matters more once you run several WordPress sites across different providers

Newfold Labs built this idea into its hosting brands with a LIVE and NOT LIVE badge in the admin bar. Borrow the principle even if your host does not ship it: something visible should tell you the public view differs from yours.

FAQ on Why Does My WordPress Site Say Coming Soon

Why does my WordPress site say coming soon but the admin dashboard works?

Coming soon mode only blocks logged-out visitors. WordPress core, the database, and wp-admin keep running normally. A plugin, host toggle, or theme setting intercepts the request and serves a holding page instead of your theme output.

How do I turn off the coming soon page in WordPress?

Find the source first, then switch it off at that source. SeedProd sits under Landing Pages. Elementor sits under Tools, Maintenance Mode. Host toggles live in the hosting dashboard, not the plugins screen.

Why does my site still say coming soon after deactivating every plugin?

Two likely reasons. A host-level toggle operates outside WordPress entirely, so plugin changes never touch it. Or a page cache is still serving the old HTML from before you made the change.

What does “Briefly unavailable for scheduled maintenance” mean?

WordPress core writes a .maintenance file to the site root during updates and deletes it on completion. An interrupted update leaves the file behind, and the site returns 503 until someone removes it manually.

Is it safe to delete the .maintenance file?

Yes. It is a temporary flag, not a content or configuration file. Delete it over FTP, SFTP, or your host File Manager with hidden files enabled, then re-run the update that failed.

Why do I see the real site but visitors see coming soon?

Every coming soon plugin bypasses the block for logged-in administrators by design. Open an incognito window to see what the public actually gets. That single check confirms the block is role-based rather than server-based.

Does a coming soon page hurt SEO?

It can. Most coming soon plugins add a noindex tag, and a holding page returning 200 gets indexed as your site content. Google drops URLs after roughly two days of sustained 503 responses.

How long can I leave maintenance mode switched on?

Keep it under 48 hours. Googlebot retries a 503 for about a week before treating it as permanent, and Elementor’s own code warns against running the mode for more than a couple of days.

Is a coming soon page the same as a broken WordPress site?

No. A broken install blocks /wp-admin/ too and usually returns 500 or nothing at all. Compare it against the blank screen failure, where no styled holding page appears anywhere.

Why did the coming soon page come back after a plugin update?

Deactivating a plugin leaves its setting stored in wpoptions. An auto-update that reactivates the plugin restores the flag. Delete the plugin after launch instead of leaving it dormant.

Conclusion

Anyone asking why does my WordPress site say coming soon is usually two clicks from a fix, not a rebuild.

Read the status code first, then work backwards. A 200 points you toward SeedProd, a Bluehost toggle, or a Kadence Pro addon. A 503 points you toward the .maintenance` file.

Purge in order after every change: plugin cache, server cache, CDN, browser. Skipping that step is why the holding page appears to survive a fix that actually worked.

Then open Search Console. A leftover noindex tag, or a 503 served without a Retry-After header, costs more than the downtime ever did.

Delete the plugin once you launch. Keep staging behind HTTP authentication, and the screen stops coming back.