Edit and update existing content with the AI Agent for WordPress
-
- What this tutorial covers
- Before you start — what the AI Agent can and cannot safely change
- Make targeted edits to a single post or page
- Bulk update content across multiple WordPress posts
- Refresh outdated blog posts with new information
- Change post status — draft to publish or back
- Tips for safer edits with Gutenberg blocks and shortcodes
- Next steps
- Frequently asked questions
- Can the AI Agent for WordPress edit existing posts without breaking blocks?
- Does the AI Agent for WordPress work with Gutenberg blocks and shortcodes?
- Can I use the AI Agent to bulk update multiple WordPress posts at once?
- How do I refresh outdated blog posts with AI in WordPress?
- Can the AI Agent change post status from draft to publish?
The AI Agent for WordPress uses clearly-scoped prompts to edit existing posts in place, including paragraphs, dates, links, and statuses, without breaking Gutenberg blocks or shortcodes.
The AI Agent for WordPress works directly inside WordPress to edit content you already have, not just generate new posts. It can replace a paragraph, update dates, swap outbound links, refresh older articles, bulk-edit dozens of posts, or move content between draft and publish. The key is scope. Tell it exactly what to change, and it focuses on that change without rewriting the surrounding Gutenberg layout.
What this tutorial covers
- Make targeted edits to a single post without disturbing surrounding Gutenberg blocks or shortcodes.
- Bulk update WordPress content, including text and URLs, across multiple posts in one prompt.
- Refresh outdated blog posts with new statistics, examples, and links.
- Change post status from draft to publish (or back) with the agent.
- Write prompts that scope edits precisely so the agent does not rewrite content you did not ask it to touch.
Before you start — what the AI Agent can and cannot safely change
The AI Agent for WordPress, available as a part of SiteGround AI Studio, edits content through the WordPress REST API. It reads the post or page you reference, applies the change you describe, and writes the result back.
What the agent does well:
- Paragraph, heading, and inline formatting changes inside core Gutenberg blocks.
- Find-and-replace operations across one post, a category, or the full content library.
- Date and year updates inside body content.
- Outbound and internal link replacements with anchor text preserved.
- Post status transitions (draft, publish, pending, private).
What it will not safely touch without an explicit instruction:
- Custom HTML inside Custom HTML blocks. The agent treats these as opaque unless you tell it otherwise.
- Shortcode parameters from third-party plugins.
- Theme files, plugin code, or anything outside the posts and pages tables.
- Multisite content unless you specify the network and site explicitly.
Not for you
This workflow is the wrong fit if any of these apply:
- You need pixel-level layout changes. Use the block editor or the Site Editor for those.
- Your posts depend heavily on uncommon third-party blocks the agent has never seen. Review the output post by post.
- You are running edits on a production site without a recent backup or a staging copy.
- You want the agent to generate brand-new long-form articles. See Create new blog posts and pages for that workflow.
Make targeted edits to a single post or page
Targeted edits are the highest-trust way to use the agent on existing content. You name one post, one block, and one change. The reason these prompts succeed where vague prompts fail is anchoring. Every prompt below names the post, the location inside the post, and an explicit boundary around what should not change.
Update a paragraph without breaking surrounding blocks
Use the post title as the primary anchor and the heading above the paragraph as the secondary anchor. Then tell the agent which paragraph to replace and which not to touch.
Example prompt:
In the post titled “Best WordPress backup plugins for 2026”, replace the third paragraph under the H2 “Why backups matter” with the following text: [your new paragraph]. Do not change any other paragraph, heading, image, or block in the post.
This works because the agent has multiple anchors: post title, heading, and paragraph position. Without clear boundaries, some agents may also rewrite nearby content to “improve flow.”
Change a date or specific value in existing content
Year updates and version-number bumps are among the most repetitive editorial tasks in evergreen content. The agent handles them in a single pass when you specify scope and exclusions.
Example prompt:
In the post titled “Why hourly backups matter for ecommerce”, change every instance of “2024” to “2026” in the body content only. Do not modify any date inside code blocks, shortcode parameters, the post slug, or the publish date.
The exclusions matter as much as the change itself. A reference to backup-2024.zip inside a code block must stay frozen, otherwise the snippet stops being accurate.
Replace a link without disturbing the rest of the post
Link replacements are safest when the prompt names the old URL, the new URL, and what to preserve. Anchor text is the most common casualty when a prompt is too loose.
Example prompt:
In the post titled “Best WooCommerce plugins for 2026”, replace every link pointing to oldsite.com/plugin-x with newsite.com/plugin-x. Keep the anchor text, the surrounding sentence, and the link styling exactly as they are.
If you skip the “keep the anchor text” instruction, some agents may rewrite the anchor text to match the new destination, which is rarely what an editor wants on a published post.
Bulk update content across multiple WordPress posts
Bulk updating WordPress content with AI is where the time savings become obvious. A site rebrand, product rename, URL restructure, or terminology shift across 80 posts is a large manual job. The agent compresses it into a much smaller workflow, but only when the scope is tightly defined and you run a dry-run audit first.
Two safety rails apply to every bulk operation:
- Filter before you act. Always narrow by category, tag, date range, author, or post type before running a site-wide change. A prompt that says “in all posts” will scan and modify everything, including unrelated landing pages.
- Dry-run first. Ask the agent to list affected posts before making any change. Compare the count to your expectation. If the numbers do not match, refine the filter before continuing.
Update text across many posts at once
Bulk text replacement is the right tool for product renames, terminology updates, and version bumps across a content library.
Example dry-run prompt:
List every published post in the “WooCommerce” category that mentions “WooCommerce 7”. For each post, return the title, URL, and the number of mentions. Do not modify anything.
Once the list looks right, the actual change prompt:
In all posts in the “WooCommerce” category that mention “WooCommerce 7”, replace every instance of “WooCommerce 7” with “WooCommerce 9” in body content only. Do not modify code blocks, shortcode parameters, image alt text, or post titles.
This pattern, narrow filter, dry-run, scoped change, is the difference between a useful bulk operation and a 200-post rollback.
Replace URLs across multiple posts
URL migrations are the second most common bulk task, usually triggered by an information architecture change or a site restructure.
Example prompt:
Across all blog posts published before January 2026, replace every internal link pointing to /old-pricing/ with /pricing/. Update only the href attribute. Do not change the anchor text, the surrounding paragraph, or any external links.
One thing the agent cannot fix on its own is external backlinks. Pair every internal URL replacement with a 301 redirect at the server level so inbound links from other sites still resolve. SiteGround Site Tools includes a redirect manager for setting these without touching .htaccess directly.
Refresh outdated blog posts with new information
Updating old blog posts with AI is a higher-effort task than a year bump because it combines several edit types: statistics, links, examples, year references, and sometimes structural updates. The agent handles all of these in one pass when the prompt is structured as a refresh brief rather than a single instruction.
Example refresh prompt:
Refresh the post titled “10 SEO mistakes hosting providers can prevent (2024)”. Specifically:
-
-
- Identify every statistic in the post and flag any with a source date older than 24 months.
-
-
-
- Replace flagged statistics with current 2025 or 2026 sources, citing the source URL inline.
-
-
-
- Replace every reference to “2024” with “2026” in body content and meta description.
-
-
-
- Check every outbound link and flag any that return 404 or redirect to unrelated content.
-
-
-
- Add a “Last updated: [today’s date]” line directly below the H1.
-
Do not change the H1, the article structure, the order of sections, or any of the existing examples.
Two notes on this prompt. First, the agent should flag stats it cannot verify rather than fabricate replacements. Review every flagged item against the cited source before publishing. Second, adding a “Last updated” line is one of the strongest freshness signals for both search engines and AI retrieval systems. After refreshing a post, it’s worth revisiting its SEO title, meta description, and internal links — see Optimize on-page SEO for that step.
Change post status — draft to publish or back
Status changes are the simplest edit the agent handles, but they are especially useful for editorial workflows where someone other than the writer controls the publish moment.
Single status change:
Change the status of the post titled “Hourly backups for active WooCommerce stores” from draft to publish. Do not modify the content, the meta description, the slug, or the publish date.
Bulk status change with a filter:
Change the status of every published post tagged “archive-2022” from publish to draft. Do not modify content. Return a list of affected posts after the change.
Combined edit and status change in one prompt:
In the post titled “WordPress backup guide for 2026”, update the meta description to [new description] and change the status from draft to publish. Do not change the H1 or body content.
For scheduled publishing, specify the date and timezone explicitly. Otherwise, the agent may publish immediately.
Tips for safer edits with Gutenberg blocks and shortcodes
| Practice | Why it matters |
| Reference posts by exact title or post ID | Topic-based references (“the backup post”) may match multiple posts and produce ambiguous edits. |
| Specify block-level scope (“the third paragraph block under H2 X”) | Helps prevent the agent from rewriting adjacent blocks for “flow.” |
| Exclude code blocks and shortcode parameters explicitly | Find-and-replace inside [shortcode id=”123″] can silently break the shortcode. |
| Run a dry-run audit before any bulk operation | The list of affected posts is the cheapest sanity check available. |
| Test on staging first | SiteGround Hosting for WordPress (GrowBig+) includes one-click staging environments for exactly this. |
| Take an on-demand backup before bulk operations | The SiteGround Backup Service on GrowBig+ plans supports on-demand backups outside the daily schedule. |
| Check WordPress revisions after each edit | Every block change creates a revision, so you can roll back per post from the WordPress editor. |
Next steps
Once you are comfortable with single-post edits, move to scoped bulk operations on a low-risk category such as old changelog posts, archived announcements, or a tag you rarely link to. Run every bulk operation on staging first, take an on-demand backup before changing production, and keep a side-by-side log of agent edits for the first few weeks so you can audit the failure modes specific to your content patterns. For a complete sequence that combines content refreshes with ideation, drafting, and publishing, see Content workflows: from ideation to publish.
The AI Agent for WordPress helps reduce one of the biggest editorial maintenance burdens: refreshing and updating existing content at scale.
Frequently asked questions
Can the AI Agent for WordPress edit existing posts without breaking blocks?
Yes. The AI Agent for WordPress edits content at the block level inside the WordPress REST API, so a scoped prompt that names the post, the block, and the change can modify only the targeted block while leaving the surrounding Gutenberg layout intact. Failures usually trace back to vague prompts like “update the intro” rather than a limitation of the agent itself. Anchor every edit to a specific post title and block location, and add an explicit boundary such as “do not change any other block.”
Does the AI Agent for WordPress work with Gutenberg blocks and shortcodes?
The agent works natively with core Gutenberg blocks including paragraphs, headings, lists, images, groups, and columns. It generally treats Custom HTML blocks and third-party shortcodes as opaque content unless instructed otherwise. For find-and-replace operations, always add an explicit “do not modify code blocks or shortcode parameters” instruction so a global text change does not silently rewrite a shortcode ID or HTML attribute.
Can I use the AI Agent to bulk update multiple WordPress posts at once?
Yes. The agent supports bulk WordPress update workflows across categories, tags, date ranges, authors, and post types. The recommended pattern is filter, dry-run, then change: narrow the scope first, ask the agent to list affected posts before modifying anything, then run the scoped change prompt. Bulk operations across hundreds of posts can complete in minutes rather than days, but always test on staging or a single post before running site-wide.
How do I refresh outdated blog posts with AI in WordPress?
To update old blog posts with AI, write the prompt as a refresh brief rather than a single instruction. List the specific tasks: flag and replace stale statistics with cited sources, check outbound links for 404s, replace year references in body content but not in slugs or publish dates, and add a “Last updated” line. Also specify what should not change, including the H1, structure, or examples. Review every replaced statistic against the cited source before publishing. The agent saves the find-and-fetch work, not the editorial verification.
Can the AI Agent change post status from draft to publish?
Yes. Status changes including draft, publish, pending, and private are among the simplest operations the agent handles. They can also be combined with content edits in a single prompt, for example, “update the meta description and change status from draft to publish.” For scheduled publishing, always specify the date and timezone explicitly. Otherwise, the agent may publish immediately.