The safest way to put a polished placeholder in front of visitors is to enable a WordPress coming-soon mode that serves the placeholder to logged-out users while authenticated editors continue working on the real site. In SeedProd, you create the page, choose a template, customize it, save it, activate Coming Soon Mode, and test the public view in a private browser window.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Choose the mode before designing anything. Coming Soon Mode is intended for a new or unfinished site and normally responds with HTTP 200, which means search engines may index the placeholder. Maintenance Mode is for short interruptions on an existing site and responds with HTTP 503 to signal temporary unavailability. The right choice affects both visitors and search crawlers.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteComing Soon Mode and Maintenance Mode are not interchangeable
A coming-soon page is a temporary front door for a site that is still being built. It can explain what the site will offer, collect launch interest, and give visitors a credible experience while the theme, content, integrations, or game-related resources are being prepared. The underlying WordPress site remains available to logged-in staff when the mode is configured correctly.
Maintenance mode communicates a different state: an established site is briefly unavailable while work is performed. SeedProd documents Maintenance Mode as returning an HTTP 503 status code to search engines. A 503 tells crawlers that the outage is temporary and that they should try again later. It is appropriate for a short maintenance window, not as the default for a weeks-long prelaunch.
| Question | Coming Soon Mode | Maintenance Mode |
|---|---|---|
| Best for | A new site or a site being built | Short-term work on an existing live site |
| What logged-out visitors see | Your coming-soon page | Your maintenance page |
| What logged-in WordPress users see | The regular site, according to SeedProd’s documented behavior | The regular site, according to SeedProd’s documented behavior |
| HTTP response documented by SeedProd | HTTP 200 | HTTP 503 |
| Search visibility | Accessible to search engines by default; decide whether to allow indexing | Signals temporary unavailability rather than normal page availability |
| Typical duration | Until the public launch | A defined maintenance interval |
Do not enable Maintenance Mode simply because the design is unfinished. Conversely, do not leave Coming Soon Mode active during a brief outage if you need crawlers to understand that the site is temporarily unavailable.
Decide what search engines should see
SeedProd says Coming Soon Mode returns HTTP 200 and allows search engines to index the page unless the WordPress site is separately set to private. That default can be useful when the page contains meaningful information about an upcoming project, but it can also expose a thin placeholder in search results before your real content exists.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Allow indexing when the page is a real preview
Allow discovery only when the page itself is useful: for example, it names the publication, describes the games or guides it will cover, and gives visitors a reliable way to follow the launch. Write a specific title and description rather than leaving generic template copy in place.
Prevent indexing when the site is not ready
Use SeedProd’s No Index setting or an appropriate robots.txt directive when you do not want the placeholder indexed. Also check WordPress’s privacy setting; a site set to private can override the expectation that a coming-soon page is publicly discoverable. Treat the indexing decision as a launch requirement, not a cosmetic setting.
A No Index instruction does not make the page private from a person who has the URL. Use access controls, a bypass URL, IP restrictions, or another authentication layer when the content must be limited to a team.
Prepare the page before you turn the switch on
Visitors need a reason to wait and a clear expectation of what happens next. Keep the first screen focused. A gaming publication might state that game guides, release coverage, or a community hub are being prepared, but it should not promise a date that the team cannot meet.
Recommended Free Tools
Include the essentials
- Identity: Use the site’s name, logo, color palette, and a recognizable visual style.
- Purpose: Explain in one or two sentences what is coming and who it is for.
- Next step: Offer an email opt-in or another notification method only if you will actually use it.
- Timing: Add an expected launch date or countdown only when the date is dependable.
- Contact or social path: Give visitors a legitimate way to ask questions or follow progress if that channel is monitored.
SeedProd lists branding, countdown timers, and opt-in forms as available content blocks. A countdown is optional, not a requirement. An inaccurate timer damages trust more than a simple “launching soon” message.
Keep the copy specific
Replace phrases such as “We are working on something awesome” with a concrete description. State whether the site will publish walkthroughs, esports news, a mod database, or another defined resource. Do not fill the page with unfinished navigation, dead buttons, or stock testimonials.
SeedProd: the documented setup sequence
SeedProd is one plugin-based way to implement this workflow. Its WordPress.org listing says the free version includes coming-soon and maintenance-page templates; the listing also describes additional paid capabilities, so do not assume every block or integration is included in the free version.
1. Open the Coming Soon setup
- Sign in to WordPress with an account that can manage plugins and site settings.
- Open the SeedProd Dashboard in the WordPress admin.
- Choose the option to set up a Coming Soon Page.
Menu labels can change between plugin versions. If the dashboard does not show the same wording, use the current Coming Soon or landing-page entry rather than enabling a similarly named setting at random.
Free tools Windows power users keep installed
One-click scans. No signup required.
2. Choose a template or start blank
- Select an available coming-soon template that matches the site’s visual direction, or choose a blank template.
- Prefer a simple layout that works on mobile screens and loads quickly.
- Remove blocks that do not serve the launch message before adding decorative elements.
SeedProd describes its landing pages as independent of the active WordPress theme. That separation is useful when the theme is incomplete: the placeholder can have a finished layout even while the production theme is still being assembled.
3. Customize the visual builder
- Add the site logo or wordmark and set the primary colors and typography.
- Write a concise headline that states what is coming.
- Add supporting text with the site’s subject, audience, and current status.
- Add a countdown block only if the launch date is dependable.
- Add an email opt-in block when you have a compliant process for storing and sending to subscribers.
- Check every button, form, image, and social link. Remove anything that is not ready to work.
For a video-game site, a useful message might identify the kinds of coverage planned and name the platform or genre focus. Avoid implying that a game, partnership, or release is confirmed unless it really is.
4. Set page SEO and visibility options
- Open the page settings for the SEO title and description.
- Choose whether to enable No Index.
- Review the site’s WordPress privacy setting and any robots.txt rule that could change crawler access.
- Save the settings before leaving the builder.
Use a title and description that accurately describe the coming site. Do not repeat a keyword unnaturally or write a launch date that conflicts with the visible page.
5. Save the design
Use the builder’s save action and wait for it to complete. If the page contains a form, submit a test entry according to your email provider’s process and confirm that the expected confirmation appears. A visual preview alone does not prove that a form delivers mail or stores consent correctly.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →6. Activate Coming Soon Mode
- Return to the SeedProd Dashboard.
- Find the Coming Soon control for the page you created.
- Turn Coming Soon Mode on.
Activation changes what unauthenticated visitors receive. Keep an existing administrator session open so you can work, but do not mistake that privileged view for the public result.
Rank #4
7. Test as a visitor
- Open the site’s public URL in a private or incognito browser window where you are logged out of WordPress.
- Check the home page and several important paths, including a likely direct URL.
- Verify that the headline, logo, responsive layout, form, links, and contact method work.
- Open the site in a normal logged-in window and confirm that your team can still see the regular WordPress site.
SeedProd’s documented behavior is that logged-in users see the regular site while visitors see the coming-soon page. Confirm the result on your own host, because other plugins, caching layers, security rules, and custom server settings can change what a request receives.
Control who can bypass the placeholder
A public placeholder and a private staging environment are different goals. SeedProd’s page settings include access controls such as a bypass URL, URL inclusion and exclusion, IP restrictions, and role-based access for coming-soon and maintenance pages.
Use a bypass URL for a small review group
A bypass URL can let reviewers see the working site without receiving WordPress credentials. Treat that URL as a secret: do not publish it in a public issue, and replace or disable it if it is shared too widely.
Use role-based access for internal editors
Role-based access can preserve the regular site for selected WordPress roles while everyone else sees the placeholder. Grant only the roles that need it, and test with an account that has exactly that role rather than assuming an administrator test represents all staff.
Use URL and IP rules for targeted exceptions
URL inclusion or exclusion can keep selected paths available, while IP restrictions can support an office or known review network. These rules are especially important when a public home page is hidden but a verification endpoint or preview path must remain reachable. Document every exception so it is removed at launch.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do when the page does not behave as expected
Logged-in users see the placeholder
- Confirm the account is actually logged in to the same WordPress installation and domain.
- Check the role-based access settings and any bypass rule.
- Open the site in a fresh private window to separate an authentication issue from a cached response.
- Review conflicts with security, redirect, or page-cache plugins.
Logged-out visitors see the regular site
- Return to the SeedProd Dashboard and confirm Coming Soon Mode is enabled.
- Verify that the intended page is selected and saved.
- Check URL exclusion rules; the requested path may be deliberately excluded.
- Clear relevant page, object, reverse-proxy, or CDN caches and test again.
The plugin listing and support material mention caching as a common troubleshooting path. That does not mean caching is always the cause; clear and verify each layer rather than changing settings blindly.
The old placeholder remains after launch
- Turn Coming Soon Mode off in the SeedProd Dashboard.
- Clear relevant WordPress and CDN caches.
- Open a private browser window and request the home page again.
- Check a second network or device if a proxy may be retaining the old response.
If one visitor still sees the placeholder while another sees the live site, compare their cache path and cookies before rebuilding the page.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe page is indexed when it should not be
- Check the page’s No Index setting.
- Review the WordPress privacy setting.
- Inspect robots.txt directives and any SEO plugin rule.
- Confirm that the public response is the intended page and status, not a cached older version.
Indexing controls are not a substitute for access control. If confidential material appears on the page, remove it and restrict access immediately.
The form or countdown is wrong
- Submit a real test entry and verify the destination mailbox or subscriber list.
- Check consent text and confirmation behavior before collecting public addresses.
- Recheck the countdown timezone and date; remove it if the launch is uncertain.
- Test on a phone-sized viewport and a desktop viewport.
Launch-day checklist
Do these checks before announcing that the site is live:
- Turn Coming Soon Mode off.
- Open a private, logged-out window and load the home page.
- Verify the main navigation, representative articles or game pages, search, forms, and contact links.
- Check that the intended indexing and privacy settings are now appropriate for the live site.
- Remove temporary bypass URLs, IP exceptions, URL exclusions, and reviewer accounts that are no longer needed.
- Clear relevant caches and test again from outside the administrator session.
- Confirm that the old page is not returned by a direct URL or a cached CDN edge.
Keep an administrator session and a private visitor session side by side during this process. The two sessions are expected to receive different output while the mode is active, so checking only one can hide a launch problem.
When a plugin-controlled page is the right approach
A plugin-controlled mode is practical when you want a visual builder, a theme-independent placeholder, logged-in access, and controls for exceptions without editing theme files. It also gives the team a clear on/off switch at launch.
It is not a universal WordPress menu. Other plugins, hosting dashboards, and custom server configurations may use different labels or implement status codes and access rules differently. SeedProd is one documented option, not proof that every WordPress installation behaves the same way. Confirm the public response on the actual domain after activation and again after disabling it.
Final decision: which mode should you enable?
Choose Coming Soon Mode when the site is new or still being built and you want logged-in staff to work while visitors see a branded placeholder. Decide deliberately whether that HTTP 200 page should be indexable. Choose Maintenance Mode for a short interruption on an existing site when a temporary HTTP 503 response is the accurate signal. In either case, create the page, test it while logged out, review access and cache behavior, and switch the mode off before the public launch.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
