In HubSpot, the Design Manager is your core environment for managing templates, custom modules, stylesheets, and other page assets. It is located under Marketing > Files and Templates > Design Tools andgoverns how your CMS content appears in the browser.
When your edits don’t show up on live pages, it usually means your working file isn’t the one being rendered, or something is getting stuck in the rendering pipeline. HubSpot pages often reference compiled or cached snapshots of templates and modules for performance reasons.
If those compiled copies aren’t refreshed properly after an update, your live content will continue displaying the old version.
Every save in the Design Manager should propagate to the content editor, and then, after publishing, to the live site. But in practice, stylesheet caching, module misalignment, and global content behaviors frequently delay or block that update cycle.
To spot and fix what’s going wrong, you need to understand how HubSpot’s CMS handles updates behind the scenes.
How It Works Under the Hood
The HubSpot Design Manager operates on a layered rendering system. Once you understand how your changes move through it, you can isolate where things break.
Here’s What Happens Step by Step:
Inputs:
- You edit a coded template, module, or stylesheet in Design Manager.
- You save or publish the changes.
Processing:
- HubSpot logs your code update and records the asset version.
- The CMS compiles the asset into an optimized, cacheable format.
- Any page linked to that asset relies on the compiled version for rendering.
Outputs:
- The live website pulls this compiled asset to display content.
- Caches on HubSpot’s side, the CDN, and your browser speed up delivery by re-using that compiled content.
Special Cases to Keep in Mind:
- If your live page uses a cloned template, any edit to the original won’t apply.
- Updates to global modules won’t appear until the module is explicitly re-published.
- Stylesheets might stay cached unless you force a refresh with a version string or clear local storage.
- Design Manager changes can also be blocked by mismatched theme settings or stale data in HubDB. Unless all components work in sync, your updates can slip through the cracks without warning.
Main Uses Inside HubSpot
Here’s where most CMS users encounter hidden update issues, and what to check when your edits don’t take effect.
Template and Theme Maintenance
Purpose: Design Manager is the main workspace for editing website and landing page templates. If changes aren’t reflected, your page might be using an old or cloned version.
Example: You add a new navigation link in a global header module, but the link never appears. A common culprit is a cloned header that didn’t get updated. Verify the active template’s module assignments inside Design Manager to fix this.
Custom Modules and Interactive Elements
Purpose: Design Manager is where developers tweak JavaScript behaviors, image displays, and design logic within custom modules.
Example: You adjust the CSS inside a product listing module to update button spacing. You save and preview the page, but nothing changes. Likely, the browser or CDN is still serving a cached version. Publishing the module and refreshing the page with a cache-busting parameter usually resolves this.
Global Content and HubDB Templates
Purpose: Edits to global footers, headers, or data-driven modules may run into syncing issues, especially with HubDB.
Example: Renaming a product category inside a HubDB table shows up in the CMS preview but not on the live site. This usually points to stale cache or outdated display modules. Re-publishing modules or triggering a full publish cycle flushes the outdated view.
Common Setup Errors and Wrong Assumptions
Editing a Cloned or Unused Template: Accidentally updating a test or backup template will not affect live content. Confirm the template currently assigned to your page under Page Settings.
Skipping Publish Changes in Modules: Edits made in custom or global modules aren’t pushed live unless you click “Publish Changes.” Saving alone won’t reflect updates.
Overlooking Browser or CDN Cache: HubSpot aggressively caches static assets. Force a refresh using a versioned URL (e.g., ?v=2) or clear your local browser cache if changes aren’t visible.
Incorrect Stylesheet Load Order: When multiple stylesheets are linked, HubSpot loads them in the order they appear. If an older stylesheet overrides your update, your changes appear ignored. Use Design Manager’s Linked Stylesheets tool to fix the hierarchy.
Missing Global Module Publishes: Global modules must be re-published after every edit. Failing to do so leaves stale versions visible on every page that includes them.
Step-by-Step Setup or Use Guide
- Go to Marketing > Files and Templates > Design Tools.
- From HubSpot CMS > Templates, select the correct template or theme. Confirm it is assigned to your working page.
- Edit your layout, module, or stylesheet.
- Click Publish Changes in Design Manager, not just “Save.”
- Open the content editor for your specific page. Ensure it points to your updated template.
- Hit Update or Publish in the page editor to flush the compiled cache.
- View the live URL and force a refresh with ?v=2 (example: https://yourdomain.com/home?v=2).
- Right-click the page and select “View Source” to inspect whether your updated code is present.
For ongoing stability:
- Use Design Manager’s “Linked Files” section to track template and module connections.
- Double-check the stylesheet load order in theme.json or page settings.
- Confirm nested module imports all resolve to live, non-cloned versions.
This debug workflow catches most sync problems before visitors see broken or outdated content.
Measuring Results in HubSpot
After resolving publishing lags, check if updates improved outcomes. HubSpot’s reporting tools measure whether new styles, layouts, or modules affected engagement.
Look at:
- Bounce Rate: Did cleaner design reduce premature exits?
- Session Duration: Are visitors staying longer with improved formatting?
- Click Map: Are updated buttons or CTAs getting more clicks?
For detailed tracking: Create a custom dashboard in Reports > Dashboards with widgets showing:
- Recently updated templates
- Global modules changed within the last 7 days
- Pages still linked to unpublished modules
This system allows your team to see when and where changes occurred, and whether updates are driving performance.
Short Example That Ties It Together
You update a global footer to add links to TikTok and YouTube profiles. You edit the module and hit save, but nothing updates live.
To fix it:
- Check Website > Pages > Settings and discover it’s using a cloned version of the footer.
- Return to Design Manager, locate the correct module, and click Publish Changes.
- Clear your browser cache and append?v=2 to the live URL.
The new icons appear correctly. Use HubSpot Analytics to track clicks over the next two weeks. Aligning your update points from editable source to live delivery ensures changes aren’t blocked by hidden settings or stale cache.
How INSIDEA Helps
INSIDEA helps marketers and CMS admins eliminate guesswork from HubSpot’s design update process. We provide HubSpot consulting services and support, hiring HubSpot experts to ensure edits propagate correctly.
We offer:
- Portal Setup and Onboarding: Align design and content structure from the start.
- On-Call CMS Troubleshooting: Fix caching or template sync issues quickly.
- Hands-On Automation Scripting: Ensure workflows enhance, not stall, publishing.
- End-to-End Module Auditing and Reorganization
- Reporting Dashboards: Tie design updates to engagement metrics.
- Team Training: Teach admins to catch and resolve update failures early.
If CMS changes aren’t syncing as they should, we can step in with hands-on support and actionable fixes. Visit INSIDEA to get started or schedule a consultation.
When design changes don’t show up live, your site and your users suffer. Audit templates, publish edits properly, and confirm updates with analytics.
If you get stuck, INSIDEA is ready to help you fix what your cache won’t.
