Using WP All Import for location pages: when it is enough, and when it isn’t

Short answer

WP All Import is enough when each location already has its own structured data and someone can build the template: import the rows into a custom post type, then display them with one design. It is not enough on its own when rows differ only by town name, because nothing in it checks that the pages differ.

WP All Import is a general importer with over 100,000 active installs, not a location-page tool. Developers use it for location pages anyway, because it puts each spreadsheet row into a real WordPress post and then gets out of the way. Whether that is enough depends on what is in your spreadsheet, and on who will build the page that shows it.

How we checked, and a disclosure. Townsmith makes Local Pages Engine, which comes up at the end. On 5 November 2026 we installed the free WP All Import 4.1.4 on a clean WordPress 7.1.4 site for our programmatic SEO tools comparison, and for this guide we read its import settings in the plugin’s code and re-read wpallimport.com’s pricing and documentation the same day.

Is WP All Import right for your location pages?

  • Use it if you are a developer, or have one; your data is already structured and genuinely different for each location, such as real branch addresses, hours, staff and a paragraph written for each town; and it comes from somewhere else, such as a CRM or a franchise database, that you will export from again.
  • Use something else if your spreadsheet is a list of towns and one phone number, if nobody on the project can build a template, or if you want each page written and checked inside WordPress before it goes live.

What does WP All Import do, and what is left to you?

JobWP All ImportLeft to you
Getting rows into WordPressImports CSV, XML, Excel or a public Google Sheet into posts, pages or a custom post typeA clean file with one row per location
The post typeImports into any registered post typeRegistering a “locations” type, with code or a plugin
Fields such as address and hoursCustom fields are a paid featureCreating the fields
The page designNothingOne template for the post type, in your theme or page builder
Updating from a new fileUpdates the posts that import created; everything, by defaultChoosing which fields an update may change
Scheduled importsPaid; automatic scheduling is a separate $19 a month serviceOr a cron job you set up
Checking that pages differNothingAll of it
Schema, links between locations, mapsNothingTheme, SEO plugin or code

How do people build location pages with it?

The usual pattern has five steps, and WP All Import does the third.

  1. Register a post type for the locations, such as locations with addresses under /locations/, and decide its fields: address, phone, opening hours, coordinates, a local paragraph, a photo. Location page URL structure helps with the address.
  2. Build the spreadsheet, one row per location and one column per field, with a column that uniquely identifies each row and never changes. The columns that make pages differ matter more than the rest; bulk creating pages from a spreadsheet lists them.
  3. Run the import. Under All Import, New Import, upload the file and choose the post type, then drag each column into the title, the content or a field. Set the post status to Draft in the third step, which WP All Import’s FAQ describes, so nothing goes live yet.
  4. Build one template for the post type that shows the fields: a single template in a block theme, a theme file, or a page builder’s theme builder. This is the part WP All Import does not touch, and it is usually the biggest job.
  5. Re-run the import when the data changes. It finds the posts that import created, by the identifier column, and updates them.

There is a simpler route with the free version: write each location’s whole page body in one column and import it into the post content, so no template is needed beyond your theme’s. It works, but you end up writing and maintaining HTML in spreadsheet cells, and the town’s content lives in the sheet rather than in WordPress.

For a fuller walkthrough of this setup with ACF and a page builder, including how to stop the pages becoming find-and-replace copies, see The Search Foundry’s guide to scaling local landing pages without spam penalties.

What does WP All Import cost?

The free plugin on WordPress.org imports into titles, content and the other standard post fields. Its readme lists what the paid version adds: custom fields, images, files fetched from a URL, recurring imports that add, edit and delete posts as a remote file changes, and your own PHP functions run on the data.

The paid price was in flux when we checked. The pricing page on 5 November 2026 said all plugins currently come with a lifetime licence whatever else the site says, that the company is testing a switch to annual pricing, and that this was the last chance to buy a lifetime licence. It showed two different sets of prices that day:

  • Developer at $149 a year, with custom fields; Professional at $299 a year, adding the ACF, Meta Box and JetEngine integrations and manual scheduling; and Unlimited Lifetime at $1,299 once.
  • An Import Pro package at $199 a year, single plugins from $99 a year, and a lifetime licence at $1,299 in one place and $1,399 in another.

The terms were the same in both: unlimited sites, including client sites, and a 90-day refund. If a licence expires, the plugins keep working without updates or support. Automatic scheduling of imports is a separate service at $19 a month for unlimited sites, according to its scheduling documentation; the alternative is setting up the cron jobs yourself. If your fields are made with ACF, budget for the package that includes the ACF integration.

What doesn’t it do?

Nothing checks that the pages differ

Import 200 rows that differ only by town name and you get 200 posts that differ only by town name, with no warning. WP All Import has no similarity check, no spintax and no variation tools; we found none in its listing or documentation. That set is the pattern Google’s spam policies describe as doorway abuse, whichever tool made it. Before you publish, compare the two pages most likely to be alike with a duplicate content checker.

Updates can overwrite hand edits

In 4.1.4’s import settings, re-running an import updates the existing posts it created, and the default is to update all data. So if someone improves a location page in WordPress and the import runs again, their change to any field the spreadsheet also supplies is replaced by the spreadsheet’s version. The alternative is to choose which data to update and untick the fields people edit by hand, such as the content. WP All Import’s pricing page lists choosing which data to update as a paid feature, though the option also appears in the free 4.1.4 plugin’s settings, so check what your version offers before the first re-run. Skipping posts whose rows have not changed is marked as a paid option in the free plugin.

The safest rule is to give every field one home. Address, hours and phone live in the spreadsheet and are updated by the import; the local paragraph and photos live in WordPress and the import never touches them. Write that rule down where the next developer will find it.

No places, schema or links of its own

WP All Import brings no list of towns or coordinates; you supply them. It writes no LocalBusiness schema, builds no hub page or links between locations, and draws no map. Those come from your theme, an SEO plugin or code, and each is a separate job: internal linking for local SEO and adding a service area map cover two of them.

When is it the right choice?

  • Branch data that lives in another system. A franchise or branch network whose addresses, hours and managers are held in a CRM or head-office database can export them and re-import on a schedule, so the website never drifts from the source.
  • An agency that already builds custom post types. If your sites are built from post types and custom fields anyway, the location pages are one more post type, and the licence covers unlimited client sites.
  • Rows that are different in substance. When each row carries facts no other row has, a team, a car park, a local paragraph someone wrote, the importer is all you need to move them, and the template does the rest.

It is not the right choice when the spreadsheet is the town list and nothing else. The importer will turn that into pages perfectly, and the pages will be the same page with a different name. Write the local content first, or build fewer pages; how many location pages to build sets out the test.

How do you run it safely?

  1. Import five rows first, as drafts, and read the pages on a phone.
  2. Keep the identifier column stable. Change a row’s identifier and the next run treats it as a new location rather than updating the old post.
  3. Decide which data an update may change before you run the import a second time, not after.
  4. Re-runs only touch posts that import created. To update pages that already exist on the site, choose the existing-items option at the first step instead.
  5. Publish in batches and watch Search Console’s page indexing report; if pages sit as crawled but not indexed, read why location pages are not indexed.

Where Townsmith fits

Local Pages Engine works the other way round. Rather than importing finished rows, you enter the services and towns in WordPress, design one blueprint in the block editor, and it builds a real page for each service in each town. Every page starts as a draft and is scored from 0 to 100 against its closest sibling, so a set that reads as copies is caught before it goes live, and each page has a named slot for the local detail only you can write. Blueprint changes are previewed page by page and never overwrite a block you have edited, which removes the overwrite problem above. The free plugin has no cap on pages; Pro adds CSV import and export of services and towns, not of page content. See features and pricing.

If your page content already lives in a spreadsheet, row by row, or your post type and template are already built, WP All Import is the better tool and Townsmith would get in the way. For comparisons with other generators, see programmatic SEO tools for WordPress and MPG and its alternatives.

Common questions

Is the free version of WP All Import enough for location pages?

Only if everything goes into the title and the content. Address, hours and coordinates in their own fields, which is what a template needs, require the paid version, as do images.

Can WP All Import design the location page?

No. It fills posts with data. How a location page looks comes from your theme’s template for that post type, or from a page builder.

Can it import from Google Sheets?

Yes. Its readme says to paste a public sheet’s URL into the option for downloading a file. Importing again automatically as the sheet changes needs the paid version and either the scheduling service or your own cron job.

Does it work with Rank Math or Yoast?

Yes. WP All Import publishes free add-ons on WordPress.org for both, one for Rank Math and one for Yoast SEO, which let you import each page’s SEO title, meta description and other settings from the same spreadsheet. The SEO plugin then handles the pages like any others.

Plugin checked and prices read on 5 November 2026. Written by Stephen Evans, who makes Local Pages Engine.