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

# Install with your website platform

> Use the same Darwin snippet in custom HTML or your site builder.

Darwin uses one asynchronous script. Copy it from [Settings → Installation](https://app.meetdarwin.ai/admin/settings/installation), then place it in the location your website platform provides for site-wide footer code.

<Tabs>
  <Tab title="Custom HTML">
    Add the snippet before `</body>` in your shared page template. If you use separate HTML files, include it on each page where the widget should load. Keep `async` so the script does not block page parsing.
  </Tab>

  <Tab title="Website builders">
    Use the builder’s custom code or footer-code setting. Confirm that your plan supports custom JavaScript, save, and publish. A designer canvas or preview hostname may behave differently from the published site; test the public domain after publishing.

    For WordPress, use your site’s approved script-insertion method or shared theme footer. For Webflow, Framer, or a similar builder, use the site-wide custom code location. The exact menu name depends on your platform version.
  </Tab>

  <Tab title="React or other web apps">
    Load the embed once from the shared application layout or your framework’s supported script mechanism. Do not add a new copy on every component render. Test both a direct page load and navigation between pages, and confirm the reported page in Darwin.

    If your site uses a content security policy, ask your developer to allow the script and its required network connections. Do not disable the policy for the entire site.
  </Tab>

  <Tab title="Tag manager">
    Add the snippet using your tag manager’s custom HTML or equivalent script tag, with the intended page trigger. Publish the container, then check the actual website. Darwin’s HTML installation check may not detect scripts injected after the initial page response.
  </Tab>
</Tabs>

## Before you publish

* Allow the exact website hostname in Darwin.
* Use the snippet for the correct workspace.
* Remove duplicate Darwin embeds.
* Check that consent settings, script blockers, or a security policy are not preventing the widget from loading.
* Test a phone-sized viewport and a page with sticky navigation or other floating controls.

[Complete the launch checklist →](/installation/launch-checklist)