We’ve been carrying around an issue for quite some time regarding how we manage SEO fallback data. Because the same fields used for internal previews—Title and Image Preview—are also used for SEO fallback data, it’s been causing confusion and often results in less-than-ideal search engine metadata.

To address this, we’re splitting the two settings and creating a dedicated “SEO Fallback” tab!

What’s new?
We’re removing the overlap between “Presentation” fields and “SEO” fields. Now you can explicitly choose which fields feed into your SEO Title, Image, and Description. These are separate from the fields used for internal previews, giving you more granular control over how your content appears in search results.

Why does it matter?
With dedicated SEO fields, you can optimize exactly how content appears on search engines—without affecting the quick, at-a-glance previews in the CMS. This ensures your internal workflow remains clear and uncluttered, while your SEO metadata stays fine-tuned for external audiences.

How do I enable it?
Simply head over to any Model’s settings, locate the new “SEO” tab, and select the fields you want to use for SEO Title, Image, and Description.

If you want to experiment with all the new presentation fields available, explore the head over the Presentation Tab!

⚠️ API Changes

We've introduced two new relationships on the item_type entity: presentation_title_field and presentation_image_field. These relationships are exclusively used for DatoCMS’s internal interface and preview functionality:

• presentation_title_field supports fields of type: string, date, date_time, link, text, structured_text, color, lat_lon, integer, and float.

• presentation_image_field supports fields of type: file, gallery, link, color, date, date_time, and lat_lon.

At the same time, the existing relationships — title_field, image_preview_field, and excerpt_field — are now dedicated solely to configuring SEO fallback settings. As a result:

• title_field no longer accepts fields of type date, date_time, link, text, structured_text, or color. It now only supports string fields.

• image_preview_field no longer accepts fields of type link or color. It now only supports file and gallery fields.

These changes only refine the accepted field types and do not affect functionality, as the previously accepted field types were already ignored for SEO purposes and if ie. a model had a date field set as title_field that field is now set as presentation_title_field.