Import CSV into WordPress

To import CSV into WordPress, add the CSV as a source in Ingestics — either a hosted CSV URL (including a published Google Sheets link) or an uploaded file — map each column to a WordPress field, and publish. Unlike a one-shot importer, the same source can be re-fetched on a schedule, so a spreadsheet your team maintains becomes content that updates itself.

This guide covers both routes: CSV by URL on the Free tier, and File Import for local and remote files on Lite.

Why is CSV useful for WordPress automation?

CSV is the plainest structured format there is: one header row naming the columns, one row per item. Every spreadsheet tool exports it, every non-technical teammate can edit it, and no API documentation is required. That makes CSV the right source whenever a human curates the data:

• Curated directories — vendors, tools, members, resources
• Editorial queues — writers fill rows, WordPress drafts appear
• Events and schedules — dates, venues, descriptions in columns
• Controlled product or listing sets — small catalogs without a full feed

A typical source looks like this:

title,description,category,image_url,link
"Spring Workshop","Half-day intro session","Events","https://…/img.jpg","https://…"

How do you import a CSV file into WordPress with Ingestics?

Step 1: Prepare the CSV

Keep the header row simple and consistent: lowercase names, no merged cells, one item per row. Columns you will typically want: title, description or body, category, image URL, and any custom values (price, date, location).

Step 2: Add the CSV as a provider

For a hosted CSV URL, open Ingestics → Providers and add an API provider pointing at the URL — CSV parsing is built into the Free tier. For Google Sheets, publish the sheet and use its CSV link; Ingestics normalizes Google Sheets share and edit URLs to CSV export endpoints automatically, so pasting the ordinary sheet URL works.

For an uploaded file (local CSV, or XLSX), use File Import on the Lite tier. Uploaded sources are held in private storage outside the web root where the server allows it, and you get a sample mapping preview before anything is imported. File Import also handles remote CSV, JSON, XML, and XLSX sources and runs large files in background batches.

Step 3: Preview and map the columns

Use the preview to confirm Ingestics parsed the rows correctly, then map columns to WordPress fields: title → post title, description → content, category → category, image_url → featured image (sideloaded into the Media Library), link → attribution or a meta field. On Pro, the Advanced Field Mapper routes columns into post meta or ACF fields.

Lite’s Post Template Builder is worth using here: compose the post title, content, and excerpt from placeholders — combining several columns into one readable layout — and check it against a sample row before running the import.

Step 4: Set the publish mode and run a test

Choose Draft for the first run and import a small batch. Check the results in the editor: encoding, line breaks, images, category assignment. Duplicate detection is on by default, so re-running the import will not duplicate rows already published.

Step 5: Schedule repeat imports (Lite and above)

For URL-based CSV sources, enable scheduled fetching and pick a cron interval. New rows become new posts on the next run; duplicate checks skip everything already imported. This is the difference between a CSV import and CSV automation — the sheet becomes a live content source. On Pro, the Advanced Sync Engine can also match existing posts (by external ID, title, slug, or custom meta) and update them when a row changes, instead of creating new posts.

What is the recommended CSV-to-WordPress field mapping?

What are the best practices for CSV imports?

• Lock the header row. Renaming a column silently breaks the mapping; treat headers as an interface.
• Validate one row first. One clean test row catches encoding and format issues before a 500-row run.
• Use Draft mode for new sources, then switch to Publish once a full batch has come through clean.
• Keep IDs if rows update. A stable id or sku column lets Pro’s sync engine update rather than duplicate.
• Watch the Activity Log. Every run records rows fetched, published, and skipped — your first stop when counts look off.

How does CSV compare with other import formats?

CSV is for human-curated, tabular data. If your source is a live service, use the REST API guide; for supplier or listing feeds, XML is more common; for editorial streams, RSS wins. Ingestics handles all of them from the same Providers screen, so a site can mix a curated CSV directory with live API data. For a spreadsheet-first walkthrough, see the Google Sheets to WordPress guide.

Which Ingestics plan do you need for CSV automation?

Free parses CSV from URLs (including Google Sheets) with manual fetch — enough to prove the workflow. Lite adds scheduled fetches, File Import for uploads and XLSX, the Post Template Builder, and frontend display via shortcode and block. Pro adds sync updates and meta/ACF mapping. The pricing page has the full tier table.