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?

If your cloned Webflow homepage shows non-functioning Script before </body> tag, HTML Embed, or Exit-Intent Pop-up elements, there are several common causes related to missing settings, script dependencies, or asset permissions.

​

1. Check Custom Code Settings

​

• Go to Project Settings > Custom Code and verify that any scripts in the Footer (before </body> tag) have been properly transferred from the original site.
• Some scripts may not copy over when cloning a project, especially if they were stored in a team or client-specific dashboard.
• If there are external script URLs, make sure they are still valid and correctly loaded.

​

2. Inspect Page-Specific Embeds

​

• Open the Webflow Designer, select the home page, and check any HTML Embed blocks.
• Ensure the embed isn’t referring to custom scripts or IDs that no longer exist or were renamed during the cloning.
• If a script uses other elements (e.g., class names or IDs) to activate, double-check those elements still match the expected structure.

​

3. Verify Exit-Intent Pop-up Settings

​

• Confirm the pop-up itself is present in the Designer and is not hidden or deleted in the cloned version.
• Inspect the interaction triggers (e.g., "Mouse leave viewport") to be sure they are still applied and connected to the pop-up.
• Check for missing or unlinked animations—sometimes cloned Interactions lose connections to elements.

​

4. Confirm Script Dependencies and Order

​

• Exit-intent and embedded components often rely on jQuery or third-party libraries. If these weren’t included in the Custom Code section, they won’t function.
• Make sure the script order doesn’t cause issues. If dependent libraries load after the script that uses them, the features may silently fail.
• Use browser DevTools console (F12) to check for errors like Uncaught ReferenceError or failed network requests.

​

5. Re-add Host-Specific Integrations (If Any)

​

• Some embeds need API keys, cookies, or domain-specific settings that were tied to the original site.
• If the original project used external marketing tools (e.g., OptinMonster, Mailchimp pop-ups, etc.), those may not clone correctly and need to be reconfigured manually.

​

6. Clear Browser and Webflow Publishing Cache

​

• After making changes, always re-publish the site, then clear your browser cache or do a hard refresh to avoid testing against outdated scripts or CSS.
• Use Webflow’s Site Activity Panel to confirm your latest publish includes the necessary changes.

​

Summary

​

Non-functioning scripts or embeds after cloning a site are usually due to missing custom code, broken interaction links, or external dependencies that didn't transfer. Verify your custom code settings, confirm interaction triggers, and inspect the browser console for errors. Re-add any host-specific or API-dependent integrations as needed.