> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remapdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Widget not visible

> Fix cases where the Remapdb widget does not appear on your website.

Use this page when the widget does not show on your live page or shows an error in the widget area.

<Warning>
  If your website is missing in Allowed websites, the widget will not load.
</Warning>

## Step-by-step fix

<Steps>
  <Step title="Step 1: Check Allowed websites first">
    Open the [**Installation**](https://app.remapdb.com/widget/install) page in Remapdb, then check **Add allowed websites**.

    Make sure the website in your browser address bar is added exactly.

    If you need help with website format, open [Code installation](/widget/installation/code-installation#website-address-rules-and-examples).
  </Step>

  <Step title="Step 2: Confirm your plan website limit">
    If your plan website limit is full, newly added websites can stay listed but inactive.

    Open [Billing](https://app.remapdb.com/settings/billing) to check your current plan, and open [Feature availability by plan](/feature-availability-by-plan) for limits.
  </Step>

  <Step title="Step 3: Confirm code is installed on the live page">
    Check the live page source and confirm both are present:

    * Widget container element.
    * The Remapdb embed script with the correct widget ID.
  </Step>

  <Step title="Step 4: Test the published website, not editor preview">
    If you use a website builder, open the published website URL and test there.
  </Step>

  <Step title="Step 5: Check subscription health">
    If subscription is not operational, the widget can be blocked even when code and website are correct.

    Open [Billing](https://app.remapdb.com/settings/billing) and confirm subscription is active.
  </Step>

  <Step title="Step 6: Clear cache and test again">
    Clear website cache/CDN cache, then reload with hard refresh (`Ctrl/Cmd + Shift + R`).
  </Step>
</Steps>

## Most common widget error codes

| Error code | Meaning                         | Primary action                       |
| ---------- | ------------------------------- | ------------------------------------ |
| `0030`     | Widget ID not found             | Verify widget ID in embed code       |
| `0031`     | Website context missing         | Re-check embed setup                 |
| `0032`     | Website is not allowed          | Add this website in Allowed websites |
| `0036`     | Subscription is not operational | Fix subscription status in Billing   |

There are other less common error codes that may be displayed in the widget area.
If you see an error code that is not listed above, please contact support for assistance. Make sure to include the error code in your support request.

## Other common issues

| Issue                                                 | Primary action                                        |
| ----------------------------------------------------- | ----------------------------------------------------- |
| Widget is displayed but does not open                 | Re-check your widget configuration                    |
| Widget is displayed but styling is incorrect          | Check your branding settings and custom CSS           |
| Widget is displayed but some features are not working | Check your subscription plan for feature availability |

## If it still does not work

Send this in your support request:

* Live page URL (copy from the browser address bar on the page where the issue happens).
* Widget ID (open **Installation**, then in **2. Install widget code** copy the `data-widget` value).
* Full error text and code (copy exactly as shown).
* Screenshot of browser console/network errors.
* Time of the latest failed test (include your timezone).

If needed, use [Support request process](/support/support-request-process#how-to-find-details-for-support-requests) for a full “how to find each detail” checklist.

Then open [Support request process](/support/support-request-process).

## Related actions

* [Installation troubleshooting](/widget/installation/installation-troubleshooting)
* [Code installation](/widget/installation/code-installation)
* [Support request process](/support/support-request-process)