# Preview page does not match published page

**URL:** <https://community.hubspot.com/t/preview-page-does-not-match-published-page/121114>\
**Category:** Blog, Website & Page Publishing\
**Tags:** website-pages, starter\
**Created:** [November 21, 2024, 5:03pm UTC](https://community.hubspot.com/t/preview-page-does-not-match-published-page/121114 "2024-11-21T17:03:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![normanb](https://avatars.discourse-cdn.com/v4/letter/n/977dab/32.png) [@normanb](https://community.hubspot.com/u/normanb)\
**Post date:** [November 21, 2024, 5:03pm UTC](https://community.hubspot.com/t/preview-page-does-not-match-published-page/121114/1 "2024-11-21T17:03:07Z")

</div>

Hi,

I have been trying to publish my webpage through hubspot, I will be looking to add blog posts to it later. The published page does not match the preview page. The preview page is attached.

 ![webpage.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/1/51149a2d6279d5be4f8edc43aee64aff721c9426.jpeg)

The actual website is at [https://analyticaspatial.com/](https://analyticaspatial.com/)

It looks like it going to the blog page but I haven’t set that up yet.

---

<div class="post-metadata">

**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\
**Post date:** [November 21, 2024, 5:32pm UTC](https://community.hubspot.com/t/preview-page-does-not-match-published-page/121114/2 "2024-11-21T17:32:16Z")

</div>

@normanb in your settings \> content \> blog you’ll see that a default blog was configure dwhen you connected your DNS - because the blog slug is blank, it is parked on the root domain. If you update the blog slug to “blog” or anything so it’s not blank it will free up your root domain for your website page.

Once you update the blog settings, then you need to edit your home page settings so the content slug is blank (remove “home” or any other text) and verify the language settings are also not set to include /en-us or your language that would prevent it from using the root domain.