Webflow sync, pageviews & more.
NEW

How can I troubleshoot the non-functioning Script before tag, HTML Embed, and Exit-intent-pop-up elements on my Webflow homepage after cloning the website?

TL;DR
  • Check Project Settings and HTML Embeds to ensure all custom code, scripts, and attributes were properly cloned.
  • Re-add any stripped external scripts or frameworks, verify dependencies like jQuery or GSAP, and use DevTools to identify and fix any errors or missing elements.

If your Script before tag, HTML Embed, or Exit-intent pop-up elements aren’t working after cloning a Webflow site, you likely need to re-check settings and script integrity in the new project.

1. Review Cloned Project for Missing Custom Code

  • Go to Project Settings > Custom Code.
  • In both Head Code and Before tag areas, check that expected scripts were cloned correctly.
  • Webflow sometimes strips code during cloning if it contains certain tags, like <script> referencing external domains or JS frameworks.

2. Check HTML Embed Blocks in Designer

  • Open the homepage in Webflow Designer.
  • Locate the embedded elements (like exit-intent pop-up triggers or script containers).
  • Make sure the HTML Embed component wasn’t emptied or altered during the clone process.
  • If it uses Custom Attributes, verify those also got carried over.

3. Ensure Scripts Aren’t Blocked or Need Manual Re-Embedding

  • If the scripts reference 3rd-party services like HubSpot, ConvertFlow, or Intercom, make sure:
  • You re-enter account-specific script IDs or API keys if required.
  • Scripts hosted externally did not get lost or disconnected during the clone.

4. Check for jQuery or JS dependencies

  • Webflow includes jQuery by default, but custom scripts might depend on other libraries that were added manually.
  • Inspect the code you cloned to see if it references libraries like GSAP, jQuery plugins, etc., and ensure they’re still included.

5. Test Exit-Intent Pop-up Triggers

  • Make sure the event listeners (e.g., mouseleave, scroll position) used for exit-intent detection are:
  • Still present in the DOM.
  • Not firing due to missing class names, IDs, or dependencies.

6. Use Browser Developer Tools to Debug

  • Open Chrome or Firefox DevTools, go to the Console tab.
  • Reload the homepage and look for any errors, such as:
  • "Uncaught ReferenceError" or "Failed to load resource".
  • These usually indicate broken scripts or missing elements.

7. Reinsert or Manually Add Missing Scripts

  • If scripts were stripped during cloning, copy them from the original site and paste them back into:
  • Project Settings > Custom Code, or
  • A dedicated HTML Embed block on the relevant page.

Summary

To fix non-functioning embed and script components on your cloned Webflow homepage, verify that custom code wasn’t stripped, re-add any lost external scripts, and confirm all event triggers and dependencies are intact. Use DevTools to identify script errors and manually restore missing code where needed.

Rate this answer

Other Webflow Questions