Use a stable public asset URL for a published product image, rather than relying on a temporary generation download link. A feed crawler may revisit the file after the original link expires or from a different session. Save the approved image through your authorized store or asset-hosting workflow, verify public read access to that specific file and keep private source materials outside the published path.
Test the address, not the dashboard preview
A browser editor can display an image because your account is signed in or because a short-lived token is still valid. That does not establish durable crawler access. Open the published asset as an unauthenticated visitor and confirm that it serves the expected image rather than a login page, redirect loop or expired-link message.
Google’s main-image guidance describes the role and accessibility of image URLs. Use its current requirements for the destination. An AI provider’s convenient download address is a delivery mechanism, not necessarily a suitable permanent publishing address.
Publish only the approved derivative
- Download the completed image you have reviewed.
- Keep the original and revision records in private project storage.
- Upload the approved derivative to the authorized public product-media location.
- Verify its file type, visible content and unauthenticated availability.
- Put that durable asset URL into the appropriate product record or feed.
Do not solve access problems by publishing a whole private directory or weakening account security. Only the approved display file needs public access. If the store handles asset hosting, use its supported upload process rather than inventing a separate file-sharing dependency.
Record the source-to-listing chain
Keep the product identifier, source photograph, approved derivative and public URL together in an internal record. This helps you retire an obsolete listing image or fix a wrong-variant association without guessing which AI download was used. The record belongs to the project, not in public alt text or the image filename if it contains sensitive details.
Is a URL ending in PNG enough?
No. The response must actually serve a supported image to the relevant visitor. File extensions, access permissions and response content can disagree.
Can a signed URL ever be useful?
Yes, for controlled private delivery. Its expiration is often a deliberate protection. Use an appropriate public derivative for a feed instead of turning the private delivery link into a permanent public reference.
Sources and scope
This is an original Imagild Editorial workflow guide, assisted by AI and reviewed against the linked sources on October 12, 2026. External tool procedures do not imply that Imagild provides those tools or guarantees their results.