When a record has no SEO image set and its model has no explicit fallback field selected, the CDA doesn’t fall back to the sitewide global SEO image. Instead it silently scans the model for the first image or gallery field, alphabetically by API key, and uses whatever is there, even if that field has nothing to do with SEO. Add a new field with an earlier alphabetical key later, and the fallback silently changes.
This can produce unexpected social preview images with no easy way to tell why.
Would love more explicit control over the fallback chain, so the record’s own SEO image and the sitewide global default are the only things in play unless a fallback field is deliberately configured at the model level.
Something like this order would make a lot more sense, and would still fall back to today’s alphabetical behavior only as a last resort:
Record SEO image → Model SEO image fallback → Global SEO image fallback → current silent field selection (optional)
Curious if others have run into this too!