HubSpot Content Hub: what is in it, how the tiers differ, and what it really costs

The renamed CMS Hub explained by job, by tier and by migration risk, so you can tell whether it fits your team.

Published by AI Knows Us · Updated 12 October 2026

HubSpot Content Hub is HubSpot's content management and content marketing product, the renamed and widened version of what used to be called CMS Hub. It hosts your website pages, blog, landing pages and knowledge base on HubSpot's own infrastructure, and it connects every page to the HubSpot CRM so content can change based on who is reading it. The 2024 rename came with a shift in scope: it is no longer only a place to build web pages, it now includes content production tools such as a brand voice setting, content remixing into other formats, podcast hosting and gated membership areas.

This page covers what is in the product, how the tiers differ, what the real cost drivers are and how to judge a migration. For the wider question of what to publish and why, see our guide to building a content marketing strategy.

What Content Hub actually is

Three things in one product.

  • A hosted CMS. Pages, blog posts, landing pages and a knowledge base, built from themes and modules in a drag and drop editor, served from HubSpot's CDN with SSL included. Developers work in HubL, HubSpot's templating language, with a local CLI for version controlled development.
  • A CRM connected delivery layer. Because the CMS and the CRM are the same system, a page can show different content to a known contact than to an anonymous visitor, with no tag manager, no plugin and no data sync. Smart content, dynamic personalisation and content partitioning all come from that single database.
  • A content production toolkit. Brand voice settings that keep generated drafts consistent, remix tools that turn one long asset into social posts and a newsletter, a case study generator, podcast hosting with transcripts, and memberships that put content behind a login tied to a CRM list.

What is inside it, grouped by job

JobWhat you get
Build and publishThemes, modules, drag and drop editor, blog, landing pages, knowledge base, multi language page variants
PersonaliseSmart content rules, CRM property tokens, dynamic pages driven by HubDB or custom objects, content partitioning by team
OptimiseOn page SEO recommendations, topic clusters, A/B testing, adaptive testing on higher tiers, Core Web Vitals reporting
ProduceBrand voice, content remix, case study generator, podcast hosting, assisted drafting inside the editor
Gate and segmentMemberships with CRM list based access, private content, single sign on options on Enterprise
ExtendHubL, serverless functions, web apps, GitHub integration, APIs, custom objects on Enterprise

How the tiers differ

HubSpot publishes the tier list and the current prices on its Content Hub pricing page, and the product overview sits at hubspot.com/products/content. Read both before you budget, because HubSpot revises its packaging regularly. The shape of the ladder stays stable even when the numbers move:

  • Free tools. A landing page builder and a small number of hosted pages on a HubSpot subdomain. Useful for a pilot, not for a company website.
  • Starter. Your own domain, the blog, basic SEO recommendations and the core editor. Fits a small site with one marketer and no developer.
  • Professional. The tier most companies actually buy. Adaptive testing, dynamic personalisation, content remix, podcast hosting, memberships, HubDB and serverless functions. This is where the CRM connection starts earning its keep.
  • Enterprise. Multiple root domains, content partitioning so regional teams only touch their own pages, custom objects, activity logging and web apps. Bought for governance as much as for features.

The choice between Starter and Professional is usually settled by one question: do you need a page to behave differently for a known contact? If yes, Professional. If no, Starter will carry you for a good while.

The real cost drivers

The licence is the visible number. Four other things move the total:

  • Marketing contacts. Several HubSpot features price against the number of contacts you market to. Content Hub itself is tier based, but personalisation only earns its fee if the CRM behind it is populated, and that population sits on a different line of the bill.
  • Theme and template work. A marketplace theme gets you live quickly. A design that matches an existing brand usually means custom modules in HubL, which is a developer project rather than a configuration task.
  • Migration of existing URLs. Content moves faster than redirects do. Budget the redirect map as a deliverable in its own right.
  • Integration with what you already run. If your product documentation, pricing engine or app lives elsewhere, decide early which paths stay off HubSpot and how navigation and analytics stitch across both.

Content Hub against WordPress and against a headless stack

Named fairly, because the three suit different companies.

  • WordPress wins on plugin choice, on developer availability and on cost at the low end. You own the hosting, the updates, the security and the performance work. Personalisation means a plugin plus a data pipe to your CRM.
  • Content Hub wins when marketing owns the site and the CRM is already HubSpot. Hosting, CDN, SSL, forms, analytics and personalisation arrive assembled. You accept HubL and HubSpot's release cycle in exchange.
  • A headless CMS with a custom front end wins when the site is a product surface rather than a marketing surface, with many templates, heavy component reuse and an engineering team that will own it.

A useful tiebreaker: count how many people will publish in a normal month and how many of them can read code. The more publishers and the fewer coders, the stronger the case for Content Hub.

Migrating onto it while keeping your search traffic

  • Export the full URL inventory first, from your crawler and from Search Console, and record current traffic and rankings per URL.
  • Decide the fate of every URL: move as is, merge, redesign or retire. Write the destination next to each one.
  • Build the 301 map from that list before launch, including trailing slash and letter case variants, and test it on staging.
  • Rebuild the templates so titles, headings, canonical tags, structured data and internal links survive the move. Templates generate most of this, so a template error multiplies across hundreds of pages.
  • Keep the old site reachable for one crawl cycle where you can, then submit the new sitemap and read the Page indexing report daily for two weeks.

Questions buyers ask

Is Content Hub the same thing as CMS Hub?

It is the same product line. HubSpot renamed CMS Hub to Content Hub in 2024 and added content production features to it. Existing CMS Hub customers moved onto the new naming, which is why documentation and third party articles still use both terms.

Can I keep my blog on WordPress and put only landing pages on HubSpot?

Yes, and plenty of companies do. Keep the split clean at directory level, give each system its own sitemap, and make sure navigation and analytics treat the two as one site so your reporting still adds up.

Does Content Hub handle technical SEO properly?

The basics come configured: clean URLs, editable titles and meta descriptions, canonical tags, automatic sitemaps, a CDN and SSL. Structured data beyond the defaults is a template job, so plan for a developer to add the blocks your content types need.

How many domains can I run?

Starter and Professional are built around one root domain with subdomains. Enterprise adds additional root domains, which is the usual reason a multi brand or multi country business moves up a tier.

What does content partitioning do?

It restricts which users can see and edit which assets. A regional team logs in and finds only its own pages, blog posts and lists. It is an Enterprise feature and it is bought for governance in large teams.

Is the drag and drop editor enough on its own?

For publishing inside an existing theme, yes, and that covers most weekly work. New page types, custom modules and anything that reads from HubDB or a custom object need a developer once, after which marketers reuse them freely.

After the migration, check the part the dashboard cannot see

Content Hub reports on visits, conversions and attributed contacts. Those reports describe people who reached your site. They say nothing about the people who asked an assistant to compare CMS options and left with a shortlist you were never on.

Buyers researching a platform like this do exactly that, and the assistant's shortlist leans on documentation, review sites and partner pages. Run your category question once, with no brand name in it, and see which vendors come back and from which sources. AI Knows Us repeats that check and logs the sources.

Read next

Or browse the whole archive.

See what AI says about you.

The first scan is free, it needs no account, and it asks the questions your buyers ask.

Free. No card. We ask 5 real buyer questions on 2 AI apps.

Already sure you want this? Join the waitlist. We open on 31 October 2026. It costs an email address. No card, and nothing is charged. Or talk to a person if you have a question first. Or read how we fix what it finds.