The HubSpot WordPress plugin is worth considering when your website generates enquiries that somebody needs to follow up in HubSpot CRM. Its value is the connection between the enquiry and the customer record. Installing it is only the first step: you still need to choose a form method, check what gets captured and decide who handles each lead.
Our recommendation is to connect one useful enquiry form first. Expand after you have verified the complete journey from submission to response. A website covered in forms is less useful than one form whose enquiries consistently reach the right person.
Table of Contents
What the plugin actually adds
The official HubSpot plugin on WordPress.org brings forms, live chat and other HubSpot tools into the WordPress environment. Check that HubSpot is the listed developer when choosing it.
The plugin also installs HubSpot’s website tracking code. However, a tracking code is separate from a visible form: installing it does not automatically place a new enquiry form on your pages. HubSpot’s tracking-code documentation distinguishes form submissions from the analytics that depend on that code. Avoid adding another copy through your theme or tag manager when the plugin already supplies it.
The plugin itself is free; advanced HubSpot features can require a paid subscription. Evaluate the eventual workflow, including follow-up automation and reporting, rather than assuming every tool visible in the account is included indefinitely. Our HubSpot free-versus-paid guide for startups explains how to approach that decision.
Before installation: permissions and hosting
HubSpot’s installation guide requires a WordPress administrator and a HubSpot Super Admin. Check the current WordPress version requirements on the plugin listing, take a recoverable backup and identify the correct HubSpot account before connecting.
WordPress.com users should check the hosting provider’s current rules. WordPress.com now allows plugin installation on all paid plans, including Personal and Premium. That contradicts the older Business-only wording still present in HubSpot’s guide. Plugin installation eligibility and compatibility with your specific site are separate checks.
In WordPress, go to Plugins, add the official HubSpot plugin, install and activate it, then use the HubSpot menu to connect your account. If you manage several businesses or client portals, verify the selected account before proceeding. HubSpot says multisite installations need activation for each site separately.
Choose how enquiries will reach HubSpot
| Method | When to consider it | What to verify |
|---|---|---|
| HubSpot form | You want to manage the form in HubSpot | Editor compatibility, embedding and CRM properties |
| Existing form with automatic capture | You want to retain a simple WordPress form | Supported HTML structure and successful capture |
| Form provider’s direct integration | Your existing form has more complex behaviour | Provider support, field mapping, cost and error handling |
Choose one route deliberately. If several integrations process the same submission, troubleshooting becomes harder: you may not know which route created a record or changed a field.
Using a HubSpot form: check the editor first
HubSpot’s WordPress form instructions cover legacy forms and currently warn that updated-editor forms cannot be embedded on WordPress pages or posts. Its newer external-site form guide provides updated-form embed code, but does not explicitly resolve compatibility with the WordPress form block.
For an existing legacy form, use the documented block or shortcode route. For an updated-editor form, confirm the supported WordPress method before committing to an embed. A standalone form share link, documented in the external-site guide, offers another way to collect enquiries while you resolve embedding. For any embedded form, add the site domain to HubSpot’s tracking settings; otherwise submissions can be marked as spam.
Keeping an existing WordPress form
HubSpot’s automatic non-HubSpot form capture needs the tracking code and the collection setting enabled. It expects a static HTML form present when the page loads, with an email-type field and standard submit input. Iframes, dynamically inserted forms and JavaScript-driven submission behaviour can prevent capture.
There are further limits. Hidden fields are not collected, and automatic contact-property mapping supports single-line text properties. A failed validation attempt can produce a partial submission before the visitor successfully submits. Submissions sharing a browser cookie can also be associated with the same contact, even when different email addresses are entered.
These details matter for shared reception devices, complex quote forms and conditional questions. Treat automatic capture as something to verify against your actual form, not as a promise that every WordPress form plugin integrates completely.
Test the enquiry, not just the connection
Illustrative example: a small consultancy wants project enquiries from a WordPress services page. Its essential information is the person’s email, company, project type and requested start date. The test should prove that a colleague can understand and answer the enquiry without searching several systems.
- Submit a clearly labelled test enquiry from the public page using a test address you control.
- Check that it appears in HubSpot and that the intended properties contain the correct values.
- Verify the person responsible receives the notification or sees the enquiry in the agreed working view.
- Test an incomplete form, then correct it and submit again. Check whether partial entries affect the workflow.
- Repeat on mobile and through the site’s normal cookie choices. Record any difference in submission capture and analytics.
- Remove test data when finished and document who owns future checks.
HubSpot’s non-HubSpot forms FAQ says a form appears in the forms index only after its first captured submission. It also explains that forms sharing CSS identifiers can be grouped together. If two separate enquiry pages seem to produce one form entry, check those identifiers before rebuilding the connection.
Decide what happens after capture
Set a response target and name an owner before increasing traffic. For the consultancy example, a daily review and a clear next action may be sufficient initially. More elaborate automation is useful only when it removes a known delay or repeated task.
Review the information you actually need, the site’s privacy and cookie setup, and which contacts should receive marketing. A request for a project quotation is a different interaction from a newsletter signup; keep those intentions clear in the form and in your process.
Measure successful enquiries and timely responses rather than the number of tools enabled. If you are still choosing the wider acquisition process, our lead generation tools guide helps put forms in context. The plugin earns its place when it reliably helps your team act on a real enquiry.
Product details checked against official documentation on 9 September 2026. This guide uses published capabilities and illustrative workflows to support your evaluation.
