You're facing a CNAME conflict for “www”, where both your domain provider (DNS) and HubSpot require control over the “www” subdomain. This is a common challenge when integrating multiple platforms.
1. Understand How CNAME Records Work
- A CNAME (Canonical Name) record allows “www.yourdomain.com” to point to another domain like “your-site.webflow.io” or a HubSpot endpoint.
- Only one CNAME can exist per subdomain (e.g., “www”), meaning you can't point “www” to both Webflow and HubSpot.
2. Determine Your Primary Hosting Platform
- If Webflow is your primary site, then “www” should point to the Webflow-assigned CNAME.
- If HubSpot hosts your main content, then “www” should point to the HubSpot CNAME.
You must choose one platform to use “www”. The other will need to use a different subdomain (like “blog.yourdomain.com”).
3. Configure Separate Subdomains
To avoid conflict, assign a unique subdomain to each platform:
- Keep “www” for Webflow (or vice versa).
- For HubSpot, choose something like “blog”, “marketing”, or “info”.
Then:
- In your DNS settings, create a CNAME record:
- For “blog” → point it to the HubSpot CNAME (e.g.,
your-hub-id.groupX.sites.hubspot.net) - In HubSpot, go to Website > Domains & URLs > Connect a domain, and set it to use blog.yourdomain.com.
4. Update Web Pages and Links
- Update internal navigation or external links so that:
- Marketing or blog pages use blog.yourdomain.com
- Main site pages use www.yourdomain.com
5. Optional: Redirect One to the Other
- If needed, set up a 301 redirect (within HubSpot or Webflow, depending on traffic flow) from one subdomain to another to consolidate SEO value.
Summary
You can't assign a CNAME record for “www” to both Webflow and HubSpot. The solution is to assign the “www” subdomain to one platform (your core site), and use a different subdomain like “blog” for the other. Configure each CNAME accordingly in your DNS provider and platform settings.