How to Set Up Your Blog in HubSpot

Most companies think of "moving the blog into HubSpot" as a design task — pick a template, match the colors, done. Then they're surprised when the real value shows up somewhere else entirely.

The point of running your blog in HubSpot isn't the editor. It's that every reader who fills out a form or clicks a CTA becomes a known contact with full history attached. Suddenly you can see which articles brought in real leads, which post someone read the week before they booked a call, and where your content budget is actually paying off. A blog on a disconnected platform gives you page views. A blog in HubSpot gives you a line from "reader" to "customer."

Here's what setting up a HubSpot blog actually involves, the one decision that shapes the whole project, and where we've learned to focus.

What setting up a HubSpot blog involves

There are three pieces, and each one is simpler than it sounds once the sequence is right.

Templates are the look of your blog — a listing page (your index of posts) and a post page. You can match your existing website exactly through HubSpot's template service, or start from a theme and shape it to your brand. Either way, you end up with two templates that carry your look automatically onto every post.

Settings are the details you lock in once so you're not deciding them per post: your blog name and URL structure, whether posts show author bylines, how you organize them with categories or tags, whether comments are on, and whether readers can subscribe to new posts.

Your domain is where the blog lives — usually a subdomain like blog.yourcompany.com, pointed to HubSpot so the blog loads on your own address, not a HubSpot one.

That's the whole job for a brand-new blog. If you already have a blog, there's one more piece — and it's the one that matters most.

The decision that shapes everything: new blog or migration

Before anything else, one question decides how the entire setup goes: are you starting a blog for the first time, or moving an existing blog off another platform?

A brand-new blog is straightforward. Connect the address, point the domain, and you're publishing.

Migrating an existing blog is a different job. Your published posts have to be exported and imported, and — this is the critical part — every old link has to be redirected to its new home. If your main website is staying on your current platform while only the blog moves, the two now live at different addresses. Skip the redirects and every link to your blog that exists across the web, and in Google's index, suddenly points at a dead page. That's how a migration quietly erases years of search ranking.

This is why we ask that one question first. It's the difference between a two-step setup and a project where the redirects are the main event.

Why running your blog in HubSpot is worth it

When your blog is set up properly inside HubSpot, the payoff compounds:

Every reader who converts is captured as a contact, with full attribution
You can see which posts drive actual leads and deals, not just traffic
Your templates match your existing brand, so nothing feels bolted-on
If you're migrating, your existing search ranking is protected instead of lost
Your content becomes the foundation the rest of your tools plug into — CTAs, follow-up, SEO, and reporting all draw on it

The last point is the one most teams underestimate. A connected blog isn't a standalone asset. It's the surface that makes every downstream marketing tool more useful, because now your content and your customer data live in the same place.

Where teams go wrong

A few patterns we see over and over:

Treating a migration like a fresh setup. The export and import are the easy part. The redirects are what protect your traffic — and they're the step most likely to get rushed or skipped. A migration without a tested redirect map is a migration that costs you ranking.

Underestimating the domain step. Pointing a subdomain to HubSpot is a small technical change, but it needs access to your DNS — and waiting on that access is the single most common reason a blog setup stalls. Lining it up early keeps the whole project moving.

Expecting features a plan doesn't include. Some capabilities — running multiple separate blogs, or publishing without HubSpot branding on lower tiers — depend on which HubSpot plan you're on. Knowing that up front avoids a surprise at go-live.

How we approach it

We treat the blog as plumbing that has to be right, not a design exercise. Before touching anything, we settle the one question that matters — new blog or migration — and get domain access lined up so nothing stalls. We match your templates to the brand we've already loaded, configure your settings once so they're consistent, connect your address, and, if you're migrating, we build and test the redirects rather than assuming they worked.

What you're left with is a blog that publishes on-brand, loads on your own domain, and feeds every reader straight into your CRM — a foundation your content can actually build on. Writing and optimizing that content is its own discipline, and one we're glad to help with when you're ready; this milestone makes sure the foundation underneath it is sound.

If you want to learn more about how to set your blog up right in HubSpot, contact The Gist.