How to bulk create pages in WordPress from a spreadsheet, without making doorway pages

Short answer

Use an importer or generator: WP All Import maps spreadsheet columns to pages, LPagery and Page Generator Pro fill a template from each row, MPG serves virtual pages, and WP-CLI scripts it. Whichever you use, import as drafts, give every row facts the other rows lack, and compare the pages before any go live.

Turning a spreadsheet into pages is the easy part; every tool below does it in minutes. The hard part is that a spreadsheet makes it effortless to publish two hundred pages that differ only in the town name, which is the pattern Google’s spam policies describe as doorway abuse. This guide covers the tools, then the two things that keep a bulk set safe: what goes in each row, and the checks before anything goes live.

A disclosure. Townsmith makes Local Pages Engine, which comes up at the end. The facts on the other tools come from our programmatic SEO tools comparison, tested on 5 November 2026. Versions, limits and prices change, so check them before you rely on them.

Which tools can bulk create pages from a spreadsheet?

ToolHow a row becomes a pageFree versionWatch out for
WP All Import 4.1.4You map each column to the title, the content or a fieldCSV or XML into posts and pagesCustom fields, and choosing which fields an update touches, are paid
LPagery 3.1.2Each row fills the placeholders in a template pageCSV or XLSX, up to 100 pages a run, 3 placeholdersIn our test, free pages went live at once rather than as drafts
Page Generator Pro (WP Zinc)Keyword lists, including from CSV, are combined into pagesPage Generator 1.8.7: keyword combinations, pages only, with a test modeHand edits are overwritten on regeneration unless you protect them
MPG 4.2.5 (Themeisle)Each row answers a URL from one template; no page is stored1 project, the first 50 rows of a fileEvery generated URL returns a 404 if the plugin is deactivated
WP-CLIA script runs wp post create for each rowFree; needs command-line access to the siteYou write and test the script yourself

WP All Import: map the columns yourself

WP All Import is an importer rather than a page generator. You upload the file, choose to create pages, then drag each column into the title, the content or a field, so a row with a long local paragraph becomes a page with that paragraph in it. The paid version imports into custom fields, which is how developers fill a locations post type and display it with one template; how to create location pages covers that method. Re-running an import updates the pages it made, and choosing which fields an update may touch is a paid feature, so check what a re-import will change before you run it over pages someone has edited. WP All Import for location pages goes further.

LPagery and Page Generator Pro: a template filled from each row

LPagery is the most direct spreadsheet route. You design one template page with placeholders such as {service} and {city}, upload the file, and each row becomes a page. The free version reads up to three placeholder columns and builds up to 100 pages a run. In our test it published the pages straight away rather than as drafts, so try a few rows first, ideally on a staging copy of the site.

Page Generator Pro builds pages from groups of keywords, either every combination or in sequence, and its keywords can come from a CSV. Its built-in location data, which the vendor says covers about 2.6 million cities and towns, makes it easy to generate a page for every town in a radius, which is exactly the set to be careful with. LPagery vs Page Generator Pro compares the two in detail.

MPG: virtual pages from a sheet

MPG does not create pages. Its project screen says the generated pages are virtual and will not appear under All Pages: each URL is built from the matching row when someone asks for it. A change to the sheet reaches every URL at once, but there is nothing in the Pages list to read through or hold back, so you check the set by visiting the URLs before you link to them. Themeisle’s documentation says that if MPG is deactivated or uninstalled, every generated page returns a 404. MPG and the alternatives covers when that trade is worth it.

WP-CLI: a script you control

If you can run commands on the site with WP-CLI, a short loop creates the pages with no plugin at all. This version reads a towns.csv with a header row and two columns, slug,title, and takes each page’s content from its own file, such as pages/lewes.html. Keeping the content out of the spreadsheet means a local paragraph full of commas never breaks the import, and it makes the writing a separate job for each town.

tail -n +2 towns.csv | tr -d '\r' | while IFS=, read -r slug title; do  wp post create "pages/$slug.html" --post_type=page --post_status=draft \    --post_parent=12 --post_name="$slug" --post_title="$title" --porcelain < /dev/nulldone
  • 12 is the ID of the parent page, such as “Areas we serve”; the pages land beneath it as drafts.
  • tr -d '\r' removes the Windows line endings a spreadsheet export often adds, which would otherwise end up in every title.
  • < /dev/null stops each wp command reading the rest of the list as its own input.
  • Titles must not contain commas in this simple version.

We ran it against WordPress 7.1.4 on 5 November 2026: three rows gave three drafts under the parent, with the slugs, titles and content from the files. To undo a run, this moves every draft under that parent to the trash:

wp post delete $(wp post list --post_type=page --post_status=draft --post_parent=12 --format=ids)

What should each row contain so the pages differ?

A row that holds only a town name makes a page that differs only by its town name. Every tool above will faithfully turn that into two hundred near-identical pages. The columns that make pages differ are the ones nobody can fill in from a list of towns:

  • The town, and its county where names repeat, so “Newport” lands on the right map.
  • The slug, decided now rather than after launch. Location page URL structure helps you choose.
  • A local paragraph of forty words or more, written by someone who has worked there. This is the column that matters most.
  • A named job there, with the month and year, and a photo you took on it. Photos for location pages covers places you have no pictures of yet.
  • How far it is, or how long it takes you to get there, from your base.
  • A question people there ask, with your answer. FAQs on location pages explains how to keep these from repeating.
  • Contact details only where they are real. A branch with its own number gets its own column entry; a town you travel to uses your main number. See NAP on your location pages.
  • A status column, “ready” or “hold”, so only rows with the local columns filled are imported.

Then try the cover-up test. Hide the town column and read the rows that are left. If you can still tell which row is which, the pages will differ. If every row reads the same without the town, so will the pages, and a row in that state should stay as “hold” until someone has something to say about the place. Filling the local column with reworded versions of one paragraph does not pass it: Google’s spam policies describe scaled content abuse as pages generated mainly to manipulate rankings, however they are made. The scaled content policy sets out what that means for location pages.

How do you check the pages before they go live?

  1. Import a small batch first, five or ten rows, as drafts where the tool allows it. Where it does not, use a staging copy of the site.
  2. Read three of them on a phone, one after another. If you could not tell which town you were in without the heading, neither can a visitor.
  3. Compare the closest pair, not the average. Paste two pages into our free duplicate content checker to see how much text they share. Duplicate content across location pages explains how to read the result.
  4. Check the details a bulk import gets wrong: each page’s address and parent, one H1, the title and meta description, a phone number that matches your Business Profile, and a link from a hub page. The local landing page checklist has the rest.
  5. Publish in batches, and look at Search Console’s page indexing report before the next. If many pages sit as crawled but not indexed, stop and read why location pages are not indexed.
  6. Know how to undo it before you start. The free Page Generator has a button that deletes what it generated, and WP-CLI can trash a run by parent, as above. For any other tool, find out how its pages are removed before you import two hundred of them.

Can Townsmith import pages from a spreadsheet?

Not pages, and the free plugin has no spreadsheet import at all. Local Pages Engine works the other way round: you give it a list of services and towns, it builds a page for each combination from one blueprint, and it scores every page against its closest sibling before it goes live.

  • Free: services and towns are entered in the setup wizard, where towns can be pasted as a list, one per line, up to 200 at a time. Pages are generated as drafts and scored, and wp townsmith generate scripts generation from the command line. See the command line documentation.
  • Pro: Local Pages, Import takes a CSV of services, with service and description columns, and a CSV of areas, with area, type, descriptor, lat, lng and parent, up to 1,000 rows a file. Items already there by name are skipped, never overwritten. The descriptor column is the town’s own description, which the quality score credits once it reaches fifty words. Our towns near a postcode tool downloads a CSV in the same area, type, lat and lng columns.

The text of each page’s local slot is written in the editor, or page by page in Pro’s Local content screen, not imported. So if your page content already lives in a spreadsheet, row by row, WP All Import or LPagery is the better tool. If what you have is a list of towns and services, and you want the pages built from one template and checked before they publish, that is what Townsmith is for. See features and pricing.

Common questions

How many pages should I create at once?

No more than you can read. The tools’ free limits, 100 pages a run in LPagery and 50 rows in MPG, are higher than most people can check in a sitting. How many location pages to build covers the total.

Should I import as drafts or publish straight away?

Drafts. A draft can be read, compared and fixed before Google sees it; a published page that turns out to be a near-copy has to be fixed in public, and it can drag the rest of the set with it.

Will Google penalise pages created in bulk?

Not for how they were made. Google’s spam policies are about pages made mainly to rank, whatever made them. The risk is sameness: a set of pages that say the same thing about every place reads as doorway pages however it was built.

Can I update the pages from the spreadsheet later?

With most tools, yes, at the risk of overwriting edits made by hand. MPG’s pages change as soon as its data does, and WP All Import, LPagery and Page Generator Pro can re-run, with options to protect hand edits mostly on their paid plans. A WP-CLI script can use wp post update. Townsmith updates from the blueprint rather than a sheet, and never overwrites a block you have edited.

Tools and limits checked on 5 November 2026; the WP-CLI steps were run on WordPress 7.1.4. Written by Stephen Evans, who makes Local Pages Engine.