A Copywriter's Guide to Shopify
Shopify copy that converts means owning product fields, collection descriptions, theme sections, and metafields–not dumping a brand story into one rich-text box. A field-level guide for ecommerce writers.
Shopify is where commercial copy meets theme constraints. The job is not “write a brand story.” It is filling the fields the theme and apps actually show: product description, SEO fields, collection copy, and metafields–without inventing claims that get the merchant in trouble.
This guide is for freelancers and agencies shipping Shopify deliverables. Use Human Writes as the polish step after the attribute sheet is true–not as a catalog generator that invents fabric weights or “award-winning” badges.
Related: Shopify product descriptions that convert, humanize Shopify product descriptions, product marketing copy, agency scale.
Surfaces you actually write
| Surface | Where it lives | Notes |
|---|---|---|
| Product title | Products → title | Search + PDP H1; keep scannable |
| Description | Product description (HTML) | Theme-dependent; avoid orphan H1s |
| SEO title / description | Search engine listing fields | Not the same as product title |
| Collection description | Collections → description | Often thin or empty–SEO opportunity |
| Theme sections | Customize → sections | Hero, rich text, image-with-text |
| Metafields | Product metafields / definitions | Only write fields the theme renders |
| Email / SMS | Flow apps (Klaviyo, Shopify Email) | Separate briefs; don’t reuse PDP fluff |
| Cart / checkout upsells | Apps or checkout extensibility | Short benefit lines; no essay |
Ask for a theme field map (or Loom of the customizer) before you quote word counts. Dawn and custom themes expose different blocks. Online Store 2.0 themes often pull specs from metafields into icon rows–writing those specs only into the description HTML means filters, comparison apps, and some feeds never see them.
What AI Shopify copy gets wrong
| Pattern | Buyer / merchant cost |
|---|---|
| Generic “premium quality” | Zero differentiation |
| Invented fabric / ingredients | Returns and chargebacks |
| Same description × 200 SKUs | Thin content + brand damage |
| SEO title = keyword dump | Low CTR |
| Collection copy ignored | Category pages rank nowhere |
| Variant differences buried | Wrong size/color orders |
Lock a product fact sheet (materials, dimensions, who it’s for, what it is not) before ChatGPT. Humanize after. For conversion structure on individual PDPs, see descriptions that convert. For catalog-wide voice, see humanize Shopify descriptions.
Before and after (product blurb)
AI catalog sludge:
Experience the ultimate in premium quality with our meticulously crafted everyday essential, designed to elevate your lifestyle with unmatched comfort and style.
After fact sheet + one voice pass:
Midweight merino crew for cool offices and travel days. 200 GSM, flatlock seams, fits true to size–size up if you like a relaxed drape. Not for high-intensity workouts (it isn’t moisture-wicking like our training line).
The second version can live in description HTML and map cleanly to metafields for material, weight, and fit.
Collection pages are not optional
Many Shopify stores treat collections as product grids with no intro. That wastes category intent (“linen sheets,” “trail runners under $150”).
| Collection element | Copy job |
|---|---|
| Title | Browse + search clarity |
| Description (top) | Who the assortment is for; 2–4 sentences |
| Empty state | Rarely written–still plan for it |
| SEO listing fields | Category phrase forward; no stuffing |
Write collection intros that help choose, not that repeat every PDP. Point to filters (“sort by size”) when the theme supports them. Empty or boilerplate collection copy is a common agency miss when scope stops at “product descriptions only.”
Metafields and apps: write what renders
Before drafting a batch:
- List metafield definitions the theme references (materials, care, dimensions, sustainability notes).
- Note apps that inject copy (reviews, size guides, subscriptions, loyalty)–don’t duplicate their jobs in the description.
- Confirm whether marketplace or Google Shopping feeds pull title + description + metafields differently than the storefront.
| Do | Don’t |
|---|---|
| Fill rendered metafields first | Invent certifications “for SEO” |
| Keep SKU / barcode / handle stable | “Humanize” product handles mid-campaign |
| Align first line with ad creative | Bait-and-switch from Meta ads |
| Use lists for specs | Walls of adjectives on mobile |
Treat metafields like structured CMS fields in WordPress or Webflow: named slots, not a second essay.
Objections you’ll hear (and answers)
| Objection | Response |
|---|---|
| “Just make it SEO longer.” | Length without answers doesn’t convert. Lead with buyer questions; put specs in metafields. |
| “AI can rewrite the whole catalog overnight.” | Only after a locked attribute sheet. Fluency without facts is inventory spam. |
| “We don’t need collection copy.” | Category pages are often the ranking URL. Thin collections leave money on the table. |
| “Humanize every field.” | Skip SKUs, legal lines, and exact variant names. One voice pass on benefit prose. |
| “Same blurb is fine for variants.” | Call out material or fit differences or you own the returns. |
Honest limitations belong in the copy–especially fit, care, and “not for.” That is conversion work, not negativity. Pair with pricing-page honesty when bundles and compare-at prices appear on the PDP.
Theme homepage and landing sections
Beyond products, Shopify freelancers often own:
- Hero headline + subhead + button labels in the theme editor
- Featured collection blurbs
- Image-with-text story blocks
- FAQ rich-text sections
Deliver these per section name, the same way you’d map Gutenberg or Webflow Navigator. A single “homepage Doc” that ignores section IDs creates paste errors when the merchant’s theme stacks differently on mobile.
Practical section: batching a SKU sprint
When the brief is “200 products by Friday”:
- Segment by product type (tees vs bottles vs kits)–different hooks.
- Build one exemplar PDP the brand loves.
- AI-draft from PIM/CSV columns only; ban fluff adjectives in the prompt.
- Fact-check a sample of 10 for invented specs.
- One Human Writes pass on the exemplar voice, then batch with the same voice rules.
- Spot-check live theme on mobile for three hero SKUs.
Agencies shipping this weekly should standardize the fact sheet and disclosure language (disclose AI on deliverables; at-scale humanizing).
Deliverable format clients can paste
- Product title (≤70 characters when possible)
- Description HTML with H2/H3 that match theme styles
- SEO title + meta description
- Collection blurb (if in scope)
- Metafield values in a table:
namespace.key→ copy - Claims to legal-review (highlighted)
- Theme section copy keyed to section names
Workflow
- Get theme + metafield inventory.
- Build fact sheets for the SKU batch.
- Draft in AI from facts only.
- One Human Writes pass for voice.
- Paste into Shopify; preview mobile PDP.
- Spot-check live theme–hidden metafields waste effort.
- Fill collection + SEO listing fields for priority categories.
Deliverable checklist
- No invented specs or certifications
- SEO fields filled for priority SKUs
- Collection pages not empty
- Metafields match what the theme renders
- Variant differences called out where they matter
- Theme section copy labeled by section
- Voice matches brand sheet after one humanize pass
- Mobile skim: first screen states the product job