Job builder-custom-code-embed-breaks-page · revised 11 October 2026
Fix one tracking snippet or widget embed that breaks a page on your site builder
One pasted snippet or widget on a Webflow, Squarespace or Wix page loads without breaking the page, and a tracking tag fires once per page view, with any builder limit named.
You might be seeing
- A widget shows a blank box, is cut off, or does not respond
- The page layout jumps or part of the page stops working after a snippet was added
- Analytics shows double visits, no visits, or conversions that do not match what you see
No passwords, keys, card details or admin invites needed to start.
What usually happened
Hosted builders let you paste code in a few fixed places, each with its own rules: some tags must not go through custom code at all, some embeds run in a sandboxed frame that cannot reach the rest of the page, and some tags are loaded twice because both a built-in integration and a pasted copy exist. A snippet that is valid on its own can still break a page because of where it was pasted.
Who it’s for: Owner or marketer who pasted a tracking snippet, chat widget, booking widget or map into a Webflow, Squarespace or Wix page and now the page looks or behaves wrongly.
Usually starts when: After adding or updating a snippet, a section is blank, the page jumps or loads slowly, a widget does not appear, or your analytics counts every visit twice or not at all.
The result: On the named pages the snippet or widget loads without adding console errors, works at desktop and phone widths, and a tracking tag sends exactly one page view per load as shown in the browser network panel or Google Tag Assistant.
Check whether this job fits
Answer these without sending logins or the snippet itself if it contains private keys. Nothing is submitted unless you choose to contact us.
Checks you can run yourself
Test with the snippet off
Turn the suspect snippet off, publish or preview, and reload the page. Turn it on again and reload.
Look for: If the fault appears only when it is on, the snippet or its placement is the cause. If it stays off, the cause is elsewhere.
What you get
- The corrected placement or replacement of the snippet, listed with where it now lives
- A before and after console and network record for the named pages
- A plain note on anything the builder cannot do for this snippet and the nearest supported route
Included
- One snippet or widget on up to three named pages of one Webflow, Squarespace or Wix site
- Identifying the faulty placement, duplicate load, http link, fixed sizing or wrong integration route
- Moving, correcting or replacing the paste so it follows that builder's own placement rules
- Before and after checks of the page in a browser with the developer console and, for Google tags, Tag Assistant
Not included
- Writing a new widget or rewriting the vendor's own code
- Cookie banners, consent rules or privacy advice, which need your own legal guidance
- Designing a tracking plan, events or conversion goals
- Adding code to Squarespace checkout pages, which Squarespace says do not support code
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
On each named page, the browser console shows no new error compared with the list recorded before the work, at desktop and phone width.
Evidence: Before and after console records for each page.
For a tracking tag, the network panel or Tag Assistant shows one page-view request per page load on each named page, not zero or two.
Evidence: Screenshots of the network panel or Tag Assistant session for each page.
A widget appears at desktop and phone width and its main action works once, such as opening the booking form or the chat window.
Evidence: Screenshots and a short screen recording of the action.
The change list names every place the snippet was found, moved, removed or replaced, and each can be reversed.
Evidence: The change list with the original text and placement kept.
Sign-off. You check the named pages and, for tracking, your own analytics real-time view, and sign off before payment. Your authorised account holder publishes.
If it fails. If the agreed checks fail, you do not pay for this fixed scope. We hand over the findings and agree whether to stop or re-quote; no surprise work.
When it fits, and when we stop
It fits when
- The site is on a paid plan that allows the kind of code you pasted
- You can tell us which snippet or widget is the suspect, or which page broke after which change
- The vendor of the snippet permits embedding on your builder
We stop and tell you if
- The widget vendor blocks being shown inside another site, which neither we nor the builder can bypass
- The fix needs code on Squarespace checkout pages, or a plan feature your plan does not include
- The faulty script is a builder's own app or the vendor's own bug, which only that provider can fix
What could go wrong
The original snippet text and placement are kept in the handover, so you can paste them back. Each change is a single setting or block you can switch off.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| Removing a duplicate tag also removes a tag you needed. | We list every tag found on the page before removing anything and you confirm which one stays. |
| A tracking change alters your reports in a way you did not expect. | We tell you the date of the change so you can note it in your reports; analytics interpretation is yours. |
| A builder update later changes how code is handled. | We note the builder's documented rules at the time of the work, and a monthly check is available as a standing service. |
An independent reviewer checks the redacted before and after evidence, the list of changes and the way back, and looks separately at anything that touches customer data, payments or logins, before you see the result.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the snippet, pages and the check that shows it works
- Record the starting state: console errors, network requests and a screenshot of each page
- Turn the snippet off and on and find where it conflicts or doubles
- Move or replace it using the builder's supported route; for tracking tags, remove the duplicate route
- Re-run the same checks and have a separate reviewer compare the records
- Hand over the change list and the steps to undo it; your account holder publishes
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access and necessary permissions are in place. Builder plan, app, domain and payment-provider charges are yours and are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
If snippets change often, a monthly check of forms, tags and embeds is available as a separate standing service.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- The builder's own help article for the snippet type may describe the supported placement. support.wix.com
- Ask the snippet's vendor, who supports their own code and can say which builders they have tested.
Questions
Will my analytics numbers change?
If a tag was firing twice, your counts will drop to the true number from the date of the change. We tell you that date; interpreting reports is yours.
Do you add a cookie banner?
No. Consent and privacy choices need your own advice. We only make sure the tag you chose loads once.
Can you install a new widget?
This job fixes one existing snippet or widget. Installing a new one that does not yet exist on the site is outside this scope.
Send an enquiry
Send us
- The page address, the builder and the name of the snippet or widget
- Roughly when it broke and what you changed just before
- A screenshot of the page and, if you can, of the browser console with private details masked
Later, once you agree
- Builder access at the role named in the access section, set up by you and removable at any time
- The vendor's install instructions for the snippet, or a link to them
- View-only access to the analytics property for a tracking fix, set up by you
You keep the live site, the builder account, the domain and all customer data. Access is agreed with you in writing before any work starts, and no work starts until it is. Any access we use is through a company-controlled account, never a personal login. The role depends on the builder. Webflow: the Designer or Site manager role, because Webflow lets only those two roles open a site's custom code section; it uses a paid full seat in your Workspace (or a guest invitation, which Webflow allows only to a Freelancer or Agency Workspace). Squarespace: the Administrator permission, because only owners and administrators can add code injection (a Website editor can add a code block but not code injection). Wix: the Website Manager role; Wix's pages do not say which role can open Custom Code, so we confirm that in your dashboard before quoting, and Wix says Custom Code needs a published site with a connected domain. We name the exact role and any seat or plan charge in the quote before you invite anyone; those charges are yours. You can remove our access at any time. No passwords or payment details go by ordinary email, and your authorised account holder publishes the final change.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “builder-custom-code-embed-breaks-page” as the subject.