How to Schedule CSV Listing Imports in Listdom

If another service regularly updates a CSV file with directory records, you can have Listdom fetch that file on a schedule instead of uploading it by hand each time. The Listdom CSV Addon lets you create an import job with an online feed URL, a saved field mapping, a run interval, and a batch size. Before relying on it, test the source and mapping, choose a schedule that matches the supplier’s update cycle, and check the job’s results after it runs.

This is for recurring feeds such as supplier inventories or a published spreadsheet. For a one-time directory launch or migration, use Listdom’s manual CSV import instead. The recurring job reuses a mapping; it does not remove the need to understand what each source column means or to review the resulting listings.

When a scheduled feed is a good fit

A scheduled import is useful when the same external source changes over time and provides a CSV file at a stable online address. For example, a directory might receive a supplier’s updated inventory each day, or a partner might maintain a published spreadsheet of venues. Listdom can revisit the source at the interval you choose and process its rows in batches.

Use the workflow when the source is maintained by someone or something outside your Listdom site and the file’s structure is sufficiently consistent to map. A saved mapping connects the source columns to the Listdom fields, so the recurring job does not require you to repeat those selections for every run.

It is usually unnecessary for a one-off import, a file that changes format every time, or a source you cannot make reachable to your server. The CSV URL must be downloadable without a person signing in through a browser. If the feed contains information that should not be public, do not publish it at a publicly accessible address merely to make an automated import work. Ask the feed provider about a secure delivery method or choose a different workflow.

Prepare and test the source before scheduling it

Start by asking the source owner how often the CSV changes, which columns are stable, and what a row represents. Confirm that the file can be opened from a private browsing window or another session that is not signed in to the provider. This does not prove that your WordPress server can fetch it, but it catches links that only work inside your account.

Inspect a recent copy of the file and make sure its headers and values match the structure you plan to map. Column names should be recognizable and consistent, and the file should have one listing per row. Decide which source fields belong in Listdom’s title, description, address, categories, locations, and custom fields. If you need to change the directory structure or create fields first, do that before setting up a recurring job.

Then use the ordinary CSV import workflow with a representative file and save its field mapping as a template. Include examples of common records and any important variation, such as different categories or optional values. Review several imported listings in the admin and on the public site. Confirm that values appear in the intended fields and that the source uses the same category and location wording you expect.

The scheduled importer requires a saved mapping template. Reusing a template saves repeated setup, but it also means changes to the source file need attention. If a supplier renames columns, changes the meaning of a field, or replaces one column with several, pause and review the mapping before trusting later runs. For a first import or a more involved migration, the bulk import workflow explains sample testing and field checks in more detail.

Create an Auto Import job in Listdom

After the feed and mapping are ready, open Listdom → Import & Export → CSV → Auto Import. This screen is available when the Listdom CSV Addon is installed and activated. Add a job by filling in the source URL, choosing the saved mapping, selecting an interval, setting the import size, and clicking Add Import Job.

Enter the feed URL

Paste the direct URL to the CSV file, not the page where someone views or edits it. A published spreadsheet may offer a CSV export URL; use the provider’s direct export link and confirm it returns a CSV file. The address needs to stay available to your website server without an interactive login.

Keep a record of who owns the feed and where it is managed. If the supplier changes providers or a spreadsheet is moved, the original URL may stop working. A scheduled job cannot fetch a file that has been renamed, made private, or replaced by an HTML error page.

Choose the saved field mapping

Select the mapping template you tested with a file from the same source. A template is not just a collection of similar labels: it defines how each source column is interpreted by your directory. For example, a Region field could mean a location taxonomy or a service area, depending on the supplier’s data model.

If there is no suitable template yet, return to the manual CSV import screen, map a representative file, and save the mapping. Do not guess by selecting a template whose headers merely look close. Verify the imported results before attaching the mapping to a recurring job.

Set the interval to match the source

The available intervals are Hourly, Twice a Day, Daily, and Weekly. Choose the least frequent interval that still meets the directory’s needs. If the supplier updates the feed every morning, an hourly schedule may just process the same source repeatedly without making information more current. If the records change once a week, a weekly job may be sufficient.

Agree on the expected update time with the feed owner, then leave a buffer for their export process. A schedule cannot make the upstream file publish earlier or correct missing source values. The aim is to reduce repetitive uploads while keeping the directory aligned with a realistic publishing cycle.

Set the batch size

Import size controls how many listings the job processes in a batch. Larger files are handled in chunks across scheduled runs. A smaller batch can make sense when you are cautious about the load of processing a large feed; a larger batch may reduce the number of runs needed to work through it. Start with a modest value, observe a real run, and adjust only when you understand how long it takes and how it affects the site.

For example, if a feed has several thousand rows and a job processes 100 per run, it may take multiple scheduled runs to reach the end of that file. Plan around the selected interval and batch size, especially when setting up a first job. Do not assume that the entire file finishes during the first scheduled event.

Monitor the job after adding it

Once you click Add Import Job, Listdom displays it in the Existing Jobs list. Review the source URL, mapping template, batch size, interval, and the available last-run information. After the first scheduled run, check the timestamp and the number of records processed, then inspect actual listings in the WordPress admin and on the public directory.

For the addon’s current field names and setup controls, see the Listdom CSV Addon setup guide.

Compare a few records against the source: a straightforward row, one with optional fields, and a row using a category or location that matters to visitors. Search or filter the public directory using those values. A successful job entry does not guarantee that the source data is correct or that every mapped field has the result you intended.

Treat a scheduled import as a repeatable way to fetch and process a file, not an automatic data-governance policy. The documentation describes matching behavior for repeated imports, but before relying on a feed to update existing records, test the result with your own identifiers and a staging or backup copy. Do not assume that removing a row from the source will remove its listing from the directory. Plan a separate review for listings that are no longer active in the supplier’s inventory.

The Auto Import screen provides a Remove action for existing jobs, but no edit control. If the URL, template, interval, or batch size needs to change, remove the job and add it again with the revised settings. Keep track of the intended configuration so a replacement job can be recreated correctly.

Account for WordPress scheduling and feed changes

The CSV Addon schedules its work through WordPress cron. WordPress cron checks for scheduled work when the site receives requests, so a quiet site may not run a job at the exact minute shown by its interval. If timing matters, ask your hosting provider or WordPress administrator whether a server cron is configured to trigger WordPress cron regularly. The WordPress Cron documentation explains how scheduled events are triggered.

Keep the feed’s column structure stable. If it changes, test a fresh download and check the mapping before the next run. If the source is unavailable, requires a login, returns an error page, or changes from CSV to another format, the scheduled fetch may fail. When a supplier changes its delivery process, verify both the URL and a downloaded sample rather than assuming that the old job will adapt.

For a new or substantially changed feed, use this short review:

1. Confirm the source owner, update cadence, direct CSV URL, and permitted fields.
2. Download a current sample and compare its headers with the saved mapping.
3. Test representative rows through manual import and inspect the site output.
4. Choose an interval that follows the source’s actual publishing cycle.
5. Start with a reasonable batch size and watch the first scheduled run.
6. Review processed records and active listings after the job runs.
7. Re-test after feed, mapping, or supplier changes.

Consistent listing fields make results easier for people to filter and compare. They also give public pages clearer facts to describe. Import scheduling can reduce repeated file handling, but it does not improve inaccurate source data or promise that a search engine or AI service will show a particular listing.

FAQ

Do I need an add-on to schedule CSV imports in Listdom?

Yes. Manual CSV imports are part of Listdom, while scheduled imports from a remote CSV feed require the Listdom CSV Addon. The addon adds the Auto Import workflow for recurring jobs.

Where do I set up a scheduled CSV job?

Go to Listdom → Import & Export → CSV → Auto Import after installing and activating the CSV Addon. You will need an online CSV URL and a saved field mapping template.

Can I use a Google Sheet as the feed?

You can use a spreadsheet’s CSV export link if it is reachable by your server without a manual sign-in. Check the link in a signed-out session and make sure you intend to expose the data available at that address.

How often can the job run?

The available intervals are hourly, twice a day, daily, and weekly. Choose one based on when the source actually changes and how current your directory needs to be.

Will scheduled imports update existing listings or remove old ones?

Do not assume either behavior without testing your own source and matching data. Test repeated imports in a staging or backed-up environment, confirm the effect on existing listings, and plan a separate review for records that disappear from the feed.

Why did my import not run exactly on schedule?

Listdom uses WordPress cron for scheduled imports. Its timing can depend on site traffic, so a job on a low-traffic site may run later than expected. Ask your host about a server cron if you need more reliable timing.

Can I edit a job after creating it?

The current Auto Import screen lets you remove a job, but does not provide an edit control. Remove the existing job and add a replacement with the corrected URL, mapping, interval, or batch size.

Set up your recurring feed

First verify the CSV with a manual sample import and save the mapping that produces the intended listings. Then install the Listdom CSV Addon, open the Auto Import screen, and add the recurring job with a suitable interval and batch size. Review the first run before treating the feed as routine directory maintenance.