Add to Preferred Sources
WordPress maintenance mode vs coming soon are two distinct features that serve different business situations — and choosing the wrong one can cost you Google rankings, email subscribers, or both. For South African operators managing their own WordPress sites, the difference is concrete: maintenance mode sends a 503 "temporarily unavailable" signal to Googlebot that preserves your existing rankings during a brief downtime, while coming soon mode typically serves a 200 OK page that Google can index. Understanding which situation calls for which mode is the whole game, and it starts with your guide to website builders in South Africa.
If you are building a brand-new site that has never been live, you want coming soon mode. If you are taking an existing live site offline for updates, you want maintenance mode. Those two rules cover most cases — but the SEO implications, POPIA compliance considerations for email capture, and the risk of getting stuck (a real problem during any unplanned interruption) add enough nuance to make the choice worth understanding properly.
Quick Answer
Use maintenance mode (503 status) when an existing live site needs brief downtime for updates or repairs — Googlebot recognises the signal and holds your rankings for short windows. Use coming soon mode (200 status + noindex, or 503) for a pre-launch site that has never been indexed. The critical error is serving a coming soon page with a 200 OK status and no noindex directive: Google will index your placeholder as your real page content. For South African operators, POPIA Section 69 requires explicit consent before you can send marketing emails to addresses captured on a coming soon page — an unticked opt-in checkbox on the sign-up form is not optional.
Jump to a section
What WordPress maintenance mode actually does
What a WordPress coming soon page actually does
The SEO difference: why the HTTP status code matters
Decision table: which mode for your situation
How to enable each mode in WordPress
Not sure which setup fits your site's situation?
Share your current WordPress configuration and we'll show you exactly which mode to use — and flag any indexation risks before they cost you rankings.
Get a quick configuration reviewWhat WordPress Maintenance Mode Actually Does
WordPress maintenance mode is a temporary state that hides your live site from visitors while telling search engines the unavailability is planned and brief. When WordPress runs a core, plugin, or theme update, it automatically creates a hidden .maintenance file in your site's root directory. While that file exists, every visitor — except logged-in administrators — sees a plain "Briefly unavailable for scheduled maintenance. Check back in a minute." message. The key technical detail: the server returns an HTTP 503 "Service Unavailable" status code, typically paired with a Retry-After header that tells crawlers exactly when to return.
WordPress removes the .maintenance file automatically when the update completes. If the update finishes cleanly, visitors typically experience only a few seconds of the message — not enough to trigger any SEO consequence. The 503 + Retry-After combination is specifically designed for this scenario: it is the signal that distinguishes "down for maintenance" from "permanently gone."
What maintenance mode is for
Maintenance mode is for an existing, previously indexed site that needs to go briefly offline. It protects existing Google rankings by sending a 503 signal that tells Googlebot: this is temporary, retry later. It is not designed as a long-term screen, and using it for days rather than hours carries real deindexation risk.
What a WordPress Coming Soon Page Actually Does
A coming soon page is a placeholder screen for a site that has never been live — or is being rebuilt so substantially that the existing site is not being shown. The maintenance mode vs coming soon page distinction is sharpest here: a coming soon page is designed to stay visible for weeks or months while a site is in development, whereas maintenance mode is designed to disappear in minutes. Most WordPress plugins that offer a coming soon mode, including the widely-used SeedProd, serve the page with an HTTP 200 OK status code rather than 503. This means the page is accessible to Google and can be indexed — which is why the noindex configuration matters so much.
Coming soon pages also serve a practical pre-launch function that maintenance mode does not: they can include email capture forms, countdown timers, and social links that build an audience before launch. For a South African business opening a new branch, launching a new product, or moving to a new domain, a coming soon page is a legitimate marketing asset — provided the email form is POPIA-compliant (covered below).
What coming soon mode is for
Coming soon mode is for a pre-launch site that has never been indexed, or for a major rebuild where the old site is no longer being shown. It is visible for an extended period, so it needs careful configuration: the right status code or noindex directive prevents Google from treating your placeholder as your real content. It is never appropriate for a brief update to a live site — that is maintenance mode's job.
The SEO Difference: Why the HTTP Status Code Matters
The HTTP status code each mode returns is what determines the SEO outcome — and this is where most operators go wrong. When you examine the wordpress maintenance page vs coming soon question technically, the 503 vs 200 difference is the whole story. Google's Gary Illyes has noted that brief 503 windows — minutes to a few hours — do not trigger the crawl-rate reduction that extended outages cause. Separately, Google's own documentation confirms that already-indexed URLs are preserved in the index during brief 5xx periods. Extended 503s lasting several days or more do cause crawl rate reductions and eventually put pages at risk of dropping from the index, but for the minutes-to-hours window a typical WordPress update requires, the 503 is safe.
The 200 OK status of a coming soon page is the opposite signal: it tells Google that this is working content, ready to index. If a coming soon page carries no noindex robots directive, Google will index the placeholder. For a new site that has never had indexed pages, this may be harmless — the placeholder just sits in the index briefly until you launch and it gets replaced. But for an existing site that switches to a coming soon screen without 503 or noindex, Google may replace its existing indexed pages with the placeholder, effectively wiping your search presence. That is the scenario worth actively avoiding.
The three HTTP scenarios and what they mean for Google
- 503 + Retry-After → Googlebot holds existing rankings, retries at the suggested time. Safe for brief maintenance windows.
- 200 OK + noindex robots meta → Googlebot sees the page but does not index it. Safe for coming soon pages on pre-launch sites. Risk: forgetting to remove noindex at launch.
- 200 OK with no noindex → Googlebot indexes the placeholder as real content. Dangerous for any site with existing rankings. Avoid.
Decision Table: WordPress Maintenance Mode vs Coming Soon — Which Mode for Your Situation
The right choice between wordpress maintenance mode vs coming soon depends entirely on the state of your site and the nature of the change you are making. The table below covers the scenarios most SA operators actually encounter.
| Scenario | Site Status | Use | Key Reason | SA-Specific Note |
|---|---|---|---|---|
| Building a brand-new site (never been live) | Pre-launch | Coming Soon (200 + noindex) | Nothing to preserve in Google's index; build audience pre-launch | Under POPIA s69, sending marketing emails to those addresses requires explicit consent — include an unticked opt-in checkbox and purpose statement on the sign-up form |
| Plugin, theme, or core update (minutes to a few hours) | Live | Maintenance Mode (503) | 503 + Retry-After signals Googlebot to retry — rankings preserved | Know how to delete .maintenance if an interruption leaves the site stuck |
| Emergency repair or hack recovery | Live | Maintenance Mode (503) | Hides broken or compromised site from visitors while protecting SEO intent | Use a plugin with a custom message so customers see a branded screen, not a server error page |
| Major redesign of an existing live site (weeks to months) | Live | Rebuild on staging; old site stays live | Do not put an existing ranked site into maintenance for weeks — deindexation risk is real | If old site must come down, use Coming Soon (503 or 200+noindex) and communicate timeline to loyal customers |
| Opening a new branch / new product line (never had a URL) | Pre-launch page on existing domain | Coming Soon page for that URL | New URL has no ranking history; email capture and pre-launch buzz are the goal | Set a clear launch date in the countdown — vague "coming soon" with no date annoys SA users |
| Domain migration to a new address | Live (old domain) | Keep old site live; redirect after launch | Do not take old domain offline before redirects are confirmed working | See the guide to moving your website without downtime |
Planning a site rebuild or relaunch?
Tell us your current setup and launch timeline — we will review your staging and redirect plan so nothing gets lost in the migration.
Get a pre-launch reviewHow to Enable Each Mode in WordPress
Both modes are straightforward to activate, and the plugin choice matters less than the configuration.
Enabling maintenance mode
WordPress handles routine updates automatically — the 503 maintenance screen appears and disappears without your input during a normal update cycle. For planned manual maintenance (a theme rebuild, a database migration), you need a plugin to hold the site in maintenance mode deliberately while you work.
LightStart (formerly WP Maintenance Mode) is a free option with role-based access control — you can stay logged in and see the live site while everyone else sees the maintenance screen. Elementor's built-in maintenance mode lives under Elementor → Tools and is available in the free plugin — no Pro licence or additional plugin required. Either way, your choice of WordPress page builder does not affect how the 503 is served; the plugin handles that separately.
Enabling coming soon mode
SeedProd is the most-installed coming soon plugin on WordPress.org. Its free version gives you a drag-and-drop editor, countdown timer, and email capture integration. The one configuration step that cannot be skipped: confirm the page returns either a 503 status or a 200 with a noindex robots directive. Check your browser's developer tools (Network tab → reload the coming soon URL → look at the status code and response headers) to verify what your plugin is actually serving.
If you already have Elementor, its built-in coming soon mode is available in the free plugin — activate it under Elementor → Tools, no Pro licence required. For a comparison of WordPress with competing platforms, the equivalent feature on Wix or Squarespace is built into the dashboard without any plugin configuration.
Correct configuration: Coming soon page returns 200 OK with <meta name="robots" content="noindex"> in the <head>. At launch, the plugin is deactivated and the noindex is removed. Google can now crawl and index the real pages.
Common mistake: Coming soon page returns 200 OK with no noindex directive. Google indexes the placeholder. At launch, the real pages compete with the placeholder already in Google's index — or the placeholder outranks the real pages briefly because it was indexed first.
When WordPress Gets Stuck in Maintenance Mode
Getting your wordpress site in maintenance mode by accident is one of the most common site emergencies SA operators encounter, and it is especially likely when an update is interrupted mid-process. The cause is always the same: the .maintenance file in your WordPress root directory was created at the start of the update but never deleted because the update did not complete cleanly.
The fix is direct: delete the .maintenance file from your site's root directory. You can do this via your hosting control panel's File Manager (enable "Show Hidden Files" — the file is hidden by default), via FTP using FileZilla, or via SSH with rm .maintenance. After deleting the file, clear your browser cache and any caching plugin cache before reloading the site.
Why SA operators see this more often than they expect
While South Africa's electricity grid was stable for well over 300 consecutive days through at least early 2026, any unplanned interruption — to power, network connectivity, or the hosting server itself — can cut a WordPress update mid-process. The result is a stuck .maintenance file. This is the moment the wordpress maintenance mode vs coming soon distinction becomes practically irrelevant: the site is simply down, not showing either screen correctly. Knowing this fix before you need it takes a real emergency off the table. The same fix applies whether the interruption is a power event, a browser crash, or a hosting timeout.
POPIA Compliance for Coming Soon Email Capture
A coming soon page that captures email addresses is collecting personal information under POPIA. Collecting that information can rely on one of POPIA's six lawful processing bases under s11 — for a pre-launch sign-up, legitimate interests or the data subject's consent are the most common. The more important constraint is what happens next: under POPIA Section 69, sending direct marketing emails to those addresses requires explicit consent OR the existing-customer exception — and since a pre-launch subscriber has never transacted with you, the existing-customer exception does not apply. This means your sign-up form needs more than a text field and a submit button.
A POPIA-compliant coming soon email capture form for a South African business includes: a clear one-line statement of what the subscriber is signing up to receive; a link to your privacy notice; and a separate, unticked checkbox explicitly consenting to receive marketing emails — not bundled into the general terms of signing up. Pre-checked boxes and "by signing up you agree to receive marketing" buried in small print do not meet the consent standard.
Your email marketing platform's sign-up form builder (Klaviyo, Omnisend, Mailchimp) can generate a compliant form — but you need to configure the consent field deliberately; it is rarely enabled by default. For a full breakdown of what POPIA requires from your marketing emails, see our POPIA email compliance guide for SA businesses.
The coming soon POPIA checklist
Before activating an email capture form on a coming soon page: (1) state clearly what emails the subscriber will receive; (2) link to your privacy policy; (3) add an unticked consent checkbox — separate from the submit action; (4) confirm the form platform stores the consent record. South African operators who skip step 3 are collecting emails they cannot legally market to when they launch.
Why South African Businesses Choose Growth Pulse Media for WordPress Setup
The wordpress coming soon vs maintenance mode decision is one of those configuration calls that looks obvious in a tutorial and causes real SEO damage when it gets wrong. Growth Pulse Media handles this work from an operator's position: Dirk van Greuning built and scaled a South African ecommerce business before founding the agency, which means the advice accounts for local hosting realities, the Information Regulator's guidance on POPIA consent, and the indexation consequences of decisions that generic global tutorials skip entirely.
Our web design service covers WordPress builds, rebuilds, and migrations — including getting the wordpress maintenance mode vs coming soon configuration right from day one, noindex verification at launch, staging environments, and redirect plans. All work is executed in-house, with a limited client load that keeps senior attention on every project. We are also a registered Shopify Partner and Omnisend Certified Partner, which matters if your site involves ecommerce or email integration alongside your WordPress build.
If you are managing a site that is already live on a platform like Google Sites or Wix, the maintenance and coming soon question presents differently — some hosted platforms do not give you HTTP header control at all, which is one of the practical reasons SA operators building for growth tend to move to self-hosted WordPress.
Who This Is NOT For
Operators running a multi-site WordPress network: Maintenance mode on a WordPress Multisite installation behaves differently from a single-site setup — some network-level plugins serve the 503 across all subsites simultaneously, which may not be what you want. This post covers single-site WordPress; Multisite configuration is a separate topic.
Businesses expecting a coming soon page to build SEO while the site is being built: A properly configured coming soon page (with noindex) will not accumulate any search rankings during the pre-launch period. The page is deliberately invisible to Google. If your goal is to start ranking before launch, you need real indexed pages — a coming soon screen is not a substitute.
Anyone planning to run maintenance mode for more than a week: If your site needs to be down for longer than a few days, the 503 maintenance approach starts to carry real deindexation risk. A major rebuild should stay on staging with the old site live, or use a coming soon approach — not an indefinite maintenance screen.
Sites on managed WordPress hosting with automatic update handling: Some managed WordPress hosts (WP Engine, Kinsta, and local SA providers offering managed hosting tiers) handle updates in the background without triggering the standard WordPress maintenance file. If your host manages updates for you, verify how they handle the update process — the standard fix for a stuck maintenance file may not apply.
Ready to launch — or worried your current setup has an indexation risk?
Send us your site URL and we will check your maintenance/coming soon configuration, status codes, and noindex settings before anything gets indexed incorrectly.
Book a configuration auditFrequently Asked Questions
What is the difference between WordPress maintenance mode and coming soon mode?
WordPress maintenance mode is for an existing live site that needs to go briefly offline for updates — it returns a 503 HTTP status code that tells search engines the downtime is temporary. A coming soon page is for a new site that has not yet launched — it typically returns a 200 OK status (often with a noindex directive) and is designed to be visible for weeks or months while the site is built. Using maintenance mode for a pre-launch site, or coming soon mode for an existing ranked site, can create SEO problems.
Will WordPress maintenance mode hurt my Google rankings?
A brief maintenance mode window — minutes to a few hours — should not hurt your rankings. Google's Gary Illyes has noted that brief 503 windows do not trigger the crawl-rate reductions that extended outages cause, and Google's own documentation confirms that already-indexed URLs are preserved during brief 5xx periods. Extended maintenance lasting several days or more does carry a real risk of crawl rate reduction and eventually deindexation, so maintenance mode should never be left active longer than necessary.
What happens if I forget to disable the coming soon page at launch?
If your coming soon page uses a noindex robots directive, Google will not index your real site pages — effectively making your site invisible in search results even though it is technically live. Forgetting to remove the coming soon mode is one of the most common launch mistakes in WordPress. After deactivating the coming soon plugin, verify in Google Search Console that your pages are being crawled and indexed, and check your site's robots meta tags to confirm no noindex directive remains active.
How do I fix WordPress stuck in maintenance mode?
Delete the .maintenance file from your WordPress root directory — access it via your hosting control panel's File Manager (enable "Show Hidden Files"), via FTP, or via SSH with rm .maintenance. After deleting the file, clear your browser and plugin caches. The site returns to normal immediately, regardless of whether the interruption was a power event, network drop, or plugin conflict.
Do I need POPIA consent for emails collected on a coming soon page?
The data collection itself can rely on one of POPIA's six lawful processing bases under s11. The critical rule applies to what you do with those addresses: under POPIA Section 69, sending direct marketing emails requires explicit consent OR the existing-customer exception — and pre-launch subscribers have never transacted with you, so that exception does not apply. Your form must include an unticked checkbox consenting to receive marketing emails, linked to a privacy notice. Pre-checked boxes or bundled consent do not meet the standard.
Get Your WordPress Configuration Right Before It Costs You Rankings
Growth Pulse Media configures and launches WordPress sites for South African businesses — maintenance mode, coming soon setup, noindex verification, POPIA-compliant forms, staging environments, and redirect plans all handled in-house. Named SA integrations: PayFast, Peach Payments, Yoco, Klaviyo, Omnisend. No obligation — we will get back to you within 24 hours.
Talk to us about your WordPress site