HubSpot Ideas

Search HubSpot Ideas or Create Idea
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Status: Idea Submitted
Jnix284
Submitted by on ‎Aug 28, 2024 7:45 AM

Connect Domain and reserve root domain for website, not blog

When you connect a domain for a free or starter account, the default is that the domain is available for the website, blog, and landing pages.

 

It is optional how you configure the domains for Pro and Enterprise, but this might also impact those users depending on the domain/subdomain chosen for the blog vs website.

 

A user connects their domain and expects to publish their website home page on the root domain.

 

They get an error that a page already exists with that page path, despite not having created any other content.

 

This is happening because the blog listing page URL hasn't been set.

 

Once a blog is created, the user can add a page path to the Blog Slug and the blog listing page is no longer parked on the root domain, allowing the home page to publish.

 

This has popped up at least 20 times in the last few weeks here in the community and it's causing a lot of confusion.

 

When a domain is connected, the root domain should be reserved for the website and since a blog listing hasn't been created yet, there should be a temporary path for "blog" until the user configures something.

See more ideas labeled with:
1 Reply
Anonymous
Not applicable
‎Sep 3, 2024 11:09 AM

Hi there,

Thank you for raising this issue—it's an important one that affects many users, and I can see how it’s causing confusion.

When users connect a domain, they naturally expect the root domain to be reserved for their website’s home page. The current setup, where the blog listing page automatically occupies the root domain if the URL isn’t configured, can definitely lead to unexpected errors and frustration.

To enhance the user experience, I strongly suggest implementing a change where the root domain is reserved exclusively for the website by default, regardless of whether the blog listing page URL has been set. Until the user configures the blog path, assigning a temporary or default path for the blog  would prevent this issue and allow the home page to publish seamlessly.

This adjustment would not only reduce confusion but also align with the user’s expectations, making the process of connecting domains smoother and more intuitive. Given how frequently this issue is arising, addressing it could greatly improve user satisfaction and reduce support requests.

Thanks for considering this enhancement!