It sounds like you're trying to publish a page to your domain's root URL (like abc.com/), but in HubSpot, only one page can live at that root path, typically your homepage. If a page is already published at "/", attempting to publish another one there will fail silently.
Here are a few things you can check:
Is there already a page at the root? Go to Website > Website Pages, filter by your domain, and see if there’s already a live page published at "/". If so, you’ll need to either update that page or unpublish it before assigning another one to the root.
Try publishing to a test slug first For example, publish your page to something like abc.com/temp-index. If that works, it confirms the issue is with trying to overwrite the homepage.
Check your redirect settings Head to Settings > Website > Redirects and make sure there isn’t a redirect rule affecting "/". Redirects can also block publishing at the root without showing a clear error.
If none of these fix it, it’s worth contacting HubSpot Support. They’ll be able to check backend logs and provide a more specific explanation.
Here are a couple of related threads you might find helpful:
Publishing a page to the root of your domain means you're setting it as your homepage. In HubSpot, a single page can be used as the primary page for the root URL. Below are some reasons why you might be getting that error:
1. Another page is already set as homepage/primary page. Go to Marketing > Website > Website Pages and look for the homepage. You can unpublish the current homepage in case you want the new page to be the homepage. Once the old homepage is no longer at /, try publishing your new page.
2. Domain issue: While you mentioned it worked before, sometimes a change in domain setup can cause issues. Go to Settings > Website > Domains & URLs. Check that your primary domain (abc.com) is correctly connected and healthy.
3. Redirects: Check Settings > Website > Redirects to make sure there’s no redirect affecting the root URL.
4. Cache: Sometimes a persistent browser cache or extension can cause odd behavior. Try clearing cache or try a fresh incognito browser window or a different browser.
Sometimes, there can be a temporary bug or a specific issue impacting your portal that only HubSpot's team can see. You can try connecting with support in case any of the above mentioned point don't work for you.
Is the domain already properly connected? Just adding the domain to HubSpot allows us to create pages under it, but it will cause an error.
Glad I could help. Solving HubSpot puzzles is what we do. Ernesto // GiantFocal Found this answer helpful? Marking it as the solution helps both the community and me - thanks in advance!
I also have a free account and am experiencing the same issue and error message with not with being able to publish to my root domain. I can publish all sorts of slug pages no problem, but nothing to my root domain. I have cleared cache, changed browsers, gone incognito, scrapped the page and started fresh, but nothing works. I've been troubleshooting with the bot chat for most of the day and it even had me check DNS settings in Cloudflare. In HubSpot, I cannot create redirects, otherwise I would have just used that as a shortcut instead. All I see are a couple of system-generated domains redirected to my root domain, but that is it. I only have one page currently, a main/home page, and I cannot get it to publish with a blank slug.
Is the domain already properly connected? Just adding the domain to HubSpot allows us to create pages under it, but it will cause an error.
Glad I could help. Solving HubSpot puzzles is what we do. Ernesto // GiantFocal Found this answer helpful? Marking it as the solution helps both the community and me - thanks in advance!
Publishing a page to the root of your domain means you're setting it as your homepage. In HubSpot, a single page can be used as the primary page for the root URL. Below are some reasons why you might be getting that error:
1. Another page is already set as homepage/primary page. Go to Marketing > Website > Website Pages and look for the homepage. You can unpublish the current homepage in case you want the new page to be the homepage. Once the old homepage is no longer at /, try publishing your new page.
2. Domain issue: While you mentioned it worked before, sometimes a change in domain setup can cause issues. Go to Settings > Website > Domains & URLs. Check that your primary domain (abc.com) is correctly connected and healthy.
3. Redirects: Check Settings > Website > Redirects to make sure there’s no redirect affecting the root URL.
4. Cache: Sometimes a persistent browser cache or extension can cause odd behavior. Try clearing cache or try a fresh incognito browser window or a different browser.
Sometimes, there can be a temporary bug or a specific issue impacting your portal that only HubSpot's team can see. You can try connecting with support in case any of the above mentioned point don't work for you.
It sounds like you're trying to publish a page to your domain's root URL (like abc.com/), but in HubSpot, only one page can live at that root path, typically your homepage. If a page is already published at "/", attempting to publish another one there will fail silently.
Here are a few things you can check:
Is there already a page at the root? Go to Website > Website Pages, filter by your domain, and see if there’s already a live page published at "/". If so, you’ll need to either update that page or unpublish it before assigning another one to the root.
Try publishing to a test slug first For example, publish your page to something like abc.com/temp-index. If that works, it confirms the issue is with trying to overwrite the homepage.
Check your redirect settings Head to Settings > Website > Redirects and make sure there isn’t a redirect rule affecting "/". Redirects can also block publishing at the root without showing a clear error.
If none of these fix it, it’s worth contacting HubSpot Support. They’ll be able to check backend logs and provide a more specific explanation.
Here are a couple of related threads you might find helpful: