One template in.
A draft page per term out.

You give it a title template, a body template and a list of terms. For each term it replaces {term}/{Term}/{TERM} and creates one WordPress draft page (or post). That is the whole plugin — 1.0.4 is 563 lines of PHP with no dependencies.

No. Version 1.0.0 stopped at 10 pages per run unless you had a licence key. That cap is gone in 1.0.1, along with the licence check itself. Every term you paste gets a draft. The only real ceiling is your host's PHP execution limit on a very long list. If a run gets cut short, run the same list again: since 1.0.2 a term whose page title already exists is skipped rather than duplicated, so a second run resumes instead of doubling up, and the screen tells you roughly how far the interrupted run got. In 1.0.0 and 1.0.1 that same advice would have created a second full set of duplicate drafts — the 10-page cap was quietly holding the damage down.

It did — twice, in two different ways, and both are fixed as of 1.0.3. In 1.0.0 and 1.0.1, {Term} ran every term through an unconditional Title Case, so McAllen came out “Mcallen”, DeLand “Deland”, McKinney “Mckinney”, LaGrange “Lagrange” and O’Fallon “O’fallon”, using the plugin's own default title template. 1.0.2 fixed that half: a word already in mixed case passes through untouched. But 1.0.2 still treated an ALL-CAPS word as carrying no case information and re-cased it, so HVAC repair became “Hvac Repair”, AC repair “Ac Repair”, BBQ catering “Bbq Catering”, SEO services “Seo Services” and US 1 corridor “Us 1 Corridor” — while the plugin's own admin screen sat there saying it never removes capitals. The person who found it had already checked the SHA-256 and diffed the published source against the zip byte for byte; the first list he ran it on was his own clients'. He was right, and the sentence in the box was wrong, which on a product whose only claimed edge is that you can read it and believe it is worse than a missing feature. 1.0.3 leaves an all-upper-case word of more than one character exactly as typed. The trade-off, stated because it is real: a term pasted as MIAMI now stays MIAMI rather than becoming Miami — MIAMI is also what you typed. What still cannot be recovered is a capital you never typed: mcallen becomes “Mcallen”, because nothing in the string says otherwise. Type each term the way you want it printed. Two things now stop this claim drifting again: the rule is defined once in the plugin file as LUMEN_PAGES_TERM_RULE and echoed by the admin screen rather than re-typed, and a fixture (apps/web/lib/lumen-pages-cases.json) pins 19 cases — miami, McAllen, DeLand, DeSoto, LaBelle, McKinney, LaGrange, O’Fallon, HVAC, AC, BBQ, SEO, US 1, MIAMI, mcallen and more — which are executed against the shipped file, not against a copy.

It can, if you publish the raw output. Filling one template with a list of city names produces near-duplicate pages, and that is exactly the pattern search engines discount — Google calls them doorway pages, and its spam policies describe them at developers.google.com/search/docs/essentials/spam-policies#doorways. Two things in the plugin push against it: everything is created as a draft, so you cannot publish without opening each page, and terms that would produce the same title collapse to one page. Beyond that the plugin cannot help you, but here is the checklist used on the 91 metro pages at restorationanswers.com, which were built exactly this way — it is a description of a process, not a promise about rankings, and that site's traffic is small. Make at least these differ on every page: a cost or price range specific to that place with the source named; named local detail a resident would recognise (neighbourhoods, counties, ZIPs); one rule that genuinely varies by location, such as a permit requirement or a state insurance deadline; the meta description, written per page; and the opening paragraph, so the first thing a reader sees is not the same sentence with a swapped noun. Do not leave these identical: the H1 pattern with only the place name changed, a boilerplate hero, or an FAQ block repeated verbatim. If you cannot make a page meaningfully different from its neighbours, that page should not exist — deleting the draft is a legitimate outcome of a run. The same checklist is in readme.txt, so it is in the box and not only on this page.

The zip you can download here contains no network code at all — no licence check, no update check, no analytics. 1.0.0 did contain a licence verifier and a self-hosted update channel; both were removed in 1.0.1. You can read the whole file; it is 563 lines.

It creates ordinary WordPress pages, so they render in your theme like any other page. There is no custom template, no shortcode and no page builder involved.

For now, download the new zip here and re-upload it. There is deliberately no auto-update channel: a self-hosted updater is one of the things that made v1.0.0 unfilable at WordPress.org. If the directory listing happens, updates arrive the normal way, from WordPress.org.

No. There is no checkout, no price, no licence key and no SKU. An earlier version of this page listed $149/yr and the zip repeated it — both were wrong and both are gone. The three items under “Planned” are what would have to exist before asking for money would be fair.

Quite possibly you shouldn't, and the table above this FAQ is there so you can decide without taking my word for it. Page Generator v1.8.6 has 4,000+ active installs, 4.6/5 from 70 ratings, was updated 2026-06-29, and arrives through WordPress.org with auto-updates — all of which Lumen Pages does not have. It also does more: it can list and delete what it generated, and it publishes on a schedule if you want. The one thing worth correcting, because it reads like a gap only this plugin has: CSV / spreadsheet import is not in that plugin's free tier either — the bullet sits under its own "Pro Version" heading. So on the axis a reader actually raised, both free tiers are a textarea. Lumen Pages is smaller on purpose: one file you can read end to end, drafts only, no network calls, no cap, no account. If auto-updates and a run history matter more to you than reading the code, take theirs — it is free too, and it is a better fit. Every figure here was read from the WordPress.org plugin API on 2026-07-30; the listing is at https://wordpress.org/plugins/page-generator/.