How to Bulk-Edit Meta Titles and Descriptions in Magento 2 (Without Editing Every Product)

Editing a meta title or description in Magento means opening one product, scrolling to the Search Engine Optimization section, typing, saving, and doing it again for the next SKU. That's fine for one product. It falls apart at fifty, and Magento's admin genuinely has no bulk-edit UI for these two fields — no mass-action, no inline grid edit. Here's the export-edit-import workflow that replaces it.

Why the admin grid doesn't help

The product grid's mass-action dropdown covers status, websites, and a handful of attributes you've explicitly added as grid-editable — but meta_title, meta_description, and meta_keywords aren't among them, and category-level meta fields have no bulk path at all. If you want to rewrite meta descriptions across a category of 200 products because a rebrand changed your naming convention, the only route Magento gives you is opening each product individually.

That's manageable for a handful of edits. It's not manageable for a catalog migration, a seasonal rewrite, or the routine cleanup that turns up once you actually start looking at what your meta tags say versus what they should say.

The export → edit → import workflow

The practical fix is to treat meta fields like any other bulk-editable data: pull them out to a spreadsheet, edit them where spreadsheet tools are actually good at editing text in bulk, then write them back.

Export produces a CSV with SKU (or category ID) and name alongside the current meta title, meta description, and meta keywords — so you're editing with full context, not guessing which row is which product.
Edit happens in Excel, Google Sheets, or any spreadsheet tool — find-and-replace across a naming convention, formula-driven templates for a whole category, or straightforward manual rewrites.
Import matches rows back by SKU or category ID and writes only the meta fields — nothing else on the product is touched.

Products and categories get separate export/import pairs, since they're different entities with different identifying keys and different meta field sets.

Import validates before it writes anything. A malformed CSV — missing header, wrong column count, a SKU column that got renamed in Excel — rejects the whole file with a clear error instead of partially importing and leaving you guessing which rows made it in. Values that would trigger Excel's CSV formula-injection behavior (a cell starting with =, +, -, or @ that Excel would otherwise try to evaluate as a formula) are handled safely on both export and import, rather than silently passed through.

What the import summary tells you

After an import runs, you get a per-row summary — which SKUs updated cleanly, which rows were skipped because the SKU didn't match any existing product, and which rows failed validation. That summary is what turns "I think it worked" into "here's exactly what changed," which matters more the larger the batch gets.

Export, edit in your spreadsheet, import — no per-product clicking.

See Bulk Meta Editor — from $29