ItemlumePRODUCT CREATIVE / PRODUCTION AND HANDOFF
Why Does a Comma in My Image Address Break Google’s Additional-Image Feed?
For text data sources, Google uses commas to separate additional-image URLs. A comma that belongs inside an individual address needs different handling, such as percent encoding it as %2C. First identify the broken list boundary; removing every comma or encoding every comma changes the wrong layer.
Inspect the list after the connector has processed it
Keep the approved image files and the feed representation separate. Several correct files can arrive as a broken image list if punctuation changes their boundaries. A source sheet that looks readable is not evidence that the receiving record contains the intended addresses.
Record the product identifier, data-source type and actual additional-image values received. Check whether the connector produces one address, several addresses or fragments that are no longer usable. Do not regenerate the photographs to repair serialization.
Distinguish address punctuation from the list separator
The additional_image_link specification gives separate formatting for text and XML sources. In the text-source example, commas between addresses are separators; commas inside an address can be encoded. Google also documents quoted individual addresses as an alternative representation.
A filename fragment such as front%2Cblue.jpg illustrates an encoded internal comma. It is not a complete submission URL or an import-ready feed. Keep the actual host and full valid address in your own authorized data source.
Do not percent-encode the entire finished list as though it were one address. Conversely, do not split every literal comma without respecting the destination’s format. Spreadsheet-field quoting and the value’s internal address list are separate layers; inspect both when your connector serializes them.
| Punctuation role | Intended meaning | Review question |
|---|---|---|
| Inside one image address | Part of that address | Did it remain inside a single usable URL? |
| Between image addresses | Separate additional images | Did the receiver produce the intended list? |
An illustrative exercise: two views, one awkward filename
Illustrative exercise: a fictional mug has a front image whose filename contains a comma and a separate handle-detail image. The intended result is two additional-image addresses. These are teaching inputs, not a tested Merchant Center upload.
Prepare one pilot record using the actual connector’s supported format. Reopen or inspect its serialized output and then the receiving product record. Confirm both image identities, their complete addresses and their association with the correct mug.
If the front address has become two fragments, fix its internal punctuation handling. If both intended addresses have become one unusable value, inspect list-separator handling. If the addresses are intact but an image cannot be fetched, move to access or delivery diagnosis instead of editing punctuation again.
Accept the parsed list and images together
Approval requires the intended number of complete, reachable addresses and the correct product views. A syntactically accepted feed does not establish that every submitted image will display in every placement.
Retain the original source row, the actual serialized value and the receiver’s observation. This guide does not perform a feed submission, test a connector, modify a store or establish Google image eligibility. Itemlume creative downloads still require an external publishing workflow.
Illustrative exercise: image-list punctuation record
These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.
| Fictional input | Intended list | Observed failure | Next branch |
|---|---|---|---|
| Front filename contains comma; separate detail view | Two full image addresses | One address split into fragments | Check internal comma representation |
| Same two images | Two full image addresses | Whole list treated as one URL | Check separator and connector serialization |
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
Frequently asked questions
Should every comma be encoded as %2C?
No. The documented distinction is between commas inside one address and the separators between addresses in a text source. Treating both alike can destroy the list.
Does a correct CSV field guarantee a correct additional-image list?
No. The outer file field and the list within that field must both be interpreted correctly by the actual connector and destination.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in Itemlume.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits