How do you plan and execute a HubSpot website redesign or relaunch?

A HubSpot website redesign is a staged process that moves from strategy to build to continuous improvement, not a single design handoff. The reliable version runs in roughly this order: discovery and goal-setting, a current-site audit with analytics benchmarks, content inventory and information architecture, messaging and buyer-journey work, a design system in Figma, the build inside HubSpot's Content Hub CMS, migration and SEO preservation, staging and QA, launch, and post-launch optimization.[9] HubSpot renamed its CMS product to Content Hub, and the CMS still sits at the center of that product as the website builder, so a redesign today is built from Content Hub's themes, templates, and modules.[2]

Two ways to sequence the work

The traditional path is a big-bang redesign: gather every requirement up front, build the full site over several months, launch once, then leave it mostly untouched until the next rebuild. The track record of that model is uneven. Only 49% of redesign projects launch on time, 54% of companies expect their redesign to take more than six months, and the average traditional redesign ships about two weeks late.[10]

Growth-driven design (GDD) is the recognized alternative. Created by Luke Summerfield at HubSpot, it is a data-driven methodology that is deliberately tool-agnostic, so it applies whether or not you use HubSpot.[7] Instead of one large launch, GDD ships a focused launchpad site covering the highest-impact pages in about 60 to 90 days, then improves it through time-boxed sprints driven by real user behavior.[4][5] This launch-fast-then-improve pattern is also how the method is described when it is run specifically on HubSpot's CMS.[12][4] The phases below cover the full end-to-end process and note where the big-bang and GDD paths diverge, so you can pick the sequence that fits your traffic, budget, and risk tolerance.

Start by defining measurable goals and recording where your current site stands, because every later decision gets judged against that baseline. Growth-driven design opens with the same move: set specific goals, then study how people actually behave on the existing site.[4] Pull your current numbers before you touch anything, including organic sessions, conversion rate, form submissions, and the traffic and exit patterns on your highest-value pages, using HubSpot's traffic analytics or Google Analytics. Without those benchmarks you cannot tell after launch whether the redesign helped or hurt.

Goal-setting also means talking to people, not only reading dashboards. Interview sales and support about the questions and objections they hear most often, and note how prospects describe their problem in their own words. IMPACT's guide treats research-based buyer personas and both quantitative and qualitative research as non-negotiable inputs to the strategy phase rather than optional extras.[8] The output of this phase is a short goal document with baseline figures and a ranked list of the outcomes the new site has to move.

Catalog every page on the current site, then design the new sitemap before anyone opens a design tool. A content inventory is a spreadsheet listing every existing URL alongside its traffic, its conversions, and a keep, merge, rewrite, or retire decision.[9] That same inventory becomes the backbone of your redirect map later, so building it thoroughly now prevents lost rankings at launch.[3]

Information architecture is the new structure: the page hierarchy, the primary navigation, and how a visitor moves from one section to the next. Group pages around what buyers are trying to do rather than around your internal org chart, and validate the grouping against the sales and support input you gathered in discovery. In a HubSpot redesign this is also where you decide which pages share a template, since a clear architecture maps directly to a smaller, cleaner set of templates and modules in Content Hub.[11] The output is a content inventory with disposition decisions plus an approved sitemap and navigation model.

Messaging and the buyer journey get settled before design because layout follows content, not the reverse. Decide what each key page needs to say, and in what order, to move a specific audience from problem-aware to ready-to-act, and only then design a layout that serves those words. IMPACT's strategy phase produces exactly this: documented value propositions, page-level strategy, and a wishlist of 50 to 150 ideas that later get prioritized rather than all built at once.[8]

Map the journey by audience temperature. A first-time visitor who just learned they have a problem needs different proof and a different next step than someone already comparing you against two competitors. Draft the actual headlines, subheads, proof points, and calls to action for the pages that carry the most pipeline, usually the homepage, the core solution pages, and the top-of-funnel entry pages. When this phase is skipped, teams tend to design attractive pages that read well and convert poorly, then blame the visuals. The output is a message and journey map that the design phase turns into layouts.

Design the site as a reusable system in Figma, not as a stack of one-off page mockups. A design system is the shared set of components, type scale, color tokens, spacing rules, and interaction states that every page is assembled from. Establish visual direction on one important page first, get sign-off, then extend the system to the rest, which keeps revisions cheap while the direction is still fluid.

Design each Figma component with its HubSpot counterpart in mind, because a component that maps cleanly to a Content Hub module makes the build faster and keeps the live site editable. HubSpot themes expose global style settings, so colors, fonts, and spacing defined once in the theme can be changed later without editing CSS.[11] Deciding those tokens in Figma and mirroring them in the theme means your design system and your CMS settings stay in sync. The output is a Figma component library and page designs that a developer can rebuild module for module.

Rebuild the design in Content Hub as a theme made of templates and modules, so your marketers can edit pages later without a developer. A HubSpot theme is a portable, self-contained collection of templates, modules, and global style settings, and content editors change theme fields through an editor instead of touching code.[11] Build a library of flexible modules for heroes, features, testimonials, pricing, and forms that non-developers can drag, arrange, and edit inside the page editor.

Pick your subscription level early, because it gates the tools you get.[9] Content Hub is HubSpot's content and CMS product, with the CMS at its center as the website builder.[2] Professional starts at $500 per month with three seats and Enterprise at $1,500 per month with five, and content staging, the tool most teams use to relaunch, is available only on the Professional and Enterprise tiers.[2][1] Building modular now pays off during continuous improvement, when a marketer can swap a headline or rearrange a page without opening a support ticket. The output is an editable theme and module library ready to hold content.

Move your pages, blog, and CRM data into HubSpot, then protect rankings with a complete URL-to-URL 301 redirect map. Every existing URL that changes needs a permanent (301) redirect to its new address, which is how search engines pass along the ranking authority the old page earned. In HubSpot you manage these under Content > Domains & URLs on the URL Redirects tab, where 301 is the default type and you can bulk upload the full list from a CSV.[3] For a blog with a consistent old structure, flexible pattern redirects rewrite a whole group of URLs at once instead of one at a time.[3]

Carry the on-page SEO signals across as well: title tags, meta descriptions, heading structure, and image alt text should travel with the content rather than getting dropped in the move. Missing or incomplete redirects are the single most common cause of a post-launch ranking drop, so the redirect map built from your content inventory is the artifact to get right. If you keep the same domain, plan the DNS cutover as part of launch. The output is a migrated content set and a redirect map covering every URL that moved.

Rebuild the redesigned pages in HubSpot's content staging environment, test them there, then publish them to the live site in one coordinated swap. Content staging hosts your in-progress pages on a sandbox domain in the form your-domain.sandbox.hs-sites.com, where you can create new staged pages or clone existing ones without the public seeing them.[1] When you replace a live page with its staged version, the original page's analytics carry over, so you keep the historical traffic data, and you can publish many pages at once rather than one at a time.[1]

Quality assurance happens against the staged pages: check rendering across browsers and screen sizes, test every form and call to action, confirm redirects resolve, and review page load. Two limits are worth planning around, since content staging does not support multi-language content and cannot be used to redesign blog pages, so those get handled outside the staging flow.[1] Launch day itself is mostly execution: publish the staged pages, apply the redirect file, and complete any DNS change.[9] The output is a live site with its analytics history intact.

After launch, the site enters continuous improvement, where you run short, data-driven sprints on the live pages rather than waiting years for the next full rebuild. In growth-driven design, every sprint starts with a single focus metric you want to move, then the highest-impact ideas to move it get prioritized into a time-boxed build.[6] The cycle repeats as plan, build, learn, transfer, and the premise underneath it is that top-performing sites come from many small refinements over time, proven by data instead of opinion.[6]

This is where the earlier modular build earns its keep. Because pages are assembled from editable modules and theme fields, a marketer can test a new headline, move a form, or rewrite a call to action without a development cycle.[11] Feed those decisions with HubSpot analytics and CRM data, and treat launch as the point where you start learning what your real visitors do. HubSpot's own methodology material and IMPACT's guide are explicit that the day the site goes live is the beginning of the work, not the end.[6][8]

Content staging does not cover everything

Content staging is the standard relaunch tool, but it is limited to the Professional and Enterprise tiers and cannot stage blog redesigns or multi-language content.[1] Plan blog and localized pages through a separate workflow so launch day does not stall on a tool that was never built for them.

Redirects are where SEO is held or lost

A redesign changes URLs, and every unmapped URL is a page that can lose its rankings. The redirect map is tedious to build from the content inventory, and it is also the single artifact most responsible for holding traffic through a relaunch.[3][10]

Growth-driven design needs sustained commitment

The launchpad model only pays off if the improvement sprints actually happen after launch.[6] If the retainer continues but the roadmap discipline does not, continuous improvement can drift into continuous invoicing with little to show for it.

Modular builds cost more effort up front

Building a clean theme and module library is more work than hard-coding a handful of pages, and the payoff arrives later, when non-developers can edit and test without waiting in a queue.[11] On a very small site that rarely changes, that up-front investment may not be worth it.

It is not the same as a refresh

A redesign rebuilds structure, messaging, and templates, while a refresh restyles the existing site without changing its architecture. If your positioning and page flow still work and only the visuals feel dated, a refresh may get you there for far less effort.

It is not locked to HubSpot

Growth-driven design is tool-agnostic and predates any single platform, so the phases here apply on other content management systems too.[7] HubSpot's content staging, redirect tools, and themes make the build and relaunch more direct, but the strategy, inventory, and messaging work is platform-independent.[1][11]

It is not finished at launch

Both HubSpot's methodology material and the growth-driven design guides treat go-live as the start of the measurement period, not the deliverable.[6][8] A site left untouched after launch slowly decays against changing visitor behavior, which is the exact problem the continuous-improvement model exists to prevent.

It is not only a design project

Most of the outcome is set before design begins, in goals, content inventory, and messaging, so treating a redesign as purely a visual exercise tends to produce attractive pages that miss their targets.[8]