Organise pages, posts and custom post types as a drag-and-drop folder tree with unlimited nesting, real-time search, optional URL nesting and automatic 301 redirects.

Clean, audited code that installs in a click, stays out of your way, and keeps getting better — backed by the team that built it.
The capabilities that matter, built in from day one.
which types are organised; per type: URL nesting, maximum depth, whether the organiser replaces the stock list screen (on by default), whether your manual order applies to front-end queries.
on/off, status code (301/302/307/308), what triggers a rule, canonical enforcement, hit tracking, retention, row cap.
accent colour, row density, indent width, font size, corner radius, icon style (folder / document / dot / none), thumbnails, guide lines, zebra striping, sticky toolbar, light/dark/auto, which columns show, and a custom CSS box.
drag and drop, confirmation policy, sort mode, default expansion depth, remembered state, search fields, search delay, minimum characters, quick edit, lazy-load threshold.
menu placement and label and icon and position, admin bar shortcut, dashboard widget, required capability, which row actions appear.
export and import the whole configuration as JSON, rebuild permalink rules, purge redirects, reset to defaults, and choose what happens on uninstall.
Install, activate and configure in minutes — no code required.
New features and compatibility updates, included with your license.
Real help from the team that built it, whenever you need it.
Choose the license that fits — every plan includes updates and support.
For hierarchical post types such as Pages, nesting already drives the URL — that is WordPress's own behaviour, and it stays that way. For flat types such as Posts, nesting is added to the permalink only if you leave "Reflect nesting in permalinks" ticked for that type. Any change is covered by an automatic 301, so nothing breaks either way. If you would rather nothing moved at all, untick URL nest
Nothing is lost. Nesting is stored in post_parent and ordering in menu_order — both core columns. Pages keep their parents and keep behaving as they always have. Flat post types keep the stored values too; WordPress simply stops displaying them until the plugin comes back.
Yes. That is one of the main reasons this exists. Posts, products, portfolio items — any post type with an admin UI can be organised, and can have that nesting reflected in its URLs.
WordPress requires slugs to be unique across a non-hierarchical post type, and that rule belongs to core, not to this plugin. So two posts in different branches cannot both be overview — the second becomes overview-2. Hierarchical types such as Pages are not affected, because WordPress scopes their slugs to the parent.
No. Each move records the old address, but every one of those records points at the page itself rather than at the address it had next. A visitor following the oldest link goes straight to the current URL in one hop.
Get Page Organizer — Folders & Nested Pages today and set it up in minutes — backed by a 30-day money-back guarantee.
Get it now