
A comma inside a product-image URL can be mistaken for the separator between additional images. Merchant Center's text-source rules distinguish those two jobs: encode a comma that belongs to a URL, while leaving the delimiter between URLs intact. Check the parsed image list before replacing otherwise correct artwork.
Key Takeaways
- Count intended images separately from commas in the source string.
- Use the serialization rules for the actual text, XML or API route.
- Verify each parsed URL still points to the correct product image.
Confirm that this is a list-parsing failure
The official additional-image attribute guide allows up to ten additional images. For text data sources, it describes comma-separated URLs and encoding literal URL commas as percent-encoded values. It also documents a quoting alternative.
Record the product identifier and the exact submitted field privately. Compare the expected number of images with the interpreted list in the supported processing view or diagnostic evidence. A broken substring resembling the end of a filename is a useful clue, not proof by itself.
Do not confuse a correct list with a correct image-role choice. The main, additional and lifestyle mapping guide covers that earlier decision.
Separate a URL comma from a delimiter
Consider a proposed asset whose filename contains a comma. Its literal comma belongs inside one URL; the comma between that URL and the next image is a list delimiter. Encoding every comma in the whole field would remove the intended separation. Encoding none could create unintended values.
Use the source's documented encoding or quoting approach for individual values. If a spreadsheet exports the feed, check the final exported text, not only the visible spreadsheet cell. CSV field quoting and an attribute's internal URL list can introduce separate layers of formatting.
Do not manually rewrite a signed delivery URL without checking its supported generation route. An encoding repair should preserve the actual address semantics and access requirements, not invent a new image location.
Keep XML and connector formats separate
The same official page shows repeated additional-image elements for XML. That differs from a comma-separated text value. An integration using an API has its own documented representation.
Ask the connector owner which format it actually sends. A screenshot of a settings field may not show the final serialized record. Avoid pasting XML tags into a text-cell workflow or concatenating an array into an unsupported string.
Keep every URL associated with its real SKU using the product-image mapping record. A successfully parsed image can still belong to the neighboring variant.
Verify the repaired list end to end
Use this proposed acceptance sequence:
- Record the expected assets and their intended order.
- Inspect the final submitted representation for the actual source format.
- Confirm the interpreted list has the expected number of values.
- Open each authorized public image route independently.
- Compare the served picture with the correct product and revision.
- Inspect item-specific diagnostics after processing.
If the parsed URLs are correct but an old image remains, move to the product-image refresh diagnosis. Keep parsing success, image fetching and displayed output as separate observations. The task is complete when the intended list reaches the correct item intact, not when the field merely stops showing a formatting error.
Related tasks
- Where Should I Put an AI Lifestyle Image If It Is Not My Main Product Photo?
- How Do I Keep AI Product Images Matched to the Correct SKU?
- Why Does Google Still Show My Old Product Image After I Upload a New One?
Sources and scope
- Google Merchant Center: Additional image link: Text sources separate additional-image URLs with commas while literal commas inside URLs require encoding or supported quoting. XML uses repeated elements instead. The attribute supports up to ten additional images.
Based on the complete official attribute source captured October 29, 2026. No URL, parser, feed or Merchant account was tested. The example and count-check procedure are proposed. Data-source formats are kept distinct and no unverified API request is provided.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.