## **🧭 Overview**

When you embed a Lead Capture widget on your website, visitors should see a public-facing form or report — not a login or registration wall. If your current snippet is redirecting visitors to an **Invitation Required** registration page, your widget is pointing to the whitelabel dashboard instead of the public Lead Capture widget endpoint. This article explains how to identify and fix that configuration.

## **🔍 How to Tell Which Problem You Have**

There are two different snippets inside Search Atlas. It is easy to copy the wrong one. Before changing anything, confirm which behavior your visitors are seeing:

- **Public widget working correctly:** Visitors land on a branded report or lead capture form with no login prompt.
- **Invitation-only redirect (this issue):** Visitors are sent to a page that says *Invitation Required* or asks them to register before they can continue. This means your snippet is linking to the whitelabel dashboard URL, not the embeddable public widget.

## **⚠️ Why This Happens**

Search Atlas has two separate access points that look similar but behave differently:

- **Whitelabel Dashboard link** — requires an invitation or account login. It is designed for clients you have explicitly invited to view their reports inside your branded portal.
- **Lead Capture Widget snippet** — a publicly embeddable code block that lets any anonymous visitor submit their site URL, receive a report, and become a lead. No login or invitation is needed.

If you copied your snippet from the whitelabel dashboard settings area rather than the Lead Capture widget settings area, visitors will always hit the invitation gate. The fix is to replace the snippet with the correct one.

## **✅ How to Get the Correct Public Widget Snippet**

1. Log in to your Search Atlas account.
2. In the left sidebar, navigate to **Lead Capture**.
3. Open the **Widget Settings** tab (not the Dashboard or Client Access tab).
4. Locate the **Embed Code** section. The correct snippet will contain a script tag referencing the public widget endpoint — it will **not** contain a dashboard subdomain URL or an invite token.
5. Copy the full snippet exactly as shown.
6. Replace the existing snippet on your website with this new code.
7. Save and publish your page, then test by opening the page in a private/incognito browser window to confirm visitors see the public form instead of an invitation prompt.

## **🛠️ Quick Checklist Before You Go Live**

- You copied the snippet from **Lead Capture → Widget Settings**, not from the whitelabel dashboard area.
- The snippet does **not** include your whitelabel subdomain (e.g., *reports.yourdomain.com/invite*) as the destination URL.
- You tested the page in an incognito window while logged out of Search Atlas.
- Visitors see the lead capture form or public report immediately — no login or registration prompt appears.

## **📋 Additional Configuration to Check**

Even with the correct snippet in place, the following settings can affect public access:

- **Widget visibility:** Inside Lead Capture → Widget Settings, confirm the widget status is set to **Active** or **Published**. A draft or paused widget may still redirect or show an error.
- **Whitelabel domain routing:** If your whitelabel domain and your lead capture widget share a parent domain, ensure the routing rules in your DNS or platform settings are not intercepting the widget URL and sending traffic to the client dashboard instead.
- **Report access toggle:** Some accounts have a setting that restricts report viewing to invited clients only. If that toggle is enabled globally, it will override the public widget. Locate the access control settings under your whitelabel configuration and confirm public report access is allowed.

## **🔄 If the Correct Snippet Still Redirects to Invitation Page**

If you have replaced the snippet with the one from Lead Capture → Widget Settings and visitors are still hitting an invitation-required page, this may indicate a platform-level configuration issue rather than a snippet error. In that case:

- Double-check that you saved and re-published the page after replacing the snippet.
- Clear any caching on your website or CDN, as an old cached version of the page may still be serving the old snippet.
- Try embedding the widget on a brand-new test page to rule out page-level conflicts.
- If the problem persists on a fresh page with the correct snippet, the issue is likely a backend configuration that requires our team to investigate.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.