How to Share HubSpot Forms on External Websites

Choose the sharing method based on the job

Start with the page experience and the operating process, rather than the feature that is easiest to click. Ask where the form should appear, how much control the website team has, and what should happen when someone submits it.

Platform integrations can be useful when a CMS provides a supported HubSpot connection, but an integration does not remove the need to validate the underlying CRM process. Confirm that the selected form, submission data, consent settings, and follow-up automation are the ones the business actually intends to use.

How to embed a HubSpot form on an external website

1. Open the form in HubSpot

Sign in to HubSpot and open the forms tool. Select the form you want to publish, then review its fields, submission settings, follow-up message, and any consent or privacy language before copying the code.

Use a form with a clear purpose. A form for a sales enquiry may need different fields and routing from a newsletter subscription or a support request. Reusing one form for unrelated processes can make reporting and ownership unclear.

2. Copy the generated embed code

Open the form’s sharing or embedding option and copy the complete snippet provided by HubSpot. The code commonly includes a JavaScript loader that retrieves the form from HubSpot when the external page loads.

Copy the code as provided. Do not remove individual attributes or rewrite the script unless the website developer understands the consequences. If the form is later changed in HubSpot, the embedded version can generally reflect those changes without requiring a new block of code, although the page should still be retested after significant edits.

3. Add the code to the external page

1. Open the page or template where the form should appear.
2. Insert a custom HTML, code, or embed block, depending on the website platform.
3. Paste the full HubSpot snippet into that block.
4. Save and publish the page.

On a custom-coded website, the developer may add the snippet to the relevant page template. On a CMS, the same task may use a custom HTML block, page builder module, or supported HubSpot integration. Avoid placing the code in a text editor that escapes or displays HTML as plain text.

4. Test the published form

Test the live page rather than relying only on the editor preview. Confirm that the form loads, labels and fields are readable, validation messages work, the confirmation experience is correct, and the page remains usable on a small screen.

Submit a controlled test record and check the result in HubSpot. Verify the contact or submission record, field values, consent status, source information, notifications, routing, and any workflow that should follow. Remove or clearly identify the test record afterwards so it does not distort reporting.

How to share a HubSpot form with a link

A shareable form page is useful when the external channel can accept a URL but cannot accept embedded code. Depending on the form type and current HubSpot account configuration, the sharing options may include a direct or standalone form link.

1. Open the form in HubSpot.
2. Review the fields, messages, consent wording, and follow-up settings.
3. Open the form’s sharing options and locate the available share or link option.
4. Copy the complete URL and open it in a private browser window to test it.
5. Use the link in an email, newsletter, social post, QR code, document, or website button.

A linked form is faster to publish, but it gives you less control over the surrounding page experience. The page may not match the external site’s navigation, typography, or conversion context. Use descriptive link text and explain what the visitor will receive after submitting.

For campaign reporting, decide how the link will be attributed before distributing it. A form submission may be recorded correctly in HubSpot while still being difficult to connect to a specific campaign if the surrounding link, page, or tracking setup is inconsistent.

Using integrations and website builders

Some website platforms offer a HubSpot integration, plugin, app, or native embed block. These options can be convenient because the website editor may allow a user to select a form without manually pasting code.

The exact setup depends on the platform and the permissions available in the HubSpot account. A typical process is to authenticate the connection, choose the form, place it on a page, and publish the change. Treat the integration as a publishing mechanism, not as proof that the full process works.

After publishing through an integration, test the same operational details as an embedded form. Check whether the correct form is displayed, whether the layout works on mobile, whether the form loads without console errors, and whether the submission reaches the intended HubSpot records and workflows.

External website tracking and consent considerations

Form capture, website analytics, and marketing attribution are related but separate concerns. An embedded form may create a submission in HubSpot, while page views and campaign attribution may depend on the tracking code, domain configuration, consent mechanism, and campaign setup used on the external site.

Confirm which domains are involved and whether the relevant HubSpot tracking and consent experience is configured for them. The exact requirements depend on your account, website architecture, audience, and applicable privacy obligations. Do not assume that adding a form automatically provides complete attribution or that a submission automatically proves marketing consent.

• Explain why the information is being collected.
• Use the appropriate consent or subscription settings for the purpose of the form.
• Check that required fields do not collect information unnecessarily.
• Test the experience when cookies or optional tracking are declined.
• Document which team owns changes to the form and its privacy wording.

Design the handoff behind the form

The most common failure is not that the form fails to load. It is that the submission enters HubSpot without a clear next action. Before publishing, define the business state created by the submission and the person or team responsible for moving it forward.

For example, a sales enquiry might create or update a contact, associate the submission with a company where possible, assign an owner, and create a follow-up task. A newsletter form may only need subscription status and source information. A support form may need a ticket or queue rather than a sales opportunity.

Keep the form’s fields aligned with that decision. If an automation needs a reliable value, use a controlled property rather than asking people to enter free text that must later be interpreted manually. Review required fields carefully: every required field adds friction and should support a clear operational need.

For larger implementations, HubSpot consulting can help connect form design with CRM properties, workflows, routing, and reporting. Broader CRM consulting may also be useful when the form is one part of a wider lead management process.

A practical launch checklist

Common mistakes when sharing HubSpot forms

Choosing a method without considering the user journey

An embed may be technically correct but poorly placed, while a standalone link may be fast but disconnected from the page context. Choose the method that supports the visitor’s next action.

Testing only whether the form appears

Visual loading is only the first test. A form can display correctly while sending incomplete data, assigning the wrong owner, or failing to trigger the intended notification.

Creating duplicate forms for minor page differences

Duplicate forms can fragment submissions and reporting. Before creating another form, check whether one controlled form with appropriate context or campaign attribution would be easier to govern.

Changing fields without reviewing dependencies

Field edits can affect workflows, lists, reports, routing, and downstream integrations. Treat a form change as a systems change when other processes depend on its data.

Sharing a HubSpot form is straightforward when the publishing method and the operational purpose are both clear. Embed the form when it belongs inside a page, use a share link when a destination URL is enough, and use an integration when it genuinely improves publishing control. In every case, test the full path from visitor input to CRM record, ownership, follow-up, and reporting.