LPagery vs Page Generator Pro

Both plugins accept CSV and XLSX files and a public Google Sheet link. LPagery reads the file in your browser and shows the columns before anything is saved. Page Generator Pro reads the file on the server and expects it in the WordPress media library first, with at least two columns. Its unit of data is a Keyword, which holds all the rows of one file.

Page Generator Pro reaches more sources. It can pull rows from Airtable, Notion, a database table and an RSS feed, and its All method multiplies two lists so that ten cities and five services become fifty pages from two short lists. LPagery works one row per page, so that pairing is done in the spreadsheet.

LPagery runs a scheduled sync, hourly by default and up to weekly. Each run downloads the sheet, creates pages for new rows, updates pages whose row changed, skips rows that did not change, and deletes pages for removed rows when you turn that option on. A failed row is retried and a failed download marks the set with the error.

Page Generator Pro treats a Google Sheet as a CSV link. The sheet is read again each time you start a run, and a manual refresh button is on the Keywords screen. We found no scheduled sync in version 5.6.1 and no code that removes a page when its row disappears. Rows deleted from the sheet leave their pages published.

In LPagery the template is any page, post or custom post type you already have. You add placeholders to it and pick it in the dashboard. Every custom field on that page is copied with placeholders replaced, so builders that store their layout in post meta work through that generic path, and eleven builders have their own adapter on top. Live Mode supports Elementor and Gutenberg templates.

Page Generator Pro uses its own Content Group post type as the template. An existing page can be imported into a new Content Group, which copies its title and content. Page builder support is a list of 34 named integrations, each declaring which meta keys to copy. It also generates taxonomy terms from the same data through Term Groups, which LPagery does not have.

Both plugins write real WordPress pages. LPagery calls this Classic Mode. LPagery also has Live Mode, where each page is a small stub and the content is rendered from the template when someone opens the page. A change to the template shows on every live page as soon as you save it, with no re-run. You can switch a page or a whole set between the two modes.

Page Generator Pro writes physical pages only. Nothing points back at the Content Group after generation, so a design change means running the group again with overwrite turned on.

This is where the two plugins differ most, and it only shows on large runs or slow hosting. LPagery puts the rows in a queue on your server. A worker drains the queue, and each page is generated in its own request, so the PHP time limit applies to one page and never to the whole run. Failed rows are retried with a pause between attempts, and a run with no progress for ten minutes is shown as stalled so you know WP-Cron is not running.

Page Generator Pro has two paths. Generate via Browser loops in your browser tab. In our test we closed the tab at 260 of 320 pages, the count stopped at 270 and the group stayed at Generating until we cancelled it. Generate via Server runs the whole loop in one WP-Cron request, and it did finish all 320 pages with no browser open. The vendor documentation says this path may be forced to stop before all pages are generated, because one long request is still subject to host limits.

Page Generator Pro also has WP-CLI commands to generate, test, trash and delete content. LPagery has no CLI.

When you upload a changed file, LPagery lets you create, ignore or update existing pages. A page is updated only when its row or its settings changed. If someone edited a generated page by hand, LPagery notices that from the save and leaves the page alone unless you choose to overwrite manual changes. Pages are matched by an internal record, so they are still found after you change the permalink pattern.

Page Generator Pro updates by running the group again. Five overwrite modes decide what happens to existing pages, and you can pick which sections to overwrite: title, content, excerpt, featured image, custom fields and so on. That per-section control is finer than LPagery's. Protection for hand-edited pages is a checkbox on each page, and a page without it is overwritten. Existing pages are found by their permalink, so a changed permalink pattern makes the old pages invisible to the next run.

Neither paid plan caps the number of pages. LPagery's worker takes 1,000 rows per tick by default, and a large upload is split into parts so a small upload limit on the host does not block it. Page Generator Pro generates 1 to 500 pages per browser request, configurable in its settings. In our test it wrote 320 pages in about 30 seconds on a plain template.

Both plugins replace placeholders in the title, slug, excerpt and content, and both fill the fields of Yoast SEO, Rank Math, All in One SEO and SEOPress from the template. LPagery does this by copying every custom field of the template page, so the SEO plugin's own fields are filled without a special integration, and All in One SEO gets its own handler because it stores data in its own table. Image columns get a filename and alt text per page in both plugins.

Page Generator Pro covers eight more SEO plugins by name, among them The SEO Framework, Slim SEO, SmartCrawl and Squirrly. It can set a per-page canonical through Yoast, and it pings IndexNow when pages are created or updated. LPagery has none of those three. Neither plugin writes its own sitemap; the pages are normal posts and show up in the core and SEO plugin sitemaps. In Live Mode, LPagery updates the modified date on every page when you save the template, so the sitemap reflects the change.

Page Generator Pro has the richer template language. An @if block shows a paragraph only for rows that match a condition. Fifteen modifiers change a value in place, for example to uppercase, to a URL slug, or to a number written out in words. Related Links lists other generated pages and can order them by distance from the current page. Spintax can be evaluated on the front end, so wording changes on every visit.

LPagery has no conditional blocks and no modifiers. If a sentence should only appear for some rows, you put that sentence in its own column and leave the cell empty for the others. Placeholders can be nested, so a cell can contain another placeholder. Views build a styled list or grid of related pages on each page, ordered by name, date or a column of your choice. Columns can set the author, parent page, status and taxonomy terms of each page.

Spintax works in both. LPagery stores a seed per page, so the chosen variant stays the same when the page is updated. Page Generator Pro picks a new variant on every run, so an update rewrites the wording of every page.

LPagery generates AI text and images per row in the LPagery app and pushes the finished page set into the plugin. You pick the text model per website from six options across OpenAI (GPT-4o Mini to GPT-5.4 Mini) and Google (Gemini Flash 2.0 and 2.5). Image prompts carry style, format, mood and your brand colours, and text prompts exist in more than twenty languages, picked from your website's country. Every paid licence gets a monthly credit top-up, so there is no API key to set up.

Page Generator Pro connects to eleven text providers and five image providers with your own API keys, so the model list is longer and you pay each provider directly. Its Add New using AI wizard builds a whole campaign from a service name: it asks the provider for fifty keyword terms and then for the template content. That wizard has no equivalent in LPagery.

Figures from the WordPress.org plugin directory on the verification date. Page Generator Pro's free listing is older and has more ratings. Its Pro version is not listed on WordPress.org.

Only LPagery has two render modes with conversion in both directions, Virtual Image URLs that serve one image file under a different name per page, a stall check for dead WP-Cron, and an import path for placeholders written for the Multiple Pages Generator plugin.

Only Page Generator Pro has the All method that multiplies lists, Term Groups for taxonomy output, WP-CLI commands, import and export of its settings and groups as JSON, and an option to evaluate spintax on the front end so wording varies per visit.

We walked both admin screens with the same five-row file and counted what a new user has to learn and click before the first page is live. LPagery needs three concepts (template page, placeholder, source file) and one required setting, the template. Everything else has a default. The first page was live after six clicks on three screens.

Page Generator Pro needs seven concepts, among them that a Keyword is a dataset, that the CSV has to be in the media library first, and that Browser and Server generation behave differently. Seven settings have to be filled, and two of them look optional but default to values that import a header row as data. The first page was queued after fifteen clicks on six screens, and live once WP-Cron ran.