PageForge 1.3: check every run before it writes, update generated pages, spintax and resumable batches. See what changed
Account Get it free

Choose whether PageForge creates native Pages, Posts or its own custom post type, what URL each produces, and what the Generated CPT Slug Base setting changes.

Updated November 18, 20263 min read

PageForge can create three kinds of content. The choice decides where the pages appear in WordPress and what their URLs look like.

TargetAppears underExample URL
PagePages > All Pages/roof-repair-austin/ or /roofing/roof-repair-austin/
PostPosts > All PostsFollows your post permalink setting, such as /roof-repair-austin/ or /2026/03/roof-repair-austin/
PageForge PageThe PageForge content list/pageforge/roof-repair-austin/

PageForge Page is the plugin’s own custom post type. It keeps generated content apart from the pages you build by hand and gives it a shared URL prefix.

Choose the target

Each template has a Target Post Type field:

  • Use global default follows the Generated Post Type setting under PageForge > Settings.
  • PageForge Page (pageforge_page), Page or Post fixes the target for that template.

A target chosen on the template overrides the global default. When you pick a template on the Generate screen, PageForge shows where the pages will go and whether the template or Settings controls it, for example “Native Page → Pages > All Pages”.

On a fresh install with nothing changed, the default is PageForge Page.

Important Changing the target or the global default affects only pages generated afterwards. Existing pages are not converted or moved.

Which one to pick

  • Page gives clean root URLs such as /roof-repair-austin/ and supports parent pages, so you can build /roofing/roof-repair-austin/. This suits most service-area and location campaigns.
  • Post suits content that belongs in your blog, categories and feeds.
  • PageForge Page keeps a large campaign separate from the rest of the site, under one prefix that you choose.

Remove /pageforge/ from new URLs

To get root URLs, edit the template and set Target Post Type to Page, or choose Use global default and set the Generated Post Type setting to Page. Native Pages appear under Pages > All Pages and use WordPress Page permalinks. Pages you already generated keep their current URLs. For a step-by-step fix, see Remove /pageforge/ from page URLs.

What Generated CPT Slug Base changes

The Generated CPT Slug Base setting under PageForge > Settings changes the prefix used by the PageForge content type. For example, setting it to locations turns /pageforge/the-magnolias/ into /locations/the-magnolias/.

It is easy to expect more from this setting than it does:

  • It only affects PageForge Page content. Native Pages and Posts use WordPress permalinks and ignore it.
  • It cannot be empty, so it cannot give PageForge Page content root-level URLs. Use the Page target for that.
  • It does not choose which content type PageForge creates.

Save the setting to refresh WordPress’s URL rules. Changing a prefix that is already in use changes the address of every published page in that content type. PageForge does not create redirects, so set up redirects from the old URLs with your SEO or redirect plugin before you change it.

Pretty permalinks

Readable URLs, and nested Page URLs such as /maths-tuition-gurgaon/dlf-phase-iv/, need pretty permalinks. Under Settings > Permalinks, choose any structure other than Plain.

Other content types

Generation targets are limited to Pages, Posts and the PageForge content type. To list generated pages elsewhere on the site, use the PageForge Sitemap block or the [pageforge_sitemap] shortcode on a hub page. See Hub pages with the sitemap block.

Next: Parent pages and URL hierarchy.

Was this page helpful?

↑↓ to move↵ to open