Multi Page Find and Replace in WordPress: Clear Stale Details in One Pass

The phone number changed. Or the address, or the price, or the name of an old promotion. There are forty pages on the site and you do not know how many of them carry it. Opening each one takes half a day, and missing one means the wrong number sits on your site for months.

WordPress content search and multi page find and replace exist for exactly this. First it finds where the text appears, then it changes all of it in one pass. This post covers how the flow works and what to watch for in bulk writes.

Find first, replace second

Keeping the two steps separate is what makes this safe. Search lists the posts and pages containing the phrase. Do not replace before you have seen that list, because your phrase often appears in places you did not expect.

The classic case: while replacing an old phone number you discover it inside a customer review or an old announcement post. You may not want to edit a historical text. Seeing the list is what lets you make that call.

Search runs over content, not just titles, so it finds a phrase buried in the body. That is the part most stock WordPress installs cannot do.

Three checks before replacing

Keep the phrase long enough. Searching for a four digit fragment catches it in other contexts too. Search the full form, and run the spaced and unspaced variants separately.

Account for formatting. If part of the text is bold or an HTML tag sits in the middle, the string is not one piece even though it looks like one. If it does not show up in search, check the page source.

Take a backup. A bulk change is not a one click undo. WordPress keeps post revisions, but reverting forty pages individually takes longer than the replacement did.

The silent trap in bulk writes

The most important rule here: a bulk operation can partially fail. Twenty eight of thirty pages update and two are refused. Calling it done without reading the result means those two carry stale information for months.

The reasons are usually mundane: the page is locked by another user, the post type is protected, or the content lives inside a page builder's own data structure. That last one is the sneaky one, because the page looks correct in the editor while the content is stored somewhere else.

So when the operation finishes, look at how many pages were updated and which were skipped. Skipped pages come back with a reason and are usually handled individually.

If the change does not appear on the site

When the update reports success but the page still shows the old text, the problem is caching, not content. Three places to check.

• Cache plugin. Clear the page cache. Some hosts run their own caching layer and refuse cache plugins altogether, in which case you purge from the host's panel.
• CDN. If a delivery network sits in front, it may be holding the old version. Purge the relevant paths.
• Browser. The layer that fools people most often. Confirm in a private window.

Working through that order is faster than re-running the same replacement because it "did not apply".

Where else this flow earns its keep

Phone numbers and addresses are the best known case, not the only one.

• Internal links left in the body after moving to a new domain.
• Old figures still written into copy after a price update.
• The name of a service you stopped offering.
• Links to a social account you closed.
• Repeated wording after a change to legal text.

They all share a shape: the information is not in one place, it is in forty, and nobody knows which forty.

Frequently Asked Questions

Can I see where the text appears before replacing it?

Yes, and that is the recommended flow. Search lists the posts and pages containing the phrase. Review that list, then replace.

Can I undo a bulk replacement?

There is no bulk undo button. WordPress keeps post revisions so individual pages can be rolled back, but taking a backup beforehand is the right approach for a bulk job.

Why were some pages not updated?

Bulk operations can partially fail. A page may be locked, the post type protected, or the content stored in a page builder's own field. The result reports which pages were skipped and why.

The change is not visible on the site, what now?

Clear the cache plugin, then the delivery network if you have one, then your browser cache. The content can be updated while an older copy is still being served.

Does search only look at titles?

No, it searches the content body as well, so numbers, addresses and links buried in the text are found too.