Find & replace across Shopify product titles and descriptions
Updated July 2026
A supplier rebrands. Legal asks you to drop a trademarked word. The same typo turns out to be in ninety descriptions. Shopify’s admin has no find & replace — your options are editing products one by one, exporting to CSV and doing surgery in a spreadsheet, or a bulk editing app. This guide covers doing it safely, because text replacement is the easiest bulk edit to get catastrophically wrong.
Where find & replace bites
- Substring surprises. Replacing
EcowithEcoLinealso turns “Second-Economy” into “Second-EcoLinenomy.” Always eyeball the actual matches, not just the match count. - Case sensitivity cuts both ways. Case-insensitive matching catches
acmeandACME, but writes your replacement’s casing everywhere. Case-sensitive is safer for brand names; run it once per casing variant you actually have. - Descriptions are HTML. The description field is stored as HTML. A phrase can be invisible to a naive search because a
<strong>tag splits it, and a careless replacement can break markup that the theme then renders literally. - Titles feed everything. Handles, SEO snippets, feeds and order history all show the title. A mangled title on 200 products is immediately customer-visible.
The safe workflow
- Narrow the set first. Filter by vendor, collection, or “title contains” so the operation only sees products that should match. A find & replace scoped to 80 products can’t damage the other 2,000.
- Preview before → after for every product. This is non-negotiable for text edits — the substring surprises above are only visible in an actual before/after diff.
- Prefer the longest distinctive phrase. Replace “Acme Outdoor Co.” rather than “Acme” whenever you can.
- Verify, and keep the originals. Re-read each product after writing, and make sure the pre-edit text is recorded somewhere. Shopify has no version history for titles or descriptions — without a journal, a bad replacement is permanent.
Doing this with SureEdit
SureEdit does find & replace on titles and on descriptions with an explicit case-sensitivity toggle, scoped by any filter (collection, tag, vendor, type, title contains). Every affected product shows its exact before → after text in the preview; products that don’t contain the phrase are left untouched rather than rewritten. After the run, every write is re-read and verified, and the original text is journaled — one click restores it if the replacement turned out too greedy.
Try SureEdit — free plan available
FAQ
Can I use regular expressions?
Most merchants shouldn’t: an unanchored regex across a whole catalog is how titles get destroyed. Literal phrase matching with a tight product filter and a real preview covers the rebrand/typo/ wording cases with far less risk.
What about the CSV export/import route?
It works for one-off migrations, but round-tripping descriptions through a spreadsheet is notorious for mangling HTML and character encoding, and the re-import is fire-and-forget: no preview, no per-product verification, no undo.