Connect a domain to HubSpot: which subdomain to use?

Connecting a domain to HubSpot is a ten-minute task preceded by a thirty-minute decision. Execution means copying two or three values from the platform and pasting them into the DNS provider's panel. The decision is defining which address will host what, and that part has no button.

The pattern is familiar: someone publishes the first landing page on a subdomain chosen on impulse, the links circulate by email and by ad, and three months later the team realizes that address should have been reserved for another content type. Changing it means republishing, remapping redirects and restarting the authority count for that URL.

This guide follows the order in which things actually happen: first the subdomain architecture, then the DNS records, and last the timings and limits that catch people out along the way.

What content does HubSpot host on your domain?

The connected domain serves seven content types: website pages, landing pages, blog posts, knowledge base articles, customer portal content, the web version of marketing emails and subscription preference pages.

Caption: when you connect a domain to HubSpot, platform content answers at the institution's own address, with automatic SSL

All of them start responding at your address rather than at a platform URL, which widens the scope of the decision.

Many teams go into this setup thinking only about the institutional website, or only about the capture pages. But the list includes items nobody remembers to map: the page where a contact adjusts communication preferences, the “view in browser” link in an email, the help center.

The path is direct. From the settings icon, go to Content, open Domains & URLs and use the Web Hosting tab, which deals exclusively with content hosting. There is a second tab, for email sending, which solves a different problem and comes back at the end of the third section.

It is worth the scope context on what changes when you move the site to Content Hub and the concrete gain in content personalized by visitor profile, the kind of feature that only exists with your own hosting.

What is the difference between a primary domain and a redirect domain?

HubSpot works with two roles. The primary domain, also called the hosting domain, is the one that serves the content and appears in the address bar.

The redirect domain hosts nothing, it simply forwards whoever arrives through it to the matching primary address. Confusing the two produces broken links.

The typical case involves variations the institution accumulated over the years: the .com alongside the country domain, the acronym alongside the full name, the domain of an old brand. None of them needs to host content, and all of them need to take the visitor to the right place.

Setting them up as redirects keeps a single canonical version of each page. As primaries, they create parallel addresses serving the same content, which splits search signals with no gain at all.

How do you choose subdomains for the site, the blog and landing pages?

The rule that organizes the decision is in the structure of the platform. In Content Hub (formerly CMS Hub) Professional, there is one primary subdomain per content type: one for website pages, one for landing pages and one for the blog. You define three addresses, not one.

That separation is not a limitation. It is architecture. It lets the institutional site sit on the root domain, the blog have its own address and the capture pages live on a third. Visitors do not notice the difference, but the operation does, because it becomes clear where each team publishes and where each metric is born.

The most common practice at educational institutions breaks down like this:

Table: Valid combinations for an education operation; HubSpot does not impose names, the criteria are legibility and permanence.

The criterion that matters most is durability. A subdomain like admissions2026 works for one cycle and then becomes debt. One like apply or resources survives several admissions cycles unchanged, and that matters in content marketing, where a page's link keeps bringing traffic years after the campaign that created it.

The address used to send email has to be a separate subdomain, distinct from the three above. Trying to use the same subdomain that already hosts pages produces connection errors. Subdomain design is decided once, which is why the warning belongs here.

Setting up DKIM, SPF and DMARC has its own logic and deserves separate treatment, but reserve the sending subdomain now, while the structure is still on paper.

Which DNS records does HubSpot ask for to connect a domain?

The rule depends only on the format of the address. A root domain requires updating A records, pointing to the IP addresses HubSpot provides. A subdomain requires a CNAME record, pointing to the hosting value generated for your account. The platform displays each value in a table with Host and Required Data.

Here is how that translates in practice:

Table: HubSpot generates the values per account, so never reuse a value from another portal or from a generic tutorial.

That last point deserves emphasis. CNAME values contain identifiers from your account. Copying from an example on the internet produces a syntactically valid record that will never validate, and the error is hard to see because the entry looks correct in the panel.

The full flow is in the official guide to updating DNS records, which is worth keeping open during execution, because every panel names the fields differently.

How do you apply the records at the provider without duplicating the domain?

Here is the error that stalls the project most. Several DNS providers automatically append the domain to the value you paste into the host field, producing duplicated entries like landing.college.edu.college.edu. HubSpot documents the behavior, and the fix is manual.

The mechanism works like this. HubSpot gives the host as landing.college.edu, the full name. Some DNS panels, however, expect only the prefix, landing, because they complete the rest themselves based on the zone you are editing. Pasting the full value into one of those panels ends with the domain written twice.

The record is created. Validation never passes.

And the diagnosis is thankless, because the provider's screen frequently shows only what you typed, not the concatenated result. You look at landing.college.edu, check it character by character against what HubSpot asked for, and conclude that it is right.

Three checks resolve this in minutes.

1. Check the record by its full name, not by the field. After saving, look at how the provider displays the entry in the zone's record list. If the domain shows up repeated, the panel completes it automatically and you should paste only the prefix.
2. Test resolution outside the panel. A DNS query in any lookup tool shows the name that was actually published, and separates what you typed from what actually exists.
3. Repeat the check on every record. If the provider concatenates, it does so on all of them, including the email authentication records you will create later.

In implementation projects, this is the item that consumes the most support time without producing any learning. It pays to check the provider's behavior on the first record, before creating the others.

How long does HubSpot's SSL take and when does it not come through?

Once the connection is validated, HubSpot provisions the SSL certificate automatically, at no cost and with no intervention. The official documentation describes the window as a few minutes in most cases, with the possibility of taking up to four hours. It is not a failure: it is the normal window for the process.

That number has to go into the schedule. The pattern that creates panic is connecting the domain on the morning of the launch. The record validates, the page still does not answer securely, someone assumes a configuration error and redoes what was already correct. Connecting the domain a day earlier eliminates the entire category of problem.

There is a documented exception worth knowing before you settle on names: domains longer than 64 characters require a custom SSL certificate, purchased separately. Rare on a short address, common when someone stacks descriptive prefixes like online-graduate-admissions.college-of-technology.edu.

With the domain live, the next infrastructure item is making sure measurement works. Installing and validating the tracking code is automatic on pages hosted by the platform, but stays manual on any page outside it.

How many domains can you connect to HubSpot on each subscription?

The limit is counted in brand domains, not subdomains. A brand domain is the root, like college.edu; the subdomains hanging off it follow a different rule. That changes the reading: whoever manages several brands is restricted, whoever manages one brand with many sections is not.

The breakdown by subscription looks like this:

Table: Limits published in the multiple subdomain hosting documentation; confirm in your own portal before locking the architecture.

The numbers are in HubSpot's own multiple subdomain hosting documentation.

An institution with a single brand and several programs operates comfortably on Content Hub Professional: site, blog and landing pages on three subdomains of the same root domain. A group with three brands on distinct domains, by contrast, hits the limit and needs to evaluate Enterprise or an add-on.

This is a calculation you run before signing, not after configuring. Anyone doing educational marketing in a multi-brand structure should bring the domain inventory to the commercial conversation, because it determines the plan.

Which errors stall people connecting a domain to HubSpot?

The blockers repeat in a handful of patterns, and none of them is a platform limitation. They are decisions taken out of order or DNS provider details that go unnoticed. Recognizing the main five before you start reduces the task to a single work session.

1. Pasting the full host into a provider that concatenates. The number one error. Always check how the record appears in the list after saving.
2. Publishing before deciding the subdomain architecture. A landing page promoted on a temporary address becomes an active link in email, ads and posts. Changing it later requires redirects and loses part of that URL's history.
3. Using the same subdomain to host content and send email. The attempt produces an error, because the sending domain has to be exclusive.
4. Not having access to the DNS provider. The most mundane and most frequent bottleneck. The credentials are usually with IT, with an old website vendor or with a former employee.
5. Scheduling the launch for the same day as the connection. SSL can take up to four hours, and one day of slack turns a risk into a non-event.

They cause delays because they appear in sequence, each revealed by the previous one, and because they almost always depend on someone from another department. Placing this stage inside the full account setup roadmap keeps it from being discovered as a surprise mid-project.

Frequently asked questions about connecting a domain to HubSpot

So where do you start to connect a domain to HubSpot?

Start on paper, not in the DNS panel. Write down the addresses the operation will use, one for each content type, plus one reserved for email sending. Confirm who has access to the domain provider, and only then open the connection screen and copy the values. In that order, the task does not come back.

The three technical points of attention are verifiable: A records for a root domain and a CNAME for a subdomain, a mandatory duplication check at providers that concatenate the domain, and a window of up to four hours for SSL before any promised launch.

The rest follows from a decision made well at the start. And it is worth remembering why this configuration exists. A connected subdomain is not a deliverable in itself, it is the place where something is going to live.

The first thing to occupy a connected subdomain is almost always a capture page, so the natural next step is building the first landing page that will use the domain you just configured.