The PageForge alternative for programmatic pages over real WordPress templates
PageForge takes a CSV and a template builder and produces bulk programmatic pages. SleekRank takes JSON, CSV, Google Sheets, Notion, or REST APIs and serves one URL per row over a normal WordPress page you already built, with mappings declared in a small JSON config.
€50 off for the first 100 lifetime licenses!
Template builder vs. mapping over a real page
PageForge sits in a familiar slot: upload a CSV, build a template inside the plugin's template builder, generate bulk pages. The pitch is straightforward and the workflow is tidy when the dataset is static and the design fits comfortably inside the builder's components. Where it strains is when the template needs to match the rest of the site's design system, when the data lives somewhere other than a CSV file, or when the dataset is something the team edits weekly.
SleekRank starts from the other direction. The template is whichever WordPress page you set as basePageId: a Gutenberg page, a Bricks layout, an Elementor template, an Oxygen build, or a hand-coded theme page. SleekRank doesn't render it; it modifies specific elements on it (tags, list selectors, CSS selectors, meta attributes) based on each row's fields, and serves the result at a URL pattern you control. The data source can be JSON, CSV, Google Sheets, Notion, or a REST endpoint, each declared in the page group's dataSources array with its own cache duration.
Both tools want to give you bulk programmatic pages. PageForge wants you to build inside it. SleekRank wants you to keep building wherever your site's design already lives and let the programmatic layer be a thin mapping config over that page's HTML.
Workflow
How SleekRank replaces a PageForge workflow
Build the base page in your usual editor
Connect the data source
Declare mappings
mappings entries that target the title tag, h1, meta description, list selectors, CSS selectors, and meta attributes on the base page. Each row's fields fill those elements on its URL.
Flush, cache, ship
wp rewrite flush and clear the SleekRank items cache the first time. Subsequent edits to the source flow through on the next cache refresh, with no generation step in between.
Comparison
SleekRank vs PageForge at a glance
urlPattern with {slug} tokensDifferences
What changes when you move off PageForge
The PageForge way
- Templates live inside PageForge's builder, separate from the rest of your WordPress design system
- Data input is centered on CSV uploads rather than live sources
- Generated output is real WordPress posts or pages per row
- Updating dataset content typically means re-running the generator
- Live sources like Sheets, Notion, or REST APIs are not first-class inputs
The SleekRank way
- Mappings target tags, lists, CSS selectors, and meta attributes on the base page
- Reads JSON, CSV, Google Sheets, Notion, and REST APIs as first-class data sources
- Per-page-group cache duration with a single SQL query to force refresh
-
URL pattern per page group like
product/section/{slug}with multi-segment tokens -
Filter hooks (
sleekRank/data/item/<slug>) for per-row data transforms
Features
Three things that actually change how you work
Use any WordPress page as the template
No parallel template builder to learn. Build the base page in whatever editor your site already uses, and SleekRank maps each row's fields onto specific elements via a small JSON config. The design lives where the rest of the site's design lives.
Live data sources, not just CSV
JSON in the theme for static config, CSV for one-off datasets, Google Sheets and Notion for content the marketing team edits directly, and REST endpoints for internal APIs. Each is a first-class source type, and a page group can mix them.
Filter hooks for custom transforms
The sleekRank/data/item/<slug> filter lets PHP transform a data row before replacements run. Build OG URLs, compute derived fields, format dates, or pull supplementary data without changing the source file.
Migration
Moving from PageForge to SleekRank
1. Identify the active datasets
List the PageForge templates currently in use and the CSV files driving them. Each pairing becomes a candidate SleekRank page group: one base page plus one data source.
2. Rebuild each template as a normal page
Recreate (or duplicate) the layout as a regular WordPress page in your usual editor. Use placeholder text where rows will fill in. This becomes the SleekRank basePageId.
3. Point at the data directly
Drop the CSV next to the theme, or graduate it to a Google Sheet, Notion database, or REST endpoint so the team that maintains the data can edit it without re-uploading. Add it as a dataSources entry on the page group.
4. Map elements and verify
Add mappings for the title, h1, meta description, list selectors, and inline elements. Run wp rewrite flush, clear the SleekRank items cache, and load a few sample URLs to confirm the layout fills correctly.
Audience
Where teams move from PageForge to SleekRank
Sites with an established design system
Agencies and product sites whose templates already live in Bricks, Elementor, Gutenberg patterns, or a custom theme don't want to rebuild them inside a separate template builder. SleekRank uses the existing page as the template directly.
Content edited outside WordPress
When marketing maintains landing-page copy in Google Sheets or Notion, SleekRank reads it directly. No export-to-CSV step before each generation, and no second copy of the data sitting in wp_posts.
Datasets that change weekly
For directories, location pages, and comparison pages where rows get edited often, SleekRank's cached-resolution model keeps the URLs aligned with the source without re-running a generator each time.
The bigger picture
Why the programmatic layer should be a thin config
Template builders inside programmatic-page plugins exist because the simplest pitch is one-stop: upload a CSV, build a template, click generate. The cost lands later. The site's broader design system, in Bricks or Elementor or a custom theme, evolves on its own track.
The plugin's template builder evolves on a different track. Components and patterns the rest of the site uses don't carry over. When the dataset changes, you regenerate inside the plugin.
When the design changes, you reconcile two design surfaces. SleekRank takes a different bet: the programmatic layer is a small mapping config over whichever HTML the base page already produces. The design stays where the rest of the site's design stays.
The data stays where the team that maintains it already edits it. The mapping is a JSON file in source control, short enough to read in one sitting. None of those pieces multiply with the dataset.
None require a re-generation pass when content changes. For sites where PageForge's builder genuinely is the right design surface and the dataset is static, PageForge keeps doing its job. For sites where the answer is closer to 'use the page we already built, against the data we already maintain, served at a URL pattern we picked', the cleaner shape is a thin mapping config over a real WordPress page.
That's the niche SleekRank fills, and it ages well as the design system and the dataset evolve independently.
Questions
Common questions about switching from PageForge
Functionally overlapping but architecturally different. PageForge keeps the template inside its own builder and produces bulk WordPress posts. SleekRank uses an existing WordPress page as the template and serves URLs over a live data source. For workflows where the dataset is static and the design fits comfortably inside PageForge's builder, the migration isn't urgent. For sites where the design lives in the main editor stack and the dataset is something the team edits regularly, SleekRank's model removes a layer of duplication.
Not automatically. The shape is different enough that automated migration of the template would lose more than it preserves. The practical path is to rebuild each template once as a normal WordPress page in your usual editor, then point a SleekRank page group at the same dataset with mappings for the elements you want filled. In our experience that takes less time than configuring an importer because the page renders standalone first.
JSON files inside the theme, CSV files, Google Sheets, Notion databases, and any REST API endpoint. Each page group declares one or more dataSources entries with a type and config. Cache duration is per source, so static JSON can cache for a day while a fast-changing API can cache for minutes.
Any existing WordPress page. You set basePageId on the page group, and SleekRank uses that page's rendered HTML as the template. Mappings target real elements on the page (title tag, h1, meta description, list selectors, CSS selectors, meta attributes), so whichever builder or editor produced the page is irrelevant.
Per page group via a urlPattern like byte/alternatives/{slug}. The {slug} token is filled from the data row. Multi-segment patterns work for nested structures, for example directory/{country}/{slug}, as long as the data carries those fields.
Resolved rows are cached in a dedicated SleekRank items table for the configured duration. Adding a row at the source adds the URL on the next refresh; editing a row updates the page. Clearing the items table forces an immediate refresh, which is the standard step after a content edit you want live now.
Yes. Mappings cover the title tag, the h1, meta description, list items inside selectors, and arbitrary inline content via CSS selectors. The base page's structured data, schema, and Open Graph image template are inherited; per-row values come through the mapping config. SleekPixel-rendered OG images are commonly wired in via the sleekRank/data/item/<slug> filter.
Yes. PageForge keeps generating posts on its existing schedule while SleekRank is configured against the same data source for the URLs that should become live. Once the new URLs are verified, the PageForge-generated posts for that dataset can be redirected or removed without affecting any other PageForge templates still in use.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Starter
EUR
per year
further 30% launch-discount applied during checkout for existing customers.
- 3 websites
- 1 year of updates
- 1 year of support
Pro
EUR
per year
further 30% launch-discount applied during checkout for existing customers.
- Unlimited websites
- 1 year of updates
- 1 year of support
Lifetime ♾️
Launch Offer
€299
EUR
once
further 30% launch-discount applied during checkout for existing customers.
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout