A section of pages, such as a guide with a parent page and several child pages, has URLs that depend on the hierarchy: /coffee-guide/grind-size/ only exists if Grind Size is a child of Coffee Guide. When you build that section on staging and copy it to the live site, the parent links have to point to the right pages on the live site, whose IDs are different. With Import Export by RockStarLab Content Sync handles that: you push the pages, and the hierarchy and URLs come out the same on the other site. In the example, a three-page coffee guide moves from a roastery’s staging site to its live site, and a fourth page follows later.
Free: Content Sync for posts and pages, including parent pages and menu order. PRO: the same for custom post types.
Short Answer
- Connect the two sites in Content Sync (once).
- On staging, go to Pages, tick the parent page and its child pages, choose Sync Content in Bulk actions, select the live site and click Push to Site.
- Keep Create New Post for pages that don’t exist on live yet and click Confirm & Sync.
Push the whole section
On staging we had Coffee Guide with two child pages, Brewing at Home and Grind Size, in that menu order. In Pages, tick all three, choose Sync Content and select the live site. If the sites aren’t connected yet, see how Content Sync works.

Click Push to Site. None of the pages exist on live, so each one is set to Create New Post:

The children were listed before their parent, and it made no difference. After Confirm & Sync, the live site had all three pages with Coffee Guide as the parent of the other two, the same menu order (1 and 2), and the same URLs: /coffee-guide/, /coffee-guide/brewing-at-home/ and /coffee-guide/grind-size/. The pages got new IDs on live; the parent link points to the live ID.
Add a child page later
A week later the guide gets a fourth page, Water Temperature, under Coffee Guide. On staging, tick only that page and push it:

The parent wasn’t part of this push, but it already existed on live from the first sync. The new page was attached to that live Coffee Guide and opened at /coffee-guide/water-temperature/; there was still exactly one Coffee Guide page on the live site.
To update pages that already exist on live, choose the live page in the mapping instead of Create New Post, or click Auto-match by Title; see mapping posts between sites.
Before you push
A push changes the live site. Try it with one page first, and back up the live site before pushing a large section.
With an AI agent
An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) can check the result on the live site:
Show the coffee guide pages on the live site with their parent page and menu order.
In our run, the agent called rsl-ie/export-preview on the live site for Pages with the fields Title, Parent Title, Menu Order and Permalink. It returned Coffee Guide with no parent, and Brewing at Home (1), Grind Size (2) and Water Temperature (3) with the parent Coffee Guide, each under /coffee-guide/.
FAQ
Do I have to push the parent first?
No. Push them together in any order, or push a child alone once its parent is on the live site.
What if the parent page isn’t on the live site at all?
Push the parent together with its children, as in the first push above.
Does it keep the menu order?
Yes, the menu order of each page is pushed with it.
Can I move a section from live to staging?
Yes, use Pull from Site in the same dialog.
Related Guides
- How Content Sync Works: API Keys, Push, Pull and What Gets Copied
- How Auto-Match by Title Works and When to Map Posts Manually
- Import WordPress Pages with Parent-Child Hierarchy from CSV
Get the free plugin on WordPress.org.

Comments 0
Have a question or a tip to share? Leave it below.