DEV Community: Arvio AI

How to bulk edit product descriptions in Shopify

Arvio AI — Mon, 24 Aug 2026 23:16:55 +0000

This is a repost. Originally published on the Arvio blog: https://arvio.a.xyz/blog/bulk-edit-product-descriptions-shopify. The canonical URL points back there.

Key takeaways

Shopify's built-in bulk editor can edit descriptions. The column is just switched off by default, which is why most people conclude it can't.
Typing — not writing, just typing — one 147-character description took 19.6 seconds in our test, and that was at a machine-steady pace faster than most people type. Fifty products is about 16 minutes of pure typing. Five hundred is nearly three hours.
A description-only CSV will not import. You need five columns, and one row per variant. The two error messages you'll hit are quoted in full below.
Shopify's current CSV template calls the columns URL handle and Description. The older names, Handle and Body (HTML), still import correctly — we imported 50 products with them on 19 August 2026.
The setting that silently loses your work is Overwrite products with matching handles. Leave it unticked and Shopify skips every product you were trying to change.

Published 21 August 2026 by Adot Technologies Inc, the team behind Arvio. Every step below was run in a live Shopify admin in August 2026; the timings are stopwatched, not estimated. Method in full at the end.

The video version

The same three methods on screen, in 6 minutes 57 seconds — including both CSV import failures exactly as the admin reports them, and the stopwatch running while one description is typed. Watch on YouTube.

The quick version

Under ~50 products: Products → select → Bulk edit → Columns → tick Description. Edit them in a grid. Costs nothing, built in, and the fastest way to touch a lot of products by hand.
Working in a spreadsheet, or handing the copy to someone else: export a product CSV, keep five columns, tick Overwrite products with matching handles, re-import.
Past the point where writing them all by hand is realistic: generate drafts, review them, then publish the ones you approve.

Neither of the first two writes a single word for you. That's what the third section is for.

Why this is harder than it should be

Shopify's product admin is built around editing one product at a time. The bulk editor exists, but it opens with a default column set — title, price, inventory, status — and Description is not in it. There is no message telling you the column exists; you have to know to go looking in the Columns picker.

That single default is why the top results for this question are full of people saying the built-in editor can't do descriptions, and why so many merchants jump straight to a paid app for something their admin already does.

Method 1 — the built-in bulk editor

Products → tick the products you want → Bulk edit.

The checkbox in the header row selects everything on the page. Once the grid opens:

Click Columns (top right) and tick Description. That's the whole trick.

While you're in that picker, media, tags, product type, vendor, template and your sales channels are one tick away too, editable in the same grid.

Now every description is in one grid. Click a cell, type, move on, without a product page loading in between. Save when you're done.

The "Editing 15 products" thing is not a limit

Select fifty products and the grid header will tell you it's editing far fewer than fifty — 15, in our run. This looks like a cap and gets reported as one. It isn't. It's lazy loading: scroll down and the header climbs to 35, then 50. The full list of fifty is in the URL's ids= parameter the entire time.

What it actually saves you

We stopwatched it. Typing one real 147-character description — not composing it, just typing it — took 19.6 seconds.

Products	Pure typing time
50	~16 minutes
200	~1 hour 5 minutes
500	~2 hours 43 minutes

That's typing only. It excludes deciding what to say, which is the part that actually takes the time.

Method 2 — export, edit and re-import a CSV

Better when you want to work in a spreadsheet, or when someone else is writing the copy.

Products → Export → Plain CSV file. Then edit, then Products → Import.

The five columns that work

A description-only file does not import. We tried, twice, and both failures produce error messages that are worth quoting because nothing seems to document them:

A product title column is required.

That's what you get with just the handle and the description. So you add the title — and if any product has variants, you then get:

Product options input is required when updating variants.

What works is five columns, with one row per variant:

Column	Why it's there
`URL handle` (older name: `Handle`)	Matches the existing product
`Title`	Required even when you're not changing it
`Option1 name`	Required if the product has variants
`Option1 value`	One row per variant
`Description` (older name: `Body (HTML)`)	This is the description field

On the column names: Shopify's current template — product_template.csv, checked verbatim in August 2026 — uses URL handle and Description. Most guides still teach Handle and Body (HTML), and we can confirm those legacy names still import: the 50-product catalogue we used for this article was itself imported with a Handle / Body (HTML) file on 19 August 2026, and all 26 descriptions in it landed. Either set works today. The current names are the safer bet for the future.

The setting that decides whether any of it lands

Overwrite products with matching handles. Leave it off and Shopify will not touch your existing products at all — your edits quietly don't land and nothing tells you why. Tick it and the preview says it in plain words: existing products will be overwritten.

It matches on the handle, not the title, so renaming a product doesn't break the match.

What a CSV import leaves alone, and what it destroys

This is the part that costs people data, and all three rules are in Shopify's own documentation:

"If a non-required column isn't included in the import CSV file … then the value in the product list remains the same."

A column you leave out entirely is safe. Your images, prices and inventory are untouched by a five-column file.

"If a non-required column in the import CSV file is blank, then the matching value in the product list is overwritten as blank."

A column you include but leave empty erases the existing value. Most people expect the opposite of one of these two, and it's usually this one.

"Changing data in the Option1 value, Option2 value, or Option3 value columns … deletes existing variant IDs, and creates new variant IDs."

This one matters because Method 2 requires you to include the option columns for variant products. Export them and re-import them unchanged and you're fine. Retype them, tidy the capitalisation, or let a spreadsheet "helpfully" reformat them, and you have replaced every variant ID on those products — which breaks anything keyed to variant IDs downstream.

Three more from the same documentation, all worth knowing before you start: the file can't exceed 15 MB, it must be UTF-8 with LF linefeeds, and opening it in Excel can corrupt image links. Back up before importing.

Method 3 — generating the drafts

Disclosure: Arvio is our own product. It's third here on purpose: the two methods above need nothing from us, and if that's all you came for, you can stop reading here.

Everything above saves you clicks. Neither method writes a word. Past a few hundred products, how fast the grid is stops being the problem. Somebody still has to write 500 descriptions.

So here's what that looks like, on the same 69-product demo store used throughout this article — 23 of which had nothing in the description field at all.

Asked in plain English to improve my product copy, deliberately without being told which products:

It looked for the best sellers first — and said so when it couldn't find any. The store has no order history. Rather than pick something and proceed, it reported the gap, pulled the whole catalogue instead, and counted what was actually missing: 23 empty descriptions, 23 missing SEO titles, 60 products with no image alt text. Then it stopped and asked what "top products" should mean, given there were no orders to rank by.

It drafted, and it did not publish. Told to write one for each of the 23, and to show the drafts rather than apply them, it returned 23 drafts on screen. We checked the store afterwards, independently of the tool's own report: all 23 descriptions were still empty. Nothing had been written.

That distinction, a draft queue rather than an autopilot, is why we built it that way. Bulk generation that writes directly to a live catalogue is a fast way to need a bulk undo.

The two runs took 127 seconds to plan and 323 seconds to draft 23 descriptions.

When you should not bother with any tool

If you have fewer than about fifty products, or descriptions are the only thing you're changing and you already have the copy written, the built-in bulk editor is the right answer and everything else is overhead. Use Method 1 and skip the rest of this section. It's already open in your browser, and it will take you twenty minutes.

Five things that go wrong

Ticking nothing and importing anyway. Without Overwrite products with matching handles, the import "succeeds" and changes nothing.
Including a column you meant to leave alone. A blank cell in an included column erases the live value. Delete the whole column instead.
Retyping the option columns. New variant IDs, silently.
One row per product instead of one per variant. Produces the "Product options input is required" error, or drops variants.
Editing the CSV in Excel. Image links can be mangled on save. Use a plain-text-safe editor or Google Sheets, and export as UTF-8.

Which method for which catalogue

Situation	Use
Under ~50 products, copy already written	Built-in bulk editor
Copy written by someone outside your admin	CSV export → edit → re-import
Hundreds of products, copy not written yet	Generate drafts, review, then publish
One product, one field	Just open the product

FAQ

Can you bulk edit product descriptions in Shopify without an app?

Yes, two ways, both built in. The bulk editor handles it once you enable the Description column in the Columns picker, and the CSV export/import route handles any number of products. Neither costs anything.

Why is there no Description column in the Shopify bulk editor?

There is — it's just off in the default column set. Click Columns at the top right of the bulk edit grid and tick Description. This is the single most common reason people conclude the built-in editor can't do descriptions.

What is the Body (HTML) column in a Shopify CSV?

It's the product description. Shopify's current export template calls it Description; Body (HTML) is the older name for the same field and still imports correctly as of August 2026.

Why does my Shopify CSV import say "A product title column is required"?

Because your file has no Title column. Shopify requires it on import even when you're not changing the title. Add it and re-export the existing titles rather than retyping them.

Why does my import say "Product options input is required when updating variants"?

Because at least one product in the file has variants and your file has no option columns. Include Option1 name and Option1 value, with one row per variant.

Does importing a CSV overwrite my product images and prices?

Not if those columns aren't in your file — Shopify leaves out-of-file columns untouched. But a column that is in the file and left blank will be overwritten as blank. That asymmetry is where most accidental data loss comes from.

How many products can the Shopify bulk editor handle at once?

More than the header implies. Selecting 50 showed "Editing 15 products" until we scrolled, at which point it filled in to 50. The real constraint on the CSV route is the documented 15 MB file limit, not a product count.

How long does it take to write 500 product descriptions?

Typing alone, on our measurement, about 2 hours 43 minutes — and that excludes composing them, which is the larger half. That's the number worth having before you decide whether to do it by hand.

Method

One Shopify store, 69 products, 50 of them a synthetic catalogue we built for this purpose and 19 pre-existing. All steps run in a live admin between 19 and 21 August 2026, in English, on desktop Chrome.

The 19.6-second figure is a single measured run of typing one 147-character description into the bulk edit grid, timed with a stopwatch inside the recording, at a steady 110 ms per keystroke. That is faster than most people type, so treat the per-product timings as a floor rather than an estimate of your afternoon. It measures keystrokes only — composing the text is excluded, and on real copy that is the larger cost.

Exclusion: the two CSV failures we quote were reproduced on this store's own export; we did not test a store with 3+ option dimensions, custom metafield columns, or a catalogue near the 15 MB limit, and we would not assume the same error messages there.

Quotations from Shopify's documentation are copied verbatim from the CSV import guide and the column names from the official template, both checked in August 2026.

Related: Your SEO app found 400 missing meta descriptions. Now what? — the same CSV route applied to SEO fields, including the current column names and which flagged items are actually worth fixing.

Related: Shopify App Store Ads: what 310,000 impressions say about Relevance, bids and dead keywords — keyword-level data from our own ad account.

Written by Adot Technologies Inc, the team behind Arvio: AI Store Operator — ask for a bulk change in plain language, review every edit before it goes live, and undo anything.

Originally published at https://arvio.a.xyz/blog/bulk-edit-product-descriptions-shopify. More Shopify bulk-editing writeups are on the Arvio blog.

How to change prices in bulk in Shopify

Arvio AI — Mon, 24 Aug 2026 23:11:44 +0000

This is a repost. Originally published on the Arvio blog: https://arvio.a.xyz/blog/bulk-price-change-shopify. The canonical URL points back there.

Key takeaways

Price is already in the bulk editor's default columns. Unlike Description, you don't have to go looking for it. What isn't there is any way to say "plus 10%" — the grid gives you cells, and you type each new number.
The unit of work is the variant, not the product. In our test catalogue, 50 products came to 88 variants. Whatever number you have in mind for "how many prices", it is probably about 1.8x larger.
Timed: changing three prices by hand in the grid took 16.93 seconds, or 5.64 seconds per row, at a machine-steady pace. Extrapolated to a 500-product catalogue at the same variant ratio, that's roughly 1 hour 23 minutes of pure typing — before you decide what any of the new prices should be.
The CSV route needs five columns, and one row per variant. The one that decides whether any of it lands is the Overwrite products with matching handles tick.
Cost per item is not a default column in the grid. Which means the view you reprice in doesn't show you whether a new price still clears what the item cost.
The AI route on the same store, end to end: 5 minutes 46 seconds from pressing enter to the last price written — 2 minutes 17 seconds of that spent producing a preview you approve before anything is saved. And read that preview: three variants moved by more than the 10% we asked for.

Published 23 August 2026 by Adot Technologies Inc, the team behind Arvio. Every step below was run in a live Shopify admin in August 2026; the timings are stopwatched inside the screen recordings, not estimated. Method — including what we could not verify — in full at the end.

The video version

Sixteen seconds of it: prices going in one at a time, then the same job as a single prompt, with the confirmation card and its old → new list in between. Watch on YouTube.

The quick version

A handful of prices: Products → tick them → Bulk edit. Price is right there in the grid. Type, tab, done.
A percentage, or anything that needs maths: export a product CSV, do the arithmetic in a spreadsheet, re-import with Overwrite products with matching handles ticked. Nothing in the Shopify admin will compute the new prices for you.
The whole catalogue, or a rule with exceptions: describe the change once, then read the preview line by line before you approve it.

The first two are very good at applying prices you have already decided on. Deciding them is still your problem, and neither route puts cost anywhere you can see it while you work.

Why "just change all my prices" is harder than it sounds

Four things get in the way, and you meet all four in the first five minutes.

Prices live on variants. A product with three sizes has three prices. Our 50-product test catalogue has 88 of them, so anyone sizing a repricing round off their product count is sizing it off the wrong number.

The product list pages at 50. The header checkbox selects the page, not the catalogue. On a 500-product store that is ten separate rounds, and nothing on screen tells you it isn't one — you can finish believing you covered everything when you covered a fifth of it.

There is no percentage field. The bulk editor is a grid of cells. In the grid we used in August 2026, a 10% increase means computing 88 new numbers somewhere else and then typing 88 numbers in.

Margin is invisible by default. Cost per item exists on the variant. It is not one of the columns the grid opens with.

Method 1 — the built-in bulk editor

Products → tick the products you want → Bulk edit.

The grid opens with a default column set — title, price, inventory, status — and unlike descriptions, price is in it. There is nothing to switch on. Click a price cell, type the new number, tab to the next.

While you are in Columns (top right), add Cost per item. Then each price sits next to what the item cost you. Without it you are changing prices with the other half of the decision off screen.

What this costs, measured. We recorded ourselves changing three prices in the grid — click the cell, type the new price, move on:

Row	Old	New	Typing
Randers Wine Rack	34.95	38.45	1.71 s
Oak Serving Spoon Set	48.50	53.35	1.67 s
Roskilde Large Canister Set (variant)	74.00	81.40	1.60 s

Three rows: 16.93 seconds. 5.64 seconds per row. Only about a third of that is typing. The rest is hunting for the right cell and clicking into it.

Scale that at the variant ratio we measured (1.76 variants per product):

Catalogue	Variants	Pure typing
50 products	88	8.3 minutes
200 products	~352	~33 minutes
500 products	~880	~1 hour 23 minutes

Two things about that table before you use it. The pace is scripted and machine-steady, which makes it faster than most people type, so read the numbers as a floor. And it is keystrokes only: deciding what each new price should be isn't in there, and on a real repricing round that is the larger half.

Method 2 — export, do the maths, re-import

This is the only native route that can apply a percentage, and only because the arithmetic happens in your spreadsheet rather than in Shopify.

Products → Export → CSV for Excel, Numbers, or other spreadsheet.

The export is wide — the file we imported on 19 August 2026 carried 25 columns. You do not need most of them. The restore file we built for this store is 88 rows and five columns:

Handle,Title,Option1 Name,Option1 Value,Variant Price
kolding-serving-spoon-set,Kolding Serving Spoon Set,Size,Large,18.95

That is the same five-column shape that imported cleanly when we did this for descriptions, with Variant Price in place of the description column. Title is required on import even though you are not changing it. Option1 Name and Option1 Value are required as soon as any product in the file has variants — and they are what makes each row address one price rather than one product.

Then, in your spreadsheet, a new price column is one formula: =ROUND(E2*1.1, 2). Paste the result back over Variant Price, save as CSV, and import.

🔴 Tick "Overwrite products with matching handles". Left unticked, Shopify treats every row as a product it already has and skips it. The import reports success. Nothing changes. This is the single most common way a bulk price change quietly does nothing.

The mechanics of Shopify's CSV import — the two error messages nothing documents, the current versus legacy column names, and which columns are safe to leave out — are covered in detail in our bulk description guide; everything there about the import itself applies unchanged here.

Before you import anything: export first, and keep that file. An untouched export of your current prices is the only undo you get. It costs one click.

Method 3 — one sentence, then read the preview

Disclosure: Arvio is our own product. It's third here on purpose — the two routes above need nothing from us.

Both of those apply prices. Neither one works out which prices, and neither one says anything when a change is about to do something you did not mean. The timings below are measured; everything we could not verify is listed at the end.

We typed one sentence into a live store of 69 products:

Increase the price of every product by 10%

Here is the whole run, stopwatched from the recording:

Moment	Clock
Prompt typed (42 characters)	4.85 s
Sent	0:11
Preview card on screen	2:28
Approved	2:31
Last price written	5:57

Two minutes seventeen seconds to produce the preview, three minutes twenty-six seconds to write the changes, five minutes forty-six seconds from enter to done. The human input across all of it was one sentence and one click.

The clock is not the interesting part. Nothing was written to the store until the preview had been approved. The card says what is about to happen — how many products and variants are in scope, the currency, how many variants have cost data on file and therefore had their margin checked, and a sample of specific old → new pairs. We re-read the store afterwards to check those samples independently:

Product / variant	Old	New	Checked
Large Round Cutting/Charcuterie Board	S$66.60	S$73.26	✅ arithmetic exact, matches the store
TCHON Bamboo Salad Bowl — Matte Grey	S$134.48	S$147.93	✅
Macrame Toddler Swing — Khaki	S$115.27	S$126.80	✅
Iringa Basket Natural — 8 inch	S$101.18	S$111.30	✅
SOAI Bamboo Serving Bowl — Soleil S	S$89.40	S$98.34	✅

And the preview earned its place. It flagged that three variants — three sizes of the same basket — would rise by more than the 10% we asked for, because applying a flat 10% to that product's existing prices would have left a bigger basket cheaper than a smaller one. We verified afterwards that the size ladder does come out monotonic (8 inch S$111.30 → 12 inch S$163.60 → 14 inch S$189.40 → 16 inch S$215.02 → 17 inch S$238.08). We could not verify the stated 15–29% range for those three, because our pre-change snapshot did not include those rows. See the method section.

That is what a preview is for. A literal instruction, applied literally, would have gone through as a perfectly valid import and left a wrong price list behind it.

Five ways a bulk price change goes wrong

The Overwrite tick, unticked. Import succeeds, nothing changes. Check a product, not the confirmation message.
Counting products instead of variants. In our catalogue that understates the work by 76%. It also understates the blast radius.
"Select all" selecting a page. The list pages at 50. Ten pages is ten rounds, and nothing tells you which round you are on.
Repricing without cost in view. Cost per item is off by default in the grid, so the default view cannot show you a price that has fallen below what the item cost.
Assuming a percentage rule is literal. A flat percentage will walk straight through a size ladder or a price point ending in .99 without noticing either. Read a sample of old → new pairs before you commit, whichever route you took, and keep the export that puts it back.

Method, and what we could not verify

Environment. One live Shopify store, 69 products — 50 a synthetic catalogue we built for testing and 19 pre-existing — in SGD, English admin, desktop Chrome. Manual timings recorded 17 August 2026; the automated run recorded 22 August 2026 at 1920x1080, 30fps, with an action log written alongside the recording.

The manual timing is a single run of three rows, timed from the action log: stopwatch start to stopwatch stop, 16.93 seconds, of which 4.98 seconds was keystrokes. The keystroke pace is scripted and steady, which makes it faster than a person. We report it as a floor. The 200- and 500-product rows in that table are arithmetic on our measured 5.64 s/row and our measured 1.76 variants per product — they are extrapolations, not observations, and a catalogue with a different variant structure will land somewhere else.

Exclusion rule. We only report a number from the automated run's confirmation card if we could reproduce it from the store itself. That excludes more than it includes, so here is the full list of what we did not confirm:

"Products affected 69" and "Variants changed 153". Our independent read covered 50 products and 61 variants — the product list pages at 50 and the grid is virtualised, so a scripted read does not see the rest. The 69 matches the number of products in the store, which is consistent, but consistent is not verified.
"Margin verified 65/153" and "Margin unverified 88 variants". Cost per item is not a default grid column, so we never read cost data at all. Verifying these means turning that column on and measuring again.
"12 size-price inversions already in the store". Reconstructing that requires size options and prices grouped per product, and the row labels we captured were not enough to order sizes reliably.
The 15–29% range on the three ladder-corrected variants. The direction and the resulting ladder we did verify. The magnitudes we cannot, because those rows are absent from our pre-change snapshot.

What we did confirm: the currency on the card (SGD, visible in the grid), and all five sampled old → new pairs, each both arithmetically exact and matching the store when re-read afterwards.

One run is one run. These are single measurements on one store, not a benchmark. We are publishing the numbers we have with their limits attached rather than rounder numbers we would have to invent.

FAQ

How do I change all prices at once in Shopify?

There is no single control that does it. In the native admin your options are the bulk edit grid, where you type each new price, or a CSV export and re-import, where a spreadsheet formula computes them. For a whole catalogue, the CSV route is the realistic one.

Can Shopify increase all prices by a percentage?

Not on its own. The bulk editor has no percentage field — it edits cells. The percentage has to happen in a spreadsheet before a CSV import, or in a tool that computes the new prices for you.

Does the Shopify bulk editor have a price column?

Yes, and it is one of the columns the grid opens with, along with title, inventory and status. This is the opposite of the description column, which exists but is switched off by default.

Which CSV columns do I need to update prices?

Five: Handle, Title, Option1 Name, Option1 Value, Variant Price. One row per variant. Title is required on import even when you are not changing it, and the option columns are required as soon as any product in the file has variants.

My price import said it worked but nothing changed. Why?

Almost always the Overwrite products with matching handles checkbox, left unticked. Shopify then treats every row as an existing product and skips it, and the import still reports success.

How do I undo a bulk price change in Shopify?

By re-importing an export taken before the change, which is why you take one. There is no undo button for an import. Our own restore file for this exercise is 88 rows and five columns — the pre-change prices, ready to import back.

How many products can I select at once?

The list pages at 50, and the header checkbox selects the page you are on. On a larger catalogue, plan for the number of pages rather than the number of products.

How long does repricing 500 products take by hand?

On our measurement, about 1 hour 23 minutes of typing at a machine-steady pace, assuming the same 1.76 variants per product. Deciding the prices is not included in that, and it is the larger half.

What we still don't know

We tested no catalogue with three option dimensions, no store with metafield-driven pricing, and no market with per-country price lists, so we have no idea whether these timings survive any of them. We also have not run an export anywhere near Shopify's file size limit. The arithmetic there would be the same; the import would not.

Related: How to bulk edit product descriptions in Shopify — the same CSV route applied to descriptions, including the two import errors nothing documents.

Related: Your SEO app found 400 missing meta descriptions. Now what? — the same shape of problem in SEO fields.

Written by Adot Technologies Inc, the team behind Arvio: AI Store Operator — describe a bulk change in plain language, review every edit before it goes live, and undo anything.

Originally published at https://arvio.a.xyz/blog/bulk-price-change-shopify. More Shopify bulk-editing writeups are on the Arvio blog.

Your SEO app found 400 missing meta descriptions. Now what?

Arvio AI — Mon, 24 Aug 2026 23:04:30 +0000

This is a repost. Originally published on the Arvio blog: https://arvio.a.xyz/blog/shopify-missing-meta-descriptions. The canonical URL points back there.

Published 20 August 2026 by Adot Technologies Inc, the team behind Arvio. Every Shopify and Google claim below links to its primary source, checked against the live documentation in August 2026.

Key takeaways

Google says snippets are "primarily created from the page content itself" and that it uses your meta description only when that would be more accurate. Missing ≠ broken. Fixing all 400 is the wrong goal.
Shopify's own docs give two different character limits (320 in one place, 160 in another). Neither is a Google limit — Google says there is no length limit and truncates to fit the device.
The CSV route is the only true bulk route, and the column names in most guides are out of date. The live template uses SEO title, SEO description, URL handle and Description — not SEO Title, Handle or Body (HTML).
The single most expensive mistake: a blank cell wipes the existing value. A column you delete entirely leaves it alone. Most people do the opposite of what they intend.

The quick version

Don't fix all 400. Sort by which pages actually get search traffic and buying intent, and fix that slice.
For a handful of pages, use Shopify's built-in editor: Products → your product → Search engine listing → pencil icon.
For hundreds, export a product CSV, keep only the identifier column plus SEO title and SEO description, and re-import. Deleting the columns you're not changing is what protects them.
Back up before importing. A blank cell in a column you did include will erase whatever was there.

First: not all 400 are worth fixing

This is the part audit tools skip, because a list of 400 problems looks more valuable than a list of 12.

Here is what Google actually documents about how snippets are built:

"Snippets are primarily created from the page content itself."

"Google sometimes uses the meta description HTML element if it might give users a more accurate description of the page than content taken directly from the page."

— Google Search Central, snippet documentation

Two things follow. A page with no meta description still gets a snippet; Google writes one off the page. And nowhere in that documentation is the meta description listed as a ranking factor. What you gain by writing one is control over the snippet, not a ranking.

Put plainly: on 400 pages, Google is choosing your search result text for you. That is not the same thing as losing traffic on 400 pages. On most of them Google does the job better than a template would. The exceptions are the high-intent pages, and those you write by hand.

There are traffic-loss numbers circulating on this topic. We went looking for the evidence behind them and couldn't verify any of it at source. The one properly controlled test we did find points the other way: SearchPilot ran an SEO A/B test that removed overlong meta descriptions and measured +4.2% organic sessions, at 90% confidence — case study here. One test isn't a law, and "90% confidence" is not "proven". But it's enough to stop anyone claiming the opposite as settled.

A working filter, in order: pages that already rank and get impressions → product pages for things people search by name → collection pages that match a category query → everything else, which can keep the auto-generated snippet indefinitely.

Method 1 — Shopify's built-in editor, one page at a time

For products, collections and blog posts the path is the same:

Products → click the product (or Products → Collections, or Content → Blog posts)
Scroll to the Search engine listing section
Click the pencil icon — not an "Edit" button
Fill in Page title, Meta description, URL handle
Save

⚠️ Pages are the exception, and it trips people up: for Online Store → Pages, the section is called Search engine listing preview and you click a button labelled Edit website SEO. Different name, different control, same fields. (Shopify's own docs use both wordings.)

The homepage lives somewhere else again: Online Store → Preferences → Social sharing image and SEO.

On length, Shopify contradicts itself. The product, collection and blog post pages all say:

"If you enter more than 70 characters for a title, or if you enter more than 320 characters for a description, then your text might get cut off in search engine results."

while the older SEO help page says "It's recommended that 160 characters is used in the description." Neither is a Google rule. Google's position is explicit:

"There's no limit on how long a meta description can be, but the snippet is truncated in Google Search results as needed, typically to fit the device width."

In practice, write a first sentence that works on its own and stop counting characters.

If you leave the fields blank, Shopify fills them in: "When these fields are blank, SEO information is automatically generated based on your product title and description." That is the status quo you're choosing to override, which is the whole point of the filter above.

Method 2 — the bulk editor, and the question Shopify's docs never answer

Shopify has a built-in bulk editor: select products in the list, click Bulk edit, and you get a spreadsheet-like grid with a Columns picker.

And here the trail goes cold. Shopify's documentation never states whether SEO fields are available in that Columns picker. The bulk editing help page never lists the available fields at all — it only gives examples, "such as price, SKU, and compare-at price". Shopify's own blog post on the subject discusses the bulk editor, then moves on to CSV and third-party apps without ever naming an SEO column. Third-party guides flatly contradict each other on this, and there's no staff answer in the community threads.

So check your own admin — it takes ten seconds: Products → tick two products → Bulk edit → open Columns → look for a page title / meta description entry. Whatever you find there is authoritative for your store and your Shopify version, and it beats anything written on the subject, including this paragraph.

Two things the docs do state clearly:

No row limit is documented, only a warning that more edits take longer.
Products only. "You can only bulk edit product pages. You can't bulk edit other page types like blog posts."

If your 400 problem pages include collections, pages or blog posts — and they usually do — the bulk editor cannot help with those regardless.

Method 3 — CSV import, with the column names most guides get wrong

This is the only route that reliably handles hundreds of products. It's also where the widely-copied advice has gone stale.

We downloaded Shopify's current product CSV template and read the header row. The live column names are:

What you'll see in most guides	What the current template actually uses
`SEO Title`	`SEO title` (lowercase t)
`SEO Description`	`SEO description` (lowercase d)
`Handle`	`URL handle`
`Body (HTML)`	`Description`

If your import silently does nothing to the SEO fields, a capitalisation or a legacy column name is the first thing to check.

The overwrite rules are the part worth memorising, straight from Shopify's CSV documentation:

"If a non-required column in the import CSV file is blank, then the matching value in the product list is overwritten as blank."

"If a non-required column isn't included in the import CSV file... then the value in the product list remains the same."

Read those twice, because they are the opposite of most people's mental model. Deleting a column protects it. Leaving a cell empty destroys it.

Which gives the safe recipe: export your products, delete every column except the identifier and the two SEO columns, fill in only the rows you're changing, delete the rows you're not, and import. Nothing else can be touched, because nothing else is in the file.

Five ways this goes wrong

Blank cells wipe good data. See above. The single most common way a "quick SEO fix" turns into a restore-from-backup afternoon.
Editing option values rebuilds your variants. "Changing data in the Option1 value, Option2 value, or Option3 value columns... deletes existing variant IDs, and creates new variant IDs." Those IDs are referenced elsewhere. Don't touch option columns in an SEO import.
Variant rows aren't product rows. Shopify's instruction is to "skip the Title, Description, Vendor, and Tags columns" on variant rows. A find-and-replace down a whole column doesn't know that.
Opening the file in Excel. Shopify warns this can corrupt image links and lose images. Use a plain-text-safe editor, and save as UTF-8 with LF linefeeds as the docs require.
File size. "Your product CSV can't exceed 15 MB." No row limit is documented, but large catalogues hit the size ceiling and need splitting.

And the rule that precedes all five, in Shopify's words: "Before you start your import, make sure that you have a backup of your product data."

Method 4 — have something draft them for you

At 400 pages, the bottleneck stops being mechanics and becomes writing. Even with the filter from section 2, a real shortlist is usually 40–80 pages of original copy that has to match what's actually on each page.

This is the part we build. Arvio is an AI store operator for Shopify. It audits the store and ranks what it finds by what it's costing rather than by count, then drafts the copy against your live catalogue: meta descriptions, page titles, alt text, product descriptions. Every change waits for your approval, and anything you approve can be undone.

When it isn't the right tool: if you have twelve pages to fix, the built-in editor in Method 1 is faster than installing anything. If you already have the copy written and just need it applied, Method 3 costs nothing and takes ten minutes. An agent earns its keep when the list is long, the pages are all different, and writing 60 unique descriptions by hand is the actual obstacle.

Three situations, three different answers

"My audit says 400 missing, I have 2,000 products."
Almost all of those 400 should stay auto-generated. Pull your Search Console query data, find the products that already receive impressions, and hand-write those. Ten to thirty pages is a normal answer.

"I have 400 products and they're all in one collection with near-identical descriptions."
This is the case where writing them individually adds little — Google will likely rewrite templated text anyway. Spend the effort on the collection page instead, which is what ranks for the category query.

"Half my missing descriptions are blog posts and pages."
Then the bulk editor is out (products only) and the product CSV is out too — we could not find any documented CSV route for collection, page or blog SEO fields. Those are one-at-a-time in the admin, or via the Admin API (productUpdate exposes seo { title description } for products; other resources have their own mutations).

FAQ

What's the ideal meta description length for Shopify?

Shopify's product docs say text may be cut off past 320 characters; an older Shopify page recommends 160. Google says there's no limit and that it truncates to fit the device. Write a first sentence that stands alone.

Does a missing meta description hurt my SEO?

Google's snippet documentation doesn't list it as a ranking factor, and states that snippets are primarily built from page content. What you lose is control of the wording, not a position.

Can I bulk edit meta descriptions in Shopify without an app?

Yes, via CSV export/import using the SEO title and SEO description columns. Whether the built-in bulk editor exposes those fields isn't documented — check the Columns picker in your own admin.

Will Google use the description I write?

Sometimes. Google says it uses the meta description "if it might give users a more accurate description of the page than content taken directly from the page." Being accurate and specific to that page is what makes it more likely.

Why did my CSV import blank out my product descriptions?

Because those columns were present but empty. An included-but-blank column overwrites with blank; an omitted column is left alone. Import only the columns you intend to change.

How many products can I import at once?

Shopify documents a 15 MB file size limit and no row limit. Large catalogues get split by size, not by row count.

Can I do this for collections and blog posts?

Not through the product CSV or the bulk editor. We could not find a documented CSV route for those, so it's the admin one at a time, or the API.

Do I need to redirect if I change the URL handle?

Shopify offers to create a redirect when you change a handle — on blog posts the checkbox is pre-selected, on collections it's an option. Take it. Changing a handle without a redirect breaks existing links.

Do I need an app to bulk edit meta descriptions in Shopify?

No. The product CSV export/import route is built into Shopify and handles hundreds of products with the SEO title and SEO description columns — the method is in section 3 above, including the column names most guides get wrong. Apps are worth paying for when you want change history, undo, scheduling or fields the CSV does not expose; they are not required for the bulk edit itself.

Related: Shopify App Store Ads: what 310,000 impressions say about Relevance, bids and dead keywords — keyword-level data from our own ad account, published because no public benchmark for the channel exists.

Written by Adot Technologies Inc, the team behind Arvio: AI Store Operator — the AI agent that fixes Shopify store SEO, product content, prices and stock in bulk, with every change waiting for your approval. Every Shopify and Google claim above links to the primary source; if we've got one wrong, tell us and we'll correct it.

Originally published at https://arvio.a.xyz/blog/shopify-missing-meta-descriptions. More Shopify bulk-editing writeups are on the Arvio blog.

Shopify App Store Ads: what 310,000 impressions say about Relevance, bids and dead keywords

Arvio AI — Mon, 24 Aug 2026 23:02:15 +0000

This is a repost. Originally published on the Arvio blog: https://arvio.a.xyz/blog/shopify-app-store-ads-benchmarks. The canonical URL points back there.

Published 20 August 2026 by Adot Technologies Inc, the team behind Arvio. Data window: June 2025 – June 2026, plus one 7-day window in August 2026. Every figure comes from keyword-level exports out of our own Shopify Partners ad dashboard; the full method is in the next section.

Key takeaways

Shopify's Relevance label predicts click-through rate very well — and install rate not at all. Click-through spans 3.6× across the five bands; click-to-install stays flat at 24–31%.
The auction sends volume away from relevance. Keywords Shopify labelled "Very high" were 58.4% of our list but took 6.4% of impressions. "Very low" was 2.8% of the list and took 24.2%.
Most keyword slots never serve at all: 49.0% had zero impressions over a full year.
The one bid-suggestion signal that separates a live keyword from a dead one is simply whether Shopify shows a range at all — not how low the range is. Keywords with a range got 3.18× the impressions per slot (95% CI 3.00–3.37).

Is there any public benchmark data for Shopify App Store Ads?

Not that we could find, which is why this post exists. Shopify shows you suggested bids and your own keyword metrics inside the Partner Dashboard, and publishes setup guidance for advertisers, but it releases no aggregate figures for the channel. We went looking for a keyword-level dataset published by a real advertiser before we ran our own numbers. There wasn't one.

So here is one account's ground truth: 310,520 impressions, 1,844 clicks and 488 installs over 365 days, broken out by the Relevance label Shopify itself assigns each keyword. It is one advertiser, not the industry, and the limits are listed in full at the end. It is still more than zero, and the arithmetic is reproducible from the tables below.

Why you should be sceptical of this post, and read it anyway

We build Arvio, an AI store operator for Shopify — it audits a store's SEO, product content, prices and stock, drafts the fixes, and holds every change for the merchant to approve. Dataset B below is Arvio's own ad account; Dataset A is our sister app, AiLead. We buy this inventory ourselves, so we have an obvious interest in how you think about the channel, and you should weigh the post accordingly.

So don't trust us. Check the method and the sample instead, and the section at the end that lists what would break these conclusions. Every number below comes from keyword-level exports out of the Shopify Partners ad dashboard. Nothing is modelled, estimated or extrapolated.

We're publishing it because if you run Google Ads or Meta you can go and look up what a normal CTR is, and here you can't. Every advertiser on this channel is calibrating against their own account and nobody else's.

Method

Sample. Two datasets, from two apps in two different categories, both ours:

	Dataset A	Dataset B
App	AiLead (sales chatbot)	Arvio (store operations)
Rows	7,620 keywords	7,609 keyword slots
Window	`Last 365 days` (Jun 2025 – Jun 2026)	`Last 7 days` (Aug 2026)
Volume	310,520 impressions · 1,844 clicks · 488 installs	8,673 impressions · 42 clicks
Match type	7,478 Broad · 142 Exact	7,599 Broad · 10 Exact
Geo	Not split — all rows are `All`	Same

The windows are different and we do not merge them. Dataset A answers "what does Relevance do to performance". Dataset B answers "which keyword slots serve at all". Any sentence below is about one dataset or the other, never both.

Selection bias, stated plainly. These are keywords we chose to buy, mined from our own search-term reports. This is therefore the distribution of a mid-size advertiser's keyword list — not the distribution of App Store search demand. If you want to know what merchants search for, this dataset cannot tell you.

How the rates are computed. CTR per band is impression-weighted (total clicks ÷ total impressions in the band), not the mean of per-keyword CTRs. That choice matters, so we checked it: the unweighted per-keyword mean gives 1.088% / 0.851% / 0.646% / 0.491% / 0.301% — same order, same monotonicity. The finding is not an artefact of weighting.

What we excluded, and what happened when we did. Both datasets are overwhelmingly Broad match, with a small Exact tail. Dropping the Exact rows entirely moves the Dataset A CTR curve from 1.121 / 0.811 / 0.656 / 0.565 / 0.310 to 1.121 / 0.808 / 0.656 / 0.565 / 0.310 — one digit in one band. We kept them.

Right-censoring. In Dataset B, 7.0% (536/7,609) of bid suggestions are capped at the display ceiling $75.00+. Any average of suggested bids is therefore biased low, and we don't publish one.

Timing caveat. Bid suggestions are read at export time. They are not locked to the metric window, so a suggestion shown next to a 7-day impression count was not necessarily the suggestion in force during those 7 days.

Account size, so you can calibrate. This is a small advertiser: annual spend on this channel is in the low four figures, not five or six. Every rate below should be read as a small account's numbers — we have no way to know whether they hold at ten or a hundred times the budget, and we'd be surprised if all of them did.

What we deliberately don't publish. Absolute spend and absolute cost per install. Those are commercial. Everything cost-related below is expressed as a ratio within the same dataset, which preserves every conclusion and leaks nothing. Given the impression, click and install counts above, anyone determined to estimate our costs can get close; the ratios are what we're standing behind.

1. Relevance predicts clicks. It does not predict installs.

Dataset A, 310,520 impressions, split by the Relevance label Shopify assigns each keyword:

Relevance	Impressions	Clicks	CTR	Installs	Click → install	Cost per install (indexed)
Very high	19,982	224	1.121%	64	28.6%	1.00×
High	41,815	339	0.811%	105	31.0%	1.20×
Medium	74,207	487	0.656%	124	25.5%	1.47×
Low	99,321	561	0.565%	137	24.4%	1.60×
Very low	75,195	233	0.310%	58	24.9%	1.83×
All	310,520	1,844	0.594%	488	26.5%	—

The CTR column is perfectly monotonic across all five bands, a 3.6× spread from top to bottom. As a predictor of whether a merchant clicks your card, the Relevance label works.

Now read the next column. Click-to-install is 31.0% for "High" and 24.9% for "Very low", and it isn't monotonic: "High" beats "Very high". Across a 3.6× swing in click-through, the probability that a click turns into an install barely moves.

That shows up in the cost column. A "Very low" keyword costs 1.83× per install compared with "Very high", and the whole of that penalty is paid getting the click rather than converting it. Merchants who arrive from a badly-matched keyword install at about the same rate as everyone else. There just aren't many of them.

So if you have been reading Relevance as a proxy for traffic quality, this data says it isn't one. It predicts click-through, and nothing past the click.

2. The auction sends volume away from the keywords Shopify calls relevant

This is the part we did not expect. The same dataset, counted by keyword instead of by impression:

Relevance	Keywords	Share of list	Impressions	Share of impressions
Very high	4,453	58.4%	19,982	6.4%
High	997	13.1%	41,815	13.5%
Medium	1,168	15.3%	74,207	23.9%
Low	785	10.3%	99,321	32.0%
Very low	217	2.8%	75,195	24.2%

Nearly six in ten of our keywords were labelled "Very high" relevance by Shopify, and together they captured 6.4% of the impressions the account received. At the other end, 217 keywords — under 3% of the list — pulled almost a quarter of all impressions.

We can't see the auction, so we can't tell you the mechanism with confidence. The shape is consistent with the obvious explanation: a keyword being highly relevant to your app says nothing about how many merchants type it, and the terms that describe your product precisely tend to be the terms nobody searches. Relevance is a match score, not a demand signal, and it is easy to read it as both.

The operational version: a keyword list that looks excellent in the Relevance column can still be starved of volume, and the dashboard will not flag this. Impression share by relevance band is not a view Shopify gives you. You have to build it.

3. Half of the keyword slots never serve

Dataset A, over a full year: 3,736 of 7,620 keywords — 49.0% — received zero impressions.

Dataset B, over 7 days: 5,819 of 7,609 slots — 76.5% — received zero impressions.

The two aren't in conflict: a keyword that serves rarely shows zero in a short window and non-zero in a long one. We quote both because neither window makes the dead half of the list look alive.

We're not saying that's the norm for the channel. But if you have never counted, the number is probably bigger than you assume, and "we have 7,000 keywords" describes a list, not a reach.

One concession, made here rather than buried at the end. Section 4 shows that on keywords where Shopify offered a bid range, our bid sat below the bottom of it 84.5% of the time. So an unknown share of these silent slots is not the channel refusing to serve them — it is us not paying to enter the auction. We can't split the two apart with observational data. Read "dead slot" as "produced nothing for us at our bids", not as "has no demand".

4. The only bid signal that separates live from dead is whether a range exists

Shopify shows a suggested bid next to each keyword. Sometimes it is a range ($16.00 – $75.00+), sometimes a single flat figure. We assumed for months that the useful signal was how expensive the suggestion was, and that cheap suggestions meant available inventory.

That was wrong. The useful signal is whether there is a range at all.

Dataset B, 7,609 slots over 7 days:

Bid suggestion	Slots	Impressions per slot	Clicks per slot
Shows a range	4,800	1.53	0.00813
Shows a flat figure	2,809	0.48	0.00107
Ratio	—	3.18× (95% CI 3.00–3.37)	7.6× (95% CI 2.4–24.6)

And the flat suggestions are barely a price at all: 93.1% of them (2,615 of 2,809) are exactly $1.00, which is the floor. Our reading is that a flat $1.00 means there is no auction to price — nobody bidding because nobody searching — so Shopify falls back to the floor.

A note on that second column, because the confidence interval is doing real work. The whole 7-day window contains only 42 clicks. The direction is not in doubt: if clicks were distributed in proportion to slot counts, the flat group should have received 15.5 of those 42 clicks; it received 3 (exact binomial, one-sided, p = 1.0 × 10⁻⁵). But the magnitude — "7.6×" — has a 95% confidence interval running from 2.4× to 24.6×, and anyone quoting 7.6× as a fact is over-reading it. The impressions-per-slot figure of 3.18× is the one to use; it is built on 8,673 impressions rather than 42 clicks and the interval is tight.

One more figure from the same dataset, which surprised us: on keywords where Shopify did show a range, our bid was below the bottom of the suggested range 84.5% of the time (4,058 of 4,800). We were not outbid; we were not in the auction.

What we'd do differently, if we were starting this account again

Not advice, just what this data would have told us eighteen months earlier:

Build the impression-share-by-relevance-band view on day one. It's the table in section 2, it takes ten lines of code, and it isn't in the dashboard.
Use the presence of a bid range as the first filter on a keyword list, before looking at the suggested amount. A flat $1.00 is not a bargain, it's an empty auction.
Stop reading Relevance as traffic quality. It's a click-through predictor. Judge quality on click-to-install, which in this account was roughly flat across every band.
Count dead slots monthly. Half a keyword list can go quiet without any dashboard changing colour.

The first two are a groupby and a division — the FAQ at the bottom has the recipe, and you don't need anything from us to run them. If you'd rather compare notes than build it, we're easy to find: we're the team behind Arvio, and we'd take a second account's numbers over another blog post any day.

What we still don't know

One advertiser, two apps, no control. We cannot separate "this is how the channel behaves" from "this is how our two apps behave in their two categories."
Installs are Shopify-attributed. We cannot verify them independently at merchant level, so the install column inherits whatever Shopify's attribution does.
No geo split. Both exports report All. Country-level effects, which are large in every other channel we run, are invisible here.
We haven't tested the causal version. Everything above is observational. We have not taken a set of keywords and moved them between bid levels to see what happens — so read section 4 as "these two groups differ", not "showing a range causes impressions".
Bid suggestions aren't time-aligned with the metric window (see Method).

If you run App Store Ads and your numbers disagree with ours, we'd genuinely like to know — a second account would roughly double the amount of public data on this channel.

FAQ

What is a good CTR for Shopify App Store Ads?

In this account, across 310,520 impressions over a year, the blended CTR was 0.594%. By relevance band it ran from 1.121% down to 0.310%. We'd caution against treating one account as a benchmark, which is exactly why we published the band-level split rather than a single number.

Does a higher Relevance score get me cheaper installs?

Cheaper, yes — 1.00× versus 1.83× per install between the top and bottom bands in this data. But the saving comes from click-through, not from install rate, which was roughly flat at 24–31% across all five bands.

Why do my "Very high" relevance keywords get no impressions?

Ours mostly didn't either — 58.4% of our keywords carried that label and they took 6.4% of impressions. Relevance measures how well a keyword matches your app, not how many merchants search it.

What does a flat $1.00 bid suggestion mean?

In our data it is overwhelmingly the floor shown when there is no auction to price — 93.1% of all flat suggestions were exactly $1.00, and those slots served at roughly a third the rate of keywords with a range.

Should I bid above the suggested range?

We can't answer that from observational data. We can say we were below the bottom of the range 84.5% of the time on keywords that had one, which is worth knowing before you conclude that a keyword "doesn't work".

How many keywords should I add?

This data doesn't support an answer, but it does undercut the premise: 49% of ours produced nothing in a year. Adding slots is not the same as adding reach.

Is Broad or Exact better?

We can't tell you — our list is 98% Broad in both datasets, so we have no meaningful Exact comparison. Anyone claiming a Broad-vs-Exact benchmark for this channel should be asked for their Exact sample size.

Can I reproduce this?

Yes, from your own account. Export keyword-level performance with the Relevance column, group by band, and compute clicks ÷ impressions and installs ÷ clicks per band. The whole analysis is a groupby and two divisions. If it doesn't replicate on your account, that's a more interesting result than this post.

Written by the team behind Arvio: AI Store Operator — the AI agent that fixes Shopify store SEO, product content, prices and stock in bulk, with every change waiting for your approval. We're a small app and we buy this ad inventory ourselves; treat this post as one advertiser opening its books, not as an industry study.

Does the Relevance score predict installs, or only clicks?

Only clicks, in this dataset. Across 310,520 impressions, click-through rate is perfectly monotonic across all five Relevance bands with a 3.6× spread from top to bottom, while click-to-install stays between 24% and 31% and is not even monotonic — "High" beats "Very high". Treat Relevance as a click-through predictor, not a traffic-quality score.

Is there any published keyword-level data for this channel?

We could not find one before publishing this. Shopify publishes no aggregate benchmarks, and the figures that circulate come from individual practitioners quoting their own accounts without the keyword-level breakdown. The tables above are our attempt to add one public sample. If you run App Store Ads, yours would be the second.

Related: Your SEO app found 400 missing meta descriptions. Now what? — the same approach applied to an audit report: which of the flagged items are actually worth fixing, and the four bulk routes for the ones that are.

Originally published at https://arvio.a.xyz/blog/shopify-app-store-ads-benchmarks. More Shopify bulk-editing writeups are on the Arvio blog.