HubSpot: CRM, Content & Business Platform

HubSpot’s Smart CRM, Content Hub, marketing, sales, service, data, revenue and agent tools explained, including the role of its website CMS.

Updated 8 September 2026

What HubSpot’s CMS is used for

HubSpot’s CMS connects website content, lead collection and analytics with its CRM. It is designed to let marketers create and manage pages within a wider business system. Developers build the themes, templates and modules that define what editors can assemble.

For example, a campaign team could publish related landing pages using a shared set of modules. The design stays consistent while editors change the campaign-specific copy and offer.

HubL templates and editable modules

HubL is HubSpot’s server-side templating language. Modules expose editable fields within templates, separating the page builder’s controls from the implementation underneath. HubSpot also documents React-based module development.

The most useful module is not always the most configurable one. A testimonial module with clear required fields can be easier to reuse than a generic block with dozens of unrelated controls.

The broader HubSpot customer platform

HubSpot combines Smart CRM with product hubs for different business teams. Marketing Hub supports marketing automation, Sales Hub supports sales work, Service Hub supports customer service, and Content Hub covers content marketing. Data Hub addresses data management; Revenue Hub covers CPQ, billing and payments. Agent Hub is the central place for building and managing AI agents across the platform.

A website is one entry point into that system. A visitor’s form submission can become a CRM contact used by marketing, sales and support workflows. Seeing a HubSpot asset on a webpage does not establish that the website itself is hosted on HubSpot or that every hub is enabled.

Planning a CRM-connected website

Map what happens after a visitor submits a form, not just how the form looks. Content, contact records and follow-up workflows need consistent ownership and naming.

Check plan-specific requirements for features such as membership content and server-side extensions. A HubSpot script embedded on another host does not mean that the entire website is built with HubSpot’s CMS.

How DNSTrace.dev detects HubSpot

Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.

js.hs-scripts.com in markup — The HubSpot tracking script, loaded from a per-portal path.
hs-banner.com in markup — The HubSpot cookie banner and consent script.
CNAME targets under hs-sites.com — The hostname a HubSpot-hosted domain is pointed at.

What a detection proves

The page loads HubSpot's platform scripts, and where a HubSpot hostname also serves the document, that HubSpot is hosting the page.

What it does not prove

Whether HubSpot hosts the whole site. The tracking script is very commonly embedded on sites built on something else entirely, so a script match alone is a marketing-stack signal rather than a hosting signal.

Common questions about HubSpot

Is using HubSpot forms the same as hosting a site on HubSpot?

No. A website can embed HubSpot forms or tracking while its pages are hosted elsewhere. CMS hosting and integration with HubSpot are separate arrangements.

Does the HubSpot script mean the site runs on HubSpot?

Not on its own. The tracking script is embedded on sites built with any CMS. Hosting is indicated when HubSpot also serves the document itself.

How is that distinction reported?

DNSTrace.dev reports the detected stack and the delivery platform as separate layers, so a HubSpot script on a WordPress site shows up as exactly that.

Content management system