Content Updater applies a transformation to a field across existing WordPress records. Choose a content type, narrow the selection, select the fields and assign a function. The example is a seasonal title edit, from the sample preview to the run, with an AI agent as the alternative.
The example changes Harbour walk in winter to Harbour walk in spring and applies the same replacement to a second route title. Start with a small selection whose original values you can inspect. The transformation workflow requires the PRO add-on.
Prepare a recoverable update
Save a WordPress backup before a large content edit. For a title-only change, also export the post IDs and original titles. Keep that export until you have checked the results. To restore particular values, you can use the CSV update-by-ID workflow.
Write down the intended content type, selection and output first. For this example, the selection is two existing draft posts, the write field is Title and the replacement is lowercase winter → spring. Selecting Title makes the scope of the operation easy to review.
1. Create the transformation
Open Import Export by RockStarLab → Functions and create a function named Winter to spring titles. The function receives the current field value and returns the replacement value. Use the following body in the function editor.
return str_replace('winter', 'spring', (string) $value);
This replacement is case-sensitive. It replaces every occurrence of the lowercase substring. A title containing Winter with a capital W requires a different rule. Review the wording against your real titles before applying it. For function creation and reusable transformations, see the transformation functions guide.
You can ask an AI assistant to draft the function with this prompt.
Write a PHP transformation body for Import Export by RockStarLab. The current title is in $value. Replace every lowercase occurrence of winter with spring and return the resulting string. Show outputs for Harbour walk in winter, Winter guide and an empty string.
Review the generated code, save the function and keep it active. Check the examples in the plugin’s transformation preview before starting the update.
2. Choose the records
Open Content Updater, select Blog Posts and continue to Filter Data. For an explicit small selection, add an ID filter with In (comma-separated) and enter the IDs from your own site. The example uses two route posts. Check that Total Items to Update matches the intended selection.
The filter step also allows field-based conditions. If you choose a status or title condition for a wider edit, inspect the matching records first. See the filter guide for the meaning of common conditions. Leaving this step empty selects the content type broadly.

3. Select Title and assign the function
At Select Fields to Update, put Title in Selected Fields and check the selected-field count. You can double-click an available field to add it. Review any fields already selected before continuing.
At Field Transformations, click Assign Transformations on the Title row. Find Winter to spring titles and click Add. Enter Harbour walk in winter under Test Value and click Test Pipeline. The output should read Harbour walk in spring. Click Apply Transformations once the output is correct.


When several functions are assigned, their order determines the output. For example, converting a value to uppercase before a case-sensitive lowercase replacement changes whether that replacement matches. Start with one function when the task needs one replacement.
4. Review the update summary
Check Content Type, Total Items, Fields to Update and Transformations Applied. For this example the expected counts are two items, one field and one transformation. If the selection is larger than expected, return to Filters before starting.
Items per Iteration controls the batch size. Use a modest batch for the first run, especially if the transformation does more than a short string replacement. The batch size does not narrow the total selection.

5. Run the update and inspect the posts
Click Start Update and check the completed counts. Open View Job Log if you need the saved run or error details. The Jobs Log guide explains how to interpret progress and item results.

Open the affected post in WordPress and confirm the title, body, excerpt and publication status. A title change can also appear in a theme’s heading and navigation. Check the front end where that title is used, then clear the relevant page cache if the previous text persists.

Perform the update with an AI agent
Use the Abilities API connection guide to connect an agent to the site. The managed updater abilities are in the rsl-ie-pro namespace. Give the agent the exact site, IDs, field and approved function name.
Find the active Winter to spring titles function. For Blog Posts with IDs [your two IDs], count the selection and preview the current titles using update-count and update-preview. Prepare an update of post_title only using update-prepare. Show the selected records and function before starting.
update-preview reads selected records. Use the function’s sample test to check transformed output. update-prepare validates the writable fields and function assignments. Function mappings use positions in the fields array. With fields: ["post_title"], the first field is position 0, so its assignment is field_functions: {"0": [FUNCTION_ID]}.
Start the prepared title update with update-start and a new request ID. Follow update-status until it finishes. Read the same posts again and compare titles, body, excerpt and status. Report the processed and error counts.
Choose rules that behave correctly when repeated
The winter-to-spring rule produces the same title when run again because the lowercase source word has already been replaced. A prefix function can add the prefix twice. A percentage price increase can compound. Decide whether repetition is appropriate before restarting a job or creating a schedule.
| Task | Approach |
|---|---|
| The same text replacement across chosen titles | Content Updater with a string transformation |
| A different new title for every post | CSV update matched by destination ID |
| Whitespace cleanup | A trim transformation on selected text fields |
| Structured custom field changes | Inspect the field’s representation and test a dedicated function on a small selection |
Video walkthrough
This video was recorded with an earlier interface. Use the current screenshots above for the menu labels and update steps.
For a step-by-step find and replace in post content, with a preview before anything is written, see Bulk Find and Replace in WordPress Posts (With a Preview First).
Frequently asked questions
Does this transformation workflow require PRO?
Yes. The function-based Content Updater workflow described here uses the PRO add-on.
Can I update just two posts?
Yes. Filter by their destination IDs and verify the matching count before starting.
Does the sample replacement match Winter with a capital letter?
No. The example uses a case-sensitive replacement of lowercase winter.
Can I safely repeat every transformation?
Review the rule first. A replacement may settle after one run, while prefixes or numeric increases can apply again.
Does update-preview show transformed values?
It reads the selected records. Use the transformation test to inspect how the function changes a sample value.

Comments 0
Have a question or a tip to share? Leave it below.