How to Bulk Edit Google Shopping Fields in Shopify

First, work out which layer you are editing

But before you buy anything, settle a distinction that trips up almost everyone. There are two separate layers feeding Google, and they are edited in different places. So the first question is not which tool to use. Instead, it is which layer your missing data actually lives in.

Layer one: the product category and its attributes

This is the native Product category field on the product itself. Shopify defines it as “the standard category of a product from Shopify’s Standard Product Taxonomy”, and setting it unlocks category-specific metafields.

In other words, those category metafields are what the taxonomy calls product attributes. So choosing the right category is not admin busywork. It decides which attribute fields even exist on your products.

Layer two: the Google-specific metafields

Some Merchant Center attributes have no home in the taxonomy. For those, the Google & YouTube channel reads custom data you add under Settings → Custom data, using the namespace mm-google-shopping with attribute names matching Google’s own. Those values then appear in your product feed.

Why this matters for your store: layer one travels everywhere, while layer two exists only for Google. Fix the category first, because it changes what layer two still needs to cover.

The mapping to Google is not automatic

But this is the assumption worth killing early. Shopify will map your products if you already have Google Product Categories, but only under a condition it states plainly: “Your Google Product Category needs to match Google’s values in English, or the ID.”

So a near-miss category name does not quietly resolve itself. It simply fails to match, and you are left guessing why a product never appears.

Meanwhile, one extra wrinkle catches social sellers. If customers check out directly on Instagram or Facebook, you must supply Google Product Categories for tax reasons, even when a standard Shopify category is already set.

The bulk edit path Shopify documents

Here is the part most merchants never find. Shopify’s bulk editor handles metafields directly, across products, variants, collections and customers. So a real Shopify bulk edit Google Shopping fields workflow looks like this:

1. Go to the Products page in your Shopify admin.
2. Use the checkboxes to select each product you want to edit.
3. Click Edit products.
4. Click Columns.
5. Under the Metafields section, choose the metafields you want to modify.
6. Click into the table and type the new values.
7. Click Save.

As a result, you now have a spreadsheet-style grid of your catalogue. Tab across it, and a field that took nine clicks per product takes seconds.

Use Chrome, Firefox or Safari for this

Shopify documents one specific browser trap, and it is an odd one:

Because the bulk editor encodes your column selection into the URL, a long selection can exceed what Edge accepts. So if saves fail silently on a wide edit, change browser before you debug anything else.

If the Google fields are not in your Columns list

They appear once the Google & YouTube channel is installed and your products have a category assigned. That is expected behaviour rather than a fault, since the channel is what defines those fields in the first place. Install it, set categories, then reopen the bulk editor.

Which guide do you want?

This post is about changing feed data at scale. If you are earlier than that, go sideways:

• Which fields matter, what “complete product data” means field by field, and how to spot thin data: How to Connect Shopify to Google Merchant Center.
• What Shopify’s native SEO fields do and do not let you batch: Shopify’s Built-In SEO Features.

What the bulk editor will not touch

Its reach stops at metafields and core product fields. It does not cover your meta title, meta description, image alt text or URL handle.

That boundary confuses people, because all of it feels like “SEO fields”. But Google Shopping attributes and search-result metadata are different systems that happen to live in the same admin.

Those fields are still bulk-editable, just somewhere else

Not reachable in the bulk editor is not the same as one-at-a-time. Shopify’s product CSV export carries columns for SEO title, SEO description and Image alt text. So you can export, edit in a spreadsheet, and re-import with “Overwrite products with matching handles” to update existing products in bulk, with no app involved.

Leave the URL handle column alone. It is in the file, but it is also the key the import matches on. Edit it in the spreadsheet and Shopify finds no match: instead of renaming the product it creates a second, duplicate one, and sets up no redirect from the old URL. Handles stay a per-product job in the admin.

Two more limits. This is the product CSV, so it reaches products only — collections, pages and blog posts have no equivalent export for these fields. And straight from Shopify’s own documentation: on import, a blank non-required column overwrites the existing value as blank. A spreadsheet missing a column you did not intend to touch will empty that field across your catalogue. Export first, work on that export, and change only what you mean to.

So the honest split is not “bulk versus manual”. It is which surface you use: the bulk editor for feed attributes and metafields, a CSV round-trip for the search-listing fields, and an app when you want the copy written rather than retyped.

The two feed fields worth fixing first

Title and description. That is because both are plain product fields, both are read straight into your feed, and both do more work than any identifier you will ever set.

Here’s why. Weak titles are the common failure. A vague title matches far fewer queries than a specific one, so the product quietly competes for less. Identifiers like GTIN matter too, but they help Google match your product rather than decide what it is relevant to.

Honest scope on our side: Plug In AI bulk-generates titles, descriptions, meta fields and alt text. It does not set your product category, GTIN, condition or any Merchant Center attribute. Those stay in the admin workflow above. We have shown the bulk-generation side in practice on 400 blank collection pages, and products work the same way.

So the realistic division of labour looks like this. Use the bulk editor for structured attributes, and use AI generation for the copy that no structured field can write for you.