HubSpot's CMS - rebranded as Content Hub in 2024 - is not a general-purpose content management system. It is a CRM-native website platform: built to run on the same contact database as HubSpot's marketing, sales, and service tools, designed to give marketers control over content publishing without developer dependency, and optimised for the specific use cases where website and CRM data need to work together in real time.
For B2B teams that are already invested in HubSpot's platform, Content Hub has a compelling value proposition: forms that write directly to the CRM without integration, personalisation tokens that use contact properties without custom code, blog management that integrates with HubSpot's SEO and content strategy tools, and landing pages that connect natively to workflows, lead scoring, and attribution reporting.
For teams evaluating website platforms from scratch, the picture is more nuanced. Content Hub's marketer-friendly design comes with real constraints on design system depth and developer flexibility. Understanding those constraints clearly - and knowing when they matter and when they do not - is the prerequisite for making a good platform decision. For the foundational CMS-vs-CRM distinction, see our CRM vs CMS guide.
What HubSpot CMS / Content Hub Is
Content Hub is HubSpot's website platform, included in the HubSpot product suite and available as a standalone product. It hosts and delivers website content - pages, blog posts, landing pages, and knowledge base articles - through HubSpot's managed infrastructure, including global CDN, SSL, and automatic security updates.
The 2024 rebrand from 'HubSpot CMS Hub' to 'Content Hub' reflected HubSpot's expansion of the product beyond traditional web pages - adding AI content tools, content remix (repurposing content into different formats), podcasts, video hosting, and member-gated content. The underlying website platform technology remained the same. When this guide refers to 'Content Hub,' it means the full current product. (Source: HubSpot Content Hub overview: hubspot.com/products/cms)
Content Hub Tiers in 2026
Content Hub is available at three tiers - Starter, Professional, and Enterprise - either as a standalone purchase or bundled in HubSpot's Marketing Hub or CRM Suite plans:
- Starter (~$20/mo): Basic CMS features - hosted website, blog, landing pages, forms, live chat integration. No A/B testing, no smart content (personalisation), no SEO recommendations tool. Appropriate for very early-stage companies or simple websites that primarily need HubSpot forms and tracking.
- Professional (~$400/mo for Content Hub standalone, or included in Marketing Hub Pro at ~$800/mo): Full CMS capabilities - A/B testing on pages and CTAs, smart content (personalisation rules), SEO recommendations, content strategy tool, custom reporting. This is the tier where Content Hub becomes genuinely competitive as a marketing platform.
- Enterprise (~$1,200/mo for Content Hub standalone): Adds serverless functions, adaptive testing (multi-variate), memberships (gated content), multilingual content management, and custom CDN configuration. Appropriate for larger B2B organisations with complex content requirements or multiple brand sites.
Pricing verified at hubspot.com/pricing, mid-2026. Prices change; verify current tiers before purchasing.
The Architecture: Themes, Templates, Modules, and HubL
HubSpot's website architecture differs from WordPress's plugin model and Webflow's visual canvas. Understanding the architecture is essential for setting realistic expectations about what marketers can do independently versus what requires developer work.
Themes are the top-level design system for a HubSpot website - the collection of templates, modules, CSS, and JavaScript that define the visual language of the site. HubSpot's Marketplace includes free and paid themes; teams can also build custom themes. The theme determines what is visually possible across the site.
Templates are the layout structures for individual page types - homepage, blog post, landing page, about page. Each template defines which areas of the page a marketer can edit and which are fixed. Creating a new template type from scratch requires a developer; editing content within an existing template is fully marketer-controlled.
Modules are the reusable content components that marketers drag onto page sections - rich text blocks, image + text, video embed, testimonial, pricing cards, FAQ accordion, form embed. Modules define what is available in the editor. A module that does not exist cannot be added to a page without a developer building it first.
HubL is HubSpot's templating language - a superset of Jinja2 that developers use to build templates and modules. It enables dynamic content (pulling contact properties, list memberships, or CRM data into page content), conditional logic, and loops. Marketers do not write HubL; developers use it to build the infrastructure marketers work within.
Marketer vs Developer Capabilities: What Each Team Can Do
The most common miscommunication when evaluating Content Hub is the assumption that 'marketer-friendly CMS' means marketers can do anything without developer involvement. That is not accurate. Content Hub gives marketers significant and genuine independence within a well-built theme - but the theme itself must be built first, and extending it requires developer work.
The practical implication: for a site running on a well-built HubSpot theme with a comprehensive module library, marketers can launch new pages, write and publish blog posts, create landing pages, run A/B tests, configure personalisation rules, manage forms, and update SEO metadata entirely without developer involvement. The constraint is that every new page type, every new module type, and every design-system-level change requires developer work. Teams that understand this boundary before implementation are better positioned to build the theme correctly from the start - and avoid the friction of discovering limitations mid-campaign.
Building Themes and Modules on Content Hub
Starting with a Marketplace Theme vs Custom Build
HubSpot's Theme Marketplace includes free and paid themes from third-party developers and HubSpot's own design team. Marketplace themes are a legitimate starting point for teams with limited development resource or tight timelines - they provide a working module library and page template set out of the box. The trade-offs: limited design differentiation (any team can buy the same theme), less precise alignment with brand guidelines, and a module library that may not cover every content type the team needs.
A custom theme built by a HubSpot developer starts from HubSpot's default theme scaffold and builds the design system, module library, and template set to the team's exact requirements. This is the right approach for B2B brands where design consistency, brand differentiation, and a complete module library are requirements - not nice-to-haves. Custom theme development typically takes 6–12 weeks depending on design system complexity.
Designing a Module Library for Marketer Self-Service
The module library - the set of reusable content components available to editors - is the most important design decision in a HubSpot implementation. A well-designed module library gives marketers everything they need to build any page type without developer involvement. A poorly designed one leaves marketers constantly requesting new modules for content that should have been anticipated.
The module design principles that produce genuine marketer independence:
- Build for the content, not the design. Modules should be defined by the type of content they contain (image + headline + text + CTA button) not by the visual design they produce. A single 'feature block' module that allows configuration of layout, background colour, and text alignment serves more use cases than five separate layout-specific modules.
- Expose configuration options, not code. Module fields (text fields, image selectors, colour pickers, toggle switches for layout options) give marketers configuration flexibility without access to the underlying CSS. A module that allows marketers to toggle between left-aligned and right-aligned image layouts removes a category of developer requests entirely.
- Include a rich text module with style controls. Every page needs a flexible rich text area. The rich text module's style options (heading sizes, text colours, link styles) should match the brand design system so marketers do not produce off-brand content when writing freely.
- Build a comprehensive form module. Forms are the most conversion-critical element on most B2B websites. A form module that allows marketers to select any HubSpot form, configure the submit action (redirect vs inline thank-you), and set the surrounding layout context without developer involvement removes a major operational dependency.
The HubSpot Content Editor Experience
The HubSpot page editor is a drag-and-drop interface where marketers add, reorder, and configure modules within the template's defined layout sections. Each module surfaces a field panel on the right side of the editor - text inputs, image selectors, dropdowns, and toggles - that controls the module's content and configuration without exposing HTML or CSS.
The editor experience in 2026 has improved significantly from earlier versions. Inline editing (clicking directly on text in the page preview to edit it), global content (header and footer elements managed once and applied site-wide), and the flexible sections model (allowing marketers to create multi-column layouts without developer work) make day-to-day content editing genuinely fast for trained users.
The limitation that experienced web editors notice: HubSpot's editor is not pixel-precise. A marketer who wants a specific spacing adjustment between two elements, or a precise alignment change within a module, will need to request a CSS change unless the module's field panel exposes those configuration options. Teams migrating from Webflow's canvas editor - where any visual property can be adjusted visually by any trained editor - find HubSpot's editor more structured and less flexible.
Migration Paths to HubSpot Content Hub
Migration from an existing CMS to HubSpot Content Hub is a website rebuild project, not a content import. The visual design, template architecture, and module library must be rebuilt in HubSpot's theme system. Content - blog posts, landing pages, standard pages - can be migrated with varying degrees of automation depending on the source platform. SEO continuity (URL structure, redirects, meta data, internal links) requires careful planning. See our CMS migration SEO guide for the full SEO framework, and our website redesign SEO checklist for the pre-cutover audit process.
Migrating from WordPress
WordPress is the most common source platform for HubSpot migrations. HubSpot provides a WordPress migration plugin that imports blog posts, pages, and images into HubSpot automatically. The import covers content but not design - templates and modules must still be rebuilt in HubSpot's theme system.
The WordPress-to-HubSpot migration considerations that catch teams by surprise:
- Plugin functionality has no direct equivalent. WordPress plugins that handle SEO (RankMath, Yoast), popups (OptinMonster), cookie consent (CookieYes), and social sharing must be replaced with HubSpot-native tools (for SEO and popups) or third-party embeds (for cookie consent and social sharing). Audit every active plugin before starting the migration and confirm the HubSpot replacement before removing the WordPress version.
- Custom post types need content modelling decisions. WordPress custom post types (resources, case studies, team members, product listings) need to be replicated in HubSpot's content type system or built as HubDB tables (HubSpot's structured data layer). This is a design decision, not a technical limitation - but it requires planning before the migration begins.
- ACF and custom field data requires custom handling. Data stored in Advanced Custom Fields (ACF) or similar WordPress plugins does not export cleanly to HubSpot's content model. This data needs to be mapped to HubDB tables or HubSpot CMS properties before it can be used in HubSpot templates.
Migrating from Webflow
Webflow to HubSpot migrations are less common than WordPress migrations, but they do happen - typically when a B2B team has been using Webflow for the website and HubSpot for CRM, and wants to consolidate into a single platform for unified tracking, forms, and personalisation. The migration considerations are the opposite of WordPress migrations: Webflow sites typically have more sophisticated design systems than the average WordPress site, which means the HubSpot theme rebuild requires more design and development investment to match the visual quality. For teams considering the reverse - running Webflow for the website and connecting it to HubSpot CRM rather than migrating to Content Hub - see our HubSpot Webflow integration guide for the integration architecture.
Migrating from Drupal, Sitecore, or Enterprise CMS
Migrations from enterprise CMS platforms (Drupal, Sitecore, Adobe Experience Manager, Episerver) to HubSpot Content Hub are less common in mid-market B2B and more common in cases where the enterprise CMS is being replaced by a more marketer-accessible system. These migrations are typically higher complexity: larger content libraries, more complex URL architectures, more sophisticated permissions and workflow requirements, and tighter CRM integration needs.
The key evaluation question before committing to an enterprise CMS migration: is HubSpot Enterprise Content Hub's feature set a step up or a step down from the existing platform for the specific use cases that matter? Enterprise CMS platforms often have capabilities (complex workflow approval, fine-grained user permissions, multi-site management, complex localisation) that HubSpot Enterprise supports in some cases but not all. A capability gap analysis before the project begins prevents expensive discoveries mid-implementation.
SEO and Personalisation: Content Hub's Key Strengths
SEO Capabilities in 2026
Content Hub's SEO tooling is more comprehensive than most CMS platforms offer natively - and this is one of the clearest arguments for the platform for teams where organic search is a primary acquisition channel.
Page-level SEO fields: Title, meta description, canonical URL, and Open Graph tags are accessible in the page editor for every page type - no plugin required, no developer needed.
Topic cluster and content strategy tool: HubSpot's content strategy tool (Marketing Hub Professional+) maps pillar pages and cluster content in a visual interface, surfacing internal linking opportunities and tracking organic performance per cluster. This is a genuinely useful tool for content marketing teams running topic cluster strategies - not just a cosmetic feature.
SEO recommendations: HubSpot's on-page SEO recommendations audit active pages for common issues - missing alt text, broken internal links, page speed warnings, missing meta descriptions - and surface them in a prioritised list without requiring an external SEO tool.
Page speed and Core Web Vitals: Content Hub's managed infrastructure and CDN provide a strong performance baseline. Page speed is affected by the quality of the theme build (CSS payload, JavaScript loading patterns, image optimisation) as much as by the platform - a well-built custom theme on HubSpot typically outperforms a heavily-plugged WordPress site on comparable infrastructure.
One limitation: schema markup (structured data for rich snippets) is not generated automatically by Content Hub and requires custom code in page templates. For B2B sites where schema types like FAQ, Article, BreadcrumbList, and Organization are important for search visibility, schema implementation is developer work. See our Webflow SEO services for how this compares to the SEO architecture on Webflow-built sites.
Smart Content and Personalisation
Smart content - serving different content to different visitors based on who they are - is one of Content Hub's clearest differentiators from standalone CMS platforms. Because Content Hub runs on the HubSpot CRM database, personalisation rules can reference any contact property without an integration:
- Lifecycle stage: Show a different homepage hero to known leads versus unknown visitors versus existing customers. A contact in the SQL lifecycle stage sees a 'speak to sales' CTA; a contact in the customer lifecycle stage sees a support resource.
- List membership: Contacts on a specific HubSpot list (e.g., members of a particular account segment, contacts who attended a webinar) see targeted content relevant to that segment when they return to the site.
- Country or language: Route visitors to language-specific content or show country-specific pricing or contact information based on the visitor's IP geolocation.
- Device type: Serve different module configurations or CTAs to mobile and desktop visitors without separate mobile pages.
Smart content is available at Content Hub Professional and Marketing Hub Professional. It requires that the visitor is a known contact in HubSpot - identified from a cookie set when they previously submitted a form or clicked a tracked link. Anonymous first-time visitors see the default content. This is not a limitation unique to HubSpot - all CRM-based personalisation requires prior contact identification - but it is worth understanding before designing a personalisation strategy.
HubDB: Structured Data for Marketers
HubDB is HubSpot's structured data layer - a database tool that allows marketers to build and manage structured content without writing SQL. It is used for content types that do not fit the standard blog/landing page model: team member directories, resource libraries, product comparison tables, event listings, office location pages, and case study databases.
A HubDB table works like a spreadsheet: columns are field types (text, image, URL, number, rich text, multi-select options), rows are individual entries (one row per team member, one row per resource), and the table's data can be pulled into any HubSpot page template via HubL. A developer builds the template that displays the HubDB data; a marketer manages the data itself - adding new rows, updating existing entries - entirely through HubSpot's interface.
HubDB is one of the features that most clearly illustrates Content Hub's positioning: it gives marketers genuine ownership of structured content that would require a developer to manage in most other CMS environments, within a framework that a developer set up once and that does not require ongoing developer involvement for routine content changes.
Limitations Worth Understanding Before Committing
Design system depth vs visual CMS tools. Webflow's visual canvas gives designers pixel-level control over every aspect of a site's visual presentation. HubSpot's module-based system is significantly more constrained - the visual design is determined at the module-build stage, and editors work within those constraints. For teams with strong brand and design requirements, or for agencies building sites with complex animation, micro-interaction, and layout precision, HubSpot's design ceiling is lower than Webflow's.
No native ecommerce beyond basic. Content Hub does not include ecommerce functionality beyond a basic shopping experience through HubSpot Payments. For B2B teams selling products online, or for any substantial ecommerce requirement, a dedicated ecommerce platform (Shopify, WooCommerce) connected to HubSpot CRM is the right architecture - not Content Hub as an ecommerce platform.
Serverless functions at Enterprise only. HubSpot's serverless functions - which allow custom server-side logic to run in response to page requests, form submissions, or API calls - are available at Content Hub Enterprise. Teams that need custom backend logic on a Professional-tier site have limited options: they can either upgrade to Enterprise or host the custom logic externally and connect it via API.
Headless delivery requires Enterprise. HubSpot's Content Delivery API - which allows content managed in HubSpot to be delivered to a custom frontend built in Next.js, React, or another framework - is available at Enterprise tier. Teams evaluating a headless architecture with HubSpot as the content management layer must budget for Enterprise pricing.
Marketplace theme quality is variable. Third-party themes in HubSpot's Marketplace range from excellent to poor. A poorly built Marketplace theme with excessive CSS, slow JavaScript, or an inflexible module library creates technical debt that is expensive to unpick later. If using a Marketplace theme, require a technical review of the theme's code quality and performance before purchasing.
Developer talent pool is smaller than WordPress. The pool of developers with HubSpot CMS and HubL expertise is smaller than the WordPress or Webflow developer communities. For teams that anticipate ongoing development work, confirm the availability of developer resource - internal or agency - before committing to the platform.
Platform Comparison: Content Hub vs Webflow vs WordPress vs Headless
The comparison most relevant to Belt Creative's clients: HubSpot Content Hub vs Webflow. For B2B teams that are deeply HubSpot-native - marketing, sales, and service all on HubSpot - Content Hub's unified architecture is a genuine advantage. For teams where design differentiation, developer flexibility, and performance are the primary website requirements, Webflow's visual canvas and code export capabilities frequently produce a better outcome. The two are not mutually exclusive: running Webflow as the website platform and HubSpot as the CRM and marketing automation platform is a widely used architecture. See our HubSpot Webflow integration guide for how to connect the two.
When to Choose HubSpot Content Hub
Content Hub is the right platform choice when:
- You are already on HubSpot Marketing Hub Professional or above. If Marketing Hub Professional is included in your HubSpot subscription, Content Hub Professional is frequently bundled or available at marginal additional cost. The integration benefit - forms, tracking, personalisation, and attribution all running natively - is compelling when the platform cost is already paid.
- Marketer self-service over design differentiation is the priority. Teams that need marketing to own content publishing, landing page creation, and A/B testing without developer dependency - and where the website's visual design does not need to be a primary brand differentiator - benefit from Content Hub's marketer-focused architecture.
- Personalisation at the contact level is a core use case. Smart content, powered by HubSpot CRM data without custom integration, is one of the clearest advantages Content Hub has over alternative platforms. If the ability to personalise website content based on contact properties - lifecycle stage, industry, account status - is a genuine priority, not an aspirational feature, Content Hub makes this straightforward.
- You need a unified view of marketing activity and website performance. HubSpot's attribution reporting connects website page views, form submissions, blog posts, CTAs, and ad interactions to a single contact record. This unified attribution is only available natively when the website runs on Content Hub. Teams that need to answer 'which website content influenced this deal?' without a third-party analytics integration benefit directly from this unification.
When to Consider Webflow or a Headless Architecture Instead
- Design is a competitive differentiator. For agencies, design studios, or B2B brands where the website's visual quality is a central part of the brand value proposition, Webflow's visual canvas, animation toolset, and design-code fidelity produce higher-quality outputs than HubSpot's module-based editor for most teams.
- You need full developer freedom. Custom backend logic, complex API integrations, dynamic server-side rendering, or architectural requirements beyond HubSpot's supported feature set are all better served by Webflow + custom code or a headless architecture.
- Your content is delivered to multiple channels. If the same content needs to power a website, a mobile app, a digital kiosk, and a sales enablement tool, a headless CMS (Contentful, Sanity, Hygraph) with HubSpot handling CRM and marketing automation is a more appropriate architecture than Content Hub.
- Your HubSpot investment is CRM-only. If the team uses HubSpot for CRM and sales but not for Marketing Hub, the integration benefit of Content Hub is diminished. In this case, a Webflow site connected to HubSpot CRM via the integration connector (see our HubSpot Webflow integration guide) achieves the critical integration (form data to CRM) at lower platform cost and higher design quality.
Work with Belt Creative
Belt Creative implements HubSpot and builds Webflow sites for B2B teams - including the platform evaluation, theme architecture, CRM integration, and migration planning that determines whether Content Hub or Webflow is the right fit for each team's specific requirements.
See our work for examples of both HubSpot and Webflow builds, or get in touch to discuss your website platform evaluation.
A Note on Sources
HubSpot Content Hub product overview: hubspot.com/products/cms. HubSpot developer documentation - CMS themes: developers.hubspot.com/docs/cms/building-blocks/themes. HubSpot pricing: hubspot.com/pricing. All pricing and feature information verified at official HubSpot documentation, mid-2026. HubSpot's product tiers and feature availability evolve frequently - verify current capability at hubspot.com/products/cms before making a platform decision.
Frequently Asked Questions
Do I Need a Developer to Use HubSpot CMS?
Not for day-to-day content management, publishing, or campaign work - but yes for initial setup and ongoing design system changes. A developer is required to build the theme, templates, and module library that marketers then use independently. Once that foundation is in place, marketers can publish pages, write blog posts, create landing pages, run A/B tests, configure smart content, and manage forms without developer involvement. Developer work is needed again when a new page type is required, a new module needs to be built, or design system elements need to change.
How Long Does a HubSpot CMS Migration Take?
For a standard B2B marketing site (under 50 pages, one blog, a handful of landing pages) migrating from WordPress: 6–10 weeks including design rebuild, content migration, SEO configuration, and testing. For larger or more complex sites (100+ pages, multiple content types, custom integrations): 12–20 weeks. The theme and module rebuild is typically the longest phase - content migration runs in parallel. DNS cutover should be planned for a low-traffic period after a thorough pre-launch audit.
How Does HubSpot CMS Compare to WordPress?
The primary differences: HubSpot CMS is a managed platform (no hosting, security, or plugin management overhead), integrates natively with HubSpot CRM, and gives marketers a more structured but less extensible editing environment. WordPress offers a larger developer ecosystem, more plugin options, and greater flexibility - but also more maintenance overhead and a less direct path to CRM integration. For B2B teams already on HubSpot, Content Hub's native integration removes the need for a separate CRM connector and eliminates form integration complexity.
How Does HubSpot CMS Compare to Webflow?
Webflow gives designers more visual control and gives developers more architectural freedom. HubSpot Content Hub gives marketers native CRM integration, smart content personalisation, and unified attribution without additional integration work. For teams where design quality and performance are primary, Webflow is typically the stronger choice. For teams where marketing self-service and CRM integration depth are primary, Content Hub is often preferred. Running Webflow for the website with HubSpot for CRM and marketing automation is a widely used architecture - see our HubSpot Webflow integration guide for how that setup works.
What Is HubDB and Do I Need It?
HubDB is HubSpot's structured data layer - a spreadsheet-like tool for managing structured content (team directories, resource libraries, event listings) that marketers manage directly and developers surface on the site via templates. Most B2B marketing sites need it for at least one content type that does not fit the standard page or blog post model. It is a genuinely useful feature for reducing developer dependency on structured content management.
Is HubSpot Content Hub Good for SEO?
Yes, particularly for teams running topic cluster content strategies. Content Hub's built-in SEO fields, content strategy tool, and SEO recommendations cover the most important on-page optimisation requirements without plugins. Page performance on HubSpot's CDN infrastructure is a strong baseline. The gap versus Webflow or a headless architecture is in developer-level SEO customisation - schema markup, advanced Core Web Vitals optimisation, and server-side rendering require more effort on HubSpot's platform. For a comparison of SEO capability across CMS platforms, see our CMS migration SEO guide.
Can I Run Multiple Sites on HubSpot Content Hub?
Yes. HubSpot Content Hub Professional supports up to three brand domains (three separate websites managed within one HubSpot portal). Enterprise supports up to 10 brand domains. For organisations managing more than three distinct brand websites, Enterprise tier or separate HubSpot portals are required. Each brand domain can have its own theme, templates, and module library, managed separately within the same HubSpot account.
What Is Smart Content and How Does It Work?
Smart content is HubSpot's name for rules-based website personalisation - serving different content to different visitors based on properties stored in the HubSpot CRM. A smart content rule can display different hero text, different CTAs, or different page sections to visitors in different lifecycle stages, different countries, or on different devices. Smart content applies only to visitors who are known HubSpot contacts (identified via cookie from a prior form submission or tracked email click). Anonymous visitors see the default content.
Sources: hubspot.com/products/cms; developers.hubspot.com/docs/cms; hubspot.com/pricing. All product capability and pricing data verified mid-2026. HubSpot's product evolves rapidly - verify current feature availability at official documentation before making platform decisions.
