Translate Shopify SEO titles — leave the URL handle alone

German is published. Product titles are translated. Google still shows the Dutch meta on `/de/...`: “Made-to-measure linen curtain | Northlight”. The H1 is German. The snippet is not. Translate & Adapt filled the title. The SEO title field in that locale is empty — or a job skipped it because someone tried to “translate” the handle.

Shopify multilingual SEO translations is the layer shops skip when they only run body copy. OO - Ultimate AI Translations includes SEO title and description among customer-facing fields, with titles, descriptions, option labels, and image alt text. Listing category: SEO translation. What jobs must not become: handles, URLs, IDs, SKUs. Those are skipped on purpose.

What is OO Translations?: side-by-side editor, Missing/Outdated jobs, locks on what you save, glossary and brand voice, backups, language switcher, metaobjects. Content types: products, collections, pages, theme, metaobjects, draft themes.

Live listing, USD: Free — your own AI (OpenAI-compatible), unlimited languages/markets/translations, language switcher; no backups, no scheduled jobs, no App AI. Professional $10/month + usage — 1+1 backup, monthly schedule, glossary, App AI at translation cost (~$0.01/unit, pass-through) or your own AI. Plus $20 — 5+5 backups, daily schedule. 0 reviews, launched 14 October 2026. Do not invent scores.

On 22 October: job history. That is where skipped versus translated shows up. This article is the field type that belongs in skipped when it is a handle, and in translated when it is a meta description.

The SERP field is not the handle

Shopify splits storefront title, body, SEO title, SEO description, and handle/URL. A shopper on `/de/products/linen-curtain` can see a German H1 while `og:title` stays Dutch. That is not “bad German from the model”. That is an empty or skipped SEO field.

Jobs skip, FAQ: empty source, locked fields, technical values (handles, URLs, IDs, short size codes, and similar). Handle `linen-curtain-made-to-measure` must not become a German slug — redirects, feeds, and internal links point at it. The SEO title “Made-to-measure linen curtain | Northlight” should become German.

Empty source: no English/Dutch meta in the default locale → skip. Fill source, then Missing. Locked: you saved a German snippet with a keyword AI must not overwrite. Unlock only if jobs may rewrite it.

Glossary (Professional+): pin “Northlight” so it does not become a translated brand in the description. Brand voice rides along with the AI request. Free: your own model, same editor, no schedule/glossary/App AI.

How the wrong snippet reaches Google

Jobs on products → title + body only. SEO fields stay source. SERP stays NL. H1 is DE.

Translating handles in a spreadsheet and re-importing. New URLs, dead old ones. The app skips handles so you do not do that.

Translate & Adapt for H1, meta by hand on 200 products. This app exists for Missing/Outdated on the same fields, including SEO title/description, with a lock when you wrote the snippet.

Expecting a schedule on Free. Free has no scheduled jobs. Run a job or use the editor. Professional monthly, Plus daily. Include SEO fields on products/pages; theme jobs will not fill product meta.

What should be translated

Customer-facing, from positioning and listing:

• titles, descriptions

• SEO title / SEO description

• option labels

• image alt text

• pages, collections, theme, metaobjects (including draft themes)

Not: handles, URLs, IDs, SKUs, barcodes, S/M/L-style size codes, JSON, empty source, locked fields.

Editor: source vs target. Save locks. Automatic/scheduled jobs do not overwrite locked fields. FAQ: *Will automatic jobs overwrite my edits? No.*

Language switcher on Free lets shoppers pick DE. If meta is still NL, that is missing SEO translation, not a switcher bug.

App AI ~$0.01/unit on Professional/Plus, or your own AI on every plan. Listing: billed at translation cost — no AI markup pitch.

Walkthrough: 180 curtain SKUs, German snippets

Store “Northlight”. DE market. Titles done. Search Console: German URLs, Dutch descriptions.

1. Install OO - Ultimate AI Translations. Free + your OpenAI-compatible key, or Professional for monthly jobs and glossary.

2. Fill source SEO where it is empty. Empty source = skip.

3. Editor, locale DE, products. Missing on SEO title/description. Review. Save — lock if the snippet is deliberate.

4. Glossary: “Northlight”, fabric names. Brand voice: plain, no superlatives.

5. Job: products, Missing + Outdated, not handles. Job details: translated vs skipped. Skipped handle is correct. Skipped SEO title with a filled source means a lock or a content type you did not select.

6. Storefront `/de`, view-source or a SERP preview: German meta. Handle unchanged.

Theme strings (“Add to cart”) are another content type. They do not fill product meta.

Get it live

1. Open the listing. Free for the editor. Professional for schedule + glossary.

2. Write SEO title/description in the source language. Then translate.

3. Jobs skip URLs — that is intended. Do not skip snippets.

4. Lock hand-written DE meta. Unlock only if AI may run again.

5. Switcher embed/block on the live theme so `/de` exists. Then the meta, not the other way around.

Multilingual SEO is two fields per product, not a new handle.

Wrap-up

Shopify multilingual SEO translations means SEO title and description in the same AI jobs as the rest of the product copy. Handles and URLs stay technical. Locks protect a snippet you wrote. Free with your own AI; schedule and App AI (~$0.01/unit) on paid plans.

Translate the snippet in OO - Ultimate AI Translations. Leave the slug alone.