# Create a hierarchy for webpages

**URL:** <https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100>\
**Category:** CMS Development\
**Created:** [May 19, 2017, 5:29pm UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100 "2017-05-19T17:29:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![A2mun](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/a2mun/32/41549_2.png) [@A2mun](https://community.hubspot.com/u/A2mun)\
**Post date:** [May 19, 2017, 5:29pm UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100/1 "2017-05-19T17:29:57Z")

</div>

Is there a way I can create a hierarchy for how webpages are displayed in the webpage list or sitetree?

I know I can set a hierarchy for external viewing through advanced menus, but how I can do this for the editors.

Currently in the site tree I just see a list of all of the web pages I have created for a particular domain

---

<div class="post-metadata">

**Author:** ![stefen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stefen/32/29274_2.png) [@stefen](https://community.hubspot.com/u/stefen)\
**Post date:** [May 19, 2017, 6:28pm UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100/2 "2017-05-19T18:28:22Z")

</div>

@A2mun that’s determined by the url structure. If you’re pages have parent child relationships to them the URL should reflect that.

For example instead of creating pages like “/parent-page” and “/child-page” you should structure the child page like so “/parent-page/child-page” if that makes sense.

---

<div class="post-metadata">

**Author:** ![A2mun](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/a2mun/32/41549_2.png) [@A2mun](https://community.hubspot.com/u/A2mun)\
**Post date:** [May 23, 2017, 2:27pm UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100/3 "2017-05-23T14:27:26Z")

</div>

Thanks!

---

<div class="post-metadata">

**Author:** ![PennyFrench](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pennyfrench/32/25270_2.png) [@PennyFrench](https://community.hubspot.com/u/PennyFrench)\
**Post date:** [May 11, 2021, 10:24pm UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100/4 "2021-05-11T22:24:43Z")

</div>

How does one make an existing page into a child page? I can find no methodology for actually creating an actual site tree. Would have expected perhaps a drag and drop hierarchy but can’t find any way to take an existing web page and make it a “child” of another page.

---

<div class="post-metadata">

**Author:** ![IHammond](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ihammond/32/47092_2.png) [@IHammond](https://community.hubspot.com/u/IHammond)\
**Post date:** [June 12, 2021, 12:53am UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100/5 "2021-06-12T00:53:09Z")

</div>

Did you solve this?

---

<div class="post-metadata">

**Author:** ![IHammond](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ihammond/32/47092_2.png) [@IHammond](https://community.hubspot.com/u/IHammond)\
**Post date:** [June 13, 2021, 8:30pm UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100/6 "2021-06-13T20:30:39Z")

</div>

@PennyFrench not sure whether it’s still relevant… But if you go into the slug and amend it to include the parent page/path is updates it in the site tree section…

I.e.

if you want to connect “/this-page” to its parent page “/that-page”, you just edit it to “/that-page/this-page” and it updates it nicely and automatically.

---

<div class="post-metadata">

**Author:** ![HColman](https://avatars.discourse-cdn.com/v4/letter/h/67e7ee/32.png) [@HColman](https://community.hubspot.com/u/HColman)\
**Post date:** [October 30, 2023, 12:12pm UTC](https://community.hubspot.com/t/create-a-hierarchy-for-webpages/2100/7 "2023-10-30T12:12:40Z")

</div>

I am having the same issue and when I updated the slug, the page disapeared from the sitemap, any ideas what went wrong?
