How do I stop a translated SEO title from being imported into the product description?

Work through the cause

1. Export the relevant language data and keep an untouched original. Identify resource, locale and field columns before editing values.
2. Change only the intended translated content. Keep body, title and metadata rows distinct, and test a small approved sample.
3. Inspect the public page title, visible product heading and description separately after import. Retain the import file and result report.

A concrete case (illustrative)

Illustrative case: a short search-result title is pasted into a body_html translation row. The import may address a valid resource but update the wrong type of content.

Acceptance and next action

Pass when each translated value appears in its intended field. Product CSV identity and translation CSV identity are different workflows; use the correct exported format instead of adapting a generic product import sheet by guesswork.

Take this question’s manual review card

The worksheet contains this question’s steps and acceptance condition. Fill in your actual source, observations and decision; blank fields do not mean approval. It does not connect to a store, modify files or automatically approve a result.

Download this review card (CSV)

Source scope: the linked documentation explains relevant tool behavior or technical context. The merchant scenario, review choices and acceptance condition are Itemlume editorial guidance; citation does not imply endorsement.