Building a Website With HubSpot (From Theme to Launch Day)

• Pick your route first: self-build with a theme, migrate, or custom build.

• A theme bundles templates, modules, global content, and style settings. Change a setting once and it reaches every page.

• Marketplace themes can't be cloned. Make a child theme to edit one safely.

• Publish pages, templates, navigation, and redirects before you change DNS.

• Content staging needs Content Hub Professional or Enterprise. Free tools have another path.

The one that matches your skills and your timeline. Searches like "build a website with HubSpot" and "build website with HubSpot" sound like one task, but building a website with HubSpot starts with a choice between three routes. HubSpot's own website onboarding page frames them the same way. (Source: "HubSpot website onboarding")

There's also a fourth option. You can host only part of your site on HubSpot, such as landing pages or a blog, and leave the rest where it is. On an existing site, you install the HubSpot tracking code to capture visits and form submissions. (Source: "Build a website")

If you're unsure which route fits, a HubSpot website development team can help you decide before you spend time on the wrong one. The rest of this guide follows the self-build path, with notes where the other routes differ.

The theme is a package. It holds templates, modules, global content, and style settings, and every page you build inherits from it. (Source: "Use themes")

The four parts do different jobs:

• Templates set the layout of a page type, such as a home page, service page, landing page, or blog post.

• Modules are the content blocks that fill a template, such as text, images, forms, and calls to action.

• Global content is anything repeated on many pages, such as the header and footer. You edit it once and it changes everywhere.

• Style settings control fonts, colors, spacing, and buttons for every template in the theme.

Every page and post you build draws on all four parts. A change to any of them reaches every page that uses the theme.

The style settings are the part to learn first. In the content editor, the global theme styles panel lets you change colors or buttons once, and the change applies to all pages and templates that use the theme. (Source: "Edit your theme settings")

One trap catches teams that switch themes midway. Setting or changing the active theme does not change the theme used by existing content. You have to swap each page's template. Pick the theme before you build, not after.

Start from the pages you need, not from the demo you like. You have three sources. Every account has at least one default HubSpot theme, you can buy themes from the Template Marketplace, and developers can build a custom theme locally with the HubSpot CLI. Content Hub accounts can also upload themes bought from Envato's ThemeForest.

Score each candidate on these questions:

The child theme limits are small. HubSpot's free tools and Content Hub Starter allow one child theme, Professional allows five, and Enterprise allows ten. (Source: "Child themes")

As a rule of thumb, a default theme suits a simple site, a marketplace theme saves design time, and a custom theme fits when brand and layout rules are tight.

The settings that every page will inherit. Building a website in HubSpot goes faster when these come first, because later changes ripple through finished pages.

1. Install the theme and make a child theme if needed. In the design manager, right-click the theme folder and choose Create child theme. You can then edit the child's settings without touching the parent.

2. Set the style settings. Open the theme settings and set colors, fonts, and buttons to match your brand guide.

3. Build the header and footer. Both are global content. Create a navigation menu and add it to the global header or footer inside the page editor, so one edit updates every page.

4. Point the blog at the theme. In your blog settings, set the blog to use the same theme as your pages. The blog post and listing templates are chosen separately, so check both.

5. Plan your forms and CRM. When a new visitor submits a HubSpot form, HubSpot creates a contact for that email address. Decide which properties each form fills and who gets notified. (Source: "Create contacts")

6. Install the tracking code if you're keeping an old site live. It captures visits and form submissions on the pages that stay elsewhere.

The order matters. Style settings and global content touch every page, so settle them before you build the first one.

One template at a time, in the editor, starting with your home page and core service pages. When you create a page, the templates from your active theme appear first. Pick the template, then add or rearrange modules in the drag-and-drop editor. Edit the header and footer once as global content, not on each page.

HubSpot's AI can speed up the first draft. Breeze can generate website pages, landing pages, blog posts, and images from prompts. Treat the output as a draft, and have a person edit it before it goes live. (Source: "Build a website")

Set the search fields on every page as you go, not at the end:

All accounts get SEO recommendations in the content editor while you work. The wider SEO tool and topic suggestions are for Marketing Hub and Content Hub Professional and Enterprise. (Source: "View SEO recommendations in HubSpot")

Finish URLs before launch if you can. HubSpot creates a redirect from the old URL to the new one when you edit the URL of a published page, but a clean first URL means fewer redirects to manage. (Source: "Change content URLs")

Everything a visitor or a search engine will touch. Building a website with HubSpot isn't done when the last page is filled. Run this list on your preview or staged pages, then run it again on the live domain.

Give each row a name, not just a tick. When a check fails the night before launch, you need to know who fixes it.

By finishing the new site before you touch DNS. HubSpot's help center says that if you're moving a live site, you should set up and publish your pages, templates, navigation, and redirects first, and back up or migrate your old content before the DNS change.

Connect a live domain before publishing content there, and visitors may see a HubSpot 404 page. While DNS changes spread, some visitors may still see the old site. (Source: "Connect a domain to HubSpot")

The launch order looks like this:

1. Back up. Save your old content before anything changes.

2. Publish. Finish and publish your pages, templates, navigation, and redirects on HubSpot.

3. Pre-provision SSL. Add the SSL records from HubSpot's dialog to your DNS, so the certificate is ready when you switch.

4. Switch DNS. Update the CNAME record for a subdomain such as www, or the A records for a root domain.

5. Verify. HubSpot checks DNS records within 15 to 80 minutes, and SSL can take up to four hours.

6. Test live. Check forms, links, and HTTPS on the live domain.

DNS is the fourth step, not the first.

Two timers matter. After you update DNS, HubSpot verifies the records within 15 to 80 minutes. A subdomain such as www uses a CNAME record, and a root domain uses A records. The SSL certificate is provisioned automatically and usually takes a few minutes, though it can take up to four hours. You can pre-provision SSL with the records in HubSpot's dialog, so the certificate is ready when you switch. (Source: "SSL and domain security in HubSpot")

If SSL fails, check three things first. A CAA record that doesn't include Google Trust Services blocks the certificate. AAAA records on HubSpot hostnames can block it. And the root domain should have only the two A records HubSpot shows, because extra ones can stop it. (Source: "Troubleshoot SSL certificate errors")

Watch, fix, and connect the search tools. A launch is the start of the measuring, not the end of the work.

• Connect Google Search Console. HubSpot shows the search queries that return your content only if you use the Google Search Console integration. (Source: "View SEO recommendations in HubSpot")

• Read the SEO recommendations. Fix missing descriptions, broken links, and slow pages as they appear.

• Check traffic and forms. Use HubSpot's traffic analytics, or add Google Analytics to your content, and confirm that form submissions still reach the CRM.

• Review AI search visibility. HubSpot's AEO recommendations can point to pages to create or update. The recommendations feature is in beta, needs Marketing Hub Professional or Enterprise, and uses credits for some features. (Source: "Review and manage AEO recommendations")

• Re-check redirects and the domain. Watch for 404 errors on old URLs, and confirm the SSL certificate stays valid.

Put a monthly review on a calendar. A site that nobody looks at after launch drifts out of date.

How to Build a Website in HubSpot Without Writing Code?

Use a theme and the drag-and-drop editor. Modules are custom-coded components, but once a developer or theme author has built them, you can customize them in the page editor without code. (Source: "What is the design manager?") The limit is a section your theme lacks. That one needs a new module.

Can I Host Only Part of My Site on HubSpot?

Yes. You can host only certain parts of a site on HubSpot, such as landing pages or a blog, and keep the rest where it is.

Can I Change My Theme Later?

Yes, but it takes work. Changing the active theme doesn't update existing pages. You swap each page's template, so the cost grows with every page you've built.

Can I Redirect Other Domains to My New Site?

Yes. All accounts can connect an unlimited number of redirect domains. A redirect domain can't host content, but it sends visitors to another domain connected to HubSpot, and you can add redirects for individual URLs. (Source: "Understand subscription limits for domains")

When Should I Bring In a Developer?

When the design needs something the theme can't make: a new section type, a custom theme, or a build your team wants under version control. HubSpot's developer tools let a developer build themes and modules locally with the HubSpot CLI.

Building a website with HubSpot goes smoothly when you decide three things before you start: the route, the theme, and the launch order. Everything else is editing.

Before you build, write the three decisions on one page. Then run the pre-launch checklist on a test lead and a test redirect. If both pass, the launch is mostly waiting for DNS.

If you'd rather hand the build to a team, HubXpert's HubSpot website design service follows six steps: discovery, wireframes, UI design, HubSpot development, testing and launch, and training and handover.