Why Does My Site Show Test Mode?

Article author
Memberstack Team
  • Updated

"Why Does My Site Show Test Mode?" Troubleshooting Guide 

If you have upgraded your Memberstack subscription and launched your site, but you or your members still see the "Test Mode" badge in the bottom-center, do not panic! This is one of the most common setup hurdles, and it can almost always be fixed in under 5 minutes.

This guide will walk you through exactly why the badge is showing and how to get your live site running smoothly.

⏱️ TL;DR

If your site still shows the "Test Mode" badge after going live, check these 3 things:

  1. Check your Domains settings: Go to Settings > Application > Application Domains. Your live domain (both yourdomain.com and www.yourdomain.com) must be listed under Live Domains, not Test Mode Domains.
  2. Skip the DNS Setup (Unless needed):** You do **not** need to complete the 4-step "Custom Domain (DNS)" section just to go live. This is optional (more details below).
  3. Clear your cache: If you just updated your domains, open your site in an Incognito/Private window. Your browser is likely caching the old "test" state.

⚡ Quick Diagnostics: The 30-Second Check

Before diving into the details, check these three things:

  • Do you have a paid Memberstack subscription? (Basic, Professional, Business, or Established). Sandbox apps are locked to Test Mode.
  • Are you looking at your production domain? Webflow staging domains (like yoursite.webflow.io) will—and should—always show Test Mode.
  • Have you opened your site in an Incognito/Private window? (Browser caching is the #1 culprit for returning admins).

If you checked those and still see the badge, locate your specific issue below.

 

1. The Core Concept: How Memberstack Decides to Show "Test Mode"

It is a common misconception that toggling the Test Mode/ Live switch inside your Memberstack Dashboard header controls your website's mode.

The dashboard toggle does not change your live website. It only changes which data you are currently viewing inside your dashboard (e.g., viewing live members vs. test members).

Instead, Memberstack looks at the domain (URL) your visitor is currently on and matches it against your Settings > Application Domains in Memberstack:

  • If the URL matches a domain in your Test Mode Domains list: Memberstack loads in Test Mode (showing the badge, using test API keys, and allowing test credit cards).
  • If the URL matches a domain in your Live Domains list: Memberstack loads in Live Mode (no badge, real payments, and live members).

2. Common Culprit: "Application Domains" vs. "Custom Domain (DNS)"

⚠️ The #1 point of confusion for new users!

In your Memberstack settings, you will see two different sections. They sound similar, but they do completely different things:

  • Application Domains (Settings > Application)
     
    • What it does: Tells Memberstack which URLs are your staging sites (Test Mode) and which are your production sites (Live Mode).
    • Do I need it to go Live? YES. This is mandatory.
  • Custom Domain (DNS) (Settings > DNS)
     
    • What it does: Connects your domain's DNS to white-label system URLs (e.g., changing auth.memberstack.com to login.yourdomain.com).
    • Do I need it to go Live? NO. Optional for standard sites. (Required only if they want to implement custom domains for the social auth login / signup flow / SSO etc. ).

The Gotcha: Many users see the "Custom Domain (DNS)" section with its 4-step setup checklist and assume they must complete it to go live. You do not. If you don’t want to set up custom domains for your  Social Logins / SSO (Google/Facebook/LinkedIn) or keeping users logged in across multiple domains (like yoursite.com and app.yoursite.com), you can completely ignore this section.

3. The www vs. Root Domain Gotcha

Computers see yourdomain.com and www.yourdomain.com as two entirely different websites. If you only add one of them to your Live Domains list, the other will default to Test Mode.

How to fix it:

  1. Go to Settings > Application > Application Domains in your Memberstack Dashboard.
  2. Look at your Live Mode Domains list.
  3. Ensure both variations of your domain are added:
    • yourdomain.com
    • www.yourdomain.com
  4. Save your changes.

4. Webflow Staging URLs (.webflow.io)

If you are building on Webflow, your site has a staging domain that ends in .webflow.io.

  • This is normal: Your staging domain should remain in your Test Mode list. This allows you to safely test signups, gating, and custom code changes using Stripe's test card (4242 4242...) without affecting your live production database.
  • The fix: Only expect the Test Mode badge to disappear when you visit your actual custom production domain (e.g., yourdomain.com).

5. Browser Caching & Stale Bookmarks

If you have recently updated your settings in Memberstack but the badge is still showing for you or a returning member, your browser is likely caching the old "test" state of the site.

How to resolve caching issues:

  • Test in Incognito: Open a Private/Incognito browser window and navigate to your live site. If the badge is gone, your settings are correct, and your main browser just needs its cache cleared.
  • Clear Site Data: In your browser, clear the cached images, files, and local storage for your domain.
  • Check Bookmarks: Ensure users aren't navigating to a bookmarked URL that contains test parameters or redirects from your staging environment.

6. Propagation Time: How long do changes take?

  • Application Domain Changes (Settings > Application): Adding or moving domains between Test Mode and Live lists in Memberstack is instantaneous. Once you click save, the change is live on our servers. (If you don't see it immediately, it is a local browser caching issue, not propagation). 
  • Custom Domain (DNS) Changes: If you did choose to set up the optional Custom Domain (DNS) records in your registrar (GoDaddy, Namecheap, Cloudflare, etc.), these changes rely on the global internet infrastructure and can take anywhere from 15 minutes to 48 hours to fully propagate worldwide.

Pro-Tip: If you use Cloudflare, make sure proxying (the orange cloud) is turned OFF (set to "DNS Only") for your Memberstack CNAME records. 

 

💡 What is the Test Mode Badge actually for?

While you are in Sandbox/Test Mode, the badge in the bottom-center is actually your best friend!

If you click the Test Mode badge, it opens the Test Mode Inspector. This built-in diagnostic panel shows you:

  • Active data attributes on the page.
  • Real-time errors or warnings in your setup.
  • Which member plan is currently simulated.

Once your domain is successfully moved to the Live list, this badge and the inspector are completely hidden from your visitors automatically.

 

📋 Summary Checklist to Go Live

To ensure your site is officially in Live Mode, make sure:

  1. You have upgraded to a paid Memberstack subscription.
  2. Your custom domain (both yourdomain.com and www.yourdomain.com) is listed under Live Mode Domains in Memberstack.
  3. Your staging domains (like .webflow.io) are listed under Test Mode Domains.
  4. You are visiting your live production URL, not a staging URL.
  5. You have tested the live URL in an Incognito window to bypass browser cache.

❓ Frequently Asked Questions (FAQ)

Q: I toggled the environment switch in my dashboard header to "Live", but my website still shows Test Mode. Why?

The toggle in the dashboard header only changes which data you are viewing inside the dashboard (e.g., viewing your live members vs. test members). It has no effect on your live website. Your website's mode is controlled purely by which domain list your URL is in under Settings > Application > Application Domains.

Q: Do I need to complete the 4-step Custom Domain (DNS) setup to go live?

No. You can completely ignore this section. This is only for advanced users who want to white-label Memberstack's system URLs for custom SSO or custom social login branding. Your site will be 100% live and secure without it.

Q: My live site is working, but a few of my members say they still see "Test Mode" when they log in. How do I fix this?

This is almost always a local browser caching issue on their end. Have them clear their browser cache, or open the site in an Incognito/Private window. Also, make sure they aren't using an old bookmarked link that points to your Webflow staging URL (like .webflow.io).

Q: Can I use test credit cards (like 4242) on my live domain to test it?

No. Once a domain is in your Live Domains list, it will only accept real credit cards and process real payments through Stripe. If you want to run a test, use your staging domain (.webflow.io) which remains in your Test Mode list.

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.