How to Troubleshoot Root Domains Not Loading in HubSpot

When your root domain fails to load in HubSpot, it disrupts far more than just your homepage. Suddenly, marketing campaigns return broken links, analytics lose attribution, and visitors hit dead ends. You’re left digging through DNS settings while your team waits for a fix.

This typically starts during domain setup—often with a misconfigured A record or incomplete SSL provisioning. While your www subdomain might be working just fine, the root domain (like example.com) is not resolving, causing confusion and lost sessions. For teams managing connected domains across departments or transitioning into HubSpot CMS, these small breaks ripple into bigger issues.

This guide walks you step-by-step through troubleshooting a root domain that won’t load in HubSpot. You’ll learn how the platform manages domain connections, what to look for in DNS and SSL errors, and how to validate changes with HubSpot’s built-in tools.

Troubleshooting and Resolving Root Domain Redirection Issues

In HubSpot, the root domain is the version of your site without a subdomain prefix—just example.com. While it’s common to publish your site or landing pages under a subdomain like www.example.com, many teams want the root itself to redirect or serve content seamlessly. If it doesn’t load, there’s almost always a misalignment in your DNS setup.

You’ll manage this in HubSpot under Settings > Domains & URLs, where you’ll find connections, verification, and SSL setup. To confirm ownership and launch your site securely, HubSpot looks for specific DNS entries—usually a combination of A records for root domains and CNAMEs for subdomains.

In most cases, the problem isn’t in HubSpot but with your DNS provider. HubSpot can only deliver your content if your domain points to its hosting environment cleanly. So, whether you’re using GoDaddy, Cloudflare, or another registrar, ensure your DNS entries fully match HubSpot’s instructions.

How It Works Under the Hood

To troubleshoot correctly, it helps to understand how HubSpot handles domains under the surface:

• DNS Inputs: At your registrar, you’ll enter the record values HubSpot provides. Subdomains usually require CNAME records, whereas the root domain typically needs an A record mapping to HubSpot’s IP.
• HubSpot Verification: After setup, HubSpot scans your DNS to verify control. Once verified, your site can be served to visitors.
• SSL Provisioning: As part of this verification, HubSpot also requests and applies an SSL certificate—activating HTTPS encryption across your site.
• Routing Behavior: HubSpot recommends redirecting traffic from the root domain to the www version or another active subdomain. In many cases, root domains can’t serve HubSpot content directly without a redirect.

If even one of these layers fails—say, the DNS record is imprecise, or SSL hasn’t been activated—your website becomes unreachable at the root. That’s why a stepwise approach to DNS, SSL, and HubSpot verification is the most reliable way to resolve these issues.

Main Uses Inside HubSpot

Hosting HubSpot CMS pages under your primary domain

If you’re running a public-facing site in HubSpot CMS, tying it cleanly to your root or www domain ensures brand consistency across all pages. Most commonly, you’ll want www.example.com to load your site—and when someone types in just example.com, it should redirect there automatically.

Say you’ve published a product promo at www.example.com/promo. Without a proper root redirect from example.com, users typing in the bare domain won’t reach the page at all. That kind of gap results in lost leads that you may never recover.

Managing multiple subdomains for marketing and service pages

When you use several subdomains—like blog.example.com for content and info.example.com for support—your root domain becomes the common frame of reference. Within HubSpot, each of these subdomains must be tied to the same verified domain property.

If the root domain is left unconnected or misdirected, traffic reports may fragment. It’s common to see inflated “direct” traffic due to failed redirects or untracked sessions. Ensuring the root routes properly consolidate your analytics and preserve attribution.

Enforcing HTTPS and SSL consistency across the site

Without proper DNS verification, HubSpot can’t provision an SSL certificate. Even if your content loads, users may see warnings about an insecure site. This can especially affect root domains if they’re not redirected and validated during setup.

For instance, connecting the domain without also updating DNS might leave your SSL status stuck as “Pending.” As soon as you update the A record to match HubSpot’s settings, the certificate can activate—often within an hour—giving you full HTTPS support across devices.

Common Setup Errors and Wrong Assumptions

• Incorrect DNS records: Many DNS providers don’t allow CNAMEs at the root, so you’ll need to point an A record to the specific IP address HubSpot provides. Relying on a CNAME here—especially if copied from a subdomain setup—will break the connection.
• Assuming subdomain setup covers the root: Setting up www.example.com in HubSpot doesn’t automatically handle example.com. Unless you configure a redirect externally or add the root domain as a connected domain with its own records, it won’t resolve.
• Skipping SSL verification: If SSL isn’t verified via DNS, your page might load over HTTP but still trigger security errors in browsers. Don’t just assume it’s live—check the “SSL active” status in your HubSpot domain settings.
• Not clearing cached DNS: DNS changes don’t reflect instantly across the web. Even when everything is correct, cached records can cause errors temporarily. Use DNS propagation tools to confirm changes have taken effect globally.

Step-by-Step Setup or Use Guide

To begin, make sure you have access to both your HubSpot account and your DNS registrar. Confirm that no conflicting redirects exist in third-party hosting or proxy services.

1. Log in to your HubSpot portal. Click the Settings gear icon.
2. In the sidebar, go to “Website,” then “Domains & URLs.”
3. Find your root domain under “Connected Domains.” If you see a status like “Action required,” you’ll need to continue setting up.
4. Click “View setup instructions” next to the domain. Copy the required A record and CNAME provided.
5. Open your DNS provider’s dashboard. Ensure you enter the A record (for the root) exactly as shown. If using www, set its CNAME to HubSpot’s target value.
6. Save changes. Allow time for DNS to update. Use a service like whatsmydns.net to track global propagation.
7. Back in HubSpot, click “Check DNS.” Wait for the status to update to “Verified.”
8. In the same menu, verify that SSL is set to “Active.” If still pending, give it at least 30–60 minutes post-DNS propagation.
9. Test both example.com and www.example.com. Confirm they load directly or redirect to working content.
10. To unify metrics, create a permanent (301) redirect from example.com to www.example.com if needed. This keeps analytics clear and consistent.

Once setup is stable, your domain should resolve quickly for all visitors—whether they start at the root, with www, or on a targeted landing page.

Measuring Results in HubSpot

After resolving domain issues, review your site’s performance to ensure everything works as expected. HubSpot gives you visibility into how connection problems affect traffic, engagement, and reporting.

Use these tools to validate improvements:

• Traffic Analytics report: Filter by domain to view merged traffic under a single address. A sudden drop in “direct” traffic may indicate redirects are working.
• Website Pages tool: Load key URLs to confirm pages are served properly from either domain.
• Site Performance dashboard: Keep an eye on load times and uptime. Delays or dips may indicate lingering DNS inconsistencies.
• Redirects report: Within “Domains & URLs,” open “URL Redirects” and confirm you’re using permanent redirects (301) instead of temporary ones (302 or 307).

Use this checklist to confirm domain health:

• The root domain redirects cleanly to www.example.com.
• SSL is active and confirmed in HubSpot.
• No duplicate pages under root and www.
• Analytics reports unify across one domain property.
• The “Connected” status shows for both root and subdomains.

These checks guard against future misfires and help your team track clean performance data.

Short Example That Ties It Together

Let’s say you’re a RevOps manager overseeing example.com in HubSpot. You notice that while www.example.com loads just fine, visiting example.com returns an error or blank screen.

You check “Domains & URLs” in your HubSpot settings and see “Not connected” by the root domain. Then, in GoDaddy, your DNS provider, you find only a CNAME for the www version—nothing for the bare domain.

You add an A record pointing to the IP that HubSpot provides. After DNS propagates, HubSpot shows “Connected.” SSL moves from “Pending” to “Active,” and both domains load successfully across phones and laptops.

Later, in “Traffic Analytics,” you confirm that session data is now consolidated. What was once 30% “direct” traffic from broken root links now tracks cleanly under www.example.com. Your campaign links work, analytics reflect reality, and users aren’t running into dead ends.

How INSIDEA Helps

If you’re still facing issues or your team doesn’t have clear ownership of the domain setup, INSIDEA can help. We work with marketing teams, IT admins, and RevOps specialists to resolve incomplete setups and bring order to multisite configurations.

Our services related to this include:

• Domain setup audit: We’ll evaluate your root domain, subdomains, and redirects to uncover inconsistencies.
• DNS troubleshooting: We identify and correct DNS errors that block HubSpot from serving your site.
• CMS hosting validation: From SSL to CDN routing, we ensure your HubSpot site is loading securely and efficiently.
• HubSpot onboarding: Helping new users configure portal basics the right way from day one.
• Ongoing management: We keep your domains connected, redirects stable, and SSL certificates valid in the long term.
• Analytics alignment: We ensure marketing and CRM data flow together, not across conflicting domains.

If a clean domain setup still feels out of reach, we’ll get your configuration stable. Schedule a consultation with our HubSpot experts or check out INSIDEA’s HubSpot consulting services today.