Back to Community
Home / Community / General

Why Your SeedProd Coming Soon Page Looks Different in Preview vs. Live

26 threads Sep 9, 2025

Content

You've spent time crafting the perfect coming soon page in the 'Website Builder by SeedProd' plugin. The live preview looks exactly how you want it. But then you open an incognito window or check on your phone, and the live page is broken, missing images, or looks completely different. This is a common and frustrating issue for many users.

Based on community reports and troubleshooting threads, this discrepancy is almost never a bug in the plugin itself. Instead, it's almost always caused by one of a few common external factors. This guide will walk you through the most likely causes and how to resolve them.

Why This Happens

The 'Website Builder by SeedProd' plugin generates your coming soon page dynamically. Several layers between the plugin and your visitor's browser can cache or alter this page, causing the preview (which often bypasses these layers) to look different from what the public sees.

Common Solutions

1. Clear All Caches (The Most Common Fix)

Caching is the number one culprit. Your browser, your WordPress plugins, and your web host can all store a temporary, static copy of your site to make it load faster. When you update your coming soon page, these caches need to be cleared to show the new version.

  • Browser Cache: Always clear your browser's cache and cookies, or test your site in an incognito/private browsing window.
  • Site Cache: If you use a caching plugin (like W3 Total Cache, WP Rocket, etc.), find its settings and use the 'Clear' or 'Purge Cache' option.
  • Hosting Cache: Many web hosts (like SiteGround, WP Engine, Bluehost) run their own server-level caching. This is often the most stubborn cache to clear. You may need to log into your hosting control panel (e.g., cPanel) or contact your host's support and ask them to flush the cache for your domain.

Pro Tip: You can often bypass some caching by adding a random parameter to your URL, like http://yoursite.com/?12345. If the page looks correct with this parameter but not without it, you have confirmed a caching issue.

2. Check If You Are Logged Into WordPress

By design, the 'Website Builder by SeedProd' plugin does not show the coming soon page to logged-in administrators. This allows you to work on your live site while visitors see the "Coming Soon" message. If you are checking your site while logged in, you will never see the coming soon page. Always log out of WordPress or use an incognito window to view your site as a visitor would.

3. Resolve Conflicts with Other Plugins or Themes

Other code on your site can sometimes conflict with the coming soon page.

  • Lazy Loading: Plugins that lazy load images (delay loading them until they are in view) can prevent your background images or logos from appearing on the coming soon page. Try temporarily disabling lazy loading features or the plugin itself to test.
  • Optimization Plugins: Plugins that minify CSS or JavaScript can occasionally break the styling of the coming soon page. Try disabling optimization plugins to see if the issue resolves.
  • General Conflict Test: The most reliable way to check for a conflict is to temporarily deactivate all other plugins besides SeedProd. If the coming soon page works correctly, reactivate your plugins one by one to identify the culprit.

4. Verify Image URLs and HTTPS

If your background image shows in preview but not live, there may be an issue with the image link. A common problem is having a mixed-content error, where your site is loaded over HTTPS (secure) but the image is linked via HTTP (insecure). Modern browsers will block the insecure image.

Ensure that the image URL in your SeedProd settings uses https:// if your website uses SSL. You can check for these errors by opening your browser's developer console (F12) and looking for red error messages when the page loads.

5. Remove Old Site Files (index.html)

Before installing WordPress, some hosts display a default placeholder page (often named index.html). If this file still exists in your root directory, the server might be displaying it instead of the WordPress index.php file that runs SeedProd. Use your host's file manager or FTP to locate and delete any old index.html or default.html files in your website's main folder.

Still Need Help?

If you have worked through all these steps and your issue persists, you can seek further help from the wider community. When asking for help, be sure to provide your site's URL and details about the steps you have already taken to troubleshoot. This information is crucial for others to assist you effectively.

Related Support Threads Support