Skip to content

Public preview · Free feed checks are available. Paid reports and downloads are not available yet.

How to repair an empty image_link attribute

When image_link is blank in the exported record, diagnose the mapping from source media to Google’s main-image attribute. Extra gallery fields do not replace it.

Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations

What does this issue mean?

The machine attribute image_link holds the main image location. A feed generator may have image data available upstream yet export it only as additional_image_link, a platform media ID or a thumbnail field. Your source store looking correct is therefore not enough; inspect the feed output consumed by Merchant Center.

Why this happens

This issue is often a connector configuration problem rather than missing photography. CSV header aliases can point to the wrong media column, and Atom or RSS exports may omit the Google namespace attribute. Inherited variation media and signed media URLs also need careful handling, because the output must remain usable after the feed is generated.

How to diagnose and fix it

  1. Inspect the raw exported record and distinguish image_link from additional gallery image attributes.
  2. Check the feed integration’s main-image mapping and variant fallback settings.
  3. Use an absolute public image URL that corresponds to the actual offer, without copying a media ID or HTML image tag.
  4. Export a fresh feed and confirm the repaired field reaches the affected product ID.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

<g:additional_image_link>https://example.com/mug.jpg</g:additional_image_link>

After review

<g:image_link>https://example.com/mug.jpg</g:image_link>

An additional image should not be discarded simply to populate the main image. Review the actual main-image choice. Static validation cannot determine image accuracy or crawler accessibility.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies image_link. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Scan your feed for this issue

Check all parsed products in an XML, CSV or TSV feed. Preview the score and issue samples free; unlock affected-product details and downloadable reports with a one-time payment. Conditional findings remain marked for review.

Check My Feed

Frequently asked questions

Does this finding always mean my product is disapproved?

An additional image should not be discarded simply to populate the main image. Review the actual main-image choice. Static validation cannot determine image accuracy or crawler accessibility.

Can Feed Doctor fix image_link automatically?

Only deterministic formatting changes are available in Fix & Export. Missing identifiers, prices, business facts and ambiguous values require manual action. Review every change and remaining finding before submitting a repaired feed.

Should I fix the exported file or my store?

Correct the source product or feed integration whenever possible. A downloaded file edit may be overwritten by the next scheduled export. Keep a backup and compare the exact affected IDs in a fresh feed snapshot.

Do I need to connect Google to scan a feed?

No. Feed Doctor accepts a Google-format XML, CSV or TSV file, or a public HTTPS feed URL. It checks the feed without accessing your Merchant Center account. Reports are private to your browser and expire after 7 days.

Related feed issues

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.