Bulk creator: CSV

Generating one WordPress post per CSV row with Aimogen Pro, mapping columns into prompts, and hosting the CSV remotely.

AI Content Creators › Bulk Creators › CSVs produces one post per CSV row, with the row values available as placeholders in every prompt.

This is the right tool when you already hold structured data — a product catalogue, a directory, a list of locations, an export from another system.

CSV File AI Post Creator - Unlocks Many New PossibilitiesBuilding a CSV-driven rule.Watch on YouTube

This tutorial was recorded before Aiomatic was renamed to Aimogen Pro. Some labels or interface elements may differ slightly from the current version.

How to Use Google Drive to Upload CSV Files and Generate AI Content Using ThemHosting the CSV on Google Drive so it can be updated without touching WordPress.Watch on YouTube

This tutorial was recorded before Aiomatic was renamed to Aimogen Pro. Some labels or interface elements may differ slightly from the current version.

The CSV#

First row is the header. Column names become placeholder names.
One post per subsequent row.
UTF-8 encoding. Other encodings produce mangled characters.
Upload the file, or point the rule at a URL.

Example:

csv

city,country,population,attraction
Lisbon,Portugal,545000,Belem Tower
Porto,Portugal,231000,Livraria Lello

Using columns in prompts#

Each column becomes a placeholder named after the header. With the CSV above:

Write a 900-word travel guide to %%city%%, %%country%%.

Population: %%population%%
Must-see attraction: %%attraction%%

Open with why %%city%% is worth visiting, then cover getting around, where to
stay, and what to eat. Mention %%attraction%% in its own section.
Write in %%language%% using a %%writing_tone%% tone.

The standard placeholders — %%post_title%%, %%blog_title%%, %%random_sentence%% and the rest — work alongside the column placeholders. See Placeholder reference.

Remote CSVs#

Pointing the rule at a URL instead of an upload means you can update the data without touching WordPress. The Google Drive route is covered in the second video above: publish the sheet as CSV and use that URL.

The file is re-fetched on each run, so new rows are picked up automatically.

Settings#

Shares the keyword creator settings, plus:

Setting	What it does
CSV file or URL	The source
Delimiter	Comma, semicolon or tab
Row tracking	Which rows have been processed, so a run continues where the last one stopped

Placeholders specific to this creator include %%post_original_title%% in addition to the standard set.

Practical guidance#

Clean the data first. The model will faithfully write about a typo in your CSV.

Keep rows independent. Each row becomes one post with no knowledge of the others. If posts need to reference each other, add that with internal linking rather than expecting the model to know.

Use a column for the title. Set Post Title Source so the title comes from a column rather than being invented, when you have a good title column.

Test with three rows. Trim the CSV, run it, read the output, then point at the full file.

Common problems#

Placeholders render literally The column name does not match. Placeholder names are derived from the header row exactly, including case and spaces. Rename headers to simple lowercase words.

Only the first row is processed Check the per-run limit and the delimiter. A wrong delimiter makes the whole file one column.

Accented characters are wrong The file is not UTF-8. Re-export it.

Rows are processed twice Row tracking was reset, or the rule was duplicated.

Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.