A parent page organises related WordPress pages into a hierarchy. For example, a Support page can contain a child page for Installation. Changing the parent can also change the child's URL, so review existing links before reorganising published content.
IN THIS ARTICLE
01 Plan the hierarchy
Choose a parent that accurately describes the child content and avoid unnecessary levels. A deep structure can create long URLs without making navigation clearer. Page hierarchy and navigation menu structure are related editorial decisions, but changing one does not guarantee the other updates exactly as intended.
Record the current child URL and identify important internal or external links. If the address will change, prepare a redirect to the new location and keep the old address in your change record.
02 Assign the parent
- Open the child page in the editor and review its current slug.
- Find the Parent page or page-attributes control in the page settings.
- Select the intended existing parent, then save or update the page.
- Confirm the resulting permalink before updating navigation or sharing the new address.
03 Verify the public structure
Open the new URL while signed out and check breadcrumbs, menus and any page lists generated by the theme. Visit the old URL and verify the intended redirect behaviour rather than assuming it will always be created automatically.
If the page appears twice in navigation, inspect the menu or Navigation block separately. A custom menu can retain an old link while another automatic page list reflects the new hierarchy.
What if assigning a parent changes the page unexpectedly?
If the parent is unavailable, confirm it is a page and that your account can edit the relevant content. WordPress should prevent a circular parent relationship; do not try to force one through database edits.
If moving the page produces a 404, inspect the resulting permalink and rewrite behaviour before creating another duplicate page. Return to the original hierarchy if necessary while a redirect or routing issue is investigated. For a large restructuring, change a small reviewed set first and keep a complete old-to-new URL map so recovery does not depend on memory.