HubSpot CMS

What Is HubSpot CMS?

HubSpot CMS, now marketed as Content Hub, is a fully hosted content management system built directly on top of HubSpot's CRM and marketing platform. Rather than being a standalone website tool that you later wire into other software, it begins life connected to a contact database, an email engine, a forms system, and analytics, so the website and the rest of a company's go-to-market stack share the same underlying records from day one.

That integration is the entire point of the product. A page built in HubSpot CMS can read from and write to the same CRM that the sales and marketing teams use, which means content can be personalized to a known visitor, a form submission can immediately create or update a contact, and a marketer can see how a specific page contributed to a pipeline without exporting data between systems. For organizations that have standardized on HubSpot for marketing automation and customer relationship management, putting the website on the same platform removes a long list of integration headaches.

HubSpot CMS is a software-as-a-service product, not a self-hosted application and not a browser extension or plugin you add to another CMS. Your pages, templates, content, and the CRM data behind them all live inside HubSpot's infrastructure, and the public site is served from HubSpot's hosting and content delivery network. Because the platform serves pages and assets from a recognizable set of HubSpot-owned domains, it tends to leave clear fingerprints that make it straightforward to identify from the outside.

It helps to frame who HubSpot CMS is for. The platform is aimed squarely at marketing teams and the businesses that run their entire funnel on HubSpot, rather than at developers seeking maximum architectural freedom or at hobbyists wanting the cheapest possible blog. The people who get the most out of it are marketers who want to launch landing pages, run A/B tests, personalize content, and tie every interaction back to a contact record without filing a ticket with engineering for each change. That positioning explains many of the product's decisions, from its drag-and-drop editing experience to the way personalization and conversion tooling are baked into the core rather than added through third-party services.

How HubSpot CMS Works

At the core of HubSpot CMS is a module-based development model. Developers build reusable modules, self-contained blocks of HTML, CSS, and JavaScript, and assemble them into templates and themes. Marketers then compose pages by dragging those modules onto a layout and editing their content in place, without touching code. This separation lets a developer establish a design system once and lets the marketing team operate it indefinitely without breaking the layout.

The templating layer uses HubL, HubSpot's own templating language, which is based on the well-known Jinjava engine. HubL lets templates pull in dynamic data, loop over content, and, crucially, reference CRM properties so that what a visitor sees can change based on who they are. For logic that needs to run on the server, HubSpot CMS supports serverless functions, allowing developers to handle form processing, call external APIs, or run custom business logic without managing their own servers.

The defining capability is CRM-powered personalization. Because the website shares a database with the CRM, a page can display different content depending on a visitor's lifecycle stage, industry, company size, or past behavior, all configured through smart content rules rather than custom code. A returning lead who has already downloaded an ebook can be shown a different call to action than a first-time visitor, and every interaction is logged against the contact's timeline.

When a request arrives, HubSpot resolves the page, applies any smart-content and personalization rules, renders the HubL templates with the appropriate CRM and content data, and serves the result from its CDN with SSL and asset optimization handled automatically. Forms submitted on the page flow straight into the CRM, where they can trigger workflows, lead scoring, and sales notifications. This closed loop, from page view to form fill to CRM record to automated follow-up, is what HubSpot CMS is built to deliver.

The marketing toolset wrapped around the CMS is extensive and tightly coupled to the content. Built-in A/B and adaptive testing let teams optimize pages against real conversion data, SEO recommendations surface on-page improvements as content is written, and analytics attribute traffic, conversions, and revenue to specific pages and campaigns. Blog posts, landing pages, and standard website pages all draw on the same CRM enrichment and automation triggers, so the entire site behaves as one connected marketing surface rather than a collection of disconnected pages.

A useful way to picture the workflow is to follow a campaign end to end. A developer or agency sets up a theme with a library of branded modules. A marketer builds a landing page from those modules, adds a form, and sets up smart content so that visitors from a particular industry see tailored messaging. When the page goes live, every submission creates a contact, enrolls that contact in a nurture workflow, and notifies a salesperson if the lead is hot. The marketer then runs an A/B test on the headline, watches conversion data accumulate in the same dashboard that tracks revenue, and iterates, all without leaving HubSpot. That self-service, closed-loop experience is the reason HubSpot-centric organizations adopt the CMS.

How to Tell if a Website Uses HubSpot CMS

HubSpot CMS leaves a number of dependable fingerprints. Because StackOptic analyzes a URL from the server side, it looks at the same signals you can check by hand with browser tools, curl, or a detection extension.

HubSpot CDN and hosting domains. The strongest signals are HubSpot's own asset and hosting domains. Sites built on the CMS commonly serve files from hs-sites.com and store uploaded media and rendered assets on hubspotusercontent domains (such as the numbered *.hubspotusercontent-na1.net and *.hs-sites.com variants). URLs pointing at these domains are a strong indicator of HubSpot even when the page itself runs on a custom domain.

HubSpot forms. HubSpot's form embed loads from hsforms.net (and related js.hsforms.net / forms.hsforms.com endpoints) and produces markup with hs-form class names. A form sourced from hsforms is a classic HubSpot tell, and on a CMS site it usually means the whole platform is HubSpot.

hs- and hbspt markers. HubSpot prefixes many of its classes, identifiers, and global objects with hs-, and its JavaScript exposes an hbspt global object used to create forms and other embeds. Seeing hs- class names throughout the markup or an hbspt reference in the source points firmly at HubSpot.

Tracking script. Most HubSpot sites load the analytics tracker from js.hs-scripts.com (the *.js file is named after the HubSpot portal ID). This script powers HubSpot's visitor analytics and is frequently present alongside the CMS.

Generator meta tag. Many HubSpot CMS pages emit a <meta name="generator" content="HubSpot"> tag in the <head>, an easy confirmation in the page source.

Here is how to check each signal yourself:

Method	What to do	What HubSpot reveals
View Source	Open the page, right-click, "View Page Source"	Generator meta, hs- class names, hbspt references, links to hs-sites.com
Browser DevTools	Inspect Elements and the Network tab	Requests to hubspotusercontent, hsforms.net, and js.hs-scripts.com
curl -s	Run curl -s https://example.com and grep the HTML	Asset URLs and script tags pointing at HubSpot domains
Wappalyzer	Run the extension on the live page	Identifies "HubSpot CMS Hub" under CMS
BuiltWith	Look up the domain	Current and historical HubSpot detection plus hosting profile

A quick command-line check is curl -s https://example.com | grep -i "hsforms\|hs-sites\|hubspotusercontent". A match strongly suggests HubSpot. For a broader methodology, see our guides on how to tell what CMS a website is using and how to find out what technology a website uses.

It is worth noting how these signals behave on production sites. Most HubSpot CMS sites run on a custom domain, so the absence of an hs-sites.com address in the browser bar does not rule HubSpot out. The asset domains, form endpoints, and tracking script travel with the published site regardless of the domain, which is why they are the most dependable tells. Occasionally a team will strip the generator meta tag, but the hubspotusercontent asset URLs, the hsforms embed, and the hbspt global are hard to remove because the site genuinely relies on them. Combining several signals at once produces a confident verdict, and server-side analysis is especially valuable here because it fetches the unmodified HTML directly, without the noise a browser adds by executing scripts and rewriting the DOM.

Key Features

• CRM-powered personalization. Smart content rules tailor pages to a visitor's lifecycle stage, industry, or behavior using shared CRM data, with no custom code.
• Drag-and-drop editing. Marketers compose and edit pages from developer-built modules without breaking the underlying design.
• HubL templating and serverless functions. A flexible templating language plus serverless functions for custom logic and integrations.
• Built-in marketing tools. A/B and adaptive testing, SEO recommendations, and conversion analytics tied directly to campaigns.
• Native forms and lead capture. Forms flow straight into the CRM, triggering workflows, lead scoring, and sales alerts.
• Managed hosting and security. Global CDN, automatic SSL, a web application firewall, and threat monitoring included.
• Unified reporting. Page performance attributed to traffic, conversions, and revenue in the same platform as the rest of marketing.

Pros and Cons

Pros

• Tightest possible integration between website content, the CRM, and marketing automation.
• Powerful personalization and conversion tooling built in rather than assembled from plugins.
• Fully managed hosting, security, and CDN remove infrastructure work.
• Marketers can operate the site independently once developers set up the theme.

Cons

• Pricing scales with the marketing platform and can be expensive compared with open-source options.
• Less architectural freedom than a headless or self-hosted CMS; you work within HubSpot's model.
• Greatest value only materializes for organizations already invested in the HubSpot ecosystem.
• Migrating away later means re-platforming content and rebuilding integrations elsewhere.

HubSpot CMS vs Alternatives

HubSpot CMS sits at the intersection of website management and marketing automation. The table below compares it with common alternatives.

Platform	Approach	CRM/marketing integration	Best for
HubSpot CMS	Hosted CMS on top of a CRM	Native, deep	Marketing teams running their funnel on HubSpot
WordPress	Self-hosted PHP CMS with plugins	Via plugins and connectors	Content-heavy sites wanting a vast ecosystem
Webflow	Visual builder with a hosted CMS	Via integrations	Design-led marketing sites
Contentful	API-first headless CMS	Via custom integration	Omnichannel product and content teams
Squarespace	Template-first hosted builder	Limited, mostly native commerce	Small businesses wanting polished defaults

If a site turns out not to be HubSpot, the same techniques identify the real platform; compare HubSpot with an API-first option like Prismic to see how a marketing-suite CMS differs from a developer-focused headless one. For lead-qualification context, our guide on what technographics are and how to use tech-stack data to qualify leads explains why detecting HubSpot matters commercially.

Use Cases

HubSpot CMS is most at home for marketing-driven websites at companies that already run HubSpot for CRM and automation. Inbound marketing teams use it to launch landing pages, gate content behind forms, and personalize the experience for known contacts, all while keeping every interaction attributed in one system.

It also suits B2B companies that want their website, blog, and campaign pages to share a single source of truth with sales, agencies that manage marketing and web presence for HubSpot-using clients, and growth teams that run frequent A/B tests and need conversion data tied to revenue. For competitive and market research, identifying HubSpot CMS is a strong signal that an organization invests in inbound marketing and marketing operations.

Consider a few concrete scenarios. A mid-market software company might run its entire marketing site on HubSpot CMS so that every demo request instantly becomes a scored contact routed to the right sales rep. A professional-services firm might use personalization to show different case studies to visitors from different industries, drawing on CRM data the sales team already maintains. An agency might standardize its HubSpot clients on the CMS to deliver landing pages and nurture campaigns from one place. The common thread is a business that treats its website as a lead-generation engine wired directly into its revenue operations.

From a sales-intelligence perspective, detecting HubSpot CMS on a prospect's site is meaningful in its own right. It indicates the organization is committed to the HubSpot ecosystem and to inbound marketing, which is valuable qualification context for vendors selling complementary marketing, sales, or data tools. Surfacing that signal automatically across many domains, rather than inspecting each site by hand, is exactly the kind of insight a technology-detection scan delivers in seconds.

Frequently Asked Questions

Is HubSpot CMS the same as Content Hub?

Yes. HubSpot rebranded its CMS product as Content Hub as part of consolidating its platform into a set of "Hubs." The underlying capabilities, hosted pages, drag-and-drop editing, HubL templating, CRM-powered personalization, and built-in marketing tools, are the same product many people still refer to as HubSpot CMS or CMS Hub. Detection signals such as the HubSpot asset domains and form embeds remain the same regardless of the name.

How can I tell if a site uses HubSpot CMS for free?

View the page source and look for hs- class names, an hbspt reference, a <meta name="generator" content="HubSpot"> tag, or asset and form URLs pointing at hs-sites.com, hubspotusercontent, or hsforms.net. Free tools like Wappalyzer and BuiltWith confirm it, and a single curl -s URL | grep hsforms command works from any terminal. Because the asset and form domains travel with the site, they remain reliable even on a custom domain.

Does HubSpot CMS host the website, or does it run on my own server?

HubSpot CMS is fully hosted by HubSpot. Your pages, templates, content, and the CRM data behind them all live inside HubSpot's infrastructure, and the public site is served from HubSpot's CDN with SSL and security handled for you. This is different from a self-hosted system like WordPress or Strapi, where you run the application on your own servers. The trade-off is less infrastructure work in exchange for operating within HubSpot's platform.

Why do HubSpot pages load files from hubspotusercontent domains?

hubspotusercontent domains (and hs-sites.com) are HubSpot's content delivery and asset-hosting infrastructure. Uploaded images, files, and rendered page assets are served from these domains for speed and reliability, even when the page itself runs on your custom domain. Spotting asset URLs that point at hubspotusercontent is one of the most reliable ways to recognize a HubSpot-hosted site from the outside.

Is HubSpot CMS good for SEO?

HubSpot CMS includes solid SEO foundations: control over title tags, meta descriptions, headings, and canonical URLs, automatic sitemaps, and on-page SEO recommendations as you write. Pages are served from a CDN with SSL, which supports good performance. As with any platform, real-world results depend more on content quality, site architecture, and ongoing optimization than on the CMS itself, but HubSpot gives marketers the controls they need without custom development.

Want to detect HubSpot CMS and the rest of a site's stack automatically? Run any URL through StackOptic at https://stackoptic.com.