A layout problem with a functional impact
The client expected the HubSpot form inside the contact section. Instead, it appeared outside the intended layout. A form that is hard to find can interrupt enquiries even when the submission itself still works.
We checked the page structure and the scripts creating the form. Moving a visual container alone would not necessarily resolve code that rendered the form somewhere else.
Give the embed a clear destination
We placed the form inside the intended page container and adjusted the integration so the form rendered there. The implementation needed to match the form type and embed method in use.
HubSpot has different form tools and embed options. An example written for a legacy embed should not be assumed to apply unchanged to every current form.
Test loading as well as appearance
Check the published page, not only the editor preview. Test a fresh visit, a return visit and a smaller screen. Caching, deferred scripts and other custom code can affect when an embed is created.
Placement is only the first test. Submit an enquiry and confirm the expected confirmation, CRM record and notification. A neatly positioned form is not enough if the enquiry goes nowhere.
Keep the integration understandable
Record where the embed is installed and avoid adding multiple copies while troubleshooting. A clear implementation makes later theme or form changes easier to manage.
If a form has moved, disappeared or stopped submitting, send the affected page and a short description of what you see. We can then review the embed and the surrounding page together.
Further reading
Need a hand with something similar?
Tell us what you are trying to achieve or what is not working. We will help you work out the next step.
Explore the service Contact us
