Structuring Pages (Parent/Child)

• WordPress Training Guide
• Why the Change?
• WordPress Basics
• User Roles
• Access & Navigation
• Creating & Editing Pages
• Workflow Stages
• Uploading Files
• Adding Links
• Create an Event
• Structuring Pages (Parent/Child)
• Final Exam
• Tips & Best Practices

We’ve covered creating pages, uploading files, adding links, and making events. Now let’s talk about site structure—how pages relate to each other. This matters because it affects navigation, breadcrumbs, and URLs.

What Are Parent and Child Pages?

WordPress lets you organize pages in a hierarchy:

• Parent Page: A top-level page for a program or major topic.
  • Example: “Program X” (overview page for the program)
• Child Page: A page nested under the parent, usually for related content.
  • Example: “Stakeholder Meetings” under “Program X”
• You can go one level deeper if needed:
  • Parent: “Program X”
  • Child: “Stakeholder Meetings”
  • Grandchild: “January 2026 Meeting Materials”

How It Works

• Breadcrumbs:
  • Our site uses breadcrumbs that reflect this hierarchy:
    • Example: Home > Program X > Stakeholder Meetings > January 2026 Meeting Materials
• URL Structure:
  • Child pages inherit the parent’s slug:
    • Parent: /program-x/
    • Child: /program-x/stakeholder-meetings/
    • Grandchild: /program-x/stakeholder-meetings/january-2026-meeting-materials/

Why It’s Important

• Navigation: Helps users understand where they are and find related content.
• SEO: Organized URLs improve search visibility.
• Content Organization: Keeps related topics grouped logically.

How to Set a Parent Page

1. In the Page Editor, open Settings (right sidebar).
2. In the first section, look for Parent.
3. The parent page will be listed; if there is no parent page, it will say None.
   1. To add or change the parent, select None or the page listed, then type the title of the page you want to set as the parent.
4. Save or submit for review.

Best Practices

• Use parent/child relationships for:
  • Program overview pages → related resources.
  • Meeting overview pages → individual meeting details.
• Avoid deep hierarchies—limit to two levels for clarity.
• Always confirm the parent matches the navigation plan.